WPR13LA262 · Piper PA-28-140
Morrissey William T Trustee Piper PA-28-140 · Accident: loss of control on ground during landing
From Friday Harbor Airport (FHR) to Skagit Regional Airport (BVS)
Event
- NTSB case
- WPR13LA262
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-28-140
- Aircraft type
- Piper PA-28
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5808U
- Operator
- Morrissey William T Trustee
- Onboard fatalities
- Unknown
- Route
- From Friday Harbor Airport (FHR), Friday Harbor, WATo Skagit Regional Airport (BVS), Burlington, WA
- Aircraft age
- About 43 years (built 1970)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA262
- Event ID
- 20130604X24846
- Case number
- WPR13LA262
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1620853fe6c4445ee6bd29145d465cc71bf77336a45381d5cf2b4423874f149c; retrieved 2026-09-15T21:46:23.845Z.