Baikonur accidents, damage and disasters: what happened and what is still active

Timeline of major accidents (Nedelin → modern era → 2025)

1960: Nedelin catastrophe

On 24 October 1960, an R‑16 ballistic missile exploded on its launch stand at the Baikonur test range during pre-launch operations, engulfing the pad in fire. Official Soviet figures long cited about 90 fatalities, while later research and declassified sources indicate 60–120 or more dead, including Chief Marshal of Artillery Mitrofan Nedelin, after whom the disaster is named. The cause was a combination of schedule pressure, on-pad work with a fully fuelled hypergolic missile, and violations of safety procedures during troubleshooting.

1990s–2010s: Proton and Soyuz failures, environmental damage

Baikonur also saw a series of Proton and Soyuz launch failures whose debris and propellants impacted Kazakh territory:

• In 1999, a Proton‑K failed shortly after launch, crashing in Kazakhstan and prompting protests and compensation disputes due to heptyl (UDMH) contamination.
• Multiple Proton failures in the 2000s damaged payloads and scattered toxic fuel and debris over steppe impact zones, with Kazakh and Russian sources documenting ecological concern.
• On 2 July 2013, a Proton‑M carrying three GLONASS satellites veered off course seconds after liftoff, crashed near the pad, and released large quantities of unburned heptyl-based propellant into the environment.
• In August 2011, a Soyuz‑U failed during a Progress cargo launch to the ISS, with the upper stage and spacecraft crashing in the Altai region and raising questions about engine quality control.

These events led to temporary stand-downs of Proton or Soyuz variants, inspections, and sometimes hardware redesigns, but launches from Baikonur resumed after corrective actions.

2018: Soyuz MS‑10 in-flight abort

On 11 October 2018, Soyuz MS‑10 suffered a booster separation failure about two minutes after launch from Baikonur, triggering an automatic abort that separated the crew capsule and returned it safely to Earth. Investigations traced the cause to a bent or improperly installed sensor on one of the strap-on boosters, and Soyuz flights were paused until inspections and process changes were implemented. The key point for risk perception: the abort system worked as designed, and crew survived without serious injury.

2025: Soyuz MS‑28 and the Site 31/6 collapse

On 27 November 2025, Soyuz MS‑28 lifted off from Baikonur’s Launch Pad 31/6; about 10 seconds after liftoff, the pad’s mobile service platform (service cabin) failed to remain secured in its underground shelter and was torn from its rails by the exhaust jet, collapsing into the flame trench. No crew were harmed, but the accident severely damaged structural elements, access platforms, and cabling, instantly rendering Russia’s only crew‑capable pad at Baikonur unusable.

Analysts noted that this single event temporarily halted Russia’s ability to launch Soyuz or Progress spacecraft from Baikonur, marking the first time since 1961 that Russia had no operational domestic pad for crewed orbital launches.

2025 case: what exactly was damaged?

Technical reports describe the damaged hardware as the mobile service platform (also called a service or maintenance cabin, index 8U216/8U0216) that wraps around the lower part of the Soyuz vehicle on the pad.

Key points of damage:

• The platform failed to lock in its parked position beneath the pad; blast forces pulled it off guide rails into the flame trench.
• The fall deformed access platforms, support structures, and attachment points used to reach the rocket’s lower stages and connect fueling lines.
• Because 31/6 was Russia’s only Baikonur pad certified for crewed Soyuz launches, the collapse effectively removed all crew and Progress launch capability from Baikonur until repairs were complete.

Investigative reporting and expert commentary suggest that launch management accepted this configuration despite not fully securing the platform, likely under pressure not to delay a high-profile mission attended by officials and thousands of tourists.

Why these accidents happen (root causes)

Several recurring factors show up across Baikonur’s failures:

• Aging Soviet infrastructure – Many key structures, including the service platform at 31/6, trace their design back to the 1950s–1970s and have been kept in service with partial refurbishments under constrained budgets.
• Complex launch systems – Multi-stage, liquid-fuel rockets with strap-on boosters and intricate ground support equipment are inherently complex; failures in sensors, separation mechanisms, or ground-handling procedures can cascade into major incidents.
• Toxic hypergolic propellants – Proton rockets and some upper stages use heptyl-based fuels that are highly toxic, amplifying the environmental impact when things go wrong.
• Human and organizational factors – Investigations repeatedly highlight human error, schedule pressure, and management decisions overriding conservative safety criteria (Nedelin catastrophe, Proton mishaps, and the 2025 pad accident all show this pattern).

In other words, Baikonur’s risk profile is not “mysterious bad luck” but a mix of aging hardware, hazardous propellants, complex integration, and occasionally brittle organizational culture.

Recovery and repairs: how Baikonur comes back after failure

Historical pattern

After the Nedelin disaster, the R‑16 program was redesigned and test procedures overhauled; the affected pad was rebuilt, and missile and space-launch operations continued from the range. Proton and Soyuz failures in the 1990s–2010s similarly led to temporary suspensions, inspections, and hardware/process changes, followed by a return to flight.

2025–2026: repairing Site 31/6

For the 31/6 collapse, Roscosmos and its ground infrastructure arm TsENKI mounted a concentrated repair effort:

• By December 2025, spare service-platform components sourced from legacy stock in Tambov and earlier deliveries were being shipped to Baikonur; a repair team of over 130–150 workers was deployed in multi-shift operations.
• Structural elements up to 19 m long and 17 tons were installed via the central opening of the pad using a specially developed method; a total of about 2,350 m² of structures were cleaned and painted and roughly 250 welded seams were made.
• On 3 March 2026, Roscosmos confirmed that a new service platform was in place and that Launch Pad 31/6 was ready to support flights again.
• The first post-repair mission, Progress MS‑33, was scheduled for 22 March 2026, restoring operational Soyuz‑2/Progress launch capability from Baikonur.

This pattern—serious incident, visible damage, but relatively fast technical recovery—is important for understanding today’s risk: Baikonur is fragile in places, yet still repairable.

What is still active today

Based on current reporting:

• Site 31/6 (Soyuz‑2 pad) – Repaired and returned to service in March 2026; slated to handle Progress MS‑33 and subsequent ISS-related missions.
• Other Soyuz and Proton pads – Proton and Soyuz launch complexes at Baikonur remain in use, with around nine launches projected for 2025, including crewed and cargo flights plus satellite missions.
• Gagarin’s Start (Site 1/5) – Historically central but currently in a state of limited or suspended use pending modernization for newer Soyuz‑2 hardware; it is not carrying the main load of crewed launches right now.

Operationally, Baikonur is no longer the huge multi-pad system it was in the 1970s–1980s, but it still supports regular Soyuz and Proton missions after the 31/6 repair.

System weaknesses: where Baikonur is vulnerable

From a risk perspective, Baikonur’s vulnerabilities include:

• Reliance on a small number of critical pads – With Gagarin’s Start offline, Site 31/6 became the only Soyuz crew pad; its 2025 damage immediately halted Russian domestic crew-launch capability until repairs.
• Aging ground infrastructure – Many systems were designed decades ago and now operate under sanctions, budget constraints, and limited access to foreign components.
• Geopolitical dependency – Russia leases Baikonur from Kazakhstan and simultaneously tries to shift activity to Vostochny; sanctions and political tensions can affect investment, modernization, and access.

This doesn’t mean Baikonur is about to fail; it does mean that single-point failures, like the 31/6 collapse, can have outsized impact.

Environmental damage: what rocket accidents do to the steppe

Studies from Kazakh and international researchers show that rocket accidents using heptyl-based fuels have measurable environmental consequences:

• Crashes of Proton and other heptyl-fuelled rockets contaminate soil with unburned UDMH and nitrogen tetroxide, affecting microbial activity, plant growth, and local fauna in impact zones.
• Field research at accident sites has documented changes in soil chemistry and toxicity over time, with some parameters gradually returning toward baseline but others remaining elevated for years.
• Local communities and authorities have repeatedly raised concerns about health and ecological effects, prompting compensation claims and stricter impact-zone management.

For visitors staying in the city and official tour zones, most of this risk is indirect—through long-term environmental health rather than acute exposure—but it is part of the broader risk picture.

Myths about Baikonur risk

• “Baikonur is unsafe and on the verge of catastrophic failure.”
  Reality: Baikonur has had serious accidents and aging infrastructure, but it also has a strong record of safe crewed operations over decades and a demonstrated ability to repair key systems like Site 31/6.
• “It’s hopelessly outdated.”
  Partly true: much hardware is old, yet incremental upgrades, inspections, and modern launch vehicles (Soyuz‑2, updated Proton‑M) mean it still meets current mission requirements.
• “It’s shutting down soon.”
  False in the near term: official statements and launch schedules show Baikonur continuing with multiple launches per year, while long-term strategy gradually shifts activity to other spaceports.

Current status: can Baikonur still be trusted?

Today, Baikonur is:

• Active – Launches are ongoing; Site 31/6 has been restored, and Proton/Soyuz missions continue to fly.
• Risk-bearing – It operates with aging infrastructure and a small number of chokepoint pads, meaning incidents like the 2025 collapse can temporarily halt key mission types.
• Adapted, not obsolete – It remains central to Russia’s ISS logistics and to certain commercial and scientific launches, even as Vostochny and other sites grow in importance.

For travelers and observers, the realistic conclusion is: Baikonur is not risk‑free, but it is not a collapsing relic either; it is a stressed but functioning system under continuous repair and adaptation.

Is Baikonur too old, too damaged, or too risky?

If you are thinking, “Baikonur feels too old, too damaged, or too risky to be reliable,” here are five concise answers:

1. Track record matters: despite notable failures, Soyuz has safely flown hundreds of crews from Baikonur, and the MS‑10 abort showed that crew safety systems work as intended.
2. Infrastructure can be repaired: the 2025 collapse was serious, but Site 31/6 was rebuilt in a few months, not years, and is back on the launch schedule.
3. Risks are understood and bounded: known issues—aging structures, toxic fuels, chokepoints—are recognized by engineers and analysts, which is why launches pause for inspections after incidents.
4. Alternatives exist at system level: even if Baikonur pauses certain missions, global crew and cargo access to orbit now includes vehicles from the U.S., Japan, and others, reducing systemic risk to human spaceflight overall.
5. For visitors, risk is mostly contextual: the primary risk you experience on-site is schedule and infrastructure uncertainty, not personal safety in the way the 1960s test crews faced.

Baikonur under pressure, not in free fall

Baikonur is not a simple success story, nor a simple disaster story; it is a launch system evolving under political, financial, and engineering pressure.

Understanding its accidents as failure → damage → recovery → current status shows that while individual events can temporarily halt missions or expose vulnerabilities, the overall system continues to adapt—maintaining a meaningful, if more fragile, role in global spaceflight rather than sliding into irrelevance.