CHI07CA245 · Cessna 172N
Oakland Flight Service Cessna 172N · Accident: hard landing
From Livingston County Spencer J. Hardy Airport (OZW) to Oakland Southwest Airport (Y47)
Event
- NTSB case
- CHI07CA245
- 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 172N
- 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
- N222UN
- Operator
- Oakland Flight Service
- Onboard fatalities
- Unknown
- Route
- From Livingston County Spencer J. Hardy Airport (OZW), Howell, MITo Oakland Southwest Airport (Y47), New Hudson, 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 · 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 › Flare, improper
- Pilot in command › Recovery from bounced landing, inadequate
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 made a bounced landing on runway 7. The student pilot stated that while on approach the airplane was "a bit high and fast." The student pilot reduced engine power and "felt" that it was "still ok to land." She reported that the airplane touched down and bounced hard twice. The airplane was now past midfield and the student pilot was not confident that the airplane could clear the trees at the end of the runway. Concerned that the next hard bounce could damage the gear and the airplane, the pilot steered the airplane off the runway onto the grass, attempted to maintain control as long as possible, and impacted bushes. The pilot reported that there were no mechanical anomalies with the airplane.
Probable cause
The student pilot's improper flare, which resulted in a hard landing. An additional cause was the pilot's inadequate recovery from a bounced landing. Factors in the accident include the pilot's failure to maintain directional control during the landing roll and the bushes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA245
- Event ID
- 20070823X01228
- Case number
- CHI07CA245
- 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: 7712b943f0466f7d763c1872217654c3e563d414c086b02093e48fcaa92c40d0; retrieved 2026-09-22T03:35:32.836Z.