NTSB CAROL · Event
Event ERA22LA379
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
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or 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 ↗.
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.