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

August 26, 2001 · Piper PA-32-301T · N9288X

Fullerton, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 26, 2001
Injury Outcomes
No injuries (4 uninjured)
Location
Fullerton, CA
Aircraft
Piper PA-32-301T
Tail Number
N9288X
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX01FA290

The airplane collided with a fence during an aborted takeoff. The pilot flew to Fullerton on Tuesday, August 21, and noted no discrepancies. The airplane was full of fuel, and everything checked normal during preflight, taxi, and engine run-up. During the departure, the pilot applied full throttle and noted 38.5 inches of manifold pressure at 2,500 rpm. He crosschecked instruments and his alignment. He was approaching midfield and noted his airspeed was above 65 knots, but not increasing. The manifold pressure looked the same, but the rpm was below 2,500; he thought it had dropped about 100 rpm. The airplane did not feel or sound like it was accelerating. He had not detected any hesitation in the engine, and did not hear any metallic sounds. He elected to abort the takeoff as he passed midfield and pulled the throttle back. He was unable to stop on the runway and collided with an airport boundary fence about 20 feet past the end of the runway shearing off the landing gear and substantially damaging the left wing. During post accident examination of the airplane, the pilot started the engine using his normal procedures. The propeller cycled normally, and both magnetos dropped 50 rpm on the magneto check. The pilot ran the engine up to full takeoff power, and all instruments, including manifold pressure and rpm, went to their red (maximum) limit marks. The pilot reduced power to idle and then ran the engine back to full power with no anomalies noted. The pilot secured the engine using his normal procedures with no difficulties encountered.

NTSB Probable Cause

The engine lost power for unknown reasons.

Full Narrative

On August 26, 2001, at 1039 Pacific daylight time, a Piper PA-32-301T, N9288X, collided with a fence during an aborted takeoff from Fullerton, California. The private pilot/owner was operating the airplane under the provisions of 14 CFR Part 91. The pilot and three passengers were not injured; the airplane sustained substantial damage. Palo Alto, California, was the destination for the personal cross-country flight. Visual meteorological conditions prevailed, and an IFR flight plan had been filed. The Safety Board Investigator-in-Charge (IIC) interviewed the pilot and the pilot submitted a written statement. The pilot stated that he purchased the airplane 3 months prior to the accident and had flown it about 15 times with no problems noted. He also owns a Piper PA-32-300, which he has flown for 7 years. He flew to Fullerton on Tuesday, August 21, and noted no discrepancies. He filled the airplane with fuel, which was 102 gallons useable. He said everything checked normal during preflight, taxi, and during the engine run-up. During the departure, he applied full throttle and noted 38.5 inches of manifold pressure at 2,500 rpm. He crosschecked instruments and his alignment. He was approaching midfield and noted his airspeed was above 65 knots, but not increasing. The manifold pressure looked the same, but the rpm was below 2,500; he thought it had dropped about 100 rpm. The airplane did not feel or sound like it was accelerating. He had not detected any hesitation in the engine, and did not hear any metallic sounds. He elected to abort the takeoff as he passed midfield and pulled the throttle back. He was unable to stop on the runway and collided with an airport boundary fence about 20 feet past the end of the runway. The landing gear sheared off and the left wing sustained substantial damage. On October 4, 2001, the IIC and a representative from Textron Lycoming examined the airplane at Aircraftsman in Chino, California. Investigators removed the top spark plugs for examination. They noted similar gaps and no mechanical deformation on all spark plugs. The spark plug electrodes were gray in color, which corresponded to normal operation according to the Champion Aviation Check-A-Plug AV-27 Chart. The Lycoming representative examined the cylinders with a lighted borescope. He noted a slight accumulation of oil on the cylinders on the left side of the engine. The recovery agent reported that he had to lay the airplane on its left side for a while during the recovery process. Investigators moved the throttle, mixture, and propeller controls, and observed them travel freely and smoothly between their high and low limits. The recovery agent removed the wings during recovery. He plumbed a fuel can into the fuel selector valve in the cabin, and strapped the fuselage to a trailer. The IIC had the pilot/owner run the engine. The pilot started the engine using his normal procedures and allowed the engine to warm up. The propeller cycled normally and the IIC observed a 50-rpm drop when checking both magnetos. The pilot ran the engine up to full takeoff power, and all instruments, including manifold pressure and rpm, went to their red (maximum) limit marks. The pilot reduced power to idle and then ran the engine back to full power with no anomalies noted. The pilot secured the engine using his normal procedures with no difficulties encountered. During the repair process, the owner had the propeller governor inspected. The repair facility thought the governor appeared to be fairly new and in good condition overall. The facility noted minor wear on the inside of the relief valve, which they thought could lead to surging, and that maximum rpm was 50 higher than specified. They reported that all other parameters were within manufacturer's specifications.

Flight

Event TypeAccident
Event Time10:39 PDT
Nearest AirportFullerton (0nm)
Runway24
Runway Length3121 ft
Runway Width75 ft
Flight Plan FiledIFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-301T
Tail NumberN9288X
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540-AH1A · Reciprocating · 310
Seats6

People & Injuries

Injury SummaryNo injuries (4 uninjured)
Fatal0
Serious0
Minor0
Uninjured4
Total4
Crew 1Age 44 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 4 kt
Visibility2.5 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter29.87 inHg
Observation Time17:44
Weather SourceWFAC

Appendix: Source Data