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 25, 2010 · Cessna 172S · N172CY

Santa Maria, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 25, 2010
Injury Outcomes
No injuries (1 uninjured)
Location
Santa Maria, CA
Aircraft
Cessna 172S
Tail Number
N172CY
Operator
Pacific Aerocademy
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR10CA475

The solo student pilot reported that he made a 40 minute flight to the destination airport in order to meet a family member for lunch. In order to initiate the landing flare, he pulled back on the control yoke, but the airplane's nose pitched up more than he expected. The pilot stated that he corrected for the higher than expected pitch attitude by pushing forward on the yoke, resulting in the airplane's nose wheel being "dropped" onto the runway surface. After contacting the runway surface, the nose wheel porpoised (bounced) one time before contacting the surface a final time. The pilot was ultimately able to stabilize the airplane by applying back pressure to the control yoke. Although he did not become aware of it until he returned to his initial point of departure, the airplane's nose wheel had struck the runway surface with sufficient force to buckle the lower part of the firewall and the forward portion of the floorboard. The propeller had also come in contact with the runway surface. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C

Full Narrative

The solo student pilot reported that he made a 40 minute flight to the destination airport in order to meet a family member for lunch. In order to initiate the landing flare, he pulled back on the control yoke, but the airplane's nose pitched up more than he expected. The pilot stated that he corrected for the higher than expected pitch attitude by pushing forward on the yoke, resulting in the airplane's nose wheel being "dropped" onto the runway surface. After contacting the runway surface, the nose wheel porpoised (bounced) one time before contacting the surface a final time. The pilot was ultimately able to stabilize the airplane by applying back pressure to the control yoke. Although he did not become aware of it until he returned to his initial point of departure, the airplane's nose wheel had struck the runway surface with sufficient force to buckle the lower part of the firewall and the forward portion of the floorboard. The propeller had also come in contact with the runway surface. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident.

Flight

Event TypeAccident
Event Time13:00 PDT
Nearest AirportSanta Maria Public (0nm)
Runway30
Runway Length6304 ft
Runway Width150 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172S
Tail NumberN172CY
Aircraft CategoryAir
DamageSubstantial
OperatorPacific Aerocademy
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO360 SER A&C · Reciprocating · 200
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data