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

June 4, 2013 · Piper PA-28-140 · N5808U

Burlington, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 4, 2013
Injury Outcomes
No injuries (1 uninjured)
Location
Burlington, WA
Aircraft
Piper PA-28-140 (1970)
Tail Number
N5808U
Operator
Morrissey William T Trustee
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR13LA262

During the landing roll, the airplane began to veer right, and the pilot applied left rudder and left braking action to align the airplane with the runway; however, both actions were ineffective. The airplane departed the right side of the runway and impacted an airport sign and a ditch. Postaccident examination of the left rudder bar assembly found that it had failed due to a fatigue crack. A rusted brown oxidized area near the center of the crack and surface features consistent with slow-growth fatigue indicated that the crack had been growing incrementally over a period of years. A review of the manufacturer's periodic inspection checklist, maintenance manual, and Service Letter No. 671 indicated that the rudder bar assembly should be inspected every 100 hours specifically for cracks in the area where the airplane's rudder bar failed. If maintenance personnel had inspected the airplane in accordance with these documents, the crack likely would have been found and the accident prevented.

NTSB Probable Cause

The failure of the rudder bar assembly during landing due to a fatigue crack. Contributing to the accident was the failure of maintenance personnel to perform an adequate inspection of the rudder bar assembly.

Full Narrative

On June 4, 2013, at about 0930 Pacific daylight time, a Piper PA-28-140, N5808U, was substantially damaged when it struck an airport sign following a loss of directional control during landing roll at Skagit Regional Airport, Burlington, Washington. The private pilot, the sole occupant, was not injured. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the personal cross-country flight, which had originated from Friday Harbor, Washington, approximately 20 minutes before the accident. A flight plan had not been filed. The pilot said that while on landing roll, he applied left rudder to straighten the airplane, with no response. He said he attempted to correct the right veering tendency with left braking action, and that was ineffective as well. The airplane departed the right side of the runway and impacted an airport sign and a ditch, which damaged the right wing. Postexamination of the left rudder control bar found that it had failed. Examination of the rudder control bar at the NTSB Materials Laboratory found a fatigue crack, which originated from the edge of a weld. There was a rusted brown oxidized area near the middle of the crack, and the surface of this area had topography and crack patterns consistent with slow growth fatigue progressing from the exterior surface radially through the tube wall. The airplane was manufactured in 1970, and according to the owner, it had an airframe total time of 3,479 hours when the accident occurred. The most recent annual inspection was completed on May 25, 2013. A review of the Piper Aircraft's periodic inspection checklist, maintenance manual, and Service Letter No. 671 dated October 5, 1973, indicated that the rudder bar assembly should be inspected every 100 hours specifically for cracks in the area where the airplane's rudder bar failed. Further, the Service Letter stated that these periodic inspections could be discontinued if two reinforcement doublers were fabricated and welded to the rudder bar in the affected area. There were no reinforcement doublers on the airplane's rudder bar.

Flight

Event TypeAccident
Event Time09:30 PDT
Nearest AirportSkagit Regional Airport (1nm)
Runway11
Runway Length5477 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-140
Tail NumberN5808U
Aircraft CategoryAir
DamageSubstantial
OperatorMorrissey William T Trustee
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 160
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind300° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point63 F / 55
Altimeter30.15 inHg
Observation Time16:35
Weather SourceWFAC

Appendix: Source Data