Ara Zobayan. Chief pilot, Island Express Helicopters. Fifty years old. More than eight thousand hours in the air, about twelve hundred of them in the aircraft he was flying that morning. Instrument rated.

Killed January 26, 2020, in the hills above Calabasas, California, along with the eight people he was carrying: Kobe Bryant and his thirteen-year-old daughter Gianna. John, Keri, and Alyssa Altobelli. Sarah and Payton Chester. Christina Mauser.

Most people remember that morning for one name. I want to start with the man at the controls, because this series is about what people paid to teach us, and he paid with everything.

Here's what I need you to know about him before anything else. He was good. He was trusted. And he had canceled flights for weather before. He knew how to say no.

That's what makes this one hard.

This isn't a story about a reckless pilot or a boss on the phone yelling "go." The investigators looked for that. They didn't find it.

This is a story about what happens to a good, careful, experienced person when the plan has momentum and nobody, including him, has named the point where it stops.

If you've ever said "we're almost done" on a job that was going sideways, this one's about you. It's about me too.

The day before, Zobayan flew the same group to the same airport, Camarillo, for a youth basketball tournament. No problems.

That evening the flight broker texted him about the next day's weather. He wrote back that it was not the best day tomorrow, but not as bad as today. The next morning he texted that it should be OK.

The weather that morning was low fog across the Los Angeles basin. His own company had logged a string of weather cancellations in the two days before. The Los Angeles police had grounded their own helicopters.

He'd filled out the company's flight risk form about two hours before takeoff. Conditions got worse after that. If he'd filled it out again at nine, the form would have required him to call his director of operations and write down an alternate plan.

He didn't. There was no alternate plan.

The helicopter lifted off from Orange County a little after nine. Approaching Burbank, the controllers told him the ceiling was low and the cloud tops were around 2,400 feet. He asked for a special clearance to keep flying visually below the clouds. He had to hold for traffic. He circled for about eleven minutes.

Then he got his clearance and kept going. Low. Following the freeways west, a few hundred feet off the ground, staying under the gray.

His company was approved to fly charters visually only. Climbing into the clouds on instruments was not a legal option for that flight. Below the clouds or on the ground. Those were the two choices.

Near Calabasas, the hills rose up into the overcast. A witness on the ground watched the helicopter disappear into the cloud.

At 9:45, he told the controller he was climbing above the layers. He climbed to within about a hundred feet of the cloud tops. Then the helicopter rolled into a left turn and started down.

The controller asked his intentions. He said he was climbing to four thousand.

He wasn't. He was descending at more than four thousand feet a minute. Inside the cloud, with no horizon, his body was telling him one thing and the aircraft was doing another.

About a minute later the helicopter hit the hillside. All nine people on board died.

The NTSB gave the probable cause in one long sentence. The pilot decided to continue visual flight into instrument conditions, became spatially disoriented, and lost control.

Then they named what was underneath it. Self-induced pressure. Plan continuation bias. A company that didn't adequately review and oversee its own safety processes.

Sit with those words, because every crew I've ever worked on has all three.

Self-induced pressure. The board found no evidence that his client or his company pushed him to fly. The pressure was his. He had a high-profile client he'd flown for years. He'd flown them the day before. Nobody on that aircraft had to say a word for him to feel what canceling would cost.

You know this one. Nobody calls the crew and says "finish today." They don't have to. The customers have been out since eight. The outage window is on the schedule. The general foreman is going to ask. You put the pressure on yourself, and you call it work ethic.

Plan continuation bias. This is the pull to finish a plan you've already started, and the investigators said it got stronger as he got closer. It's why "we're forty minutes from done" is one of the most dangerous sentences on a job site. Every minute you invest makes the next minute easier to justify. The closer you get, the harder it is to see that the conditions changed behind you.

No alternate plan. This is the one I want every foreman to tape to the dash. When the weather turned, there was nothing written down for what happens next. No "if the ceiling drops below this, we land here." So every decision in that cockpit was made in the moment, under pressure, by one person.

That's the miss. Not that he couldn't fly. That the stop was never named before the pull to finish showed up. And once it showed up, there was nobody, not even him, left to name it.

The fix for this one isn't more skill. He had more skill than any of us will ever have in an aircraft.

The fix is naming the stop while it's still cheap. Before the job starts. Out loud. With a condition you can see.

I’ve stood where Zobayan sat. Not in a cockpit. On a tower.

October 19, 2015. Northern California. My crew was replacing hardware and insulators on an energized 500kV transmission line, with a parallel 500kV circuit energized on the same corridor. A helicopter was moving people and material to the structures. I was a journeyman with eight years on my card, and I was the safety lead for our crew.

We’d driven two and a half hours to get to the job. We already had a full day of work planned on two towers. When we got there, we found out there was a third. It had been hit by lightning the night before.

More work than hours, before anybody left the ground. Nobody told us to hurry. Nobody ever pushed our crew to put production over safety. They didn’t have to. The day had already grown.

The helicopter put my partner and I on the bridge of the tower. That’s where we saw it. A vertical run of OPGW, optical ground wire, dropping about fifty feet to a splice box and running back up to the top before it went on to the next structure. We’d worked OPGW plenty. We’d never worked it in that configuration.

Here’s what I need you to see. My first thought wasn’t “should we stop?” It was “we obviously need to ground it.”

The question on that bridge was never whether. It was only how.

So we did what good crews do. We paused. We called the foreman at the landing zone and had him send a ground out. We applied it to one of the runs. We talked it through. In my head: one ground should be fine.

Then the doubt showed up. Is it a loop? Did we fully ground it?

I didn’t say it out loud. I reached out and tapped the wire with my hand. Nothing happened. The doubt went away.

A few minutes later, with my left wrist resting on the OPGW, I reached for the tower with my right hand. Somewhere between 8,000 and 12,000 volts of induced energy went through me, through my suit, down the tower and into the earth. I told the whole story of that day in I Told You There Were Two Incidents. This One Is Mine. I’m not going to retell it here.

I’m going to tell you what the stop would have cost.

Thirty minutes. Fly everybody back to the landing zone. Re-tailboard. Open the grounding manual and look up how to properly ground a configuration we’d never worked. On a day that already had three towers in it, thirty minutes felt expensive. So it never came up.

We paused twice on that bridge. Both times, the pause ended with a plan to keep working. A pause that ends in “we’re good” is still a decision to keep going.

Zobayan circled for eleven minutes outside Burbank. I stood on a bridge with a doubt. Neither of us had a stop named before we got there. So when the unfamiliar thing showed up, the only question left was how to get through it.

That’s the miss I own. We saw it. We paused. But I never named “a configuration we’ve never worked” as a reason to come down. Not at the tailboard, and not on that bridge. And at 150 feet, with three towers to finish, I was never going to invent it.

What momentum sounded like on my bridge: “We obviously need to ground it.”

What a named pause would have sounded like: “We’ve never worked it like this. We’re flying back to the LZ to look it up.”

The second sentence costs thirty minutes. It isn’t braver than the first one. It’s just easier to say if you decided at the tailboard, before anybody was invested, that something you’ve never seen is a reason to come down.

Pilots have a name for this. Personal minimums. Before you ever leave the ground, you decide the ceiling, the visibility, and the wind you won't fly in, no matter how good you feel when you get there. You decide it on the ground because you know you won't decide it well in the air.

We need the same thing on the line. I call it the Pause Point. You set it at the tailboard and you run it with AAA.

ASK. Before the work starts, name the stop. At the tailboard, ask one question out loud: "What would make us stop today?" Then get specific. Not "if it gets bad." A condition you can see. Wind that moves the material. A configuration you’ve never worked. Lightning inside the distance you agreed on. Light you can't work in.

Field script: "Before we go up, what's the condition that brings us down? Say it now so nobody has to argue about it later."

ADAPT. Name the second plan. Zobayan had no alternate. Your crew needs one. If we stop, what happens next? Who makes it safe? How do we restore? Who calls the general foreman? When the second plan already exists, stopping stops feeling like failure. It's just the other plan.

Field script: "If we stop, here's what we do. Make it safe, restore, call it in. Everybody good with that?"

ACT. When the Pause Point shows up, keep the promise. When the condition you named arrives, don't renegotiate. Don't say "let's just watch it." The whole point of naming it early is that you don't have to win an argument with yourself at forty minutes from done.

Field script: "That's the line we named this morning. We're stopping."

Who can call it: anybody. The apprentice who sees something unfamiliar gets the same Pause Point as the foreman. If the crew agreed on it at the tailboard, anyone who sees it can say it, and nobody has to justify it.

What kills it, every time:

The rule: No job leaves the tailboard without a named Pause Point and a named second plan. Two sentences. Thirty seconds. Every morning.

Get the Pause Point Card and Stop-Work Script, free. 👇

For Field Leaders (on the crew): Tomorrow morning, before anybody goes up, say your Pause Point out loud and ask the crew to add theirs. Then think about the last time you said "we're almost done." Were you right, or were you just close? Be honest with yourself about how often the closer you got, the less you wanted to hear about the wind. That pull is in all of us. The only defense is deciding before it shows up.

For Supervisors (in your programs): Pull up your job briefing form. Does it have a line for the stop condition and the alternate plan? If it doesn't, your crews are doing what Zobayan did. Making every stop decision in the moment, alone. Add the line. Then look at how you answer the phone when a foreman stops a job. If your first question is "why," you are the self-induced pressure. Make your first question "is everybody okay?" and your second one "what do you need?"

For Executives (at the system level): The NTSB didn't stop at the pilot. It named the company's safety oversight as a contributing cause. His risk form was filled out two hours early and nobody made it current. Ask yourself the same question about your organization. When conditions change after the morning brief, what in your system forces a second look? If the answer is "the foreman's judgment," you've put the whole weight on the one person feeling the most pressure to finish. Build the second look into the system. Then back every foreman who uses it, publicly, especially when it costs you an outage window.

Every crew in your company is carrying some version of "should be OK." The only question is whether anybody has named what they'll do when it isn't.

This is the story I bring to safety stand-downs and annual kickoffs. Not as a celebrity crash. As a mirror. Your people will hear about a pilot who knew how to say no and didn't, and they'll recognize themselves at forty minutes from done. Then I teach them how to name the stop before the momentum shows up, with Ask, Adapt, Act, and they leave with one sentence they're going to say at tomorrow's tailboard.

Reply to this email with the words NAME IT and I'll send you my keynote topics and my open dates for 2027.

Or go straight here: [Book a Name It Stand-Down →]

Tomorrow morning, before the gear goes on, ask your crew one question out loud:

"What would make us stop today?"

Get one specific condition and one second plan. Write them on the tailboard sheet. Then, if the condition shows up, keep the promise.

Then reply to this email and tell me what your crew named. I read every one.

Three from the archive that belong next to this one:

Want to build a culture where every worker goes home safe?
Let's talk. Reply to this email, or visit www.leadingsafelineworkers.com to book a keynote, training, or consultation. Because safety isn't a program. It's a leadership decision.

Share this with someone who needs it.
Forward this to a foreman, a safety manager, or a crew member who's trying to lead better. Let's build this together.

P.S. I'm holding two dates in Q4 for on-site stand-downs, and I'm booking Q1 2027 now. If you're building next year's training plan this month, reply and I'll hold one while you get approval.

Until next time,

Lito Wilkins