Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 18, 2022 · Robinson Helicopter R44 · N4050P

Las Vegas, NV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 18, 2022
Injury Outcomes
No injuries (3 uninjured)
Location
Las Vegas, NV
Aircraft
Robinson Helicopter R44 (2020)
Tail Number
N4050P
Operator
Southern Utah University
Injuries
None
Aircraft Damage
Minor
NTSB Number
WPR23LA041

The student pilot in the helicopter was conducting his first solo flight in the airport traffic pattern at a towered airport. The student pilot was cleared by the local LC2 controller (controller) to depart from taxiway Papa, which parallels the north side of runway 30R, and to fly the taxiway Papa option, which was a closed traffic pattern to the taxiway. After several successful full-stop landings to taxiway Papa, 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. However, the helicopter pilot reported that he mistakenly flew an approach to runway 30R, rather than taxiway Papa; he then 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 then collided with the aft section of the skids and the helicopter pitched up, rotated left about 90° and landed upright on the runway. The accident airplane was on a right downwind to land on runway 30R when the controller advised the pilot of the helicopter traffic operating on taxiway Papa. The airplane pilot stated that she made visual contact with the helicopter and that it appeared to be operating on taxiway Papa. During the turn onto the base leg for runway 30R, the right wing blocked the instructor’s view of the runway and she lost sight of the helicopter. The instructor stated that as they turned onto final approach, she was assisting the student in maintaining airspeed and the glide slope while managing the flap setting. She stated that a moment later, while approaching the runway threshold, 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 recalled that it was too late to abort the landing by the time she realized the helicopter’s position, 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, sustaining substantial damage to the spar. After hearing the helicopter’s call sign to acknowledge the instruction, the controller repeated the instruction and “observed [the] helicopter hovering over Taxiway Papa very slowly drifting towards a right turn on Kilo.” After walking across the tower to view an aircraft entering the pattern, she returned to observe that the Cessna had, “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. The student pilot’s mistaken approach to runway 30R, rather than the taxiway where he was cleared to land (and where he had conducted previous full-stop landings), put him directly in the path of, and facing away from, the approaching airplane.

NTSB Probable Cause

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

Full Narrative

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.

Flight

Event TypeAccident
Event Time10:27 PST
Nearest AirportNorth Las Vegas (0nm E)
Runway30R
Runway Length4199 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftRobinson Helicopter R44
Tail NumberN4050P
Aircraft CategoryHeli
DamageMinor
OperatorSouthern Utah University
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2D · Reciprocating · 180 | Lycoming · O-540-F1B5 · Reciprocating · 260
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 27 · First Class · None
Crew 2Age 38 · None · None
Crew 3Age 33 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point50 F / 18 F
Altimeter30.10 inHg
Observation Time17:53
Weather SourceWFAC

Appendix: Source Data