FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA345 · North American T-6G

17 Sept 2023 · Reno, NV, United States

North American T-6G and North American AT-6B · Accident: midair collision on approach

Report a problem

Event

NTSB case
WPR23FA345
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · North American T-6G

Aircraft type
North American T-6
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2897G
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 64 years (built 1959)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern downwind
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · North American AT-6B

Aircraft type
North American AT-6
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N57418
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 81 years (built 1942)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern downwind
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilots of the accident airplanes were participating in a closed-course air race. Both pilots had just completed the race and entered the airport traffic pattern for runway 8. Several witnesses observed the airplanes, Race 14 and Race 6, collide while Race 14 was on the base leg (a southerly heading) and Race 6 was on the downwind leg (a west-southwest heading). Witnesses, including the pilot of another race airplane, reported that Race 14 was on a wide base leg for the runway, while Race 6 was closer in on the downwind leg for the runway. While the exact flight path of each airplane could not be determined, based upon witness and other pilots’ statements, along with Race 14’s radio transmissions, it’s likely that the wider pattern flown by Race 14, and the tighter pattern flown by Race 6, placed Race 14 to the right of Race 6’s flight path. Given the pilot of Race 14’s transmission “base with gear,” it’s likely that the pilot of Race 6 may have been looking to the left for Race 14. Sun data at the time of the accident showed that the center of the sun’s disk would have been ahead and slightly to the right of Race 14’s flight path, and to the left of Race 6’s flight path, about 50° above the horizon. The person who was in the Race Control position reported that he was in the control tower providing advisory functions for the T-6 Gold Race. At the conclusion of the race, after the participants had exited the race course, Race 14 reported midfield abeam for runway 08 (meaning the aircraft was abeam the tower on downwind for runway 8); Race Control then advised Race 14 that he was in the No. 1 position to land. After Race 6 then reported midfield abeam, Race Control advised Race 6 that he was following traffic ahead on downwind. He further stated that when Race 14 reported base and gear, he had cleared him to land on runway 8. Soon after, other aircraft in the cool-down pattern started to report midfield abeam the tower; he advised them of traffic ahead on the downwind. Race Control then observed an aircraft falling from the sky about the location of the base leg for runway 08; he then alerted the people in the tower. Shortly after, he observed a second airplane falling and impacting the ground. A witness located along the edge of airport property captured audio transmissions during the race. The recording includes various transmissions from Race 14 and Race 6. Although there were multiple unintelligible transmissions, no discernible transmissions regarding a traffic alert from Race Control could be identified.

Standard operating procedures outlined the duties for various positions of personnel in the tower at the time of the race along with expected radio transmissions by the pilots and tower controller. The operating procedures provided no distinct procedures for tower personnel to provide traffic separation. Additionally, the air boss stated that it was an expectation but there was no written guidance.

Probable cause

The failure of both the Race 14 and Race 6 pilots to see and avoid each other while in the airport traffic pattern. Contributing to the accident was both pilots’ failure to fly the standard downwind and base legs.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA345
Event ID
20230917193074
Case number
WPR23FA345
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 0f602ded67c46949bac50c312f20b43dadb0bca23b8f24c221f767260798092a; retrieved 2026-09-13T18:11:50.659Z.