Photo Info

From VFR to IIMC: How small decisions led to the 2020 S-76 helicopter tragedy

By Jop Dingemans and Janine Lythe

Published on: May 1, 2026
Estimated reading time 20 minutes, seconds.

We look at what can be learned from one of the highest-profile accidents in recent memory — the crash of an S-76 in Calabasas, California, which claimed nine lives in January 2020.

The circumstances surrounding the fatal crash of a Sikorsky S-76B on Jan. 26, 2020, which claimed the lives of nine people, including Kobe Bryant and his daughter Gianna, make a lot of pilots uncomfortable. Not because the accident is complicated, or hard to understand, but because it’s a scenario we’ve seen play out time and time again in the rotary industry.

It wasn’t due to a technical issue. The helicopter was perfectly serviceable, flown by an experienced pilot on a route and in an aircraft he knew well, but on a day with marginal weather conditions. The flight ended with the aircraft in a rapidly descending left turn in instrument meteorological conditions (IMC), crashing into terrain in Calabasas, California. 

Let’s go over what happened, why it happened, and what we can learn from it.

Accident Overview

On Jan. 26, 2020, at 9:07 a.m. PST, a Sikorsky S-76B (N72EX), operated by Island Express Helicopters Inc., departed under visual flight rules (VFR) from John Wayne Airport (SNA) in Orange County, California. (Image 1)

Its destination was Camarillo Airport (CMA), in Camarillo, California, which is about 24 miles west of the accident site. (Image 2).

After departing SNA, the helicopter mainly flew at altitudes between 400 to 600 feet (120 to 180 meters) AGL (above ground level), always remaining below 1,700 ft (520 m) AMSL (above mean sea level).

At 09:20:14, 8.5 miles (13.6 kilometers) southeast of Bob Hope Airport (BUR), the pilot requested special VFR clearance through the BUR airspace. (Image 3)

Air traffic control (ATC) requested the pilot to hold outside the airspace due to traffic. After a few holds, the helicopter progressed through controlled airspace without any issues. (Image 4)

At the start of the transit, ATC advised the pilot of the following weather conditions:

Image 2

Overcast ceiling at 1,100 ft
(335 m) AGL

Visibility of 2.5 miles
(4.5 km) with haze

Cloud tops at 2,400 ft
(730 m) msl

After transiting BUR airspace, the helicopter started following US Route 101 (US 101) westbound. Image 5 is a picture taken at 09:44:20 by CCTV cameras from the US101, showing the local conditions.

At 09:44:34 (about two minutes before the accident), the helicopter was still flying west at an altitude of about 1,370 ft (420 m) msl, 450 ft (135 m) agl over US 101 and rising terrain. (Image 6)

The pilot announced to ATC that he was initiating a climb to get the helicopter “above the cloud layers,” and the helicopter immediately began climbing at a rate of about 1,500 ft (460 m) per minute.

Image 3

At about the same time, the helicopter began a gradual left turn, and its flight path generally continued to follow US 101. (Image 7)

About 36 seconds later and while still climbing, the helicopter began to turn more tightly to the left, and its flight path diverged from its overflight of US 101. The helicopter reached an altitude of about 2,370 ft (725 m) msl (about 1,600 ft/490 m agl) at 09:45:15, and then began to descend rapidly while in a left turn. (Image 8)

At 09:45:17 (during the descent), the air traffic controller asked the pilot to “say intentions,” and the pilot replied that he was “climbing to 4,000 ft.”

A witness near the accident site heard the helicopter, then saw it emerge from the bottom of the cloud layer in a left-banked descent about one or two seconds before impact. About three minutes after impact, a ground witness managed to capture a photo (Image 9) of the accident site.

Al nine occupants were fatally injured, and the helicopter was destroyed.

Image 4

Investigation Findings

The investigation team was able to confirm that the accident included:

No mechanical failures

No medical issues

No drugs, alcohol, or fatigue

No evidence of direct pressure from the company or client

So, what happened? The report states:

“The probable cause of this accident was the pilot’s decision to continue flight under visual flight rules into instrument meteorological conditions, which resulted in the pilot’s spatial disorientation and loss of control.”

Image 5

And:

“Contributing to the accident was the pilot’s likely self-induced pressure and the pilot’s plan continuation bias, which adversely affected his decision-making, and Island Express Helicopters Inc.’s inadequate review and oversight of its safety management processes.”

What can we learn from it? Firstly, the weather risk was underestimated. The pilot completed a flight risk assessment earlier that morning and it came out as “low risk.”

However, the updated weather before departure would have triggered a higher level of scrutiny and required an alternate plan. That reassessment didn’t happen, partly because it wasn’t clear that it had to.

Before departing, the pilot did mention to the air charter broker that his intention was to go “up and around” the weather.

The NTSB said there was no record that the pilot obtained a formal preflight weather briefing for the accident flight “either directly from the flight services provider, through his ForeFlight application, or from a third-party vendor.”

Image 6

The NTSB also noted the benefits of a mandatory safety management system, which would have helped prevent a situation like this.

The problem with flights like these around unconventional terrain was highlighted by a weather service forecaster the NTSB spoke with.

“The area it was approaching at that time often had cloud ceilings and visibilities that were lower than the areas to the east when regional weather conditions like those that existed on the day of the accident were present.”

Image 7

The next problem was the inadvertent entry into IMC, which caused spatial disorientation. By the time the decision to climb was made, the aircraft was already entering cloud. The pilot didn’t slow down, maneuver away, or land.

“The pilot’s poor decision to fly at an excessive airspeed for the weather conditions was inconsistent with his adverse-weather-avoidance training and reduced the time available for him to choose an alternative course of action to avoid entering IMC,” the NTSB concluded.

Climbing rapidly into cloud while turning removed all external visual references. This created the perfect conditions for vestibular illusions and spatial disorientation, which quickly led to loss of control.

Image 8

The NTSB also noted that the pilot’s decision to continue into deteriorating weather didn’t match his usual judgment. They concluded it was likely driven by self-induced pressure, no clear Plan B, and classic plan continuation bias, especially as the destination got closer.

The report notes: “At the time that the flight began entering IMC, it was only about 25 miles from CMA (the destination), which had been reporting weather conditions above the basic VFR minimums since before the accident flight departed.”

And:

“With plan continuation bias, the closer the pilot gets to the destination, the stronger the bias becomes.”

The existence of external pressure is tricky to determine, as it’s almost impossible to provide accurate and objective evidence of what company cultures are like, and how pilot minds are influenced overall.

However, the NTSB notes there was:

No pressure from the company

No pressure from the client

No pressure from the broker

It concludes the pilot was likely experiencing internal pressure — which can be the hardest type to recognize. 

Image 9

This begs the question as to what influences there are within a culture that increase or reduce a pilot’s internal pressure. There are lots of variances here, depending on the culture you find yourself in.

The NTSB report did mention some “influences,” such as the pilot being the client’s preferred pilot, who he trusted to fly his children, and the pilot likely not wanting to disappoint the client by not completing the flight.

What Can we Learn From It?

There are some new, and some age-old takeaways from this tragic accident:

  • Marginal VFR is often borrowed time

Flying just under the cloud, just legal, just comfortable enough, is not a stable place to be.

It works right up until something changes. There’s no room for anything to go sideways. Terrain rises. Visibility drops. Workload spikes. Options disappear. Ask any HEMS pilot trying to get to a dying patient.

This flight is a classic example of margin slowly getting thinner until there was nothing left. If your plan relies on everything staying the same, it isn’t really a plan. Have options, ask what-ifs, and be aware of plan continuation bias when you get closer to your destination.

“Let’s just climb above it,” requires planning and mental preparation. Climbing feels like action. Like you’re taking control of the situation. But if you’re already close to cloud, and aren’t fully set up for instruments, that climb can remove your last escape route in seconds if you haven’t planned and prepared yourself properly.

In this accident, the moment visual references disappeared, the helicopter entered a situation where time, orientation, and control were all working against the pilot. From there, recovery options ran out very quickly. 

NTSB Photo
  • IIMC Remains a Huge Threat to Helicopter Pilots

This is one of the most uncomfortable lessons. We keep seeing that even experienced instrument qualified pilots can suffer startle effect and other threats from an unplanned entry into IMC.

By the time you enter clouds inadvertently, any decision that follows is reactive, not proactive. If you’re asking yourself whether it’s time to change the plan, there is a good chance the weather has already won that argument.

  • The most powerful pressure often comes from ourselves

There was no pressure from the company. No pressure from the client. No one telling the pilot to push on. The pressure came from within. The pilot wanted to make it work, to deliver, to succeed and complete the task. Saying ‘no’ can be way easier said than done.

Self-induced pressure is quiet, convincing, and incredibly hard to spot or be aware of, especially when the destination is close and the route is familiar.

  • Experience doesn’t make you immune — and it can make traps harder to see

This pilot was experienced, current, trained, and respected. Yet plan continuation bias still crept in. Familiarity still reduced caution. Confidence potentially shortened reassessment.

Experience doesn’t remove human factors, we still deal with the same traps and biases that, without awareness, can be even stronger when we’ve flown for a long time.

NTSB Photo

Conclusion

Crashes like these always hit differently, because marginal VFR conditions are one of the most common threats for helicopter operations. A flight that started out feeling “doable.” Weather that was legal, but uncomfortable. A familiar route. A capable pilot. A helicopter that was working exactly as it should, but with less and less margin.

Nothing here jumps out as objectively reckless. Most of the decisions make sense when you look at them in isolation. And that’s the scary part. Because this is exactly how a lot of helicopter accidents start — not with one big mistake, but with a series of small, debatable ones that slowly box you in.

Join the Conversation

1 Comment

  1. You had an IFR certified pilot and aircraft flown on a VFR only 135 certificate because the additional cost for operating IFR put the company at a competitive disadvantage. With marginal weather that day, the trip could have been easily and safely flown on an IFR flight. Pilots also avoid flying IFR as they are not comfortable flying in the instrument environment.

Leave a comment

Your email address will not be published. Required fields are marked *

Notice a spelling mistake or typo?

Click on the button below to send an email to our team and we will get to it as soon as possible.

Report an error or typo

Have a story idea you would like to suggest?

Click on the button below to send an email to our team and we will get to it as soon as possible.

Suggest a story