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 26, 2008 · Cessna 172S · N331ME

Stevensville, MD

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 26, 2008
Injury Outcomes
1 injury (1 minor injury), 1 uninjured
Location
Stevensville, MD
Aircraft
Cessna 172S
Tail Number
N331ME
Operator
Chesapeake Proflight
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
NYC08CA257

The certificated flight instructor and the student pilot were practicing crosswind takeoffs and landings with an 8 knot, 90-degree crosswind. During the second landing attempt, as the airplane crossed the runway threshold, the student reduced power "more abruptly" than he had on the previous landing. The airplane "bounced," and the flight instructor told the student to add power. The student then "took out the wind correction on the ailerons and tensed up." The flight instructor attempted to re-apply the left aileron control, and told the student "don't fight me." The student then added power while the flight instructor retracted the flaps 10 degrees, from the 20-degree setting. The flight instructor expected the student to increase the engine power to full for a go-around, as they had practiced in the previous lessons, but he did not and the airplane bounced a second time. The airplane was at the far right edge of the runway when the flight instructor assumed the flight controls and reduced the engine power to idle. The airplane continued off the right side of the runway, and onto a grass area, where it struck an embankment, and nosed over, resulting in substantial damage to the fuselage, wing spar, and firewall.

NTSB Probable Cause

The flight instructor's inadequate remedial action following the student pilot's improper recovery from a bounced landing.

Full Narrative

According to the certificated flight instructor, he and the student pilot of the Cessna 172S were practicing crosswind takeoffs and landings with an 8 knot, 90-degree crosswind. During the second landing attempt, as the airplane crossed the runway threshold, the student reduced power "more abruptly" than he had on the previous landing. The airplane "bounced," and the flight instructor told the student to add power. The student then "took out the wind correction on the ailerons and tensed up." The flight instructor then attempted to re-apply the left aileron control, and told the student "don't fight me." The student then added power while the flight instructor retracted the flaps from the 10-degree setting. The flight instructor expected the student to increase the engine power to full for a go-around, but he did not and the airplane bounced a second time. The airplane was at the far right edge of the runway, when the flight instructor assumed the flight controls and reduced the engine power to idle. The airplane continued off the right side of the runway, and onto a grass area, where it struck an embankment, and nosed over, resulting in substantial damage to the fuselage, wing spar, and firewall.

Flight

Event TypeAccident
Event Time09:30 EDT
Nearest AirportBay Bridge Airport (0nm)
Runway29
Runway Length2903 ft
Runway Width60 ft
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172S
Tail NumberN331ME
Aircraft CategoryAir
DamageSubstantial
OperatorChesapeake Proflight
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360 · Reciprocating
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury), 1 uninjured
Fatal0
Serious0
Minor1
Uninjured1
Total2
Crew 1Age 35 · First Class · Minor
Crew 2Age 22 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind190° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter30.03 inHg
Observation Time13:30
Weather SourceWFAC

Appendix: Source Data