FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA232 · Morrisey 2150A

6 Jul 2017 · Honesdale, PA, United States

Morrisey 2150A · Accident: fuel exhaustion during initial climb

From Cherry Ridge Airport (N30) to Cherry Ridge Airport (N30)

Report a problem

Event

NTSB case
ERA17FA232
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
General aviation
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

Morrisey 2150A

Aircraft type
Morrisey 2150
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
N917JL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cherry Ridge Airport (N30), Honesdale, PATo Cherry Ridge Airport (N30), Honesdale, PA
Aircraft age
About 56 years (built 1961)
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
Initial climb
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
Fuel exhaustion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot was taking off in day, visual meteorological conditions. According to a witness who was both a pilot and a mechanic, the airplane took off and sounded "normal" and returned for landing. After touchdown, the airplane continued for a touch-and-go landing but the engine, "fumbled… faltered drastically for 3 or 4 seconds" before the pilot aborted the takeoff, taxied back to the beginning of the runway, and took off again. During that takeoff, the witness heard the engine "miss" and heard further power interruptions before his attention was diverted from the airplane. The witness did not see the accident. Airport surveillance video depicted the airplane on its takeoff roll, followed by an initial climb and a left turn in the vicinity of the crosswind leg of the airport traffic pattern. The airplane then entered a shallow descent and a shallow bank angle as it descended from view behind trees.

Examination of the airplane at the accident site revealed no fuel odor and no evidence of fuel spillage at the scene. Three ounces of fuel were recovered from the airplane. Detailed examination of the airframe and engine revealed no preimpact mechanical anomalies that would have precluded normal operation; however, locking pliers were substituted for the trim actuator handle, and a bird's nest was found in the engine. In addition, the lap belt and shoulder harnesses were not buckled, and the shoulder harnesses were stowed behind the seat, the lap belts were stowed to either side of the seat pan, and the mold growth, dirt, and corrosion visible on the belts, buckle, and male tabs suggested they had not been used for an extended period of time. Examination of airplane records revealed that the airplane's most recent annual inspection was 5 years before the accident.

Whether the pilot confirmed the amount of fuel onboard before departure could not be determined, but his failure to appropriately address the "faltering" engine before attempting another takeoff reflects poor hazard recognition and impaired decision making. Given the lack of fuel found onboard after the accident, the loss of engine power was likely the result of fuel exhaustion.

Additionally, toxicology testing of the pilot identified the use of butalbital (a barbiturate) and marijuana, both of which can affect decision-making. Thus, it is likely that the effects from the pilot's use of two psychoactive substances contributed to his decision to conduct the takeoff after observing an engine anomaly. Because the pilot was over 40 years old, his medical certificate expired 2 years after issuance; thus it was not valid at the time of the accident.

Probable cause

A total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot's use of two psychoactive substances, which led to his impaired decision to attempt to takeoff after engine issues became evident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA232
Event ID
20170706X74454
Case number
ERA17FA232
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: 29b92da74830c9556318646815f78ec6bd6383988147e9a15626ff799d1088a5; retrieved 2026-09-15T06:05:52.083Z.