FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC85FNE01 · Marr/Eckburg LONG EZE

19 Mar 1985 · Waterbury, CT, United States

Marr/Eckburg LONG EZE · Accident: total loss of engine power (non-mechanical) on approach

From Robertson Field (4B8) to Waterbury Oxford Airport (OXC)

Report a problem

Event

NTSB case
NYC85FNE01
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

Marr/Eckburg LONG EZE

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
N49EZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Robertson Field (4B8), Plainville, CTTo Waterbury Oxford Airport (OXC), Waterbury, CT
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)
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 › Checklist, not followed
  • Pilot in command › Fuel tank selector position, improper use of
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Lack of recent experience in kind of aircraft
  • Pilot in command › Lack of total experience in kind of aircraft

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

NTSB narrative

THE ACFT CRASHED INTO AN EMBANKMENT SHORT OF RWY 36 AFTER A LOSS OF PWR ON FINAL APPROACH. THE PLT SAID HE WAS OPERATING ON THE RT TANK WHEN THE ENG QUIT. HE IMMEDIATELY AWITCHED TO THE LEFT TANK AND ACTIVATED THE BOOST PUMP. THE PROP HAD STOPPED AND THE ACFT WAS NOT EQUIPPED WITH A STARTER. THE PLT LATER SAID HE NOTICED A RISE IN FUEL PRESSURE BUT DUE TO LACK OF ROTATION THE ENG DID NOT START. THE POST ACC EXAM REVEALED 8 GALS OF FUEL IN THE LEFT ENG AND NONE IN THE RIGHT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC85FNE01
Event ID
20001214X36025
Case number
NYC85FNE01
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: df8ba4a2f6786e0f711e92a646fbec6b0cdc33078be2b8ba8dc51d8f58dcec70; retrieved 2026-09-21T17:20:18.440Z.