GAA16CA187

NTSB accident investigation · Cessna 172 · Scottsdale, AZ · March 6, 2016

Accident · No injuriesData collectionFinal report
Date
March 6, 2016, 09:45 local (16:45 UTC)
Place
Scottsdale, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6023VCessna 172
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report June 15, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160306024339A
Case key
92994

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 failure of the student pilot to maintain pitch control while landing, which resulted in a hard landing, loss of directional control, and runway excursion.

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.

Performance/control parameters: pitch controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172S: 26 casesAll aircraft: 526 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172S: 66 casesAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · Student/instructed pilotCessna 172S: 206 casesAll aircraft: 9,295 casesProbable cause

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 solo student pilot reported that the airplane bounced after touched down, then veered off the runway to the left and came to a stop in gravel. A postaccident exam revealed substantial damage to the firewall. According to the student pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Factual narrative

The solo student pilot reported that the airplane bounced after touched down, then veered off the runway to the left and came to a stop in gravel. A postaccident exam revealed substantial damage to the firewall. According to the student pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Aircraft

Registration
N6023V
Reported as
Cessna 172 (S)
Category
Airplane
Serial number
172S10198
Built
2006
Engine
Lycoming IO-360-L2A, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Sawyer Aviation
Registered owner
Sawyer Aviation
Airworthiness certificate
Standard, Normal
Departed
SDL · Scottsdale, AZ
Destination
SDL · Scottsdale, AZ
Airport
SDL · Scottsdale, runway 03, 8,249 × 100 ft, asphalt
Equipment
Electronic multifunction display

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
Pilot
Age
35
Injuries
None
Certificate
Student
Medical
Class 3, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
11 total · 11 in this make and model · 11 in the last 90 days · 1.5 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
140° at 7 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
70 °F, dew point 27 °F
Altimeter
29.95 inHg
Observed at
KSDL

Docket · 2

The files NTSB released with the investigation on May 31, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 628 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 N6023V · 1

Matched to the same aircraft by N-number and date.