- Date
- June 28, 2017, 12:45 local (16:45 UTC)
- Place
- Emporia, VA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2460ACessna 172
- Defining event
- Landing-flare/touchdown: Abnormal runway contact
- Weather
- Visual (VMC) · Day
- Status
- Completed · report October 24, 2018
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA / FSDO
- FAA report
- 20170628009609A
- Case key
- 95458
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Factual narrative
The student pilot reported that the flight was his first solo cross-country, and the arrival and departure at his first airport was non-eventful. 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 a left base leg and maintained 70 knots, and lowered the wing flaps to 30° on final approach, maintaining an airspeed "between 50 and 54 knots". At the runway numbers he began to pull back on the control wheel to initiate the landing flare. The nose of the airplane then abruptly pitched up and to the left, which he believed felt like a gust of wind. 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 then departed the runway to the left. During the runway excursion, the nose landing gear collapsed and the airplane skid 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 airspeed for a normal landing should have been 60-70 knots with the wing flaps down.
Aircraft
- Registration
- N2460A
- Reported as
- Cessna 172 (R)
- Category
- Airplane
- Serial number
- 17280932
- Built
- 2000
- Airframe hours
- 8,033.6
- Engine
- Lycoming IO-360-L2A, 160 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- Epix Services LLC, doing business as Epix Aviation
- Registered owner
- Skydance Aviation LLC
- Airworthiness certificate
- Standard, Utility; Standard, Normal
- Last inspection
- 100 hour · June 5, 2017
- Departed
- PMZ · Plymouth, NC
- Destination
- EMV · Emporia, VA
- Airport
- EMV · Emporia-Greensville Rgnl, runway 34, 5,010 × 100 ft, asphalt
- Equipment
- Stall warning system
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Student pilot
- Age
- 56
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3
- Seat
- Left
- Restraint
- 3-point
- Flight hours
- 64 total · 43 in this make and model · 24 in the last 90 days · 24 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 230° at 3 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 77 °F, dew point 46 °F
- Altimeter
- 30.21 inHg
- Observed at
- EMV
Docket · 5
The files NTSB released with the investigation on September 17, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.9 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N2460A · 1
Matched to the same aircraft by N-number and date.