ANC97FA099 · de Havilland DHC-2
de Havilland DHC-2 · Accident: partial loss of engine power (mechanical failure) en route
From LAKE HOOD, AK to CHELATNA LAKE, AK
Event
- NTSB case
- ANC97FA099
- 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
- 4 · 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
- Charter & commuter
- 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-2
- Aircraft type
- de Havilland DHC-2
- 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
- N5164G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LAKE HOOD, AKTo CHELATNA LAKE, AK
- 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 135: Air Taxi & Commuter
- 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
- Partial loss of engine power (mechanical 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
- Stall
- 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
- Engine assembly, push rod › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot boarded the 4 passengers and cargo (unsecured) for a chartered flight to a fishing lodge. The floatplane departed uneventfully. About 45 min. later, while cruising about 1,700 ft. above rugged terrain and a river, the engine began to lose power and the floatplane descended. The pilot attempted a forced landing in a small lake that was 1,200 ft. in length and located about 1 mile west of the river. During the approach to landing, the airplane stalled and impacted swampy terrain at the lake's edge in a steep nose down attitude. An examination of the wreckage revealed that the no.1 engine exhaust pushrod had failed in fatigue just below the top (valve) ball end. Examination of the pushrod revealed that material had been pushed away from the rod during installation of the ball end. The fatigue crack may have initiated from a score mark produced by the installation. Pushrod life is reduced due to surface scratches. The life of the failed pushrod could not be determined. Insufficient information exists in the overhaul manual regarding pushrod life/inspection.
Probable cause
a loss of engine power due to the fatigue failure of the no.1 exhaust push rod. Factors contributing to the accident were: insufficient information on pushrod inspection and overhaul from the manufacturer, unsuitable terrain available for landing, and the pilot's failure to maintain airspeed during the approach which led to an inadvertent stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC97FA099
- Event ID
- 20001208X08273
- Case number
- ANC97FA099
- 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: 8238235caff40ab2b7419e446f8bff9e0fadeb115a59529b74369f65d7955d36; retrieved 2026-09-18T13:29:03.894Z.