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 23, 1998 · Piper PA-28R-200 · N222LC

Baker, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 23, 1998
Injury Outcomes
No injuries (1 uninjured)
Location
Baker, CA
Aircraft
Piper PA-28R-200
Tail Number
N222LC
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX98LA241

While en route to the destination airport, the pilot noted the fuel flow gage was fluctuating and the engine began to run roughly. He switched to the backup electric fuel pump and the engine smoothed out. Shortly thereafter, the fuel flow gage again provided an intermittent reading. The pilot decided to make a precautionary landing at an alternate airport and overflew the field to check the windsock for wind direction. He reported that right at touchdown he noted a wind change to a tailwind and decided to abort the landing. He applied full power, but the engine did not respond. The airplane was landed straight ahead, overran the runway, and struck an elevated road. The pilot reported that prior to the flight, on the day of the accident, the airplane had been refueled. After fueling, he conducted a run-up and noted that the engine was sputtering. He taxied to a maintenance facility and asked them to inspect the aircraft. The maintenance facility found that the fuel injector nozzles were dirty. They cleaned and reinstalled them. The pilot conducted another run-up with no discrepancies noted and departed the airport. A postaccident engine test run and inspection were conducted with no anomalies noted. The fuel system was inspected, to include the fuel servo unit, with no discrepancies found.

NTSB Probable Cause

A loss of engine power for undetermined reasons.

Full Narrative

On July 23, 1998, at 1100 hours Pacific daylight time, a Piper PA-28R-200, N222LC, experienced a loss of engine power after aborting a landing at the Baker, California, airport. The airplane, operated under 14 CFR Part 91, sustained substantial damage during the ensuing runway overrun and collision with ground obstacles. The private pilot/owner, the sole occupant, was not injured. Visual meteorological conditions existed for the personal flight and no flight plan was filed. The flight originated from the General Fox Field airport, Lancaster, California, at 1000 on the day of the accident and was scheduled to terminate at the Henderson, Nevada, airport. In a telephone interview with the Safety Board, the pilot stated that he had departed from the Van Nuys, California, airport on July 22, 1998, and was returning to Henderson. He stated that near Daggett, California, he encountered a storm. He made the decision to return to the General Fox Field airport and wait out the storm. On the morning of July 23, the pilot reported that the airplane was refueled and he conducted the preflight inspection. He noted that during the run-up the engine sputtered, and he taxied the airplane to a maintenance facility located on the field. He then checked the fuel, with no water or debris present. The pilot then solicited the maintenance facility to check out his airplane. The pilot reported that the maintenance facility found the fuel injectors were dirty and cleaned them. They ground checked the engine and it ran fine. The pilot conducted another run-up and did not notice any further discrepancies. He reported that he had the tanks "topped off" with fuel, and checked the fuel for water or debris, with no discrepancies noted. He taxied back for takeoff and performed another run-up with no malfunctions noted. While en route to Henderson, the pilot noticed that the fuel flow gage was fluctuating and the engine began to run rough and sputter. The pilot said he believed that he had lost the engine driven fuel pump. He then switched to the backup electric driven fuel pump and for a few seconds the airplane ran fine. Shortly thereafter, the fuel flow gage began providing an intermittent reading again and he decided to make a precautionary landing at Baker airport. The pilot reported that he checked the windsock and was attempting to land into the wind. He stated that right before touchdown he noted that the windsock had changed direction and he was now landing with a tailwind. He decided to abort the landing and added full power, but the engine did not respond. He landed the airplane straight ahead and engine power came back on just after touchdown. The pilot stated that the airplane overran the runway and struck an elevated road. Following the accident, an inspection and ground test run of the engine was performed. The battery had to be recharged prior to the engine run-up. After the battery had been recharged, the engine was started and run for 5 minutes with no discrepancies found. All engine instrument readings were within manufacturer's limits. A magneto check was conducted at 2,000 rpm with no discrepancies. No leaking was observed before, during, or after the test run. The fuel vents in each of the wing assemblies were examined and found to be free of any obstructions. The throttle and mixture controls were found to be secure at their respective arms. All of the fuel lines to the engine were found to be secure. There were no further discrepancies noted with the inspection of the fuel system. The fuel servo was removed and a flow test was conducted and was found to be within manufacturer's specifications. The fuel servo was then disassembled with no anomalies noted.

Flight

Event TypeAccident
Event Time11:00 PDT
Nearest AirportBAKER (0nm)
Runway33
Runway Length3157 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28R-200
Tail NumberN222LC
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-C1C · Reciprocating · 200
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 51 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind4 kt
CeilingNone
Temperature / Dew Point64 F
Altimeter0
Observation Time17:51
Weather SourceWFAC

Appendix: Source Data