Aviation Crash Map

Cessna 208B N12373

30 November 2013 · Saint Marys, Alaska, United States · Fatal

Summary

On 30 November 2013 at about 03:24 local time, a Cessna 208B registered N12373, operated by Hageland Aviation, was involved in an accident near Saint Marys, Alaska, United States. 11 people were on board and 5 died, 6 were seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 03:24
Classification
Accident
Location
Saint Marys, Alaska, United States
Nearest airport
St Mary's (KSM)
Coordinates
62.0508, -163.2692
Aircraft
Cessna 208B
Registration
N12373
Category
Airplane
Year built
1998
Engines
1
Operating rule
Part 135: Air Taxi & Commuter
Phase of flight
Not recorded
Route
Bethel → Saint Marys
Aircraft damage
Substantial
Weather
IMC
Light
Night
NTSB number
ANC14MA008

People

5 people died.

On board Died Serious Minor Uninjured
11 5 6 0 0

Probable cause

The pilot's decision to initiate a visual flight rules approach into an area of instrument meteorological conditions at night and the flight coordinators' release of the flight without discussing the risks with the pilot, which resulted in the pilot experiencing a loss of situational awareness and subsequent controlled flight into terrain. Contributing to the accident were the operator's inadequate procedures for operational control and flight release and its inadequate training and oversight of operational control personnel. Also contributing to the accident was the Federal Aviation Administration's failure to hold the operator accountable for correcting known operational deficiencies and ensuring compliance with its operational control procedures.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.

Other Cessna 208 accidents

Date Aircraft Location Operator Outcome Died
12 Dec 2013 Cessna 208B
N687MA
Kalaupapa, Hawaii, United States Makani Kai Air Fatal 1
22 Oct 2013 Cessna 208
N861MA
Wailea, Hawaii, United States Mokulele Flight Service Inc No injuries -
16 Jan 2013 Cessna 208B
N1120N
Pellston, Michigan, United States Martinaire Aviation, L.L.C. Fatal 1
15 Jul 2013 Cessna 208B
8R-AMS
Mathews Ridge, Guyana Air Services Limited Serious injuries -
14 Oct 2013 Cessna 208B
XA-TXM
Loreto, BCS, Mexico Aeroservicios Guerrero S.A. de C. V. Fatal 14
17 Jul 2013 Cessna 208B
N732MD
Chicago, Illinois, United States Multi-Aero Inc No injuries -

All 339 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
24 Jul 2013 De Havilland BEAVER DHC 2
N4787C
Thorne Bay, Alaska, United States Promech Air LLC Serious injuries -
5 Sep 2013 Cessna U206G
N735LS
McGrath, Alaska, United States Alaska Skyways, Inc. Minor injuries -
26 Mar 2013 De Havilland DHC-2 MK. I(L20A)
N995SP
Anchorage, Alaska, United States Joe Schuster No injuries -
9 Sep 2013 Zenith 701
N701MG
Big Lake, Alaska, United States Whedbee Kenneth Mikel Trustee Fatal 1
16 Feb 2013 Piper PA-31-350
N15PR
Dutch Harbor, Alaska, United States Grant Aviation Inc No injuries -
18 Feb 2013 Cessna 170B
N2814C
Skwentna, Alaska, United States Stone Robert D Serious injuries -

All 170,864 records in United States