14 Nov 2008: CESSNA 207 — Yute Air Alaska

14 Nov 2008: CESSNA 207 (N36CF) — Yute Air Alaska

No fatalities • Napaskiak, AK, United States

Probable cause

The pilot's continued flight into adverse weather and icing conditions, and his failure to maintain sufficient airspeed to avoid a stall, resulting in a loss of control and in-flight collision with terrain while on an approach to land.

— NTSB Determination

Accident narrative

On November 14, 2008, about 1710 Alaska Standard time, a Cessna 207 airplane, N36CF, sustained substantial damage when it collided with terrain while maneuvering for landing at Napaskiak, Alaska. The airplane was then consumed by a postcrash fire. The airplane was being operated as Flight 555 by Flight Alaska, dba Yute Air Alaska, Anchorage, Alaska, as a visual flight rules (VFR) commuter flight under Title 14, CFR Part 135, when the accident occurred. The commercial pilot received minor injuries, and the sole passenger was not injured. Instrument meteorological conditions prevailed in the area of the accident, and VFR company flight following procedures were in effect. The flight originated at the Quinhagak Airport, Quinhagak, Alaska, about 1625, and was en route to Bethel, Alaska.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), on November 17, the director of operations for the operator reported that numerous flights from Bethel had been canceled or delayed due to poor weather earlier in the day. The weather improved in the afternoon with a ceiling of about 1,500 feet, and a visibility of 7 miles, and the pilot departed Bethel at 1452 for his first destination, Eek, Alaska. After departure, the pilot decided not to land at his first destination because of low visibility, and continued to Quinhagak. The pilot encountered light icing conditions while en route, and deiced the airplane after landing at Quinhagak.

The pilot departed Quinhagak with one passenger about 1625, and told the director of operations that the Bethel Airport was reporting a ceiling of 500 feet overcast, with a visibility of 5 miles. After departure, the weather at Bethel deteriorated, and the pilot decided to land at Napaskiak. While maneuvering over the Napaskiak Airport, the pilot began a descending left turn toward the approach end of runway 02. The airplane stalled and mushed to the ground, about 250 feet short of the runway threshold. It collided with tall brush and the ground, and a postcrash fire erupted as the pilot and passenger were exiting the airplane.

During a telephone conversation with the NTSB IIC on November 17, the pilot reported that when he arrived over the airport at Napaskiak, he was about 200 feet agl, and the visibility was about 1 mile. He indicated that the airplane had accumulated some ice. He said he began a left turn for the runway, but the left wing stalled, and the airplane mushed into the ground.

The closest weather reporting facility is Bethel, which is located about 5 miles northwest of the accident. At 1705, an aviation routine weather report (METAR) was reporting, in part: Wind, 190 degrees (true) at 8 knots; visibility, 3/4 statute mile in mist; clouds and sky condition, 500 feet broken, 1,600 feet broken, 2,900 feet overcast; temperature, 21 degrees F; dew point, 21 degrees F; altimeter, 29.79 inHg.

Contributing factors

  • cause Airspeed — Not attained/maintained
  • cause Pilot
  • cause Response/compensation
  • cause Pilot

Conditions

Weather
IMC, wind 180/08kt, vis 0.75sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.