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

May 9, 2007 · Cessna 172S · N924LP

Asheville, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 9, 2007
Injury Outcomes
No injuries (1 uninjured)
Location
Asheville, NC
Aircraft
Cessna 172S
Tail Number
N924LP
Operator
Montgomery County Aviation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC07CA116

According to the pilot, since the Cessna 172 was "high," he adjusted the flight controls for a "rapid" descent, and intercepted the visual glideslope on short final. At that point, the flaps were fully deployed, and the throttle at idle. Once over the runway, the pilot flared too "high," the airplane landed hard, and bounced about four times with each bounce becoming more "violent." On the last bounce, the airplane touched down nosewheel first, and the propeller struck the runway. The pilot added that there were no problems with the airplane, and that the runway was twice as long, and twice as wide as his home runway, causing him to initiate the landing flare too high.

NTSB Probable Cause

The pilot's improper landing flare which resulted in a hard landing. A factor in the accident was the visual illusion experienced by the pilot from landing on a long, wide runway.

Full Narrative

According to the pilot, since the Cessna 172 was "high," he adjusted the flight controls for a "rapid" descent, and intercepted the visual glideslope on short final. At that point, the flaps were fully deployed, and the throttle at idle. Once over the runway, the pilot flared too "high," the airplane landed hard, and bounced about four times with each bounce becoming more "violent." On the last bounce, the airplane touched down nosewheel first, and the propeller struck the runway. The pilot added that there were no problems with the airplane, and that the runway was twice as long, and twice as wide as his home runway, causing him to initiate the landing flare too high.

Flight

Event TypeAccident
Event Time15:55 EDT
Nearest AirportAsheville Regional (0nm)
Runway16
Runway Length8001 ft
Runway Width150 ft
Flight Plan FiledIFR
Aircraft FireNo

Aircraft

AircraftCessna 172S
Tail NumberN924LP
Aircraft CategoryAir
DamageSubstantial
OperatorMontgomery County Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-L2A · Reciprocating

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
WindCalm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0

Appendix: Source Data