Saint Mary's

The approach to Saint Mary's Airport was initiated in marginal weather conditions. On short final, the single engine airplane crashed about 800 metres short of runway and was destroyed. All four occupants were killed. The airplane was completing a taxi flight from Bethel.

The scheduled commuter flight departed 40 minutes late for a two-stop flight. During the first leg of the night visual flight rules (VFR) flight, weather at the first destination airport deteriorated, so the pilot diverted to the second destination airport. The pilot requested and received a special VFR clearance from an air route traffic controller into the diversion airport area. Review of automatic dependent surveillance-broadcast data transmitted by the airplane showed that, after the clearance was issued, the airplane's track changed and proceeded in a direct line to the diversion airport. Postaccident examination of the pilot's radio showed that his audio panel was selected to the air route traffic control (ARTCC) frequency rather than the destination airport frequency; therefore, although the pilot attempted to activate the pilot-controlled lighting at the destination airport, as heard on the ARTCC frequency, it did not activate. Further, witnesses on the ground at St. Mary's reported that the airport lighting system was not activated when they saw the accident airplane fly over, and then proceed away from the airport. Witnesses in the area described the weather at the airport as deteriorating with fog and ice. About 1 mile from the runway, the airplane began to descend, followed by a descending right turn and controlled flight into terrain. The pilot appeared to be in control of the airplane up to the point of the right descending turn. Given the lack of runway lighting, the restricted visibility due to fog, and the witness statements, the pilot likely lost situational awareness of the airplane's geographic position, which led to his subsequent controlled flight into terrain. After the airplane proceeded away from the airport, the witnesses attempted to contact the pilot by radio. When the pilot did not respond, they accessed the company's flight tracking software and noted that the airplane's last reported position was in the area of the airplane's observed flightpath. They proceeded to search the area where they believed the airplane was located and found the airplane about 1 hour later. Postaccident examination of the airframe and engine revealed no mechanical malfunctions or anomalies that would have precluded normal operation. About 3/4 inch of ice was noted on the nonprotected surfaces of the empennage. However, ice formation on the airplane's inflatable leading edge de-ice boots was consistent with normal operation of the de-ice system, and structural icing likely was not a factor in the accident. According to the company's General Operations Manual (GOM), operational control was held by the flight coordinator for the accident flight, and the flight coordinator and pilot-in-command (PIC) were jointly responsible for preflight planning, flight delay, and release of the flight, which included the risk assessment process. The flight coordinator assigned the flight a risk level of 2 (on a scale of 1 to 4) due to instrument meteorological and night conditions and contaminated runways at both of the destination airports. The first flight coordinator assigned another flight coordinator to create the manifest, which listed eight passengers and a risk assessment level of 2. According to company risk assessment and operational control procedures, a risk level of 2 required a discussion between the PIC and flight coordinator about the risks involved. However, the flight coordinators did not discuss with the pilot the risks and weather conditions associated with the flight. Neither of the flight coordinators working the flight had received company training on the risk assessment program. At the time of the accident, no signoff was required for flight coordinators or pilots on the risk assessment form, and the form was not integrated into the company manuals. A review of Federal Aviation Administration (FAA) surveillance activities revealed that aviation safety inspectors had performed numerous operational control inspections and repeatedly noted deficiencies within the company's training, risk management, and operational control procedures. Enforcement Information System records indicated that FAA inspectors observed multiple incidences of the operator's noncompliance related to flight operations and that they opened investigations; however, the investigations were closed after only administrative action had been taken. Therefore, although FAA inspectors were providing surveillance and noting discrepancies within the company's procedures and processes, the FAA did not hold the operator sufficiently accountable for correcting the types of operational deficiencies evident in this accident, such as the operator's failure to comply with its operations specifications, operations training manual, and GOM and applicable federal regulations.

The airline transport pilot was cleared for the localizer approach. The airplane impacted the ground 3.2 nautical miles from the runway threshold. The minimum descent altitude (MDA) for the approach was 560 feet msl, which is 263 feet above touchdown. Night, instrument meteorological conditions prevailed at the time of the accident. The surrounding terrain was flat, snow-covered, and featureless. The reported weather was 200 feet overcast, 1 1/2 miles visibility in snow, and winds of 12 knots, gusting to 32 knots. The pilot reported he was established on the final approach course, descending to the MDA, and then woke up in the snow. He said he did not remember any problems with the airplane. No pre accident mechanical anomalies were discovered with the airplane during the investigation. The airport has high intensity runway lights, sequenced flashing lead-in lights, and visual approach slope indicator lights. All airport lights and navigation aids were functioning. The airplane was not equipped with an autopilot. Captains have the option of requesting a copilot, but, the captain's pay is reduced by a portion equal to one-half the copilot's pay. The pilot had returned from the previous nights trip at 0725. He had three rest periods, four hours, two hours, and five hours 15 minutes, since his previous nights flight. Each rest period was interrupted by contact with the company. The company indicated that it is the pilot's responsibility to tell the company if duty times are being exceeded. 14 CFR 135.267 states, in part: '(d) Each assignment ... must provide for at least 10 consecutive hours of rest during the 24 hours that precedes the planned completion of the assignment.'

The CFR Part 135 cargo flight departed at night on an IFR flight with a load of mining equipment. Route of flight was over remote/mountainous terrain. About 2 hours after takeoff, while cruising at 12,000' feet msl, the right engine and propeller began to overspeed. The captain feathered the #2 engine and declared an emergency. He began to divert to an alternate destination, about 120 miles away in an area of lower terrain, but the aircraft would not maintain altitude (single engine service ceiling, as loaded, was about 8,700 feet). The captain increased power to the left engine, but it began to produce banging and coughing noises. The captain elected to perform an emergency landing at a nearby, remote, military airfield (A/F). The A/F was located in mountainous terrain and had a one-way, daylight only approach. The captain lowered the gear and flaps, and began a visual approach while attempting to keep the runway end identifier lights (REIL) in view. The aircraft encountered severe turbulence, and the captain applied full throttle to the left engine in an attempt to climb. The REIL disappeared from view, and the aircraft collided with snow covered terrain about 2 miles west of the A/F. Ground personnel at the A/F reported high winds and blowing snow with limited visibility. Postcrash exam of the right engine revealed a loss of the propeller control system hydraulic oil. Flight at 12,000 feet was conducted without crew oxygen. The crew had exceeded their maximum allowable duty day without adequate crew rest.

The pilot stalled the airplane while making a steep turn to avoid high voltage power lines. The airplane caught fire on impact and the air taxi pilot subsequently died of extensive thermal injuries. The pilot was flying in formation with another aircraft at low altitude. When the power lines were sighted the other aircraft successfully pulled up and avoided the wires. The accident pilot turned steeply and lost control of the aircraft before crashing.

The aircraft crashed during a LOC DME approach. According to ATC the aircraft crashed after making a procedure turn at the faf. The winds in the area were being called 250° at 10 knots gusting to 28 knots. A caution on the approach plate has a remark, 'precipitous terrain - expect turbulence'. Both occupants were killed.

While approaching Chevak, the pilot encountered whiteout conditions and limited visibility due to snow falls. The pilot suffered a spatial disorientation and the airplane collided with ground while in traffic pattern-circling. Two passengers were killed while five other occupants were seriously injured.

The approach to Land’s End Airport was completed in very bad weather conditions. During the last segment, the twin engine aircraft hit the runway surface, went out of control and crashed. All six passengers were injured and the pilot, Captain David Louis Dustin was killed.

The aircraft departed St Mary's on a private trip to Bradford, north Pennsylvania. En route, the pilot encountered poor visibility due to foggy conditions. He reduced his altitude and apparently attempted an emergency landing when the aircraft crashed in a pasture near Kane. The aircraft was destroyed and all four occupants were killed.