2026-W46
9 Nov 2026 to 15 Nov 2026
49 claims: 25 CONFIRMED, 24 UNCONFIRMED
Grouped by the site stated in the claim; moves use their destination. No site means no site was stated. A claim naming several vehicles or hardware items appears once under a combined group.
mb1 Mega Bay 1
B22
note UNCONFIRMED
VickiCocks15 says the Booster Transport Ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad for launch, and that the booster lifting jig was moved into Mega Bay 1 on 8 Nov.
B25
note UNCONFIRMED
VickiCocks15 says Booster 25's A5 section was relocated to Mega Bay 1 while the attached lift of Ship 45 was underway. Her first post named Booster 45 and a later post corrected it to Booster 25.
mb2 Mega Bay 2
S42
note CONFIRMED
Ship 42 was lifted onto a transport stand and left Mega Bay 2 on the evening of 11 Nov (Texas time) while the Starlink speed loader and loading box came over from the Starfactory to the ring yard; the loader was then lifted into Mega Bay 2, and on 12 Nov Ship 42 was moved back inside Mega Bay 2 to have its 26 Starlink V3 satellites installed.
note UNCONFIRMED
VickiCocks15 says a Ship lift jig was raised and translated across to the right-hand side of Mega Bay 2, theoretically for Ship 42. She notes ships have previously been moved onto a STR for payload bay satellite loading.
S45
note CONFIRMED
Ship 45 was sleeved over its transfer tubes in Mega Bay 2 and the jig removed, then the final Ship section arrived. VickiCocks15 describes the sequence; lewisknaggs42 says the nose cone rollout to the aft section took 19 days, credited to LabPadre.
gigabay-tx Gigabay (Starbase)
Site and other claims
note UNCONFIRMED
VickiCocks15 says a test rig for the doorway runners was lifted and lowered within the Gigabay framework.
pad1 Starbase Pad 1
Site and other claims
note CONFIRMED
The second of four sloped wall sections was installed in the Pad 1 flame trench, and VickiCocks15 later saw another sloped trench wall section lifted into place.
pad2 Starbase Pad 2
B22
note UNCONFIRMED
VickiCocks15 says the Pad 2 chopsticks released Booster 22 again on 11 Nov and returned to the side of the launch mount, with the crew lift that had worked on the grid fins moved away, then later the chopsticks moved back up the tower and hugged Booster 22 once more. She also says one of the chopstick sims was put back in the Super Crusher cage, suggesting testing of 43.1 is not finished.
note CONFIRMED
The Pad 2 chopsticks released Booster 22 and descended the tower and the SQD arm was reset. Workers then spent several hours around B22's catch pins and grid fins, the booster transport stand returned to the build site, the SQD was retracted and the chopsticks went back to the booster support position.
note CONFIRMED
Booster 22 was lifted to the top of the Pad 2 tower, moved around on the chopsticks using the pusher system, and lowered onto the orbital launch mount. VickiCocks15 later described it as settled on the mount with the clamps lined up.
move CONFIRMED
Booster 22 left the production site and arrived at the Pad 2 launch site on the evening of 9 Nov (Texas time), for Flight 15. Trackers posted it as T-93 hours.
S42
note UNCONFIRMED
LabPadre says the stabilizer pins engaged on Ship 42 as it lowered to connect the SQD, and later that the SQD attached to S42 and residual detanking began; Blobifie also says the SQD arm attached to allow detanking and safing.
note UNCONFIRMED
VickiCocks15 says the SQD access platform was retracted, the SQD attached to Ship 42, and a fast retract and reattach test performed. TrackingTheSB also says the SQD was being connected to Ship 42.
note CONFIRMED
Ship 42 was driven to the Starbase launch site on 12 Nov, lifted onto Booster 22 at Pad 2 and stacked for Flight 15. SpaceX posted that Ship 42 moves to the Starbase pad ahead of launch, and NASASpaceflight posted the Ship 42 lift.
Site and other claims
note UNCONFIRMED
VickiCocks15 says the LM-2 hold-down clamps and both BQDs have been extended after Flight 15.
note UNCONFIRMED
TrackingTheSB says the Pad 2 chopsticks, which had sat at the bottom of the tower after the Booster 22 divert, returned to catch height; LabPadre also reports the chopsticks raised back to the catch position after a brief inspection by workers.
No site
B22
note CONFIRMED
Elon Musk says the booster is meant to land with tiny residuals, so the fix is better engine performance and consistency (underway with Raptor V3.2) plus flight software that does MECO1 about one second earlier to leave enough propellant for boostback and landing.
note UNCONFIRMED
Blobifie says Dan Huot stated the Booster 22 landing abort was a GNC issue that led to a self abort and a Gulf splashdown, and that the flight termination system triggered after engine cutoff.
note CONFIRMED
Elon Musk says the green flame on Flight 15 came from burning copper from depleting fuel in the regenerative cooling circuit as the main combustion chamber went oxygen-rich, caused by slight engine underperformance.
note UNCONFIRMED
LabPadre says Kate confirmed Booster 22's boostback burn ended early on a low fuel mass alarm, and the booster then autonomously judged itself out of position for a catch and diverted.
note UNCONFIRMED
TrackingTheSB says the remains of Booster 22 seem to have gone fully under the water during the night, citing NASASpaceflight imagery.
note CONFIRMED
SpaceX says Super Heavy diverted to an offshore splashdown in the Gulf on Flight 15 instead of the planned catch; LabPadre logged the booster divert at T+00:06:35 and NASASpaceflight carried SpaceX's Dan Huot saying Booster 22 automatically aborted the return to Pad 2 due to a GNC issue.
note UNCONFIRMED
VickiCocks15 says the booster transport ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad before launch, and that the road delay was pushed back to 20:00 local time on 9 Nov.
B25
note UNCONFIRMED
VickiCocks15 says Booster 25's A6 section headed towards MB-1 on 12 Nov, followed by the associated LOX landing tank, and that the rear Gigabay door was closed for the first time she has seen.
S42
note CONFIRMED
Elon Musk says he went over the whole Starship heat shield and it looks great overall, the engines look great too, and Ship 42 could probably be reflown with a few weeks of refurbishment, but many small fixes are needed for airplane-like immediate reusability. LabPadre relayed the reflight line.
note UNCONFIRMED
Blobifie says Ship 42 was safed and its transport stand moved to the launch site, and later (04:22 UTC) that S42 was still hanging from the chopsticks attached to the SQD, with a beacon set up in the rocket garden where it will be displayed.
note UNCONFIRMED
AshleyKillip says a band about 19 tiles wide on Ship 42, running from the bottom of the liquid oxygen tank up to the forward dome, has a distinct matte look where plasma appears to have ablated the layer that usually makes the tiles glossy.
note CONFIRMED
Ship 42 was lowered onto its ship transport stand at Pad 2 after the Ship QD arm retracted and a flap was retracted, then rolled back to the production site, arriving around 23:15 UTC on 15 Nov (NASASpaceflight, RGV Aerial Photography, LabPadre).
note CONFIRMED
SpaceX says Ship 42 completed a good deorbit burn and was on course to reenter ahead of a planned catch at Starbase about an hour later.
note UNCONFIRMED
NASASpaceflight posted a Cybertruck procession with the Ship Transport Stand after the catch, and AshleyKillip says the stand was on the way to the launch site to collect S42.
note CONFIRMED
SpaceX says Starship and its heatshield are healthy in orbit and that a planned return to launch site catch at Starbase is about 22.5 hours after launch.
note UNCONFIRMED
LabPadre says Ship 42 deployed 26 V3 Starlink satellites by T+01:17:40 and closed its payload bay door.
note CONFIRMED
SpaceX says Starship performed its orbital insertion burn with a single Raptor engine and entered an orbit of Earth (about 275 km planned), after the ascent burn left it on a planned suborbital trajectory.
note UNCONFIRMED
TrackingTheSB says what looks to be alignment markers have been added to Ship 42, and that it is unclear whether they are for general operations or specific to post-catch operations.
note CONFIRMED
SpaceX says Starship began deploying a payload of 26 Starlink V3 satellites on Flight 15, a sequence taking about 42 minutes.
Site and other claims
outcome CONFIRMED
Flight 15 result: Ship 42 reached orbit with a Starlink V3 payload and was caught by the Pad 2 chopsticks at Starbase, the first ship catch; Booster 22 diverted to an offshore Gulf splashdown instead of a catch.
note CONFIRMED
SpaceX says Starship is in a long coast phase and that teams intend to stay in orbit about 21 hours, with a few early deorbit options available if needed.
note CONFIRMED
SpaceX posted 'Liftoff of Starship!' at 22:48 UTC on 13 Nov for Flight 15 (Booster 22 and Ship 42 per LabPadre), the Flight 15 liftoff from Starbase.
note UNCONFIRMED
Blobifie says the FAA has yet to issue SpaceX a licence for Flight 15 launch, 12 hours before the window.
filing CONFIRMED
City of Starbase Mayor's Order No. 2026-26, declared 13 Nov 2026 at 10:00 a.m., closes Boca Chica Beach and State Highway 4 on Sunday 15 Nov, 11:00 a.m. to 11:30 p.m. CT (primary closure period) for SpaceX spaceflight activities, with a clear zone under the Final Tiered Environmental Assessment.
filing UNCONFIRMED
LabPadre lists new NOTAMs ahead of Flight 15 on 12 and 13 Nov, including 11/144 and 11/145 for Starbase, TX on 14 Nov 16:45 to 18:40 CST, 11/164 for Starbase, TX on 15 Nov 16:45 to 18:40 CST and Oakland Oceanic FIR notices for 15 Nov, and says one batch covers potential re-entry locations and catch of Starship 42.
filing CONFIRMED
FAA hazards TFR FDC 6/7165 near Brownsville VORTAC (BRO), issued 12 Nov 2026 at 1206 UTC with SpaceX Security, Starbase as point of contact: 1.5 nm radius from the surface to 5,000 ft AGL centred 25°57'01"N 97°14'59"W, from 19 Nov 0500 UTC to 29 Nov 0500 UTC.
filing UNCONFIRMED
LabPadre lists a new USCG safety zone, SOUTH BAY SAFETY ZONE SPACE LAUNCH, Sector Corpus Christi, from 11 Nov 18:00 CST to 21 Nov 17:59 CST.
filing CONFIRMED
City of Starbase Mayor's Order No. 2026-25, declared 11 Nov 2026 at 9:45 a.m., closes State Highway 4 and Boca Chica Beach on Fri 13 Nov and Sat 14 Nov, 11:00 a.m. to 11:30 p.m. CT each day (both primary closure periods) for SpaceX spaceflight activities, with a clear zone under the Final Tiered Environmental Assessment. LabPadre reported the same two closure days.
filing CONFIRMED
FAA Space Operations NOTAMs FDC 6/7129 to 6/7132 for Starbase, Texas, issued 11 Nov 2026 at 1650 UTC: surface to unlimited over a region bounded near BRO, 13 Nov 2230 to 14 Nov 0040 UTC (6/7129), 14 Nov 2230 to 15 Nov 0040 UTC (6/7130), 14 Nov 2053 to 15 Nov 0014 UTC (6/7131) and 15 Nov 2053 to 16 Nov 0014 UTC (6/7132). The NOTAM text does not name a flight.
filing CONFIRMED
FAA TFR FDC 6/6928 near Brownsville, Texas (BROWNSVILLE VORTAC), issued 10 Nov 2026 at 18:22 UTC with SpaceX Security, Starbase as point of contact, from 12 Nov 05:00 UTC to 4 Dec 05:00 UTC, reason temporary flight restrictions, type Hazards.
filing UNCONFIRMED
LabPadre posted an updated marine hazard area for Starship Flight 15 in NAVAREA IV, 13 Nov 16:45 CST to 19 Nov 18:40 CST, and an updated Gulf of Mexico hazardous space operations area for Sector Corpus Christi covering the same window.
filing CONFIRMED
FAA operations advisory (ATCSCC ADVZY 064 DCC, Operations Plan, 9 Nov 2026) lists SpaceX Starship FLT-15 from Starbase, primary 13 Nov 2245Z to 0040Z and backup 14 Nov 2245Z to 0040Z, and FLT-15 reentry, primary 14 Nov 2056Z to 0014Z and backup 15 Nov 2056Z to 0014Z.
note UNCONFIRMED
LabPadre reports a new NAVAREA IV marine hazard area for Starship Flight 15, 13 Nov 16:45 to 18:40 CST, linking the USCG NAVCEN chart.
