CHI92LA226 · Cessna 175A
Cessna 175A · Accident: total loss of engine power (non-mechanical) en route
From 5G9 · OTTAWA LAKE, MI to an unrecorded destination
Event
- NTSB case
- CHI92LA226
- 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
- 0
- 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
Cessna 175A
- Aircraft type
- Cessna 175
- 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
- N6853E
- Operator
- Conroy, Robert J. · private individual
- Onboard fatalities
- Unknown
- Route
- From 5G9 · OTTAWA LAKE, MITo not recorded
- Aircraft age
- Not recorded
- 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 · cruise
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- Pilot in command › Aircraft preflight, inadequate
Approximate · Estimated position: the centre of East Lansing, MI, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED HE WAS IN CRUISE FLIGHT AT 3,000 FEET WHEN THE ENGINE BEGAN TO RUN ROUGH AND HE NOTED A DROP IN OIL PRESSURE. HE PERFORMED A FORCED LANDING ON A GRASS AIRSTRIP AT AN UNCONTROLLED AIRPORT. THE AIRPLANE RAN OFF THE DEPARTURE END OF THE RUNWAY, ACROSS A ROAD AND CAME TO REST INVERTED IN A DITCH. POST-ACCIDENT EXAMINATION OF THE WRECKAGE REVEALED THE PRESENCE OF ENGINE OIL ALL OVER THE WINGS, TAIL SECTION, AND THE SIDES AND BOTTOM OF THE FUSELAGE. THE OIL FILLER CAP WAS LOOSE IN THE ENGINE COMPARTMENT, ATTACHED BY ITS CHAIN.
Probable cause
THE PILOT'S INADEQUATE PREFLIGHT INSPECTION OF THE AIRCRAFT WHICH RESULTED IN A LOSS OF ENGINE POWER DURING CRUISE FLIGHT. RELATED FACTORS ARE THE LOOSE OIL FILLER CAP, AND THE SHORT, WET GRASS STRIP USED FOR THE EMERGENCY LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA226
- Event ID
- 20001211X15352
- Case number
- CHI92LA226
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: a618c47ac57291da9e3207943741a58a3b0bfe527ad37674ae1d206ad799338f; retrieved 2026-09-21T14:49:20.779Z.