NYC95LA116 · Ryan NAVION A
Blue Hill Air Ryan NAVION A · Accident: total loss of engine power (non-mechanical) en route
From Norwood Memorial Airport (OWD) to Katama Airpark (1B2)
Event
- NTSB case
- NYC95LA116
- 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
Ryan NAVION A
- Aircraft type
- Ryan NAVION
- 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
- N4285K
- Operator
- Blue Hill Air
- Onboard fatalities
- Unknown
- Route
- From Norwood Memorial Airport (OWD), Norwood, MATo Katama Airpark (1B2), Edgartown, MA
- 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 supply, inattentive
Approximate · Estimated position: the centre of Taunton, MA, the place the record names. Not the accident site.
NTSB narrative
IN CRUISE FLIGHT, THE ENGINE SPUTTERED, THEN QUIT. THE PILOT MADE A FORCED LANDING IN A ROUGH FIELD. EXAMINATION OF THE FUEL SYSTEM (37 GALLONS USEABLE), REVEALED IT WAS INTACT, THE FUEL TANKS WERE EMPTY, AND THERE WAS NO EVIDENCE OF FUEL LEAKAGE OR SIPHONING. THE PILOT REPORTED HE HAD STARTED WITH FULL TANKS AND THEN ADDED 10 GALLONS OF FUEL AFTER THE 2ND FLIGHT. THE AIRPLANE HAD FLOWN 3.6 HOURS AND MADE 5 TAKEOFFS WHEN THE POWER LOSS OCCURRED. THE PILOT REPORTED HE COMPUTED THE FUEL BURN AT 12 GPH.
Probable cause
the failure of the pilot to monitor his fuel supply, which resulted in a power loss due to fuel exhaustion, and a forced landing in rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA116
- Event ID
- 20001207X03539
- Case number
- NYC95LA116
- 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: 911a513b3e63975cbc585ecce02e7af8fc21ed755eae71d15dd47e65600e594e; retrieved 2026-09-21T22:18:52.574Z.