NYC96LA183 · Piper PA-28-140
Piper PA-28-140 · Accident: total loss of engine power (non-mechanical) en route
From Essex County Airport (CDW) to an unrecorded destination
Event
- NTSB case
- NYC96LA183
- 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
- 0
- 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-140
- 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
- N1792T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Essex County Airport (CDW), Caldwell, NJTo not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel management, improper
Approximate · Estimated position: the centre of Closter, NJ, the place the record names. Not the accident site.
NTSB narrative
The pilot had been airborne for 4 hours, 20 minutes, on an aerial observation flight, in a Piper PA-28-140, and was returning to his departure airport, when the engine lost power. He switched fuel tanks, but was unable to get the engine running again. He made a forced landing on a golf course. During the ground roll, the left wing struck a tree, which ruptured the fuel tank and bent the wing backwards. Examination of the airplane revealed that the right wing fuel tank was empty, and there was no evidence of a fuel spill from the ruptured left wing fuel tank. The pilot reported that he had departed with 36 gallons onboard and planned on a fuel burn of 7 gallons per hour.
Probable cause
The pilot's improper fuel management, which resulted in a power loss due to fuel exhaustion, followed by the airplane striking a tree during a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA183
- Event ID
- 20001208X06799
- Case number
- NYC96LA183
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 769a5e5494f58c0cac634ae6566c21ba1b39b295f6edea5cdf05ff09f91fd757; retrieved 2026-09-22T21:12:50.328Z.