Starlink Group 7-15 launch bulletin 2024-02-22/23
Starlink Group 7-15 launch bulletin 2024-02-22/23
Time for another Starlink mission. This one's an evening launch from Vandenburg. It will be the 19th flight of booster B1061.
Scheduled for (UTC) | 2024-02-23 04:11 |
---|---|
Scheduled for (local) | 2024-02-22 20:11 (PST) |
Mission | Starlink Group 7-15 |
Launch site | SLC-4E, Vandenberg Space Force Base, California, USA. |
Vehicle | Falcon 9 |
Booster | B1061 19th Flight |
Landing | ADSD Of Course I Still Love You at T+00:08:23 |
Inclination | 53° Why? |
Payload | 22 x Starlink V2 Mini deployed at T+01:02:17 |
Customer | SpaceX |
Mission success criteria | Successful launch and delivery of payload to low earth orbit |
Webcasts
Stream | Link |
---|---|
Space Affairs | https://www.youtube.com/watch?v=oQWd7EnE8MU |
The Launch Pad | https://www.youtube.com/watch?v=ikloLxNHxvU |
SpaceX | https://www.spacex.com/launches/mission/?missionId=sl-7-15 |
SpaceFlight Now | https://www.youtube.com/watch?v=wmHTtpdEoTA |
The Space Devs | https://www.youtube.com/watch?v=ySJ2qEwoxkE |
You're viewing a single thread.
Thanks for posting this thread! It looks great!
Spaceflight Now has a livestream link too now, which you could add: https://www.youtube.com/watch?v=wmHTtpdEoTA
You might want to adjust the dateful link, as it seems to be pointing to 23:11 on Thursday, rather than 04:11 on Friday.
1 0 ReplyThanks. The date link was a bit wrong but seems to give the correct result: https://dateful.com/convert/utc?t=2011&d=2024-02-23T04:11
I didn't notice the t=2011 argument and just appended T04:11 to the d argument. Seems to work ok for me.
1 0 ReplySeems to work ok for me.
Huh, that's odd. This is what I see:
Also, if you could add the Spaceflight Now and Space Devs links to the table in the main post, that would be great!
https://www.youtube.com/watch?v=wmHTtpdEoTA
https://www.youtube.com/watch?v=ySJ2qEwoxkE
Thanks again for helping out with this thread!
1 0 ReplySpaceflight Now and Space Devs links added. I've also fixed the dateful link. I think it might have been the & that was also messed up and may be resolved differently by different browser - anyway I hope it is fixed now.
1 0 Reply