NTSB CAROL · Event
Event GAA16CA517
Aircraft involved
Probable cause & findings
The pilot's failure to maintain adequate separation and visual lookout during landing, which resulted in his airplane colliding with the airplane ahead of it on the runway.
Factual narrative
The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface. The pilots of two biplanes involved in a collision on a runway during landing, reported that they were landing after competing in a National Championship Biplane Gold Race. The pilot of the Mong reported that he had seen the Pitts biplane ahead of him in the pattern, followed him through his base and final approach legs, and witnessed the Pitts land on the runway. The pilot of the Mong further reported that his biplane had bounced during his initial touchdown on the runway and he added power to correct for the discrepancy and to land in a three-point attitude. The pilot of the Mong reported that he had lost sight of the Pitts biplane during the landing and did not see it again until the impact. The Mong's right wing struck the Pitt's left wing. The Mong spun 180 degrees and slid backwards for 100 yards, during which time the tailwheel snapped in half, and the Pitts was also spun around on the runway. The pilot of the Pitts biplane reported that he had landed and started a right turn off of the runway onto the taxiway when his airplane was struck from behind on its left wing. Both biplanes received substantial damage. Both of the biplane pilots reported that there were no pre impact mechanical failures or malfunctions with their airframe or engine that would have precluded normal operation. The pilot of the Mong also reported that he never heard a call on the radio to go around due to the spacing between the two landing biplanes. Currently the race organizers are looking into a revised recovery procedure to ensure that runways are declared clear before subsequent aircraft touchdown on the runway surface. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
- — Personnel issues-Task performance-Use of equip/info-Use of policy/procedure-Flt operations/dispatcher
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
- — Personnel issues-Task performance-Use of equip/info-Use of policy/procedure-Flt operations/dispatcher
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA16CA517.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.