ERA09CA061 · Cessna 172 M
Richards Flight Training Cessna 172 M · Accident: hard landing
From Fort Lauderdale Executive Airport (FXE) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- ERA09CA061
- 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 172 M
- 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
- N12236
- Operator
- Richards Flight Training
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Ft. Lauderdale, FLTo Fort Lauderdale Executive Airport (FXE), Ft. Lauderdale, FL
- 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
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After departing the airport, the student pilot of the Cessna 172M flew with his flight instructor to a fixed location and returned to the airport. The student pilot and his instructor landed at the airport without incident and the flight instructor exited the airplane. The student pilot retrieved the current weather information and departed the airport again. This was the student pilot's third supervised solo flight. He flew back to the fixed location and turned back to the airport. The air traffic control tower cleared him to land. He said the approach seemed “normal.” The airplane touched down, then bounced once, possibly twice. During the bounced landing, the nose gear hit the runway hard. The nose wheel collapsed and the airplane “slid” from the center of the runway to the left edge before coming to a stop.
Probable cause
The student pilot's improper flare during landing. Contributing to the accident was the student pilot's lack of experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA061
- Event ID
- 20081118X10433
- Case number
- ERA09CA061
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 50a243f904900611a04387e00e1d4b0b09c1718c4472b50de83f52df5b282c2c; retrieved 2026-09-15T10:33:33.987Z.