MIA03CA148 · Cessna 172S
Cessna 172S · Accident: hard landing
From Olive Branch Airport (OLV) to Olive Branch Airport (OLV)
Event
- NTSB case
- MIA03CA148
- 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
- N970SP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Olive Branch Airport (OLV), Olive Branch, MSTo Olive Branch Airport (OLV)
- 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 student pilot stated that as he approached the runway to perform the landing flare/touchdown he reduced engine power and applied back pressure to the control yoke until the main landing gear touched the runway. He said as he continued to apply back pressure after having touched down, the airplane became airborne again, so he relaxed back pressure to flare again, but upon touching the ground the airplane bounced back into the air. He said there were additional attempts to perform the landing flare, but each time successive bounces occurred. During the last attempt, the student said he added a small amount of power in an attempt to recover and the airplane first impacted on its main landing gear, then it "abruptly" impacted on the nose gear as well. The airplane then leaned forward, and remained on the ground, while at a speed of about 20 knots, incurring damage to the propeller, nose gear and firewall. According to the student, prior to the accident there were no mechanical failures or malfunctions to the airplane or any of its systems.
Probable cause
The student pilot's improper landing flare/touchdown and inadequate recovery from a bounced landing which resulted in a hard landing and damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03CA148
- Event ID
- 20030911X01516
- Case number
- MIA03CA148
- 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: 3e07626397598a0de5730764ae4c2484fdc1caac1c5d0384ebc83a478ae4c9f1; retrieved 2026-09-22T08:53:51.114Z.