CHI07CA132 · Cessna 172P
Cessna 172P · Accident: hard landing
From Southern Wisconsin Regional Airport (JVL) to Kenosha Regional Airport (ENW)
Event
- NTSB case
- CHI07CA132
- 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
- Unknown
- 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 172P
- 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
- N97464
- Operator
- Ameriflyers
- Onboard fatalities
- Unknown
- Route
- From Southern Wisconsin Regional Airport (JVL), Janesville, WITo Kenosha Regional Airport (ENW), Kenosha, 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was substantially damaged during a bounced landing. The pilot stated that when he was on final, he noticed he was too high so he began to slip the airplane. As he started his flare, he noticed he was still too high and decided to reduce the power to idle. The airplane bounced, became airborne, and bounced again. He kept the flare going and touched down again, finally staying on the ground. He taxied the airplane to the ramp for parking, shut down the airplane, and discovered the nose wheel tire was flat.
Probable cause
The pilot's improper recovery from a bounced landing, which resulted in a flat nose wheel tire and a buckled firewall. A factor was the porpoising that was encountered during the flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA132
- Event ID
- 20070606X00683
- Case number
- CHI07CA132
- 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, coordinates. 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: 1986d3e7b7881fe2b634e4622ef143cae0a0e68535250fb71532cb5453a88234; retrieved 2026-09-22T03:50:42.016Z.