NTSB CAROL · Event
Event SEA04LA129
Aircraft involved
Probable cause & findings
Clearance was not maintained during taxi to the runway by the pilot of another aircraft which resulted in an on ground collision with the aircraft standing on the runway. The aircraft standing on the runway was a factor.
Factual narrative
On July 10, 2004, about 1735 Pacific daylight time, an experimental Fitz Starduster SA300, N328SF collided with an experimental Logston Starduster SA100DL, N35RL, while both aircraft were taxiing onto the runway at Arlington Municipal Airport, Arlington, Washington. Both aircraft were owned and piloted by the private pilots as 14 CFR Part 91 pleasure flights. Visual meteorological conditions prevailed at the time and no flight plan was filed for either aircraft. The Starduster SA300 received minor damage while Starduster SA100DL was substantially damaged. Neither pilot was injured. The aircraft were preparing for departure as a flight of two with a destination to Hoquiam, Washington. In a written statement, the pilot of the Starduster SA100DL reported that he and the pilot of a Starduster SA300 were to be a flight of two for takeoff. The pilot reported that he was in the lead during the taxi to runway 34, with the Starduster SA300 trailing. The pilot of the Starduster SA100DL was waived onto the runway by one of several flagmen that were directing aircraft for takeoff. This was the end of the air show that had been ongoing for several days. Flagmen were used to direct aircraft from parking, taxi and takeoff. The Starduster SA100DL pilot reported that a flagman on the runway waived him to the right side of the runway centerline and then a second flagman motioned him to a point to stop. A few seconds after he stopped at the designated point, the trailing Starduster SA300 collided into the left wings of the Starduster SA100DL. In a written statement, the pilot of the Starduster SA300 reported that the flagmen on the runway did not let the aircraft enter the runway the same as they had been doing during the air show for a flight of two. The preceding aircraft was stopped shorter than they had been doing. When the pilot of the Starduster SA300 was waived on, his aircraft collided with the left wings of the preceding Starduster SA100DL. Both top and bottom left wing spars of the Starduster SA100DL were broken, as well as ribs, flying wire and cable. The Starduster SA300 received minor damage. The pilot of the Starduster SA100DL reported that he and the pilot of a Starduster SA300 were to be a flight of two for takeoff. The pilot reported that he was in the lead during the taxi to runway 34, with the Starduster SA300 trailing. The pilot of the Starduster SA100DL was waived onto the runway by one of several flagmen that were directing aircraft for takeoff. This was the end of the air show that had been ongoing for several days. Flagmen were used to direct aircraft from parking, taxi and takeoff. The Starduster SA100DL pilot reported that a flagman on the runway waived him to the right side of the runway centerline and then a second flagman motioned him to a point to stop. A few seconds after he stopped at the designated point, the trailing Starduster SA300 collided into the left wings of the Starduster SA100DL. The pilot of the Starduster SA300 reported that the flagmen on the runway did not let the aircraft enter the runway the same as they had been doing during the air show for a flight of two. The preceding aircraft was stopped shorter than they had been doing. When the pilot of the Starduster SA300 was waived on, his aircraft collided with the left wings of the preceding Starduster SA100DL. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_SEA04LA129.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.