The U.S. aircraft register, updated daily
Accidents · NTSB CEN19LA163 · Final report

Amateur-built Challenger accident near Switz City, Indiana, June 11, 2019

On June 11, 2019 at about 1:00 am local time, a 2010 amateur-built Challenger, registered N582L, was substantially damaged in an accident during enroute near Switz City, Indiana. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to failure of a connecting rod bearing. Contributing to the engine failure was the lack of an engine overhaul within the prescribed interval.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 11, 2019 · about 1:00 am local time
Place
Switz City, Indiana · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Challenger II, built 2010
Registration
N582L · registry record · serial CH2-0708-LSS-LW
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of the experimental, amateur-built airplane reported that, while returning to the airport after a local flight, the engine speed "suddenly" decreased from about 5,000 rpm to 2,500 rpm. He trimmed the airplane for its best glide airspeed and began looking for a forced landing site. About 30 seconds later, the engine seized and lost power completely. The airplane touched down short of the pilot's intended landing point and nosed over resulting in substantial damage to the fuselage and empennage. An engine examination revealed that a lower connecting rod bearing had failed, resulting in the total loss of engine power. Maintenance records indicated that an engine overhaul was completed slightly more than 5 years before the accident flight. The engine manufacturer's maintenance schedule specified that an engine overhaul be completed every 5 years or 300 hours, whichever comes first. It is likely that, had the engine been overhauled in accordance with manufacturer guidance, the worn connecting rod bearing would have been detected during the overhaul and resulted in its replacement.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Powerplant sys/comp malf/fail during enroute
  2. Loss of engine power (total) during enroute defining event
  3. Off-field or emergency landing during emergency descent

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Fatigue/wear/corrosion
  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
  • factor Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Owner/builder

Pilot

  • Certificate: student
  • Flight time: 124 hours in all; 76 in this make and model; 11 in the last 90 days; 4 in the last 30 days
  • Last flight review: March 23, 2019
  • Medical certificate: None
  • Seat: frt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 176 hours
  • Last inspection: condition inspection, August 15, 2018; 46 hours since
  • Maximum gross weight: 1,075 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582 (piston); 176 hours total

The flight

  • Departed from: 1I3 Bloomfield IN at 11:30 pm
  • Destination: 1I3 Bloomfield IN
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Temperature: 61°F (16°C), dew point 55°F (13°C)
  • Altimeter: 30.11 inHg
  • Observation at 2:53 am from BMG, 21 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on February 28, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.