NTSB CAROL · Event
Event SEA96LA121
Aircraft involved
Probable cause & findings
failure of the non-certificated pilot to ensure that the landing gear was properly extended for landing. The non-certificated pilot's diverted attention was a related factor.
Factual narrative
On June 9, 1996, at approximately 2100 Pacific daylight time, N2145D, a Beech 35, sustained substantial damage in a wheels-up landing at Aurora State Airport, Aurora, Oregon. The aircraft was being operated under 14 CFR 91 on a local flight out of Aurora. The non-certificated pilot (who owned the aircraft but had not registered it to his name since purchasing it in approximately January 1994) and a pilot-rated passenger (who holds a commercial pilot certificate but did not hold a current medical certificate at the time of the accident) were not injured. Visual meteorological conditions prevailed at the time of the accident and no flight plan had been filed. In a telephone interview with an FAA inspector in the Hillsboro, Oregon, Flight Standards District Office (FSDO), the pilot/owner stated that his passenger was acting as pilot-in-command and was flying the aircraft at the time of the accident. However, the passenger stated to investigators that he was not flying the aircraft at the time of the accident, and that he had been unaware that the pilot/owner of the aircraft did not hold a pilot certificate. He said that he would not have flown with the pilot/owner if he had known the pilot/owner did not have a license. The passenger also stated that he did not touch the aircraft controls "except to save my life when I realize[d] the gear was retracted on touchdown." The pilot/owner indicated on his accident report that he occupied the left seat, with the pilot-rated passenger in the right seat of the aircraft. Both occupants stated to the FAA inspector that while in the traffic pattern, their attention was diverted while searching for another aircraft which called inbound to Aurora on an instrument approach and reported being at their altitude. The passenger stated that the gear was initially down and that the pilot/owner raised the gear during the search for the other aircraft. The pilot/owner stated that he thought the passenger "cycled the landing gear twice" before the accident. The passenger, who also is a Bonanza owner and has logged about 2,500 hours of pilot time, said that as the pilot/owner began the landing flare he could tell by the speed and pitch attitude that the gear had not been extended. He said that when the tail touched, he reached forward and pulled back on the yoke in order to cushion the contact with the runway. The aircraft then slid to a stop on the runway on its belly. According to the passenger, he did not realize the pilot/owner did not hold a pilot certificate until he was advised of that situation after the accident. No problems were found in the aircraft's gear extension system, and neither occupant claimed that there had been any malfunction. According to copies of the aircraft logbook, the aircraft's last annual inspection, dated April 15, 1996 at 3,452.0 tachometer hours, was signed off as: "This aircraft has been inspected IAW an annual inspection and a list of discrepancies dated 1-2-96 has been provided to the aircraft owner." The logbook entry indicated that per FAA Airworthiness Directive (AD) 62-08-03, cracks were found but no further action was taken. This AD mandates inspection of certain type control wheels for cracks every 100 hours in service or 12 calendar months, and specifies that if cracks are found, the control wheels are to be replaced before further flight. Although a subsequent aircraft logbook entry, dated May 24, 1996 at 3,455 tachometer hours, indicated that a "loaner dual control yoke" had been installed by Flightcraft, Inc. of Portland, Oregon, no further evidence was provided to indicate that the aircraft had been signed off as airworthy, based on annual inspection, within the 12 months prior to the accident. The passenger held a commercial pilot certificate, but did not have a current medical certificate. According to him, the non-certificated pilot/owner was attempting a touch-and-go landing, when they were both distracted by a call from the pilot of another aircraft which was on an instrument approach to the same airport. Neither the passenger nor the pilot/owner realized the gear was not down until the tail of the aircraft contacted the asphalt runway. The aircraft then slid to a stop on its belly. Although the pilot/owner claimed the passenger was the pilot-in-command, the passenger said he did not realize the pilot/owner did not hold a pilot certificate until advised of that situation after the accident; he said that he would not have flown with the pilot/owner had he been aware of this fact. The aircraft had not been certificated as airworthy, per annual inspection, within the previous 12 months. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_SEA96LA121.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). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2022 · Journal article (JAAER)
SMS for Part 135 Commuter and On-Demand Operations - The Practitioner’s Perspective
On May 15th, 2017, N452DA, a Learjet 35A operated by Trans-Pacific Air Charter, LLC, departed from Philadelphia to Teterboro, New Jersey (TEB) on a positioning flight under 14 Code of Federal Regulati…
- 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.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
Editor's Note: Celebrating 35 Years of Scholarly Excellence
A letter from the editor, Dr. Dahai Liu, on the JAAER's 35th anniversary.
- NASA NTRS 2024 · Presentation
Part 135 and Business Operator Low Altitude Events: An Analysis of ASRS Reports
This presentation provides an aviation SME's human factors analysis of selected Low Altitude and Controlled Flight Towards Terrain (CFTT) events involving Part 135 and business jet operators as report…
- NASA NTRS 2022 · Conference Paper
The In-time Aviation Safety Management System Concept for Part 135 Operators
Transformations of the National Airspace System, such as envisioned with Advanced Air Mobility, will enable improvements for managing and assuring safety for Part 135 transportation of passengers and …
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA)
Analysis of Part 135 Aircraft Accidents to Facilitate Flight Data Monitoring
The scheduled and on-demand air services with Title 14 Code of Federal Regulations (CFR) Part 135 certificate are operating with relatively less stringent safety program criteria compared to Part 121 …
Browse the full corpus — academia portal ↗