NTSB CAROL · Event
Event SEA05LA185
Registry · N1829P
FAA Aircraft Registry record.
Make / Model
PIPER PA-22-150
Year of manufacture
1955 · 50 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19560130
ADS-B equipped
Yes — Mode-S A14BBB
Registrant of record
BOLL RYAN C
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Separation of the tailwheel assembly spring resulting in a loss of directional control and subsequent collision with a berm. The berm was a factor in the accident.
Factual narrative
On August 31, 2005, about 1840 Pacific daylight time, a tailwheel equipped Piper PA-22-150, N1829P, sustained substantial damage during the landing rollout at the Mead Flying Service Airport (S70), Mead, Washington. The airplane is registered to the pilot, and was being operated as a visual flight rules (VFR) cross-country flight under the provisions of 14 CFR Part 91, when the accident occurred. The private pilot and passenger were not injured. Visual meteorological conditions prevailed for the flight that originated at Hoskins Field Airport, Olympia, Washington, about 2 hours and 30 minutes prior to the accident. During a telephone conversation with the National Transportation Safety Board IIC, the pilot reported that shortly after touchdown (three-point landing) the airplane developed a significant vibration/shimmy emanating from the area of the tailwheel. He reported that immediately after the onset of the vibration the airplane began to "pull to the right." The pilot applied corrective actions (full left rudder and braking action), however the airplane continued to track to the right and exited the runway edge. After exiting the runway, the airplane collided with a berm and ground looped. During the ground loop, the left wing and tail made ground contact resulting in substantial damage. The pilot reported that a post accident examination of the tailwheel assembly revealed that the left control spring was disconnected. The pilot further stated that he believed the control spring become disconnected as a result of the shimmy during landing. The pilot reported that shortly after touchdown (three-point landing) the airplane developed a significant vibration/shimmy emanating from the area of the tailwheel. He reported that immediately after the onset of the vibration the airplane began to "pull to the right." The pilot applied corrective actions, however the airplane continued to track to the right and exited the runway edge. After exiting the runway, the airplane collided with a berm and ground looped. The pilot reported that a post accident examination of the tailwheel assembly revealed that the left control spring was disconnected. The pilot further stated that he believed the control spring become disconnected as a result of the shimmy during landing. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_SEA05LA185.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.