FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC90LA222 · Piper PA-31-350

24 Aug 1990 · Norridgewock, ME, United States

Telford Aviation Piper PA-31-350 · Accident: total loss of engine power (non-mechanical) en route

From Bangor International Airport (BGR) to WVY · Waterville, ME

Report a problem

Event

NTSB case
NYC90LA222
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
Instrument Meteorological Cond

Piper PA-31-350

Aircraft type
Piper PA-31
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
N250SC
Onboard fatalities
Unknown
Route
From Bangor International Airport (BGR), Bangor, METo WVY · Waterville, ME
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)
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

  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › In-flight planning/decision, inattentive

Approximate · Estimated position: the centre of Norridgewock, ME, the place the record names. Not the accident site.

NTSB narrative

THE PILOT WAS UNABLE TO LAND BECAUSE OF FOG. HE DIVERTED TO TWO OTHER AIRPORTS, BUT THESE WERE ALSO FOGGED IN. WHILE FLYING TO A THIRD AIRPORT, BOTH ENGINES QUIT AND THE PILOT LANDED THE AIRPLANE IN A FIELD. AN ON SITE INVESTIGATION REVEALED THE AIRPLANE HAD NO FUEL IN THE TANKS. THE PILOT ACKNOWLEDGED HE HAD NOT CHECKED THE FUEL QUANTITY BEFORE THE FLIGHT. THE PILOT STATED THE FIRST TIME HE REALIZED HE DIDN'T HAVE FUEL IN THE AUXILIARY TANKS WAS WHEN HE SELECTED THEM WHILE DIVERTING TO THE THIRD AIRPORT.

Probable cause

THE PILOT'S IMPROPER PREFLIGHT AND INFLIGHT PLANNING OF THE FUEL, WHICH RESULTED IN FUEL EXHAUSTION AND FORCED LANDING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC90LA222
Event ID
20001212X24125
Case number
NYC90LA222
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: e69e7f9126f1e575e342d6edf4fbc90b88d45e79f80ae8ac46bf03e15347cf4b; retrieved 2026-09-23T05:24:02.542Z.