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 1, 2022 · Pitts S1 S · N23RS

Sturgeon Bay, WI

Overview

Report Status
Probable Cause
Event Type
Accident
Date
July 1, 2022
Injury Outcomes
1 injury (1 minor injury)
Location
Sturgeon Bay, WI
Aircraft
Pitts S1 S (1981)
Tail Number
N23RS
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CEN22LA302

The pilot reported that during landing touchdown with all three wheels “down,” and the airplane “tracking fine,” he removed his feet from the lower rudder pedal bars to apply braking via the upper braking pedal bars. The pedals then fell rearward toward the pilot and his right foot got wedged between the lower rudder pedal bar and the upper braking pedal bar. The pilot reported this action caught him by surprise and he applied “heavy” right rudder, thinking it was braking application. The airplane departed the right side of the runway, nosed over, and came to rest inverted in the grass next to the runway. The airplane sustained substantial damage to the top right wing and the empennage. The pilot reported there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot reported that he had recently purchased the airplane and did not know that the rudder pedal return springs were not installed. The investigation revealed that the airplane was previously modified for aerobatic competition with the addition of a large rudder and that due to cockpit spacing limitations, the rudder pedal return springs could not be installed. The pilot concluded that the accident could have been prevented by performing a “very thorough” inspection and understanding all the modifications made to the airplane before flying it.

NTSB Probable Cause

The pilot’s failure to maintain airplane control during landing, which resulted in a runway excursion and nose over. Contributing to the accident was the pilot’s inadequate preflight inspection and the pilot’s lack of flight control system knowledge.

Full Narrative

The pilot reported that during landing touchdown with all three wheels “down,” and the airplane “tracking fine,” he removed his feet from the lower rudder pedal bars to apply braking via the upper braking pedal bars. The pedals then fell rearward toward the pilot and his right foot got wedged between the lower rudder pedal bar and the upper braking pedal bar. The pilot reported this action caught him by surprise and he applied “heavy” right rudder, thinking it was braking application. The airplane departed the right side of the runway, nosed over, and came to rest inverted in the grass next to the runway. The airplane sustained substantial damage to the top right wing and the empennage. The pilot reported there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot reported that he had recently purchased the airplane and did not know that the rudder pedal return springs were not installed. The investigation revealed that the airplane was previously modified for aerobatic competition with the addition of a large rudder and that due to cockpit spacing limitations, the rudder pedal return springs could not be installed. The pilot concluded that the accident could have been prevented by performing a “very thorough” inspection and understanding all the modifications made to the airplane before flying it.

Flight

Event TypeAccident
Event Time15:00 CDT
Nearest AirportDoor County Cherryland (0nm N)
Runway02
Runway Length4000 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPitts S1 S
Tail NumberN23RS
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming Engines · IO-360 Series · Reciprocating · 180
Seats1

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 73 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 8 kt, gusting 14 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point52 F
Altimeter29.95 inHg
Observation Time14:56
Weather SourceWFAC

Appendix: Source Data