NTSB CAROL · Event
Event SEA07LA270
Aircraft involved
Probable cause & findings
The pilot's failure to follow the manufacturer's procedures during a go-around and subsequent loss of airplane control. A contributing factor to the accident was the dark night.
Factual narrative
On September 21, 2007, about 1930 Pacific daylight time, a Socata TB20, N203AB, collided with terrain during a go-around at Beatty Airport, Beatty, Nevada. The pilot, who was also the registered owner of the airplane, was operating it under the provisions of 14 CFR Part 91. The private pilot and passenger sustained serious injuries. The airplane was substantially damaged. Night visual meteorological conditions prevailed and no flight plan was filed. The airplane departed from Derby Field Airport, Lovelock, Nevada, about 1800. The pilot reported in a written statement that he decided to land at Beatty due to deteriorating weather at his destination. During the approach to runway 34, about 400 to 500 feet above ground level, it appeared to him that the airplane was high, so he initiated a go-around. The pilot applied full throttle, retracted the flaps one notch, and retracted the landing gear. Without warning, the airplane impacted the ground on the downwind leg. After evacuating the airplane he observed the landing gear in the down position. The pilot reported 242 hours total flight time, with 10.6 hours over the last 24 hours. He reported 8.0 total night hours. The pilot had flown 1.6 hours at night in the last 90 days and 0.8-hour at night in the last 30 days. The passenger, also a pilot, reported approximately 3,500 hours total flight time. He was not familiar with the accident airplane as the majority of his time was in high-wing Cessna airplanes. During the flight, the passenger assisted the pilot with navigation but did not fly the airplane. The passenger reported that while en route, they encountered weather and decided to land at Beatty. The weather conditions at the time were clear at Beatty, but it was dark. The passenger stated that the pilot aligned the airplane for the approach to runway 34, but he thought the airplane was too high and was descending too quickly, at a rate of 1,200 feet per minute. As the airplane crossed the threshold, he told the pilot that he should perform a go-around. The pilot applied full power and turned crosswind, then turned onto the downwind leg. Shortly thereafter, the left wing clipped the ground and the airplane cartwheeled. The passenger reported that he was knocked unconscious during the collision sequence, but prior to ground impact, he did not hear any stall warnings or feel a buffet. He could not recall if the pilot retracted the landing gear and/or flaps, and he thought that the pilot might not have arrested his descent, prior to initiating the go-around and making turns in the traffic pattern. He did not believe that there were any mechanical anomalies that resulted in a loss of control. During the on-site documentation, the first identified piece of wreckage was the left wing tip. A 500-foot distance separated the wing tip and the main wreckage. Both wings were sheared from the structure and in pieces leading up to the main wreckage. The landing gear was in the extended position. According to aircraft recovery personnel, the cockpit flap indicator showed that the flaps were in the fully retracted position. The landing gear selector handle was in the extended position. The Pilot Operating Handbook for the airplane indicates under Normal Procedures, Section 4, that during a go-around, smoothly apply power and obtain/maintain 76 to 81 knots indicated airspeed (KIAS). Then, once the climb rate is positive, retract the landing gear and set the flaps to the takeoff setting. Once 90 KIAS is reached, fully retract the flaps and climb at 95 KIAS. According to the United States Naval Observatory records for Las Vegas, Nevada, on September 21, 2007, sunset was at 1839 and the end of civil twilight was at 1905. The pilot and passenger were on a cross-country flight. After night had fallen, they encountered deteriorating weather conditions, and diverted to an airport along their route of flight. During the final approach leg of the traffic pattern, the airplane entered an excessive descent rate, and the pilot initiated a go-around. As the pilot turned the airplane onto the downwind leg, the left wing impacted the ground. The pilot operating handbook for the airplane indicates that once a positive rate of climb is established, the landing gear should be retracted, as well as incremental flap retraction. Although the pilot believed that he retracted the flaps and landing gear, the cockpit selectors were both found in the extended position. The pilot had approximately 8 hours total night flight time, with 0.8-hour in the 30 days prior to the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2007_SEA07LA270.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 (stall, loss of control, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- 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.
Browse the full corpus — academia portal ↗