CEN24LA379 · Textron Aviation Inc 172S
Textron Aviation Inc 172S · Accident: abnormal runway contact during landing
Event
- NTSB case
- CEN24LA379
- 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
Textron Aviation Inc 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
- N281EA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 1 year (built 2023)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the student pilot’s second instructional flight, he performed an uneventful touch and go landing. When the student was on final for his second touch and go landing, about 25 ft above the runway, he initiated an early flare and pitched the airplane down which led to a sharp descent toward the runway. The airplane landed hard and bounced on the runway. The flight instructor took the controls and initiated a go-around. The flight instructor assisted the student on one more touch and go landing, then made a full stop landing. During a post-flight inspection, substantial damage (buckling) was found on the underside of the empennage and the firewall. The flight instructor reported that the accident could have been prevented by initiating a go around earlier. No mechanical malfunctions or failures with the airplane were reported.
Probable cause
The student pilot’s improper flare and the flight instructor’s delayed remedial action that resulted in a hard, bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA379
- Event ID
- 20241001195235
- Case number
- CEN24LA379
- 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, cause areas. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: d552d4d2b0ab25a04e4c5947effae1572914302b42d446b8f556439cb1bb3dfa; retrieved 2026-09-16T19:20:30.808Z.