ERA13CA185

NTSB accident investigation · Cessna 172N · Bally, PA · March 30, 2013

Accident · No injuriesData collectionFinal report
Date
March 30, 2013, 13:15 local (17:15 UTC)
Place
Bally, PA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4601DCessna 172N
Defining event
Takeoff: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report June 4, 2013
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20130330004879A
Case key
86552

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 directional control during the takeoff roll.

Findings · 2

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 · PilotCessna 172N: 150 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172N: 82 casesAll aircraft: 3,958 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 pilot reported that he was departing on runway 34 with three passengers and that he had conducted an engine run-up before takeoff and all systems were working properly. He taxied the airplane onto the runway and initiated the takeoff roll. As he pulled back the control yoke, the airplane began to drift to the left, and he was unable to correct the drift. He did not regain control of the airplane, and it exited the runway. The airplane rolled into a grove of pine trees and sustained substantial damage to the tail section and right wing. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Factual narrative

The pilot reported that he was departing on runway 34 with three passengers. He said that he conducted an engine run-up prior to takeoff and all systems were working properly. He taxied the airplane onto the runway and initiated the takeoff roll. As he pulled back the control yoke, the airplane began to drift to the left, and he was unable to correct the drift. He did not regain control of the airplane and it exited the runway. The airplane rolled into a grove of pine trees, and sustained substantial damage to the tail section and right wing. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Aircraft

Registration
N4601D
Reported as
Cessna 172N
Category
Airplane
Serial number
17272312
Airframe hours
8,730
Engine
Lycoming O-360-A4M, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Aero-Tech Services
Registered owner
Aero-Tech Services
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · March 20, 2013 · 16 hours before
Departed
7N8 · Bally, PA
Destination
LNS · Lancaster, PA
Airport
7N8 · Butter Valley Airport, runway 34, 2,420 × 85 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
Pilot
Age
23
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
March 14, 2013
Seat
Left
Flight hours
48 total · 48 in this make and model · 10 as pilot in command · 9 in the last 90 days · 4 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
270° at 11 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
54 °F, dew point 3 °F
Altimeter
30.17 inHg
Observed at
LNS

Docket · 3

The files NTSB released with the investigation on May 10, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.2 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.