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

September 14, 2024 · Piper PA32 260 · N6FT

Baltimore, MD

Overview

Report Status
Factual report
Event Type
Accident
Date
September 14, 2024
Injury Outcomes
No injuries (3 uninjured)
Location
Baltimore, MD
Aircraft
Piper PA32 260 (1966)
Tail Number
N6FT
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA24LA380

On September 14, 2024, about 1405 eastern daylight time, a Piper PA-32-260, N6FT, was substantially damaged when it was involved in an accident near Baltimore, Maryland. The commercial pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that earlier that day he had flown the airplane on two uneventful flights. The third flight that day, which would be the accident flight, was to fly two passengers around the airport traffic pattern for a planned flight duration of about 10 minutes. After engine start, he taxied to runway 15L and waited about 10 to 15 minutes while in line to depart. After being cleared for takeoff, with the fuel selector positioned to the left main fuel tank, he applied full power and the engine responded. He rotated at 80 miles-per-hour (mph) and reported becoming airborne when the airplane was halfway down the 5,000-ft-long runway. He accelerated to between 110 and 115 mph, but when the airplane was about 200 ft above the runway, the engine lost power completely. He pushed the elevator control forward and touched down on the runway at a fast airspeed. With the throttle full forward, the engine regained power and the airplane climbed off the runway. He then pushed the elevator forward and touched down on grass before the airplane crested a hill then came to rest adjacent to a building on airport property. An initial inspection of the airplane at the accident site by the Federal Aviation Administration inspector revealed that the right main fuel tank was breached, but the left was not. No contaminants were noted in the left main fuel tank. The airplane was recovered and retained for further examination of the airframe and engine.

Full Narrative

On September 14, 2024, about 1405 eastern daylight time, a Piper PA-32-260, N6FT, was substantially damaged when it was involved in an accident near Baltimore, Maryland. The commercial pilot and two passengers were not injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 personal flight. The pilot stated that earlier that day he had flown the airplane on two uneventful flights. The third flight that day, which would be the accident flight, was to fly two passengers around the airport traffic pattern for a planned flight duration of about 10 minutes. After engine start, he taxied to runway 15L and waited about 10 to 15 minutes while in line to depart. After being cleared for takeoff, with the fuel selector positioned to the left main fuel tank, he applied full power and the engine responded. He rotated at 80 miles-per-hour (mph) and reported becoming airborne when the airplane was halfway down the 5,000-ft-long runway. He accelerated to between 110 and 115 mph, but when the airplane was about 200 ft above the runway, the engine lost power completely. He pushed the elevator control forward and touched down on the runway at a fast airspeed. With the throttle full forward, the engine regained power and the airplane climbed off the runway. He then pushed the elevator forward and touched down on grass before the airplane crested a hill then came to rest adjacent to a building on airport property. An initial inspection of the airplane at the accident site by the Federal Aviation Administration inspector revealed that the right main fuel tank was breached, but the left was not. No contaminants were noted in the left main fuel tank. The airplane was recovered and retained for further examination of the airframe and engine.

Flight

Event TypeAccident
Event Time14:05 EDT
Nearest AirportBaltimore/Washington Int'L Thu (0.8nm E)
Runway15L
Runway Length5000 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA32 260
Tail NumberN6FT
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Seats5

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3

Conditions

ConditionsVMC
LightDaylight
Wind50° @ 11 kt
Visibility10 sm
CeilingBroken clouds 25000 ft
Temperature / Dew Point61 F
Altimeter30.21 inHg
Observation Time13:54
Weather SourceWFAC

Appendix: Source Data