6 Mar 2013: CESSNA 207 — Yute Air Alaska

6 Mar 2013: CESSNA 207 (N1704U) — Yute Air Alaska

No fatalities • Bethel, AK, United States

Probable cause

The failure of the engine’s No. 1 piston connecting rod retaining bolts due to fatigue fracturing, which resulted in a loss of engine power during cruise flight.

— NTSB Determination

Accident narrative

On March 6, 2013, about 1730 Alaska standard time, a Cessna 207 airplane, N1704U, sustained substantial damage during a forced landing on snow-covered tundra about 16 miles northeast of Bethel, Alaska. The airplane was operated as Flight 595, by Yute Air Alaska, Anchorage, Alaska, as a visual flight rules, scheduled passenger/cargo flight under the provisions of 14 Code of Federal Regulations Part 135. The airline transport pilot and the two passengers were not injured. Visual meteorological conditions prevailed at the time of the accident, and the airplane was operating on a company VFR flight plan. The flight had departed Bethel about 1718, en route to Kalskag, Alaska.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge on March 6, the director of operations for Yute Air Alaska reported that the flight originally departed Bethel destined for Kalskag. The pilot reported that about 15 minutes after departure, the engine made a "very loud and unusual whining" noise, which was followed by a partial loss of engine power. He reported the problem to his dispatcher via the company radio frequency, and began a turn toward a frozen pond for an emergency landing. During the turn, all engine power was lost. He then selected a closer area of snow-covered terrain, with small trees, as a forced landing site. Just prior to touchdown, the left stabilizer struck the tops of the trees, resulting in substantial damage to the horizontal stabilizer. After touchdown, the nose tire and fork broke free of the airplane.

The airplane was equipped with a Continental Motors IO-520 series engine. A preliminary examination of the engine by company maintenance personnel revealed a crack in the crankcase.

The airplane was recovered to a company facility where the engine was removed and shipped to Alaska Aircraft Engines, Anchorage for further examination. The engine was subsequently crated and shipped to Continental Motors, Inc. Analytical Department, Mobile, Alabama for disassembly and inspection.

On May 15, 2013 under the supervision of an FAA District Office MIDO Safety Inspector, the engine was disassembled and examined at Continental Motors.

The examination revealed that most of the engine's major internal damage was associated with the number one piston assembly.

According to a report prepared by the manufacturer's investigator, the number one piston was fractured at the piston pin bore, releasing the number one rod and piston pin assembly at the small end. The unsupported number one rod and piston pin assembly caused damage to the rear section of the crankcase and camshaft. The number one rod had released from the crankshaft, and exhibited extreme mechanical damage. The number one rod was found in the oil sump. There were no signs of lubrication distress. Portions of the piston skirt were recovered from the oil sump and inspected in the CMI lab. The number one cylinder, piston, rod, and sump contents were retained in bonded storage.

The number one piston assembly, connecting rod, and associated pieces were shipped to the National Transportation Safety Board Materials Laboratory, Washington, DC.

An examination of the number one piston assembly at the NTSB laboratory on February 12, 2014, revealed fatigue fractures in both connecting rod retaining bolts. Damage to the piston and wrist pin were consistent with damage following the release of the connecting rod from the crankshaft. A copy of the NTSB laboratory report is in the public docket for this case.

Contributing factors

  • cause Recip eng cyl section — Failure

Conditions

Weather
VMC, wind 030/11kt, vis 10sm

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.