-
SpaceX F9 : Starlink group 7-11 : VSFB SLC-4E : 23/24 January 2024 (00:35 UTC)
by
zubenelgenubi
on 03 Jan, 2024 18:04
-
Thread for the Starlink Group 7-11 launch.
Launch 24 January 2024, 00:35:00 UTC (23 Jan 4:35 p.m. PST), from Vandenberg SFB SLC-4E, on booster 1063-16. The first stage successfully landed aboard Of Course I Still Love You.Payload 22 Starlink V2 Mini satellites to 53 degree inclination orbit on a southeastern trajectory. Initial orbit 286 x 295 km.
Please use the
Starlink Discussion Thread for all general discussion on Starlink.
Check the
Starlink Index Thread for links to more Starlink information.
L2 SpaceX:
https://forum.nasaspaceflight.com/index.php?board=60.0
-
#1
by
zubenelgenubi
on 03 Jan, 2024 18:17
-
Cross-posts:
Four more Starlinks from Vandy
<snip>
2090-EX-ST-2023 Mission 2193 Starlink Group 7-11
<snip>
ASDS North 29 52 50 West 116 45 3
[Launch NET Nov 12]
https://nextspaceflight.com/launches/details/7322
Starlink Group 7-11
Launch Time
NET December, 2023
Starlink 7-11 likely follows
Starlink 7-10, with a launch NET January.
https://nextspaceflight.com/launches/details/7322
Starlink Group 7-11
Launch Time
NET January, 2024
Currently, launch should be NET mid January. (
Starlink 7-10 is currently scheduled to launch NET January 8.)
Unless,
Starlink 8-1 is cleared to launch in the near future. Then, it likely takes priority.
This likely pertains to Starlink 8-1.
BREAKING NEWS! FCC Approves in Part, Defers in Part SpaceX's Feb. 07, 2023 application to provide "Commercial" Direct 2 Device service. Providing SpaceX with "First Mover Advantage" in the D2D marketplace
SATMOD2023020700021
https://twitter.com/FREESPEECH1017/status/1730772350646526400
More on SpaceX D2D "Scope of Grant"
The most important. "Authority to Launch"
This Grant authorizes SpaceX for the Launch of "Modified" satellites (up to 7,500 Gen. 2) into the three authorized Gen. 2 orbital parameters and allows "limited on-orbit check out in the PCS G Block of the satellite buss and antenna deployment for a period of 10 days or less. This authority does not permit LEOP operations. Only the initial 10 day check out period on orbit.
This authorization was the first necessary step in the process. You can not authorize the "launch of satellites" on a STA. So this is the purpose of this License Grant. SpaceX will need to perform LEOP operations shortly after the payloads are past the initial checkout period.
That is where the new STA SpaceX applied for today 12/01 comes into play.
SES-STA-INTR2023-06753
"SpaceX will conduct its payload testing activities during the launch and early orbit phase (“LEOP”) of the satellites’ mission. During the critical check-out phase, which will begin within hours of launch at an altitude between 290 km and 350 km—depending on the particulars of the specific launch—and will continue for several weeks for each satellite, SpaceX will test the functionality of each direct-to-cellular payload and its network capabilities to ensure that they are operating as intended. Permitting this initial, internal LEOP check-out testing over several weeks (or longer as necessary) for each satellite is critical to assess and address issues as they arise."
Then eventually they will transition to the previously filed STA on October 2nd. for wide-spread testing with TMobile.
SAT-STA-20231002-00240
"Direct-to-cell STA to launch and test its non-geostationary orbit NGSO second generation Gen2 satellites with direct-to-cellular communications payloads to connect unmodified cellular phones directly to SpaceX Gen2 satellites"
Every D2D operator that will provide service to the US will require authority to launch from the FCC.
https://twitter.com/FREESPEECH1017/status/1730971108495823025
Correct. 10 days, then the STA will be approved fo[r] LEOP testing, 30 days, renewable. The take away is, you can't launch on a STA. Because you can not easily "unlaunch them" if the STA is not renewed. Watch for a series of filings next week for D2D missions @FCC. I suspect that the 800 satellite number will include at least 1 Starship launch.
Edit/add: zubenelgenubi
BREAKING NEWS! FCC Approves in Part, Defers in Part SpaceX's Feb. 07, 2023 application to provide "Commercial" Direct 2 Device service. Providing SpaceX with "First Mover Advantage" in the D2D marketplace
<snip>
So we will get notice of the Starlink Group 8-1 launch soon. 
If
Group 8 launches are approved, the still remaining
Group 6 and
7 launches may be canceled.
-
#2
by
Ken the Bin
on 11 Jan, 2024 13:20
-
NGA Space Debris notice that is effectively a Rocket Launching notice.
111020Z JAN 24
NAVAREA XII 9/24(21).
EASTERN NORTH PACIFIC.
MEXICO.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
160327Z TO 160755Z, 170305Z TO 170733Z,
180244Z TO 180712Z, 190222Z TO 190650Z,
200200Z TO 200628Z, 210200Z TO 210628Z
AND 220200Z TO 220628Z JAN
IN AREA BOUND BY
29-09.00N 116-24.00W, 29-18.00N 116-43.00W,
30-31.00N 117-14.00W, 30-31.00N 117-13.00W,
30-17.00N 116-46.00W, 29-41.00N 116-04.00W,
29-23.00N 116-02.00W.
2. CANCEL THIS MSG 220728Z JAN 24.//
The two multi-launch NGA Space Debris notices that are still in effect (the same notice for two different Navigational Areas).
270500Z DEC 23
HYDROPAC 4029/23(22).
EASTERN SOUTH PACIFIC.
DNC 06, DNC 07.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
310001Z DEC 23 TO 210001Z FEB 24
IN AREA BOUND BY
34-20.00S 090-24.00W, 31-22.00S 090-24.00W,
00-10.00S 115-17.00W, 01-19.00S 116-54.00W.
2. CANCEL THIS MSG 210101Z FEB 24.//
270500Z DEC 23
NAVAREA XII 885/23(22).
EASTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
310001Z DEC 23 TO 210001Z FEB 24
IN AREA BOUND BY
34-20.00S 090-24.00W, 31-22.00S 090-24.00W,
00-10.00S 115-17.00W, 01-19.00S 116-54.00W.
2. CANCEL THIS MSG 210101Z FEB 24.//
-
#3
by
zubenelgenubi
on 12 Jan, 2024 00:08
-
4 day
OCISLY turnaround? Is that possible?
What is the approximate minimum turnaround with calm seas Long Beach to the
Group 7 recovery zone and back (not counting dock operations)? 🌊
-
#4
by
OneSpeed
on 12 Jan, 2024 01:01
-
NGA Space Debris notice that is effectively a Rocket Launching notice.
Maps from the NGA notices. The booster recovery area is a slightly different shape from previous group 7 launches, but the ASDS is still 642km downrange.
-
#5
by
VLN
on 12 Jan, 2024 04:19
-
4 day OCISLY turnaround? Is that possible?
What is the approximate minimum turnaround with calm seas Long Beach to the Group 7 recovery zone and back (not counting dock operations)? 🌊
With the slip in Starlink 7-10, this is now 2 days and 18.5 hr between launch times.
ca
tdlr is still right that a round trip for OCISLY is over 5 days. Unloading the booster at PoLB adds at least a day to that. So if Starlink 7-11 doesn't slip, it's truly impossible for OCISLY to catch both boosters.
Maybe there's a surprise afoot. Note that Debra C accompanied OCISLY for several launches between Thanksgiving and Jan 2, while Scorpius sat in PoLB. This time, Scorpius is braving the seas with OCISLY while Debra C is in port. Why would they be cultivating two vessels to accompany one ASDS?
-
#6
by
catdlr
on 12 Jan, 2024 04:52
-
4 day OCISLY turnaround? Is that possible?
What is the approximate minimum turnaround with calm seas Long Beach to the Group 7 recovery zone and back (not counting dock operations)? 🌊
With the slip in Starlink 7-10, this is now 2 days and 18.5 hr between launch times.
catdlr is still right that a round trip for OCISLY is over 5 days. Unloading the booster at PoLB adds at least a day to that. So if Starlink 7-11 doesn't slip, it's truly impossible for OCISLY to catch both boosters.
Maybe there's a surprise afoot. Note that Debra C accompanied OCISLY for several launches between Thanksgiving and Jan 2, while Scorpius sat in PoLB. This time, Scorpius is braving the seas with OCISLY while Debra C is in port. Why would they be cultivating two vessels to accompany one ASDS?
I have always considered the possibility that SpaceX might lease a dock at the Port of San Diego to store one booster and then set out to retrieve another and return to bring back that and the one left at San Diego, ultimately transporting both back on one barge. This idea came to me when the OCISLY had to dock there due to bad weather conditions. They may have already made arrangements to set this up, but I am not certain. Someone will need to closely monitor cruise tracking over the next few days to see what unfolds.
It's only 3 hours between Long Beach and San Diego. Wouldn't it be faster to bring all the boosters into San Diego after catching them and truck them back to Long Beach for refurbishment? That way the travel distance from the landing zone to San Diego is much closer and provides a quicker turnaround. But maybe there are low overpasses and detours required for the truck and booster to navigate. Might be a pass on that suggestion.
-
#7
by
wjbarnett
on 12 Jan, 2024 13:06
-
I thought they were not trucking boosters out of Long Beach at all, but putting them in pairs on a barge back to VSFB's dock. Doing that from San Diego makes sense to me, but I'd also guess has more expensive dock space.
-
#8
by
catdlr
on 12 Jan, 2024 15:37
-
I thought they were not trucking boosters out of Long Beach at all, but putting them in pairs on a barge back to VSFB's dock. Doing that from San Diego makes sense to me, but I'd also guess has more expensive dock space.
HI wjbarnett,
I'm not 100% sure that SpaceX is taking valuable time using the barge to transport boosters back up to VSFB. They would have to be laying flat on separate transports. There is no crane at the VSFB port if coming vertically either. I agree that would be the correct solution. The VSFB port and the Launch Pad are reasonably close, especially to the new SLC-6 site. I just have not seen any ship movement to substantial it. I'm always vulnerable to error, but my statements might jar someone's recollection to post a reply (me, me, me, I know it, teacher).
SpaceX has invested somewhat at Long Beach for Booster retrieval, but there's no evidence of anything happening at San Diego, I was just fishing. I caught you.
Thanks, wjbarnett for the response. Always questions we have.
Best.
Tony
-
#9
by
Alexphysics
on 12 Jan, 2024 17:55
-
I'm not 100% sure that SpaceX is taking valuable time using the barge to transport boosters back up to VSFB. They would have to be laying flat on separate transports. There is no crane at the VSFB port if coming vertically either. I agree that would be the correct solution. The VSFB port and the Launch Pad are reasonably close, especially to the new SLC-6 site. I just have not seen any ship movement to substantial it.
SpaceX barges boosters and fairing halves every week or so from Port of Long Beach out to Vandenberg using the dock at the end of SLC-6. No need for a crane at Vandenberg as the boosters and fairing halves already arrive in horizontal configuration from Long Beach.
-
#10
by
catdlr
on 12 Jan, 2024 18:06
-
I'm not 100% sure that SpaceX is taking valuable time using the barge to transport boosters back up to VSFB. They would have to be laying flat on separate transports. There is no crane at the VSFB port if coming vertically either. I agree that would be the correct solution. The VSFB port and the Launch Pad are reasonably close, especially to the new SLC-6 site. I just have not seen any ship movement to substantial it.
SpaceX barges boosters and fairing halves every week or so from Port of Long Beach out to Vandenberg using the dock at the end of SLC-6. No need for a crane at Vandenberg as the boosters and fairing halves already arrive in horizontal configuration from Long Beach.
You heard it from "The Man" Alex. Thanks, Alex. wjbarnett your "thought" was right.
So having a port in San Diego wouldn't make sense if they're barging booster and fairings from Long Beach. It would mean a full transfer of facilities and make the barge trip from San Diego to VSFB longer. It's a half-dozen of one or 6 six of another as they say.
Ok back to the launch.
Thanks, everyone,
Tony
-
#11
by
Galactic Penguin SST
on 13 Jan, 2024 01:08
-
Not surprisingly this has slipped at least 1 day as 7-10 slips, suggesting that SpaceX is trying to perform 4 days pad turnarounds on the West Coast as well:
R0011/24 NOTAMN
Q) SCIZ/QRDCA/IV/BO/W/000/999/4100S11910W715
A) SCIZ B) 2401170444 C) 2401230807
D) JAN 17 0444-0912 JAN 18 0423-0851 JAN 19 0401-0829 JAN 20 0339-0807
JAN 21 0339-0807 JAN 22 0339-0807 JAN 23 0339-0807
E) ZONE ...D... SECT WEST PACIFIC DUE TO RE-ENTRY FALCON 9 STARLINK 7
-11 STAGE 2 REENTRY ACTIVITY. THE AREA IS BOUNDED BY GEO COORD:
1500S 10724W
1500S 10441W
3122S 09024W
3420S 09024W
INSTRUCTIONS: SANTIAGO OCEANIC CONTROL 10024 KHZ FANS 1A EQUIPPED
ACFT LOG ON SCEZ
INFO PROVIDED BY SPACE X OPS, USA
F) SFC G) UNL
-
#12
by
zubenelgenubi
on 15 Jan, 2024 22:56
-
With the Starlink 7-10 launch on January 14, that should make this launch NET January 18 UTC? (Four day SLC-4E/OCISLY turnaround goal)
Which first stage will be used for this launch? (semi-rhetorical question)
Falcon 9 first stages are apparently now cleared for use up to twenty times for non-human spaceflight missions, although that number is apparently more restricted for Cargo Dragon than these other payloads.
Available first stages, with UTC date of most recent recovery:
1063.16 Nov 20
1071.13 Dec 8
1075.9 Dec 24
Edit January 19 UTC: It's B1063.16.
Edited
-
#13
by
alugobi
on 15 Jan, 2024 23:12
-
Go Beyond is currently off Ensenada, not quite half the way back to Long Beach, making 7.7knots. I wouldn't count on getting OCISLY back down there by the 18th.
-
#14
by
Martin_G
on 16 Jan, 2024 09:30
-
-
#15
by
FLHerne
on 16 Jan, 2024 13:29
-
So having a port in San Diego wouldn't make sense if they're barging booster and fairings from Long Beach. It would mean a full transfer of facilities and make the barge trip from San Diego to VSFB longer. It's a half-dozen of one or 6 six of another as they say.
It would be useful for JRTI cycle time. The barge used to transfer boosters/fairings to Vandenberg is a different one, generic flat utility barge, not the ASDS.
-
#16
by
VLN
on 16 Jan, 2024 14:41
-
https://www.fly.faa.gov/adv/adv_spt.jsp
SPACE X STARLINK 7-11
VANDENBERG SFB, CA
PRIMARY: 01/19/24 0222Z-0650Z
BACKUP: 01/20-23/24 0200Z-0628Z
Booster recovery zone:
B0041/24 NOTAMR B0032/24
Q) MMFR/QRDCA/IV/BO/W/000/999/
A) MMFR
B) 2401190222
C) 2401250442
D) 19 0222-0650, 20 21 22 23 0200-0628, 24 0035-0503, 25 0014-0442
E) DANGEROUS AREA FOR REENTRY OF ROCKET FALCON 9 STARLINK 7-11
LATERAL LIMIT AREA FORMED BY THE UNION OF THE FLW POINTS:
29 09N 116 24W
29 18N 116 43W
30 35N 117 34W
31 00N 117 34W
31 00N 117 19W
30 25N 116 41W
29 41N 116 04W
29 23N 116 02W
29 09N 116 24W
MMFR
F) MSL
G) UNL
Second stage reentry:
R0016/24 NOTAMN
Q) SCIZ/QRDCA/IV/BO/W/000/999/4100S11910W715
A) SCIZ
B) 2401190401
C) 2401250621
D) 19 0401-0829 / 20 0339-0807 / 21 0339-0807 / 22 0339-0807 /
23 0339-0807 / 24 0214-0642/ 25 0153-0621
E) ZONE ...D... SECT W PACIFIC DUE TO RE-ENTRY FALCON 9 STARLINK 7-11
STAGE 2 REENTRY ACT. THE AREA IS BOUNDED BY:
1500S 10724W
1500S 10441W
3122S 09024W
3420S 09024W
INSTRUCTIONS: SANTIAGO OCEANIC CONTROL 10024 KHZ FANS 1A EQUIPPED ACFT LOG ON SCEZ
INFO PROVIDED BY SPACE X OPS, USA
F) SFC
G) UNL
-
#17
by
Ken the Bin
on 16 Jan, 2024 20:59
-
A cancel-and-replace NGA Space Debris notice (effectively a Rocket Launching notice) for the postponement to the January 19 UTC, including two new backup days for the days removed.
Note that the time for January 19 has changed from 02:22 UTC to 04:00 UTC.162121Z JAN 24
NAVAREA XII 16/24(21).
EASTERN NORTH PACIFIC.
MEXICO.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
190400Z TO 190650Z, 200200Z TO 200628Z,
210200Z TO 210628Z, 220200Z TO 220628Z,
230200Z TO 230628Z, 240035Z TO 240503Z
AND 250014Z TO 250442Z JAN
IN AREA BOUND BY
29-09.00N 116-24.00W, 29-18.00N 116-43.00W,
30-31.00N 117-14.00W, 30-31.00N 117-13.00W,
30-17.00N 116-46.00W, 29-41.00N 116-04.00W,
29-23.00N 116-02.00W.
2. CANCEL NAVAREA XII 9/24.
3. CANCEL THIS MSG 250642Z JAN 24.
-
#18
by
VLN
on 17 Jan, 2024 05:15
-
A cancel-and-replace NGA Space Debris notice (effectively a Rocket Launching notice) for the postponement to the January 19 UTC, including two new backup days for the days removed.
Note that the time for January 19 has changed from 02:22 UTC to 04:00 UTC.
162121Z JAN 24
NAVAREA XII 16/24(21).
EASTERN NORTH PACIFIC.
MEXICO.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
190400Z TO 190650Z, 200200Z TO 200628Z,
{snip}
The first opportunity is still too soon for OCISLY. To arrive at the recovery zone well before 2024-01-19 0400Z, OCISLY would have to leave PoLB by about 2024-01-16 2300Z, or roughly the time it arrived in port today from catching Starlink 7-10. (It can't even catch the trailing edge of the first launch window, because it didn't leave by mid-afternoon PST.)
Meanwhile, Debra C hasn't budged. They haven't deployed a secret twin OCISLY as I speculated. So I can't dispute that WYSIWYG, and therefore the launch will be NET 2024-01-20 0200Z.
-
#19
by
catdlr
on 17 Jan, 2024 05:30
-
A cancel-and-replace NGA Space Debris notice (effectively a Rocket Launching notice) for the postponement to the January 19 UTC, including two new backup days for the days removed.
Note that the time for January 19 has changed from 02:22 UTC to 04:00 UTC.
162121Z JAN 24
NAVAREA XII 16/24(21).
EASTERN NORTH PACIFIC.
MEXICO.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
190400Z TO 190650Z, 200200Z TO 200628Z,
{snip}
The first opportunity is still too soon for OCISLY. To arrive at the recovery zone well before 2024-01-19 0400Z, OCISLY would have to leave PoLB by about 2024-01-16 2300Z, or roughly the time it arrived in port today from catching Starlink 7-10. (It can't even catch the trailing edge of the first launch window, because it didn't leave by mid-afternoon PST.)
Meanwhile, Debra C hasn't budged. They haven't deployed a secret twin OCISLY as I speculated. So I can't dispute that WYSIWYG, and therefore the launch will be NET 2024-01-20 0200Z.
Thursday evening local time is the last opportunity to launch, Friday and into the weekend, a front comes though from the north bring rain. I'll provide marine weather tomorrow.
