NTSB CAROL · Event
Event LAX03LA083
Registry · N5400M
FAA Aircraft Registry record.
Make / Model
DJI AGRAS T100
ADS-B equipped
Yes — Mode-S A6DA50
Registrant of record
MASON KENNARD FARMS LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
failure of the CFI to ensure that the pilot under instruction adequately understood the engine out procedure during the preflight planning phase of the flight; failure of the pilot under instruction to obtain/maintain directional control; and the inadequate supervision and delayed remedial action of the CFI during the engine out procedure. The pilot under instruction's misunderstanding of the engine out procedure was a factor in the accident.
Factual narrative
On January 17, 2003, at 1030 Pacific standard time, a Beech 76, N5400M, collided with a snow bank during takeoff from the Tahoe-Truckee Airport (TRK), Truckee, California. The Palo Alto Flying Club was operating the rental airplane under the provisions of 14 CFR Part 91. The airplane sustained substantial damage. The certified flight instructor (CFI) and the private pilot under instruction PUI) were not injured. The cross-country instructional flight departed the Palo Alto Airport of Santa Clara County (PAO), Palo Alto, California, at 0845, en route to TRK. Visual meteorological conditions prevailed, and no flight plan had been filed. On February 5, 2003 the incident was upgraded to an accident after verification that the airplane had been substantially damaged. According to the CFI, the purpose of the flight was to practice maneuvers. At TRK he briefed the PUI on the procedures for a simulated engine failure on takeoff, which included recovery procedures. The PUI aligned the airplane with the runway centerline. The PUI engaged the brakes, added partial power, and then full power. The PUI released the brakes, and the CFI leaned the left mixture to idle cut off. The CFI stated that the airplane yawed to the left, and the PUI "failed to pull the throttles to idle." The airplane collided with the snow bank. The CFI reported that prior to colliding with the snow bank, the right mixture was to idle cut off. According to the PUI, they had conducted engine out procedures on the training flight from PAO. After landing the CFI suggested that, since the runway was 7,000 feet long, it would be a good airport to practice engine out procedures during the takeoff roll. There would be plenty of room to stop. The PUI stated that the CFI explained the "procedure of reducing power, using rudder to control direction, and stated that he would fail the left engine." The PUI indicated that his understanding was that the "failure" would occur after they "were underway" in the air. He was surprised when the airplane veered to the left immediately after he started to add power. He was too slow in "reducing power, [and] fixated on rudder control." Both pilots reported that there were no mechanical anomalies with the airplane. The airplane veered off the runway and struck a snow bank off the left side of the pavement. The CFI briefed on an engine out procedure prior to takeoff and told the student he was going to fail the left engine. However, the pilot under instruction (PUI) did not fully understand the procedure. He believed that the engine failure would happen when they were in the air and not on the ground. During the takeoff roll, the CFI simulated the engine out by pulling the left mixture. However, the PUI did not pull the throttles to idle as briefed. He was surprised when the airplane started to veer to the left during the takeoff roll. He fixated on the rudder controls, and did not reduce engine power on the right engine. Both pilots stated that there were no mechanical anomalies with the airplane. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_LAX03LA083.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 (engine failure). 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 2018 · Accident report
Atlas Air Flight 3591 Boeing 767 Loss of Control (preliminary)
Atlas Air 3591 / Boeing 767-300 / Trinity Bay TX (Feb 23 2019) — preliminary. Preliminary investigation findings; superseded by the AAR-21/01 final report.
- 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.
- arXiv 2022 · arXiv preprint
Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NASA NTRS 2019 · Conference Paper
Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
Browse the full corpus — academia portal ↗