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

September 19, 2021 · Cessna 172N · N4977G

Grass Valley, CA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
September 19, 2021
Injury Outcomes
No injuries (1 uninjured)
Location
Grass Valley, CA
Aircraft
Cessna 172N (1979)
Tail Number
N4977G
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR21LA348

The pilot reported that, he departed normally to fly the airport traffic pattern. After he turned to the base leg of the traffic pattern, he observed a low voltage indication on the annunciator panel and was unable to announce his base turn on the radio. The pilot then turned to the final approach leg of the traffic pattern without making the announcement on the radio and added three notches of flaps. He experienced “windshear” near the runway threshold and the airplane briefly ascended. The pilot attempted to regain his glide path by extending full flaps and the airplane floated down the runway. At the time he was concerned about climbing out, so he elected to continue the landing instead of performing a go-around. After the airplane eventually touched down on the runway, the pilot applied full braking, but the airplane skidded off the runway edge into a ditch, which resulted in substantial damage to the right wing. According to the pilot, he misjudged the landing distance and landed long to salvage the landing instead of attempting a go-around. He further remarked that the electrical issue affected his radio and prevented him from announcing his base and final turns in the airport traffic pattern, which may have influenced his decision to land promptly. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

NTSB Probable Cause

The pilot’s failure to attain a proper touchdown point on the runway while landing in gusting wind conditions, which resulted in a runway overrun. Contributing to the accident was the pilot’s distraction due to an electrical issue.

Full Narrative

The pilot reported that, he departed normally to fly the airport traffic pattern. After he turned to the base leg of the traffic pattern, he observed a low voltage indication on the annunciator panel and was unable to announce his base turn on the radio. The pilot then turned to the final approach leg of the traffic pattern without making the announcement on the radio and added three notches of flaps. He experienced “windshear” near the runway threshold and the airplane briefly ascended. The pilot attempted to regain his glide path by extending full flaps and the airplane floated down the runway. At the time he was concerned about climbing out, so he elected to continue the landing instead of performing a go-around. After the airplane eventually touched down on the runway, the pilot applied full braking, but the airplane skidded off the runway edge into a ditch, which resulted in substantial damage to the right wing. According to the pilot, he misjudged the landing distance and landed long to salvage the landing instead of attempting a go-around. He further remarked that the electrical issue affected his radio and prevented him from announcing his base and final turns in the airport traffic pattern, which may have influenced his decision to land promptly. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time15:30 PDT
Nearest AirportNevada County (0.1nm E)
Runway07/2
Runway Length4657 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172N
Tail NumberN4977G
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-H2BD · Reciprocating · 160
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
WindGusting 11 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F / 43 F
Altimeter30.10 inHg
Observation Time15:35
Weather SourceWFAC

Appendix: Source Data