{"id":6789,"date":"2025-11-28T08:06:15","date_gmt":"2025-11-28T08:06:15","guid":{"rendered":"https:\/\/readtrends.com\/en\/baikonur-crew-pad-damage\/"},"modified":"2025-11-28T08:06:15","modified_gmt":"2025-11-28T08:06:15","slug":"baikonur-crew-pad-damage","status":"publish","type":"post","link":"https:\/\/readtrends.com\/en\/baikonur-crew-pad-damage\/","title":{"rendered":"Baikonur\u2019s sole crewed pad suffers major damage during Soyuz launch"},"content":{"rendered":"<article>\n<p><time datetime=\"2025-11-28\">On Nov. 28, 2025<\/time>, a Soyuz MS-28 rocket lifted off from the Baikonur Cosmodrome and delivered three astronauts safely to the International Space Station, but the facility\u2019s only operational crewed launchpad, Site 31\/6, sustained significant blast damage during liftoff. Post-launch footage released by Roscosmos shows large structural elements displaced into the pad\u2019s flame trench and charred debris at the scene. Roscosmos told state media the complex is being assessed and that spare components exist to restore the site, while no crew harm was reported.<\/p>\n<ul>\n<li>Launch outcome: Soyuz MS-28 successfully reached the International Space Station on Nov. 28, 2025; all three crew members, including NASA astronaut Chris Williams, arrived safely.<\/li>\n<li>Damage observed: Roscosmos footage shows what appears to be a service-bay assembly displaced into the pad\u2019s exhaust trench with visible charring on structural pieces.<\/li>\n<li>Site affected: The impact was at Site 31\/6, Baikonur \u2014 Russia\u2019s only currently active pad for crewed Soyuz launches.<\/li>\n<li>Immediate response: Roscosmos told state media the launch complex is under assessment and that backup parts are available to restore the facility.<\/li>\n<li>Operational risk: With Site 31\/6 impaired and Gagarin\u2019s Start (Site 1) out of crewed use since 2019, Russia lacks an established alternate within Baikonur for routine crewed Soyuz departures.<\/li>\n<li>Historical context: Site 31\/6 dates to the 1960s; Baikonur remains leased from Kazakhstan while Russia develops Vostochny, which is not yet equipped for crewed missions.<\/li>\n<\/ul>\n<section>\n<h2>Background<\/h2>\n<p>Baikonur Cosmodrome, located in Kazakhstan and operated under long-term lease by Russia, contains several historic pads dating to the Soviet era. Site 31\/6 was built in the 1960s and has been used in recent years as the primary pad for Soyuz crewed missions after Site 1 (Gagarin\u2019s Start) ceased routine crewed operations in 2019. Russian authorities have discussed preserving Gagarin\u2019s Start as a cultural site rather than returning it to full flight duty.<\/p>\n<p>Russia has been expanding domestic launch infrastructure with the Vostochny Cosmodrome, but Vostochny has not completed the hardware and procedural certification needed for regular crewed flights. That leaves Baikonur \u2014 and in practice Site 31\/6 \u2014 as the near-term route for Soyuz transport to the International Space Station. Modernization proposals for older pads, including previous international interest, have not produced a ready alternate.<\/p>\n<\/section>\n<section>\n<h2>Main Event<\/h2>\n<p>During the Soyuz MS-28 liftoff on Nov. 28, visual material distributed by Roscosmos captured plume behavior and later aerial shots of the launcher area. Video from immediately after the ascent shows debris and a large, charred object lying in the pad\u2019s exhaust trench that was not present in prelaunch footage. The imagery suggests part of the launch infrastructure \u2014 identified in industry terms as the service bay assembly \u2014 became dislodged as booster engines fired.<\/p>\n<p>State-controlled media published the agency\u2019s preliminary assessment, noting the launch itself proceeded nominally and the crew were unharmed. Roscosmos said teams are inspecting the launch complex and that necessary backup components are available to restore the pad. The agency did not provide a detailed technical diagnosis or a timeline for repairs in its initial comments to state outlets.<\/p>\n<p>Observers noted that footage of the trench immediately before liftoff showed an empty flame trench, meaning the displaced structure likely came from below the pad during engine ignition. The visible charring and the placement of debris in the trench are consistent with either a structural collapse under engine loads or a secondary blast\/overpressure event, though cause remains under investigation.<\/p>\n<\/section>\n<section>\n<h2>Analysis &#038; Implications<\/h2>\n<p>Operationally, damage to Site 31\/6 complicates Russia\u2019s short-term ability to send crews to orbit from Baikonur. With Site 1 out of routine service since 2019 and Vostochny not yet certified for crewed missions, there is limited immediate redundancy for Soyuz departures. Depending on the full extent of damage and the length of repairs, crew rotation schedules and cargo flights could face delays or require alternative arrangements with international partners.<\/p>\n<p>Technically, the most likely direct impact is to pad turnaround time. Replacing a service bay and repairing structural elements beneath a launcher deck typically requires careful engineering assessment, removal of compromised components, and installation of replacement systems \u2014 work that can take weeks to months depending on supply, skilled labor availability, and whether foundations were undermined by heat or blast forces.<\/p>\n<p>Strategically, the incident highlights Russia\u2019s reliance on legacy infrastructure outside its borders and the vulnerability this creates. The Baikonur lease remains a geopolitical and operational constraint; until Vostochny reaches maturity for crewed flights, any prolonged outage at Site 31\/6 would force Moscow to seek contingency plans that could include accelerated upgrades at Vostochny, limited use of robotic launches only, or emergency international arrangements.<\/p>\n<p>Financially and programmatically, repair costs and schedule disruption could influence Soyuz cadence and budget priorities. If major components need replacement or if investigations identify systemic design or maintenance issues, Roscosmos may face additional scrutiny over safety procedures and infrastructure investment plans.<\/p>\n<\/section>\n<figure>\n<table>\n<thead>\n<tr>\n<th>Launch Pad<\/th>\n<th>Era Built<\/th>\n<th>Current status (2025)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Site 31\/6 (Baikonur)<\/td>\n<td>1960s<\/td>\n<td>Active for crewed Soyuz launches; damage reported Nov. 28, 2025<\/td>\n<\/tr>\n<tr>\n<td>Site 1 \/ Gagarin\u2019s Start (Baikonur)<\/td>\n<td>1950s<\/td>\n<td>Out of routine crewed service since 2019; slated for museum\/heritage use<\/td>\n<\/tr>\n<tr>\n<td>Vostochny Cosmodrome (Russia)<\/td>\n<td>2010s\u20132020s<\/td>\n<td>Under development; not yet certified for regular crewed launches<\/td>\n<\/tr>\n<\/tbody>\n<\/table><figcaption>Comparison of Baikonur crewed pads and Russia\u2019s Vostochny site (contextual summary).<\/figcaption><\/figure>\n<p>Context: the table shows why losing Site 31\/6 would reduce immediate redundancy for crewed missions. Repair timelines will determine whether schedule impacts are measured in weeks or months.<\/p>\n<section>\n<h2>Reactions &#038; Quotes<\/h2>\n<blockquote>\n<p>&#8220;The launch complex&#8217;s condition is currently being assessed,&#8221;<\/p>\n<p>    <cite>Roscosmos (statement to state media)<\/cite>\n  <\/p><\/blockquote>\n<blockquote>\n<p>&#8220;All necessary backup components are available for restoration, and the damage will be repaired soon,&#8221;<\/p>\n<p>    <cite>Roscosmos (statement to state media)<\/cite>\n  <\/p><\/blockquote>\n<blockquote>\n<p>&#8220;If a service-bay assembly has been expelled or destroyed, inspections and component replacement could extend pad downtime by weeks or months,&#8221;<\/p>\n<p>    <cite>space industry consultant (comment to press)<\/cite>\n  <\/p><\/blockquote>\n<p>Each quote was released as part of preliminary statements or commentary while formal engineering inspections continue. Roscosmos emphasized crew safety and restoration capacity; independent analysts flagged the potential for meaningful schedule impacts depending on inspection results.<\/p>\n<\/section>\n<aside>\n<details>\n<summary>Explainer: service bay, flame trench, and why they matter<\/summary>\n<p>The service bay is a substructure beneath a launch pad that houses cabling, sensors, fluid lines and provides technicians access to the rocket\u2019s tail and stage interfaces. The flame or exhaust trench channels engine plumes away from the vehicle and pad during ignition and liftoff. Damage to either component can compromise pad safety systems, monitoring equipment and structural supports; even if a vehicle reaches orbit safely, pad repairs are essential to restore certified, repeatable launch operations.<\/p>\n<\/details>\n<\/aside>\n<section>\n<h2>Unconfirmed<\/h2>\n<ul>\n<li>The exact mechanical cause of the service-bay displacement \u2014 whether structural collapse, overpressure, or a localized explosion \u2014 has not been publicly confirmed.<\/li>\n<li>Roscosmos has not released a technical timeline for inspections and repairs; the length of pad downtime remains uncertain.<\/li>\n<li>The long-term programmatic impact on upcoming crew rotations and commercial payload schedules has not been disclosed and depends on repair duration and resource allocation.<\/li>\n<\/ul>\n<\/section>\n<section>\n<h2>Bottom Line<\/h2>\n<p>The Nov. 28, 2025 Soyuz MS-28 launch successfully carried three crew members to the ISS, but visible damage to Site 31\/6\u2019s subsurface service bay has introduced operational risk for Russia\u2019s immediate crewed launch cadence. With Site 1 offline for routine launches and Vostochny not fully prepared for crewed operations, Baikonur\u2019s remaining active pad is a critical single point of failure until repairs are completed or alternatives are certified.<\/p>\n<p>Authorities have signaled that restoration is possible using spare components, but independent analysts caution that full structural inspections and replacements can be time-consuming. The coming days and weeks of Roscosmos technical reporting will determine whether effects are limited and short-term or whether they prompt broader schedule and policy responses from Russia and partner agencies.<\/p>\n<\/section>\n<section>\n<h2>Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.businessinsider.com\/russia-only-way-send-astronaut-space-serious-blast-damage-baikonur-2025-11\" target=\"_blank\" rel=\"noopener\">Business Insider<\/a> \u2014 news report summarizing Roscosmos footage and state-media statements<\/li>\n<li><a href=\"https:\/\/www.roscosmos.ru\/\" target=\"_blank\" rel=\"noopener\">Roscosmos<\/a> \u2014 Russian federal space agency official releases and footage (official)<\/li>\n<\/ul>\n<\/section>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>On Nov. 28, 2025, a Soyuz MS-28 rocket lifted off from the Baikonur Cosmodrome and delivered three astronauts safely to the International Space Station, but the facility\u2019s only operational crewed launchpad, Site 31\/6, sustained significant blast damage during liftoff. Post-launch footage released by Roscosmos shows large structural elements displaced into the pad\u2019s flame trench and &#8230; <a title=\"Baikonur\u2019s sole crewed pad suffers major damage during Soyuz launch\" class=\"read-more\" href=\"https:\/\/readtrends.com\/en\/baikonur-crew-pad-damage\/\" aria-label=\"Read more about Baikonur\u2019s sole crewed pad suffers major damage during Soyuz launch\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":6784,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Baikonur crewed launchpad damaged in Soyuz liftoff \u2014 Insight News","rank_math_description":"During the Nov. 28, 2025 Soyuz MS-28 liftoff at Baikonur, a service-bay assembly appears to have collapsed into the flame trench. Crew safe; Roscosmos inspects and plans repairs.","rank_math_focus_keyword":"Baikonur, Soyuz MS-28, launchpad damage, Site 31\/6, Roscosmos","footnotes":""},"categories":[2],"tags":[],"class_list":["post-6789","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-top-stories"],"_links":{"self":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts\/6789","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/comments?post=6789"}],"version-history":[{"count":0,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts\/6789\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/media\/6784"}],"wp:attachment":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/media?parent=6789"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/categories?post=6789"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/tags?post=6789"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}