CHI93LA005 · Univair 415C
Carter Aero Club Univair 415C · Accident: total loss of engine power (non-mechanical) en route
From CGX · Chicago, IL to Carter Airport (92C)
Event
- NTSB case
- CHI93LA005
- 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
Univair 415C
- Aircraft type
- Univair 415
- 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
- N99256
- Operator
- Carter Aero Club
- Onboard fatalities
- Unknown
- Route
- From CGX · Chicago, ILTo Carter Airport (92C), Pulaski, WI
- 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)
- 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
- Fuel starvation
- 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 › Emergency procedure, misjudged
- Pilot in command › Remedial action, inadequate
Approximate · Estimated position: the centre of Waukesha, WI, the place the record names. Not the accident site.
NTSB narrative
THE PILOT WAS NEARING A CONTROLLED AIRPORT AT 3000' AGL WHEN THE ENGINE BEGIN TO LOSE POWER. THE ENGINE SOON QUIT, AND THE PILOT MADE AN APPROACH TO RUNWAY 36. HE MISJUDGED HIS APPROACH, OVERSHOT FINAL APPROACH, AND LANDED IN SOFT TERRAIN ADJACENT TO RUNWAY 36. AN EXAMINATION OF THE AIRPLANE AND ENGINE DISCLOSED NO PREIMPACT MECHANICAL DEFICIENCIES. THE MAIN FUSELAGE FUEL TANK WAS EMPTY OF USABLE FUEL. THE WING TANKS WERE NEARLY FULL, BUT THE SELECTOR SWITCH WHICH CONTROLS THE FUEL FLOW FROM THE WING TANKS TO THE FUSELAGE TANK WAS FOUND IN THE 'OFF' POSITION.
Probable cause
THE PILOT'S INADEQUATE REMEDIAL ACTIONS AND HIS MISJUDGED EMERGENCY PROCEDURE (APPROACH TO LANDING).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA005
- Event ID
- 20001211X15831
- Case number
- CHI93LA005
- 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: 3aae5c990fed60c7cd81488b03b62b56dfe8533d0914a07c388ebd6054a22d4d; retrieved 2026-09-21T23:06:32.258Z.