Thursday, the twice postponed Starlink Group 9-3 launch went up from Vandenberg at the beginning of the window (no jellyfish for SoCal on
this one), and the booster (B1063 on its 19th flight) worked and was recovered.
Snidely explained :
Snidely used thar keyboard to writen:
Thursday, the twice postponed Starlink Group 9-3 launch went up from
Vandenberg at the beginning of the window (no jellyfish for SoCal on this >>> one), and the booster (B1063 on its 19th flight) worked and was recovered. >>>
But the second stage could be seen in the downlink to be shedding more ice >>> than usual from the insulated "bag" above the nozzle, and fell way short of >>> 200 km (152 km than down to 139 km after "stage 2 in terminal guidance" >>> was announced). SpaceX terminated the feed after "MVac shutdown" was
called out, about 38 min into the youtube relay by Spaceflight Now.
SpaceX's web site says "the second stage engine did not complete its second >>> burn .... satellites were deployed into a lower than intended orbit.
SpaceX has made contact with five of the satellites so far and is attmpting >>> to have them raise orbit using their ion thrusters."
/dps
Broken sense line. Return to flight successful on July 27, lift off at 1:45 >> EDT (Florida local time) from KSC, satellite deployment normal.
Two more Starlink launches this weekend, using the other two F9 launch sites:
CCSFS and Vandenberg.
A link to Eric Berger's article: <URL:https://arstechnica.com/space/2024/07/spacex-roars-back-to-orbit-barely-two-weeks-after-in-flight-anomaly/>
/dps
--
https://xkcd.com/2704
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 138:15:36 |
| Calls: | 12,087 |
| Files: | 14,997 |
| Messages: | 6,517,398 |