NYC95LA002 · Cessna 185F
Cessna 185F · Accident: total loss of engine power (non-mechanical) on approach
From Nantucket, MA (no airport) to an unrecorded destination
Event
- NTSB case
- NYC95LA002
- 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
Cessna 185F
- Aircraft type
- Cessna 185
- 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
- N53074
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nantucket, MA (no airport)To 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
- Approach · VFR pattern final
- 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; Tree(s)
- 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
- Object › Tree(s)
- Pilot in command › Fuel consumption calculations, inaccurate
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Estimated position: the centre of Rochester, MA, the place the record names. Not the accident site.
NTSB narrative
THE PILOT WAS APPROACHING THE POND FOR A LANDING IN THE FLOAT-EQUIPPED AIRPLANE, WHEN THE ENGINE SUDDENLY QUIT. THE PILOT WAS UNABLE TO GLIDE TO THE POND, AND THE AIRPLANE IMPACTED TREES DURING THE FORCED LANDING. THE FAA INSPECTOR EXAMINED THE AIRPLANE AND FOUND 1 GALLON OF FUEL IN THE LEFT TANK AND NO FUEL IN THE RIGHT TANK. THE ENGINE WAS PLACED IN A TEST STAND AND STARTED. THE FAA INSPECTOR STATED IN HIS REPORT: 'THE ENGINE WAS STARTED AND RAN FOR APPROXIMATELY 15 MINUTES AT VARIOUS POWER SETTINGS...WITH NO APPARENT MALFUNCTIONS.'
Probable cause
The pilot's inadeqaute calculation of fuel and inadeqaute inflight decision which resulted in fuel exhaustion and the loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA002
- Event ID
- 20001206X02503
- Case number
- NYC95LA002
- 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: 024085f848828bc9414e0c6339489d3da29f1ff7cfc516aaafb3e48bc9a53f38; retrieved 2026-09-23T00:33:38.395Z.