ERA17CA216 · Cessna 172 R
Epix Services Cessna 172 R · Accident: abnormal runway contact during landing
From Plymouth Municipal Airport (PMZ) to Emporia Greensville Regional Airport (EMV)
Event
- NTSB case
- ERA17CA216
- 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 R
- 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
- N2460A
- Operator
- Epix Services
- Onboard fatalities
- Unknown
- Route
- From Plymouth Municipal Airport (PMZ), Plymouth, NCTo Emporia Greensville Regional Airport (EMV), Emporia, VA
- Aircraft age
- About 17 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
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that the flight was his first solo cross-country, and the arrival and departure at his first airport were uneventful. About 8 miles from the second airport, he listened to the airport's automatic weather observation system, which reported that the wind was coming from 020° at 5 knots. He entered the left traffic pattern for runway 34, and while on the downwind leg abeam the end of the runway, he reduced engine power to idle and lowered the wing flaps to 10°. He then turned onto the left base leg and maintained 70 knots and lowered the wing flaps to 30° on final approach, maintaining an airspeed of "between 50 and 54 knots." At the runway numbers, he began to pull back on the control wheel to initiate the landing flare. The airplane's nose then abruptly pitched up and left, which he believed felt like a wind gust. He tried to correct by releasing back pressure on the control wheel and using rudder and ailerons to move back to the right, but the airplane was still left of the runway centerline. Subsequently, the airplane bounced hard numerous times, the propeller struck the runway, and the airplane then departed the runway to the left. During the runway excursion, the nose landing gear collapsed, and the airplane skidded across a taxiway, eventually stopping in the grass. The fuselage and firewall were substantially damaged.
The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Review of the Pilot's Operating Handbook indicated that the airspeed for a normal landing should have been between 60 and 70 knots with the wing flaps down.
Probable cause
The student pilot's failure to maintain an adequate airspeed for landing and his improper landing flare and recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17CA216
- Event ID
- 20170628X73152
- Case number
- ERA17CA216
- 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: f1a2a0d5cecb12639f66ae78f5147854d56358d58e533ee4dcecc85b387d46df; retrieved 2026-09-16T05:28:09.491Z.