Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 26, 2002 · Cessna 172P · N5268K

Creston, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 26, 2002
Injury Outcomes
No injuries (3 uninjured)
Location
Creston, CA
Aircraft
Cessna 172P
Tail Number
N5268K
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX02LA237

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time20:30 PDT
Nearest AirportPaso Robles (12nm SSE)
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN5268K
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 36 · First Class · None

Conditions

ConditionsVMC
LightDark Night
Wind300° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F / 46
Altimeter30.01 inHg
Observation Time02:53
Weather SourceWFAC

Appendix: Source Data