No fatalities

2018-07-10: De Havilland DHC-3 Otter (N3952B) — Taquan Air — Hydaburg, United States of America

Hydaburg, United States of AmericaFlight

On July 10, 2018, a De Havilland DHC-3 Otter (registration N3952B) operated by Taquan Air was involved in an aviation accident near Hydaburg, United States of America in flight. No fatalities were reported. Investigators recorded the probable cause as: The pilot's decision to continue the visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 6 related events involving the same aircraft type or operator are linked below.

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781191343Data APIEditorial standards

An airline transport pilot on a VFR flight with 10 passengers encountered rapidly decreasing visibility in a mountain pass, attempted a turn, lost situational awareness, and collided with mountainous terrain, resulting in substantial damage. The investigation found the pilot's decision to continue VFR into IMC as the probable cause.

Incident Overview

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

Pilot and Aircraft Information

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

Weather Conditions

The weather forecast at the time of the accident 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 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 throughout 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.

Terrain Awareness and Warning System (TAWS)

The airplane was equipped with a terrain awareness and warning system (TAWS); however, the alerts were inhibited at the time of the accident. Although TAWS was required to be installed per 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 operating at a lower altitude, he would likely have received numerous nuisance alerts; the investigation could not determine the extent to which TAWS would have impacted the pilot's actions.

Operational Control and Company Management

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 by telephone. According to the chief pilot, he had assumed a large percentage of the DO's duties. The president of the company said 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, contrary to 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 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 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 she did not have operational control. Additionally, 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, insufficient company onsite management, inadequate operational control procedures, and 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 official probable cause is the pilot's decision to continue the visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain.