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 7, 1996 · Cessna 172P · N5394K

Reno, NV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 7, 1996
Injury Outcomes
No injuries (2 uninjured)
Location
Reno, NV
Aircraft
Cessna 172P
Tail Number
N5394K
Operator
Reno Flying Service
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX96LA192

The pilot thought his aircraft was too high as he turned final, but after lowering additional flaps he allowed the aircraft to become too low and slow. When he saw the VASI lights indications he thought that the aircraft might land short. He applied 'some' power but it did not stop the aircraft from sinking. He responded by increasing back pressure in an attempt to increase his glide. He heard the stall warning horn and felt the stall buffet, but did not add any more power because he thought that once the aircraft entered ground effect it would reach the runway. The aircraft stalled, landing hard short of the runway threshold. The aircraft bounced and then struck the raised threshold lip with its right main gear. It settled back on runway 26 and then slid to a stop off the right side. The approach was flown over rising terrain which can give a pilot the illusion that the aircraft is at a higher altitude. If not recognized, this illusion may induce him to maintain a higher pitch attitude resulting in a lower airspeed and an increased rate of descent during an approach.

NTSB Probable Cause

the pilot's failure to obtain and maintain flying speed and a proper glide path, which resulted in an inadvertent stall during a visual approach. An increased altitude illusion created by rising terrain under the final approach course was a factor.

Full Narrative

On May 7, 1996, at 1135 hours Pacific daylight time, a Cessna 172P, N5394K, landed short of the runway while on final approach to Reno-Stead Airport, Reno, Nevada. The aircraft sustained substantial damage; however, neither the certificated private pilot nor his passenger was injured. The aircraft was being operated as a personal flight by Reno Flying Service when the accident occurred. The flight originated in Reno at 1115 on the day of the accident. Visual meteorological conditions prevailed at the time and no flight plan had been filed. The pilot reported to FAA inspectors that he was too high after turning final on runway 26. However, by the time the aircraft was on short final, he said he had allowed the aircraft to get too low and slow. He said he increased back pressure on the control wheel in an attempt to increase his glide rather than adding power. He reported hearing the stall warning horn and feeling the stall buffet, but thought that once the aircraft entered ground effect it would reach the runway. In his written report to the Safety Board, the pilot stated that he prepared the aircraft for landing while on downwind. He slowed the aircraft to 70 knots while at a pattern altitude of 5,800 feet msl. He applied carburetor heat, throttled back to 1,500 rpm, and lowered 10 degrees of flaps. He lowered the flaps to 20 degrees while on his base leg. After rolling out on final approach he lowered the flaps to 30 degrees, but noticed the visual approach slope indicator (VASI) lights were indicating that he was low. In response to being low, he added "some" power. As the aircraft neared the approach threshold, it continued to sink but he did not add power because he thought the aircraft would still be able to touch down on the runway. When he realized that he might land short, he applied back pressure on the controls to raise the nose but the aircraft stalled almost simultaneously. The aircraft landed hard about 10 feet short of the runway threshold, shattering the windscreen. The pilot thought he felt the aircraft bounce and then settle on the runway. He attempted to stay on the runway but the aircraft veered off the right side of the runway as he applied the brakes. The aircraft came to rest about 10 feet off the right side of the runway, 600 feet beyond the runway threshold. The Federal Aviation Administration (FAA) inspector who responded to the accident reported that the aircraft landed about 11 feet short of the threshold of runway 26. After locating the initial impact marks, a second impact mark was found on the 2-inch raised lip on the runway threshold. That mark corresponded to the right main landing gear. The aircraft slid to a stop off the right side of the runway. He reported that the final approach was flown over rising terrain. According to the FAA Airman's Information Manual, ". . . upsloping terrain can create the illusion that the aircraft is higher than it actually is." A postaccident inspection of the aircraft by FAA airworthiness inspectors revealed that the nose gear strut collapsed and the top of the cylinder was separated. The tire on the right main landing gear was ruptured and flat. The aircraft firewall was buckled.

Flight

Event TypeAccident
Event Time11:35 PDT
Nearest AirportReno/Stead (0nm)
Runway26
Runway Length7600 ft
Runway Width150 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN5394K
Aircraft CategoryAir
DamageSubstantial
OperatorReno Flying Service
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D2J · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 32 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind290° @ 5 kt
CeilingNone
Temperature / Dew Point63 F / 0 C
Altimeter0
Observation Time18:00
Weather SourceWFAC

Appendix: Source Data