ERA24FA323 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of control in flight on approach
From Morristown Municipal Airport (MMU) to an unrecorded destination
Event
- NTSB case
- ERA24FA323
- 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
- 2 · 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
- Instrument Meteorological Cond
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N990PT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morristown Municipal Airport (MMU), Morristown, NJTo not recorded
- Aircraft age
- About 1 year (built 2023)
- 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
- Approach · IFR missed approach
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot received a weather briefing package from a commercial service when he filed his instrument flight rules (IFR) flight plan before departing on the accident flight. The weather briefing information the pilot received included forecasts and AIRMETs for low IFR (LIFR) conditions at the destination airport during the planned time of arrival (LIFR, refers to a cloud ceiling below 500 ft above ground level [agl] and/or visibility less than 1 mile). Reported conditions at the destination airport about 31 minutes before the accident included visibility of 1.5 miles in light rain and mist and an overcast ceiling at 300 ft agl. As the flight neared the destination airport, an air traffic controller provided the pilot with a radar vector, cleared the flight for an instrument landing system (ILS) approach. The ILS approach specified a minimum visibility of 3/4 mile and a decision height of 200 ft agl, or 283 ft mean seal level (msl). A review of flight data parameters downloaded from the airplane’s recoverable data module (RDM) revealed that the airplane’s autopilot was engaged for nearly the entire flight, from shortly after takeoff to about 17 seconds before the accident. The data showed that, after the controller cleared the flight for the approach, the airplane turned to the assigned heading vector, then it turned to a heading consistent with the final approach segment and began a descent toward the runway. When the airplane was about 200 ft msl (or about 117 ft agl) and about 0.4 nautical mile (nm) from the runway threshold with the flaps fully down, the autopilot was disengaged. The airplane’s pitch angle then increased rapidly to about 30° nose-up, its vertical ascent rate reached about 2,350 ft per minute (fpm), its flaps were reduced to 50%, and it climbed to about 450 ft msl, where it remained for about 2 seconds before it began to descend. The airplane then transitioned to an extreme nose-down pitch and extreme left-bank roll while its engine power increased. It briefly rolled back toward wings-level before again entering a left-bank roll, and its descent rate increased to about 4,000 fpm before the data ended. A witness outside at the airport stated that he heard the airplane’s engine noise go to full power, and, when he looked up, he saw the airplane in a sharp left turn before it descended to the ground. He stated that the weather conditions were “brutal” and that he could barely see the airplane at 200 yards away due to the thick fog. A witness who was driving a car near the airport captured video of the airplane in an uncontrolled descent, coming into view as it descended below a low cloud/fog layer. The airframe was largely consumed by a postimpact fire that precluded a detailed examination of flight control continuity; however, all major components of the airplane were identified. Examination of the identified airframe components and the engine revealed no evidence of any preimpact malfunction, and a review of engine data parameters recovered from the RDM revealed that the engine operated normally throughout the flight. The autopsy of the pilot indicated cardiovascular disease that could be associated with increased risk of an impairing or incapacitating cardiovascular event such as heart attack or stroke. Although such an event cannot be excluded by autopsy evidence alone, there is no evidence that such an event occurred. Postmortem toxicology testing detected the opioid codeine, the codeine metabolite morphine, and thebaine. The presence of thebaine is not explained by pharmaceutical codeine use and likely indicates poppyseed consumption. It is possible that the measured codeine and morphine levels might be attributable to poppyseed consumption alone, although the possibility that codeine was also used cannot be excluded. Regardless, the codeine concentration in postmortem heart blood was low, and no morphine was detected in blood. As such, there is no clear evidence that the pilot was impaired by opioid effects at the time of the accident. Overall, there is no clear indication from reviewed evidence that the pilot was significantly impaired by effects of medical conditions or medications, but this possibility cannot be excluded given his identified risk factors for impairment. The pilot’s logbooks were not recovered, so his total or recent experience flying in instrument meteorological conditions (IMC) was not known. Based on the available weather information, it is likely that the airplane was in IMC as the pilot descended on autopilot below the ILS approach decision height. The pilot’s subsequent actions while hand-flying the airplane, which included increasing the airplane’s pitch, reducing the flaps, and increasing engine power, were consistent with the initiation of a missed approach. Although vestibular illusions are commonly experienced by pilots during maneuvering flight in IMC, the accident pilot’s aggressive pitch control inputs while executing the missed approach likely intensified such vestibular illusions, increasing the likelihood of his experiencing spatial disorientation. The airplane’s subsequent extreme nose-down pitch and extreme left roll were consistent with the pilot’s loss of airplane control due to spatial disorientation.
Probable cause
The pilot’s aggressive pitch and power control inputs while executing a missed approach, which resulted in his spatial disorientation and a loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA323
- Event ID
- 20240725194767
- Case number
- ERA24FA323
- 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, coordinates, cause areas. 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: d7dc86606bb3b94a8bed4de444fae55973818e616aa82b52fd1fb5c907e2b2c6; retrieved 2026-09-15T08:25:20.798Z.