CHI90LA010 · Cessna 172M
Cessna 172M · Accident: in flight collision with object on approach
From Lawrence J Timmerman Airport (MWC) to Lawrence J Timmerman Airport (MWC)
Event
- NTSB case
- CHI90LA010
- 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 172M
- Aircraft type
- Cessna 172
- 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
- N1325U
- Operator
- Nack, James W. · private individual
- Onboard fatalities
- Unknown
- Route
- From Lawrence J Timmerman Airport (MWC), Milwaukee, WITo Lawrence J Timmerman Airport (MWC)
- 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 go-around
- 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
- In flight collision with object
- 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
- Wire, transmission
- 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(cfi) › Airspeed, not obtained
- Pilot in command(cfi) › Go-around, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DRG AN INSTRUCTIONAL FLT, AN EMERGENCY LANDING TO AN ARPT WAS DEMONSTRATED, SIMULATING AN ENG FAILURE. THE INSTRUCTOR (CFI) RPRTD THAT DRG A SUBSEQUENT GO-AROUND, THE ACFT FAILED TO FLY OUT OF GROUND EFFECT BEFORE REACHING A CORN FIELD AT THE END OF THE RWY. THE ACFT BEGAN TO SETTLE OVER THE CORN FIELD AS IT WAS APCHG POWER LINES. REALIZING THE ACFT WOULD NOT CLIMB OVER THE POWER LINES, THE CFI OPTED TO FLY UNDER THE WIRES. HOWEVER, THE TOP OF THE VERTICAL STABILIZER CONTACTED & SEVERED THE LOWERMOST WIRE. THE ACFT THEN CONTACTED THE GROUND, BOUNCED, SETTLED IN A LOT WITH TALL WEEDS & NOSED OVER. NO PREIMPACT ANOMALIES WERE FOUND IN THE AIRFRAME OR ENG THAT WOULD HAVE CONTRIBUTED TO THE OCCURRENCE.
Probable cause
DELAY OF THE FLIGHT INSTRUCTOR (CFI) IN MAKING A GO-AROUND AND HIS FAILURE TO ATTAIN SUFFICIENT AIRSPEED TO CLIMB AFTER TAKING OFF AGAIN. THE TRANSMISSION WIRE (POWER LINE) AND HIGH VEGETATION WERE CONTRIBUTING FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA010
- Event ID
- 20001213X29563
- Case number
- CHI90LA010
- 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: 582571638596ddd544b7790284e395d168131cc9c069c5c851a9485b22245e60; retrieved 2026-09-23T07:04:02.408Z.