ASN Wikibase Occurrence # 217507
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 9 November 2018 |
Time: | 15:00 |
Type: | Cessna 310R |
Owner/operator: | Kbuf Air Llc. |
Registration: | N5044J |
MSN: | 310R0164 |
Year of manufacture: | 1975 |
Total airframe hrs: | 5416 hours |
Engine model: | Continental IO-550-A3B |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Delaware County, Tompkins, NY -
United States of America
|
Phase: | En route |
Nature: | Private |
Departure airport: | Niagara Falls International Airport, NY (IAG/KIAG) |
Destination airport: | Teterboro Airport, NJ (TEB/KTEB) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The pilot was conducting an instrument flight rules flight along a route that he had flown frequently in the months before the accident. About 55 minutes into the flight, while at cruise altitude, the pilot stated to air traffic control, "I need to get on the ground immediately." The controller provided the pilot with the nearest airport information; however, no further intelligible radio transmissions were received from the pilot. Radar data showed the airplane enter a turning descent before radar contact was lost about 1.8 nautical miles from the accident site.
A witness near the accident site heard engines revving up and down for about 1 minute and subsequently saw an airplane overhead. She reported that the engines were loud, and as the airplane flew by, she saw gray smoke trailing the airplane and a red/orange glow originating from under the right wing area. The airplane then flew out of view, and she subsequently heard a loud explosion and saw a plume of smoke.
The distribution of the wreckage was consistent with a high-speed impact. Flight control continuity could not be established due to the heavy fragmentation of the wreckage; however, all major flight control components were located in the debris field. Examination of the engines revealed no anomalies or thermal damage that would have precluded normal operation. Both damage signatures and witness accounts indicated that the engines were producing power at the time of the accident.
Autopsy findings were consistent with the pilot's inhalation of smoke/soot before the impact occurred. The wreckage also exhibited evidence of an in-flight fire. Small areas of broomstrawing and localized thermal damage were found on structures located in the left side of the cockpit area, where the pilot was likely seated. In addition, there was evidence of airflow-driven soot tailing on rivets in a few areas of the fuselage. The recovered instrument panel, wiring, and avionics showed no signs of electrical arcing or fire. Although the airplane's combustion cabin heater was not inspected in accordance with the latest airworthiness directive, the interior components of the heater showed no signs of fire. Based on this information, the heavy fragmentation of the wreckage, and the postcrash fire to which it was also exposed, the origin of the in-flight fire could not be determined.
There was no record that the pilot accessed any weather products before or during the accident flight. The pilot likely encountered light to moderate icing conditions about 3 minutes after takeoff, which had been forecast by several products issued before the pilot's departure; however, these conditions deteriorated to moderate or greater turbulence and moderate or greater icing conditions, including supercooled large droplet (SLD) icing, during the final 10 minutes of the flight. These conditions were not forecast or reflected in pilot reports. The pilot did not state that he was accumulating airframe icing at any time during the flight, but it is likely that the SLD icing rapidly accumulated on the airframe to the extent that the airplane could no longer sustain flight.
Although it could not be determined when the in-flight fire occurred it was likely the reason for the pilot stating he had to get on the ground immediately. Further, it is also likely that the SLD and the prevailing instrument meteorological conditions in the area reduced the likelihood that the pilot could have expediently performed an emergency descent and landing.
Probable Cause: An in-flight fire of undetermined origin. Contributing to the accident were the severe icing conditions encountered during the final minutes of the flight, which led to a loss of airplane control.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | ERA19FA039 |
Status: | Investigation completed |
Duration: | 1 year and 8 months |
Download report: | Final report |
|
Sources:
NTSB
https://flightaware.com/live/flight/N5044J FAA register:
https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=5044J Location
Images:
Photo: NTSB
Revision history:
Date/time | Contributor | Updates |
09-Nov-2018 23:28 |
Geno |
Added |
09-Nov-2018 23:58 |
Iceman 29 |
Updated [Time, Embed code] |
10-Nov-2018 00:00 |
Iceman 29 |
Updated [Source, Embed code] |
10-Nov-2018 02:01 |
Geno |
Updated [Aircraft type, Total fatalities, Total occupants, Other fatalities, Location, Source, Damage, Narrative] |
11-Nov-2018 01:29 |
Geno |
Updated [Aircraft type, Registration, Cn, Operator, Phase, Departure airport, Destination airport, Source, Damage, Narrative] |
19-Jul-2020 06:27 |
ASN Update Bot |
Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ] |
19-Jul-2020 06:42 |
harro |
Updated [Departure airport, Destination airport, Source, Narrative, Photo, Accident report, ] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation