WPR14CA116

NTSB accident investigation · Cessna 172 - N · Glendale, AZ · February 15, 2014

Accident · No injuriesData collectionFinal report
Date
February 15, 2014, 15:40 local (22:40 UTC)
Place
Glendale, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N738BHCessna 172 - N
Defining event
Landing-landing roll: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report April 23, 2014
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA
FAA report
20140215002169A
Case key
88816

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 pilot's failure to maintain control of the airplane during the landing roll, which resulted in a runway excursion and subsequent impact with a taxiway sign.

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: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172N: 82 casesAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 172N: 150 casesAll aircraft: 9,295 casesProbable cause
Object/animal/substance: sign/markerEnvironmental issues › Physical environment · Contributed to outcomeCessna 172N: 7 casesAll aircraft: 214 cases

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

After touching down the airplane veered to the left. The pilot added right rudder to correct back to the centerline, however, it continued toward the right side of the runway. The airplane subsequently went off of the runway and impacted a taxiway sign, which resulted in substantial damage to the rear right wing spar. A postaccident examination of the airplane by a Federal Aviation Administration aviation safety inspector revealed no preimpact anomalies that would have precluded normal operation.

Factual narrative

After touching down the airplane veered to the left. The pilot added right rudder to correct back to the centerline, however, it continued toward the right side of the runway. The airplane subsequently went off of the runway and impacted a taxiway sign, which resulted in substantial damage to the rear right wing spar. A postaccident examination of the airplane by a Federal Aviation Administration aviation safety inspector revealed no preimpact anomalies that would have precluded normal operation.

Aircraft

Registration
N738BH
Reported as
Cessna 172 - N (N)
Category
Airplane
Serial number
17269845
Built
1977
Airframe hours
9,265
Engine
Lycoming O-320, 165 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · November 27, 2013 · 47 hours before
Departed
GEU · Glendale, AZ
Destination
GEU · Glendale, AZ
Airport
GEU · Glendale, runway 19, 7,150 × 100 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
35
Injuries
None
Certificate
Student
Medical
Class 3, With waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
36 total · 36 in this make and model · 4 as pilot in command · 36 in the last 90 days · 9 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Variable at 4 knots
Visibility
20 statute miles
Lowest ceiling
25,000 ft broken
Temperature
82 °F, dew point 34 °F
Altimeter
29.97 inHg
Observed at
GEU

Docket · 3

The files NTSB released with the investigation on April 15, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.3 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.