CEN19LA163 · Griff Challenger II
Griff Challenger II · Accident: loss of engine power (total) en route
From Shawnee Field (1I3) to Shawnee Field (1I3)
Event
- NTSB case
- CEN19LA163
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Griff Challenger II
- Aircraft type
- Griff CHALLENGER
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N582L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Shawnee Field (1I3), Bloomfield, INTo Shawnee Field (1I3), Bloomfield, IN
- Aircraft age
- About 9 years (built 2010)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA163
- Event ID
- 20190612X11148
- Case number
- CEN19LA163
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 9e2e11e35aac59bb0171f262342057a0d2340b776c9836c3052b35e8e4654386; retrieved 2026-09-16T09:15:21.830Z.