N193AZSteve P Peltekian ROTORWAY 162F · 2012

On July 29, 2023, about 1227 central daylight time (CDT), a Rotorway 162F helicopter, N193AZ, and an ELA Eclipse 10 gyroplane, N221EL, were involved in a midair collision near Oshkosh, Wisconsin. The helicopter was destroyed, and the pilot and passenger were fatally injured. The gyroplane was destroyed, and the pilot and passenger received serious injuries. Both aircraft were operated as Title 14 Code of Federal Regulations Part 91 personal flights.

On the morning of the accident, both pilots attended an Experimental Aircraft Association (EAA) AirVenture Oshkosh Ultralight/Homebuilt fun fly zone (FFZ) daily rotorcraft briefing. A witness, who attended multiple daily rotorcraft briefings, reported that the briefings contained concerns from other pilots related to gyroplane operations. The gyroplane pilots were told by event coordinators, in part, to stop performing 360° turns and spirals while in the traffic pattern. In addition, coordinators repeated their daily request for pilots to communicate their intentions in the traffic pattern.

According to onboard GPS and Automatic Dependent Surveillance-Broadcast (ADS-B) data, the gyroplane departed Wittman Regional Airport (OSH), Oshkosh, Wisconsin, runway 36, traveled to the south, west, and back to the north to enter the ultralight/homebuilt rotorcraft runway traffic pattern near the intersection of Highway 26 and County Road N. According to ADS-B data and an onboard GoPro video camera, the helicopter departed the designated rotorcraft takeoff and landing zone, which was located to the west of the ultralight/homebuilt runway and began a left circuit in the rotorcraft short traffic pattern.

About 35 seconds before the collision, the rear seat passenger in the gyroplane began taking a video with his cellular phone camera. At this time, the gyroplane was on the base leg from the south and began a 360° left turn. The helicopter, which was positioned behind the gyroplane in the traffic pattern, was also approaching the runway on the base leg from the south, following the north/south paved road (see figure 1).

Figure 1. Flight tracks of the helicopter (red) and gyroplane (yellow).

The GoPro video showed that the helicopter’s right-seat occupant flinched as the undercarriage and right side of the gyroplane, crossing from the left to the right in a left bank, are first visible though the helicopter windscreen. Three tenths of a second later, there was a sound of impact. At the time of the impact, the helicopter was at zero roll angle, the flight instruments indicated the helicopter was about 225 ft above ground level in a 200 ft-per-minute descent at an indicated airspeed of 77 mph, and the engine instruments were in the green range.

A witness reported that he observed two helicopters that were in front of the accident gyroplane; one helicopter was on the base leg to final approach, and one helicopter was on final approach. He reported that the accident gyroplane “made a hard 180° turn in the pattern, on a base leg over the trees, to what [he] thought was a go around for spacing.” The witness did not observe the collision between the gyroplane and helicopter, but heard a loud bang, and then noticed aircraft debris falling to the ground.

Both aircraft descended in a near-vertical attitude with debris separating from both aircraft. The helicopter impacted terrain, came to rest inverted, and a postaccident fire ensued (see figure 2). The gyroplane impacted an unoccupied airplane that was parked between the north/south paved road and runway 36L (see figure 3). No ground injuries were reported.

Figure 2. Helicopter as it came to rest

Figure 3. Gyroplane and unoccupied parked airplane

A review of the GPS data from the gyroplane revealed that, the day before the accident, the pilot had performed a 360° turn near the northwest end of the ultralight/homebuilt runway.

The helicopter pilot had attended and flown for several years at the EAA AirVenture Oshkosh FFZ. The pilot was described by fellow FFZ pilots as very respected among his peers, assisted in the daily pilot briefings, and was considered an air safety advisor to the flight operations.

The gyroplane pilot reported that, due to his injuries, he had no recollection of the accident flight. EAA AirVenture 2023 was the gyroplane pilot’s first event in which he flew his gyroplane. The pilot had flown the accident gyroplane at the FFZ the day before the accident.

The gyroplane passenger, who was seated in the rear seat, reported that he had not previously met the pilot before the flight, and he was a passenger for a demonstration flight. The passenger was provided a headset for the flight and could communicate with the pilot via the headset. He reported that, while coming into land, the pilot performed “an impressive tight left turn.” He was not aware of the reason for the left turn.

Postaccident examination of the helicopter revealed that both outboard sections of the main rotor blades were separated and came to rest in the debris field (see figure 4). The main rotor blade’s structure displayed impact marks and white paint transfers, consistent with the gyroplane’s structure and paint color.

The gyroplane’s right horizontal and vertical stabilizers displayed shear cuts and separated structure consistent with helicopter main rotor blade contact (see figure 5). The gyroplane’s main rotor mast was separated about mid-length with an impact signature consistent with the helicopter’s main rotor blade (see figure 6).

Examination of both aircraft revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.

Figure 4. Separated outboard sections of the helicopter’s main rotor blades.

Figure 5. The upper photograph depicts the gyroplane’s separated right horizontal stabilizer and lower vertical stabilizer. The lower photograph depicts the separated stabilizer section in comparison with the helicopter main rotor blade contact witness marks and white paint transfer.

Figure 6. Gyroplane’s separated rotor mast section and the helicopter’s main rotor blade contact witness mark.

The EAA AirVenture Oshkosh FFZ provides flight operations opportunities for powered parachutes, ultralight and light airplanes, and rotorcraft during the mornings and evenings of the EAA AirVenture Oshkosh fly-in event. The operations are typically conducted at the designated ultralight/homebuilt rotorcraft runway and rotorcraft landing zone. Flight operations are divided into separate time periods to allow similar performance aircraft in the traffic pattern at the same time. Pilot briefings for each type of flight operation were conducted each morning of the event and were required attendance for piloting an aircraft at the FFZ.

During the morning rotorcraft briefings, an information sheet was provided to the attendees that included information related to flight operations and emergencies. In reference to potential traffic congestion while in the traffic pattern, pilots were verbally briefed not to perform a 360° turn for spacing, but to execute a side-step maneuver and perform another traffic pattern circuit. In addition, pilots were verbally briefed and provided a visual map on a short traffic pattern that would be communicated and implemented by the flight operations air boss. The decision to transition from the longer traffic pattern to the shorter traffic pattern during the rotorcraft flight operation’s time period was at the discretion of the air boss. For aircraft equipped with a radio, pilots would typically announce their position in relation to certain landmarks, and their intention to conduct either a low pass, high pass, or full-stop landing.

Following the accident, the EAA implemented the following changes to the procedures and operations at the FFZ:

- Standardized briefing for all types of FFZ operations

- Standardized traffic pattern for all types of FFZ operations with exception of the powered-parachutes group due to speed performance

- Standardized aircraft spotter locations for all types of FFZ operations

- Implemented and designated a sterile corridor for traffic on base leg over the north/south paved road

- Employed a 1-strike rule for anyone that does not conform to FFZ procedures and operations

The National Transportation Safety Board (NTSB) Vehicle Recorder Division received video files from a GoPro camera that was recovered from the helicopter, and a cellular phone camera video that was obtained from the gyroplane passenger. The timing of the files was correlated with local time by using the time of the impact on each video and aligning that event with available GPS and ADS-B data that showed when the aircraft collided. The Vehicle Recorder Division provided a summary of the recorded content.

An autopsy of the helicopter pilot was performed by the Walworth County Medical Examiner. The autopsy report was reviewed by the NTSB Investigator-In-Charge. According to the autopsy report, the cause of death was multiple blunt force injuries, and the manner of death was accident.

Toxicology testing performed at the FAA’s Forensic Sciences Laboratory found salicylic acid, metoprolol, rosuvastatin, and valsartan in the pilot’s blood and liver. Salicylic acid is a metabolite of aspirin and used to treat minor pain and as an antiplatelet medication to prevent blood clots. Metoprolol is a beta blockage prescription medication that is used to treat high blood pressure and to prevent heart attacks in patients with coronary artery disease. Rosuvastatin is a prescription medication used to treat high cholesterol. Valsartan is a prescription medication used to treat high blood pressure. None of these medications are known to adversely affect performance.