23 Aug 2008: CESSNA 207A — HAGELAND AVIATION

23 Aug 2008: CESSNA 207A (N17GN) — HAGELAND AVIATION

No fatalities • Kongiganak, AK, United States

Probable cause

The pilot's decision to attempt to takeoff on a short, wet runway with a heavily loaded airplane, and his failure to abort the takeoff before it became impracticable.

— NTSB Determination

Accident narrative

On August 22, 2008, about 1815 Alaska daylight time, a Cessna 207A airplane, N17GN, operated by Hageland Aviation, Anchorage, Alaska, as scheduled commuter Flight 8066, overran the runway at Kongiganak, Alaska, during an aborted takeoff, sustaining substantial damage to the left wing and fuselage. The commercial pilot and three of the five passengers reported no injuries; two passengers reported minor injuries. The flight was en route to Bethel, Alaska, in visual meteorological conditions, and a company VFR flight plan was in effect.

In a telephone interview with the NTSB investigator-in-charge on September 3, 2008, the pilot related that he loaded numerous bags and five passengers in preparation for takeoff on runway 36, which is 1,885 feet long and has a gravel surface. The pilot noted that he was at or near gross weight, but didn't have an exact weight of the airplane at the time he attempted to takeoff. He said that the tail of the airplane fell to the ground as it was being loaded, but that he didn't have the front seat passenger or himself seated yet, and once they were seated, the airplane's tail remained off the ground.

He noted that a thunderstorm had passed through the general vicinity, that it was still raining, and the runway was wet. He thought the wind was calm. After he applied full power for takeoff, he said that he encountered numerous water puddles on the runway which slowed the airplane's acceleration. About 3/4 down the runway, the airplane lifted off, but would not climb. He indicated that he looked at the fuel pressure gauge, which seemed a little low, and he felt that the engine wasn't making full power, but he wasn't sure. The airplane flew over the end of the runway in ground effect, but would not climb, and began to sink. The pilot stated that he added another 10 degrees of flap to the 20 degrees he already had, and pulled back on the control wheel to cushion the collision with the tundra.

The pilot said he had flown the airplane on four or five legs that day, and had no problems with the engine. He also said that he had what he thought was a low power indication a few days before the accident, and had told company maintenance personnel about it. In his written statement to the NTSB, the pilot said he thought the accident was due to the runway conditions, a lack of power, and "being heavy, but under gross weight."

Discussions with the operator's director of operations disclosed no recent history of any engine performance or maintenance problems, and a review of company maintenance records revealed no pilot complaints about significant mechanical problems or power loss in the preceding 60 days. In a written report submitted by the operator's director of operations, he indicated there were no mechanical problems with the airplane at the time of the accident.

On September 17, an FAA aviation airworthiness inspector went to the operator's facility in Bethel and inspected the accident engine. After the inspection, the inspector monitored the engine while it was started and ran to full operating rpm without any anomalies, including fuel pressure, fuel flow, and engine magnetos.

A witness to the accident noted that the airplane slowed significantly each time that it hit a water puddle during the takeoff roll, and that there were numerous bags aboard, and a very large man seated in the right front seat. He also said he thought there was a slight tailwind during the takeoff attempt.

Contributing factors

  • cause Pilot
  • Capability exceeded
  • cause Decision related to condition
  • factor Contributed to outcome

Conditions

Weather
VMC, wind 310/06kt, vis 7sm

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.