CHI93LA243 · Cessna 150
Cessna 150 · Accident: loss of control in flight on approach
From Kenosha Regional Airport (ENW) to an unrecorded destination
Event
- NTSB case
- CHI93LA243
- 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 150
- Aircraft type
- Cessna 150
- 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
- N6097G
- Operator
- Schacht, Wilbur G. · private individual
- Onboard fatalities
- Unknown
- Route
- From Kenosha Regional Airport (ENW), Kenosha, WITo 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 turn to base
- 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 control in flight
- 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/spin
- 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 › Airspeed, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A WITNESS, WHO IS ALSO A PILOT, REPORTED SEEING N6097G DIRECTLY IN FRONT OF, BUT SOMEWHAT HIGHER THAN HIMSELF WHILE ENTERING THE LANDING PATTERN FOR BARNETT MEMORIAL AIRPORT TO THE SOUTHWEST OF RUNWAY 27. WHILE THE WITNESS WAS TRAVELING EAST ON THE DOWNWIND LEG, N6097G 'SWOOPED DOWN INTO THE PATTERN' INTO A POSITION TO THE LEFT AND SLIGHTLY BEHIND THE WITNESS' AIRCRAFT, ALSO ON THE DOWNWIND LEG. THE WITNESS REPORTED HEARING A VOICE ON THE RADIO SAY, 'BASE TO FINAL MT. MORRIS,' WHEN N6097G WAS EVEN WITH THE EAST END OF THE RUNWAY. THE WITNESS REPORTED THEN SEEING THE AIRPLANE MAKE A SHARP LEFT TURN AND STATED 'THE LEFT WING TIP 'STALLED' AND WENT DOWNWARD, PIVOTING ON THE LEFT WING TIP, TURNING AROUND 2-3 TIMES.' THEN, JUST PRIOR TO IMPACT WITH THE GROUND, THE PILOT APPEARED TO GAIN SOME CONTROL AS BOTH WINGS WERE LEVEL. POST ACCIDENT EXAMINATION REVEALED NO EVIDENCE OF PRE-IMPACT MECHANICAL MALFUNCTION WITH THE AIRFRAME, ENGINE, OR ACCESSORIES.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO MAINTAIN ADEQUATE AIRSPEED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA243
- Event ID
- 20001211X12834
- Case number
- CHI93LA243
- 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: a850786d3615cf2bcdc517d6c7ec6246c1130e1de9d37a78b410cae42a072fa2; retrieved 2026-09-21T14:18:57.220Z.