FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA349 · Mooney Airplane Co Inc M20TN

10 Sept 2015 · Atlantic City, AO, United States Possible conflict

Mooney Airplane Co Inc M20TN · Accident en route

From Gaylord Regional Airport (GLR) to Atlantic City International Airport (ACY)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA15LA349
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Mooney Airplane Co Inc M20TN

Aircraft type
Mooney M20
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N370MM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gaylord Regional Airport (GLR), Gaylord, MITo Atlantic City International Airport (ACY), Atlantic City, NJ
Aircraft age
About 8 years (built 2007)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Physical
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot departed Michigan on a personal cross-country flight in the autopilot-equipped airplane destined for New Jersey. Air traffic control records indicated that after the airplane departed, about 1200, a controller instructed the pilot to climb to 25,000 ft mean sea level (msl). At 1216, the pilot read back the assigned altitude and continued toward the destination. About 23 minutes later, the controller attempted to contact the pilot; however, the pilot did not respond. Controllers' repeated attempts to contact the pilot throughout the remainder of the flight were unsuccessful as the airplane continued flying a straight course toward the destination.

According to radar data, about 2 hours 22 minutes after the pilot's last transmission and while about 5 miles northwest of the destination, the airplane began descending out of 25,000 ft msl while on a southeast heading until it impacted the Atlantic Ocean about 8 minutes later. Given that the pilot refueled the airplane several days before the flight and filed a flight plan that indicated that the airplane's fuel onboard would allow for 6 hours of flight, it is likely that both fuel tanks had 51 gallons of fuel onboard. Fuel consumption calculations indicate that the airplane would consume up to 22.6 gallons of fuel per hour at cruise flight at 25,000 ft. Therefore, it is likely that the amount of fuel consumed on the day of the flight, given initial takeoff and climb consumption in addition to the 2 hours 22 minute cruise flight, would have been equivalent to the fuel available in one tank. Without pilot action to switch fuel tanks, the engine became starved of fuel and the airplane began its descent to the ocean.

An examination of the airframe and engine revealed no preimpact anomalies that would have precluded normal operation.

During an examination of the oxygen system on the airplane, a fitting, which connected an oxygen line to a regulator on the tank, was found loose and could be moved in both directions by hand without resistance. The oxygen system was serviced with oxygen 5 flight hours before the accident and had a capacity of at least 11 hours of oxygen for pilot-only operations; however, it is likely that the loose oxygen line allowed oxygen to escape and drained the oxygen canister more quickly than the pilot expected. Therefore, although the pilot was found wearing an oxygen mask, given the high altitude the airplane was at for the duration of the flight, the pilot's failure to respond to controller contact, and evidence indicating that he would have had reduced availability of supplemental oxygen, it is likely that the pilot became incapacitated due to hypoxia. The airplane's continued flight at 25,000 ft msl and its descent profile were consistent with the airplane operating under autopilot control and then descending to water impact due to fuel starvation.

The servicing of the oxygen system was performed at the time of an annual inspection, which should have included an inspection of the oxygen system for leaks.

Toxicology testing of specimens from the pilot detected 26 mg/dL ethanol in the blood; given that no ethanol was detected elsewhere, the low level of ethanol detected in pilot's blood was likely due to postmortem production not from ingestion; therefore, ethanol likely did not contribute to the accident. Diphenhydramine, an impairing medication that causes sedation, altered mood, and impaired cognitive and psychomotor performance, was detected in the liver and cavity blood. Because diphenhydramine undergoes postmortem distribution, levels may have been significantly lower than the detected postmortem levels ; therefore, it could not be determined whether the pilot's use of diphenhydramine contributed to the accident.

Probable cause

A loose oxygen line, which was not detected by maintenance personnel during a recent annual inspection, that allowed oxygen to escape and drain the oxygen canister more quickly than the pilot expected. This reduced the pilot's availability of supplemental oxygen and led to his experiencing hypoxia and the airplane subsequently flying on autopilot until it eventually lost power due to fuel starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA349
Event ID
20150910X75635
Case number
ERA15LA349
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d02b7c3bcb98fc67848396b8984352bdf0e670d706fe5d8f351a705ec4aea31f; retrieved 2026-09-14T21:30:44.413Z.