Pilot Nick - 6 min read

You probably saw it yesterday. The headline writes itself:

If you’re someone who already grips the armrest at takeoff, your stomach just went through the floor. The one thing you assumed was a given that the person in the left seat is allowed to be there suddenly feels like a question.

So take a breath.

I want to walk you through this one the way I’d brief it to my own crew. Because the headline and the reality are two very different aircraft.

Here’s the part I’ll say plainly before anything else: the man could fly the plane. That was never the allegation.

What actually happened

On Tuesday, Peel Regional Police announced the results of an investigation they’d named Project Icarus. They allege that a former Air Canada captain named in the coverage as Geoffrey Wall, now retired captained more than 900 domestic and international flights between 2009 and 2025 without holding the licence Canadian rules require for the job.

He’s facing seven criminal charges, including fraud, forgery and public mischief. Transport Canada has also levied a monetary penalty.

I’m going to keep using the word allegedly, because that’s what these are: allegations. Nothing here has been proven in court, and a charge is not a conviction. But the documented facts of the licensing gap are not really in dispute even Air Canada has acknowledged it.

So let’s talk about what that gap actually is. Because “without a licence” is doing an enormous amount of work in that headline, and it does not mean what you think.

“Without a licence” doesn’t mean what you think

There isn’t one pilot’s licence. There’s a ladder of them.

To fly passengers for an airline, you build up through a series of certifications, each one a higher bar than the last. The big two that matter here:

• A Commercial Pilot Licence (CPL) — this lets you fly professionally and get paid for it. It takes serious training, exams, and a flight test.

• An Airline Transport Pilot Licence (ATPL) — the top rung. In Canada, this is the licence a captain of a large airline aircraft is required to hold. You earn it mainly by clearing a battery of additional written exams — air law, meteorology, navigation, flight planning — on top of an experience requirement of well over a thousand hours.

Here’s the crux of the case. Police and Air Canada both say the accused held a valid Commercial Pilot Licence and was fully trained. What he allegedly lacked was the ATPL — the captain-level credential. The alleged crime isn’t that an untrained stranger wandered into the cockpit. It’s that the paperwork certifying he’d cleared that top rung was, police allege, fraudulent.

That’s a meaningful difference. “Unqualified to fly” and “missing a specific certification while demonstrably able to fly” are not the same sentence even though the headline blurs them into one.

The part that should reassure you

Now the most reassuring part of this whole story, the one almost no headline will mention.

In Canada, an airline pilot’s competence isn’t checked once, at licensing, and then trusted forever. It’s checked relentlessly, for your entire flying career.

Every six months, I’m back in a simulator being put through my worst day, engine failures, fires, failures stacked on failures and graded on it. Every twelve months, a certified check pilot rides in the cockpit on a real flight and watches everything I do. Air Canada has confirmed its pilots go through exactly this: recurrent training every six months, plus an annual flight check with a Transport Canada check pilot.

By the airline’s own account, this captain was repeatedly tested in the simulator and in the actual aircraft and met or exceeded the standard, year after year.

I’ve sat through dozens of these checks. I can tell you there is no faking your way through them. A check pilot watching you fly an approach in a crosswind, or handle an engine failure at the worst possible moment, sees through anything in about ninety seconds. Whatever the paperwork said, the flying was independently graded by the regulator over and over again.

So when the headline implies that 900 flights’ worth of passengers were at the mercy of someone who couldn’t do the job — the evidence we have points the other way. The flying was watched. Closely. The whole time.

These are the layers that were quietly protecting you on every one of those flights:

1. A fully qualified first officer in the other seat, trained to take over instantly.

2. Standard operating procedures that mean any two qualified pilots can fly together safely, even as strangers.

3. Recurrent simulator checks every six months, grading each pilot on emergencies you’ll thankfully never see.

4. An annual line check with a regulator’s check pilot riding along on a real flight.

5. The aircraft itself built with layers of redundancy so that no single point, human or mechanical, is the only thing keeping you in the air.

A licence is one layer. This story is about that one layer being allegedly faked. Every other layer was doing its job.

So if he could clearly fly the plane, why does the missing licence matter at all?

That’s the part worth paying attention to. And it’s where this story stops being reassuring and starts being important.

The five layers above are the whole reassurance and they’re real. But knowing he could fly the plane and understanding why the missing licence still matters are two very different things.

Read more

Pilot Nick - 8 min read

Thirty seconds.

That’s roughly how long it took a Boeing 767 over New Jersey to go from a textbook approach to clipping a light pole on a highway. At 500 feet, by the crew’s own account, the airplane was on speed and on profile. By the time it reached the airport boundary, it was about six feet off the ground — over a turnpike that sits short of the runway, where a stabilized approach would have it crossing the actual threshold near fifty feet.

That’s the whole story, and it’s worth understanding exactly how thirty good seconds became thirty dangerous ones.

I’ve now read the NTSB’s preliminary report on the May 3rd United approach into Newark a few times. I want to do something different with this one. Not reassure you — teach you. I’m going to put on my analyst hat and walk through this approach the way I’d debrief it in a training department, line by line.

Two things before I start.

1. One: the report is preliminary. The NTSB has not published a probable cause, and won’t for a while. Nothing below is an official finding. It’s my read of the published flight-data and cockpit-voice information, as a pilot who has flown this exact kind of approach hundreds of times.

2. Two: this is not a pile-on. Every honest pilot reading this report feels the same cold flicker of there but for the grace of God. The value here isn’t blame. It’s the lesson — because the lesson is one that keeps the rest of us alive.

First, the thing my regulars already know: what “stable” actually means

If you’ve read my earlier pieces on the stabilized approach, you can skip this. For everyone else, here’s the spine of the whole thing, because you cannot understand this incident without it. You can read below my article on approach stabilization:

Long before the runway, every airline approach has to pass through a gate, a specific altitude, usually 1,000 feet in cloud or 500 feet in visual conditions. At that gate, the approach must be stable, which means all of these are true at once:

• On path — on the correct vertical glidepath and lined up on centerline.

• On speed — at the target approach speed, not fast, not slow.

• Configured — gear down, flaps set for landing, nothing left to change.

• Controlled descent — a normal rate down, not a dive.

• Thrust set — engines spooled to a sensible power, not idle.

• Briefed and checked — every checklist complete, both pilots on the same page.

Here’s the part that matters most: if the approach is not stable at that gate, the rule isn’t “try to fix it.” The rule is go around. Climb away, sort it out, come back and try again.

A stabilized approach is not bureaucracy. It is the single most reliable predictor of a safe landing in all of aviation. Unstable approaches are behind a huge share of landing accidents — and almost every one of them had a go-around available that wasn’t taken.

Hold that thought. We’ll need it.

Leave a comment

The approach that was working

Now the flight. And I want to be fair to this crew, because the front half of this approach was normal.

It was a gusty afternoon — wind from the west at 19 knots, gusting 30, enough to give them what the captain described as moderate turbulence. Their landing runway had been changed three times during the descent, finally settling on runway 29, a runway with no precision electronic glidepath, where you fly the last segment visually using the runway’s approach lights.

At 500 feet, the first officer reported they were on speed and on profile. The captain answered the automated five-hundred-foot callout with one word: stable. By the book, that’s the gate passed.

So far, so normal. Gusty, busy, but normal.

Then came the choice that, in my read, set the trap.

The duck-under and what really happened…

It's a technique nearly every pilot has used and gotten away with. Below, I'll show you exactly what he did, the thirty seconds it came apart, and the one option that sat on the table the whole way down to six feet.

Read more

Pilot Nick · 10 min read

You’re three hours into a normal flight. The cabin lights are dim. You’ve already eaten one meal, watched half a movie, and looked at your watch twice. Your seatmate is asleep with their mouth slightly open.

You shift in your seat and do the math you don’t really want to do.

Three down. Seven to go. Maybe eight if there’s a headwind.

Now imagine fourteen to go.

Or eighteen.

Or twenty-two.

That’s the question Qantas is about to answer for the first time in commercial aviation history and on Tuesday, June 2, the airplane built to answer it left the ground in Toulouse for the first time.

Up at 35,000 feet, the question we’re asking is different from yours. We’re not asking how you will get through it. We’re asking how we will.

What just happened in Toulouse

On June 2, 2026, the first Airbus A350-1000ULR — the Ultra Long Range variant built specifically for Qantas — completed its maiden flight from Toulouse. Three hours and 43 minutes. Cruise at 41,000 feet over the Bay of Biscay. Two Airbus experimental test pilots and four flight-test engineers on board.

That sortie was the official beginning of an 80-hour flight-test programme that will run for about two months, focused almost entirely on one part of the airplane: the fuel system.

Because this isn’t a normal A350.

The A350-1000ULR carries a 20,000-litre extra rear-centre fuel tank that adds roughly 1,000 nautical miles of range over the standard -1000, giving the airplane a total range approaching 10,000 nautical miles. When it enters service, it will be the longest-range commercial airliner ever built surpassing the A350-900ULR that Singapore Airlines uses on the Singapore–New York run.

Qantas has ordered 12 of them. The first won’t be delivered until April 2027 (the original end-2026 timeline slipped due to supply chain issues). But the airplane that will fly Sydney to London Heathrow nonstop — 10,573 miles, the longest commercial route in history is now flying, and Qantas expects to launch commercial service in the first half of 2027.

For context: today’s longest commercial flight in the world is Singapore Airlines’ SQ23/SQ24 between Singapore Changi and Newark Liberty — roughly 9,537 miles, 18 to 19 hours in the air, flown by the A350-900ULR (the previous generation of the same family). That’s the route the industry already considers the edge of the operational envelope.

Project Sunrise adds roughly four more hours and another 1,000 miles on top of it.

That much you can read in the press release. Here’s the part the press release doesn’t tell you.

The airplane is the easy part of Project Sunrise. The humans are the hard part.

What 22 hours actually feels like up front

I’ve flown 8-hour transatlantic legs, 12-hour Asia–Europe legs, 14-hour Asia –US legs. I have never flown 22 hours nonstop, because no commercial pilot ever has. Even Singapore Airlines SQ23 — today’s longest commercial sector — tops out at 18 to 19 hours.

Project Sunrise is asking the industry to push that envelope by another four hours. Which, in flight-deck terms, is enormous.

Here’s why.

In the cockpit, the metabolic cost of flying isn’t the actual stick-and-rudder work — the autopilot does most of that. The metabolic cost is the constant vigilance. You’re monitoring six fuel tanks, four engine indicators, weather radar, traffic radar, ATC frequencies in three regions, oceanic crossing procedures, alternate airport availability over the next 1,500 miles, and the dozen subtle ways the airplane talks to you when something is starting to drift. You’re doing that at 41,000 feet in a 12% humidity, 800 mb pressure environment that is steadily dehydrating you, regardless of how much water the cabin crew brings up.

For 8 hours, this is manageable.

For 18, it requires choreographed sleep.

For 22, it requires choreographed everything.

Leave a comment

The 5 things Project Sunrise had to solve before a single commercial passenger could board

The aircraft modification is one of five solvable problems. Here are the other four and how the system answers each one.

1. The range problem (solved by the engineers)

An A350-1000, off the showroom floor, cannot do Sydney to London nonstop. It’s roughly 800 nautical miles short, depending on payload and winds.

So Airbus took the most fuel-efficient widebody on the market and added a 20,000-litre rear-centre tank. The fuel system now has to manage a larger, more complex weight distribution which is why this week’s flight tests are 80 hours, two months, and focused almost entirely on the fuel system. The certification is not about whether the engines run. It’s about whether the new fuel architecture is safe in every fuel-loading scenario, including the one where you suddenly need to divert with 80% of your fuel still on board.

2. The duty-time problem (solved by the regulators)

The standard regulatory duty-time limit for two pilots is in the order of 13 to 14 hours from sign-on to engines off. A 22-hour flight, by definition, blows through that limit before you’re halfway across the Indian Ocean.

The fix is a 4-pilot crew. Two captains, two first officers effectively two complete cockpit teams. All four are in the cockpit for takeoff and landing — standard procedure at every ULR carrier, because the highest-workload phases of the flight deserve the highest level of human redundancy. The rotation happens during cruise: each pilot gets one long rest break (~4 hours) and one short break (~2.5 hours) in a dedicated crew bunk above the main cabin, choreographed so the pair flying the approach is the most rested one.

In real life: when you board a Project Sunrise flight, there are four pilots on your manifest, and all four are up front when you push back from the gate. The system is older than you think — Singapore, Qantas, Emirates, and Cathay have been running variants of this for over 20 years on slightly shorter ULR routes.

3. The biology problem (managed by science, not engineering)

The human circadian rhythm does not know what year it is, what time zone you crossed, or what your boarding pass says. It runs on a roughly 24-hour clock anchored to light.

On a 22-hour flight, you will cross every time zone on Earth. Your body will not know what time it is, even after you land. This isn’t a passenger problem — it’s a pilot problem, because the pilots flying your approach are the same pilots whose circadian rhythm has been shoved through a blender.

This is why Qantas has spent years on circadian research. The cabin lighting is engineered to push passengers (and crew) onto destination time within the first few hours. Meals are timed deliberately. The pilots’ rest cycles are choreographed against their personal sleep timing, not just the clock.

4. The “fresh for the approach” problem (the hardest one)

This is the one keeping the safety analysts up at night.

The approach and landing phase of any flight is the most safety-critical part. It’s also, in a normal flight, the part the pilots are freshest for, because they’re at the start of their duty period.

On a 22-hour flight, the approach happens at the end of the duty period. The pilots flying you into Heathrow have, in theory, been awake or rested-poorly for most of the last day. The system mitigates this — the pilots who land the airplane take the long mid-flight rest break specifically so they’re as fresh as possible for descent — but it cannot eliminate the basic biological cost of being on duty for 22 straight hours.

5. The unknown-unknowns problem (still being tested right now)

This is what the next 80 flight-test hours are for.

Every ultra-long-range aircraft brings a category of failure modes that didn’t exist on shorter flights: fuel pump behavior during a 22-hour cycle, hydraulic system aging on a single sortie, crew rest area performance over long durations, cabin pressurization stability over 22-hour cycles, even avionics cooling behavior when the systems have been running uninterrupted for a day.

None of these are likely to fail. All of them have to be proven.

The framework above is the system. But the most useful thing for a passenger isn’t understanding the engineering — it’s understanding what your actual experience will be in three real scenarios most ULR passengers worry about.

Read more

🕒 9 min read · Black Box Series · Episode 03 · Pilot Nick

You’re in seat 9F.

It’s a routine afternoon — Denver to Chicago, drinks served, descent still an hour away. The sun is hitting the wing through the window. You’re maybe halfway through your magazine.

Then a bang you feel in your ribs.

Not a clunk. A bang. The whole airplane lurches sideways. Your tray slides. Somewhere behind you, a glass breaks. The engines — you can’t quite put your finger on what’s different, but something is off.

The seatbelt sign comes on. The captain’s voice comes over the PA, calmer than it has any right to be.

“Ladies and gentlemen, we’ve had a problem with our number two engine. We are diverting to Sioux City.”

That’s the polite version.

Up at FL370, the cockpit just lost the airplane.

If you’re new here Black Box is the series where I take a real aviation incident and break it down the way a pilot actually thinks about it.

Not the news version. Not the dramatized version.

The version from the left seat.

What the crew saw. What they decided. Why. And most importantly for the nervous flyers reading this what changed afterwards, so that you never have to.

Here’s what almost nobody — passenger or pilot — fully understood about wide-body airliners on July 19, 1989.

A DC-10 has three hydraulic systems. Three. Each one independent, each one rated to fly the airplane on its own. You can lose one. You can lose two. The third one will still move the rudder, the elevators, the ailerons, the flaps, and the landing gear.

The design philosophy was simple: no single failure should be able to take all three. The probability of losing all three hydraulic systems on a DC-10 was calculated at roughly one in a billion flight hours.

Then a fan disk in engine number two — the one mounted in the tail — failed.

Not a crack the airline missed. A microscopic metallurgical defect, present in the titanium since the disk was forged 18 years earlier, that finally let go after 41,000 cycles of heating and cooling and spinning at 8,000 rpm.

The disk burst.

Shrapnel sprayed through the tail at hundreds of miles per hour and severed the lines of all three hydraulic systems — every one of which, for design reasons that made sense in 1968, happened to pass within a few feet of each other right behind that engine.

In about two seconds, the crew of United 232 had a DC-10 with no working flight controls.

No rudder. No elevators. No ailerons. No flaps. No spoilers. No nose-wheel steering. Nothing.

And the good news — yes, there is some — is what they did next.

Captain Al Haynes had been flying for 33 years. 30,000 hours. He’d never seen anything like this. Nobody had.

His first instinct, the one drilled into every airline pilot, was to grab the checklist. Loss of all hydraulics. He looked. There was no procedure.

There was no procedure because the situation wasn’t supposed to be possible.

The airplane was now in a slow right roll, pitching gently up and down in a long, lazy oscillation pilots call a phugoid — the natural rhythm an airplane settles into when nobody is flying it. Nose up, slow down. Nose down, speed up. Sixty seconds per cycle. Beautiful, almost, except they were 37,000 feet over Iowa with 296 people behind them.

First Officer William Record was on the controls and feeling nothing. The yoke moved freely. None of it did anything.

In the cabin behind them was a man named Dennis Fitch an off-duty United Check Airman who happened to be deadheading home. A DC-10 instructor. He’d actually trained for a hydraulic-loss scenario in a simulator, just out of curiosity, and discovered something interesting: you could sort of steer an airplane with the throttles.

Push the left engine forward, the airplane yaws and rolls right. Push the right engine, it rolls left. Add thrust to both, the nose comes up. Pull both back, the nose drops.

Fitch walked into the cockpit, introduced himself, and offered to help.

Haynes pointed at the center pedestal.

For the next 44 minutes, Fitch knelt on the floor between the captain and first officer, his hands on two thrust levers, flying the airplane the way nobody had ever flown an airplane before. Haynes ran the radios and the cabin. Record held the useless yoke. Second Officer Dudley Dvorak worked the system pages, looking for anything that could be saved.

Four pilots. Two engines. Zero flight controls. One runway in Iowa.

This is the part nobody trains for. So here’s what they did instead.

The 5 things the crew did right — without a checklist

These weren’t steps in a procedure. They’re what airline pilots now study as the textbook for “no procedure exists.”

1. They flew the airplane first.

Before anything else — before the radios, before the cabin, before the diversion — they flew.

In that order, always. The temptation when something catastrophic happens is to start talking, start asking, start fixing. The crew of 232 did none of that for the first 90 seconds. They figured out what the airplane was doing, then what it would do next, then what it might let them do.

2. They accepted the airplane they had.

Haynes never tried to get back the airplane they’d taken off in. He worked with the one he had. No working controls? Fine. What does work? Two throttles. Okay. We fly with two throttles.

3. They put the right person on the right job — immediately.

Fitch was a passenger. Fitch was also the only person on board who’d ever thought about flying a DC-10 with throttles alone. Haynes didn’t care about rank, schedule, or who was supposed to be where. He looked at the problem and put the most-qualified hand on it within two minutes of Fitch walking through the cockpit door.

4. They told the truth, fast.

Haynes got on the radio with Sioux City approach and told them, plainly: “We have almost no controllability.” Not “we have a problem.” Not “we’re declaring an emergency.” A specific, factual description that let the ground know exactly what was about to land on them and gave them 40 minutes to position every fire truck, ambulance, and Air National Guard medic in the county.

5. They kept their sense of humor.

This is the one that gets quoted most. When the approach controller cleared them to any runway, Haynes laughed and said, “You want to be particular and make it a runway, huh?” That isn’t gallows humor. That’s a crew whose stress was so far past the red line that the only way to keep working was to acknowledge it. Pilots call this winding the clock — doing something small and human to keep your nervous system below the threshold where it stops thinking.

This is the part the public never sees. The crew of 232 didn’t survive because they were braver. They survived because they had a system — and when the system ran out of procedures, they had each other.

“Could this happen on my flight today?”

Read more

You’re in 14A. Window seat. Somewhere over the Carolinas in July.

Outside, the cloud has been building for twenty minutes — first cottony, then bruised, then black. The cabin lights flicker once. Twice. There’s a flash, white and total, then a crack that doesn’t sound like anything you’ve heard before.

A kid two rows back yells. Your hand finds the armrest. The man across the aisle whispers “oh god” under his breath, and you realize you said it too.

You want someone — a calm voice, an adult voice — to come over the PA and tell you everything is okay.

Up at 37,000 feet, we know that feeling. We just don’t have it.

Here’s what most people get wrong about lightning.

They think the bolt is the danger.

It isn’t. The bolt is a discharge. A photograph of something that already happened. By the time you see the flash through your window, the physics are finished — the airplane took the strike, the current ran around the aluminum skin to the trailing edge, and it left the airframe somewhere out behind us, probably without leaving so much as a scorch mark.

The danger isn’t the lightning. The danger is the cloud that produced it.

And the cloud that produced it is something we worked out how to handle forty miles ago, on the ground, before any of this started.

That’s the part no one tells passengers. They imagine pilots squinting through the windshield, white-knuckled, “trying to make it through the storm.” We’re not. We’re managing distance. We’re managing geometry. We’re managing the small set of decisions that turn lightning from a problem into a non-event.

Let me tell you about an actual one.

Atlanta to Newark. Evening flight. A line of thunderstorms had been forming all afternoon along the spine of the Appalachians — the kind of line you can see on the weather radar from 200 miles away, painted in cells of yellow, red, and the magenta we call the bad ones.

My first officer and I briefed the line on the ground, before we even started engines. We knew where the gaps were. We knew which cell we’d deviate around first. We had a fuel number for the diversion and a fuel number for the divert-to-Charlotte-instead.

We launched. Climbed through 18,000 feet. At cruise, we were 40 miles out from the first cell when ATC cleared us to deviate left of course. We did. We threaded the line.

And then, between two cells we had already decided were safe to fly between — crack.

A flash so bright it lit the cockpit like a stage light. A sound that doesn’t have a real name. The autopilot stayed engaged. The instruments stayed green. My first officer looked at me. I looked at him. He said, “Well, that was a strike.” I said, “Yep.”

We finished the flight. Ground crew looked the airplane over in Newark. They found a tiny exit burn near the right horizontal stabilizer. Nothing structural. Nothing the airplane wasn’t built to take.

The strike was a non-event. The decision that prevented it from being an event was made on the ground, 90 minutes earlier, with a coffee in our hands and a flight plan on the table.

That’s the principle. The flash isn’t the moment. The moment was always earlier.

A small confession before we get into the framework.

When we know the line ahead has lightning and we know we’re at our 20-mile distance, we don’t dread it. Most pilots love it.

At night, if the storms ahead are really firing, we’ll turn the cockpit lights all the way up. Counter-intuitive, you’d think dim is better but bright lights keep our eyes adapted to brightness, so when the next bolt lights up the sky, we don’t go temporarily blind from the flash.

Then we watch.

A thunderstorm at night, from the flight deck, with the right distance between us and it, is one of the most beautiful sights in this job. Cells lighting up from inside like paper lanterns. The whole horizon flashing white, then black, then white again.

We’re not white-knuckled up there. We’re often quietly grinning.

Here’s the framework — five steps. They map to the cockpit, but I’ve written each with a version you can use from 14A.

Step 1: Decide on the ground, not in the air

In the cockpit, we don’t make storm decisions while we’re flying through them. We make them on the ground, with charts and forecasts, hours before takeoff. By the time we’re airborne, the decision is already made — we’re just executing it.

You can use this immediately. If you’re a nervous flyer and you know you’re flying in summer, the moment you’re in the air with a flash outside your window is the worst possible time to start managing fear. Do that work the night before. Read the route forecast. Look at the radar from your hotel room. Decide, before the gate, that you’ve already accepted what you might see.

One practical move while you're still on the ground: if you don't love thunderstorms, book the early flight. Convective weather builds with the heat of the day — most thunderstorms in the US form between 2 and 6 p.m. local. A 7 a.m. departure usually beats the system entirely. It's the single cheapest fix in this article, and most passengers never use it.

Step 2: Read the radar, not the flash

Check the actual radar trend the night before, Windy is the simplest version of what we look at up front. Don't rely on the icon on your phone weather app. Storms in the southeastern US tend to form mid-afternoon and dissipate after sunset. A 9 a.m. departure into a 4 p.m. arrival window is a different conversation than a 4 p.m. departure into the same window.

Step 3: the 20-mile rule

The standard separation in commercial flying is 20 nautical miles upwind of a thunderstorm cell. Most carriers train to it. Some require more. The number isn’t arbitrary — it’s far enough out that we’re clear of the hail, the wind shear, and the strongest vertical currents.

Step 4: Trust the aluminum cage

Every commercial airliner is certified for lightning. The skin of the aircraft is a “Faraday cage” the current travels around the outside and exits at a trailing edge, usually through a wick designed exactly for that purpose.

Here’s the math passengers never see:

• Every commercial airliner is struck by lightning, on average, once a year.

• That works out to roughly “one strike per 1,000 flight hours.”

• Across the global commercial fleet, that’s “tens of thousands of strikes a year” almost none of which make the news, because almost none of them do anything.

The last passenger jet brought down by lightning in the United States was “Pan Am Flight 214 in December 1963”.

After it, the FAA rewrote the lightning protection standards. Every airliner certified since has been built to those rules. No commercial jet designed under them has ever been brought down by a strike.

Here’s what a strike actually looks like from seat 14A:

A flash. The cabin lights might flicker, they might not. If you’re at the window, you’ll see white for a half-second, like a camera flash close to your face.

Then a crack. Loud. Sometimes a deep boom, sometimes a sharp snap. It depends on where you’re sitting and where the strike exited the airframe.

Sometimes not always, a faint smell of ozone in the cabin a few minutes later. Same smell as after a thunderstorm on the ground.

That’s it.

The autopilot stays engaged. The screens stay green. The flight attendants keep walking down the aisle with the cart. The captain might come on the PA and say “you may have noticed we just took a lightning strike, everything’s normal.” Some captains don’t even mention it.

After landing, the ground crew walks the airplane with a checklist. They find an entry mark and an exit mark usually pinhead-sized, sometimes the size of a quarter. The airplane is back in service in 30 minutes.

That’s the entire event.

I have been struck. My colleagues have been struck. The airplanes were fine every time.

You can use this immediately. When the flash happens and at some point in your flying life it might — your body will tell you the airplane is broken. Your eyes will tell you the airplane is fine. The airplane is fine. Believe your eyes.

Step 5: Aviate—Navigate—Communicate

This is the oldest piece of pilot wisdom there is. When something happens in the cockpit, the order is non-negotiable. First we keep flying the airplane. Then we figure out where you’re going. Then and only then do you talk about it. But I’ll tell you we plan ahead, way ahead…

Pilots aren’t calmer than passengers because we’re braver. We’re calmer because we’ve already decided what we’re going to do, long before there’s anything to do.

Read more

Pilot Nick — 4 min read

Each edition: real questions from real passengers. Real answers from the cockpit.

Because knowledge beats fear every time.

And yes… we’ll go a little deeper for the avgeeks too.

Lessons From The Flight Deck ✈ is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

👇 This Edition’s Questions:

This month’s three questions share something in common — they’re all about the invisible layer of every flight you take. The conversations you can’t hear. The river of air you can’t see. The decisions being made before you’ve even buckled your seatbelt.

Let’s go.

💬 Question #1: “What do pilots actually talk about up there? Is it boring during cruise?”

✈️ You picture us up front, hours into a flight, watching the autopilot do its thing. So what’s actually happening behind that locked door?

The short answer: it depends entirely on the altitude.

Below 10,000 feet — the “sterile cockpit”

There’s a rule in aviation called the sterile cockpit rule. Below 10,000 feet — climb out and descent — no conversation is allowed that isn’t directly related to operating the aircraft. No chat about the weekend. No coffee orders. No “did you see the game last night.”

Why? Because those phases of flight are where 80% of incidents historically occur. Takeoff, climb, descent, approach, landing — that’s when we’re configuring the aircraft, talking to multiple ATC controllers, scanning for traffic, briefing approaches, and managing the highest workload of the entire flight.

A casual remark at the wrong moment can pull attention away from a critical task. So we don’t make them.

Inside the cockpit during those phases, you’d hear something close to a surgical theatre: checklists, callouts, instrument scans, ATC readbacks. Precise, calm, deliberate.

Above 10,000 feet — different rhythm

Once we’re established in cruise, the workload drops dramatically. The autopilot is flying, the FMS is navigating, the systems are monitoring themselves and reporting any issue instantly.

But “boring” isn’t the right word. It’s more like active monitoring.

We’re cross-checking fuel burn against the flight plan. Watching weather radar 100 miles ahead. Listening to ATC for traffic in our area. Reviewing the arrival and approach for our destination, often hours before we get there. Checking alternate airports in case something changes.

And yes — we also talk.

About the flight, about flying in general, about the industry, about our families, about whatever interesting thing one of us read last week. Cockpits are small spaces, and over the course of a 10-hour flight you learn a lot about the person beside you. Some of my best conversations in 25 years have happened at 38,000 feet over the Atlantic at 3 AM.

The pilot truth:

The locked cockpit door creates this idea that something mysterious is happening up front. It isn’t. It’s two highly trained professionals doing a job that alternates between intense concentration and quiet vigilance with the occasional good conversation in between.

The bottom line:

Below 10,000 feet, we’re surgeons. Above it, we’re navigators with a view. Either way, we’re never just “sitting there.”

💬 Question #2: “Why does the same flight take longer in one direction than the other?”

✈️ You fly New York to London in 6 hours. The return takes 7.5. Same aircraft, same route, same distance. What gives?

You’re flying through a river of air and which way it’s flowing changes everything.

Meet the jet stream

At cruise altitudes — roughly 30,000 to 40,000 feet — there are massive ribbons of fast-moving air circling the planet. The most famous is the North Atlantic jet stream, which generally flows from west to east at speeds that can exceed 250 mph.

That’s not wind in the way you experience it on the ground. That’s a moving conveyor belt of air the size of a small country.

Fly with it (eastbound) and your ground speed gets a huge boost. Fly against it (westbound) and you’re effectively swimming upstream.

A Boeing 777 cruising at Mach 0.84 might be doing 560 mph through the air — but with a 150 mph tailwind, it’s covering ground at 710 mph. Turn around and fly home, and that same aircraft is now making 410 mph over the ground. Same aircraft. Same engines. Same fuel burn. Two completely different flight times.

Read more

Pilot Nick · 8 min read

You’re in seat 24C, three hours into the flight, somewhere over the ocean.

The cabin lights are dim. The person next to you is asleep. You glance up at the little compartment above your head, the one you’ve never seen open and you think, just for a second:

what would it actually feel like if those masks dropped right now?

You’ve seen the safety video a hundred times. You know “put yours on before helping others.” You know it means breathe normally.

You also know, somewhere in the back of your mind, that the safety video doesn’t tell you what comes before the mask. Or after. Or what the pilots are doing in the 30 seconds you’d be fumbling with the elastic.

Up at 35,000 feet, we know that feeling too, not as passengers, but as the pilots who train for this scenario more than almost anything else in the simulator.

What most passengers get wrong about that yellow mask

Most people think the scary part of cabin pressure is the moment the mask falls from the ceiling.

I’ll tell you what’s actually scary if you’re a pilot: the version where the mask doesn’t fall because the cabin never gave anyone a warning loud enough to react to.

The cabin pressurization system is one of the most reliable systems on the aircraft. So reliable that most passengers fly thousands of hours over a lifetime and never give it a thought.

That reliability is also why, when something does go wrong, the second-most-feared cabin event for nervous flyers becomes the one almost nobody understands.

Here’s the truth your safety card doesn’t have room for: those yellow masks aren’t a parachute.

They’re a clock.

And once you understand the clock, you understand the entire procedure including why the pilots’ first job isn’t to comfort you.

It’s to dive.

Even if we fail, the airplane doesn’t

Most modern private jets and the Airbus A350 are equipped with a system called Automatic Emergency Descent — AED for short or ADM (Automatic Descent Mode)

If the cabin altitude crosses a critical threshold and the pilots don’t react within seconds — because they’re already hypoxic, incapacitated, or simply too slow — the autopilot and autothrottle take over. The airplane disconnects from its cruise route, banks roughly 90 degrees off the airway to clear traffic below, pulls the throttles to idle, deploys the speed brakes, and dives toward 10,000 feet on its own.

No pilot input required.

On every other airliner — which is still the majority of the fleet flying today — the pilots execute the exact same maneuver themselves. And that is precisely what we train, in a full-motion simulator, every six months.

It was engineered into the airplane for one reason: because hypoxia takes away the judgment to recognize hypoxia, the system can no longer assume a human will catch it in time. So the system catches itself.

This is the second clock you didn’t know was running. The first is the oxygen in the yellow mask. The second is the airplane itself already programmed to do what your body would be trying to do, if it could.

What we actually train for and what “emergency descent” really means

Every six months, I sit in a full-motion simulator for a recurrent training session. Cabin decompression is on the syllabus almost every single time — right alongside engine failure on takeoff, fire warning at altitude, and a rejected takeoff at decision speed. It is, statistically, one of the four scenarios airline pilots rehearse more than any other.

This is not a “we covered it once” kind of training. This is a “we run it until our hands move before our brain does” kind of training.

So when you hear the phrase emergency descent, here’s what’s actually happening in the cockpit:

Masks on, within two seconds. Both pilots reach for their quick-don oxygen masks the moment the cue is recognized. Mask first. Communicate second. The cockpit oxygen system is independent of the cabin’s — stored at high pressure, lasts far longer, and is the reason the pilots can keep flying the airplane while you breathe through your yellow one.

Autopilot stays engaged. Modern philosophy is to let the automation do the precision work while the humans manage the procedure. We don’t disconnect to “fly it manually” because we’re brave. We let the autopilot fly because it doesn’t get hypoxic.

90-degree turn off the airway. Other traffic is below us; we need to get out of their cruising level before we descend through it. The turn is automatic on aircraft equipped with ADM, manually flown on those that aren’t.

Throttles to idle. Speed brakes out. Nose down. The airplane is now in a high-speed descent at, or just below, its maximum operating speed (Vmo/Mmo) typically 4,000 to 6,000 feet per minute, roughly the descent rate of a fast express elevator.

Level off at 10,000 feet or the minimum safe altitude over terrain, whichever is higher. Below 10,000, the air outside is breathable on its own. The clock stops there.

The whole sequence, from chime to level-off, is usually complete in 3 to 5 minutes.

From the cabin, it feels like the plane is falling. From the cockpit, it feels like the airplane is running the same checklist we’ve run forty times in the simulator — because it is.

The quietest decompression is the deadliest

Pilots are trained for three kinds of cabin pressure loss, each with a different time signature:

The danger isn’t the pressure differential. It’s the hypoxia.

Hypoxia doesn’t feel like suffocation. It feels like being fine. Mild euphoria. Slightly slurred speech. A little tunnel vision. The judgment to recognize what’s happening is one of the first things hypoxia takes away.

The textbook example is Helios Airways Flight 522. August 2005. A Boeing 737-300 climbed out of Larnaca with its pressurization controller left in MANUAL after maintenance the night before. The cockpit warning sounded and the already-hypoxic crew misread it as a different alarm. The passenger masks dropped automatically. The system worked. The people didn’t.

The aircraft flew its programmed route alone for over two hours before fuel exhaustion. 121 souls lost. No mechanical failure only a missed switch, a confusing alarm, and a kind of decompression that doesn’t announce itself.

Helios is the reason almost every modern airliner and corporate jet manufactured since has been engineered with Automatic Descent Mode. The same chain of events on a 2026 aircraft ends with the autopilot saving everyone before hypoxia ever finishes its work.

You don’t gamble with the quiet kind and the engineers, after Helios, made sure the airplane wouldn’t either.

Read more

Pilot Nick — 6 min read

You’re sitting at the kitchen table at 11 p.m.

The job offer is on the screen. More money. Different city. A boss you’ve never met. Your partner is asleep upstairs. You’ve read the email forty times, and somehow each time it gets less clear, not more.

You want someone to just tell you what to do.

Up at 35,000 feet, we know that feeling.

A warning light flashes. The weather ahead has changed. A passenger needs medical attention. Two hundred people are sitting behind us — most of them watching a movie, completely unaware and we have minutes, sometimes seconds, to choose.

Here’s what most people get wrong about pilots: they assume we’re calmer because we’re braver. Or smarter. Or wired differently.

We’re not.

We’re calmer because we’re following a system. And the good news is — you can borrow it.

The Cockpit Reality

Forget what you’ve seen in movies.

When something goes wrong at 35,000 feet, the cockpit doesn’t get louder — it gets quieter. The first words out of a captain’s mouth aren’t a command. They’re almost always the same four:

“Okay. Let’s slow this down.”

Not because we’re calmer than you. Because we’ve been trained to follow a system before we follow a feeling.

Here’s a small example. A few years ago, flying into a European airport at night, we got a thunderstorm cell sitting right on the approach path. Tower was vectoring everyone around it. Our fuel was fine, but not infinite. The first officer looked at me. I looked at the radar. And before we did anything else, I said the line every pilot says in moments like this:

Fly the plane first. Figure out where to go second. Talk about it third.

That order matters. Most bad decisions in life and in cockpits happen because someone reverses it. They start communicating (panicking, asking everyone for advice, doom-scrolling) before they’ve stabilized the basics.

So here’s the framework. Five steps. Use it next time life gets loud.

The Pilot Decision Framework

Step 1: Slow the situation down

In the cockpit, the first move when something goes wrong isn’t to act. It’s to create time.

We climb to a safer altitude. We level off. We put the autopilot on. We give ourselves a stable platform to think from.

Pilots have a phrase for this: wind the clock. It comes from the old days when, before doing anything else in an emergency, you’d literally wind the cockpit clock. The point wasn’t the clock. The point was: do one small, deliberate thing before you do anything big.

You can use this immediately. Before responding to the email, the offer, the argument, the news do one small deliberate thing. Make tea. Walk around the block. Sleep on it. You’re not avoiding the decision. You’re stabilizing the platform you’re going to make it from.

Step 2: Define the real problem

Here’s where most people get stuck — and where most cockpit errors happen too.

The emotional problem is rarely the actual problem.

When that warning light flashes, the emotional problem is “something is wrong and people could die.” The actual problem might be “a faulty sensor is sending a bad signal.” Those are very different problems. They have very different solutions.

In real life: The emotional problem is “I have to decide whether to take this job.” The actual problem might be “I don’t know what I want my life to look like in five years, and this offer is forcing me to figure it out.” Those are also very different problems.

Ask yourself: What am I actually trying to solve here? Write it in one sentence. If you can’t, you’re not ready to decide yet — you’re ready to think.

Leave a comment

Step 3: Gather only what matters

In the cockpit, we have access to roughly a thousand pieces of information at any given moment. Engine temperatures. Fuel flow. Wind speeds. Navigation data. Traffic. Weather. Cabin pressure. ATC chatter.

If we tried to process all of it, we’d freeze.

So we filter. Hard. We ask one question: What information do I need to make THIS decision, right now?

Everything else gets ignored. Not forever — just for now.

You can use this immediately. When you’re stuck on a decision, write down the three pieces of information that actually matter. Not the ten things you’re worried about. The three things that would change your answer.

If you can’t think of three — you probably already know your answer.

Step 4: Choose a safe, good-enough option

This one is the hardest for high-achievers to swallow.

Pilots are not trying to make the perfect decision. We’re trying to make a safe, sensible one quickly and then move on.

There’s a concept in aviation called the 80% rule. If you have 80% of the information and 80% confidence in your choice, decide. The last 20% almost never arrives in time, and waiting for it is itself a decision — usually a worse one.

In life, “perfect” is the enemy of “decided.” Most of the regret I hear from people isn’t about choosing wrong. It’s about not choosing at all, and watching the option expire.

Step 5: Commit and adapt

Here’s the part Hollywood gets right.

Once a pilot makes a decision to divert, to return, to continue we commit. We don’t keep relitigating it every two minutes. We execute, and we monitor.

But and this is critical committing is not the same as being stubborn. As new information arrives, we adjust. A diverted flight might re-divert if conditions change. We’re not married to the decision. We’re married to the outcome: getting everyone on the ground safely.

Decide. Monitor. Adjust. That’s the loop. Most people get it wrong by either flip-flopping (never committing) or doubling down (never adjusting). Neither one flies.

Pilots aren’t better decision-makers because they’re smarter. They’re better because they use systems when their emotions would rather not.

Subscribe now

What This Looks Like in Real Life

Let’s stop talking about cockpits for a minute and put the framework on the ground. Three scenarios. Same five steps. Watch how the noise drops out.

Read more

Pilot Nick - 6 min read

It’s 11:47 PM. Your flight is in nine hours.

You’re not sleeping. You’re on your phone, and you’re on Turbli.

You’ve typed in your route three times tonight. The little colored bars haven’t changed. Yellow over the Rockies. A patch of orange somewhere near Denver. You’ve zoomed in. You’ve zoomed out. You’ve checked the “light, moderate, severe” key twice, even though you have it memorized.

You’re not crazy. You’re trying to feel in control.

I want to talk to you about that app — gently, because I know it feels like a lifeline. But there are some things it isn’t telling you, and I think once you understand them, you’ll sleep a little better tonight.

First, Credit Where It’s Due

Let me say this clearly, because I respect the people who built it: Turbli is a genuinely well-engineered tool.

It’s not pulling random weather data. It uses NOAA’s Graphical Turbulence Guidance the same underlying turbulence forecast data pilots use for flight planning. It even adjusts for your specific aircraft’s wing loading, which affects how it handles bumps. The team behind it clearly knows aviation.

So the problem isn’t the data. The problem is the packaging and what gets lost between the cockpit and your phone.

What Turbli Actually Misses

1. The forecast updates every 6 hours. The atmosphere doesn’t.

Turbli’s turbulence forecast refreshes four times a day. That’s standard for global weather models. But the air you’ll fly through changes much faster than that. Jet streams shift. Storms develop. Pilot reports come in every few minutes. By the time you read a Turbli forecast, the data underneath it is already hours old — and your flight is still hours away.

We don’t fly on six-hour-old forecasts. We fly on continuously updated turbulence layers, refreshed in near real-time and cross-referenced with what aircraft ahead of us are reporting right now.

2. The forecast doesn’t see what other pilots just reported.

Turbli has a PIREP map — pilot reports of actual turbulence — and it’s a useful feature. But here’s the catch most users miss: the PIREP map is separate from your flight forecast. Your flight’s turbulence prediction is built from forecast models alone. The real-time pilot reports aren’t blended into the colored bars you’re staring at.

In the cockpit, PIREPs are integrated. We don’t toggle between maps. The latest pilot report from the aircraft 80 miles ahead of us shows up on the same screen as the forecast — and it overrides the forecast every time. That’s the difference between “what the model predicted at 6 AM” and “what’s actually happening at 35,000 feet right now.”

3. Clear Air Turbulence is the hardest kind to forecast for anyone.

This isn’t a Turbli flaw. It’s physics.

Clear Air Turbulence (CAT) — the bumps in clear blue sky, no clouds, no storms happens at the edges of jet streams in wind shears thousands of feet thick but only a few miles wide. Forecast models smooth those edges out. Even the best aviation weather systems list CAT as a probability, not a certainty.

The honest answer about turbulence forecasting is this: everyone is making educated guesses. Pilots make better guesses because we have real-time data and the ability to react. Turbli makes a reasonable guess based on a 6-hour-old model. Your phone screen doesn’t show you that distinction.

4. The forecast assumes we’ll fly straight through whatever it predicted. We almost never do.

This is the one Turbli openly admits — buried in their FAQ. When their forecast shows severe turbulence, they note that “your pilot might find an alternative route.” That’s a polite way of saying: the forecast you’re looking at doesn’t account for the most important variable, which is the captain.

If we hit a bump, we ask ATC for a different altitude. Or we deviate around it. Or we slow to “turbulence penetration speed” — a specific airspeed engineered to keep the aircraft stable. Sometimes we change altitude before hitting the bump, because the PIREP from the aircraft ahead of us told us to.

The forecast assumes a plane flying in a straight line at one altitude. Real flights don’t work that way. The captain and his or her First Officer is part of the system. Turbli, by definition, can’t forecast what I’ll choose to do.

The Bigger Problem (This Is The One That Matters)

Here’s the part I really want you to hear.

Even if Turbli were 100% accurate and no app can be checking it the night before your flight isn’t preparing you.

It’s priming you.

When you stare at those orange and red bars at midnight, your brain isn’t filing the information away calmly. It’s rehearsing fear. By the time you board, every small bump becomes a confirmation of what the app warned you about. A normal pocket of light chop — the kind that doesn’t even register for me in the cockpit — feels like the beginning of something worse.

You’re not flying through more turbulence than other passengers. You’re flying through the same air, with a brain that’s already decided what every bump means.

That’s not Turbli’s fault. That’s just how anxiety works when you give it a forecast to obsess over.

So if the app isn’t the answer… what should you actually trust?

Read more

Pilot Nick — 6 min read

Last winter I was deadheading home that’s airline-speak for flying as a passenger so I can pick up my next trip the following morning and the woman seated beside me did something I’d never quite seen on a flight before. She was reading an article. And about halfway through it, she started to cry.

I’d taken the aisle, the way I always do on positioning flights. She was at the window. Mid-forties, neat coat across her lap, no carry-on bag, the kind of passenger who flies because she has to, not because she enjoys it.

Subscribe now

I’d been half-watching her since boarding. The white knuckles on the armrest. The slow, deliberate breathing. When the boarding door thumped shut she let out a small, private exhale that I recognized, the one nervous flyers make when they accept there’s no longer an option to walk back up the jet bridge.

About ten minutes into the climb, she pulled out her phone, started reading, and her eyes filled.

“Are you alright?” I asked, the way you do.

She turned the screen toward me. One of those splashy headlines about climate change and turbulence half doom, half clickbait.

“Is it true?” she said. “Not in my head. For real. The sky is actually getting rougher?”

I told her the truth.

Yes. It is and I will explain you why

Read more

🕒 12 min read · Black Box Series · Episode 02 · Pilot Nick

July 23, 1983. A Saturday evening in central Canada.

A brand-new Boeing 767, just five months old, is cruising at 41,000 feet over a place called Red Lake, Ontario.

Sixty-one passengers. Eight crew. A standard domestic flight from Montreal to Edmonton.

In the cockpit Captain Robert “Bob” Pearson, 48 years old, 15,000 hours of flight time. Beside him First Officer Maurice Quintal, 36, ex-Royal Canadian Air Force.

It’s a quiet flight. The kind of evening sector pilots love. Smooth air. Clear sky. The sun is going down over the Canadian shield.

Then a single chime fills the cockpit.

Four notes. Soft. Almost polite.

Both pilots glance at the warning panel.

It says the aircraft has a fuel pressure problem on the left side.

Pearson and Quintal exchange a look the look pilots give each other when something on the panel doesn’t quite make sense. Because according to the fuel quantity readout in front of them, they have plenty of fuel.

Plenty.

Ninety seconds later, the left engine flames out.

Thirty seconds after that, the right one follows.

And the world’s most modern airliner a brand-new, twin-engine, computerized 767 becomes the largest glider in commercial aviation history.

What happens in the next 17 minutes is taught in every airline training program on Earth.

If you’re new here Black Box is the series where I take a real aviation incident and break it down the way a pilot actually thinks about it.

Not the news version. Not the dramatized version.

The version from the left seat.

What the crew saw. What they decided. Why. And most importantly for the nervous flyers reading this what changed afterwards, so that you never have to.

Read more

Pilot Nick — 7 min read

Here’s something that might surprise you.

On a normal flight from New York to London, there are roughly 7 hours where I’m calm, alert, and doing my job at a relaxed pace.

Subscribe now

And then there are two windows each about 90 seconds long where every pilot on the flight deck goes completely silent, locks onto the instruments, and runs through a very specific mental checklist.

Most passengers never notice either one.

No announcement. No change in engine sound. No visible cue from the cabin.

But if you knew what we were watching for, you’d realize something: the two most carefully monitored moments of your entire flight aren’t takeoff and landing themselves.

They’re the moments inside takeoff and landing that almost no one outside the flight deck has ever heard of.

Both have hard rules. Both can be aborted. And both exist because decades of accident data taught the industry something uncomfortable: the most dangerous mistake a pilot can make is trying to salvage a bad situation instead of making a clean decision.

Let me show you both.

Read more

🕒 12 min read · Black Box Series · Episode 01 · Pilot Nick

At 37,000 feet over the Indian Ocean, on a clear June night in 1982, 247 passengers were finishing dinner.

Then the windows began to glow.

Not the soft glow of a sunset. A strange, electric blue shimmer dancing along the leading edge of the wings. Inside the cabin, a smoky haze began drifting down the aisles. It smelled oddly like sulfur.

Captain Eric Moody was in the cockpit of British Airways Flight 009, a Boeing 747 en route from Kuala Lumpur to Perth. He’d been flying for decades. He had never seen anything like this.

And in the next 90 seconds, every single one of his four engines would quietly shut down.

One. By. One.

You voted for it, so here it is.

Black Box is a new series inside Lessons From The Flight Deck where I take real aviation incidents, the ones that made history and break them down the way a pilot actually thinks about them.

Not the dramatized version. Not the Wikipedia summary.

The cockpit view.

What the crew saw. What they decided. What they felt. And most importantly what it teaches us about how modern aviation became one of the safest things you can do on this planet.

We’re starting with BA009. Because if you’ve ever worried about something going wrong at cruise altitude, this story will change how you think about it forever.

Let’s go back to that night.

The Strangest Warning in Aviation

The first clue something was wrong wasn’t an alarm.

It was the smell.

The flight engineer, Barry Townley-Freeman, noticed it first — that faint, sharp, sulfuric scent. Then the haze. Then a passenger sitting near the window looked out and saw something impossible: the engines were glowing.

Not on fire. Glowing.

Long streams of luminous blue-white light were streaming backward from all four engine cowlings, like the plane was flying through a thunderstorm made of stars. The leading edges of the wings shimmered with the same eerie light.

This is a phenomenon called St. Elmo’s Fire, an electrical discharge that happens when an aircraft flies through particles that build up a static charge on the airframe. Pilots see it occasionally in thunderstorms. It’s harmless.

But there were no thunderstorms that night. The radar was clean. The sky was clear.

So what were they flying through?

At 13:42 UTC, they got their answer.

4️⃣ Engine four flamed out.

Moody and his first officer, Roger Greaves, ran the shutdown drill. A single engine failure on a 747 is serious, but manageable. The aircraft can fly comfortably on three.

Then, less than a minute later:

2️⃣ Engine two flamed out.

Then almost simultaneously:

1️⃣ + 3️⃣ Engines one and three.

All four. Gone.

The most powerful commercial jet in the world had just become the world’s largest, heaviest, and least aerodynamic glider — 180 tons of metal, 247 souls on board, 37,000 feet above the black Indian Ocean.

“Ladies and Gentlemen, This Is Your Captain Speaking...”

What Captain Moody said next became one of the most famous PAs in aviation history.

He keyed the mic. His voice was calm. Almost casual.

“Ladies and gentlemen, this is your captain speaking. We have a small problem. All four engines have stopped. We are doing our damnedest to get them going again. I trust you are not in too much distress.”

Read that again.

A small problem.

That line is studied in pilot training to this day not because it was clever, but because it reveals something fundamental about how pilots are trained to think in a crisis.

Here’s what most people don’t understand about that moment:

What Was Actually Happening Behind the Scenes

While passengers stared at glowing wings and wondered if they were about to die, the flight deck was a masterclass in disciplined problem-solving.

Moody and his crew were doing three things at once, all from memory:

1. Flying the aircraft. This sounds obvious, but it’s the first rule drilled into every pilot: Aviate. Navigate then Communicate.In that order. Always. No matter what’s on fire, screaming, or failing, fly the plane first. Moody trimmed the 747 for its best glide speed, a figure he knew cold: roughly 250 knots, giving them a glide ratio of about 15:1. For every foot they descended, they’d travel 15 feet forward.

2. Running the restart drill. The 747’s engines can be relit in flight — but only within a specific envelope of altitude and airspeed. Too high and the air is too thin for combustion. Too slow and the windmilling turbines won’t spin fast enough. The crew had to descend into the restart window while still trying to clear whatever mountains lay between them and Jakarta.

3. Solving a mystery. Nothing about this made sense. Four simultaneous engine failures on a modern jet is statistically almost impossible. The checklists didn’t have an answer. The weather radar showed clear skies. Whatever had caused this, they were still flying through it.

Subscribe now

The next part is where this story becomes extraordinary and where it stops being just a historical curiosity and starts being something that genuinely changed how modern aviation protects you every time you fly.

What the crew of BA009 discovered in the next 14 minutes rewrote the safety rules of the entire industry. It’s the reason a threat that was invisible to pilots in 1982 is now tracked by satellites, monitored by nine dedicated centers around the world, and briefed to every captain before every flight.

But to understand why, you have to understand what Moody did next and the single decision that saved 247 lives.

🔒 The rest of this story is for paid subscribers.

Read more

I’ve logged over 10,000 hours in the left seat.

But a few times a year, I’m just like you boarding pass in hand, backpack under the seat in front of me, trying to figure out if the guy in 24B is going to claim both armrests.

Here’s the thing most passengers don’t know:

I never stop being a pilot.

Even when I’m in row 24 with a ginger ale, there’s a quiet checklist running in the back of my head before the flight. It’s not anxiety. It’s not paranoia. It’s just the habit of 25 years of flying, the same instincts that kick in before I push the throttles forward.

It runs fast. A minute or two, tops. And most of what I’m checking boils down to one question: is this flight going to leave on time?

So today I’m handing it to you. Seven things I check before every single flight from the moment I walk into the terminal to the moment we close the doors.

Screenshot this one. You’ll use it on your next trip.

1. The Weather — But Not the Way You Think

Most passengers check the weather at their destination. Will it rain? Do I need a jacket?

I check three things:

• Departure airport weather (wind, visibility, thunderstorms nearby)

• Destination weather (same, plus the forecast for my arrival window)

• Anything big happening between the two (a line of storms over the Midwest, for example)

Why? Because weather doesn’t just affect takeoff and landing. It shapes the route. A line of thunderstorms over Kentucky might mean a smoother or bumpier ride depending on how we go around it.

You don’t need to be a meteorologist. I use the same free app most pilots glance at: Windy.com. Zoom out. Look at the big picture between your two cities. If you see a big red blob, expect some deviations. That’s not scary, that’s your crew doing their job.

Read below if you want to know more about Weather App 👇🏻

2. The Aircraft Type — and My Boarding Strategy

This one takes 10 seconds on the airline app and completely changes how I play the boarding game.

If you’ve read The Boarding Mistake 90% of Passengers Make, you already know this:

The goal isn’t to be first on the plane, it’s to minimize your time sitting in a packed cabin or worst in the Jetty.

That’s the principle.

(I’ll link the article below if you missed it👇🏻)

Share Lessons From The Flight Deck ✈

But the right wait time depends entirely on what aircraft you’re on. Here’s how I adjust:

Widebody (777, A350, 787, A380): Boarding 250-400 people takes a while. I wait. Sometimes 20-25 minutes after boarding starts. I want to be one of the last 15% on the plane. Overhead bin space is not a concern — there’s plenty. My carry-on will find a home near my seat. What I’m avoiding is 30 extra minutes of sitting in a metal tube while the rest of the cabin files in past my knees.

Narrow-body mainline (737, A320, 757): My sweet spot. 10-15 minutes after general boarding begins. The initial jam has cleared, most bins are still open, and I can walk straight to my row without the stop-and-go shuffle.

Regional jet (CRJ, E175, Embraer 145): Here’s where my strategy flips. On a small regional jet, overhead space is brutally limited — those bins barely fit a backpack, let alone a 22-inch roller. Board too late and you’ll be forced to gate-check your bag, then wait on the jet bridge at your destination to reclaim it.

So on a regional jet, if I’m traveling with a carry-on I actually need? I board earlier. Not in the first wave, never in the first wave but I don’t push my luck either. 5-7 minutes after boarding starts is my move. Enough to let the jam clear, early enough to protect my bag.

The quick rule: Big plane = wait longer, protect your sanity. Small plane with a carry-on = board earlier, protect your bag.

3. My Seat Position

If you’re a nervous flyer, my advice hasn’t changed: sit over or just ahead of the wing. I wrote a full breakdown of why in Pilot’s Secret for a Smooth Flight: Sit Here. Short version — the wing is the pivot point of the aircraft, so turbulence feels noticeably milder there. If bumps make you anxious, that’s your seat.

Read my article below explaining the bext seat for a smooth flight 👇🏻

Leave a comment

But when I’m flying as a passenger? My priorities are different. Here’s what I actually look for:

Read more

On Monday, Bloomberg broke the story. United Airlines CEO Scott Kirby has been pitching the idea of merging with American Airlines to the White House.

Not to a boardroom. Not to shareholders. To government officials, reportedly during a meeting at the White House in late February that was originally scheduled to discuss the future of Dulles Airport.

Kirby apparently raised the merger idea at the tail end of that agenda.

Let that sink in for a second.

If this deal ever goes through, United and American combined would become the largest airline on the planet. We’re talking about two carriers that together control more than a third of the entire U.S. domestic market. A combined fleet that would dwarf anything else flying today. Hubs at O’Hare, Dallas-Fort Worth, Newark, Denver, Charlotte, LAX, Miami, Houston, Washington Dulles basically, everywhere.

And I’ll tell you this: the conversation around this merger is already wrong.

Pundits are talking about stock prices. Analysts are arguing about antitrust law. Cable news is debating politics.

Nobody is asking the question that actually matters to you:

What does this mean for the person sitting in seat 14C?

That’s what I’m going to break down today. Because I’ve lived through airline mergers from the cockpit. I’ve seen what they do to operations, to crews, to the flight you’re about to board. And there are things happening behind the scenes right now that most people don’t understand.

🔒 The rest of this article is for paid subscribers.

Inside the cockpit, mergers don’t play out the way you think.

I break down what actually changes when two airlines become one:
• The hidden operational pressure pilots deal with
• Why the first 18 months are the most critical
• What’s really happening during turbulence, delays, and crew transitions
• And what every nervous flyer needs to understand to stay calm

This is the part you won’t hear on the news.

Read more

Frequent flyer or nervous flyer, the goal is the same:

👉 Feel in control when you travel

Over the past few weeks, I’ve reworked my entire ebook collection.

Cleaner. More focused. Built around one idea:

giving you the same clarity we use in the cockpit

Inside, you’ll learn how to:
• choose better seats (and avoid the worst ones)
• travel more efficiently through airports
• understand what’s actually happening during your flight
• feel calmer and more confident from takeoff to landing

No guesswork. Just practical insights from 25+ years in the flight deck.

Ebooks at 20%

For the next 24 hours:

👉 20% off all ebooks 💰
Use code: SPRINGBREAK20
(ends tomorrow at midnight)

If you fly often or want to feel better when you do this will change how you travel.

Ebooks 24h at 20%

Fly safe,
Pilot Nick ✈️

N-171D Boeing B-767-300ER

She was built during the George H.W. Bush administration.

She took her first breath of sky on April 22, 1990 — a test flight out of Boeing’s factory in Everett, Washington. Six weeks later, she was delivered to Delta Air Lines, registration N171DN, and she never wore another airline’s name for the rest of her life.

On April 9, 2026, she flew her final revenue flight — Delta 715 from San Francisco to Atlanta. The next morning, she ferried quietly to Birmingham, Alabama, where she’ll be taken apart, piece by piece.

No fanfare. No water cannon salute. Just one last flight to the scrapper.

That’s a pilot’s airplane. She didn’t need a ceremony. Her logbook spoke for itself.

BY THE NUMBERS

Here’s what 36 years of flying looks like.

Over 150,000 flight hours. Think about that for a second. That’s more than 17 years of continuous, non-stop flight without ever touching the ground. It’s roughly 6,250 days in the air.

She crossed every ocean Delta flies. She connected Atlanta to Europe, to Asia, to Latin America. In her younger years, she was an international workhorse — the kind of airplane that made Delta a global airline. In her later years, she settled into transcontinental routes: ATL to SFO, ATL to JFK, ATL to Phoenix. Still earning her keep. Still carrying passengers. Still running.

The only time she stopped was during COVID. From January 2020 to April 2021, she sat in storage — like most of the world’s fleet. Then she came back and flew for five more years.

Even in her final weeks, she wasn’t parked in a hangar waiting for a retirement party. She was flying real routes, carrying real passengers, generating real revenue. Delta was squeezing every last ounce of value out of this airplane right up to the end. That tells you something about how good she was.

THE AIRPLANE THAT CHANGED THE RULES

This is where it gets fascinating and where this story becomes bigger than one airplane.

Before the 767, there was a hard rule in aviation: twin-engine airplanes could not fly more than 60 minutes from a suitable diversion airport. That meant if you wanted to cross an ocean, you needed three or four engines. Period. The 747. The L-1011 TriStar. The DC-10. Those were your only options.

The thinking was simple. If you lose an engine over the middle of the Atlantic on a twin-engine jet, you’d better be close to land.

In 1980, when Boeing approached the FAA about flying the 767 on long overwater routes, the FAA administrator’s response was blunt. He said he wouldn’t allow twin-engine jets to fly long-haul overwater routes — and he didn’t mean for just a year or two.

But Boeing had the data. The 767’s engines were achieving reliability numbers no previous powerplant had ever matched. The airplane itself had built-in redundancy that made it fundamentally different from anything that came before — dual hydraulic systems, advanced avionics, and an Engine-Indicating and Crew-Alerting System (EICAS) that gave pilots real-time engine health data we’d never had access to before.

In 1985, TWA flew the first ETOPS revenue flight: a 767 from Boston to Paris under a brand-new 120-minute rule. The airplane burned thousands of pounds less fuel than the L-1011 TriStar it replaced on that same route.

By 1991, more passengers were crossing the Atlantic in 767s than in three- and four-engine jets combined.

By 2000, half of all transatlantic crossings were made by 767s.

The 767 didn’t just fly the routes — it invented them. It proved that two engines, proper engineering, and rigorous maintenance were enough to cross any ocean on Earth. Every twin-engine jet you fly on today — the 787, the A350, the 777 — exists because the 767 proved it could be done.

So when you hear that N171DN has been retired, understand what you’re really hearing. You’re hearing the final chapter for one of the airplanes that changed the fundamental rules of how we fly.

Subscribe now

But there’s a lot more to this airplane’s story and to the 767 itself that most people never hear about. Including the incredible story of how Delta got its very first one.

✈️ There’s more to this story.

In 1982, three Delta flight attendants did something no airline employees had ever done before or since. That story, plus the 10 facts about this airplane that made me fall in love with the 767 the first time I flew one.

Read more

You’re sitting at the gate. It’s January. Boarding was on time, the doors are closed, and then… nothing happens.

A few minutes pass. Then you see it through the window — a truck pulling up with a long mechanical arm, and suddenly your airplane is getting hosed down with a bright green (or orange) liquid. The captain comes on and says something about “de-icing procedures” and a brief delay.

Half the cabin groans. A few people pull out their phones to text about running late.

But here’s the thing: what you just watched might be the single most important thing that happens to your airplane all day.

And from the cockpit, we’re not frustrated by the delay.

We requested it.

Let me show you what’s really going on.

Lessons From The Flight Deck ✈ is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Read more

I’ve heard it hundreds of times.

A passenger in first class, half-joking as they sip their drink, leans toward a flight attendant and says: “So… are the pilots actually up there, or did the computer take over?”

Everyone laughs. But the question is serious and the assumption behind it is one of the most common misconceptions in all of aviation.

People genuinely believe that once autopilot is on, the cockpit goes quiet. That we kick back, read a magazine, maybe catch a nap.

I want to set the record straight. Not just to defend my profession but because understanding what’s really happening up front might be the single most reassuring thing you’ll ever learn about flying.

WHAT YOU PICTURE

Here’s what most passengers imagine:

Climb to cruise altitude. Press a button. Put the plane on autopilot. Coffee. Crossword puzzle. Maybe a quick nap. Wake up 8 hours later for descent.

“The computer’s flying. The pilots are just there in case something goes wrong.”

I understand where this comes from. Aviation movies. News reports. A general sense that modern aircraft are so sophisticated they practically fly themselves.

And on the surface? It looks that way. Cruising at 37,000 feet, the aircraft is smooth, stable, and seemingly serene.

But here’s what you don’t see.

Subscribe now

WHAT’S ACTUALLY HAPPENING

The moment autopilot engages — typically a few minutes after takeoff — it doesn’t mean we stop flying the aircraft. It means we change how we’re flying it.

Think of autopilot like cruise control in a car. You’ve set your speed, but you’re still steering, watching the road, anticipating the curve ahead, ready to brake if something unexpected happens. You haven’t handed the wheel to the car and gone to sleep.

Now multiply that by a hundred. Add weather systems across three time zones. Air traffic control instructions every few minutes. Fuel calculations updating in real time. Contingency planning for airports you might never visit.

That’s closer to what we’re doing.

On a long-haul flight, my co-pilot and I will monitor dozens of systems, receive multiple re-routes, cross-check fuel burns against our flight plan, and brief for alternate procedures — all while the autopilot holds our altitude to within 10 feet.

But here’s where it gets genuinely interesting — and this is the part most passengers never hear about.

The autopilot isn’t making decisions. We are. Every input it follows comes from us. Every constraint it works within, we set. Every change in route, altitude, or speed — that’s the pilots talking to the aircraft through a system called the Flight Management Computer.

And managing that system, while simultaneously monitoring engine performance, weather radar, hydraulic pressures, fuel balance, cabin altitude, and a hundred other parameters…

That’s a full-time job. That’s our full-time job.

What I’m about to share inside the paid section is something most people never get to see: a real breakdown of what a typical cruise phase looks like from the left seat — the decisions being made, the systems being watched, and the one thing that happens on almost every long-haul flight that would surprise even the most frequent flyer.

Subscribe HERE

Read more

I want to tell you about a message I received.

I won’t share her name, but she’d been reading this newsletter for about three months. She was what I’d call a “quiet subscriber” never commented, never replied to a post. Just opened every email and read it.

Then one day she sent me a message:

“Nick, I haven’t been on a plane in 6 years. I missed my sister’s wedding in Portugal. I missed my best friend’s 40th in Bali. My family stopped inviting me on holidays because they knew I’d say no. I’ve tried therapy, I’ve tried medication, I’ve tried hypnotherapy. Nothing worked because nobody could answer the one question that kept me up at night: what is actually happening up there?”

That question what is actually happening up there? is the question I’ve spent 28 years answering. Not in a textbook way. Not with statistics. But from the seat where I sit every day, hands on the controls, watching the instruments, listening to the sounds, and knowing exactly what every single one of them means.

So I told her what I tell every nervous flyer who asks:

Your fear isn’t irrational. It’s uninformed.

There’s a difference. An irrational fear has no basis, you’d be scared even with all the facts. An uninformed fear disappears when you understand what’s actually going on. And for the vast majority of nervous flyers, the fear is uninformed. It lives in the gap between what you experience as a passenger and what we know in the cockpit.

She went through my Fear-Free Flying Masterclass. All of it. She told me she watched the turbulence module three times.

And then last week, she sent me this:

“I’m on a plane right now. 38,000 feet. We hit some chop 20 minutes ago and instead of panicking, I thought: ‘that’s just the jet stream boundary Nick talked about.’ I can’t believe I’m writing this from the air.”

Subscribe now

I’m not sharing this to sell you something. I’m sharing it because I know there are people reading this right now who are in the same position she was avoiding flights, missing life events, and feeling stuck.

You don’t need more courage. You don’t need to “just relax.” You need someone who sits in the cockpit every day to explain what’s happening, in plain language, with honesty.

That’s what the masterclass does. It’s not therapy. It’s not meditation. It’s a pilot giving you the manual to your own flight — every sound, every bump, every phase, every “what if” — so your brain stops filling the gaps with fear.

The Fear-Free Flying Masterclass — $149. Self-paced. Lifetime access.

See what’s inside the Masterclass

And if her story resonated with you — if you’re the person who’s been reading this newsletter quietly, avoiding flights, and wishing things were different — I want you to know: it can be different. I’ve seen it hundreds of times. Understanding is the exit door from fear.

Fly Safe,

Pilot Nick