Loss of pressurization Accident Socata TBM700N (TBM900) N900KN,
ASN logo
ASN Wikibase Occurrence # 169555
 
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:Friday 5 September 2014
Time:14:10
Type:Silhouette image of generic TBM9 model; specific model in this crash may look slightly different    
Socata TBM700N (TBM900)
Owner/operator:New 51LG
Registration: N900KN
MSN: 1003
Year of manufacture:2014
Total airframe hrs:97 hours
Engine model:P&W Canada PT6A-66D
Fatalities:Fatalities: 2 / Occupants: 2
Aircraft damage: Destroyed
Category:Accident
Location:Caribbean Sea, near the NE coast of Jamaica -   Jamaica
Phase: En route
Nature:Private
Departure airport:Rochester-Monroe County Airport, NY (ROC/KROC)
Destination airport:Naples Airport, FL (APF/KAPF)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
On September 5, 2014, about 1410 eastern daylight time (EDT), a Daher-Socata TBM700 (marketed as a TBM900 model), N900KN, was destroyed when it impacted open water in the Caribbean Sea near the northeast coast of Jamaica. The commercial pilot and the passenger were fatally injured. An instrument flight rules flight plan was filed for the cross-county flight that originated from Greater Rochester International Airport (ROC), Rochester, New York, at 0826 and was destined for Naples Municipal Airport (APF), Naples, Florida. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91.

The commercial pilot and his wife departed New York in their turboprop airplane on a cross-country flight to Florida. About 1 hour 40 minutes into the flight and while cruising at flight level (FL) 280, the pilot notified air traffic control (ATC) of an abnormal indication in the airplane and requested a descent to FL180. The responding controller instructed the pilot to descend to FL250 and turn left 30°, and the pilot acknowledged and complied with the instruction; he then again requested a lower altitude. Although the pilot declined emergency handling and did not specify the nature of the problem, the controller independently determined that the flight had encountered a pressurization issue and immediately coordinated with another ATC facility to clear nearby traffic. The controller then issued instructions to the pilot to descend to FL200 and change course; however, the pilot did not comply with the assignments despite acknowledging the instructions multiple times. The pilot’s failure to comply with the controller’s instructions, his long microphone pauses after concluding a statement over the radio, and his confusion were consistent with cognitive impairment due to hypoxia. Further, the pilot’s transmissions to ATC indicated impairment within 2 minutes 30 seconds of reporting the abnormal indication, which is consistent with the Federal Aviation Administration’s published time of useful consciousness/effective performance time ranges for the onset of hypoxia.

Military airplanes were dispatched about 30 minutes after the pilot’s final transmission to ATC to intercept and examine the airplane. The pilots of the military airplanes reported that the airplane appeared to be flying normally at FL250, that both occupants appeared to be asleep or unconscious, and that neither occupant was wearing an oxygen mask. Photographs taken from one of the military airplanes revealed that the airplane’s emergency exit door was recessed into the fuselage frame, consistent with a depressurized cabin. The military airplanes escorted the airplane as it continued on a constant course and altitude until it approached Cuban airspace, at which point they discontinued their escort. Radar data indicated that the airplane continued on the same flight track until about 5 hours 48 minutes after takeoff, when it descended to impact in the Caribbean Sea north of Jamaica. The flight’s duration was consistent with a departure with full fuel and normal cruise endurance.

Some of the wreckage, including fuselage and engine components, was recovered from the ocean floor about 4 months after the accident. Data recovered from nonvolatile memory in the airplane’s global air system controller (GASC) indicated that several fault codes associated with the cabin pressurization system were registered during the flight. These faults indicated that the overheat thermal switch (OTSW), which was associated with overheat protection, had activated, which resulted in a shutdown of the engine bleed air supply to the cabin pressurization system. Without a bleed air supply to maintain selected cabin pressure, the cabin altitude would have increased to the altitude of the outside environment over a period of about 4 minutes.

The faults recorded by the GASC’s nonvolatile memory and associated system alerts/warnings would have been displayed to the pilot, both as discrete system anomaly messages on the crew alerting system (CAS) and as master warning and/or master caution annunciations. A witness report indicated that the pilot was known to routinely monitor cabin altitude while flying in the airplane and in his previous pressurized airplanes. Based on his instrument scanning practices and the airplane’s aural warning system, he likely would have observed any CAS message at or near its onset. Thus, the CAS messages and the associated alerts were likely the precipitating event for the pilot’s call to ATC requesting a lower altitude.

The pilot was likely not familiar with the physiological effects of hypoxia because he had not recently been in an altitude chamber for training, but he should have been familiar with the airplane’s pressurization system emergency and oxygen mask donning procedures because he had recently attended a transition course for the accident airplane make and model that covered these procedures. However, the pressurization system training segment of the 5-day transition course comprised only about 90 minutes of about 36 total hours of training, and it is unknown if the pilot would have retained enough information to recognize the significance of the CAS messages as they appeared during the accident flight, much less recall the corresponding emergency procedures from memory. Coupled with the pilot’s reported diligence in using checklists, this suggests that he would have attempted a physical review of the emergency procedures outlined in the Pilot’s Operating Handbook (POH). A review of the 656-page POH for the airplane found that only one of the four emergency checklist procedures that corresponded to pressurization system-related CAS messages included a step to don an oxygen mask, and it was only a suggestion, not a mandatory step. The combined lack of emergency guidance to immediately don an oxygen mask and the rapid increase in the cabin altitude significantly increased the risk of hypoxia, a condition resistant to self-diagnosis, especially for a person who has not recently experienced its effects in a controlled environment such as an altitude chamber.

Additionally, once the pilot reported the problem indication to ATC, he requested a descent to FL180 instead of 10,000 ft as prescribed by the POH. In a second transmission, he accepted FL250 and declined priority handling. These two separate errors were either early signs of cognitive dysfunction due to hypoxia or indications that the pilot did not interpret the CAS messages as a matter related to the pressurization system.

Although the cabin bleed-down rate was 4 minutes, the pilot showed evidence of deteriorating cognitive abilities about 2 minutes 30 seconds after he initially reported the problem to ATC. Ultimately, the pilot had less than 4 minutes to detect the pressurization system failure CAS messages, report the problem to ATC, locate the proper procedures in a voluminous POH, and complete each procedure, all while suffering from an insidious and mentally impairing condition that decreased his cognitive performance over time.

Following the accident, the airplane manufacturer revised the emergency procedures for newly manufactured airplanes to require flight crews to don their oxygen masks as the first checklist item in each of the relevant emergency checklists. Further, the manufacturer has stated that it plans to issue the same revisions for previous models in 2017.

The airplane manufacturer previously documented numerous OTSW replacements that occurred between 2008 and after the date of the accident. Many of these units were removed after the GASC systems in their respective airplanes generated fault codes that showed an overheat of the bleed air system. Each of the OTSWs that were tested at the manufacturer’s facility showed results that were consistent with normal operating units. Additionally, the OTSW from the accident airplane passed several of the manufacturer’s functional tests despite the presence of internal corrosion from sea water.

Further investigation determined that the pressurization system design forced the GASC to unnecessarily discontinue the flow of bleed air into the cabin if the bleed air temperature exceeded an initial threshold and did not subsequently fall below a secondary threshold within 30 seconds. According to the airplane manufacturer, the purpose of this design was to protect the structural integrity of the airplane, the system, and the passengers in case of overheat detection. As a result of this accident and the ensuing investigation, the manufacturer made changes to the programming of the GASC and to the airplane’s wiring that are designed to reduce the potential for the GASC to shut off the flow of bleed air into the cabin and to maximize the bleed availability.

Contrary to its normal position for flight, the cockpit oxygen switch was found in the “off” position, which prevents oxygen from flowing to the oxygen masks. A witness’s description of the pilot’s before starting engine procedure during a previous flight showed that he may not have precisely complied with the published procedure for turning on the oxygen switch and testing the oxygen masks. However, as the pilot reportedly was diligent in completing preflight inspections and checklists, the investigation could not determine why the cockpit oxygen switch was turned off. Further, because the oxygen masks were not observed on either occupant, the position of the oxygen switch would not have made a difference in this accident.

See the public docket for this accident for comments from the Bureau d’Enquêtes et d’Analyses.

Probable Cause: The design of the cabin pressurization system, which made it prone to unnecessary shutdown, combined with a checklist design that prioritized troubleshooting over ensuring that the pilot was sufficiently protected from hypoxia. This resulted in a loss of cabin pressure that rendered the pilot and passenger unconscious during cruise flight and eventually led to an in-flight loss of power due to fuel exhaustion over the open ocean.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA14LA424
Status: Investigation completed
Duration: 3 years and 2 months
Download report: Final report

Sources:

NTSB

Location

Images:




Photos: NTSB

Media:

Revision history:

Date/timeContributorUpdates
05-Sep-2014 18:35 harro Added
05-Sep-2014 18:37 harro Updated [Aircraft type, Source, Embed code]
05-Sep-2014 18:49 harro Updated [Location, Country, Embed code, Narrative]
05-Sep-2014 19:14 harro Updated [Total fatalities, Location, Source, Narrative]
05-Sep-2014 19:15 harro Updated [Cn, Other fatalities, Damage, Narrative]
05-Sep-2014 19:55 gerard57 Updated [Total fatalities, Total occupants, Source, Narrative]
05-Sep-2014 19:56 harro Updated [Time, Source]
06-Sep-2014 04:33 Geno Updated [Source]
06-Sep-2014 07:15 Aerossurance Updated [Narrative]
06-Sep-2014 07:18 Aerossurance Updated [Source]
06-Sep-2014 07:18 Aerossurance Updated [Source]
06-Sep-2014 16:13 BLT Updated [Total fatalities, Total occupants]
06-Sep-2014 17:50 Aerossurance Updated [Source]
07-Sep-2014 06:21 Chieftain Updated [Total fatalities, Total occupants, Source]
07-Sep-2014 18:11 Aerossurance Updated [Source, Damage, Narrative]
11-Sep-2014 15:33 Aerossurance Updated [Source, Narrative]
14-Sep-2014 08:54 Aerossurance Updated [Time, Source, Narrative]
07-Oct-2014 20:20 Aerossurance Updated [Source, Narrative]
21-Jan-2015 18:47 gerard57 Updated [Source, Damage, Narrative]
31-Jul-2016 20:56 Dr.John Smith Updated [Time, Operator, Location, Source, Narrative]
31-Jul-2016 20:59 Dr.John Smith Updated [Source, Embed code]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Aug-2018 15:27 wf Updated [Embed code, Damage]
30-Mar-2019 15:26 Aerossurance Updated [Operator, Location, Source, Narrative]
07-May-2022 10:27 Ron Averes Updated [Location, Source]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org