NTSB CAROL · Event
Event WPR18LA267
Aircraft involved
Probable cause & findings
The pilot of the race 13 airplane's failure to maintain clearance from the race 37 airplane during the closed course air race.
Factual narrative
On September 14, 2018, about 1004 Pacific daylight time, a Aero Vodochody L39C, N139UK, operating as Race 13, and an Aero Vodochody L39, N139PJ, operating as Race 37 collided in midair about 3 miles north of the Reno Stead Airport (RTS), Reno, Nevada. The airline transport pilot of Race 13 and the airline transport pilot of Race 37 were not injured. Race 13 sustained minor damage to the left side of the fuselage and bottom of the left wing; race 37 sustained substantial damage to the right wing and empennage. Race 13 was registered to Black Rock Aero LLC and race 37 was registered to MPE Enterprises Corporation. Both airplanes were operated by the pilots as a Title 14 Code of Federal Regulations Part 91 air race flights. Visual meteorological conditions prevailed, and no flight plan was filed for either airplane, which originated from RTS at 0950.During an in person interview, the pilot of race 13 reported that he was observing the pilot of race 37 flying a tight line on the course and he was observing his line throughout the race, and announced on the race frequency that he was passing race 37 on the right. The pilot said that he had sight of race 37 at all times and that during the 5th lap, in an area of pylon 4, he thought the pilot of race 37 may have rolled right prior to the collision. Following the collision, the pilot of race 13 declared an emergency and landed uneventfully. During an in person interview, the pilot of race 37 reported that during the 4th lap, while passing pylon 7, he recalled hearing the pilot of race 13 state that he was on his right. The pilot said that during the 5th lap, as he was passing pylon 4, it felt like a car crash and that he never saw race 13. Shortly after, he heard the pilot of race 13 declare a mayday and he decided to declare mayday as well, while noting sluggish control responsiveness. The pilot of race 37 was able to land uneventfully. Review of video that was captured by a witness revealed that race 37 appeared to be in a level attitude while nearing pylon 4, and race 13 appeared to be in a slight left bank, behind race 37. Shortly after, race 37 was observed initiating a left bank, while race 13 was rapidly approaching race 37 from behind. Just prior to the collision, race 13 was observed rolling out of the turn to an almost level attitude. Examination of Race 37 revealed that the outboard 24 inches of the right wing and right aileron were separated from the airplane. Additional damage to the bottom portion of the vertical stabilizer and the leading edge of the left horizontal stabilizer was observed. Examination of Race 13 revealed damage to two inspection panels and fairings on the forward left side of the fuselage. During the closed course air race, the pilot of the race 13 airplane announced that he was passing the race 37 airplane on his right. A video recording of the midair collision showed that, as the two airplanes approached one of the racecourse pylons, race 13 was in a slight left bank behind race 37, which was in a level attitude. Shortly after, race 37 initiated a left bank, while race 13 was rapidly approaching race 37 from behind. Just before the collision, race 13 rolled out of the turn to an almost level attitude. The two airplanes then collided, which resulted in damage to the right wing and aileron of race 37 and damage to two inspection panels and fairings on the forward left side of the fuselage of race 13. Both airplanes landed uneventfully after the collision. The pilot of race 13 failed to maintain adequate separation from race 37 while overtaking the other airplane. 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
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
Verbatim from NTSB's published report. Source file
NTSB_2018_WPR18LA267.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.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (midair collision). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Airspace Saturation and Midair Collision Risk: A Case Study at a Class D Airport
Near midair collisions are precursor events to actual collisions and may be an indicator of risk. While previous studies have used reports of near midair collisions to relate factors such as airspace …
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for Urban Air Mobility (UAM)
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for UAM
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2019 · Other - Patent
Apparatus for aiding a pilot in avoiding a midair collision between aircraft
An apparatus for aiding a pilot in avoiding a midair collision between aircraft is described. A protected aircraft carries a transmitter, a transponder, a receiver, and a data processor; and an intrud…
- Embry-Riddle Scholarly Commons 2018 · Journal article (IJAAA)
Evaluating Small UAS Near Midair Collision Risk Using AeroScope and ADS-B
As small unmanned aircraft systems (sUAS) continue to proliferate in the National Airspace System (NAS), near midair collisions are becoming more common.
- NASA NTRS 2011 · Reprint (Version printed in journal)
Midair collisions - The accidents, the systems, and the Realpolitik
Two midair collisions occurring in 1978 are described, and the air traffic control system and procedures in use at the time, human factors implications and political consequences of the accidents are …
Browse the full corpus — academia portal ↗