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

November 21, 2003 · Piper PA-32-300 · N28693

Superior, WI

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 21, 2003
Injury Outcomes
No injuries (1 uninjured)
Location
Superior, WI
Aircraft
Piper PA-32-300
Tail Number
N28693
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CHI04LA034

The airplane collided with a ditch following a loss of directional control while landing. The pilot reported the airplane touched down at an airspeed of 80 to 85 knots. He reported that after a brief landing roll, he tapped the brakes and the airplane pulled to the left toward the grass. The pilot reported he pulled back on the control yoke and applied light brakes as the airplane continued toward the grass. Upon seeing a drainage ditch that was perpendicular to the runway, the pilot applied power and pulled back in an attempt to clear the ditch. The airplane contacted the ditch at which time the landing gear collapsed. Inspection of the airplane's brakes following the accident failed to reveal any mechanical failure/malfunction. Skid marks on the runway matched the track of the right main and nose gears. No tracks from the left main gear were visible until a point where the airplane had traveled into the grass. The pilot made the following recommendation as to how the accident could have been avoided: "Reduce landing touchdown speed, and after landing allow aircraft to runout and burn off speed naturally before applying brakes."

NTSB Probable Cause

The pilot's failure to maintain directional control of the airplane during the landing roll. Factors associated with the accident were the ditch that the airplane contacted.

Full Narrative

On November 21, 2003, at 1125 central standard time, a Piper PA-32-300, N28693, collided with a ditch following a loss of directional control while landing on runway 31(4,000 feet by 75 feet, dry asphalt), at the Bong Airport (SUW), Superior, Wisconsin. The pilot was not injured. The airplane received substantial damage. The 14 CFR Part 91 personal flight was operating in visual meteorological conditions without a flight plan. The flight originated from the Crystal Airport, Minneapolis, Minnesota, at 1020. The pilot reported he "cut power" before landing and the airplane touched down at an airspeed of 80 to 85 knots. He reported that after a brief landing roll, he tapped the brakes and the airplane pulled to the left toward the grass. The pilot reported he pulled back on the control yoke and applied light brakes as the airplane continued toward the grass. Upon seeing a drainage ditch that was perpendicular to the runway, the pilot applied power and pulled back in an attempt to clear the ditch. The airplane contacted the ditch at which time the landing gear collapsed. An inspector from the Federal Aviation Administration Minneapolis, Minnesota, Flight Standards District Office inspected the airplane's brakes following the accident and was unable to detect any mechanical failure/malfunction. The inspector reported that there were skid marks on the runway which matched the track of the right main and nose gears. He stated that there were no tracks from the left main gear until the airplane had traveled into the grass. Winds reported at SUW, 10 minutes prior to the accident, were from 270 degrees at 7 knots. The pilot made the following recommendation as to how the accident could have been avoided. "Reduce landing touchdown speed, and after landing allow aircraft to runout and burn off speed naturally before applying brakes."

Flight

Event TypeAccident
Event Time11:25 CST
Nearest AirportBong Airport (0nm N)
Runway31
Runway Length4000 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-300
Tail NumberN28693
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IOP-540-K1G5 · Reciprocating · 300
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind270° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point34 C / 21 C
Altimeter30.15 inHg
Observation Time17:15
Weather SourceWFAC

Appendix: Source Data