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 10, 2000 · Piper PA-28-180 · N4209T

Santa Maria, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 10, 2000
Injury Outcomes
4 injuries (4 minor injuries)
Location
Santa Maria, CA
Aircraft
Piper PA-28-180
Tail Number
N4209T
Operator
Santa Ynez Flyers
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
LAX00LA259

The airplane lost power in cruise flight and made a forced landing in a residential area near the Santa Maria Airport, colliding with obstructions during the touchdown and landing roll. The flight originated at Reno, Nevada, and had made an en route stop at Concord, California. On departure from Reno, the fuel tanks contained 34 total gallons, and the pilot did not refuel the airplane while at Concord. About 25 miles northwest of the accident site, the pilot first observed indications of a low fuel state and notified Los Angeles ARTCC that he would be diverting to Santa Maria because of the critical fuel situation. When the pilot changed frequencies to the Santa Maria ATCT local controller, he reported that he thought the airplane was out of fuel. Two minutes later the pilot announced that he was "completely out of fuel" and did not think he would make it to the runway. The pilot told responding police officers that he figured the fuel on board was adequate to continue to his destination. No breaches were observed in either of the fuel tanks or the lines. No fuel was found in the tanks.

NTSB Probable Cause

The pilot's failure to ensure that an adequate fuel supply was on board at last departure, which resulted in a loss of engine power due to fuel exhaustion. The pilot's failure to refuel the airplane at the en route stop was also causal.

Full Narrative

On July 10, 2000, at 1347 Pacific daylight time, a Piper PA-28-180, N4209T, collided with obstructions during an off airport landing in Santa Maria, California. The forced landing was precipitated by a total loss of power during cruise. The aircraft sustained substantial damage, and the certificated private pilot and three passengers received minor injuries. The aircraft was being operated by the pilot/owner as a personal flight under the provisions of 14 CFR Part 91 when the accident occurred. The flight originated from Concord Buchanan Field, Concord, California, about 1145, and was destined for the Santa Ynez Airport. It was the second leg of a flight that began earlier that day from the Reno, Nevada, International Airport. Visual meteorological conditions prevailed, and a flight plan had not been filed. The Los Angeles Air Route Traffic Control Center (ARTCC) reported the pilot having transmitted a change of plans en route at 1332. The pilot advised that the landing would now be at the Santa Maria Airport due to a low fuel state. A request for a tower frequency change was approved by ARTCC. At 1334, the pilot contacted the Santa Maria tower about 5 miles northwest of the airport with a request for landing instructions. He notified the tower that he thought the airplane was out of fuel, and that he did not have the airport in sight. At 2036, he then advised that the airplane "was completely out of fuel and did not think it would make the runway." The airplane landed near Inger and Sequoia streets, about 1 mile from the airport. The airplane collided with a tree and wall of a residence collapsing the nose gear and damaging the right wing. Post crash photographs obtained from the Federal Aviation Administration inspector documented the wreckage and condition of the airplane. No breaches were noted in either of the two fuel tanks located in the wings. A deep semicircular impression was observed on the leading edge of the right wing. The left horizontal stabilizer had shown an impact feature and two tears on the front leading edge. Records obtained in the investigation indicated that the airplane had been fueled to the tabs in Reno approximately 1 hour before the flight. According to Piper Aircraft, the tabs are filler neck indicators. They delineate (approximately) a 17-gallon quantity in each of the two 25-gallon tanks, and Piper designates two of the gallons as unusable. After receiving fuel, the airplane departed for Concord Buchanan Field, a distance of approximately 140 miles. It was approximately another 202 miles from Concord to Santa Maria, bringing the total to 342 nautical miles. On board were four passengers, a canine, and carryon baggage. According to the Santa Maria Police Officer who responded to the scene, the approximate combined weight of the passengers and canine was 635 pounds. Carryon items consisted of (6) duffle size bags with clothing and personal items inside. The pilot stated in the accident report that he had 30 gallons aboard at the time of last departure. He told the Santa Maria police that he had topped off the fuel tanks in Reno. He said he made good time to Concord and figured to have around 3 hours of fuel aboard. He had estimated only 2 hours 15 minutes flight time to Santa Ynez. Upon reaching San Luis Obisbo, the fuel quantity indicators read 1/4 in the cockpit, which in his estimate, was enough to continue to his destination. The instruments then went to zero before the airplane reached Santa Maria. Fuel pressure was lost in the selected tank. The pilot switched tanks, and then lost pressure in the other one. An attempt to land in an open field was made, but the pilot reported not having enough altitude or speed.

Flight

Event TypeAccident
Event Time13:47 PDT
Nearest AirportSanta Maria Public (5nm NNE)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-180
Tail NumberN4209T
Aircraft CategoryAir
DamageSubstantial
OperatorSanta Ynez Flyers
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4A · Reciprocating · 180
Seats4

People & Injuries

Injury Summary4 injuries (4 minor injuries)
Fatal0
Serious0
Minor4
Uninjured0
Total4
Crew 1Age 38 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 7 kt
Visibility10 sm
CeilingBroken clouds 2000 ft
Temperature / Dew Point66 F / 54
Altimeter30.00 inHg
Observation Time19:51
Weather SourceWFAC

Appendix: Source Data