Jump to content

Ariane flight VA241

From Wikipedia, the free encyclopedia

Ariane flight VA241
The Ariane 5 launch vehicle, and the SES-14 and Al Yah 3 satellites, depicted in front of the Earth
Artwork featured on visitors' brochures
Ariane 5 ECA launch
Launch25 January 2018 (2018-01-25), 22:20:00 UTC
OperatorArianespace
PadKourou ELA-3
Payload
OutcomePartial failure
Components
Serial no.5101
Ariane launches
← VA240
VA242 →

Ariane flight VA241 was an Ariane 5 space launch that occurred from the Guiana Space Centre on 25 January 2018 at 22:20 UTC.

Payload

[edit]

The launcher was carrying the SES-14 and Al Yah 3 geostationary satellites, with a total payload mass of approximately 9,123 kg (20,113 lb). The satellites were accommodated together on the SYLDA adapter inside the long version of the upper stage fairing.[1]

SES-14

[edit]

SES-14, built by Airbus Defence and Space in Toulouse, France for SES of Luxembourg, was in the upper position. It had a mass at liftoff of 4,423 kg (9,751 lb), hosting the NASA-funded GOLD payload.[1] SES-14 was the second satellite based on Airbus's Eurostar E3000 EOR satellite bus to be launched by Arianespace.

Al Yah 3

[edit]

Al Yah 3, built by Orbital ATK in the United States for Yahsat of the United Arab Emirates, was in the lower position. It had a mass at liftoff of 3,795 kg (8,367 lb).[1] Al Yah 3 was the first satellite based on Orbital ATK's GEOStar-3 satellite bus to be launched by Arianespace.

Mission description

[edit]

Launch date

[edit]

The 97th Ariane 5 launch (1st of 2018) was planned to take place within a launch window of 45 minutes starting on 25 January 2018 at 22:20 UTC (19:20 local time). The launcher engines effectively were ignited at the very beginning of that window, from Ariane Launch Complex No. 3 (ELA-3) in Kourou, French Guiana.[2]

Orbit

[edit]

The mission was planned to last 35 minutes and 7 seconds, placing both satellites into a super-synchronous transfer orbit, with an apogee of about 45,000 km (28,000 mi) and a perigee of about 250 km (160 mi), at an inclination of about 3°.[1]

Countdown and flight sequence

[edit]

The planned sequence was as follows:[1]

Anomaly

[edit]
The Ariane 5 ECA on the launch pad prior to launch.
Ascent of the Ariane 5 ECA during the flight.

The telemetry of the launcher was lost from about 9 minutes to 9 minutes and 30 seconds (the uncertainty being due to the fact that the data as displayed in real-time may have been extrapolated for a finite amount of time) into the flight, close to the moment when the main stage (EPC) separation and upper stage (ESC-A) ignition should have occurred.[1]

Then about 1 hour after liftoff, Arianespace's CEO and chairman Stéphane Israël made a quick speech saying that the launcher suffered an anomaly. His statement in front of the VIP audience in the Jupiter control room was:

"Ladies and gentlemen, so I come to give you some information because we have had an anomaly on this launch. Indeed, we lost contact with the launcher a few seconds after the ignition of the upper stage. At that time, we can consider that the upper composite and the satellite[s] have been satellised [sic: bad translation of French satellisés, meaning put in orbit]. But as I said, we lost contact. So up to now, our customers do not have contact with the satellite[s]. We need now some time to know if they have been separated [sic], and where they are exactly, to better analyse the consequences of this anomaly. I want to present my deepest excuses to our customers, who have entrusted us one more time. We know that there is no launch with no risk. We know that launch is always difficult, and tonight Ariane 5 has had an anomaly, so let's take time now to better understand the situation of the satellite[s]. Arianespace, in full transparency, will come back to you to provide you with some more information as soon as we have them. I apologise on behalf of Arianespace".[3]

Later in the night, Arianespace issued a first press release [2] mentioning that the Natal tracking station did not acquire telemetry of the launcher, which lasted until the end of the mission, and that the separation of both payloads was confirmed, together with their successful injection into Earth orbit and the link acquisition by both customers.

On the same day, Arianespace issued a second press release[4] stating that SES and YahSat confirmed the acquisition and good health of the two satellites despite a deviation of their trajectory. It was also stated that the telemetry was lost by the tracking stations 9 minutes and 26 seconds after reference time T, due to a deviation of the trajectory.

On 26 January 2018, SES informed on their website that while its satellite is in good health it would require to "set up a new orbit raising plan", and that it would thus "reach the geostationary orbit only four weeks later than originally planned",[5] indicating that the satellites were not delivered to the intended super-synchronous transfer orbit (with an apogee of 45,000 km and inclination of 3°[1]) by the launch vehicle. This was confirmed later that day when the orbital elements of the satellites were released, revealing that the deployment orbit's apogee had a minor deviation of about 2,000 km while the inclination suffered a significant deviation of almost 18° from intended.[6]

The flight path anomaly became obvious when initial analysis showed that the launch azimuth had gone wrong since the very beginning of the flight, during the first stage firing,[6] with unexpected slow roll manoeuvre just after liftoff.[7] In standard Ariane 5 launch, the roll maneuvre should only begin around 17 seconds after reference time T or 10 seconds after liftoff.[8]

The anomaly might have been due to a human error during the programming of the Guidance, Navigation and Control (GNC) combined with a failed verification procedure according to early developments as the launch team reported not to have double-checked the guidance computer parameters to reduce workload duplication, even though double-checking them played the vital role in the rocket's reliability.[9][10] But Arianespace and ArianeGroup issued a statement insisting that all the control processes remain unchanged,[11] while they restructured the organization now directly from ArianeGroup, affecting the launch team now with many of ArianeGroup engineers.[12]

Frédérique Vidal, Minister of Higher Education, Research and Innovation, said that the rocket did not overfly Kourou, but for the first time flew very close to the city of Kourou.[13] In standard launch of any rocket it should have been immediately destroyed by either Range Safety Officer or its onboard Autonomous Flight Termination System once the rocket flew off course. But at the point when the Range Safety Officer for this mission wanted to destroy the rocket, it was too late as it already overflew close to the city of Kourou, so destroying the rocket would have been potentially more dangerous with the debris raining down over Kourou than continuing flight.[14]

Aftermath

[edit]

An independent investigation board was established in collaboration with the European Space Agency (ESA) and National Aeronautics and Space Administration (NASA),[15] under the chairmanship of ESA's inspector general to investigate what caused the trajectory deviation during flight. The conclusions of the investigation commission led by ESA's inspector general, Toni Tolker-Nielsen, were released on 22 February 2018, indicating that engineers left the inertial navigation units' azimuth value at 90° (the standard for geostationary transfer orbit (GTO) launch on Ariane 5), however unusually 70° was intended for these payloads riding into unusual supersynchronous transfer orbit (GTO), explaining the cause of the 17° trajectory deviation.[16][17][18] Standard verification procedure missed the azimuth data.[18] The reason of launching both satellites to SSGTO was Al Yah 3 satellite manufacturer (Orbital-ATK) abruptly requested Arianespace to change the target orbit profile to SSGTO in order to release the Al Yah 3 satellite at a right angle relative to the direction of motion of the launch vehicle.[19][20]

Both satellites have now conducted orbital make-up procedure by changing their maneuvering plan, which would extend commissioning time.[21]

SES-14 needed about 4 weeks longer than planned commissioning time, meaning that entry into service now expected in August instead of July.[22] Nevertheless, SES-14 is still expected to be able to meet the designed life time,[23] since it was originally to be launched on the Falcon 9 launch vehicle which would have required more propellant reserves as Falcon 9 usually deploys geostationary satellites into a high inclination orbit that requires more propellant to approach into final geostationary orbit.[24] SES informed NASA that they expect no effect on the quality of observations and data of the agency's Global-scale Observations of the Limb and Disk (GOLD) instrument after the launch anomaly.[25]

Al Yah 3 was also confirmed healthy after more than 12 hours without further statement, and like SES-14, Al Yah 3's maneuvering plan was also revised to still fulfill the original mission.[26] As of 30 May 2018, Al Yah 3 had arrived to the intended geostationary orbit, after series of recovery maneuvers had been performed and completed its in-orbit testing.[27] Al Yah 3 is expected to enter into service around July 2018, at the start of new Eutelsat's fiscal year.[28] Due to excess propellant usage during recovery, Al Yah 3's operational life was reduced to approximately 9 years.[29] Yahsat was expected to receive up to 50% of its insured value (~US$108 million) in damages.[30][31]

This mission anomaly ended the 82 consecutive launch success streak from 2003.[32]

References

[edit]
  1. ^ a b c d e f g http://www.arianespace.com/wp-content/uploads/2018/01/VA241-launchkit-EN2.pdf VA241 Launch Kit
  2. ^ a b http://www.arianespace.com/wp-content/uploads/2018/01/CDP-18-05-VA241-update-FR.pdf First press release by Arianespace (in French)
  3. ^ https://www.youtube.com/watch?v=g47aftHgOnk&t=10m7s Replay of the Arianespace live video flux.
  4. ^ http://www.arianespace.com/wp-content/uploads/2018/01/1-26-2018-VA241-Ariane5-a-mis-en-orbite-SES14-AlYah3-FR.pdf Second press release by Arianespace (in French)
  5. ^ "SES-14 in good health and on track despite launch anomaly".
  6. ^ a b "A Bizarre Failure Scenario Emerges for Ariane 5 Mission Anomaly with SES 14 & Al Yah 3 – Ariane 5 VA241". Spaceflight 101. 26 January 2018. Retrieved 27 January 2018.
  7. ^ @DutchSpace (10 February 2018). "So, SES released the hi-res lift-off shot of #VA241 this allowed me to better compare the apparent roll I mentioned already here: https://twitter.com/DutchSpace/status/960646821977690112 … It seems pretty clear that when comparing VA241 (left) with VA230 (right) there had to be a roll pretty much from lift-off ... pic.twitter.com/WOID41BNld" (Tweet). Retrieved 12 February 2018 – via Twitter.
  8. ^ "VA241 Launch Kit Rev. 2" (PDF). Arianespace. Retrieved 12 February 2018.
  9. ^ Vanlerberghe, Cyrille (30 January 2018). "Ariane 5 : une erreur humaine à l'origine de la mauvaise trajectoire" [Ariane 5 : A human error is the origin of the bad trajectory]. Le Figaro (in French). Retrieved 30 January 2018.
  10. ^ Cabirol, Michel (30 January 2018). "L'incroyable raté d'ArianeGroup lors du lancement d'Ariane 5 (VA241)" [The incredible negligence of ArianeGroup during the Ariane 5 (VA241) launch]. La Tribune (in French). Retrieved 30 January 2018.
  11. ^ "Ariane 5 VA241 Anomaly Analysis – Ariane 5 VA241". Spaceflight101. Retrieved 4 February 2018.
  12. ^ Capdevila, Didier. "2018, Une Nouvelle Organisation pour Ariane" [2018, A New Organization for Ariane] (in French). Capcom Espace. Retrieved 4 February 2018.
  13. ^ Cabirol, Michel (26 February 2018). "Trois questions sans réponse autour du vol VA241 d'Ariane 5" [Three unanswered questions around the Ariane 5 flight VA241]. La Tribune (in French). Retrieved 26 February 2018.
  14. ^ de Selding and, Peter B. [@pbdes] (25 February 2018). "It's a question that will be asked. Industry officials say a judgment was made that the rocket was performing well (except for trajectory) and that the danger to local population of debris from flight termination outweighed the dangers of continuing flight" (Tweet). Retrieved 28 February 2018 – via Twitter.
  15. ^ Henry, Caleb (1 February 2018). "NASA to be part of Ariane 5 anomaly investigation". SpaceNews. Retrieved 7 March 2018.
  16. ^ "Action plan approved for next Ariane 5 launches". European Space Agency. 2 March 2018. Retrieved 8 March 2018. After the release of the conclusions of the Ariane VA241 Independent Enquiry Commission on 22 February, the findings and recommendations were formally presented to a Steering Board on 28 February.
  17. ^ "Independent Enquiry Commission announces conclusions concerning the launcher trajectory deviation during Flight VA241". Arianespace. 23 February 2018. Retrieved 8 March 2018. The Independent Enquiry Commission formed after the Ariane 5 launcher's trajectory deviation during its January 25, 2018 mission issued its conclusions on Thursday, February 22. The anomaly's cause is perfectly understood and recommendations are clearly identified. Arianespace and ArianeGroup are immediately implementing the Independent Enquiry Commission's recommended corrective measures. The current Soyuz and Ariane 5 launch campaigns are continuing at the Guiana Space Center in French Guiana for the two launches planned in March.
  18. ^ a b "Independent Enquiry Commission announces conclusions concerning the launcher trajectory deviation during Flight VA241". Arianespace. Retrieved 23 February 2018.
  19. ^ Todd, David (23 February 2018). "Arianespace knows cause of Ariane 5 flight deviation but concern remains about range safety". Seradata. Retrieved 7 March 2018.
  20. ^ Barensky, Stefan (23 February 2018). "La commission d'enquête indépendante dédouane Ariane 5" [The independent Enquiry Commission gives Ariane 5 go ahead] (in French). Aerospatium. Retrieved 26 February 2018.
  21. ^ "Ariane 5 satellites in orbit but not in right location". Yahoo! News. AFP News. 26 January 2018. Retrieved 26 January 2018.
  22. ^ Amos, Jonathan (26 January 2018). "Ariane rocket suffers rare anomaly". BBC News. Retrieved 26 January 2018.
  23. ^ Payer, Markus. "SES-14 in good health and on track despite launch anomaly". SES. Retrieved 26 January 2018.
  24. ^ Payer, Markus (28 August 2017). "SES Swaps SES-12 and SES-14 Launches". SES. Retrieved 17 February 2018.
  25. ^ http://gold.cs.ucf.edu/contact-successfully-established-with-ses-14-satellite-hosting-gold/ Contact Successfully Established With SES-14 Satellite Hosting GOLD
  26. ^ "Yahsat confirms launch of Al Yah 3 mission Satellite to greatly increase its global coverage". journeyofpride.com. Archived from the original on 27 January 2018. Retrieved 26 January 2018.
  27. ^ "UAE's Al Yah 3 satellite ready to provide internet services after successful tests in space". The National. 30 May 2018. Retrieved 19 June 2018.
  28. ^ Henry, Caleb (16 February 2018). "Eutelsat CEO optimistic on shorter broadcast contracts, OTT potential". SpaceNews. Retrieved 17 February 2018.
  29. ^ Todd, David (22 May 2018). "Al Yah 3 arrives in geostationary orbit but is predicted to have lost part of its expected lifespan". Seradata. Retrieved 19 June 2018.
  30. ^ Forrester, Chris (12 March 2018). "YahSat to make 50% insurance claim". Advanced Television. Retrieved 21 March 2018.
  31. ^ de Selding, Peter B. (20 March 2018). "Yahsat expected to file US$108-million claim for loss of life on Al Yah 3 satellite because of @Arianespace @ArianeGroup Ariane 5 off-target orbital injection". Twitter. Retrieved 21 March 2018.
  32. ^ Neiberlien, Henry (29 January 2018). "After 16 years, Ariane 5 finally fails". The Avion. Archived from the original on 30 January 2018. Retrieved 30 January 2018.
[edit]