ERA15CA150 · Cessna 172S
AV-ED Flight School Cessna 172S · Accident: hard landing
From Culpeper Regional Airport (CJR) to Richmond International Airport (RIC)
Event
- NTSB case
- ERA15CA150
- 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
- N144ME
- Operator
- AV-ED Flight School
- Onboard fatalities
- Unknown
- Route
- From Culpeper Regional Airport (CJR), Culpeper, VATo Richmond International Airport (RIC), Richmond, VA
- Aircraft age
- About 15 years (built 2000)
- 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
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a full stop landing at an airport on the second leg of a multiple leg cross country flight, the student pilot landed, the airplane bounced, and then touched down again, hard on the nose landing gear. The student pilot then lost directional control, the airplane drifted towards the left side of the runway, and then came to rest. Examination of the airplane by a Federal Aviation Administration inspector revealed that the airplane had incurred substantial damage. The tip of one propeller blade was bent, the nose wheel landing gear tire was flat, the cabin floor was wrinkled, the belly skin of the fuselage was wrinkled, and the firewall was buckled. The student pilot was uninjured, and he advised that he had no mechanical problems prior to the accident.
Probable cause
The student pilot's inadequate landing flare which resulted in a hard landing and substantial damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15CA150
- Event ID
- 20150310X83524
- Case number
- ERA15CA150
- 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: afd3be9c5954cd668e8980c7102559d6975d7b225d81f7e4c9429438ebbf9959; retrieved 2026-09-16T02:08:23.426Z.