LAX04LA124

NTSB accident investigation · Cessna 172N · Upland, CA · February 13, 2004

Accident · Minor injuriesLimited investigationFinal report
Date
February 13, 2004, 15:40 local (23:40 UTC)
Place
Upland, CA
Injuries
2 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N5107KCessna 172N
Weather
Visual (VMC) · Day
Status
Completed · report April 28, 2005
Report
Approved by Office Director
Parties
Federal Aviation Administration
FAA report
20040213002039A
Case key
58766

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

A partial loss of engine power for undetermined reasons during takeoff.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine powerTakeoff - initial climb
Reason for occurrence undeterminedUnknownCause
Forced landingEmergency landing after takeoff
OverrunLanding - roll
Terrain condition - runway
On ground/water collision with objectLanding - roll
Object - vehicle
Terrain condition - dirt bank/rising embankment

Analysis

The engine lost partial power just after the airplane lifted off the runway and the pilot aborted the takeoff and attempted to land on the remaining runway. The airplane touched down on the runway, overran its departure end, impacted a flatbed trailer, and came to rest on uneven terrain against a berm about 43 yards from the runway. The pilot reported that the airplane appeared to have been in proper working condition and worthy of flight during his preflight and pretakeoff inspections. However, after climbing for several seconds he heard the engine lose power, and its tachometer decreased to 1,400 rpm. The pilot believed that the airplane was not going to continue flying so he elected to abort the takeoff. To ascertain the reason for the power loss, the accident airplane's engine was removed from the airplane and installed on another airframe. After removing and replacing several impact-damaged engine accessories/components, the engine was run up to 2,400 rpm. With the exception of a minor vibration due to the fact that the crankshaft was bent, the engine operated normally. The reason for the partial engine power loss, as reported by the pilot, was not ascertained.

Factual narrative

On February 13, 2004, about 1540 Pacific standard time, a Cessna 172N, N5107K, experienced a partial loss of engine power during takeoff from runway 24 at the Cable Airport, Upland, California. The pilot aborted the takeoff and attempted to stop on the available runway. The airplane sustained substantial damage when it overran the runway's departure end, impacted a flatbed trailer, and came to rest on uneven terrain against a berm about 43 yards from the runway. Cable Air, Inc., operated the airplane. The private pilot and one passenger sustained minor injuries; the second passenger was not injured. Visual meteorological conditions prevailed, and no flight plan had been filed for the local area personal flight. The flight was performed under the provisions of 14 CFR Part 91, and it was originating at the time of the mishap.

In the pilot's completed "Aircraft Accident Report," NTSB Form 6120.1/2, he indicated that prior to taking off he performed a preflight inspection of the airplane. He performed a runup and determined that the airplane was in proper working condition and worthy of flight. During the takeoff roll, the pilot again observed that the engine instruments were still "looking good." However, after climbing for several seconds the pilot heard the engine lose power. According to the pilot, he observed that the engine's tachometer had decreased to 1,400 rpm, and he opined that the airplane was not going to continue flying. Therefore, he aborted the climb and lowered the wing flaps.

Cable Airport management personnel verbally reported to the National Transportation Safety Board investigator that skid marks were noted on the departure end of the runway leading to the accident airplane. There were about 156 feet of skid marks on the runway, which led to 128 feet of skid-like marks in the dirt.

Under the direction of the Safety Board investigator, the airplane was recovered from the accident site and was examined under Federal Aviation Administration (FAA) supervision. In summary, the FAA inspector reported that on February 17, the accident airplane's engine was removed from N5107K, and it was installed on another Cessna 172 airframe that was awaiting an engine overhaul. After removing and replacing several impact-damaged components, the engine was run up to 2,400 rpm. With the exception of a minor vibration due to the fact that the crankshaft was bent, the engine operated normally. The reason for the partial engine power loss, as reported by the pilot, was not ascertained.

Aircraft

Registration
N5107K
Reported as
Cessna 172N
Category
Airplane
Serial number
17273972
Airframe hours
14,453
Engine
Lycoming O-320-H2AD, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Cable Air, Inc.
Registered owner
Janette J. Cable, Trustee
Airworthiness certificate
Standard, Normal
Last inspection
Annual · February 5, 2004
Departed
CCB · Upland, CA
Destination
CCB
Airport
CCB · Cable, runway 24, 3,865 × 75 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
Minor
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
September 1, 2003
Seat
Left
Flight hours
250 total · 217 in this make and model · 186 as pilot in command · 25 in the last 90 days · 13 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
80° at 10 knots
Visibility
30 statute miles
Lowest ceiling
15,000 ft overcast
Altimeter
30.15 inHg
Observed at
POC, 5 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.