CHI93LA166 · Cessna 175
Cessna 175 · Accident: partial loss of engine power (mechanical failure) en route
From MBS International Airport (MBS) to an unrecorded destination
Event
- NTSB case
- CHI93LA166
- 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 175
- 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
- N7303M
- Operator
- Frederick H. Herman · private individual
- Onboard fatalities
- Unknown
- Route
- From MBS International Airport (MBS), Saginaw, 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
- Partial loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Operation with known deficiencies in equipment, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A NIGHT VFR CROSS COUNTRY FLIGHT THE PILOT REPORTED HE EXPERIENCED AN ENGINE POWER LOSS. HE STATED HE LANDED AT A NEARBY AIRPORT AND SOUGHT A MECHANIC'S HELP. THE COST OF THE MECHANIC WAS PROHIBITIVE AND THE PILOT ATTEMPTED TO DETERMINE THE PROBLEM. HE STATED HE EXAMINED THE ENGINE VISUALLY AND FOUND NOTHING UNUSUAL. HE STATED HE RAN THE ENGINE FOR 20 MINUTES AT VARIOUS RPM SETTINGS. UPON COMPLETION OF THE RUNUP THE PILOT DEPARTED AND CONTINUED HIS CROSS COUNTRY FLIGHT. WHILE AT CRUISE THE ENGINE BEGAN TO LOSE POWER. REMEDIAL ACTION BY THE PILOT DID NOT CORRECT THE POWER LOSS. THE AIRPLANE COLLIDED WITH TREES AND SWAMPY TERRAIN. THE ON-SCENE INVESTIGATION IDENTIFIED AN INTERMITTENTLY FIRING LEFT MAGNETO.
Probable cause
THE PILOT OPERATING THE AIRPLANE WITH A KNOWN DEFICIENCY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA166
- Event ID
- 20001211X12350
- Case number
- CHI93LA166
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1993-05-09.
- API snapshot SHA-256: d78d07f003561c13ae52463cf7c2bde52923b86cfb3bc8b980f6ae1e161d29c4; retrieved 2026-09-21T22:57:38.438Z.