ERA14LA085 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of engine power (total) en route
From Danbury Municipal Airport (DXR) to Danbury Municipal Airport (DXR)
Event
- NTSB case
- ERA14LA085
- 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
- 0 · 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
Piper PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N9409J
- Operator
- Schwartz Michael
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo Danbury Municipal Airport (DXR), Danbury, CT
- Aircraft age
- About 48 years (built 1966)
- 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
- 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
- Substantial
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that both fuel tanks were full when the flight departed. About 30 minutes into the flight, a GPS alarm alerted the pilot to switch fuel tanks, so he switched the fuel tank selector. He then proceeded north to return to the departure airport. About 51 minutes into the flight, while about 2,200 ft above the ground, the engine rpm began to decrease. The pilot attempted to restore power by repositioning the fuel selector, turning on the auxiliary fuel pump, pushing the throttle, and verifying that the mixture control was full rich; however, none of these actions restored engine power. The pilot declared an emergency to the tower air traffic controller, who then provided a vector to a nearby airport. The pilot was unable to visually locate the airport and recognized that he would be unable to land there, so he maneuvered for a forced landing on an expressway. The onboard camera showed the propeller stop while the airplane was on approach and the pilot turn off the fuel selector. The pilot subsequently landed the airplane hard on the expressway, which caused substantial damage to the airplane.
Following recovery of the airplane, 45 gallons of uncontaminated fuel was drained from both fuel tanks; however, fuel system components in the engine compartment contained minimal fuel, consistent with fuel starvation. Although the airplane was equipped with an engine monitor that records and retains engine parameters, it did not record fuel flow. However, the engine monitor did record a sudden and equal decrease in the exhaust gas temperature and cylinder head temperature for all of the cylinders, consistent with the loss of engine power described by the pilot. Although the reason for the loss of engine power was likely due to fuel starvation, the reason for the fuel starvation could not be determined by either an examination of the fuel supply system or a postaccident test run of the engine.
Probable cause
The total loss of engine power due to fuel starvation for reasons that could not be determined during postaccident engine examination or testing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA085
- Event ID
- 20140105X41404
- Case number
- ERA14LA085
- 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: e783cba81735534ef44d0564a2061a9dfa12a875960d370fdfae79f726317841; retrieved 2026-09-15T23:13:50.948Z.