JRTI delivered B1052 at 5pm ET today and would need to be back at the LZ, 630km downrange, on Sunday night for Starlink 4-34 if the current NET date is to hold.At 6.5 knots (fast) the droneship would take 96 hours to reach the LZ. The launch NET is less than 96 hours away. 1/2
So, my analysis of the situation has two options:1. SL 4-34 is going to be delayed from Sunday night2. SpaceX is going to expend the first booster they fly 14 timesOption 2 is total rampant speculation. An FCC permit DOES exist to use the droneship for this mission. (2/2)
Looks lik the booster used is actually B1067.6, not B1051.14 as previously listed on Next Spaceflight.They've gotten lots of booster assignments wrong recently, for some reason.
Starlink 4-34 (Sun): JRTI droneship is hauling downrange, under the tow of tug Kurt J Crosby.With a crazy turnaround time from the last mission, JRTI should reach the LZ around midday on Sunday, 11 hours before T-0. 💪😱 Impressive stuff.
What was the reason for this evenings booster static fire of a Starlink mission? Thank you.
They've gotten lots of booster assignments wrong recently, for some reason.
110107Z SEP 22NAVAREA IV 919/22(11,26).WESTERN NORTH ATLANTIC.FLORIDA.1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING 140200Z TO 140307Z SEP, ALTERNATE 150138Z TO 150245Z, 160117Z TO 160224Z, 170055Z TO 170202Z, 180033Z TO 180140Z AND 190012Z TO 190119Z SEP IN AREAS BOUND BY: A. 28-39.12N 080-37.77W, 28-58.00N 080-17.00W, 28-51.00N 080-11.00W, 28-34.00N 080-28.00W, 28-32.35N 080-33.78W. B. 32-02.00N 076-46.00W, 33-11.00N 075-55.00W, 33-22.00N 075-07.00W, 33-01.00N 074-42.00W, 32-22.00N 075-03.00W, 31-52.00N 076-36.00W.2. CANCEL NAVAREA IV 910/22.3. CANCEL THIS MSG 190219Z SEP 22.
New NOTMAR was issued replacing the one Ken posted above, seems to have slipped a couple days.