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

April 13, 2011 · Cessna 172S · N2468Z

Saint Petersburg, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 13, 2011
Injury Outcomes
No injuries (1 uninjured)
Location
Saint Petersburg, FL
Aircraft
Cessna 172S
Tail Number
N2468Z
Operator
Bay Air Flying Service
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA11CA244

The student pilot stated that after takeoff during his second supervised solo flight, he remained in the traffic pattern and landed uneventfully. During the landing roll he elected to perform a touch-and-go landing and applied power for takeoff. Immediately after adding power, the airplane turned left. He applied right rudder to correct the left turn but then decided to perform a full stop landing. He applied the brakes in an effort to keep the airplane on the runway, and reduced power before the airplane departed the runway, and went into water while traveling about 30 knots. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The student's certified flight instructor stated that after veering to the left, the airplane exited the runway, crossed a perpendicular runway, and then impacted a ditch at which time he heard power applied. He then observed the airplane travel into the water and ran to the airplane to assist his student. Postaccident inspection of the flight controls revealed no evidence of preimpact failure or malfunction. The airplane sustained substantial damage to the firewall and fuselage.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C

Full Narrative

The student pilot stated that after takeoff during his second supervised solo flight, he remained in the traffic pattern and landed uneventfully, but during the landing roll elected to perform a touch-and-go landing and applied power. Immediately after adding power, the airplane turned left and he used rudder to correct the left turn but then decided to perform a full stop landing. He applied the brakes in an effort to keep the airplane on the runway, and reduced power, then added a little power inadvertently because he was nervous, then reduced power. The airplane departed the runway, and went into water while traveling about 30 knots. The student pilot further stated there was no preimpact mechanical failure or malfunction. The students’ certified flight instructor stated that after veering to the left, the airplane exited the runway onto grass, crossed runway 25, and then went into a ditch at which time he heard power applied. He then watched the airplane travel into the water and ran to the airplane to assist his student. Postaccident inspection of the flight controls by a Federal Aviation Administration airworthiness inspector revealed no evidence of preimpact failure or malfunction.

Flight

Event TypeAccident
Event Time18:55 EDT
Nearest AirportAlbert Whitted Airport (0nm)
Runway36
Runway Length2864 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172S
Tail NumberN2468Z
Aircraft CategoryAir
DamageSubstantial
OperatorBay Air Flying Service
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-L2A · Reciprocating · 180
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind340° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point46
Altimeter29.96 inHg
Observation Time22:56
Weather SourceWFAC

Appendix: Source Data