ANC97LA090 · Beech D18S
Beech D18S · Accident: loss of engine power during initial climb
From UUO to Sleetmute Airport (SLQ)
Event
- NTSB case
- ANC97LA090
- 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
Beech D18S
- Aircraft type
- Beechcraft 18
- 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
- N765D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From UUOTo Sleetmute Airport (SLQ), SLEETMUTE, 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 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
- Initial climb
- 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot took off from a 4400-foot-long gravel airstrip with a near gross weight load of cargo. He said that shortly after lift-off the airplane felt 'sluggish', and he believes the left engine began to lose power. He said the airplane would not climb, and he elected to bring both engines to idle and land on the remaining runway. The airplane touched down a short distance from the end of the runway, and continued off the end and into the woods. A fire erupted, and the airplane was destroyed by fire. The pilot is unsure if the fire occurred in the air, or shortly after the airplane went off the end of the runway. The engines were extensively damaged by fire, and were not examined. FAA inspectors on scene said there was no obvious signs of catastrophic engine failure.
Probable cause
The loss of engine power for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC97LA090
- Event ID
- 20001208X08046
- Case number
- ANC97LA090
- 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: ea23bfd54fe2b726d1ada267c90f69d3db64e3cc781ce77002d5e87a3a25bcba; retrieved 2026-09-22T19:23:30.986Z.