FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI90LA163 · Cessna U206

25 Jun 1990 · Savoy, IL, United States

Peoria Scanning Service Cessna U206 · Accident: loss of engine power on approach

From Mount Hawley Auxiliary Airport (3MY) to an unrecorded destination

Report a problem

Event

NTSB case
CHI90LA163
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 U206

Aircraft type
Cessna 206
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
N35703
Onboard fatalities
Unknown
Route
From Mount Hawley Auxiliary Airport (3MY), Peoria, ILTo 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
Approach · VFR pattern final
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
Loss of engine power
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
Stall
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 › Reason for occurrence undetermined
  • Pilot in command › Stall, inadvertent

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED THAT WHEN SHE REDUCED POWER DURING SHORT FINAL APPROACH FOR THE LANDING, THE ENGINE FAILED COMPLETELY. THE AIRCRAFT IMPACTED THE GROUND ABRUPTLY, APPROXIMATELY 200 FEET FROM THE APPROACH END OF THE LANDING RUNWAY, AND FLIPPED OVER, COMING TO REST INVERTED. POST-ACCIDENT INVESTIGATION REVEALED NO EVIDENCE OF MECHANICAL MALFUNCTION/DIFFICULTY WHICH WOULD HAVE RESULTED IN A LOSS OF ENGINE POWER, AND THE ENGINE STARTED AND RAN NORMALLY AT LOW POWER SETTINGS. THE ENGINE WAS RUN AT LOW POWER SETTINGS ONLY DUE TO DAMAGE TO THE PROPELLER, AND A BROKEN ENGINE MOUNT.

Probable cause

THE LOSS OF ENGINE POWER FOR UNDETERMINED REASONS AND THE INADVERTENT STALL DURING THE FORCED LANDING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI90LA163
Event ID
20001212X23369
Case number
CHI90LA163
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 1990-06-26.
  • API snapshot SHA-256: d5fad0be95acc1272b41492fd74691710b71dcac18acba9da75e3311cf0eb25c; retrieved 2026-09-21T23:50:42.260Z.