FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

40 Mile Air de Havilland DHC-3 accident

10 Feb 1989 · Fairbanks, AK, United States

de Havilland DHC-3 · Accident: in flight collision with terrain/water during takeoff

From Fairbanks International Airport (FAI) to Eagle Airport (EAA)

Report a problem

Event

NTSB case
ANC89FA043
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
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-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
N5056Q
Operator
40 Mile Air
Onboard fatalities
Unknown
Route
From Fairbanks International Airport (FAI), Fairbanks, AKTo Eagle Airport (EAA), EAGLE, 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
Takeoff · rejected takeoff
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
In flight collision with terrain/water
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

  • Pilot in command › Ice/frost removal from aircraft, not performed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PLT RPRTD THAT BEFORE THE FLT, THE WINGS & STABILIZER WERE SWEPT, LEAVING A LAYER OF 'POLISHED' FROST. FREIGHT WAS LOADED & THE ACFT WAS SERVICED TO BRING THE FUEL LEVEL UP TO 120 GAL. AFTER START, TAXI & RUN-UP, THE PLT BEGAN HIS TAKEOFF FROM THE APPROACH END OF THE 10,300 FT RWY (WITH 35' MP & 2250 RPM). AT ABOUT 100 FT AGL, HE ADJUSTED THE POWER (TO 30' MP & 2000 RPM) & RAISED THE FLAPS TO CLIMB AT 82 KTS. HOWEVER, THE ACFT DID NOT CLIMB & WOULD NOT ACCELERATE IN LEVEL FLT. THE PLT INCREASED THE POWER (TO 31' MP & 2100 RPM), BUT HE BELIEVED THERE WAS A DEFINITE LOSS OF POWER. SUBSEQUENTLY, THE ACFT WAS DAMAGED WHEN THE PLT ABORTED THE TAKEOFF ON SNOW COVERED TERRAIN BEYOND THE END OF THE RWY. NO PRE-ACDNT PART FAILURE OR MALFUNCTION OF THE ACFT OR ENG WAS FOUND. AN INV REVEALED THE ENTIRE ACFT WAS COVERED WITH A COATING OF FROST. COMPANY RECORDS SHOWED THE EMPTY WEIGHT OF THE ACFT WAS 5088 LBS; THE ACFT'S ACTUAL EMPTY WEIGHT WAS 5285 LBS. AN FAA INSPECTOR CALCULATED THAT THE TAKEOFF GROSS WEIGHT EXCEEDED THE MAX LIMIT BY 130 LBS.

Probable cause

FAILURE OF THE PILOT TO REMOVE FROST FROM THE AIRCRAFT. CONTRIBUTING FACTORS WERE: IMPROPER WEIGHT AND BALANCE AND SNOW COVERED TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC89FA043
Event ID
20001213X27678
Case number
ANC89FA043
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: 1a11d4a1e19049de6a3582bca9af48aaed98d5fa26a454197f6db618112c53b0; retrieved 2026-09-18T19:14:11.753Z.
  • The NTSB's operator name is blank for N5056Q; the operator shown is the name the NTSB records it doing business as.