Baikonur Cosmodrome Damage After Soyuz Launch

Incident Overview

On November 27, 2025, Russia's Roscosmos space agency reported significant damage to the launch pad at the Baikonur Cosmodrome in Kazakhstan during the liftoff of the Soyuz MS-28 mission to the International Space Station (ISS). The mission successfully delivered two Russian cosmonauts and one NASA astronaut to the ISS.

Damage Details

The damage primarily involved the collapse of a mobile servicing unit beneath the launch pad immediately after the rocket’s ascent. This servicing cabin is crucial for preparing crewed Soyuz and Progress missions and supports maintenance and operations. Its collapse led to parts falling onto launchpad 31, potentially causing extended suspension of launch operations.

Impact on Future Missions

The compromised servicing unit may result in significant delays for future crewed launches from Baikonur, Russia’s only launch site for manned missions. Although Roscosmos assured that all necessary spare parts are available and promised swift repairs, the incident marks the first time since the early 1960s that Russia may be unable to conduct crewed launches for a certain period.

Crew and Mission Status

Despite the launch pad damage, the Soyuz MS-28 spacecraft docked safely with the ISS, with the crew in good health. The team is expected to remain on the ISS for about eight months, with a planned return in late July 2026.

Roscosmos Response

Roscosmos stated that an evaluation of the launch complex’s condition is ongoing and reassured that the damage will be promptly repaired using reserves and spare parts. The agency is actively working to restore the Baikonur Cosmodrome to operational status soon.

“All necessary reserve are there to restore it. The damage will be eliminated very soon.” — Roscosmos


This incident underlines the vulnerability of Russia’s sole launch site for crewed missions and may prompt a reshuffling of spaceflight schedules and international space cooperation plans.

more

The Kyiv Independent The Kyiv Independent — 2025-11-28

More News