- Date
- June 10, 2019, 21:00 local (Jun 11, 2019, 01:00 UTC)
- Place
- Switz City, IN
- Injuries
- 1 serious
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N582LGriff Challenger
- Defining event
- Enroute: Loss of engine power (total)
- Weather
- Visual (VMC) · Day
- Status
- Completed
- Report
- Approved by Office Director
- Investigation class
- Class 3
- NTSB office
- Central Region
- Parties
- FAA Flight Standards, Rotech Flight Safety, Inc.
- FAA report
- 20190611006629A
- Case key
- 99603
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
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.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Factual narrative
On June 11, 2019, about 2100 eastern daylight time, an amateur-built Griff Challenger II airplane, N582L, was substantially damaged during a forced landing following a loss of engine power near Switz City, Indiana. The pilot sustained serious injuries. The airplane was registered to and operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological condition prevailed, and the flight was not operated on a flight plan. The local flight departed from Shawnee Field (1I3), Bloomfield, Indiana, about 1930. The pilot reported that while returning to the airport at 2,000 ft mean sea level the engine speed "suddenly" decreased from about 5,000 rpm to 2,500 rpm. The engine water temperature began "rising fast." He trimmed the airplane for best glide airspeed and began looking for a forced landing site. About 30 seconds later, the engine lost power completely. The airplane touched down short of his intended landing point and nosed over. An engine examination was conducted under oversight of a Federal Aviation Administration inspector, with the assist of a technical representative of the engine manufacturer. The examination revealed a lower connecting rod bearing had failed. Metallic debris consistent with fragmented bearing material was recovered from the cylinder. The cylinder head and the piston exhibited mechanical peening damage. The connecting rod exhibited surface corrosion but appeared otherwise intact. Excessive play was noted between the connecting rod and the crankshaft journal consistent with the failure of the bearing. The airplane maintenance records noted that the engine was reinstalled after an overhaul on April 21, 2014 at 75.3 hours total airframe time. The most recent condition inspection was completed on August 15, 2018 at 130 hours total airframe time. The pilot reported the airframe time was 176 hours at the time of the accident. The engine manufacturer's maintenance schedule specified that an engine overhaul be completed every 5 years or 300 hours, whichever comes first. At the time of the accident, the engine was about 7 weeks beyond the 5-year overhaul limit. About 100 hours time-in-service had elapsed since the overhaul in 2014. An aircraft owner is not required comply with the engine manufacturer's recommended overhaul interval when operating under Part 91 unless the engine does not meet the requirements of a condition inspection.
Aircraft
- Registration
- N582L
- Reported as
- Griff Challenger (II)
- Category
- Airplane, amateur-built
- Serial number
- CH2-0708-LSS-LW
- Built
- 2010
- Airframe hours
- 176
- Engine
- Rotax 582, 65 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Special, Experimental (Special)
- Last inspection
- Condition · August 15, 2018 · 46 hours before
- Departed
- 1I3 · Bloomfield, IN
- Destination
- 1I3 · Bloomfield, IN
- Equipment
- Handheld GPS
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 52
- Injuries
- Serious
- Certificate
- Student
- Last flight review
- March 23, 2019
- Seat
- Front
- Restraint
- 4-point
- Flight hours
- 124 total · 76 in this make and model · 11 in the last 90 days · 4 in the last 30 days · 2 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 10 statute miles
- Temperature
- 61 °F, dew point 55 °F
- Altimeter
- 30.11 inHg
- Observed at
- BMG, 21 nm away
Docket · 5
The files NTSB released with the investigation on February 28, 2020, on NTSB’s docket system: statements, records, photos and specialists’ reports. 5.5 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.