FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC82FNC09 · Cessna U206

6 May 1982 · Millinocket, ME, United States

Millinocket Lake Flying Servic Cessna U206 · Accident: total loss of engine power (non-mechanical) en route

From SMITH POND, ME to New Egypt, NJ

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
NYC82FNC09
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 U206

Aircraft type
Cessna 206
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
N60166
Onboard fatalities
Unknown
Route
From SMITH POND, METo New Egypt, NJ
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, misjudged
  • Pilot in command › Preflight planning/preparation, inadequate

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

NTSB narrative

BEFORE DEPARTING SMITH POND, MAINE, THE PILOT CHECKED THE FUEL AND ESTIMATED HE HAD BETWEEN 30 AND 40 GALLONS ON BOARD. HE FLEW TO WATERVILLE, THEN TO KATACHDINE LAKE, AND WAS ON THE NEXT LEG OF THE FLIGHT WHEN THE ENGINE LOST POWER. HE SWITCHED TANKS AND THE ENGINE STARTED FOR A FEW SECONDS, THEN LOST POWER AGAIN. THIS OCCURRED OVER LEVEL TERRAIN COVERED WITH TREES, BUT WITH NO CLEARING. THE FLOAT PLANE WAS BADLY DAMAGED DURING A FORCED LANDING IN THE WOODED AREA. THE PILOT STATED THAT THIS WAS A NEWLY PURCHASED AIRCRAFT AND THE FUEL GAUGES READ FULL AT THE TIME OF THE ACCIDENT. THE PILOT SUSPECTED A PROBLEM WITH THE FUEL TANK VENTS. HOWEVER, AN INSPECTION REVEALED THEY WERE CLEAN AND HAD NO SIGNS OF BLOCKAGE. THE AIRCRAFT HAD TRAVELED ABOUT 216 MILES AFTER DEPARTING SMITH POND. THE ESTIMATED CRUISE SPEED WITH FLOATS WAS ABOUT 110 MPH. THE PILOT REPORTED THAT THE FUEL FLOW METER WAS INDICATING ABOUT 15 GAL/HR IN FLIGHT. THE ENGINE RAN SATISFACTORILY DURING AN OPERATIONAL CHECK ON 5/27/82.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC82FNC09
Event ID
20020917X04060
Case number
NYC82FNC09
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: 0f07ddb32605394b59a7a1e13996f2c4dfc8827abe6b7cfbc02ca350fedb476a; retrieved 2026-09-24T03:17:51.266Z.