ASN Wikibase Occurrence # 203780
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Wednesday 3 January 2018 |
Time: | 19:06 LT |
Type: | Cirrus SR22T |
Owner/operator: | Abide Aviation LLC |
Registration: | N325JK |
MSN: | 1290 |
Year of manufacture: | 2016 |
Total airframe hrs: | 426 hours |
Engine model: | Continental TSIO-550-K1B |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Gulf of Mexico -
United States of America
|
Phase: | En route |
Nature: | Private |
Departure airport: | Oklahoma City-Wiley Post Airport, OK (PWA/KPWA) |
Destination airport: | Georgetown Municipal Airport, TX (KGTU) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The pilot was in cruise flight at 19,000 ft mean sea level when he became unresponsive to air traffic control. Military pilots dispatched to intercept the airplane reported that the pilot was seated upright with his head tilted back against his seat and was unresponsive. The airplane continued on its established course at 19,000 ft over the Gulf of Mexico, where radar contact was lost about 3.75 hours after the pilot's last communication with air traffic control.
The engine likely lost total power due to fuel exhaustion and the airplane descended into the water.
The airplane was equipped with a hypoxia recognition system which was designed to descend the airplane to a lower altitude in the event of pilot incapacitation. Given the altitude of the accident airplane, the system should have activated about 17 minutes after the pilot's last input or interaction with the system. Following the accident, the manufacturer identified a condition under which uncommanded inputs could be made to the airplane's avionics, which could interfere with the normal function of the hypoxia recognition and automated descent features; however, the reason for the accident airplane's continued flight at 19,000 ft could not be determined, as the airplane was not recovered.
The last few transmissions by the pilot to air traffic control illustrated a degradation in communication consistent with incapacitation. Given this interaction with the pilot and the lack of response from the pilot when the airplane was intercepted, it is likely that the pilot became incapacitated due to hypoxic hypoxia.
Probable Cause: The pilot's incapacitation resulted in impact with the Gulf of Mexico. The reason the hypoxia recognition system did not descend the airplane as designed could not be determined as the airplane was not located.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | CEN18FA400 |
Status: | Investigation completed |
Duration: | 3 years and 7 months |
Download report: | Final report |
|
Sources:
NTSB CEN18FA400
https://flightaware.com/live/flight/N325JK FAA register:
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=325JK Location
Images:
Revision history:
Date/time | Contributor | Updates |
04-Jan-2018 07:03 |
Copi |
Added |
04-Jan-2018 07:27 |
copi |
Updated [Cn, Source, Narrative] |
04-Jan-2018 09:33 |
Aerossurance |
Updated [Location, Narrative] |
04-Jan-2018 09:34 |
Aerossurance |
Updated [Aircraft type] |
04-Jan-2018 09:40 |
harro |
Updated [Source, Narrative] |
04-Jan-2018 18:07 |
Geno |
Updated [Time, Operator, Total occupants, Other fatalities, Source, Damage] |
05-Jan-2018 01:26 |
Geno |
Updated [Source] |
05-Jan-2018 09:48 |
copi |
Updated [Total fatalities, Source, Damage] |
07-Jan-2018 19:48 |
Anon. |
Updated [Source, Narrative] |
05-May-2018 12:28 |
rvargast17 |
Updated [Damage] |
09-Jul-2022 12:41 |
ASN Update Bot |
Updated [Time, Other fatalities, Country, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation