ANC04LA098 · de Havilland DHC-3
Exousia de Havilland DHC-3 · Accident: in flight encounter with weather while maneuvering
From McGrath Airport (PAMC) to Ralph Wien Memorial Airport (PAOT)
Event
- NTSB case
- ANC04LA098
- 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
- 1 · 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
- Instrument 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
- N197TT
- Operator
- Exousia
- Onboard fatalities
- Unknown
- Route
- From McGrath Airport (PAMC), McGrath, AKTo Ralph Wien Memorial Airport (PAOT), Kotzebue, 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
- Maneuvering
- 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 encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); 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
- Destroyed
Cause areas
- Pilot in command › Clearance, inadequate
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport certificated pilot was conducting a VFR cross-country business flight, transporting cargo and personnel to a remote airport. The accident airplane was one of two airplanes transporting supplies for a hunting/fishing company, traveling a multi-segment route. The pilot was accompanied by a pilot-rated passenger occupying the right front seat, and a second passenger seated behind the pilot. The pilot obtained a weather briefing from the FAA, which included AIRMETs for mountain obscuration, and IFR conditions due to low ceilings and visibility in smoke, light rain and mist. The pilot said that when he took off on the accident flight, the visibility was 1 to 3 miles in smoke, haze, and fog, but was VFR. He recalled hazy conditions in which he could see rolling hills and river cuts. The pilot-rated passenger was initially flying the airplane. Upon entering lowering visibility, the pilot said he reassumed control of the airplane, and attempted a 180 degree turn to clear the low visibility area, but collided with trees and crashed. The rear seat passenger reported that the accident airplane was flying about 500 to 1,000 feet above the ground because of smoke and fog. He estimated the visibility at takeoff was about 1 mile. About 30 minutes after departure, the airplane was flying over mountainous terrain, and appeared to be following a canyon. The passenger said that the visibility decreased due to fog. He said that the airplane's throw-over control yoke was initially positioned in front of the right seat, pilot-rated passenger, when suddenly a mountain ridge appeared in front of the airplane. The pilot repositioned the control yoke in front of the left seat, banked the airplane to the left, and added engine power. Within a few seconds, the passenger indicated that he felt the airplane collide with several trees and then descend to the ground. The airplane came to rest upright with extensive fuselage damage, about 1,400 feet msl. One wing was torn off the airframe. A postcrash fire consumed the wreckage. A terminal forecast for the airport of departure included few clouds at 500 feet, and visibilities as low as 3 miles in smoke and mist. The destination airport for the accident flight segment had few clouds at 100 feet, and visibilities as low as 2 1/2 miles.
Probable cause
The pilot's inadequate in-flight planning/decision making, his continued VFR flight into instrument meteorological conditions, and his failure to maintain obstacle clearance. Factors contributing to the accident were low ceilings due to smoke, rain, and mist.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC04LA098
- Event ID
- 20040831X01327
- Case number
- ANC04LA098
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-08-28.
- API snapshot SHA-256: c08cc2fb3ac90cefe927e860c66487fe020eadf6b06b8d294b68854dcc37a64c; retrieved 2026-09-20T18:21:38.681Z.