ERA09CA404 · Cessna 172 S
AV-ED Flight School Cessna 172 S · Accident: abnormal runway contact during landing
From Leesburg Executive Airport (JYO) to York Airport (THV)
Event
- NTSB case
- ERA09CA404
- 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 S
- 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 Leesburg Executive Airport (JYO), Leesburg, VATo York Airport (THV), York, PA
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the student pilot, the first landing attempt of the solo cross country flight resulted in a go-around. During his second attempt, the student pilot landed the airplane about one-third of the way down the 5,188-foot runway, "hard but smooth (not a bounce);" however, the airplane subsequently became airborne. The student pilot landed the airplane once more, and although he believed the “plane had safely and completely landed,” it became airborne yet again. At that point, the student pilot felt a go-around was not possible, and "pulled back" on the flight controls. The airplane then "probably stalled and dropped to the runway," the nose landing gear collapsed, and damage to the engine firewall and left wing resulted. Winds at the time were variable at 4 knots. No preaccident mechanical anomalies were noted by the student pilot.
Probable cause
The student pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA404
- Event ID
- 20090715X84357
- Case number
- ERA09CA404
- 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: 8a9cc88a4ed509b87fd7de00c1c7b0924829239de8c2f15703af473e71ad6a10; retrieved 2026-09-15T11:52:58.823Z.