NTSB CAROL · Event
Event ERA11LA345
Registry · N129SG
FAA Aircraft Registry record.
Make / Model
SELECTTECH GEOSPATIAL LLC EH-4
ADS-B equipped
Yes — Mode-S A076B8
Registrant of record
SELECTTECH GEOSPATIAL LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot-in-command's failure to execute a go-around when the airplane was high and fast on the final approach.
Factual narrative
On June 15, 2011, about 1725 central daylight time, a Cessna 525A, N129SG, was substantially damaged following a runway overrun at John C. Tune Airport (JWN), Nashville, Tennessee. The certificated airline transport pilot and four passengers were not injured. The airplane was registered to and operated by Deer Horn Aviation LTD under the provisions of 14 Code of Federal Regulations Part 91, as a business flight. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed. The flight originated from Artesia Municipal Airport (ATS), Artesia, New Mexico, about 1406 mountain daylight time. The pilot-in-command (PIC) reported the following. As the airplane was approaching JWN, one of the owners of the airplane, who held a student pilot certificate, was in the right seat and at the controls. Air traffic control vectored the airplane to the final approach course, and the PIC acquired the airport and cancelled the IFR clearance. He informed the student pilot that the airplane was "high and hot" and he needed to "get down and slow down." The student pilot told the PIC that this "landing is yours" and the PIC assumed the controls. He configured the airplane for landing and "started a steep approach." He considered a go-around, but elected to continue the approach. Approaching the runway, the "sink rate" and "pull up" aural warnings activated on the ground proximity warning system (GPWS). He continued with the approach and the airplane touched down about 1,500 feet down the 5,500 foot long runway. The PIC applied the brakes fully, but the airplane continued down the runway. The PIC reported that he could feel the antiskid braking system working, but he neglected to consider the runway condition, which was wet. The airplane overran the runway and struck the instrument landing system antennas. The PIC applied full left rudder to avoid going down an embankment. The airplane came to rest after turning about 180 degrees. An inspector with the Federal Aviation Administration responded to the accident site and examined the airplane. The left main landing gear was collapsed, and structural damage to the wings was evident. The cockpit voice recorder (CVR) was sent to the NTSB Vehicle Recorders Laboratory for further examination. A review of the CVR recording revealed the following. The recording began at 1521 as the airplane was in cruise climb to flight level 390. The student pilot was at the controls, receiving guidance and instruction from the PIC. During cruise, the pilots discussed various non-pertinent topics, interspersed with operational instruction related to convective activity along the route, avionics, aircraft operating techniques, and the use of weather radar. During the descent into JWN, the student pilot noted how fun it was to deviate around thunderstorms while the PIC explained that the nearby storms were of significant intensity. About 1717, air traffic control assigned an altitude of 3,000 feet and the PIC directed the student pilot to start a descent. The PIC advised the student that the winds may be gusty and that he had the student’s "back." About 1721, after ATC assigned a 170 degree heading and cleared the aircraft for the instrument landing system (ILS) runway 20 approach, the PIC noted that the localizer was not being received. He then realized that he had entered the incorrect frequency into the radio. The airplane subsequently flew through the localizer course, and ATC issued a vector to re-intercept the course. At 1722, the PIC noted that the airplane was on course, reported that the runway was in sight, and cancelled the IFR flight plan with ATC. At 1723, the PIC noted that the aircraft was "real high," and the student pilot should get the plane down. The student pilot acknowledged, and then asked the PIC if he wanted to take the landing. The PIC responded that he would take the controls. The PIC then advised on the common traffic advisory frequency that the airplane was on a straight-in approach to runway 20 at JWN. At 1724, the GPWS announced "sink rate sink rate," followed by a radio altimeter annunciation of "five hundred." From this point until touchdown, the GPWS repeated "pull up" eight times, as the PIC stated, "Don’t worry about it." During the landing roll, the student pilot and the PIC began making animated expressions of concern, commencing at 1724:56 and continuing until the end of the recording. The PIC reported that he was not a certified flight instructor. He also reported that there were no mechanical malfunctions or failures with the airplane during the accident flight. JWN was equipped with an Automated Weather Observing System (AWOS); however, at the time of the accident, wind, temperature, and dew point information were not available. The 1711 weather at Nashville International Airport (BNA) located 9 miles east of JWN, included the following: winds from 180 degrees at 6 knots, 6 miles visibility, light rain and thunderstorms, scattered clouds at 4,500 feet, scattered cumulonimbus clouds at 6,000 feet, broken clouds at 11,000 feet, overcast clouds at 25,000 feet, temperature 19 degrees Celsius, dew point 18 degrees Celsius, and altimeter 29.78 inches of mercury. Thunderstorms began at 1701 and rain began at 1701. There was occasional lightning in the area. As a result of the accident, the operator modified its operational procedures to restrict unqualified personnel from the cockpit during flight. Also, a formal risk assessment program was initiated. The pilot-in-command (PIC) was in the left cockpit seat, and a passenger, who possessed a student pilot certificate, was in the right cockpit seat. The PIC was not a certificated flight instructor; however, the student pilot was at the controls for a majority of the flight. During the descent and initial approach, the student pilot allowed the airplane to become high and fast, and the PIC subsequently took over the controls and continued the approach. During the final approach, the ground proximity warning system announced "sink rate" eight times. After touchdown, the antiskid system activated; however, there was insufficient runway remaining on which to stop the airplane. The PIC reported that he neglected to consider the wet runway condition. The airplane overran the runway and struck the instrument landing system antennas before coming to a stop. The PIC reported that there were no mechanical malfunctions or failures during the flight. As a result of the accident, the operator modified its operational procedures to restrict unqualified personnel from the cockpit during flight and initiated a formal risk assessment program. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Action/decision-Action-Lack of action-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Incorrect use/operation - C
Verbatim from NTSB's published report. Source file
NTSB_2011_ERA11LA345.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 ↗