FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA313 · Beech C35

16 Aug 2015 · Hicksville, NY, United States

Beech C35 · Accident: loss of engine power (total) en route

From Francis S Gabreski Airport (FOK) to Morristown Municipal Airport (MMU)

Report a problem

Event

NTSB case
ERA15FA313
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
Charter & commuter
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

Beech C35

Aircraft type
Beechcraft 35
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
N5946C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Francis S Gabreski Airport (FOK), Westhampton Bch, NYTo Morristown Municipal Airport (MMU), Morristown, NJ
Aircraft age
About 63 years (built 1952)
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 135: Air Taxi & Commuter
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
Loss of engine power (total)
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

  • Environmental issues › Task environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The commercial pilot was conducting an on-demand air taxi flight. The passenger reported that, while they were in cruise flight (about 6,500 ft mean sea level, according to radar data), he heard a loud "pop" sound and saw a flicker of light from the engine area, followed by an "oil smell." The engine then began to "sputter" and lost power. The pilot attempted to restart the engine without success. The pilot reported the problem to air traffic control (ATC); however, he did not declare an emergency.

The New York terminal radar approach control (N90) LaGuardia Airport (LGA) departure controller subsequently provided the pilot with the relative locations of several nearby airports, and the pilot determined that he was closest to Republic Airport (FRG), Farmingdale, New York, but that he did not have sufficient altitude to reach it. The LGA controller then provided vectors to Bethpage Airport, an alternate airport depicted on his radar video map (RVM), and noted that, although the airport was closed, there was a runway there. The controller provided vectors to Bethpage for a forced landing, but the pilot reported that he did not see the runway. The next several transmissions between the controller and the pilot revealed that the pilot was unable to acquire the Bethpage runway (because it no longer existed) while the controller continued to provide heading and distance to it. The controller subsequently lost radar contact with the pilot, and the airplane eventually crashed into a railroad grade crossing cantilever arm before coming to rest on railroad tracks.

The investigation revealed that the runway the controller was directing the pilot to no longer existed; industrial buildings occupied the location of the former airport and had been there for several years. However, the runway was depicted on the controller's RVM because it had not been removed following the closure of the airport. If the RVM had not shown Bethpage as an airport, the controller might have provided alternative diversion options, including nearby parkways, to the pilot, which would have prevented him from focusing on a runway that did not exist. Further investigation revealed that the Federal Aviation Administration (FAA) did not require periodic review and validation of RVMs and had no procedures to ensure that nonoperational airports were removed from RVMs systemwide. Since this accident, the FAA has revised and corrected its internal procedures to ensure all nonoperational airports are removed from RVMs in the United States.

An examination of the engine revealed that the crankshaft failed at the No. 2 main journal. The No. 2 main bearings were heat damaged and extruded into the crank cheek. The No. 2 main bearing supports had bearing shift and fretting signatures. The No. 2 main bearing had rotated in the bearing support. Contact with the crankshaft by the main bearing initiated the fracture of the crankshaft. The engine maintenance records did not reveal evidence of a recent engine repair in this area. Torque values obtained during the engine disassembly did not reveal evidence of an undertorqued condition. The engine had operated about 1,427 hours since its last major overhaul.

Toxicological testing detected amphetamine, oxycodone, oxymorphone, losartan, 7-amino-clonazepam, and acetaminophen in the pilot's blood and/or urine. It is unlikely that the losartan and acetaminophen impaired the pilot's judgment. The direct effects of clonazepam, which is used to treat panic disorder or seizures, did not contribute to the accident; however, it could not be determined whether the pilot's underlying medical conditions contributed to the accident. The exact effects of oxycodone on the pilot at or around the time of the accident could not be determined. The level of amphetamine was significantly higher than the therapeutic range, indicating that the pilot was likely abusing the drug and that he was impaired by it at the time of the accident. The combination of the pilot's use of drugs and his medical conditions likely significantly impaired his psychomotor functioning and decision-making and led to his delay in responding appropriately to the in-flight loss of engine power and, therefore, contributed to the accident. Review of radar data revealed that 2 minutes 18 seconds had elapsed and that the airplane had lost about 2,000 ft of altitude while continuing on a westerly heading before the pilot turned the airplane toward FRG. If the pilot had turned immediately after he realized the engine had lost power, he would have had adequate altitude to glide to a suitable runway.

Probable cause

The pilot's improper decision to delay turning toward a suitable runway once he realized that an engine failure had occurred, which resulted in his having inadequate altitude to glide to a suitable runway, and the New York terminal radar approach control LaGuardia Airport area controller's provision of erroneous emergency divert airport information to the pilot.

Contributing to the accident were (1) the Federal Aviation Administration's lack of a requirement to periodically review and validate radar video maps, (2) the failure of the engine crankshaft due to a bearing shift, and (3) the pilot's impairment due to his abuse of amphetamine and underlying medical condition(s).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA313
Event ID
20150816X95657
Case number
ERA15FA313
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. 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: 3117bcdec8d4a8c7efcb100b6ae86158591d3fb8d1eb762ae668da9fa248b838; retrieved 2026-09-14T19:49:50.958Z.