CHI05CA124 · Cessna 172S
Cessna 172S · Accident: hard landing
From Huron County Memorial Airport (BAX) to St Clair County International Airport (PHN)
Event
- NTSB case
- CHI05CA124
- 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 172S
- 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
- N860SA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Huron County Memorial Airport (BAX), Bad Axe, MITo St Clair County International Airport (PHN), Port Huron, MI
- 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
- 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 › Flare, misjudged
- Pilot in command › Go-around, not performed
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 piloted by a student pilot, sustained substantial damage during a hard landing on a runway 28. The pilot stated, "Upon turning base leg I determined that I was high and reduced power to idle. I maintained an airspeed of 65 [knots] and judged that I would touch down at the runway midpoint. At the midpoint I had not touched down and was still 30 to 50 [feet] above the runway. Instead of going around I attempted to land. In the process I rotated [too] soon and [too] much. This resulted in landing at a higher speed. I landed hard and bounced up. I maintained direction accurately and stopped the aircraft within the confines of the runway." Recorded wind at the airport was 310 degrees at 5 knots. The pilot reported no mechanical malfunctions with the airplane in reference to the flight.
Probable cause
The pilot not performing a go-around and misjudging the flare leading to a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA124
- Event ID
- 20050622X00832
- Case number
- CHI05CA124
- 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: 7dc94ff1d649f3a62d82d7cda45ccabbe35c51cfbc661b03f7de021585935fc6; retrieved 2026-09-22T05:53:27.918Z.