FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Taquan Air De Havilland DHC 3 Undesignat accident

10 Jul 2018 · Hydaburg, AK, United States

De Havilland DHC 3 Undesignat · Accident: loss of visual reference en route

From Klawock, AK to Ketchikan, AK

Report a problem

Event

NTSB case
ANC18FA053
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
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
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 3 Undesignat

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
N3952B
Operator
Taquan Air
Onboard fatalities
Unknown
Route
From Klawock, AKTo Ketchikan, 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
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
Loss of visual reference
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

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

NTSB narrative

The airline transport pilot was conducting a commercial visual flight rules (VFR) flight transporting 10 passengers from a remote fishing lodge. According to the pilot, while in level cruise flight about 1,100 ft mean sea level (msl) and as the flight progressed into a mountain pass, visibility decreased rapidly. In an attempt to turn around and return to VFR conditions, the pilot initiated a climbing right turn. Before completing the 180° right turn, he saw what he believed to be a body of water and became momentarily disoriented, so he leveled the wings. Shortly thereafter, he realized that the airplane was approaching an area of snow-covered mountainous terrain, so he applied full power and initiated a steep climb; the airspeed decayed, and the airplane collided with an area of rocky, rising terrain, which resulted in substantial damage to the wings and fuselage.

The pilot reported no mechanical malfunctions or anomalies that would have precluded normal operation, and the examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The weather forecast at the accident time included scattered clouds at 2,500 ft msl, overcast clouds at 5,000 ft msl with cloud tops to 14,000 ft and clouds layered above that to flight level 250, and isolated broken clouds at 2,500 ft with light rain. AIRMET advisory SIERRA for "mountains obscured in clouds/precipitation" was valid at the time of the accident. Conditions were expected to deteriorate. Passenger interviews revealed that through the course of the flight, the airplane was operating in marginal visual meteorological conditions and occasional instrument meteorological conditions (IMC) with areas of precipitation, reduced visibility, obscuration, and, at times, little to no forward visibility. Thus, based on weather reports and forecasts, and the pilot's and passengers' statements, it is likely that the flight encountered IMC as it approached mountainous terrain and that the pilot then lost situational awareness.

The airplane was equipped with a terrain awareness and warning system (TAWS); however, the alerts were inhibited at the time of the accident. Although the TAWS was required to be installed per Federal Aviation Administration (FAA) regulations, there is no requirement for it to be used. All company pilots interviewed stated that the TAWS inhibit switch remained in the inhibit position unless a controlled flight into terrain (CFIT) escape maneuver was being accomplished. However, the check airman who last administered the accident pilot's competency check stated that the TAWS inhibit switch was never moved, even during a CFIT escape maneuver. The unwritten company policy to leave the TAWS in the inhibit mode and the failure of the pilot to move the TAWS out of the inhibit mode when weather conditions began to deteriorate were inconsistent with the goal of providing the highest level of safety. However, if the pilot had been using TAWS, due to the fact that he was operating at a lower altitude and thus would have likely received numerous nuisance alerts, the investigation could not determine the extent to which TAWS would have impacted the pilot's actions.

At the time of the accident, the director of operations (DO) for the company resided in another city and served as DO for another air carrier as well. He traveled to the company's main base of operation about once per month but was available via telephone. According to the chief pilot, he had assumed a large percentage of the DO's duties. The president of the company said that the chief pilot had taken over "officer of the deck" and "we're just basically using him [the DO] for his recordkeeping."

The FAA was aware that the company's DO was also DO for another commuter operation. FAA Flight Standards District Office management and principal operations inspectors allowed him to continue to hold those positions, although it was contrary to the guidance provided in FAA Order 8900.1.

The company's General Operations Manual (GOM) only listed the DO, the chief pilot, and the president by name as having the authority to exercise operational control. However, numerous company personnel stated that operational control could be and was routinely delegated to senior pilots. The GOM stated that the DO "routinely" delegated the duty of operational control to flight coordinators, but the flight coordinator on duty at the time of the accident stated that she did not have operational control. In addition, the investigation revealed numerous inadequate and missing operational control procedures and processes in company manuals and operations specifications.

Based on the FAA's inappropriate approval of the DO, the insufficient company onsite management, the inadequate operational control procedures, and the exercise of operational control by unapproved persons likely resulted in a lack of oversight of flight operations, inattentive and distracted management personnel, and a loss of operational control within the air carrier. However, the investigation could not determine the extent to which any changes to operational control, company management, and FAA oversight would have influenced the pilot's decision to continue the VFR flight into IMC.

Probable cause

The pilot's decision to continue the visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC18FA053
Event ID
20180711X04255
Case number
ANC18FA053
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. 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: 170fd07d58ae8d3b5fc9314527002f3fef2ed2b3d492e6bd052ab049f5e5deae; retrieved 2026-09-16T07:48:58.960Z.