ERA14CA169

NTSB accident investigation · Cessna 172M · Knoxville, TN · March 23, 2014

Accident · No injuriesData collectionFinal report
Date
March 23, 2014, 15:30 local (19:30 UTC)
Place
Knoxville, TN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8893VCessna 172M
Defining event
Takeoff: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report July 30, 2014
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
FAA report
20140323002709A
Case key
88965

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 directional control during the takeoff roll, which resulted in a collision with an obstacle.

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.

Use of equip/info: aircraft controlPersonnel issues › Task performance · Student/instructed pilotCessna 172M: 123 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172M: 59 casesAll aircraft: 3,958 casesProbable cause
Object/animal/substance: poleEnvironmental issues › Physical environment · Contributed to outcomeCessna 172M: 4 casesAll aircraft: 142 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

According to the student pilot, during the takeoff roll the airplane began to veer to the left after approximately 225 feet. The student pilot applied right rudder and reduced power in an attempt to regain control of the airplane. The airplane continued off of the runway and collided with a pole, resulting in substantial damage to the left wing. The pilot did not report any mechanical anomalies that would have precluded normal operation prior to the accident.

Factual narrative

According to the student pilot, during the takeoff roll the airplane began to veer to the left after approximately 225 feet. The student pilot applied right rudder and reduced power in an attempt to regain control of the airplane. The airplane continued off of the runway and collided with a pole, resulting in substantial damage to the left wing. The pilot did not report any mechanical anomalies that would have precluded normal operation prior to the accident.

Aircraft

Registration
N8893V
Reported as
Cessna 172M
Category
Airplane
Serial number
17264251
Built
1974
Airframe hours
6,899
Engine
Lycoming 0-320 SERIES, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
East Tennessee Pilots Club
Registered owner
East Tennessee Pilots Club
Airworthiness certificate
Standard, Normal; Standard, Utility
Last inspection
100 hour · March 7, 2014 · 40 hours before
Departed
TN98 · Knoxville, TN
Destination
TN98 · Knoxville, TN
Airport
TN98 · Sky Ranch, runway 19, 2,100 × 150 ft, grass/turf
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
45
Injuries
None
Certificate
Student
Medical
Class 3, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
32 total · 32 in this make and model · 2 as pilot in command · 32 in the last 90 days · 17 in the last 30 days · 2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
350° at 9 knots, gusting 15
Visibility
10 statute miles
Lowest ceiling
None
Temperature
54 °F, dew point 36 °F
Altimeter
30.10 inHg
Observed at
TYS, 4 nm away

Docket · 5

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