ANC82IA076 · Cessna 206B
Cessna 206B · Incident: total loss of engine power (non-mechanical) on approach
From SZ0 · Emmonak, AK to an unrecorded destination
Event
- NTSB case
- ANC82IA076
- 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
- Incident
- 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 206B
- 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
- N3870G
- Operator
- Frank Allen Borman
- Onboard fatalities
- Unknown
- Route
- From SZ0 · Emmonak, AKTo 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 contamination
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Fluid, fuel › Water
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHEN ON SHORT FINAL THE PILOT ATTEMPTED TO ADD POWER FOR GLIDE PATH CORRECTION BUT RECEIVED NO ENGINE RESPONSE. HE SWITCHED TANKS AND OPENED THE STRAINER DRAIN VALVE BECAUSE OF PREVIOUS WATER CONTAMINATION PROBLEMS. HE MADE A LEFT TURN TO MAKE AN EMERGENCY LANDING ON A RIVER BANK, AND ABOUT FIVE SECONDS BEFORE TOUCH DOWN, SWITCHED ON THE FUEL BOOST PUMP. STILL NO RESPONSE FROM THE ENGINE OCCURRED. THE AIRCRAFT LANDED ON THE RIVER BANK, COLLAPSING THE NOSE GEAR AND RECEIVING OTHER AIRFRAME DAMAGE. SUBSEQUENT INVESTIGATION REVEALED THE PRESENCE OF WATER IN THE FUEL SUMP. THE PILOT STATED THAT HE HAD BEEN EXPERIENCING FUEL CONTAMINATION FROM A VARIETY OF SOURCES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ANC82IA076
- Event ID
- 20020917X02716
- Case number
- ANC82IA076
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 87d42396ccef15d298ff8156d12dfff9a61160177c775aead0dbe7ac84df91d7; retrieved 2026-09-24T01:20:24.811Z.