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

March 21, 2004 · Stanley Glasair SH-2 · N309TS

San Luis Obispo, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 21, 2004
Injury Outcomes
1 injury (1 minor injury)
Location
San Luis Obispo, CA
Aircraft
Stanley Glasair SH-2
Tail Number
N309TS
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
LAX04LA169

The airplane experienced a loss of engine power and impacted a ditch during the pilot's forced landing in a field. While approaching the proximity of the destination airport, the pilot observed the engine gauges indicating rising oil temperature. About 5 miles from the airport, the engine emitted a loud noise and he declared an emergency due to an engine failure. Realizing that he would be unable to make it to the runway, the pilot executed a forced landing in a field; during the landing roll, the airplane impacted a ditch and tumbled. Post-accident external visual examination by a Federal Aviation Administration (FAA) inspector revealed that the engine sustained a catastrophic failure, with a hole knocked in the upper case spine above the rear cylinders. Looking through the hole, the inspector observed that the right rear piston had seized in the No. 3 cylinder and its respective connecting rod was broken just above crankshaft rod end flare. The inspector could not identify the rod end cap or the bearing shells. The No. 3 piston skirt was visibly scorched in the direction of piston travel. A visual examination of the engine, disclosed that all of the cylinders were worn and scored. After the accident, the owner took the engine to a maintenance facility that examined the engine and reported that rod bearing in the No. 3 cylinder failed. The facility declined to provide detailed observations on the internal condition of the engine, the rod fracture, and condition of the bearing. The FAA inspector said the pilot told him that prior to the accident, the engine was experiencing excessive oil consumption. In response, the pilot removed the No. 3 cylinder from the engine and employed an engine shop to change the piston in an effort to alleviate the excessive oil consumption problems. After the maintenance was preformed, the pilot reinstalled the cylinder. The inspector added that sometime prior to the accident the pilot had also modified the engine by installing larger pistons.

NTSB Probable Cause

The loss of engine power due to the failure of the #3 cylinder piston and connecting rod for undetermined reasons.

Full Narrative

On March 21, 2004, at 1243 Pacific standard time, a homebuilt Stanley Glasair SH-2, N309TS, experienced a loss of engine power and impacted a ditch during a forced landing in a field west of the San Luis County Regional Airport, San Luis Obispo, California. The pilot owned and operated the airplane under the provisions of 14 CFR Part 91. The airline transport pilot, the sole occupant, sustained minor injuries; the airplane sustained substantial damage. The personal flight originated at Corcoran, California, about 1215, with a planned destination of San Luis Obispo. Visual meteorological conditions prevailed and a flight plan had not been filed. In written and verbal statements, the pilot reported that he was receiving visual flight rules (VFR) flight advisories from the Los Angeles Air Route Traffic Control Center while en route to San Luis Obispo. While approaching the airport proximity, he noted that the engine gauges indicated that the oil temperature was rapidly rising. While proceeding directly to San Luis Obispo, he transmitted over the radio that he was experiencing a rough running engine. About 5 miles from the airport, the engine noise became unusually loud, and he declared an emergency due to an engine failure. The pilot further stated that the sector controller provided a radar vector to the airport, and instructed him to contact the San Luis Obispo Air Traffic Control Tower. While about 1,200 feet above ground level (agl), and 2 1/2 miles from the airport, a small oil fire erupted in the engine compartment. Realizing that he would be unable to make it to the runway, the pilot executed a forced landing in a field; during the landing roll, the airplane impacted a ditch and tumbled. In a telephone conversation with a National Transportation Safety Board investigator, the Federal Aviation Administration (FAA) inspector reported that responding municipal fire department personnel extinguished the fire, which had burned the firewall and portions of the structure just aft of it. The oil was leaking out of the engine and dripping on the hot exhaust, becoming a catalyst for ignition. Following the accident, the airplane wreckage was transported to the pilot's hangar, where the FAA inspector examined it. He reported that the Lycoming O-360-A1B engine sustained a catastrophic failure, with a hole knocked in the upper case spine above the rear cylinders. He noted that the right rear piston had seized in the number 3 cylinder and its respective connecting rod was broken just above crankshaft rod end flare. The inspector could not identify the rod end cap or the bearing shells. The inspector did not teardown or open the engine for detailed examination of the parts. The FAA inspector further stated that prior to the accident, the pilot noticed the engine was experiencing excessive oil consumption. In response, the pilot removed a cylinder from the engine and employed an engine shop to change the piston in an effort to alleviate the excessive oil consumption problems. After the maintenance was preformed, the pilot reinstalled the cylinder. He added that sometime prior to the accident the pilot had also modified the engine by installing larger pistons. According to the FAA inspector, the pilot, who holds neither a repairman, nor an airframe and power plant certificate, was performing most of the maintenance on the airplane. Upon visual examination of the engine, he noted that all of the cylinders were worn and scored. The owner took the engine to an overhaul facility that had previously performed work on the engine, and they examined it after the accident. The manager of the facility reported that the rod bearing in the number 3 cylinder failed (part number LW-13212). He further stated that he sent the bearing to a lab for metallurgy testing. Despite numerous attempts by a Safety Board investigator, the overhaul facility failed to return any follow-up phone calls requesting information on the internal condition of the engine as found during the teardown. A reference book about aircraft piston engines, the "Sky Ranch Engineering Manual," states that there are six major causes of bearing distress, which include, "dirt, lack of lubrication, misassembly, misalignment, overloading, and corrosion."

Flight

Event TypeAccident
Event Time12:43 PST
Nearest AirportSan Luis County Regional Airpo (1nm E)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireIflt
Aircraft ExplosionNo

Aircraft

AircraftStanley Glasair SH-2
Tail NumberN309TS
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-A1B · Reciprocating · 200
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 62 · First Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind290° @ 9 kt
Visibility9 sm
CeilingNone
Temperature / Dew Point63 F / 55
Altimeter30.06 inHg
Observation Time20:46
Weather SourceWFAC

Appendix: Source Data