NTSB CAROL · Event
Event ATL05CA131
Registry · N3ST
FAA Aircraft Registry record.
Make / Model
LEARJET INC 45
Year of manufacture
2014
Engine
HONEYWELL TFE731-40BR-1
Seats / Engines
12 seats · 2 engines
Last airworthiness date
20141218
ADS-B equipped
Yes — Mode-S A31C42
Registrant of record
SOUTHERN TIRE AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's delay in aborting the landing and his failure to maintain obstacle clearance. Contributing factors were hydroplaning condition, and the localizer antenna.
Factual narrative
On July 15, 2005 at 1510 eastern daylight time a Cessna 525A, N3ST, registered to Beehawk Aviation Inc., operating as a 14 CFR Part 91 business flight, collided with a localizer antenna during a go-around at Newnan Coweta County Airport, Newnan, Georgia. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed. The airplane received substantial damage. The airline transport rated pilot and four passengers reported no injuries. The flight originated from Venice, Florida, on July 15, 2005, at 1345. The pilot stated he obtained a computer weather briefing before departing Venice, Florida. No thunderstorms or rain was forecast for the destination airport. The pilot was cleared by Atlanta Center to descend to11,000 feet. The pilot listened to the Aviation Weather Observation Service for Newnan, Georgia, and there was no report of thunderstorms or rain showers in the vicinity. The pilot requested a visual approach from the controller. The controller informed the pilot to intercept the localizer for runway 32 and informed the pilot their was weather to his front. The pilot observed the weather at 25 miles on his radar screen. When the flight was 10 miles from the locator outer marker the controller asked the pilot if he wanted to continue with the visual approach. The pilot stated no and was cleared for the localizer runway 32 approach. The pilot lowered the flaps to 15-degrees, upon reaching the locator outer marker lowered the landing gear was lowered, and the airspeed was reduced to 125 knots. When the airplane was 5 miles from runway 32, the pilot observed rain showers crossing the final approach course; however the runway remained in sight. The pilot slowed the airplane to 115 knots and crossed through and out the other side of the rain shower while descending through 200 feet. The airplane touched down on runway 32 at the 1,000-foot marker. The pilot lowered the flaps to 60 and brakes were applied and the airplane started to hydroplane. The airplane began to drift nose right and left rudder was applied. The hydroplaning increased so the pilot released the brakes. The airplane slowed to 78 knots and the airplane continued to hydroplane. The pilot applied brakes again and the airplane continued to hydroplane. The pilot initiated a go-around with 2,300 feet of runway remaining. The flaps were raised to 15-degrees and the thrust levers were set for take off. The airspeed increased to 80 knots and the airplane continued to hydroplane for the next 500 to 800 feet. The pilot could see the end of the runway approaching and observed the localizer antennas off the departure end of the runway. The pilot rotated the airplane, and the airplane became airborne 300 feet from the end of the runway. The airplane was slow to climb and the pilot informed his front seat passenger that the airplane was going to collide with the localizer antennas. The airplane collided with the antennas on leading edge of the right wing and left gear door. The pilot continued the climb to traffic pattern altitude and checked the airplane for responsiveness and damage. At the same time he called the fixed base operator and informed him he was going to make a low pass down runway 14 and asked them to check for damage. He made the low pass and was informed by personnel on the ground that everything seemed ok. The pilot landed the airplane with out further incident. Review of airport information revealed the Newnan asphalt runway is 5, 500 feet long and 100 feet wide. According to the Airport Manager the runway is in good condition and is crowned in the middle for water drainage. Additional crowning is scheduled to be added to the airport in August 2005. The runway is not grooved and there are no plans to groove the runway. Review of information obtained from Aeronautical Learning Laboratory For Science Technology And Research, Hydroplaning is a condition that can develop whenever a tire is moving on a wet surface. The tire squeezes water from under the tread generating water pressures which can lift portions of the tire off the runway and reduce the amount of friction the tire can develop. On a runway contaminated by rain or wet snow, it can be possible for an airplane to accelerate to take-off speed and then to stop on the runway in an aborted take-off. During landing, deceleration and stopping an airplane can be similarly compromised. The pilot obtained a full weather briefing before departing on an instrument flight. No thunderstorms or rain was forecasted for the destination airport. The pilot was requested and received clearance for a visual approach at the destination airport. The pilot listened to the AWOS information and no rain or thunderstorm activity was reported. The controller informed the pilot their was a weather cell located 25 miles north of his position and provided a vector for a localizer runway 32 approach. The pilot verified the weather on the airplanes weather radar. The pilot was cleared for the approach 10 miles from the locator outer marker. The pilot lowered the flaps to 15-degrees and extended the landing gear at the locator outer marker. The pilot slowed the airplane to 115 knots and observed rain showers crossing the runway while descending through 200 feet. The airplane touched down at the 1,000 foot marker and the flaps were lowered to 60. The antiskid was on and the airplane started hydroplaning. The pilot attempted to use brakes and the hydroplaning increased. The pilot released the brakes and the airplane slowed down to 78 knots. The pilot applied brakes and the hydroplaning continued. The pilot elected to abort the landing with 2,300 feet of runway remaining. The airplane continued to hydroplane and became airborne 300 feet from the end of the runway. The left main landing gear door and right leading edge of the right wing collided with the localizer antenna on climb out. The pilot climbed to traffic pattern altitude , checked for damage, contacted personnel on the ground , and made a low pass for a visual check of damage. The pilot reentered left traffic and landed with out further incident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_ATL05CA131.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around, thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
Browse the full corpus — academia portal ↗