ERA22LA379
2022-08-20 · Bealeton, Virginia, United States · Minor · 1 aircraft · Status: Completed
Airport 3VA3
Aircraft involved
Probable cause & findings
The pilot of the departing airplane’s failure to see and avoid the landing airplane before takeoff, resulting in a collision with the landing airplane. Contributing was the airport’s failure to encourage pilots to use radios for traffic deconfliction when equipped.
Factual narrative
The vintage biplanes were operating at a private airport that provided airshows and airplane rides to the public. The pilot of the departing airplane taxied for takeoff and was number two behind another airplane that was taxiing ahead of him. At the same time, the pilot of the landing airplane was in the traffic pattern, preparing for landing. Local procedures required landing airplanes to make a low approach to signal airplanes taking off that a landing was imminent; the procedure was implemented because some airplanes at the airport were not equipped with radios. Landing aircraft had the right-of-way over aircraft taking off. The pilot of the landing airplane reported that he performed the required low approach, completed the traffic pattern, and proceeded onto final approach for landing. At the same time, the pilot of the departing airplane taxied onto the runway for takeoff and did not see the low approach by the landing airplane or his subsequent pattern. The pilot of the landing airplane did not see the departing airplane on the runway and landed on top of the departing airplane before the departing airplane became airborne. Both airplanes sustained substantial damage, the two pilots had minor injuries, and two passengers were not injured. Although both airplanes were equipped with radios, neither pilot was making radio calls; instead, they relied on the established visual traffic separation procedures only. A review of the airport’s standard operating procedures revealed that they did not address the use of radios or encourage pilots to use them if equipped. Following the accident, the airport made several modifications to their local procedures including recommending that all pilots of aircraft equipped with radios use them while in the traffic pattern; and moving the holding area short of the runway to another location that afforded better visibility of the traffic pattern. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft
- — Organizational issues-Management-Policy/procedure-Availability of policy/proc-Airport
- — Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot
- — Organizational issues-Management-Policy/procedure-Availability of policy/proc-Airport
Verbatim from NTSB's published report. Source file
NTSB_2022_ERA22LA379.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗