ANC08LA089 · de Havilland DHC-3
Rainbow King Lodge de Havilland DHC-3 · Accident: powerplant system/component malfunction/failure en route
From Iliamna, AK to an unrecorded destination
Event
- NTSB case
- ANC08LA089
- 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
- Unknown
- 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
de Havilland DHC-3
- Aircraft type
- de Havilland DHC-3
- 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
- N61FE
- Operator
- Rainbow King Lodge
- Onboard fatalities
- Unknown
- Route
- From Iliamna, 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
- En route · cruise
- Defining eventThe 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
- Powerplant system/component malfunction/failure
- 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
- Tree(s)
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The solo airline transport pilot was making a local reconnaissance flight in a float-equipped airplane under 14 Code of Federal Regulations Part 91 in conjunction with a wilderness lodge business. The pilot said that he was scouting local lakes and rivers for fish and, while returning to a float pond near the lodge, the airplane's engine lost oil pressure and then lost power. The pilot said that he descended to a road, and that after he touched the floats on the road the left wing struck a tree, causing the airplane to depart the roadway. The airplane sustained damage to the left wing's leading edge and fuselage. A mechanic said that the number 8 cylinder separated from the engine, causing an oil line to separate.
Probable cause
A total loss of engine power due to the separation of the number 8 cylinder from the engine, which separated an oil line, resulting in a loss of oil and oil pressure. Contributing to the accident was the float-equipped airplane's forced landing on a road.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC08LA089
- Event ID
- 20080731X01137
- Case number
- ANC08LA089
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 05aaa52e223bef70cf3b52fedb1867cc8fce685932aac74adfb7ad2ba568a4e2; retrieved 2026-09-15T09:58:00.138Z.