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 6, 2016 · Cessna 172 S · N5275S

Payson, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 6, 2016
Injury Outcomes
No injuries (1 uninjured)
Location
Payson, AZ
Aircraft
Cessna 172 S (2002)
Tail Number
N5275S
Operator
Westwind School of Aeronautics
Injuries
None
Aircraft Damage
Substantial
NTSB Number
GAA16CA188

According to the student pilot, during landing on his solo flight the airplane porpoised. He reported that after landing he repositioned the airplane, but prior to takeoff, a fellow pilot, who witnessed the porpoise, contacted him on the VHF radio, and informed him that he should have the airplane checked out before attempting to takeoff. The student pilot taxied to the parking area and the airport manager and airframe and powerplant mechanic inspected the airplane. The student pilot called his flight instructor and conveyed the situation and the level of damage. However, according to the flight instructor, the student pilot only conveyed the damage to the tail skid. The flight instructor reported that he told the student to confer with the mechanic and determine if the airplane was airworthy. The student pilot departed and proceeded to the airport where his flight school was based. Shortly after the departure, the airport manager that looked the airplane over for the student pilot, called the flight school and conveyed the gravity of the situation and informed the school that the airplane actually sustained damage to the firewall, tail skid and rudder fairing. The flight instructor did not confer with anyone other than the student pilot to ensure the airplane was airworthy. The airplane sustained substantial damage to the fire wall. The student pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.

NTSB Probable Cause

The student pilot's failure to maintain pitch control during the landing flare, resulting in the subsequent porpoise during landing and substantial damage to the firewall.

Full Narrative

According to the student pilot, during landing on his solo flight the airplane porpoised. He reported that after landing he repositioned the airplane, but prior to takeoff, a fellow pilot, who witnessed the porpoise, contacted him on the VHF radio, and informed him that he should have the airplane checked out before attempting to takeoff. The student pilot taxied to the parking area and the airport manager and airframe and powerplant mechanic inspected the airplane. The student pilot called his flight instructor and conveyed the situation and the level of damage. However, according to the flight instructor, the student pilot only conveyed the damage to the tail skid. The flight instructor reported that he told the student to confer with the mechanic and determine if the airplane was airworthy. The student pilot departed and proceeded to the airport where his flight school was based. Shortly after the departure, the airport manager that looked the airplane over for the student pilot, called the flight school and conveyed the gravity of the situation and informed the school that the airplane actually sustained damage to the firewall, tail skid and rudder fairing. The flight instructor did not confer with anyone other than the student pilot to ensure the airplane was airworthy. The airplane sustained substantial damage to the fire wall. The student pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.

Flight

Event TypeAccident
Event Time08:45 MST
Nearest AirportPAYSON (0nm NE)
Runway06
Runway Length5504 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 S
Tail NumberN5275S
Aircraft CategoryAir
DamageSubstantial
OperatorWestwind School of Aeronautics
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 30 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind20° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F / 9 C
Altimeter30.37 inHg
Observation Time15:35
Weather SourceWFAC

Appendix: Source Data