NTSB CAROL · Event
Event CEN11LA651
Aircraft involved
Probable cause & findings
The loss of engine power due to fuel starvation during climbout for undetermined reasons, because postaccident examination of the fuel system did not reveal any discrepancies that would have precluded normal engine operation. Contributing to the accident was the pilot not visually checking the fuel level prior to departure.
Factual narrative
On September 17, 2011, about 1807 eastern daylight time, a North American AT-6, N217RK, impacted a tree and terrain after a loss of engine power during takeoff from runway 8 (3,600 feet by 100 feet, dry turf) at the Hat Field Airport (5N7), near Nunica, Michigan. The commercial pilot received serious injuries. The airplane sustained substantial firewall, fuselage, and wing damage. The airplane was registered to Tailwinds Inc. and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Day visual flight rules (VFR) conditions prevailed for the flight, which was not operated on a VFR flight rules flight plan. The flight was originating at the time of the accident and was destined for the Mason Jewett Field Airport, near Mason, Michigan. Review of a video taken at 5N7 revealed that the airplane was the fourth airplane in a flight of multiple airplanes to depart the airport. The video revealed that the accident airplane lost power during its takeoff, impacted a tree on the left side of the departure runway, and subsequently impacted terrain. The pilot’s accident report indicated that the airplane was "ground checked" and each aircraft took off as briefed in a single-ship sequence leaving nine seconds between each departure, which allowed any departing aircraft time to abort its takeoff roll. The pilot indicated that he applied full takeoff power. As the airplane passed about two-thirds of the runway’s length, the airplane had a positive rate of climb. The low fuel pressure light illuminated just before gear retraction, the fuel pressure dropped to zero, and the engine abruptly quit. The pilot lowered the airplane’s nose and impacted a tree during the forced descent. The impact turned the plane, causing it to hit the ground at a vertical angle tearing the engine and propeller from the plane. According to the pilot, the airplane had been refueled prior to flying to the accident airport to its full capacity of 110 gallons, of which, 106 gallons is usable. The airplane had two 55-gallon fuel tanks, one in each wing. The fuel selector has four positions; right tank on, left tank on, left tank reserve, and off. The pilot indicated that the “flight to the accident airport required 50 minutes, which would have burned, with start-up, taxi and flight time, 29 gallons. This was verified prior to departure at the accident airport by visual reference of fuel gauges and aircraft fuel flow meter.” However, the pilot did not visually check the level of the fuel tank’s contents. A Federal Aviation Administration inspector examined the wreckage. The inspector indicated he observed that the right fuel tank was full. The gascolator contained a cup of fuel and the screen was clean. The engine driven fuel pump was removed from the engine and the pump produced suction when rotated by hand. The fuel selector was found set to the reserve position. The wobble pump was able to pump fluid and produced pressure at its output port. The left main and reserve standpipes and screens were installed correctly and were free of obstructions. The left fuel tank contained about four gallons of fuel. The airplane’s engine monitor and fuel flow monitor were shipped to the National Transportation Safety Board Recorder Laboratory for downloading. The airplane was equipped with a J. P. Instruments EDM-700 panel mounted engine monitor gauge. The gauge monitored and recorded exhaust gas temperature, cylinder head temperature, and battery voltage. The gauge was in good condition and its data was extracted normally from the device. The download contained approximately 11 hours of data over 18 power cycles. The data from the accident flight and the flight prior to it were plotted. The plot of the flight prior to the accident, on September 17, 2011, covered a time period from 14:24:00 to 15:28:12. The accident flight plot covered a time period from 17:58:46 to 18:07:10 and no recorded engine anomalies were detected in the plot. The airplane was also equipped with a Shadin Avionics Miniflo-L fuel flow monitor gauge, which was a digital fuel management system, designed to provide fuel management information under real time flight conditions to the pilot. The unit does not interface with an airplane’s fuel quantity indicating system. The unit required the pilot to enter the initial fuel on board the aircraft. All calculations and data provided by the unit were based on fuel flow. The fuel flow indicator unit was received in good condition and it reported a value of “good” when it self-tested as power was applied. Its data indicated 32.5 gallons of fuel used and 77.1 gallons remaining. The pilot’s safety recommendation, in part, stated: I do know that wearing my seat belt with shoulder harness and aviation flight helmet likely saved my life. When flying these types of planes, please always wear your safety gear. You can't choose when an accident may occur, but you can be prepared when it does. According to the pilot, the airplane had been refueled to its full capacity prior to the flight to the accident airport. The pilot indicated that the "flight to the accident airport required 50 minutes, which would have burned, with start-up, taxi, and flight time, 29 gallons.” The pilot then departed the accident airport and stated that he applied full takeoff power. On climbout, the low fuel pressure light illuminated just before gear retraction, the fuel pressure then dropped to zero, and the engine abruptly lost power. A video taken at the airport where the accident occurred revealed that the airplane lost power during takeoff, impacted a tree on the left side of the departure runway, and subsequently impacted terrain. The airplane’s engine monitor data revealed no recorded engine anomalies and fuel flow monitor data indicated 32.5 gallons of fuel used up to the time of the accident, and 77.1 gallons remaining. The pilot stated that he verified the fuel prior to departure at the accident airport by visual reference of fuel gauges and airplane fuel flow meter. Examination of the wreckage revealed that the right fuel tank was full. No anomalies were detected during the examination of the engine-driven fuel pump, gascolator, and the wobble pump. The fuel selector was found selected to the reserve position, which feeds from the reserve fuel retained within the standpipe and any additional left tank fuel above that retained reserve amount. The left main and reserve standpipes and screens were installed correctly and were free of obstructions. The left fuel tank contained about four gallons of fuel when it was defueled. The pilot did not visually check the level of the fuel tank’s contents prior to departure; had he done so, he would have recognized that the left tank’s fuel level was below what was expected. Fuel usage figures provided by both the pilot and the engine monitor data indicated there should have been over 20 gallons of fuel remaining in the left tank at the time of the accident. The reason for the discrepancy between the expected and actual fuel amounts could not be determined. 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 Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level - C
- F Personnel issues-Task performance-Inspection-Preflight inspection-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2011_CEN11LA651.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, fuel starvation). 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 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 …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗