- Date
- July 25, 2002, 20:30 local (Jul 26, 2002, 03:30 UTC)
- Place
- Creston, CA
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N5268KCessna 172P
- Weather
- Visual (VMC) · Night/dark
- Status
- Completed · report July 29, 2004
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20020725017359A
- Case key
- 55315
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 inadequate in-flight planning/decision, which resulted in fuel exhaustion and loss of engine power. A factor in the accident was the dark night conditions.
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.
Analysis
The airplane made a forced landing on a road and collided with a sign, following a total loss of engine power. Prior to takeoff, the pilot visually checked the fuel level by looking inside the tanks. He estimated that he had about 5 1/2 hours of fuel on board the airplane. He planned his cross-country to be about a 3-hour trip, in dark night conditions. While en route, about 12 miles from his planned destination, the engine lost power. He attempted to restart the engine by following the procedures on the emergency checklist, but the engine would not start. He performed a forced landing on a road and the airplane's right wing collided with a sign. The pilot thought that the accident was a result of fuel exhaustion. The pilot did not report any mechanical problems with the airplane prior to the accident.
Factual narrative
On July 25, 2002, about 2030 Pacific daylight time, a Cessna 172P, N5268K, lost engine power and made a forced landing on a road near Creston, California. During the landing rollout, the airplane collided with a highway sign. A private individual owned and operated the airplane under the provisions of 14 CFR Part 91. The private pilot and two passengers were not injured; the airplane sustained substantial damage. The personal cross-country flight departed Montgomery Field Airport (MYF), San Diego, California, about 1850, with a planned destination of Paso Robles Municipal Airport (PRB), Paso Robles, California. Night visual meteorological conditions prevailed, and a visual flight rules (VFR) flight plan had been filed.
During a telephone interview with the National Transportation Safety Board investigator-in-charge (IIC), the pilot stated that the airplane had recently come out of a 100-hour inspection. Prior to takeoff, he visually checked the fuel level by looking inside the tanks. He estimated that he had about 5 1/2 hours of fuel on board the airplane. He planned his cross-country to be about a 3-hour trip. About an hour before the engine quit he recalled the fuel gauges in the cockpit showing 1/2 tank of fuel on the right side, and a little under 1/2 tank of fuel on the left side. While en route, it was a dark night and he could not make out the terrain below. He approached the vicinity of Paso Robles and the engine quit. He attempted to restart the engine by following the procedures on the emergency checklist, but the engine would not start.
The pilot saw two headlights below, off to the right of his course. He maneuvered the airplane in that direction, while avoiding several power lines. He positioned the airplane over a two-lane road, ahead of the headlights. While touching down on the road, he noticed that several hundred feet ahead of him, the road had a 90-degree turn to the right with a corresponding 25-mile-an-hour road sign and yellow arrow signs. If he continued forward off the road, he would collide with a fence. He opted to take the turn and applied heavy brake pressure. The airplane's right wing collided with an arrow sign. The airplane came to rest about 12 miles southeast of PRB.
The pilot thought that the accident was a result of fuel exhaustion. He did not report any mechanical problems with the airplane prior to the accident.
Aircraft
- Registration
- N5268K
- Reported as
- Cessna 172P
- Category
- Airplane
- Serial number
- 17274038
- Airframe hours
- 9,668.8
- Engine
- Lycoming O-360-A4M, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal; Standard, Utility
- Last inspection
- Annual · July 25, 2002 · 6 hours before
- Departed
- MYF · San Diego, CA
- Destination
- PRB · Paso Robles, CA
- Flight plan
- VFR
- Airport
- PRB · Paso Robles
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
- 36
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 1, Valid Medical--no waivers/lim.
- Last flight review
- October 1, 2003
- Seat
- Left
- Flight hours
- 217 total · 217 in this make and model · 138 as pilot in command · 20 in the last 90 days · 16 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Night/dark
- Wind
- 300° at 9 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 64 °F, dew point 46 °F
- Altimeter
- 30.01 inHg
- Observed at
- PRB, 12 nm away
Docket · 2
The files NTSB released with the investigation on June 3, 2004, on NTSB’s docket system: statements, records, photos and specialists’ reports. 384 KB 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.
Other investigations on N5268K · 1
Matched to the same aircraft by N-number and date.