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 17, 1998 · Piper PA-28-181 · N2953Y

Springfield, MO

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 17, 1998
Injury Outcomes
No injuries (1 uninjured)
Location
Springfield, MO
Aircraft
Piper PA-28-181
Tail Number
N2953Y
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CHI98LA258

The pilot stated that while he was in contact with approach control, the engine quit suddenly, he switched tanks, and the engine restarted without hesitation. The pilot notified approach control of his fuel situation and approach control communicated to the pilot that he was flying directly over the airport. The pilot stated that he still did not have visual contact with the airport. The engine quit, for the second time, and the pilot executed a forced landing into a field. The pilot stated that he used 3 notches of flaps, tried to keep the wings level, and was aware of some trees that were at the beginning of the field he had selected. The aircraft came to rest on some railroad tracks. Post accident investigation showed that the pilot had been flying for at least 4 hours and 4 minutes at the time of the first engine failure. The fuel tanks were drained, with 1.5 pints of fuel being drained from each wing tank. There was no evidence of a fuel spill at the accident site and the fuel tanks were not compromised during the forced landing. There were no other anomalies found with the aircraft, flight controls, or engine.

NTSB Probable Cause

the pilot in command's inadequate preflight planning/preparation and inaccurate fuel consumption calculations that caused the aircraft's fuel supply to be exceeded. Factors to the accident were the dark light condition and the rough/uneven terrain condition.

Full Narrative

On July 16, 1998, at 2100 central daylight time, a Piper PA-28-181, N2953Y, piloted by a private pilot, sustained substantial damage when it impacted the terrain during a forced landing resulting from a loss of engine power during a visual approach to Springfield Downtown Airport, near Springfield, Missouri. Visual meteorological conditions prevailed at the time of the accident. The 14 CFR Part 91 personal flight was operating on an IFR flight plan. The pilot reported no injuries. The flight departed from Austin Executive Airpark, near Austin, Texas, at 1708. According to the pilot's written statement, he had preflighted the aircraft and had noted that the fuel tanks were full, indicating 48 usable gallons of fuel. The pilot stated that he had flown the flight at 2550 rpm and had leaned the engine by utilizing an exhaust gas temperature (egt) gauge. The pilot stated that he canceled his IFR flight plan when he made visual contact with the Springfield Downtown Airport. The pilot made an initial call to the potential traffic in the pattern, heard no response, and continued for a straight-in landing on runway 29. The pilot stated approximately 3 miles from the airport he heard another aircraft announcing that they were going to make a straight-in landing for runway 11. Considering the faster traffic, the pilot decided to enter a left downwind to land behind the faster traffic on runway 11. The pilot stated that he had made visual contact with the other aircraft. While positioning the aircraft for a left downwind for runway 11, the pilot lost visual contact with the other aircraft and the airport environment. The pilot stated that he contacted Springfield approach control and asked for a vector back to the airport. The pilot stated that while he was in contact with approach control, that the engine quit suddenly, he switched tanks, and the engine restarted without hesitation. The pilot notified approach control of his fuel situation and approach control communicated to the pilot that he was flying directly over the airport. The pilot stated that he still did not have visual contact with the airport. The engine quit, for the second time, and the pilot executed a forced landing into a field. The pilot stated that he used 3 notches of flaps, tried to keep the wings level, and was aware of some trees that were at the beginning of the field he had selected. The aircraft came to rest on some railroad tracks. Post accident investigation showed that the pilot had been flying for at least 4 hours and 4 minutes at the time of the first engine failure. The fuel tanks were drained, with 1.5 pints of fuel being drained from each wing tank. There was no evidence of a fuel spill at the accident site and the fuel tanks were not compromised during the forced landing. There were no other anomalies found with the aircraft, flight controls, or engine.

Flight

Event TypeAccident
Event Time21:00 CDT
Nearest Airport0nm
Runway0
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-181
Tail NumberN2953Y
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDark Night
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter30.00 inHg
Observation Time02:10
Weather SourceWFAC

Appendix: Source Data