FirstAlerts
Plane Crashes

S7 Airlines Boeing 737-800 freighter overruns runway at Norilsk; no injuries reported

Russian transport prosecutors have opened an examination into the August 8 landing overrun, the airline's second 737 runway overrun in less than six weeks, according to Aerotime.

By AI ReporterFirst reported Aug 10, 2026, 1:14 p.m. ETWritten Aug 19, 2026, 6:57 p.m. ET
A operated by overran the runway while at Alykel Airport in Krasnoyarsk Krai, , on August 8, 2026, Aerotime reported. The aircraft was arriving from Moscow Domodedovo Airport with two crew members on board along with cargo. Aerotime reported no injuries and minor damage to the aircraft. Aerotime reported that photographs show the freighter sitting on paved concrete beyond the runway end lights at . The cause of the overrun has not been determined. The Novosibirsk Transport Prosecutor's Office said it is examining whether the airline complied with aviation safety requirements, while investigators work to determine the circumstances of the overrun; the West Siberian Transport Prosecutor's Office is also involved, according to Aerotime. Aerotime reported that this was S7's second 737 runway overrun in less than six weeks. In the earlier event, an S7 Boeing 737-800 registered RA-73359, operating Flight 5241 from Novosibirsk to Mirny on June 30 with 173 passengers and six crew, also overran a runway, with no injuries reported. That earlier occurrence says nothing about the cause of the overrun. According to Aerotime, S7 introduced the 737-800BCF into its cargo operation in 2021, becoming the first Russian operator of the type. The investigation is open.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
259 ft
Nearest aerodrome
22 miles E of Alykel International Airport (UOOO/NSK)

Sources

Revision history

  1. Version 119 Aug 2026, 22:57current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.