Heli Student pilot’s Wrong Turn Triggers Midair collision — Cessna Lands Beneath

The event in context

On 18 November 2022, a training flight at North Las Vegas Airport produced a remarkable midair collision involving a Cessna 172M, N88E, and a Robinson R44, N4050P. Nobody was injured, but the Cessna suffered substantial damage and the helicopter sustained minor damage.

The helicopter student was conducting his first solo traffic-pattern flight. The tower had cleared him to use the Taxiway Papa option, a specialized closed pattern associated with the taxiway. After several successful landings, the controller instructed him to make a right turn at Taxiway Kilo and land on the east ramp at his own risk. The student misunderstood the instruction and positioned the helicopter over the active runway instead.

The NTSB found the probable cause in the helicopter student’s failure to follow the tower controller’s landing instructions. That finding is unusually concrete. The student had been operating in a specialized traffic pattern and was instructed to turn at Taxiway Kilo and land on the east ramp. Instead, the helicopter ended up over the active runway, directly in the path of the Cessna on final.

Reconstructing this flight

The Cessna was approaching Runway 30R on a right downwind/base/final sequence. The instructor had briefly seen the helicopter and believed it was operating where expected. During the base turn, the Cessna’s wing blocked the instructor’s view.

On short final, the instructor suddenly saw the helicopter hovering over the runway. With the aircraft already too close to the helicopter for a normal go-around to guarantee separation, she chose to land beneath it. The Cessna’s left wing struck the helicopter’s skids. The impact yawed the Cessna left and damaged its wing spar. The helicopter pitched and rotated before landing upright.

The physical outcome was fortunate. The timing could easily have produced fatalities.

The Cessna crew then faced a collision that was already physically close. The instructor saw the helicopter late because the aircraft’s structure temporarily blocked the view during the base-to-final transition. On short final, the instructor elected to land underneath the helicopter rather than attempt an aggressive last-second maneuver. The Cessna’s wing struck the helicopter’s skids, while the helicopter remained upright and both aircraft survived.

What the evidence establishes

The NTSB determined that the probable cause was the student helicopter pilot’s failure to follow the tower controller’s landing instructions, resulting in the collision. That finding does not mean the event was caused by one careless individual in isolation. It also demonstrates why traffic-pattern operations use multiple layers of protection: ATC instructions, predictable pattern geometry, visual scanning and pilot cross-checks.

The phrase “Taxiway Papa option” was meaningful to the local operation, but a student pilot who is unsure of an instruction must clarify it before acting. In a training environment, asking “confirm the taxiway option” is far safer than making an assumption.

The Cessna instructor also faced an extremely compressed decision window. Once the helicopter appeared directly ahead, there was no perfect option. The choice to land beneath it avoided a direct collision with the helicopter’s cabin and allowed both aircraft to survive.

The event is valuable because it shows how a misunderstood clearance can defeat several layers of protection at once: the student’s expected path changed, the controller’s mental picture became different from the actual one, and the Cessna crew had only seconds to react. The correct corrective action is not merely ‘look outside more’; it is to clarify the clearance before moving into a different piece of airport airspace.

Investigation and findings

The accident is a strong reminder that airport traffic patterns are three-dimensional. Two aircraft can appear separated on a chart or in a controller’s mental picture and still occupy the same physical space within seconds.

How the Two Aircraft Entered the Same Airspace

The reconstructed sequence can be read as a chain of six decision points: Helicopter pattern work → Instruction misunderstood → Helicopter over active runway → Cessna on final → Wing/skid contact → Both aircraft land. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from helicopter pattern work to both aircraft land. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

The Active-Runway Conflict

The decisive safety issue in this incident was specific to the sequence: Instruction misunderstood; Helicopter over active runway; Cessna on final. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

• https://data.ntsb.gov/
• https://www.faa.gov/airports/runway_safety

Accident Facts