![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2026\/03\/IMG_5462.jpeg\")
<\/p>\n
Progress MS-31 docking to the Poisk module on July 5, 2025. (Credit: NASA)<\/p>\n
The cargo ship, also known as Progress 94 by NASA, will remain docked at the Station for roughly six months before it is loaded with trash, undocked, and commanded to make a destructive reentry into Earth\u2019s atmosphere over the South Pacific.<\/p>\n
See Also<\/h4>\n\n- Progress MS-33 Updates<\/li>\n
- ISS Section<\/li>\n
- NSF Store<\/li>\n<\/ul>\n
Prior to Progress MS-33\u2019s launch, Progress MS-31 undocked from the Poisk<\/em> module on Monday, March 16, and deorbited to a similar destructive reentry. This cleared the way for MS-33 to dock to the module. Progress MS-32 is docked to the Zvezda<\/em> module\u2019s aft port, while Soyuz MS-28 is docked to the Rassvet<\/em> module.<\/p>\nProgress MS-33\u2019s path to the pad and to flight was lengthy. The cargo ship was originally scheduled to fly in December 2025, but the flight was delayed for over three months due to an incident that took place during the Soyuz MS-28 launch on Nov. 27, 2025.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2025\/11\/IMG_4540-e1764539055298.webp\")
<\/p>\n
Image of the collapse maintenance cabin at Site 31\/6. (Credit: Kosmonavtiki Novosti)<\/p>\n
Although MS-28\u2019s ascent and orbital insertion went as planned, events on the ground at Site 31\/6 told a different story. In addition to a number of platforms on the launch tower, which splits up and retracts before flight, there is a mobile maintenance cabin underneath the rocket that is retracted before launch as well.<\/p>\n
That access platform, as a Roscosmos investigation found, was not properly secured, and the forces of launch caused the platform to fall into the flame trench. This fall caused severe damage and made the platform unusable. Without that platform, launches from Site 31\/6 could not proceed, and there were no other available launch pads that could host Soyuz launches to ISS.<\/p>\n
The maintenance platform is necessary to allow workers access to the lower half of the Soyuz rocket, where they can install pyrotechnics and remove protective covers.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2026\/03\/IMG_5464.png\")
<\/p>\n
The Progress MS-33 spacecraft during prelaunch testing. (Credit: RKK Energia)<\/p>\n
Roscosmos scrambled to fix the pad, as without it they would not be able to supply the Russian segment with fuel, water, or other consumables that the Zvezda<\/em> service module and the rest of the segment use, without assistance from partners.<\/p>\nAn extended period of time without the pad would also have rendered the Russians unable to launch crews on their own spacecraft or to conduct orbital reboost burns from their segment.<\/p>\n
After initial concern about the Russians\u2019 ability to produce a new platform, Roscosmos found a spare unit built during the 1970s. The unit needed modifications to service the current pad and rocket, but Roscosmos was able to finish the work in time for a spring launch of Progress MS-33.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/09\/Baikonur_Cosmodrome_Soyuz_launch_pad-scaled.jpg\")
<\/p>\n
Site No. 1\/5 at the Baikonur Cosmodrome, Kazakhstan. (Credit: NASA\/Bill Ingalls)<\/p>\n
As long as nothing further happens to make Site 31\/6 unusable, Russia will now be able to fly Progress cargo ships and Soyuz crewed spacecraft to ISS. Baikonur also has another pad that was used to fly missions to the ISS in the past, Site 1\/5. However, this launch pad is currently being retired.<\/p>\n
Site 1\/5, which hosted the Sputnik launch on Oct. 4, 1957, supported Yuri Gagarin\u2019s history-making launch into space on April 12, 1961. Soyuz MS-15 was the last mission to launch from Gagarin\u2019s Start on Sept. 25, 2019, and the Russian program emphasized developing Vostochny Cosmodrome in Russian territory rather than upgrading Gagarin\u2019s Start at Baikonur.<\/p>\n
In fact, Site 1\/5 is now not even controlled by Russia. It is now controlled by the host nation Kazakhstan, and is planned to be transformed into a museum. In addition, Vostochny Cosmodrome does not have the necessary facilities to handle Progress cargo ships, and there is a lack of suitable abort options for Soyuz crew launches from that site.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2021\/04\/Poster-2-First-assembly-stage-scaled-e1619807198914.jpeg\")
<\/p>\n
Phase 1 of the ROSS construction. (Credit: Katya Pavlushchenko)<\/p>\n
Site 31\/6 will likely be Russia\u2019s only launch pad capable of hosting ISS launches until the Station is decommissioned. The United States Congress recently included language in the NASA Authorization Act of 2026 to extend ISS operations until September 30, 2032, to keep the Station operational until commercial alternatives are available.<\/p>\n
If this extension is approved, the Russian program will likely continue to use the Station until its decommissioning, and the continued ability to fly Progress and Soyuz vehicles to ISS is critical to allowing the Russian human spaceflight program to stay operational.<\/p>\n
After the ISS is decommissioned, Russia had planned the Russian Orbital Service Station (ROSS) as a successor, but there are questions about its funding and status. In the meantime, the next Progress launch from Site 31\/6, Progress MS-34, is scheduled for April 25. The Soyuz MS-29 crewed launch is set for July 14.<\/p>\n
(Lead image: Progress MS-33 launches from Baikonur Cosmodrome on March 22, 2026. Credit: NASA)<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"Just under four months after Soyuz MS-28 launched from Site 31\/6 at Baikonur Cosmodrome in Kazakhstan, an eventful flight that resulted in severe damage to critical launch pad structure, the next Russian mission to the International Space Station is now underway. Progress MS-33, an uncrewed cargo ship loaded with over 2,500 kg of food, fuel, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[7831,1601,2514,717,233,513,7870,234,7840,1302,514],"class_list":["post-23561","post","type-post","status-publish","format-standard","hentry","category-news","tag-baikonur","tag-baikonur-cosmodrome","tag-gagarins-start","tag-international-space-station","tag-iss","tag-progress","tag-progress-ms-33","tag-roscosmos","tag-site-31-6","tag-soyuz","tag-soyuz-2-1a"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/23561"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=23561"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/23561\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=23561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=23561"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=23561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Prior to Progress MS-33\u2019s launch, Progress MS-31 undocked from the Poisk<\/em> module on Monday, March 16, and deorbited to a similar destructive reentry. This cleared the way for MS-33 to dock to the module. Progress MS-32 is docked to the Zvezda<\/em> module\u2019s aft port, while Soyuz MS-28 is docked to the Rassvet<\/em> module.<\/p>\n Progress MS-33\u2019s path to the pad and to flight was lengthy. The cargo ship was originally scheduled to fly in December 2025, but the flight was delayed for over three months due to an incident that took place during the Soyuz MS-28 launch on Nov. 27, 2025.<\/p>\n Image of the collapse maintenance cabin at Site 31\/6. (Credit: Kosmonavtiki Novosti)<\/p>\n Although MS-28\u2019s ascent and orbital insertion went as planned, events on the ground at Site 31\/6 told a different story. In addition to a number of platforms on the launch tower, which splits up and retracts before flight, there is a mobile maintenance cabin underneath the rocket that is retracted before launch as well.<\/p>\n That access platform, as a Roscosmos investigation found, was not properly secured, and the forces of launch caused the platform to fall into the flame trench. This fall caused severe damage and made the platform unusable. Without that platform, launches from Site 31\/6 could not proceed, and there were no other available launch pads that could host Soyuz launches to ISS.<\/p>\n The maintenance platform is necessary to allow workers access to the lower half of the Soyuz rocket, where they can install pyrotechnics and remove protective covers.<\/p>\n The Progress MS-33 spacecraft during prelaunch testing. (Credit: RKK Energia)<\/p>\n Roscosmos scrambled to fix the pad, as without it they would not be able to supply the Russian segment with fuel, water, or other consumables that the Zvezda<\/em> service module and the rest of the segment use, without assistance from partners.<\/p>\n An extended period of time without the pad would also have rendered the Russians unable to launch crews on their own spacecraft or to conduct orbital reboost burns from their segment.<\/p>\n After initial concern about the Russians\u2019 ability to produce a new platform, Roscosmos found a spare unit built during the 1970s. The unit needed modifications to service the current pad and rocket, but Roscosmos was able to finish the work in time for a spring launch of Progress MS-33.<\/p>\n Site No. 1\/5 at the Baikonur Cosmodrome, Kazakhstan. (Credit: NASA\/Bill Ingalls)<\/p>\n As long as nothing further happens to make Site 31\/6 unusable, Russia will now be able to fly Progress cargo ships and Soyuz crewed spacecraft to ISS. Baikonur also has another pad that was used to fly missions to the ISS in the past, Site 1\/5. However, this launch pad is currently being retired.<\/p>\n Site 1\/5, which hosted the Sputnik launch on Oct. 4, 1957, supported Yuri Gagarin\u2019s history-making launch into space on April 12, 1961. Soyuz MS-15 was the last mission to launch from Gagarin\u2019s Start on Sept. 25, 2019, and the Russian program emphasized developing Vostochny Cosmodrome in Russian territory rather than upgrading Gagarin\u2019s Start at Baikonur.<\/p>\n In fact, Site 1\/5 is now not even controlled by Russia. It is now controlled by the host nation Kazakhstan, and is planned to be transformed into a museum. In addition, Vostochny Cosmodrome does not have the necessary facilities to handle Progress cargo ships, and there is a lack of suitable abort options for Soyuz crew launches from that site.<\/p>\n Phase 1 of the ROSS construction. (Credit: Katya Pavlushchenko)<\/p>\n Site 31\/6 will likely be Russia\u2019s only launch pad capable of hosting ISS launches until the Station is decommissioned. The United States Congress recently included language in the NASA Authorization Act of 2026 to extend ISS operations until September 30, 2032, to keep the Station operational until commercial alternatives are available.<\/p>\n If this extension is approved, the Russian program will likely continue to use the Station until its decommissioning, and the continued ability to fly Progress and Soyuz vehicles to ISS is critical to allowing the Russian human spaceflight program to stay operational.<\/p>\n After the ISS is decommissioned, Russia had planned the Russian Orbital Service Station (ROSS) as a successor, but there are questions about its funding and status. In the meantime, the next Progress launch from Site 31\/6, Progress MS-34, is scheduled for April 25. The Soyuz MS-29 crewed launch is set for July 14.<\/p>\n (Lead image: Progress MS-33 launches from Baikonur Cosmodrome on March 22, 2026. Credit: NASA)<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Just under four months after Soyuz MS-28 launched from Site 31\/6 at Baikonur Cosmodrome in Kazakhstan, an eventful flight that resulted in severe damage to critical launch pad structure, the next Russian mission to the International Space Station is now underway. Progress MS-33, an uncrewed cargo ship loaded with over 2,500 kg of food, fuel, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[7831,1601,2514,717,233,513,7870,234,7840,1302,514],"class_list":["post-23561","post","type-post","status-publish","format-standard","hentry","category-news","tag-baikonur","tag-baikonur-cosmodrome","tag-gagarins-start","tag-international-space-station","tag-iss","tag-progress","tag-progress-ms-33","tag-roscosmos","tag-site-31-6","tag-soyuz","tag-soyuz-2-1a"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/23561"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=23561"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/23561\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=23561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=23561"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=23561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/p>\n<\/p>\n<\/p>\n<\/p>\n