FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southeast Aviation de Havilland DHC-2 MK.I accident

5 Aug 2021 · Ketchikan, AK, United States

de Havilland DHC-2 MK.I · Accident: controlled flight into terrain/object (CFIT) en route

From Misty Fjords, AK to an unrecorded destination

Report a problem

Event

NTSB case
ANC21FA069
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
6 · 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
Instrument Meteorological Cond

de Havilland DHC-2 MK.I

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
N1249K
Onboard fatalities
Unknown
Route
From Misty Fjords, AKTo not recorded
Aircraft age
About 56 years (built 1965)
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
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
Controlled flight into terrain/object (CFIT)
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident flight was the pilot’s second passenger sightseeing flight of the day that overflew remote inland fjords, coastal waterways, and mountainous, tree-covered terrain in the Misty Fjords National Monument. Limited information was available about the airplane’s flight track due to radar limitations, and the flight tracking information from the airplane only provided data in 1-minute intervals. The data indicated that the airplane was on the return leg of the flight and in the final minutes of flight, the pilot was flying on the right side of a valley. The airplane impacted mountainous terrain at 1,750 ft mean sea level (msl), about 250 ft below the summit.

Examination of the wreckage revealed no evidence of preaccident failures or malfunctions that would have precluded normal operation. Damage to the propeller indicated that it was rotating and under power at the time of the accident. The orientation and distribution of the wreckage indicated that the airplane impacted a tree in a left-wing-low attitude, likely as the pilot was attempting to maneuver away from terrain.

Review of weather information for the day of the accident revealed a conditionally unstable environment below 6,000 ft msl, which led to rain organizing in bands of shower activity. Satellite imagery depicted that one of these bands was moving northeastward across the accident site at the accident time. Federal Aviation Administration (FAA) weather cameras and local weather observations also indicated that lower visibility and mountain obscuration conditions were progressing northward across the accident area with time. Based on photographs recovered from passenger cell phones along with FAA weather camera imagery, the accident flight encountered mountain obscuration conditions, rain shower activity, and reduced visibilities and cloud ceilings, resulting in instrument meteorological conditions (IMC) before the impact with terrain.

The pilot reviewed weather conditions before the first flight of the day; however, there was no indication that he obtained updated weather conditions or additional weather information before departing on the accident flight. Based on interviews, the accident pilot landed following the first flight of the day in lowering visibility, ceiling, and precipitation, and departed on the accident flight in precipitation, based on passenger photos. Therefore, the pilot had knowledge of the weather conditions that he could have encountered along the route of flight before departure.

The operator had adequate policies and procedures in place for pilots regarding inadvertent encounters with IMC; however, the pilot’s training records indicated that he was signed off for cue-based training that did not occur. Cue-based training is intended to help calibrate pilots’ weather assessment and foster an ability to accurately assess and respond appropriately to cues associated with deteriorating weather. Had the pilot completed the training, it might have helped improve his decision-making skills to either cancel the flight before departure or turn around earlier in the flight. The operator’s lack of safety management protocols resulted in the pilot not receiving the required cue-based training, allowed him to continue operating air tours with minimal remedial training following a previous accident, and allowed the accident airplane to operate without a valid FAA registration.

The operator was signatory to a voluntary local air tour operator’s group letter of agreement that was developed to improve the overall safety of flight operations in the area of the Misty Fjords National Monument. Participation was voluntary and not regulated by the FAA, and the investigation noted multiple instances in which the LOA policies were ignored, including on the accident flight. For example, the accident flight did not follow the standard Misty Fjords route outlined in the LOA nor did it comply with the recommended altitudes for flights into and out of the Misty Fjords.

FAA inspectors providing oversight for the area reported that, when they addressed operators about disregarding the LOA, the operators would respond that the LOA was voluntary and that they did not need to follow the guidance. The FAA’s reliance on voluntary compliance initiatives in the local air tour industry failed to produce compliance with safety initiatives or to reduce accidents in the Ketchikan region.

Probable cause

The pilot’s decision to continue visual flight rules (VFR) flight into instrument meteorological conditions (IMC), which resulted in controlled flight into terrain. Contributing to the accident was the FAA’s reliance on voluntary compliance with the Ketchikan Operator’s Letter of Agreement.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC21FA069
Event ID
20210806103647
Case number
ANC21FA069
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: 794c9586eefca9652ee9c3cc6e326ff17cce48aa327435cc36a04b23af2196a0; retrieved 2026-09-15T07:32:49.369Z.