N786SRBeech B200 · 1982

On May 16, 2011, about 0218 Alaska daylight time, a Beechcraft B200 airplane, N786SR, sustained substantial damage during a collision with terrain about 7 miles southwest of Atqasuk, Alaska, while on an instrument approach to the Atqasuk Edward Burnell Senior Memorial Airport. The airplane was operated by the North Slope Borough, Barrow, Alaska, as a instrument flight rules (IFR), public aircraft medical transport positioning flight, under 14 Code of Federal Regulations (CFR), Part 91. The airline transport pilot received minor injuries, and the two North Slope Borough medical personnel aboard received minor injuries. Instrument meteorological conditions prevailed, and an instrument flight plan was in effect. The medical transport flight departed the Wiley Post/Will Rogers Memorial Airport, Barrow, Alaska, about 0148, and was en route to Atqasuk to transport a patient to Anchorage, Alaska.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the chief pilot for the operator said the pilot reported to him that during the approach to Atqasuk, the airplane accumulated a large quantity of airframe ice, and he decided to discontinue the approach. He then retracted the landing gear, but the airplane failed to climb as anticipated, and struck the ground.

During the impact with terrain, the empennage was severed from the airplane.

Due to the remote location, the wreckage was not examined by the NTSB. No mechanical issues were reported by the operator or the pilot.

Photographs received from the operator, and reviewed by the NTSB IIC, showed that the airplane impacted flat, snow-covered tundra in a wings-level, tail-low attitude. The tail section aft of the passenger cabin was severed from the fuselage, and had upward crushing. Photographs of both propellers showed extreme torsional twisting and bending.

In a written statement the pilot said about 35 miles from the destination airport he received clearance for the RNAV (GPS) Rwy 6 approach (copy of the approach plate is contained in the public docket for this report). He started a descent, but remained above 2200 feet which was above the cloud tops. Prior to reaching the initial approach fix (IAF) FIBAK, he descended to 2,000 feet, which was mostly in the clouds. All of the anti-ice systems were turned on, and the deice boots were activated one time, prior to reaching intermediate fix (IF) DUVFU. From DUVFU he proceeded inbound to the final approach fix (FAF) IRIQU (8.7 miles), while descending to 1,700 feet. According to the pilot, the deice boots seemed to be shedding the ice almost completely, and everything was in order. About midway between DUFVU and IRIQU he extended the flaps, and about one mile from IRIQU he extended the landing gear. After extending the landing gear he added power, but the airplane continued to descend. He raised the flaps and gear, and applied full climb power. The airplane shuddered as it climbed through about 2,000 feet, and started to break out of the clouds, but the airspeed continued to decrease. The stall warning horn came on, and remained on continuously. He said he lowered the nose to increase airspeed. The airplane broke out of the clouds about 800 feet above the ground, but continued to descend, and impacted the snow-covered terrain.

Although the pilot told his supervisor that he was properly rested, and fit to make the flight, he had clocked in for duty at 1228 the previous day, and clocked out at 2207, less than 2 hours before he was called for the accident flight. During that duty period he had not flown any aircraft.

In a written statement, a passenger in a forward facing seat behind the pilot said she had a clear view of the center and right side cockpit instruments. During the final approach she said she saw the instrument panel, and noted the altitude, 1,400 feet, estimated time en route (ETE) 1:30 and decreasing, and speed 148 knots. The last time she looked at the panel she noted that the altitude was holding at 1,400, and the ETE was 1:26. She heard the power increase, and felt the airplane's nose pitch up. As the airplane's nose pitched up, the airplane began to roll from side to side. The attitude indicator showed rolls in both directions exceeding 45 degrees. The airplane broke out of the clouds momentarily, but then descended back into them. When the airplane broke out beneath the clouds, the left wing was pointed at the ground, greater than 45 degrees. The airplane impacted the snow-covered tundra. The passenger reported seeing rime ice on the right wing, behind the de-ice boot, from the center of the wing to the tip, after the accident. She reported there was no ice on the left wing. The passenger's statement is contained in the public docket for this report.

The accident airplane was equipped with external satellite tracking, and internal engine and flight control monitoring. The data was provided by the operator, and examined by the IIC. According to the airplane's pilot operating handbook (POH), section 4, page 23, the minimum safe operating speed for the airplane in continuous icing conditions is 140 knots indicated airspeed (IAS). The airplane's indicated airspeed dropped below 140 knots at 02:13:53, four minutes prior to impact. At 02:14:53 the IAS had dropped to 100.2 knots. At 02:15:53 the IAS was 85.9 knots, and at 02:16:53 the IAS had increased to 112 knots. During the last one minute of flight, the indicated airspeed varied continuously to a high of 124.5 knots to a low of 64.6 knots, and the vertical speed varied from +1965 feet per minute to -2464 feet per minute. The last data prior to impact, at 02:17:52, showed that the airplane was at an altitude of 67 feet, heading 216 degrees, indicated airspeed 68 knots, descending at 1651 feet per minute, and the nose was pitched up at 20 degrees.

Weather reported at the destination airport at the time of the accident was; ceiling 800 overcast, 3 miles visibility, temperature/dew point was 27/25,wind 070 degrees at 15, not gusting, and the altimeter was 29.78 inches of mercury.

The area forecast anticipated moderate icing in the area.

In a written statement the chief pilot wrote that borough pilots are on call for 14/24 hour periods. Then they are off two weeks. The accident pilot worked the previous day, but was the only pilot who had not flown any missions. He had clocked in at 1228 and out at 2207. According to the chief pilot, he was the most suitable pilot for the operation that began just after midnight. The chief pilot verbally queried him on his state of rest and currency to accept the mission, and he stated he was fine to take the flight. The chief pilot was aware that sleep cycles and circadian rhythms are disturbed by varied shift schedules and prolonged activity.

An NTSB study of flight crew-involved major accidents found that pilots with more than 12 hours (averaging 13.8 hours) of time since waking made significantly more procedural and tactical decision errors (mostly errors of omission) than pilots with less than 12-hours of time since waking.

A 2000 FAA-sponsored study found accidents to be more prevalent among pilots who had been on duty for more than 10 hours. Additionally, a study performed by the U.S. Naval Safety Center found that helicopter pilots who were on duty for more than 10 of the last 24 hours were more likely to be involved in pilot-at-fault accidents than pilots who had not accumulated as much duty time.

Although many EMS flights are flown under FAR Part 135, this flight was flown under CFR Part 91. FAR Part 135 and Part 91 differ regarding crew rest requirements. The provisions of Part 135 require that the flight crew obtain adequate rest before conducting an EMS flight with a patient on board, calling for a minimum of 9 consecutive hours of rest during the 24 consecutive hour period prior to the completion of the assigned flight. In contrast, Part 91 has no duty time restrictions. As noted, fatigue impairs performance and diminishes alertness.

According to the North Slope Borough's Assistant Fire Chief, the North Slope Borough's practice is to base the go/no-go decision solely on the ability to go, that is, crew, aircraft and weather, without considering the necessity to go, i.e., patient condition, or time of day.

The area hospitals/clinics do not typically triage a patient’s transportation; they simply request that they be transported. Following the accident flight, due to the non critical nature of the patient's injury/illness, the patient took a commercial flight to Anchorage the following morning for further medical treatment.

The following FAA advisory circulars are directed at commercial EMS patient transportation, and while they are not mandated for Part 135, Part 91, or Public Aircraft operations, they do outline certain professional protocols to be followed when transporting patients for hire.

FAA Advisory Circular (AC) 135-14A states in part:

(6) A decision whether or not to conduct a flight, or to continue a flight as planned, is required by regulation to be made by the pilot in command. This decision should be based on the information received from other elements involved and on his/her judgment as an experienced pilot. The decision should not be based solely on the condition of the patient.

(7) The final step is the decision to conduct the flight in a safe and timely manner.

f. Judgment and Decisions

The decision making process should have input from all elements involved in an EMS operation. Aero medical directors, aircraft operators, the flight crew, medical personnel, and ground crew contribute to this process. The degree of input from each element depends upon the type and complexity of every mission.

Flight Time and Rest Requirements. Each operator should maintain records showing compliance with the flight and rest requirements of FAR Part 135.

(1) The certificate holder's manual should include policy regarding pilots on call with the use of remote paging devices. The manual should indicate how the use of these devices impacts duty time limitations.