27 Jun 2011: RICHARD CHALLENGER II

27 Jun 2011: RICHARD CHALLENGER II (N9103L) — Unknown operator

No fatalities • Moses Lake, WA, United States

Probable cause

A loss of engine power during the initial climb for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

— NTSB Determination

Accident narrative

On June 27, 2011, about 0930 Pacific daylight time, an experimental Richard Challenger II, N9103L, nosed over during a power-off forced landing on soft vegetation covered terrain about one-half mile west of Moses Lake Municipal Airport, Moses Lake, Washington. The flight instructor received serious injuries, and the private pilot received minor injuries. The airplane, which was owned and operated by the private pilot, sustained substantial damage. The local 14 Code of Federal Regulations Part 91 instructional flight, which was taking place in visual meteorological conditions, departed Moses Lake Municipal Airport about two minutes prior to the accident. No flight plan had been filed.

According to the Federal Aviation Administration (FAA) inspector who responded to the scene, the private pilot had recently purchased the airplane and was getting checked out in it by the flight instructor. During the first flight of the day, the owner made two takeoffs and two landings, and the flight was then terminated so that the owner and the instructor could discuss the next phase of the checkout, which was to take place beyond the traffic pattern. The owner, accompanied by the instructor, then took off for the second flight, and just after passing the end of the runway and starting to climb out in the direction of the planned practice area, the engine started overheating. They therefore elected to return to the airport, but as they started to turn back, the engine started losing power. Since it appeared that they were not going to be able to make it back to the airport, the instructor pilot took control of the airplane and attempted a landing in a soft agricultural field of tall wheat. Although the touchdown was successful, during the initial part of the landing roll, the airplane nosed over onto its back. After it flipped over, a fire broke out, which eventually consumed a majority of the airplane's structure.

The initial postaccident examination of the airplane determined that portions of the airframe and engine systems had been destroyed by the fire. A further examination of the engine, which was monitored by the Federal Aviation Administration, found two anomalies. The first was that there was no engine cooling system vent line installed. This line, which is required by section 11.3.6 of the Rotax Installation Manual, was necessary on this specific installation because the engine was installed inverted (cylinder heads down). Instead, all venting holes were closed off with threaded plugs. But a further teardown of the engine did not reveal any evidence of any unusual wear, seizure marks, lack of lubrication, or signatures indicative of overheating on the pistons, piston rings, cylinder walls, or connecting rods; which is the area the cooling system is meant to extract heat from.

The second anomaly was that the propeller and crankshaft could not be turned by hand. Therefore the crankcase halves were separated for further examination. The separation of the crankcase revealed that both the inner and outer crankshaft MAG bearings would not rotate and that their phenolic bearing cages were melted. Therefore, the crankshaft assembly, to include the bearings and connecting rods, was sent to the NTSB Materials Laboratory for further examination. There it was determined that the phenolic bearing cage material, which when tested, melted at about 400 degrees Fahrenheit, had all flowed toward one side of the bearing assembly. It was also determined that there was a congregation (ganging) of the bearing balls on the same side that the phenolic cage material had flowed to, and that there was no indication of crankshaft rotation at the time the phenolic material melted. It was also noted that the melting of the phenolic cages was not uniformly consistent around their entire circumference, but was greater on one side than on the other. There was also no indication of bearing failure or incipient failure, and all corrosion found on the internal engine parts was consistent with postaccident exposure to moisture.

At the completion of the examination process, no preimpact anomaly or malfunction had been found that would have contributed to a loss of engine power.

Contributing factors

  • Terrain

Conditions

Weather
VMC, 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.