GAA17CA546

NTSB accident investigation · Cessna 150 · Siler City, NC · September 20, 2017

Accident · No injuriesData collectionFinal report
Date
September 20, 2017, 15:30 local (19:30 UTC)
Place
Siler City, NC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N6250TCessna 150
Defining event
Takeoff: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed · report April 23, 2018
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20170920020849A
Case key
96054

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 improper decision to take off with known electrical issues, which distracted him and led to a loss of directional control during the takeoff roll.

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 · PilotCessna 150E: 3 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 150E: 1 caseAll 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

According to the pilot, during a time-building, cross-country flight, the airplane had multiple mechanical malfunctions. On the fourth leg of the flight, he departed the airport and noticed that the airplane was low on fuel. He flew to a nearby airport, landed, and added 10 gallons of fuel. After fueling, the airplane would not start, and the pilot asked maintenance personnel to jump the airplane's battery. Then, during taxi to the runway, he noticed that the "radios and other electronics" were inoperative, but he continued to the runway. During the takeoff roll, he was startled by a loud noise in his headset, which he believed came from the airplane's communication radio. He attempted to assess the problem during the takeoff roll, and the airplane veered off the right side of the runway into the safety area. After regaining control, he taxied back to the approach end of the runway. He performed a flight control check and an engine power check and departed the airport. The pilot reported that he then landed at a nontowered airport "to check out the aircraft." He performed another flight control check and an engine run-up but did not exit the airplane "because of the starting issue." The pilot then departed for the destination airport. He reported that he landed the airplane and taxied to parking. He recalled that he performed a postflight check of the airplane, but "other than grass and grass stains [he] did not see any damage." Later that evening, the airplane's owner informed the pilot that the left wing was damaged. The airplane sustained substantial damage to the left-wing spar and aileron.

Factual narrative

According to the pilot, during a time building cross-country flight, the airplane had multiple mechanical malfunctions. On the fourth leg of the flight, he departed the airport and noticed that the airplane was low on fuel. He flew to a nearby airport, landed, and added 10 gallons of fuel. After fueling, the airplane would not start, and he asked a maintenance shop to jump the airplane's battery. Then, during taxi to the runway, he noticed that the "radios and other electronics" were inoperative, but he continued to the runway. During the takeoff roll, he was startled by a loud noise in his headset, which he believed came from the airplane's communication radio. He attempted to assess the problem during the takeoff roll and the airplane veered off the right side of the runway into the safety area. After regaining control, he taxied back to the approach end of the runway. He performed a flight control check and an engine power check and departed the airport. The pilot reported that he then landed at a non-towered airport "to check out the aircraft". He performed another flight control check and an engine run-up but did not exit the airplane "because of the starting issue." The pilot then departed for the destination airport. He reported that he landed the airplane and taxied to parking. He recalled that he performed a post-flight check of the airplane, but "other than grass and grass stains [he] did not see any damage". Later that evening, the owner of the airplane informed the pilot that the left wing was damaged. The airplane sustained substantial damage to the left-wing spar and aileron.

Aircraft

Registration
N6250T
Reported as
Cessna 150 (E)
Category
Airplane
Serial number
15060950
Built
1964
Airframe hours
6,162
Engine
Cont Motor O-200 SERIES, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 26, 2017
Departed
EXX · Lexington, NC
Destination
EXX · Lexington, NC
Flight plan
VFR
Airport
SCR · Siler City Muni, runway 04, 5,000 × 75 ft, asphalt
Equipment
ADS-B

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
67
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
December 27, 2016
Seat
Left
Restraint
3-point
Flight hours
147 total · 7 in this make and model · 43 as pilot in command · 5 in the last 90 days · 3 in the last 30 days · 2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
250° at 7 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
86 °F, dew point 64 °F
Altimeter
30.00 inHg
Observed at
KHBI, 19 nm away

Docket · 2

The files NTSB released with the investigation on March 27, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.9 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.