Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 27, 2011 · Richard Challenger II · N9103L

Moses Lake, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 27, 2011
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury)
Location
Moses Lake, WA
Aircraft
Richard Challenger II
Tail Number
N9103L
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
WPR11LA291

The pilot and the flight instructor were in the process of starting the climb after takeoff in the airplane that the pilot had recently purchased. As they started to turn toward the practice area, the airplane’s water-cooled engine suddenly began to overheat. The pilots therefore initiated a turn back toward the airport, but the engine started losing power. Because it appeared that they would not be able to make it to the airport, the flight instructor took over and landed the airplane in a nearby soft field covered with a crop of wheat. During the landing roll, the airplane nosed over and a fire began, which eventually consumed much of the airframe structure and engine components. Although the engine cooling system was missing a mandatory cooling system vent line, the teardown examination did not reveal any evidence of overheating or component seizure in the engine’s top end. The investigation also determined that the failure of the crankshaft to rotate after the accident was due to the postaccident melting and subsequent solidification of the phenolic MAG bearing cages due to the postimpact fire. The investigation was unable to determine the reason for the loss of engine power.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time09:30 PDT
Nearest Airport0nm
Flight Plan FiledNone
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftRichard Challenger II
Tail NumberN9103L
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsBombardier · ROTAX (ALL) · Reciprocating · 66
Seats2

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury)
Fatal0
Serious1
Minor1
Uninjured0
Total2
Crew 1Age 70 · Second Class · Serious
Crew 2Age 58 · None · Minor

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point45 C
Altimeter29.82 inHg
Weather SourcePILO

Appendix: Source Data