N4050P

MINR
None

ROBINSON HELICOPTER R44S/N: 30061

Accident Details

Date
Friday, November 18, 2022
NTSB Number
WPR23LA041
Location
Las Vegas, NV
Event ID
20221121106336
Coordinates
36.210703, -115.194440
Aircraft Damage
MINR
Highest Injury
None
Fatalities
0
Serious Injuries
0
Minor Injuries
0
Uninjured
3
Total Aboard
3

Probable Cause and Findings

The student helicopter pilot’s failure to follow the tower controller’s landing instructions, which resulted in a midair collision.

Aircraft Information

Registration
N4050P
Make
ROBINSON HELICOPTER
Serial Number
30061
Engine Type
Reciprocating
Year Built
2020
Model / ICAO
R44R44
Aircraft Type
Rotorcraft
No. of Engines
1

Registered Owner (Historical)

Name
AEROTRUST SERVICES CORP TRUSTEE
Address
251 LITTLE FALLS DR
Status
Deregistered
City
WILMINGTON
State / Zip Code
DE 19808-1674
Country
United States

Analysis

On November 18, 2022, about 1027 Pacific standard time, a Cessna 172M, N88E, and a Robinson R44, N4050P, collided over runway 30R at North Las Vegas Airport (VGT), Las Vegas, Nevada. The flight instructor and student pilot on board the Cessna and the student pilot on board the Robinson were not injured. Both aircraft were operated under the provisions of Title 14 Code of Federal Regulations Part 91 as instructional flights.

There were two helicopters, a Cessna airplane, and a Diamond airplane operating in the airport’s right-hand traffic pattern at the time of the accident. One helicopter, which was alternating turns in the taxiway pattern with the accident helicopter, was waiting on the east ramp for their turn in the pattern. The two airplanes were using right traffic for runway 30R. Taxiway Papa parallels the north side of runway 30R; both runway 30R and taxiway Papa were under control of the LC2 controller at the time of the accident.

The Cessna had completed 3 approaches to runway 30R, including one full-stop and two touch-and-go landings, and the accident helicopter had completed 4 full-stop landings to taxiway Papa before the accident. (See Figure 1.)

[For Figure 1, I suggest using high-res version of Fig. 4 from ATC Factual Report]

At 10:24, the tower controller cleared the Cessna for the option to land on runway 30R; the pilot read back the instructions.

At 10:25, the controller cleared the accident helicopter for takeoff from taxiway Papa, and subsequently cleared the student pilot for the option back to taxiway Papa; the pilot acknowledged the instructions.

At 10:26, the controller advised the Cessna that there was helicopter traffic in a close right base for taxiway Papa, and the pilot replied that they were looking for the helicopter.

At 10:27, the controller instructed the accident helicopter to, when able, make a right turn on taxiway Kilo, and that landing on the east ramp was at the pilot’s own risk. (See Figure 2.) The pilot responded by stating “Las Vegas tower, five zero papa.” The controller again instructed the helicopter pilot to make a right turn onto taxiway Kilo. The pilot did not acknowledge the instruction.

Figure 2. View of initial point of impact in relation to Taxiway Papa, Taxiway Kilo, the East Ramp, and ATC.

The student pilot in the accident helicopter, who was conducting a solo instructional flight, reported that he had departed from taxiway Papa, flew the right-hand traffic pattern, and was instructed by the controller to fly his approach to taxiway Papa. However, he reported that he mistakenly flew his approach to runway 30R and terminated the approach in a hover over the runway. Video surveillance footage shows that the nose of the helicopter was oriented in the landing direction; the student pilot reported being unaware that an airplane was on approach to land on the runway. The airplane collided with the aft section of the skids and the helicopter pitched up, rotated left about 90° and landed upright on the runway.

The instructor in the Cessna stated that, when they were on the downwind leg of the traffic pattern, she had brief visual contact with the helicopter, which appeared to be operating on taxiway Papa. During the turn onto the base leg, the right wing blocked the instructor’s view of the runway. The instructor stated that as they turned onto the final approach she was assisting the student in maintaining airspeed and the glideslope while managing the flap setting. She stated that a moment later she saw the helicopter and it appeared to be hovering over runway 30R, about 100-300 ft past the runway numbers, and not on taxiway Papa. The instructor in the Cessna recalled that it was too late to abort the landing and elected to touch down underneath the helicopter. The airplane’s left wing collided with the skids of the helicopter, the fuselage rotated left, and the wing struck the ground, causing substantial damage to the spar. Subsequently the right wing struck the runway surface before the airplane came to an abrupt stop.

The controller stated that, after instructing the helicopter to turn right onto taxiway Kilo, “I didn’t hear a readback at the time,” but that she “thought that perhaps it was a critical stage of flight for him.” After hearing the helicopter’s call sign to acknowledge the instruction, she repeated the instruction and “observed [the] helicopter hovering over Taxiway Papa very slowly drifting towards a right turn on Kilo.” She continued,

At the time, I had to walk across the tower to find my remaining aircraft in the pattern to make sure that the pattern entry was complete, and I observed the aircraft, the Diamond Star, entering the pattern. And I turned around to walk across the tower to observe my helicopter, and at that time, I saw a helicopter. It appeared that he made, instead of a right turn into the ramp, he made a left turn and was entering the runway.

She then watched as the Cessna “cranked the wheels all the way to the left to avoid the helicopter.” At that time, the helicopter landed on the runway, right in front of the Cessna, and the airplane “tipped on the wing, and for a minute, it looked like it would go upside-down” before turning upright again.

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# WPR23LA041