- Date
- June 28, 2014, 12:00 local (19:00 UTC)
- Place
- Mesa, AZ
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N3069QCessna 182K
- Defining event
- Landing-flare/touchdown: Abnormal runway contact
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 5, 2014
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20140628016259A
- Case key
- 90081
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 inadequate landing flare which resulted in a loss of aircraft control and hard 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 stated that the purpose of the solo flight was to perform maneuvers in the local practice area in preparation for an upcoming checkride. After performing a series of maneuvers, the pilot returned to the airport and was cleared to land on the active runway. The pilot noted that during the landing flare she realized the airspeed was higher than desired and responded by manipulating the throttle control. During the landing, the airplane touched down hard and bounced back airborne. The airplane continued to bounce down the runway about 3 to 4 times before coming to a stop. As a result of the impact, the airplane incurred substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Factual narrative
The student pilot stated that the purpose of the solo flight was to perform maneuvers in the local practice area in preparation for an upcoming checkride. After performing a series of maneuvers, the pilot returned to the airport and was cleared to land on the active runway. The pilot noted that during the landing flare she realized the airspeed was higher than desired and responded by manipulating the throttle control. During the landing, the airplane touched down hard and bounced back airborne. The airplane continued to bounce down the runway about 3 to 4 times before coming to a stop. As a result of the impact, the airplane incurred substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Aircraft
- Registration
- N3069Q
- Reported as
- Cessna 182K (K)
- Category
- Airplane
- Serial number
- 18258069
- Built
- 1967
- Engine
- Cont Motor O-470 SERIES, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · March 30, 2014
- Departed
- FFZ · Mesa, AZ
- Destination
- FFZ · Mesa, AZ
- Airport
- FFZ · Falcon Fld, runway 22R, 3,799 × 75 ft, asphalt
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
- 39
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3, Without waivers/limitations
- Seat
- Left
- Flight hours
- 98 total · 57 in this make and model · 11 as pilot in command · 40 in the last 90 days · 12 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 170° at 5 knots
- Visibility
- 40 statute miles
- Lowest ceiling
- None
- Temperature
- 97 °F, dew point 46 °F
- Altimeter
- 29.81 inHg
- Observed at
- FFZ
Docket · 1
The files NTSB released with the investigation on November 20, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 544 KB 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 N3069Q · 1
Matched to the same aircraft by N-number and date.