CINXE.COM

<html> <head> <title>Progress M-27M</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="description" content="Mission of Progress M-27M cargo ship by Anatoly Zak"> <meta name="keywords" content="Mission of Progress M-27M (Progress 59) cargo ship by Anatoly Zak"> <link rel="stylesheet" type="text/css" href="CSS/theme.css"> <script type="text/javascript">  </script> </head> <body bgcolor="#FFFFFF" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" onLoad="MM_preloadImages('../menu_centers_over.gif','../menu_home_over.jpg','../menu_rockets_over.gif','../menu_spacecraft_over.gif','../menu_people_over.jpg','../menu_chronology_over.gif')" link="#FF0000" vlink="#000000"> <table width="100%" border="0" cellspacing="0" cellpadding="0" height="40" vspace="0" hspace="0" name="top banner" bordercolor="0" align="center"> <tr bgcolor="#999999" align="center" valign="top"> <td height="40"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/m27m_b.jpg" width="600" height="40" align="right" usemap="#Map2" border="0"> <map name="Map2"> <area shape="rect" coords="140,12,210,37" href="spacecraft_manned_2010s.html"> <area shape="rect" coords="57,15,132,36" href="spacecraft.html"> <area shape="rect" coords="215,12,285,36" href="iss.html"> <area shape="rect" coords="291,14,364,36" href="iss_chronology_flights.html"> <area shape="rect" coords="368,13,459,36" href="progress_m_0m.html"> </map></td> </tr> </table> <table width="100%" border="0" cellspacing="0" cellpadding="5" vspace="0" hspace="0" height="100%" bordercolor="0" align="center" name="main"> <tr> <td width="120" height="200%" rowspan="3" align="left" valign="top" bordercolor="#999999" bgcolor="#999999"> <p> <div align="center"> <script language="JavaScript">  </script> <script language="JavaScript">  </script> <table width="120" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td><a href="index.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('Image4','','images/menu_home_over.jpg',1)"><img name="Image4" border="0" src="images/menu_home_up.jpg" width="120" height="30"></a></td> </tr> <tr> <td> <div align="center"><a href="rockets.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('rockets','','images/menu_rockets_over.gif',1)"><img name="rockets" border="0" src="images/menu_rockets_up.gif" width="120" height="30"></a></div> </td> </tr> <tr> <td> <div align="center"><a href="spacecraft.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('spacecraft','','images/menu_spacecraft_over.gif',1)"><img name="spacecraft" border="0" src="images/menu_spacecraft_up.gif" width="120" height="30"></a></div> </td> </tr> <tr> <td><a href="centers.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('Image3','','images/menu_centers_over.gif',1)"><img name="Image3" border="0" src="images/menu_centers_up.gif" width="120" height="30"></a></td> </tr> <tr> <td><a href="people.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('people1','','images/menu_people_over.jpg',1)"><img name="people1" border="0" src="images/menu_people_up.jpg" width="120" height="30"></a></td> </tr> <tr> <td><a href="chronology.html" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('chrono','','images/menu_chronology_over.gif',1)"><img name="chrono" border="0" src="images/menu_chronology_up.gif" width="120" height="30"></a></td> </tr> </table> <a href="http://www.twitter.com/russianspaceweb"><img src="images/logos/twitter_logo.jpg" alt="Twitter" width="120" height="37" border="0"></a><a href="http://www.sen.com/news/russia-to-launch-station-resupply-mission"><img src="images/logos/facebook_logo.jpg" alt="Facebook" width="120" height="37" border="0"></a> </div> <p align="center" class="menuTextLinks"><font color="#FFFFFF"><a href="site_map.html">Site map</a></font></p> <p align="center" class="menuTextLinks"><font color="#FFFFFF"><a href="site_update.html">Site update log</a></font></p> <p align="center" class="menuTextLinks"><font color="#FFFFFF"><a href="site_info.html">About this site</a></font></p> <p align="center" class="menuTextLinks"><a href="zak.html">About the author</a></p> <p align="center" class="menuTextLinks"><a href="mailto:(Anatoly%20Zak)%20agzak@russianspaceweb.com">Mailbox</a></p> <hr> <p align="center" class="menuTextLinks"><b><a href="sponsor.html">SUPPORT THIS SITE!</a></b></p> <hr> <p align="center" class="menuTextLinks"><font color="#FFFFFF"><strong><a href="advertise.html">ADVERTISE</a></strong></font></p> <hr> <p align="center" class="menuTextLinks"><b>Searching for details:</b></p> <span class="menuTextLinks">The author of this page will appreciate comments, corrections and imagery related to the subject. Please contact <a href="mailto:(Anatoly Zak) agzak@russianspaceweb.com">Anatoly Zak</a>. </span> <hr align="center"> <p align="center" class="menuTextLinks">Related pages:</p> <div align="center"></div> <div align="center"><a href="progress.html" class="menuTextLinks">Progress cargo ship</a> </div> <hr> <p align="center"><font size="1" face="Verdana, Arial, Helvetica, sans-serif"></font></p> <p align="center"><font size="1" face="Verdana, Arial, Helvetica, sans-serif"><a href="persona.html"></a></font></p> <p align="center"> </p></td> <td height="50%" colspan="2" align="left" valign="top" bordercolor="#CCCCCC" bgcolor="#CCCCCC"> <p align="left" class="menuTextLinks"><a href="site_update.html">Site news</a> | <a href="site_map.html">Site map</a> | <a href="site_info.html">About this site</a> | </font><a href="zak.html">About the author</a> | <a href="testimonials.html">Testimonials</a> | <a href="mailto:(Anatoly%20Zak)%20agzak@russianspaceweb.com">Mailbox</a> | <strong><a href="advertise.html">ADVERTISE!</a></strong> | <b><a href="sponsor.html">DONATE!</a></b></p> </td> </tr> <tr> <td bordercolor="#CCCCCC" align="left" valign="top"><p class="mainHeadline">Progress M-27M fails to resupply ISS</p> <p class="quickDesc">The Progress M-27M spacecraft (production No. 426) was the second Russian cargo vehicle to fly to the International Space Station, ISS, in 2015 to re-supply crew onboard the outpost. It was also the 150th Progress spacecraft and the 59th Russian cargo flight to the ISS, known as P59. The mission ran into severe problems immediately after reaching orbit.</p> <p align="center"> <script type="text/javascript"></script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> </p> <p align="left" class="navLine">Previous mission: <a href="progress-m26m.html">Progress M-26M</a></p> <p align="center" class="navLine"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/insertion_1.jpg" alt="Insertion" width="730" height="555"></p> <p align="center" class="picCaption">Ground track and launch profile for Progress M-27M mission on April 28, 2015.</p> <table width="100%" border="0" cellpadding="0" cellspacing="3" bgcolor="#FF9900"> <tr> <td bgcolor="#FF9900"><div align="center"> <span class="bodyText"><strong>From the publisher:</strong> Pace of our development depends primarily on the level of support from our readers!</span> <form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top"> <div align="center"> <input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="TLH8PL3QPAD8J"> <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> <img alt="Donate" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"> </div> </form> </div></td> </tr> </table> <p class="bodyText"><span class="bodyText"><strong>Progress M-27M flight plan</strong></span></p> <p><span class="bodyText">According to the original plan, the docking of Progress M-27M at the outpost was scheduled on the day of the launch at 16:06:39 Moscow Time (9:06 a.m. EDT). According to the agency, the remote-control radio system, TORU, could be used to attempt to stop the rotation of the spacecraft, however chances of success were low due to unpredictable motion of the vehicle.</span></p> <p class="bodyText">Progress M-27M was to follow a six-hour rendezvous profile with the outpost, aiming to achieve <a href="docking.html">docking</a> at 16:06:39 Moscow Time (9:06 a.m. EST) on the day of the launch at the Earth-facing docking port on the <a href="iss_dc.html">Docking Compartment-1</a>, SO1, of the <a href="iss_russia.html">Russian segment</a>. At the moment of the rendezvous with the cargo ship, the space station was expected to be in a 398.01 by 411.02-kilometer orbit.</p> <p class="bodyText">To reach the outpost, Progress M-27M was scheduled to conduct four orbit-boosting engine firings, one during the mission's first revolution around the Earth and three more during the second orbit: </p> <table width="100%" border="0" cellspacing="0" cellpadding="3"> <tr> <td rowspan="2" bgcolor="#CCCCCC" class="tableHeader"><div align="left"><strong>Moscow time</strong></div></td> <td rowspan="2" bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Orbit</strong></div></td> <td rowspan="2" bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Delta V</strong></div></td> <td rowspan="2" bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Burn duration</strong></div></td> <td colspan="4" bgcolor="#999999" class="tableHeader"><div align="center"><strong>Resulting orbit after each maneuver</strong></div></td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Period</strong></div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Inclination</strong></div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Perigee</strong></div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center"><strong>Apogee</strong></div></td> </tr> <tr> <td bgcolor="#FAF6F6" class="tableText"><div align="left">10:52:18</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">1</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="right">26.47 m/s</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">66.6 seconds</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">89.44 minutes</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">51.65 degrees</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">219.3 kilometers</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">283.9 kilometers</div></td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText"><div align="left">11:29:06</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">2</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="right">21.45 m/s</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">53.8 seconds</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">90.18 minutes</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">51.67 degrees</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">281.5 kilometers</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">300.6 kilometers</div></td> </tr> <tr> <td bgcolor="#FAF6F6" class="tableText"><div align="left">12:13:13</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">2</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="right">7.00 m/s</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">18.4 seconds</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">90.43 minutes</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">51.67 degrees</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">292.8 kilometers</div></td> <td bgcolor="#FAF6F6" class="tableText"><div align="center">313.8 kilometers</div></td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText"><div align="left">12:43:18</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">2</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="right">7.00 m/s</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">18.4 seconds</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">90.67 minutes</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">51.64 degrees</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">307.4 kilometers</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">335.2 kilometers</div></td> </tr> </table> <p><span class="bodyText">The autonomous rendezvous process was scheduled to start at 14:01:07 Moscow Time (7:01 a.m. EDT, 11:01 GMT). The final maneuvering, including a flyaround of the station, a short period of station-keeping and, finally, berthing would be initiated at 15:46:13 Moscow Time (11:36 EDT, 12:46 GMT).</span></p> <p align="center"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/m27m_rendzevous_1.jpg" alt="Rendezvous" width="632" height="902"></p> <p align="left"><span class="bodyText">In preparation for launch, the Progress M-27M cargo ship was rolled out to Pad No. 6 at <a href="baikonur_r7_31.html">Site 31</a> in <a href="baikonur.html">Baikonur</a> on the morning of April 26, 2015. </span></p> <p class="subheadLine">Launch and ride to orbit</p> <p align="center" class="subheadLine"><iframe width="640" height="360" src="https://www.youtube.com/embed/BJhSabDSohI?feature=player_embedded" frameborder="0" allowfullscreen></iframe></p> <p align="center" class="subheadLine"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/ignition_1.jpg" alt="Ignition" width="730" height="504"></p> <p class="bodyText">The liftoff of a <a href="soyuz2_lv.html">Soyuz-2-1a</a> rocket took place as scheduled on April 28, 2015, at 10:09:50 Moscow Time (3:09 a.m. EDT, 07:09 GMT) from Pad No. 6 at <a href="baikonur_r7_31.html">Site 31</a> in Baikonur. The launch vehicle carried the 7,290-kilogram <a href="progress.html">Progress</a> M-27M spacecraft bound to the <a href="iss.html">International Space Station</a>, ISS. Following a <a href="baikonur_downrange.html">standard ascent</a>, the spacecraft separated from the <a href="soyuz_lv_stage3.html">third stage</a> of the launch vehicle eight minutes 45 seconds after the liftoff.</p> <p><span class="subheadLine"><a name="accident"></a>Post-launch problems</span></p> <p class="bodyText">According to NASA, following the separation from the launch vehicle, the Progress M-27M successfully deployed its power-generating solar arrays and a trio of communications antennas. However, the mission control in Korolev was not able to confirm a successful opening of a pair of the Kurs rendezvous antennas onboard the vehicle and the pressurization in one of two manifolds of the propulsion system. At the time, the telemetry from the spacecraft became sporadic. (The failure of the main computer onboard the spacecraft was also confirmed based on fragments of telemetry, a mission control source later said.) The radio system of orbital parameters also indicated that an apogee (highest point) of the Progress' orbit was 40 kilometers higher than normal. At the time, representatives of RKTs Progress, the Soyuz rocket manufacturer, told members of the State Commission overseeing the mission that the orbital insertion had gone as scheduled and the radio-control system had miscalculated orbital parameters.</p> <p class="bodyText">As a result, the mission was immediately switched to a longer, 34-orbit rendezvous profile with the ISS, which would give ground controllers extra time to troubleshoot the issue. If they could resolve all the problems, the docking of the cargo ship at the station would take place around 5:03 EDT on April 30, NASA said.</p> <p class="bodyText">After the second orbit, representatives of RKTs Progress admitted to the State Commission that they had not seen a signal confirming the separation between the <a href="soyuz_lv_stage3.html">third stage</a> and the spacecraft due to loss of telemetry. The higher-than-normal orbital parameters, which were announced 1.5 hour earlier, turned out to be real. </p> <p class="bodyText">Before the end of the day, engineers concluded that one propulsion system manifold onboard Progress responsible for the rendezvous maneuvers had lost pressure, making the trip to the station impossible. Ground control still hoped to activate the second manifold, normally used to deorbit the spacecraft, which appeared to be in order. Its thrusters could be used to stabilize the spacecraft and to perform a controlled deorbiting maneuver.</p> <p class="bodyText">However, during four passes within range of <a href="kik.html">Russian ground stations</a> on April 28, mission control was not able to confirm the status of onboard systems. A video downlinked from the spacecraft around 16:00 Moscow Time, during a third pass over Russia (but the 4th revolution of the mission) showed a very fast rotation of the vehicle:</p> <p align="center" class="bodyText"> <iframe width="640" height="360" src="https://www.youtube.com/embed/YMiNjHjpunU?feature=player_detailpage" frameborder="0" allowfullscreen></iframe></p> <p><span class="bodyText">Russian ground controllers estimated the rotation rate at one full circle every three seconds, which would explain the sporadic telemetry.</span></p> <p><span class="bodyText">According to NASA, at the very end of the communication window, Russian ground controllers sent commands to the Progress to stop its spin, but had no chance to see any effect from the action. The fourth and final communication session on April 28 also produced no visible results.</span></p> <p><span class="bodyText">Next opportunity for Russian flight controllers to communicate with the spacecraft would come on April 29, 2015, at 03:50 Moscow Time during a 15- or 16-minute window, TASS reported.</span></p> <p class="subheadLine"><a name="accident"></a>Initial accident information</p> <p><span class="bodyText">Initial fragmentary data available about the accident quickly led to questions about the performance of the launch vehicle. The telemetry from the <a href="soyuz_lv_stage3.html">third stage</a> of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> rocket apparently stopped coming 1.5 seconds after the GK-3 command, which cuts off the <a href="rd0110.html">RD-0110</a> engine onboard the rocket. The telemetry showed that the pressure in the combustion chamber of the engine started falling (as expected). However the spacecraft separation command, which was to come 3.3 seconds (plus/minus 0.3 seconds) after the GK-3 command, was never confirmed. The flow of data from a telemetry system located between oxidizer and fuel tanks on the <a href="soyuz_lv_stage3.html">third stage</a> and transmitted via four antennas along two communications channels stopped within a fraction of a second from each other at T+526 seconds in flight.</span></p> <p><span class="bodyText">The separation command was supposed to activate three dual pyrotechnic locks connecting the top edge of the third stage with the basis of the Progress. Three spring-loaded pushers would gently push the spacecraft away along 33 pins 0.13 seconds after the separation command. Four sensors would confirm the separation, which is known as separation contact or KO.</span></p> <p><span class="bodyText">According to Russian mission control sources, who applied several different methods to measure the actual orbital parameters after the launch, the spacecraft entered a 193.85 by 279.15-kilometer orbit, which was higher than expected, but far from being fatal for the mission.</span></p> <p class="bodyText">According to the mission control in Korolev, following the separation from the third stage at 10:18:38 Moscow Time, the Progress M-27M was expected to enter a 193 by 238-kilometer orbit, where it could remain for no less than 20 revolutions around the Earth or around 30 hours without any additional maneuvers, before naturally decaying into the Earth's atmosphere.</p> <p><span class="bodyText">However, NORAD data indicated much more severe deviation (120.5 by 316.4 kilometers) or 70 kilometers up and down, which many Russian observers believed to be erroneous. By the time the flow of telemetry from the Progress was interrupted few seconds before the separation of the spacecraft from the rocket, its orbit was around 38 or 39 kilometers off the mark at its apogee, even though the rocket should've been capable of delivering its cargo within five kilometers from a prescribed altitude.</span></p> <p class="bodyText">Despite some suspicions about the performance of the rocket, TV images downlinked from Progress at the time of the separation from the third stage appeared to show a stable flight. If correct, something else had to happen to send the spacecraft into a spin. It was also suggested that during the first TV transmission, the camera had actually been off, delivering just a black square.</p> <p class="bodyText">Still, at the end of the day, the <em>Interfax</em> news agency quoted an unnamed source as saying that a botched separation between the spacecraft and the <a href="soyuz_lv_stage3.html">third stage</a> of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> rocket had been a culprit.</p> <p class="bodyText">According to one hypothesis, the separation between the spacecraft and the rocket was somehow delayed, causing it to coincide or take place after the opening of the depressurization valve on the oxidizer tank of the <a href="soyuz_lv_stage3.html">third stage</a>, which is normally programmed to take place four seconds (plus/minus 0.3 seconds) after the GK-3 command.</p> <p class="bodyText">The pressurized gas escaping from the rocket causes its body to spin and could take the spacecraft with it if it was still connected to the stage at the time. Still, the separation would have to take place somehow and some thrust would have to be applied to both vehicles taking them as far as 40 kilometers in separate directions. A possible collision resulting in an explosion could also explain a presence of at least 44 fragments detected by NORAD near the spacecraft.</p> <p class="bodyText">Also, by the evening of April 28, NORAD updated orbital elements for the Progress M-27M mission, which finally came to a virtual agreement with the previously available parameters from Russian tracking means: a 188- by 260-kilometer orbit with an inclination 51.65 degrees toward the Equator.</p> <p align="left" class="bodyText"><span class="tableHeadline">Planned and actual orbital parameters for Progress M-27M mission:</span></p> <table width="100%" border="0" cellspacing="0" cellpadding="3"> <tr> <td bgcolor="#CCCCCC" class="tableHeader">-</td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center">Planned parking orbit</div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center">Actual orbit for Progress M-27M</div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center">Actual orbit for <a href="soyuz_lv_stage3.html">Stage III</a></div></td> </tr> <tr> <td class="tableText">Perigee</td> <td class="tableText"><div align="center"> 193 kilometers</div></td> <td class="tableText"><div align="center">193.85 kilometers</div></td> <td class="tableText"><div align="center"><span class="bodyText">~193</span> kilometers</div></td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText">Apogee</td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">238 kilometers</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">279.15 kilometers</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">~200 kilometers</div></td> </tr> </table> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/orbit_1-3_1.jpg" alt="Orbit" width="730" height="450"></p> <p align="center" class="bodyText"><em>First three revolutions of the ISS around the Earth on April 28, 2015.</em></p> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/indicator_1.jpg" alt="Indicator" width="729" height="671"></p> <p align="center" class="bodyText"><em>An interpretation of info screens transmitted by cameras onboard Progress M-27M right after reaching orbit (top) and during its 3rd orbit (bottom) provides clues about possible failure of the attitude control system and massive consumption of onboard propellant.</em></p> <p class="subheadLine"><a name="0429"></a>Events of April 29</p> <p class="bodyText">Another attempt to communicate with Progress M-27M was apparently made during the mission's 13th orbit, in the early hours Moscow Time, however it was also fruitless. The spacecraft likely continued tumbling in space. The new communication window opened around 05:00 Moscow Time (10 p.m. EDT on April 28), however again produced no results. A total of six attempts were made during the day, all failed.</p> <p class="bodyText">Specialists sent commands to the spacecraft to stop its rotation, but they failed even though the thrusters were activated, mission control sources said. The damage to propellant supply lines was suspected as a result and an attempt to switch to a backup propellant manifold did not work either. Plans to use manual remote-control system, TORU, to control the spacecraft were dropped as well. The Russian space officials then formally concluded that the controlling the spacecraft would not be possible, but monitoring of its orbit continued with the use of radio systems.</p> <p class="bodyText">According to a press-release issued by the Join Functional Component Command for Joint Space Operations Center at Vandenberg Air Force Base in California, it made first observation of the Progress M-27M at 3:04 a.m. EDT and established that the spacecraft had been making one full rotation every five seconds. </p> <p class="bodyText">According to NASA, during the day, the mission control in Korolev also asked the <a href="iss_soyuz_tma16m.html">current ISS crew</a> to try to photograph the stricken ship as it passes 170 kilometers below the station around 8:30 p.m. EDT. NASA also said that a previous night, Russian ground controllers had been able to establish communications with the vehicle and review telemetry. Russian controllers configured the refueling system to feed the thrusters <em>(editor's note: in the remaining manifold)</em> and made two unsuccessful attempts to command the thrusters to stabilize the vehicle’s angular rotation, NASA said.</p> <p class="bodyText">During the night from April 29 to April 30, Gennady Padalka photographed the Progress M-27M and sent images to mission control, however their resolution was far from enabling to discern any external damage to the spacecraft, <em>Interfax</em> reported.</p> <p class="subheadLine"><a name="reentry"></a>Reentry</p> <p align="center" class="subheadLine"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/crane_1.jpg" alt="Crane" width="730" height="485"></p> <p class="bodyText">On April 29, various estimates put the reentry of Progress M-27M into the Earth's atmosphere between May 3 and May 11, 2015. The Russian mission control predicted the plunge between May 5 and May 8. A preliminary estimate issued by US military predicted the reentry on May 9. In the meantime, the third stage, which delivered the Progress M-27M into orbit, reentered the atmosphere on April 29 without an accident and so did most of the debris associated with the launch.</p> <p class="bodyText">On May 4, US military predicted the reentry of Progress M-27M on May 8, 2015, at 13:13 GMT during the mission's 167th revolution around the Earth. If any debris of the spacecraft would survive the reentry, they would fall in the Pacific off the US West Coast.</p> <p class="bodyText">On May 5, US military issued another prognosis advancing the reentry time to the 166th orbit of the Progress M-27M mission on May 8, 2015, at 12:17 GMT. In the meantime, specialists at the Mission Control in Korolev still maintained communications with the crippled spacecraft using its radio signals for orbit tracking and the reentry time predictions.</p> <p class="bodyText">On May 6, Roskosmos issued a statement predicting the reentry of Progress M-27M on May 8, 2015, between 01:23 Moscow Time (6:23 p.m. EDT, 22:23 GMT on May 7) and 21:55 Moscow Time (2:55 p.m. EDT, 18:55 GMT). The agency promised a more accurate forecast 24 hours before the event and a possible impact area for its debris. Only small fragments of the structure can reach the Earth's surface, Roskosmos said. Around the same time, US military issued a prognosis for a decay on May 8 at 08:59 GMT (4:59 a.m. EDT) during the 164th orbit of the Progress M-27M mission. As of May 6, Progress M-27M was orbiting the Earth in a 166 by 193-kilometer orbit.</p> <p class="bodyText">By May 7, US military moved forward the reentry prediction for the Progress M-27M mission by four revolutions, now forecasting the event on May 8, at 03:32 GMT, during mission's 160th orbit. A powerful magnetic storm on the Sun accelerated the decay of the stricken ship's orbit. In the afternoon, Roskosmos predicted reentry between 00:45 and 06:36 Moscow Time on the same day (5:45 p.m. - 11:36 p.m. EDT on May 7). The agency promised another forecast after 17:00 Moscow Time on May 7. However it was issued at the end of the business hours in Moscow and narrowed the reentry window from 01:13 to 04:51 Moscow Time on May 8 (6:13 p.m. to 9:51 p.m. EDT on May 7).</p> <p class="bodyText">Another forecast from the US military came in the middle of the day, predicting the reentry on May 8, 2015, at 01:36 GMT (9:36 p.m. EDT on May 7). Around that time, the spacecraft descended to a 141 by 155-kilometer orbit. The forecast was updated one more time in the evening, this time pushing back the reentry by 11 minutes to 01:47 GMT (9:47 p.m. EDT). Another update came during the final two orbits of the spacecraft and put the decay at 01:52 GMT (9:51 p.m. EDT).</p> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/groundtrack_1.jpg" alt="ground track" width="728" height="370"></p> <p align="center" class="bodyText"><em>Ground track of the Progress M-27M mission on May 7, 2015.</em></p> <p class="bodyText">On May 8, 2015, at 05:19 Moscow Time, Roskosmos issued a statement announcing the reentry of the Progress M-27M during its 160th orbit at 05:04 Moscow Time over the central part of the Pacific Ocean. However, it was unclear how the agency was able to confirm that fact given the lack of tracking capabilities over this region.</p> <p class="bodyText">At 04:20, the US military issued a confirmation of the reentry, but placed it further down the orbital path of the spacecraft over the Pacific Ocean, west of the Southern tip of South America at the point -51 degrees latitude and 273 degrees longitude. According to that information, the reentry took place at 02:20 GMT. The US could actually detect the heat signature of the event with the help of infrared sensors onboard of its early warning satellites.</p> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/reentry_map_1.jpg" alt="Reentry" width="726" height="369"></p> <p align="center" class="bodyText"><em>The final orbit and reentry locations for Progress M-27M on May 8, 2015, according to Roskosmos (left) and the US military (right).</em></p> <p class="bodyText"><strong><a name="investigation"></a>Failure investigation</strong></p> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/stage3_1.jpg" alt="Stage 3" width="730" height="485"></p> <p align="center" class="picCaption">Progress M-27M spacecraft under a payload fairing integrated with the third stage of the Soyuz-2-1a launch vehicle.</p> <p class="bodyText">From the beginning, the investigation into the Progress M-27M failure focused solely on three final seconds in the operation of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> launch vehicle and the separation of the spacecraft. It looked like a delayed command to cutoff the engine of the rocket's <a href="soyuz_lv_stage3.html">third stage</a> held the key to the mystery. The following timeline of those critical moments had emerged by May 1:</p> <table width="100%" border="0" cellspacing="0" cellpadding="3"> <tr> <td bgcolor="#CCCCCC" class="tableHeader">Milestone</td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center">Actual</div></td> <td bgcolor="#CCCCCC" class="tableHeader"><div align="center">Nominal (planned)</div></td> <td bgcolor="#CCCCCC" class="tableHeader">Note</td> </tr> <tr> <td class="tableText">Spacecraft separation readiness command</td> <td class="tableText"><div align="center">526.26 seconds</div></td> <td class="tableText"><div align="center">?</div></td> <td class="tableText">-</td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText">Stage III engine cutoff command, GK-3</td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">526.32 seconds</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">524.97 seconds</div></td> <td bgcolor="#CCCCCC" class="tableText">1.35 seconds late</td> </tr> <tr> <td class="tableText">Stage III engine cutoff begins (thrust reduction)</td> <td class="tableText"><div align="center">526.51 seconds</div></td> <td class="tableText"><div align="center">?</div></td> <td class="tableText">-</td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText">Loss of telemetry from channel 1 (MAS1) on <a href="soyuz_lv_stage3.html">third stage</a></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">526.67 seconds</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">N/A</div></td> <td bgcolor="#CCCCCC" class="tableText">-</td> </tr> <tr> <td class="tableText">Loss of telemetry from channel 2* (MAS3) on <a href="soyuz_lv_stage3.html">third stage</a></td> <td class="tableText"><div align="center">526.73 seconds</div></td> <td class="tableText"><div align="center">N/A</div></td> <td class="tableText">-</td> </tr> <tr> <td bgcolor="#CCCCCC" class="tableText">Spacecraft separation command, KO</td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">529.62 seconds**</div></td> <td bgcolor="#CCCCCC" class="tableText"><div align="center">528.27 seconds***</div></td> <td bgcolor="#CCCCCC" class="tableText">-</td> </tr> </table> <p class="footerCredit"><span class="tableText">*</span>Telemetry from channel 2 is normally transmitted with some delay; **Estimated but not confirmed time; ***+/- 0.3 seconds, actual separation, known as KO, takes place 0.13 seconds after the spacecraft separation command; </p> <p class="footerCredit"><em>Source: </em>Novosti Kosmonavtiki</p> <p class="bodyText"><strong>Spacecraft data analysis</strong></p> <p class="bodyText">According to sources at RKTs Progress, the telemetry from the spacecraft stopped coming slightly earlier than the telemetry from the rocket. However the spacecraft retained some limited function, while multiple debris large enough to detect them from the ground were accompanying the mission and signs of problems were found in the telemetry from the rocket.</p> <p class="bodyText">As a result, in the first weeks after the accident, publicly available sources tended to explain the accident by an explosion onboard the rocket stage, which damaged the spacecraft, while some considerable force still propelled both vehicles to different orbits. The spacecraft apparently never fired its engines and all its propellant had remained intact after the accident, according to available telemetry. In addition, it takes 30 seconds for the propulsion system onboard the Progress to be pressurized -- clearly not enough to make it operational at the time of the accident. Moreover, an apparent failure of the main computer onboard Progress M-27M probably blocked all its dynamic operations.</p> <p class="bodyText">Investigators also concluded that following the pressurization sequence onboard Progress, the propellant under pressure of around 12 atmospheres was venting from lines punctured by a nearby explosion of the <a href="soyuz_lv_stage3.html">third stage</a>, causing the tumbling of the spacecraft, a source at the mission control in Korolev said.</p> <p class="bodyText"><strong>Rocket data analysis</strong></p> <p class="bodyText">Despite all the suspicions about the rocket, its engineers insisted that there was little evidence of the explosion in the available telemetry. For example, data showed normal shutdown of the <a href="rd0110.html">RD-0110</a> engine, including the slowdown of the engine's turbopump, the fall of pressure in the combustion chamber and in the gas generator.</p> <p class="bodyText">At the conclusion of the engine cutoff sequence, special sensors also signaled that the pressure in the engine's four combustion chambers fell to a level of full inactivity. The pyrotechnics then closed shut a pair of valves on a gas generator of the engine, four more valves were closed on oxidizer lines leading to each of four combustion chambers and one valve cut off the main fuel line.</p> <p class="bodyText">However, from 0.2 to 0.4 seconds after the engine cutoff command, multiple sensors on the stage suddenly showed out-of-limit parameters, as if they were physically cut or thorn. For example, the turbopump rotation rate in the engine was going down smoothly as planned until it suddenly spiked to impossible 250 thousand rotations per minute and stayed there, according to the telemetry. The same way, the combustion chamber pressure sensors showed the fall to 3 kilograms per square centimeter, followed by a sudden surge to out-of-range parameters.</p> <p class="bodyText">The flow of data from the RTSTs telemetry system located between oxidizer and fuel tanks on the <a href="soyuz_lv_stage3.html">third stage</a> and transmitted via four antennas along two communications channels stopped within a fraction of a second from each other at T+526 seconds in flight. However some fragmentary data still continued coming from two out of three data sources.</p> <p class="bodyText">Most importantly, the telemetry showed that temperature inside the oxidizer tank of the rocket remained constant at 80 degrees Celsius until T+550 seconds, indicating that its propellant drainage valve remained closed and the vessel was intact long after the separation of the Progress. No other indications of destructive events were available either, sources said.</p> <p class="bodyText">Finally, the RTSTs radio-telemetry system onboard the third stage was switched off by the flight control system as scheduled at T+554 seconds into the mission, or 24 seconds after the separation between the spacecraft and the rocket.</p> <p class="bodyText"><strong><a name="official" id="official"></a></strong><span class="subheadLine">Official conclusions</span></p> <p class="bodyText">On May 12, 2015, the State Commission led by Deputy Head of Roskosmos Aleksandr Ivanov presented its preliminary conclusions on the Progress M-27M accident. According to the agency press-release published on the same day, the launch of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> rocket with Progress M-27M went as scheduled until the moment of separation between the spacecraft and the <a href="soyuz_lv_stage3.html">third stage</a> of the rocket. The abnormal separation took place at T+526.716 seconds in flight, sending the spacecraft to an orbit with an apogee 40 kilometers higher than normal and the third stage entering orbit with an apogee 20 kilometers below normal, the agency said.</p> <p class="bodyText">After reviewing all the materials, members of the State Commission came to a preliminary conclusion that a version of the abnormal separation had been objectively confirmed, which includes two subsequent events related to the depressurization (disintegration after the cutoff of the third-stage engine) first of the oxidizer tank and then of the fuel tank, Roskosmos said.</p> <p class="bodyText">The agency said that the work of the Commission had been ongoing and that the final classification of the character of the cause leading to the launch failure would require in-depth calculations and theoretical studies, an additional simulation and a number of experimental works, which will be conducted.</p> <p class="bodyText">Beginning on May 13, members of the Commission were to begin work at the sites of the companies-producers of rocket technology for determining and correcting possible causes of the accident, Roskosmos said. According to industry sources, in addition to visits to main contractors on the rocket and the spacecraft, TsNIIMash engineers went to Saratov in order to test nickel-cadmium batteries on the rocket. The team would try similate a situation with the shortsurcuit and the explosion of the battery.</p> <p class="bodyText">The press-release also announced a new schedule of ISS missions, which was developed in cooperation with the project partners (in the wake of the accident):</p> <ul> <li class="bodyText">Beginning of June 2015: Return to Earth of the <a href="iss_soyuz_tma15m.html">ISS crew</a>;</li> <li class="bodyText">Beginning of July 2015: Launch of another <a href="progress_m_0m.html">cargo ship</a> to the <a href="iss.html">ISS</a>;</li> <li class="bodyText">End of July 2015: Launch of another <a href="soyuz.html">piloted spacecraft</a> to the <a href="iss.html">ISS</a>;</li> </ul> <p class="bodyText">The final conclusions of the State Commission are expected on May 22, 2015, Roskosmos said. However new developments suddenly intervened.</p> <p class="bodyText"><strong><a name="turn"></a></strong><span class="subheadLine">Progress failure investigation might take a dramatic turn, alternative scenarios studied</span></p> <p align="center" class="bodyText"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/po_1.jpg" alt="PO" width="730" height="485"></p> <p class="bodyText">According to industry sources, on May 21, Aleksandr Danilyuk, Deputy Head of TsNIIMash research institute, which led the investigation, was preparing to sign off on a <a href="#official">conclusion</a> confirming the disintegration of the oxygen tank on the <a href="soyuz_lv_stage3.html">third stage</a> of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> rocket due to a manufacturing defect. At the time, the prevailing theory was that the welded seam connecting the upper bulkhead to the rest of the tank had given way, because it had to be welded twice during its production. The dual welding was the only one of 50 documented instances of deviations from the standard manufacturing process for the rocket and the spacecraft that the commission thought could have led to the accident.</p> <p class="bodyText">A source familiar with the investigation reported on the online forum of the <em>Novosti Kosmonavtiki</em> magazine that the disintegration of the oxygen tank had been accepted as the primary cause of the failure primarily because the tank was deemed to be the only source of thrust, which could send the spacecraft 40 kilometers above its projected altitude according to TsNIIMash calculations, which were reportedly doubted by at least some engineers.</p> <p class="bodyText">However at what was expected to be a final meeting of the investigative team, the head of TsSKB Progress, Aleksandr Kirilin and his deputy Ravil Akhmetov presented results of a detailed study dating back to the 1960s and proving that even after five welding cycles, the properties of the seam would not deteriorate. </p> <p class="bodyText">At the same time, TsSKB Progress officials put forward a new theory how the Progress spacecraft could contribute to the failure, as a result of a separation from the rocket at a wrong time. According to TsSKB Progress, the spacecraft could initiate the separation process based on its own software algorithms and signals from four separation sensors, which apparently do not take into the account the status of the launch vehicle. (During a nominal flight, the separation is conducted jointly by the rocket's computers which command to cut the pyrotechnic bolts holding two vehicles together and by the spacecraft's computer, which commands to cut fasteners on its side of the interface.). At the same time, the TsSKB analysis of data from the rocket's flight control system also indicated that it had never issued a command for the separation of the spacecraft.</p> <p class="bodyText">TsSKB conducted a ground separation test involving an experimental <a href="soyuz_lv_stage3.html">third stage</a> and the transfer section from the <a href="progress.html">Progress</a>. First engineers exploded pyro-bolts on the rocket side and then blew up fasteners on the spacecraft side. The attitude control sensor, located in the intertank section of the rocket stage, reportedly showed equal loads from both events.</p> <p class="bodyText">Based on all the data, TsSKB Progress apparently presented its own chronology of events based on the analysis of available telemetry, which claimed that the orbit confirmation command, PO, and the spacecraft separation command, KO, were issued within 0.12 seconds from each other at T+526 seconds in flight, while they had to have an interval from one to 15 seconds, according to the launch profile agreed between TsSKB Progress and RKK Energia. According to TsSKB Progress, events then developed according the following timeline: </p> <ul> <li class="bodyText"><strong>T+526.32 seconds: </strong> Orbit confirmation command, PO;</li> <li class="bodyText"><strong>T+526.44 seconds:</strong> Engine cutoff command, GK3;</li> <li class="bodyText"><strong>T+526.56 - 526.58 seconds:</strong> The telemetry from the spacecraft is interrupted;</li> <li class="bodyText"><strong>T+526.56 - 526.62 seconds:</strong> Most telemetry from the rocket also stops; </li> <li class="bodyText"><strong>T+526.62 - 526.65 seconds:</strong> Some acceleration typical for the firing of pyrotechnics is detected;</li> <li class="bodyText"> <strong>T+526.66 seconds:</strong> The stage gets a "kick" against the direction of the flight;</li> <li class="bodyText"><strong>T+526.68 seconds:</strong> Separation sensors on the side of the rocket are activated;</li> <li class="bodyText"><strong>T+526.69 seconds:</strong> Sharp fall in pressure in the oxidizer tank of the rocket;</li> <li class="bodyText"><strong>T+526.75 seconds:</strong> Fall in pressure in the fuel tank of the rocket.</li> </ul> <p class="bodyText">Not surprisingly, RKK Energia staunchly opposed this version of events and insisted that nothing wrong could happen to the spacecraft, despite little data to prove it one way or another. Still, TsNIIMash put off making the conclusion in the investigation until at least May 26, while launching urgent re-evaluation of all available data.</p> <p class="bodyText">On May 25, 2015, TsNIIMash conducted a failure test on the oxidizer tank which underwent two rounds of welding. However it cracked along the line near the fueling valve only after the internal pressure had reached 10.2 atmospheres, which is far above the normal pressure of 4.5-4.6 atmospheres during the flight. The fuel tank has even lower pressure of 2.2 atmospheres.</p> <p class="subheadLine"><a name="conclusion"></a>Roskosmos declares Progress investigation over</p> <p class="bodyText">On June 1, 2015, Roskosmos published a press-release entitled "Cause of the Failure Determined." It went as following:</p> <p class="bodyText">...After a thorough analysis of the failed launch and the completion of full-scale experiments, members of the commission came to the following conclusion: </p> <p class="bodyText">The damage to the ship during its abnormal separation from the third stage of the <a href="soyuz2_lv.html">Soyuz-2-1a</a> launch vehicle resulted from a particular property of the joint use of the cargo spacecraft and the launch vehicle. This design property was related to frequency and dynamic characteristics of joint vehicles. </p> <p class="bodyText">This design property was not fully accounted for during the development of the rocket and spacecraft complex. </p> <p class="bodyText">Limitations on further flights of the Soyuz-2-1a rocket with other spacecraft had not been found.</p> <p class="bodyText">Currently, Roskosmos is developing an action plan for conducting further flight tests of this space complex. </p> <p class="bodyText">On June 9, 2015, Roskosmos will finalize the new flight manifest for human missions in 2015, including launches of cargo ships.</p> <p class="bodyText"> </p> <p class="bodyText"> </p> <p class="bodyText"> </p> <p align="center" class="tableHeadline"><em><strong>Read much more about the history of the Russian space program in a richly illustrated, large-format glossy edition:</strong></em></p> <p align="center"><a href="book_future.html"><img src="images/zak/portfolio/Books/cover_front_455px.jpg" alt="Book" width="354" height="460" border="0"></a></p> <p> </p> <p class="tableHeadline"> </p> <p align="center"> <script type="text/javascript"></script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> </p> <p><a class="addthis_button" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4a9567347f52c441"><img src="http://s7.addthis.com/static/btn/v2/lg-share-en.gif" width="125" height="16" alt="Bookmark and Share" style="border:0"/></a></p> <hr> <p align="center" class="footerCredit">The page is maintained by Anatoly Zak</p> <p align="center" class="footerCredit">Last update: June 5, 2018 </p> <p align="center" class="footerCredit">All rights reserved</p></td> <td width="200" rowspan="2" align="left" valign="top" bordercolor="#CCCCCC" bgcolor="#CCCCCC" ><p align="center"><a href="book_future.html"><img src="images/zak/book_future_200x486.jpg" alt="Book" width="200" height="486" border="0"></a></p> <p align="center"><font face="Verdana, Arial, Helvetica, sans-serif" size="2"><b><font color="#FF0000">IMAGE ARCHIVE</font></b></font></p> <p align="center"><strong><font color="#FF0000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/top_2.jpg" alt="top" width="200" height="242" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/top_1.jpg','progress','scrollbars=yes,resizable=yes,width=730,height=495')"></a></font></strong></p> <p align="left"><span class="picCaption">Click to enlarge. Credit: RKK Energia</span></p> <p align="center"><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/processing_v_2.jpg" alt="processing" width="200" height="300" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/processing_v_1.jpg','ship','scrollbars=yes,resizable=yes,width=800,height=1210')"></a></p> <p align="left"><span class="picCaption">Click to enlarge. Credit: RKK Energia</span></p> <p align="center"><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/processing_h_2.jpg" alt="processing" width="200" height="256" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/processing_h_1.jpg','ship','scrollbars=yes,resizable=yes,width=800,height=542')"></a></p> <p align="left" class="picCaption">Click to enlarge. Credit: RKK Energia</p> <hr> <p><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/kgch_2.jpg" alt="KGch" width="200" height="186" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/kgch_1.jpg','kgch','scrollbars=yes,resizable=yes,width=800,height=542')"></a></p> <p><span class="picCaption">Click to enlarge. Credit: RKK Energia</span></p> <p><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/lv_sp_interface_2.jpg" alt="sp" width="200" height="199" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/lv_sp_interface_1.jpg','ship','scrollbars=yes,resizable=yes,width=800,height=544')"></a></p> <p align="left" class="picCaption">Pre-launch processing of Progress M-27M spacecraft. Click to enlarge. Credit: RKK Energia</p> <hr> <p align="center"><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/rollout_2.jpg" alt="rollout" width="200" height="261" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/rollout_1.jpg','rollout','scrollbars=yes,resizable=yes,width=800,height=542')"></a></p> <p align="left" class="picCaption">A Soyuz-2-1a rocket with Progress M-27M spacecraft rolls out to Pad 6 at Site 31 in Baikonur. Click to enlarge. Credit: RKK Energia</p> <hr> <p><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/pad_kgch_2.jpg" alt="Pad" width="200" height="259" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/pad_kgch_1.jpg','kgch','scrollbars=yes,resizable=yes,width=772,height=532')"></a></p> <p><span class="picCaption">Click to enlarge. Credit: RKK Energia</span></p> <p align="center"><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/pad_gantry_2.jpg" alt="Gantry" width="200" height="276" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/pad_gantry_1.jpg','pad','scrollbars=yes,resizable=yes,width=760,height=518')"></a></p> <p align="left" class="picCaption">A Soyuz-2-1a rocket with Progress M-27M spacecraft shortly after delivery to Pad 6 at Site 31 in Baikonur. Click to enlarge. Credit: RKK Energia</p> <hr> <p><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/trail_2.jpg" alt="trail" width="200" height="316"></p> <p><a href="javascript:;"><img src="images/spacecraft/manned/space_stations/iss/progress_mm/27/flight_2.jpg" alt="Flight" width="200" height="311" border="0" onClick="MM_openBrWindow('images/spacecraft/manned/space_stations/iss/progress_mm/27/flight_1.jpg','soyuz','scrollbars=yes,resizable=yes,width=800,height=542')"></a></p> <p><span class="picCaption">Progress M-27M lifts off on April 28, 2015. Click to enlarge. Credit: RKK Energia</span></p> <hr> <p> </p> <p> </p> </td> </tr> <tr> <td align="left" valign="top" bordercolor="#CCCCCC" bgcolor="#CCCCCC"><div align="center" class="menuTextLinks"><a href="site_update.html">Site news</a> | <a href="site_map.html">Site map</a> | <a href="site_info.html">About this site</a> | </font><a href="zak.html">About the author</a> | <a href="testimonials.html">Testimonials</a> | <a href="mailto:(Anatoly%20Zak)%20agzak@russianspaceweb.com">Mailbox</a> | <strong><a href="advertise.html">ADVERTISE!</a></strong> | <b><a href="sponsor.html">DONATE!</a></b></div></td> </tr> </table> <table width="100%" border="0" cellspacing="0" cellpadding="0" height="40" vspace="0" hspace="0" align="center" bordercolor="0"> <tr bgcolor="#999999"> <td><img src="images/footer3.gif" width="600" height="40" align="right" vspace="0" hspace="0" usemap="#Map" border="0"> <map name="Map"> <area shape="rect" coords="493,4,595,38" href="index.html"><area shape="rect" coords="59,3,105,37" href="#top" target="_self"> </map></td> </tr> </table> <map name="Map3"> <area shape="rect" coords="2,169,89,310" href="soyuz_lv_stage1.html"> <area shape="rect" coords="15,4,379,70" href="soyuz_lv_stage2.html"> <area shape="rect" coords="417,3,562,88" href="soyuz_lv_stage3.html"> <area shape="rect" coords="620,102,725,143" href="baikonur_downrange.html"> <area shape="rect" coords="91,422,579,542" href="baikonur_downrange.html"> <area shape="rect" coords="224,250,369,291" href="baikonur_downrange.html"> <area shape="rect" coords="162,276,223,306" href="baikonur.html"> </map></body> </html>