ERA13CA395 · Cessna 172S
Airborne Systems Cessna 172S · Accident: abnormal runway contact during landing
From Fort Lauderdale Executive Airport (FXE) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- ERA13CA395
- 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
- N6065P
- Operator
- Airborne Systems
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Fort Lauderdale Executive Airport (FXE), Fort 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot had flown with her instructor earlier that day and successfully performed about 5 takeoff’s and landings which included 1 go-around. She was then signed off for her first solo flight, and instructed to perform full stop taxi back landings. The student pilot stated that the flight departed and remained in the traffic pattern where on final approach she recognized the airplane was low. She applied power to level off, and noticed the airspeed was increasing so she, “…jerked the control stick.” The airplane contacted the runway, bounced, where she applied aft control, and was about to apply power but the airplane contacted the runway again causing the nose landing gear to collapse.
The student pilot’s certified flight instructor who was watching and listening on a portable VHF transceiver reported observing the airplane bounce twice, and the second bounce was higher than the first. He then lost sight of the airplane and heard the student pilot’s voice on the radio, followed by a comment from the controller that help was on the way.
The operator reported there was no mechanical failure or malfunction, and postaccident inspection of the flight controls by a Federal Aviation Administration airworthiness inspector revealed no evidence of preimpact failure or malfunction.
Probable cause
The student pilot’s failure to apply power to go-around following a bounced landing resulting in abnormal runway contact and collapse of the nose landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA395
- Event ID
- 20130904X95631
- Case number
- ERA13CA395
- 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: 3891265873d0ac27be177f0aa342746245e90f342dcaab8c01fce63573904da0; retrieved 2026-09-15T22:45:02.553Z.