S7 Airlines and the Second Boeing Seven Thirty-Seven Runway Overrun in Six Weeks at Norilsk

An S7 Airlines Boeing 737-800 freighter overran the runway while landing at Norilsk in northern Russia, coming to rest past the end of the usable surface. According to AeroTime, this is the second runway overrun for the same airline, on the same aircraft type, within six weeks. As of this writing on August 10, 2026, formal investigation findings are not yet public, so the cause remains undetermined - but the recurrence itself is the story, and its lessons apply directly to your own flying.

What Happened at Norilsk

The aircraft, a Boeing 737-800 configured as a freighter, touched down at Alykel Airport serving Norilsk and rolled off the departure end of the runway. It stopped past the usable surface.

On its own, a single overrun is a routine incident report. What put this one on the wire is the timeline: two overruns, one operator, one fleet type, six weeks apart. When you see that pattern, you stop calling it bad luck.

To be clear, the detailed cause findings are not public. Anything below that moves into interpretation is flagged as such. Hold your conclusions loosely until the investigators finish their work.

Why Norilsk Is a Hard Place to Fly

Norilsk sits above the Arctic Circle and is one of the northernmost cities on Earth with a functioning airline network. Alykel operates in an environment hostile to aviation for most of the year - long, hard winters where blowing snow and ice are the default condition, and where a runway can go from adequate to treacherous in the span of a single weather cell.

That environment matters because on a contaminated runway - snow, slush, ice, or standing water - your stopping distance is not a fixed number. It’s a variable that can double, triple, or worse, depending on what’s actually on the pavement versus what the crew believes is there.

That gap - between what’s actually on the runway and what the crew believes - is where overruns live.

What a Runway Overrun Actually Is

A runway overrun is simple to describe and brutal in practice: the airplane touches down and there is not enough remaining runway to stop before the pavement ends. Sometimes it stops in the overrun area. Sometimes it goes through the fence. Sometimes it finds a ravine, a road, or water - which is why the industry treats overruns so seriously.

Fundamentally, an overrun is a landing distance problem. And landing distance is one of those calculations most of us computed carefully for exactly one checkride afternoon, then quietly stopped thinking about once we had a few hundred hours and a familiar home field.

Why This Matters for Your Flying

Landing distance depends on a stack of factors that don’t add up politely - they multiply: your weight, approach speed, density altitude, wind, runway slope, and surface condition.

The one that bites people is approach speed. Your POH numbers assume you cross the threshold at book speed - not five knots fast because it felt comfortable, not ten knots fast because a gust made you nervous.

Here’s the part that should make you sit up: excess speed doesn’t cost you landing distance in a straight line - it costs you exponentially. You carry that extra energy into the flare, you float, and every second of float is runway disappearing behind you at better than 100 feet per second in a light airplane, much faster in a jet.

Cross the fence 10% fast, and you can add 20% or more to your ground roll. Put a wet or contaminated surface underneath that, and the numbers stop being academic. The book landing distance has less margin than most pilots assume - and on a contaminated runway, some of that margin is already spent before the wheels touch.

What Two Overruns in Six Weeks Should Tell Any Operator

One overrun is an event. Two overruns - same operator, same type, six weeks apart - is a system telling you something.

The discipline of listening to that signal is called a safety management system (SMS), and every serious operator is supposed to run one. The idea is that you don’t wait for the accident. You collect the small signals - unstabilized approaches, late touchdowns, hard braking events, crews reporting they used more runway than expected - and you find the pattern before it becomes an airplane in the weeds.

A single overrun should trigger an investigation. A second, in the same window on the same fleet, should trigger a much louder look at training, procedures, and the landing performance data crews are using.

(Interpretation, flagged as opinion.) When you see two identical failures in six weeks, the question is almost never one crew having a bad day. The fairer question is what in the operating environment made the same outcome likely twice: Was the landing performance guidance realistic for those runway conditions? Were crews getting accurate, timely braking action reports? Was there pressure - spoken or unspoken - to complete the landing rather than go around and divert? Those are the questions a mature investigation asks. They’re also the questions any of us should ask after our own close call.

You have a safety management system too - a smaller one. It’s the honest debrief you give yourself after a landing that didn’t feel right. Two close calls of the same kind are not two accidents. They’re one warning, delivered twice.

The Airframe Is Rarely the Story

The Boeing 737-800 is one of the most common airliners on the planet - thousands flying, in passenger and freighter configurations, across every climate. It is a known, mature, well-understood machine. So when a specific operator has a specific recurring problem, the airframe is rarely the cause. The story is the operation around the airframe - the training, procedures, and how decisions get made when the weather is bad, the runway is short, and everyone wants to be on the ground.

That scales all the way down to us. Your Cessna 172, Piper, or Cirrus is also a known, well-understood machine. When one ends up off the end of a runway, it’s almost never because the airplane did something surprising. It’s because the planning, speed control, go-around discipline, or honest runway assessment broke down somewhere on the approach. The machines are reliable. It’s the decisions that get us.

Four Practical Takeaways for Your Next Approach

1. Compute the actual landing distance for the conditions you actually have. If the runway is wet, use the wet numbers. If it’s contaminated and your aircraft has contaminated-runway data, use it - and if it doesn’t, understand you’re operating where the manufacturer never charted, and add margin. A dry, sea-level book number on an icy strip isn’t a plan; it’s a hope.

2. Fly the speed. The stabilized approach concept exists for exactly this reason. Be on speed, on path, configured, and settled well before the threshold. If you’re not stabilized by your personal gate - 500 feet, 1,000 feet, wherever you draw the line - go around. There’s no trophy for salvaging a bad approach.

3. Practice touchdown-point discipline. The runway available to stop in starts at your wheels, not at the threshold. Every foot you float past the aiming point is stopping distance given away for free. Land in the touchdown zone, or don’t land.

4. Believe the runway, not the schedule. Whatever pressure exists to complete a landing has never once made a runway longer. Your airplane will stop where physics says it stops, not where the timetable wants it to.

The overrun is the most democratic accident in aviation. It happens to student pilots on their first solo and to seasoned freight crews above the Arctic Circle, and it happens for the same handful of reasons every time: too fast, too long, too much energy, too little runway, and a decision to land that should have been a decision to go around.

Key Takeaways

• S7 Airlines suffered its second Boeing 737-800 runway overrun at Norilsk in six weeks, per AeroTime; formal cause findings are not yet public as of August 10, 2026.
• Norilsk’s Alykel Airport sits above the Arctic Circle, where contaminated runways make stopping distance a variable that can double or triple.
• Excess approach speed costs landing distance exponentially - about 10% fast can add 20% or more to your ground roll.
• Two identical failures in six weeks point to the operation, not the airframe - the 737-800 is a mature, well-understood machine.
• Run your own numbers for real conditions, fly a stabilized approach, hold touchdown-point discipline, and go around when the approach isn’t right.