NASASpaceFlight.com Forum
SpaceX Vehicles and Missions => SpaceX Falcon Missions Section => Topic started by: Jansen on 12/10/2020 06:04 am
-
Discussion thread for Starlink v1.0 Launch 17.
NSF Threads for Starlink v1.0 L17: Discussion (https://forum.nasaspaceflight.com/index.php?topic=52511.0)
NSF Articles for Starlink v1.0 L17: https://www.nasaspaceflight.com/2021/02/spacex-launch-delayed-starlink/
Launched successfully on March 4 at 3:24am EST (0824 UTC) on Falcon 9 (booster 1049.8 ) from Kennedy Space Center’s LC-39A. ASDS landing successful on OCISLY, towed by tugboat Hawk. Fairing recovery of both halves from the water by support ships GO Searcher and GO Navigator was successful.
The Falcon 9 first stage rocket booster supporting this mission previously flew on seven missions: the Iridium-8 mission, the Telstar 18 VANTAGE mission, and five Starlink missions. Following stage separation, SpaceX will land Falcon 9’s first stage on the “Of Course I Still Love You” droneship, which will be located in the Atlantic Ocean. One half of Falcon 9’s fairing previously flew on three Starlink missions, and the other half previously supported two Starlink missions.
Payload: A batch of 60 Starlink satellites. Expected deployment orbit of approximately 255x287km.
Please use the Starlink Discussion Thread (https://forum.nasaspaceflight.com/index.php?topic=48297.0) for all general discussion on Starlink.
Check the Starlink Index Thread (https://forum.nasaspaceflight.com/index.php?topic=48981.0) for links to more Starlink information.
L2 SpaceX:
https://forum.nasaspaceflight.com/index.php?board=60.0 (https://forum.nasaspaceflight.com/index.php?board=60.0)
From a previous mission's Press Kit:
Each Starlink satellite weights approximately 260 kg and features a compact, flat-panel design that minimizes volume, allowing for a dense launch stack to take full advantage of Falcon 9’s launch capabilities. With four powerful phased array and two parabolic antennas on each satellite ... At end of their life cycle, the satellites will utilize their on-board propulsion system to deorbit over the course of a few months. In the unlikely event their propulsion system becomes inoperable, the satellites will burn up in Earth’s atmosphere within 1-5 years, significantly less than the hundreds or thousands of years required at higher altitudes. Further, Starlink components are designed for full demisability.
Starlink is targeting service in the Northern U.S. and Canada in 2020, rapidly expanding to near global coverage of the populated world by 2021. Additional information on the system can be found at starlink.com.
-
Crosspost:
And Mission 1545 (Starlink v1.0 L17)
https://fcc.report/ELS/Space-Exploration-Technologies-Corp-SpaceX/1829-EX-ST-2020
-
Crosspost:
And Mission 1545 (Starlink v1.0 L17)
https://fcc.report/ELS/Space-Exploration-Technologies-Corp-SpaceX/1829-EX-ST-2020
The STA for this mission has been granted. Valid from 12 January 2021 through 12 July 2021.
https://apps.fcc.gov/els/GetAtt.html?id=264968&x=.
-
Looking at the current manifest, the earliest launch possible based on previous pad turnaround is 30 Jan from LC-39A and SLC-40.
It would also be the fourth launch of the month, tying a launch record and on par for SpaceX’s target of 48 launches in 2021.
-
Looking at the current manifest, the earliest launch possible based on previous pad turnaround is 30 Jan from LC-39A and SLC-40.
Why? They've done 6-day turnarounds on both pads in the past (when counting from launch to next SF, which is a more useful metric than launch-to-launch).
-
Looking at the current manifest, the earliest launch possible based on previous pad turnaround is 30 Jan from LC-39A and SLC-40.
Why? They've done 6-day turnarounds on both pads in the past (when counting from launch to next SF, which is a more useful metric than launch-to-launch).
Launch to launch turnaround is more useful for predicting the next launch date as it includes payload mate and integrated system checks.
-
But launch to launch metric also includes stuff like weather delays or rocket HW issues which skews the numbers.
Starlink missions often skip static fires and even when they don't, they're done with payload already attached, so that's maybe like an extra day from when the pad is ready for a SF. So I think it's safe to say the pad turnaround can be as low as 7 days, not 12 days, like you're calculating.
-
The Hazard area for this mission has been posted.
https://twitter.com/EmreKelly/status/1352005107223818242
-
That ASDS needs to haul butt back to port to unload and get back on station to make the 27th.
-
B1049 seems like the obvious choice for this mission.
-
Noway this launch will occur in 7 days. JRTI needs 4 days to get back home, then at least a few hours for unloading, and 4-5 days for a trip to the landing zone.
-
Anyone have the AIS data on Hawk? If octograbber was quick, they may already be well underway, making the 27th not entirely impossible.
-
Noway this launch will occur in 7 days. JRTI needs 4 days to get back home, then at least a few hours for unloading, and 4-5 days for a trip to the landing zone.
Should be enough room on the deck to have 2 boosters on at once. Never would happen but I suspect its technically feasible.
-
Noway this launch will occur in 7 days. JRTI needs 4 days to get back home, then at least a few hours for unloading, and 4-5 days for a trip to the landing zone.
Should be enough room on the deck to have 2 boosters on at once. Never would happen but I suspect its technically feasible.
I'm sure this has already been discussed to death in another better thread but this is one of those cases where it would just be insane without making substantial changes. Most notably, SpaceX would need to secure the stage with Octagrabber, move it to a corner, remove Octagrabber, and safely secure the stage again with jacks and shoes. Even then, in the event that the second booster lands but is hit by sea conditions that prevent recovery and leave it sliding around, two boosters would be at risk. Almost impossible to imagine SpaceX risking two landings on the same ship in with the current operational regime and fleet as-is.
But again, please discuss this concept elsewhere unless it becomes clear that it's actually SpaceX's plan for JRTI and B1051.
-
If they really want to make it happen, they can dump the booster at Morehead City and get back to LZ.
-
If they really want to make it happen, they can dump the booster at Morehead City and get back to LZ.
This would greatly increase the turnaround time on the booster and ultimately be counterproductive to the long term launch cadence.
-
That ASDS needs to haul butt back to port to unload and get back on station to make the 27th.
It would not be the first time that someone at SpaceX used an older date that did not account for delays to previous launches. Expect this to be postponed at least 2-3 days.
-
Next SpaceFlight and Ben Cooper have updated the launch to January 27.
Edit: Targeting approximately 8am EST (1300 UTC)
Edit2: Recovery on JRTI
-
B1049 seems like the obvious choice for this mission.
I concur, but there may be some refurbishment delays.
Here’s the full list of possible boosters for the curious:
B1049.8
63 days Nov 25-Jan 27
B1063.2
66 days Nov21-Jan 27
B1059.6
39 days Dec 19-Jan 27
-
B1049 seems like the obvious choice for this mission.
I concur, but there may be some refurbishment delays.
Here’s the full list of possible boosters for the curious:
B1049.8
63 days Nov 25-Jan 27
B1063.2
66 days Nov21-Jan 27
B1059.6
39 days Dec 19-Jan 27
1063 is still at West coast.
1049 seems most logical.
1056 then for Starlink 18 likely begin feb
1060 then for Starlink 19 likely mid feb
-
Should be enough room on the deck to have 2 boosters on at once. Never would happen but I suspect its technically feasible.
I'm sure this has already been discussed to death in another better thread but this is one of those cases where it would just be insane without making substantial changes. Most notably, SpaceX would need to secure the stage with Octagrabber, move it to a corner, remove Octagrabber, and safely secure the stage again with jacks and shoes. Even then, in the event that the second booster lands but is hit by sea conditions that prevent recovery and leave it sliding around, two boosters would be at risk. Almost impossible to imagine SpaceX risking two landings on the same ship in with the current operational regime and fleet as-is.
But again, please discuss this concept elsewhere unless it becomes clear that it's actually SpaceX's plan for JRTI and B1051.
Both of you are right. It's technically feasible (the accuracy is good enough) but has practical problems after the landing. Previous discussion is here. (https://forum.nasaspaceflight.com/index.php?topic=42667.msg1663587#msg1663587)
-
This would greatly increase the turnaround time on the booster and ultimately be counterproductive to the long term launch cadence.
I don't disagree on any of those points.
My message was simply to address JRTI being able to leave the LZ and get back in time for another Starlink launch on the 27th.
Clearly, the obvious answer is going to be, delay from the 27th.
-
This would greatly increase the turnaround time on the booster and ultimately be counterproductive to the long term launch cadence.
I don't disagree on any of those points.
My message was simply to address JRTI being able to leave the LZ and get back in time for another Starlink launch on the 27th.
Clearly, the obvious answer is going to be, delay from the 27th.
Agree, it will likely be delayed a few days.
LOL, maybe one of the first jobs for the new platforms is to just sit on the starlink LZ and catch F9's and off load multiples of them horizontally onto a ASDS for return.
-
There is quite large window for possible delay of Starlink v1.0-L17 mission between 27 Jan to 03 Feb according to issued NOTAM in Melbourne and Mauritius FIR for Stage2 debris reentry.
Such reentry area correspond again for double Stage2 burn with circular deploying orbit.
FIMM-FIR
NOTAM #: A0010/21 Class: International Status: Active Issue Date UTC: 01/21/2021 1119 Start Date UTC: 01/27/2021 1522 End Date UTC: 02/03/2021 1344
A0010/21 NOTAMN
Q) FIMM/QRALW/IV/NBO/W/000/999/2530S06515E999
A) FIMM
B) 2101271522 C) 2102031344
D) ON 27 JAN 21 FM 1522 AND 1615
ON 28 JAN 21 BTN 1501 AND 1554
ON 29 JAN 21 BTN 1439 AND 1532
ON 30 JAN 21 BTN 1418 AND 1511
ON 31 JAN 21 BTN 1356 AND 1449
ON 01 FEB 21 BTN 1335 AND 1428
ON 02 FEB 21 BTN 1313 AND 1406
ON 03 FEB 21 BTN 1251 AND 1344
E) ALTITUDE RESERVATION FOR HAZARDOUS OPERATIONS FROM SFC
TO UNL FOR ATMOSPHERIC REENTRY AND SPLASHDOWN OF LAUNCH VEHICLE
UPPER STAGE WI AN AREA BOUNDED BY FLW COORD:
2943S 06007E, 2455S 06427E, 3845S 08430E, 4512S 09945E,
4946S 11913E, 5042S 13819E, 4850S 15644E, 5146S 15808E
5442S 14832E, 5620S 13103E, 5552S 10750E, 4911S 08505E
3432S 06413E, 2943S 06007E
F) SFC G) UNL
-
JRTI and Hawk are still at the LZ, so this pretty much guarantees the 27th is not happening.
https://twitter.com/julia_bergeron/status/1352281814681980929
-
https://nextspaceflight.com/launches/details/2672
Next SpaceFlight is now confirming B1049.8 from LC-39A.
-
Map of NOTMAR Launch Hazard Areas of Starlink v1.0-L17 (https://www.google.com/maps/d/viewer?hl=en&mid=1CCc2GEEGG08j6fMUrkBEbDA5QFscr2bD&ll=30.749966946666923%2C-76.42617895925308&z=7) mission from LC-39A, valid for primary launch day 27 Jan in window between 13:13-14:31 UTC, backup 28-Jan to 03 Feb.
Hazard areas are identical to previous Starlink mission. Droneship landing on usual location.
221003Z JAN 21
NAVAREA IV 67/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
271313Z TO 271431Z JAN, ALTERNATE
281252Z TO 281410Z, 291230Z TO 291348Z,
301209Z TO 301327Z, 311147Z TO 311305Z JAN,
011126Z TO 011244Z, 021104Z TO 021222Z AND
031042Z TO 031200Z FEB IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL THIS MSG 031300Z FEB 21.
220950Z JAN 21
HYDROPAC 296/21(61,75,76).
SOUTHERN INDIAN OCEAN.
SOUTHEASTERN INDIAN OCEAN.
DNC 03, DNC 04, DNC 05.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
271522Z TO 271615Z JAN, ALTERNATE
281501Z TO 281554Z, 291439Z TO 291532Z,
301418Z TO 301511Z, 311356Z TO 311449Z JAN,
011335Z TO 011428Z, 021313Z TO 021406Z AND
031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL THIS MSG 031444Z FEB 21.
-
Launch is postponed to 29 January.
222106Z JAN 21
NAVAREA IV 70/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
291230Z TO 291348Z, ALTERNATE
301209Z TO 301327Z, 311147Z TO 311305Z JAN,
011126Z TO 011244Z, 021104Z TO 021222Z AND
031042Z TO 031200Z FEB IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 67/21.
3. CANCEL THIS MSG 031300Z FEB 21.
222042Z JAN 21
HYDROPAC 307/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
291230Z TO 291348Z JAN, ALTERNATE
301418Z TO 301511Z, 311356Z TO 311449Z JAN,
011335Z TO 011428Z, 021313Z TO 021406Z AND
031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 296/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
The Space Debris notice has been updated to fix the timeframe for the 29th.
231026Z JAN 21
HYDROPAC 312/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
291439Z TO 291532Z JAN, ALTERNATE
301418Z TO 301511Z, 311356Z TO 311449Z JAN,
011335Z TO 011428Z, 021313Z TO 021406Z AND
031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 307/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
Cross-post; confirmation re: launch date, approximate time of date, and location; my bold:
http://www.launchphotography.com/Launch_Viewing_Guide.html
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the eighteenth Starlink batch from pad 39A on January 29 at around 8am EST. Then, a Falcon 9 will launch the nineteenth Starlink batch from pad 40 on February TBA. A Falcon 9 will launch the twentieth Starlink batch on February TBA. Upcoming launches include multiple Starlink missions on February TBA.
State of play on the Space Coast for the immediate future:
Scheduled:
Date - Satellite(s) - Rocket - Launch Site - Time (UTC)
2021
February 4 early February - Starlink flight 18 19 (x60) [v1.0 L18] - Falcon 9-107 108 (1059.6 1060.5 S) - Canaveral SLC-40 / Kennedy LC-39A - 06:19
(Starlink: launch 20-22 minutes earlier/day)
February 16 mid NET 11 12 14 15 - Starlink flight 19 20 (x60) [v1.0 L19] - Falcon 9-108 109 (1059.6 S) - Canaveral SLC-40 / Kennedy LC-39A Canaveral SLC-40 - 03:59 ~06:00 05:47 05:25 04:42 04:20 04:21
(Starlink: launch 20-22 minutes earlier/day)
March 4 January late 27 29 30 31 February 1 early 2 3 4 5 7 mid 16 17 NET 19 TBD 26 March 1 NET 2 3 - Starlink flight 20 19 18 (x60) [v1.0 L17] - Falcon 9-109 108 107 (B1049.8 S) - Kennedy LC-39A - 08:24 or 10:42 ~13:00 12:24 12:02 11:41 ~11:00 11:19 10:57 10:36 10:14 09:31 ~06:00-08:00 06:17 05:55 05:12 TBD ~03:00 01:37 01:15 00:53
(Starlink: launch 20-22 minutes earlier/day)
March 8 February or March very late February NET February 25 - Starlink flight 21 (x60) [v1.0 L20] - Falcon 9-110 (1051.9 or 1058.6 S) - Canaveral SLC-40 / Kennedy LC-39A - 03:41 ~07:30 ~03:30 ~03:40
(Starlink: launch 20-22 minutes earlier/day)
Mid? March very late February? - Starlink flight 22 (x60) [v1.0 L21] - Falcon 9-111 (1058.6 or 1051.9? S) - Kennedy LC-39A / Canaveral SLC-40?
(Starlink: launch 20-22 minutes earlier/day)
NET March Q2 - Starlink flight 23 (x60) [v1.0 L22] - Falcon 9-112 (S) - Kennedy LC-39A / Canaveral SLC-40
(Starlink: launch 20-22 minutes earlier/day)
NET March Q2 - Starlink flight 24 (x60) [v1.0 L23] - Falcon 9-113 (S) - Kennedy LC-39A / Canaveral SLC-40
(Starlink: launch 20-22 minutes earlier/day)
NET April 20 - USCV-2: Dragon v2 Crew 2 - Falcon 9 (B1061.2 S) - Kennedy LC-39A - 09:00-10:30 09:00-10:00
(ISS flights: launch 22-26 minutes earlier/day)
May March 25 29 NET April 2 - CST-100 Starliner (unmanned test) (Boe-OFT 2) - Atlas V N22 (AV-082) - Canaveral SLC-41 - TBD daytime ~10:00-11:00 ~21:00 ~18:00
(ISS flights: launch 22-26 minutes earlier/day)
Mid-year February 26 Q2 - STP-3: STPSat-6, LDPE-1, small satellite (x6) - Atlas V 551 - Canaveral SLC-41
Changes on January 8th
Changes on January 20th
Changes on January 22th
Changes on January 24th
Changes on January 25th
Changes on January 26th
Changes on January 28th
Changes on January 30th
Changes on January 31st
Changes on February 1st
Changes on February 2nd
Changes on February 3rd
Changes on February 4th
Changes on February 5th
Changes on February 9th
Changes on February 11th
Changes on February 12th
Changes on February 13th
Changes on February 15th
Changes on February 16th
Changes on February 17th
Changes on February 18th
Changes on February 19th
Changes on February 20th
Changes on February 22nd
Changes on February 23rd
Changes on March 1st
Changes on March 2nd
Changes on March 4th
zubenelgenubi
Apparently, we are in the midst of a Starlink-Launchapalooza!
EDIT February 2: Two Falcon 9 launches on February 4, pre-dawn EST!!!
-
If JRTI or OCISLY are unable to turn around and depart tonight or tomorrow, it's safe to assume Starlink-17 is going to slip. For reference, JRTI and its tug left Port Canaveral on the evening of Jan 13 when Starlink-16 was still scheduled around 8am Jan 17, so we're likely already into the cutting-it-close zone with JRTI still in port this evening.
-
Postponed to January 30 per the NGA:
261506Z JAN 21
NAVAREA IV 80/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
301209Z TO 301327Z, ALTERNATE
311147Z TO 311305Z JAN,011126Z TO 011244Z,
021104Z TO 021222Z AND 031042Z TO 031200Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 70/21.
3. CANCEL THIS MSG 031300Z FEB 21.
261523Z JAN 21
HYDROPAC 341/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
301418Z TO 301511Z, JAN, ALTERNATE
311356Z TO 311449Z JAN, 011335Z TO 011428Z,
021313Z TO 021406Z AND 031251Z TO 031344Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 312/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
https://twitter.com/SpaceXFleet/status/1354125656641183750
-
Ben Cooper and NextSpaceFlight now reporting launch time of 7:24 am.
Edit: SpaceFlight Now confirms.
https://spaceflightnow.com/launch-schedule/
-
Lots of activity on JRTI, looks like they are trying for a departure tonight.
-
90% GO for launch on Primary, 80% on Backup. Moderate risk from booster recovery weather.
-
https://twitter.com/julia_bergeron/status/1354470292521951233
-
https://twitter.com/SpaceXFleet/status/1354420670873161740
-
JRTI is en route. Gonna be a challenge to reach the LZ in time with more than a few hours to spare.
https://twitter.com/SpaceXFleet/status/1354569594971762694
-
https://twitter.com/NASASpaceflight/status/1354572888507035649
-
https://twitter.com/SpaceXFleet/status/1354719825466155009
-
No major changes, still 90% GO for launch day
-
Postponed for one day more to January 31
281713Z JAN 21
NAVAREA IV 86/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
311147Z TO 311305Z JAN, ALTERNATE
011126Z TO 011244Z, 021104Z TO 021222Z
AND 031042Z TO 031200Z FEB IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 80/21.
3. CANCEL THIS MSG 031300Z FEB 21.
281727Z JAN 21
HYDROPAC 367/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
311356Z TO 311449Z JAN, ALTERNATE
011335Z TO 011428Z, 021313Z TO 021406Z
AND 031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 341/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
If it flies on the 31st it will be about 10 minutes before sunrise.
-
https://spaceflightnow.com/2021/01/28/falcon-9-rocket-arrives-on-pad-39a-for-sunrise-starlink-launch-this-weekend/
There is an instantaneous launch opportunity at 7:02 a.m. EST (1202 GMT), about 10 minutes before sunrise Sunday.
Possible static fire as well.
-
https://twitter.com/spaceflightnow/status/1355034924168962048
SpaceX has raised a Falcon 9 rocket vertical on pad 39A at the Kennedy Space Center in preparation for a possible test-firing Friday, followed by a launch set for Sunday with the next 60 Starlink internet satellites.
Read more: spaceflightnow.com/2021/01/28/fal…
-
L-2 launch weather for Sunday remains 80% GO
-
https://twitter.com/spaceflightnow/status/1355169675076907008
SpaceX appears to have aborted a Falcon 9 static fire test on pad 39A this morning after loading propellants into the rocket.
The launcher is packed with around 60 more Starlink internet satellites for liftoff in a couple of days.
spaceflightnow.com/2021/01/29/fal…
-
https://twitter.com/SpaceXFleet/status/1355238375620546571
-
If it flies on the 31st it will be about 10 minutes before sunrise.
How many days can this be delayed before the staging at altitude is in the pre-dawn dark and "the show" is diminished?
An exact answer lies at the intersection of orbital mechanics and spherical trigonometry, a pretty rough neighborhood. :P
-
https://twitter.com/spacexfleet/status/1355295484676550659
Ms. Tree and Ms. Chief will head direct to the Port of Morehead City, NC, to wait for a date for Starlink, which seems to be delayed.
Fairing Catcher departure suggests the delay won't be too long.
-
[email protected]
10:27 PM (16 minutes ago)
to NAVSAFETY1
300318Z JAN 21
NAVAREA IV 92/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
011126Z TO 011244Z JAN, ALTERNATE
021104Z TO 021222Z, AND 031042Z TO 031200Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 86/21.
3. CANCEL THIS MSG 031300Z FEB 21.
-
Ben Cooper is reporting a launch time of 6:41 am EST.
-
The new Space Debris notice has also now been issued:
300338Z JAN 21
HYDROPAC 388/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
011335Z TO 011428Z FEB, ALTERNATE
021313Z TO 021406Z, AND
031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 367/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
Ben Cooper is reporting a launch time of 6:41 am EST.
That should be ~30 minutes before sunrise at the Cape and perhaps a few minutes before "first light" (astronomical twilight?).
The rocket could enter sunlight during the first stage burn at something like 50-60 km altitude.
(A precise answer is at the intersection of orbital mechanics and spherical trigonometry, a tough neighborhood. :P )
Could make for a nice display at staging.
-
SpaceFlight Now has confirmed the new time.
https://spaceflightnow.com/launch-schedule/
-
Falcon 9 is now back to horizontal, based on Spaceflight Now webcam (members only).
-
L-2 weather forecast is 60% GO
-
If the booster recovery weather doesn’t improve, it could get bumped for a couple more days.
-
If the booster recovery weather doesn’t improve, it could get bumped for a couple more days.
It's pretty much guaranteed, unless SpaceX decided to expend the booster. Neither ASDS is currently on its way to the landing zone, so Feb 1 isn't feasible anymore.
-
http://www.launchphotography.com/Launch_Viewing_Guide.html
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the eighteenth Starlink batch from pad 39A on February at ~6am EST. Launch times for Starlink launches get around 20-22 miutes earlier each day. Then, a Falcon 9 will launch the nineteenth Starlink batch from pad 40 on February 4 earliest at 1:19am EST.
-
Falcon 9 is now back to horizontal, based on Spaceflight Now webcam (members only).
From this, I deduce no Static Fire today.
Edit LV returning to the vertical.
***
http://www.launchphotography.com/Launch_Viewing_Guide.html
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the eighteenth Starlink batch from pad 39A on February at ~6am EST. Launch times for Starlink launches get around 20-22 miutes earlier each day.
February 1: 11:41 UTC,
February 2: ~11:20 UTC, rounding down to ~11:00 UTC as in his post,
February 3: ~11:00 UTC,
February 4: ~10:40 UTC, rounding up to ~11:00 UTC as in his post,
and so on.
-
SF is still planned for today, although the rocket remains horizontal (webcam here (https://www.youtube.com/watch?v=9V34LaCXPwM&feature=youtu.be)), so I don't know if they can still make it.
https://twitter.com/EmreKelly/status/1355577700803612682
-
They really need to fix that 😂
-
https://www.youtube.com/watch?v=9V34LaCXPwM
It’s going up!
-
https://twitter.com/spacexfleet/status/1355669191714603008
Update on Just Read the Instructions.
The droneship has changed direction and is no longer returning to Cape Canaveral.
JRTI is now heading back towards the Starlink LZ. (Check out the loop!)
-
Conditions are forecasted to improve enough that a Feb 1 launch attempt is feasible.
Ben Cooper and Next SpaceFlight have updated their calendars.
-
Any news on when SpaceX will do the static fire for the Falcon 9 launching the Starlink v1.0 L17 mission?
-
https://spaceflightnow.com/2021/01/29/falcon-9-starlink-v10-l17-mission-status-center/
SpaceX has delayed the launch of the Falcon 9 with another batch of 60 Starlink satellites until Monday, following an aborted static fire on Friday. It will make another attempt to static fire the rocket's first stage on Sunday afternoon.
-
https://twitter.com/ncspaceops/status/1355877786297237509
.@SpaceX fairing catching sisters GO Ms Chief & GO Ms Tree arrived in the Port of Morehead City overnight. They’ll be hanging out here until dispatched to support the forthcoming #Starlink mission(s) @SpaceXFleet #spacex #spacexfleet 👯♀️ #nc #NorthCarolina #carteretcounty
-
https://twitter.com/spacetfrs/status/1355890083770097664?s=21
Feb 1st may no longer be on the table.
-
Another postponement to Feb 02 11:19 UTC according to NOTMAR message.
311437Z JAN 21
NAVAREA IV 95/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
021104Z TO 021222Z FEB, ALTERNATE
031042Z TO 031200Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 92/21.
3. CANCEL THIS MSG 031300Z FEB 21.
311452Z JAN 21
HYDROPAC 396/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
021313Z TO 021406Z FEB, ALTERNATE
031251Z TO 031344Z FEB IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 388/21.
3. CANCEL THIS MSG 031444Z FEB 21.
-
With static firing scheduled for this afternoon, is launch still set for Monday morning (Feb. 1) or has it moved out to Tuesday?
-
L-2 launch weather forecast only 40% GO & booster recovery difficult (70% GO next day but still difficult booster recovery)
-
Static fire just now.
-
https://twitter.com/emrekelly/status/1355954863922933763
Test fire at 39A! If all looks well, this mission (18th Starlink) is on for no earlier than 0619 ET Tuesday, Feb. 2.
-
18th Starlink: SpaceX test fires Falcon 9 at Kennedy Space Center in Florida
https://youtu.be/TEBCEjnDKnM
-
https://twitter.com/spacexfleet/status/1356007758911438848
Overdue recovery fleet status map!
Both active droneships are en-route to the Starlink LZ as SpaceX prepares for two Falcon 9 missions in one week.
-
https://twitter.com/SpaceX/status/1356063929462472709
Static fire test complete – targeting Tuesday, February 2 at 6:19 a.m. EST for launch of 60 Starlink satellites from LC-39A; team is keeping an eye on launch and recovery weather
-
L-1 launch weather forecast, still only 40% GO & high risk booster recovery (24 hour delay has now dropped to 60% GO)
-
https://twitter.com/spacex/status/1356279692202897408
Due to rough weather in the recovery area, now targeting no earlier than Wednesday, February 3 at 5:57 a.m. EST for launch of Starlink
-
Due to rough weather in the recovery area, now targeting no earlier than Wednesday, February 3 at 5:57 a.m. EST for launch of Starlink.
Cross-post; interesting development given Ben Cooper's update from several hours earlier:
http://www.launchphotography.com/Launch_Viewing_Guide.html
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the eighteenth Starlink batch from pad 39A on February TBD around 5-6am EST. Launch times for Starlink launches get around 20-22 minutes earlier each day. Then, a Falcon 9 will launch the nineteenth Starlink batch from pad 40 on February 4 earliest at 1:19am EST.
-
The 45th Weather Squadron is predicting that the "high" booster recovery weather risk will persist for Wednesday morning's window, but will improve during the day and only be "moderate" by L18's Thursday morning window (T-0 of 01:19L).
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
That would be quite a feat, but would the interval be too short for:
* The Range?
* Hawthorne mission control?
* The Cape pad crews?
* The booster recovery crews (who would meet sunrise with two boosters in need of securing)?
* The fairing recovery crews (who would have to recover the first set in the dark to be prepared for the second set)?
-
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
That would be quite a feat, but would the interval be too short for:
* The Range?
* Hawthorne mission control?
* The Cape pad crews?
* The booster recovery crews (who would meet sunrise with two boosters in need of securing)?
* The fairing recovery crews (who would have to recover the first set in the dark to be prepared for the second set)?
There is a chance of L18 launching before L17. It all depends on how the weather plays out.
Four hours is doable for the Eastern Range with the same vehicle type due to AFTS.
Hawthorne shouldn’t have any issues, as there is a sizeable gap between missions.
The launches are on different pads, so no issue there if they have sufficient personnel.
They might need to send a second support ship with additional personnel, depending on the timeline.
Fairing recovery shouldn’t be a problem, as they’ve demonstrated rapid recovery from the water from a single ship.
-
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
I don't think so. The launches are numered chronolgically. The CC launch may go before the KSC launch, but then the CC launch will be called L17 and this one here will become L18.
-
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
I don't think so. The launches are numered chronolgically. The CC launch may go before the KSC launch, but then the CC launch will be called L17 and this one here will become L18.
I don't think anyone will really care if 18 flies before 17. I doubt the flights get renamed/numbered. Maybe in media reporting only.
Eventually this will happen because a satellite or rocket will have some issue and the next flight will jump it. SpaceX won't care, just get those data birds up there.
-
NOTMAR update with postponement to NET Feb 03, alternatively Feb 04 to Feb 09.
Incorrect times of launch window, which are same as S2 reentry window now.
011824Z FEB 21
NAVAREA IV 98/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
031251Z TO 031344Z FEB, ALTERNATE
041230Z TO 041323Z, 051208Z TO 051301Z,
061147Z TO 061240Z, 071125Z TO 071218Z,
081104Z TO 081157Z AND 091042Z TO 091135Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 95/21.
3. CANCEL THIS MSG 091235Z FEB 21
011840Z FEB 21
HYDROPAC 404/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
031251Z TO 031344Z FEB, ALTERNATE
041230Z TO 041323Z, 051208Z TO 051301Z,
061147Z TO 061240Z, 071125Z TO 071218Z,
081104Z TO 081157Z AND 091042Z TO 091135Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 396/21.
3. CANCEL THIS MSG 091235Z FEB 21.
-
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
I don't think so. The launches are numered chronolgically. The CC launch may go before the KSC launch, but then the CC launch will be called L17 and this one here will become L18.
No. The missions are named L17 and L18, regardless of what order they fly.
-
Is there *any* chance we could see the order reversed, and have L18 fly just over four hours before L17?
I don't think so. The launches are numered chronolgically. The CC launch may go before the KSC launch, but then the CC launch will be called L17 and this one here will become L18.
No. The missions are named L17 and L18, regardless of what order they fly.
Yep. The references are in a hundred places and they can't change them all. Changing names would create confusion throughout the land. Chaos would rule.
-
No. The missions are named L17 and L18, regardless of what order they fly.
Yeah, probably it's going to stay L17 and L18 on the range.
On the other hand, I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly. And we'll see what they send in the emails to the space tracking community (e.g. T.S. Kelso called the previous mission Starlink-18 on CelesTrak and SpaceX had specifically told them to use this very numbering in some previous emails).
-
On the other hand, I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly.
Exactly, which is why I want the flight from SLC-40 to go first. We'd have L18, the eighteenth Starlink mission.
-
I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly. And we'll see what they send in the emails to the space tracking community (e.g. T.S. Kelso called the previous mission Starlink-18 on CelesTrak and SpaceX had specifically told them to use this very numbering in some previous emails).
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
-
I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly. And we'll see what they send in the emails to the space tracking community (e.g. T.S. Kelso called the previous mission Starlink-18 on CelesTrak and SpaceX had specifically told them to use this very numbering in some previous emails).
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
That was the L2 launch of v0.9 sats. the L numbers for these are for v1.x sats.
-
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
That was the L2 launch of v0.9 sats. the L numbers for these are for v1.x sats.
The Starlink satellites on Transporter-1 were v1.0, it was the lasers that were v0.9. They’re not going to go back on to an obsolete design and put lasers on them.
-
Unless the laser gear is taking up the space the ka band gear used.
It's not
-
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
That was the L2 launch of v0.9 sats. the L numbers for these are for v1.x sats.
The Starlink satellites on Transporter-1 were v1.0, it was the lasers that were v0.9. They’re not going to go back on to an obsolete design and put lasers on them.
not according to Elon and SpaceX. yes it is a 1.x bus but Elon said that all of the polar sats to be launched this year including those flown on Transporter-1 are v0.9 for payloads (due to being experimental and not for operational customer use).
-
Here's the corrected Rocket Launching notice:
012018Z FEB 21
NAVAREA IV 100/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
031042Z TO 031200Z FEB, ALTERNATE
041021Z TO 041139Z, 050959Z TO 051117Z,
060938Z TO 061056Z, 070916Z TO 071034Z,
080855Z TO 081013Z AND 090833Z TO 090951Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 98/21.
3. CANCEL THIS MSG 091051Z FEB 21.
-
I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly. And we'll see what they send in the emails to the space tracking community (e.g. T.S. Kelso called the previous mission Starlink-18 on CelesTrak and SpaceX had specifically told them to use this very numbering in some previous emails).
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
That was the L2 launch of v0.9 sats. the L numbers for these are for v1.x sats.
You’re not understanding what I wrote. I’m stating the possibility that SpaceX will count the satellites from Transporter-1 as a Starlink mission, the same way they counted the original v0.9 as a Starlink mission
It doesn’t affect the Launch numbering system at all.
-
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
That was the L2 launch of v0.9 sats. the L numbers for these are for v1.x sats.
The Starlink satellites on Transporter-1 were v1.0, it was the lasers that were v0.9. They’re not going to go back on to an obsolete design and put lasers on them.
not according to Elon and SpaceX. yes it is a 1.x bus but Elon said that all of the polar sats to be launched this year including those flown on Transporter-1 are v0.9 for payloads (due to being experimental and not for operational customer use).
Crosspost:
https://twitter.com/elonmusk/status/1353566586985013254?s=19
https://twitter.com/elonmusk/status/1353574169288396800?s=19
The ISL are v0.9, which is different from the satellite design being v0.9 (which was the first batch of 60 test Starlinks).
-
not according to Elon and SpaceX. yes it is a 1.x bus but Elon said that all of the polar sats to be launched this year including those flown on Transporter-1 are v0.9 for payloads (due to being experimental and not for operational customer use).
He did not say the sats are not for operational customer use.
-
https://twitter.com/SpaceXFleet/status/1356397711357050883
-
Jeepers. The intensity of the mission numbering debate above could come straight out of an episode of Big Bang Theory😀.
-
https://twitter.com/spacexfleet/status/1356528907479097347
Droneship support ship GO Quest has departed from the Port of Morehead City towards the Starlink LZ.
A great sign that SpaceX is still working towards Falcon 9 liftoff on Wednesday.
-
I'm pretty sure that on their website SpaceX will call these missions "eighteenth Starlink mission" and "nineteenth Starlink mission" in whichever order they fly. And we'll see what they send in the emails to the space tracking community (e.g. T.S. Kelso called the previous mission Starlink-18 on CelesTrak and SpaceX had specifically told them to use this very numbering in some previous emails).
It’s possible that SpaceX will refer to this as the 19th Starlink mission, counting the 10 from Transporter-1. We will get official word soon.
There is not the slightest chance in the world that Space will add one to its count because of Transporter-1!
-
50% GO for tomorrow, +90% GO on backup day. Booster recovery risk is still high, vs moderate/low on backup day.
-
[email protected]
11:32 AM (17 minutes ago)
to NAVSAFETY1
021628Z FEB 21
NAVAREA IV 103/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
041021Z TO 041139Z FEB, ALTERNATE
050959Z TO 051117Z, 060938Z TO 061056Z,
070916Z TO 071034Z, 080855Z TO 081013Z
AND 090833Z TO 090951Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 100/21.
3. CANCEL THIS MSG 091051Z FEB 21.
-
According to Ben Cooper, this launch is now planned for "February 4 at 5:36am EST".
The next (or maybe previous :) ) Starlink launch is now planned for "February 4 or 5 earliest at 1:19am or ~12:58am EST".
Can they launch two missions within a little more than 4 hours according to what we know? I doubt it.
-
The corresponding Space Debris notice:
021640Z FEB 21
HYDROPAC 408/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
041230Z TO 041323Z FEB, ALTERNATE
051208Z TO 051301Z, 061147Z TO 061240Z,
071125Z TO 071218Z, 081104Z TO 081157Z
AND 091042Z TO 091135Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 404/21.
3. CANCEL THIS MSG 091235Z FEB 21.
-
Can they launch two missions within a little more than 4 hours according to what we know? I doubt it.
Yes, according to previous statements from the Eastern Range. AFTS makes it possible.
-
L-2 weather forecast for Feb 4 is up. >90% GO for the primary day, 70% GO for the backup. Booster recovery weather risk is Mod-Low and Moderate, respectively.
-
Just wanted to note that this is the seventh time that the launch date has changed since originally announced.
Wonder if that’s a record? 😂
-
https://twitter.com/SpaceX/status/1356807508975845381?s=19
BTW how do we know the "L17" & "L18" designators are assigned to specific rockets/satellites and not sequential?
-
https://twitter.com/SpaceX/status/1356807508975845381?s=19
BTW how do we know the "L17" & "L18" designators are assigned to specific rockets/satellites and not sequential?
Those are the mission names they provide to the range. They are on all of the planning documents (weather forecasts, hazard areas).
-
Crosspost:
https://twitter.com/spacexfleet/status/1356891369860644864
Departure!
Ms. Tree and Ms. Chief are outbound from the Port of Morehead City for the SpaceX Starlink double-header.
-
L-1 launch weather forecast, 90+ % GO
-
Another postponement to Feb 05 10:14 UTC (22 minutes earlier) based on NOTMAR update.
031558Z FEB 21
NAVAREA IV 105/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
050959Z TO 051117Z FEB, ALTERNATE
060938Z TO 061056Z, 070916Z TO 071034Z,
080855Z TO 081013Z AND 090833Z TO 090951Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 103/21.
3. CANCEL THIS MSG 091051Z FEB 21.
031609Z FEB 21
HYDROPAC 414/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
051208Z TO 051301Z FEB, ALTERNATE
061147Z TO 061240Z, 071125Z TO 071218Z,
081104Z TO 081157Z AND 091042Z TO 091135Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 408/21.
3. CANCEL THIS MSG 091235Z FEB 21.
-
Ben Cooper and Next SpaceFlight now confirming date change.
-
Someone forgot to tell 45th media team ...
twitter.com/45thspacewing/status/1357041906979639297
The 45th Space Wing has approved the launch of two SpaceX Falcon 9 missions carrying hundreds of Starlink satellites. Working extremely close with our FAA, USN, and international partners, Starlink L-17 and Starlink L-18 are approved to launch at 0536L and 0119L, respectively.
https://twitter.com/45thspacewing/status/1357041908355395585
This is the first time since 11 November 1966 that two launches will lift off from the Eastern Range on the same day. Those previous missions were Gemini 12 and Atlas Agena which lifted off 99 minutes apart from each other. The two Falcons will lift off less than 5 hours apart.
-
Someone forgot to tell 45th media team ...
Yeah, I'm going with the NOTMAR and NOTAM.
-
Liked just for the fun fact!
This is the first time since 11 November 1966 that two launches will lift off from the Eastern Range on the same day. Those previous missions were Gemini 12 and Atlas Agena which lifted off 99 minutes apart from each other. The two Falcons will lift off less than 5 hours apart.
-
New L-2 weather forecast for launch on the 5th, released at 2 PM Eastern: 70% GO (with moderate recovery risk) for the 5th , 70% GO (with "high-moderate" recovery risk) for the 6th.
-
https://twitter.com/spacex/status/1357061342876766208
To allow additional time for pre-launch checks, now targeting Friday, February 5 at 5:14 a.m. EST for launch of Starlink from LC-39A
-
https://twitter.com/spacex/status/1357061342876766208
To allow additional time for pre-launch checks, now targeting Friday, February 5 at 5:14 a.m. EST for launch of Starlink from LC-39A
Will it now be redesignated as "L18"?
-
Updated launch weather forecast - now L-2 and 70% GO
-
Don’t think anything has changed from the one posted an hour ago?
-
Jeepers. The intensity of the mission numbering debate above could come straight out of an episode of Big Bang Theory😀.
Heh. SpaceX is trolling us by not publishing any hint on the launch number for L18. :D
SpaceX is targeting Thursday, February 4 for launch of 60 Starlink satellites from Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station in Florida.
https://www.spacex.com/launches/
For comparison, this (https://web.archive.org/web/20210120113025/https://www.spacex.com/launches/) is what they wrote on L16:
SpaceX is targeting Wednesday, January 20 for its seventeenth Starlink mission, which will launch 60 Starlink satellites from Launch Complex 39A (LC-39A) at Kennedy Space Center.
-
https://twitter.com/Cygnusx112/status/1357067888646053890
Not often we get to see TWO Falcon 9’s vertical at the same time. First launch in a few hours off of LC-40 at 1:19am L. LC-39A is Friday at 5:14am L.
Left Tweet image is of SLC-40; right Tweet image is of LC-39A.
The Falcon for this thread's launch coverage is on LC-39A.
-
https://twitter.com/TSKelso/status/1357220349771874307
-
Nice shot from SpaceX L18 webcast
-
L-1 launch weather forecast, still 70% GO
-
Launch now Sunday at 4:31 am local.
-
https://twitter.com/spacexfleet/status/1357432301022556161
This explains why Ms. Tree and Ms. Chief are returning to Port Canaveral.
Plenty of time to unload and reset from L18 and get back out for L17, as required.
-
Launch now Sunday at 4:31 am local.
Delayed for the ninth time since the original Jan 27 date.
-
The new Rocket Launching notice from the NGA hasn't arrived yet, but here is the new Space Debris notice:
042055Z FEB 21
HYDROPAC 428/21(GEN).
INDIAN OCEAN.
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
071125Z TO 071218Z FEB, ALTERNATE
081104Z TO 081157Z AND 091042Z TO 091135Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 414/21.
3. CANCEL THIS MSG 091235Z FEB 21.
-
And here's the new Rocket Launching notice:
042040Z FEB 21
NAVAREA IV 110/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
070916Z TO 071034Z FEB, ALTERNATE
080855Z TO 081013Z AND 090833Z TO 090951Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 105/21.
3. CANCEL THIS MSG 091051Z FEB 21.
-
Launch now Sunday at 4:31 am local.
Delayed for the ninth time since the original Jan 27 date.
Ouch, this one really doesn't want to go anywhere in a hurry does it.
Now we know why the fairing recovery ships are coming back. They can make that turn and be about out.
Soon we'll be wondering if 19 goes before 17.
-
https://twitter.com/spacex/status/1357441415454674944
Targeting no earlier than February 7 at 4:31 a.m. EST for launch of Starlink from 39A, pending Range availability, to allow time for pre-launch checks and recovery vessels to get on station after offloading fairing halves from previous mission; team is monitoring recovery weather
-
Launch now Sunday at 4:31 am local.
Delayed for the ninth time since the original Jan 27 date.
Ouch, this one really doesn't want to go anywhere in a hurry does it.
Now we know why the fairing recovery ships are coming back. They can make that turn and be about out.
Soon we'll be wondering if 19 goes before 17.
Nine delays? That's nothing! Wasn't a Titan 23G launch delayed by years? Big booster Titans used to sit in Florida for that long. There were a few Deltas too that suffered long delays for various reasons, more often than not due to payload issues. And Shuttle. Oh boy, I remember a few of those campaigns. 17 will go soon enough, and before 19 unless it suffers more hardware problems.
- Ed Kyle
-
https://spaceflightnow.com/titan/g9/031012saga.html
DMSP-5D3 F16, which was the last Titan II(23)G payload, was delayed for 33 months.
First countdown was January 2001, and it took off in October 2003. It was destacked twice to let two other missions launch (NOAA-M and Coriolis).
-
Has any reason been given for this new delay? Could it be some non-technical reason, like wanting to have a launch on the same day that Shift4 Payments’ commercial runs during the Super Bowl?
-
Has any reason been given for this new delay? Could it be some non-technical reason, like wanting to have a launch on the same day that Shift4 Payments’ commercial runs during the Super Bowl?
Three posts up:
Targeting no earlier than February 7 at 4:31 a.m. EST for launch of Starlink from 39A, pending Range availability, to allow time for pre-launch checks and recovery vessels to get on station after offloading fairing halves from previous mission; team is monitoring recovery weather
-
Has any reason been given for this new delay? Could it be some non-technical reason, like wanting to have a launch on the same day that Shift4 Payments’ commercial runs during the Super Bowl?
Three posts up:
Targeting no earlier than February 7 at 4:31 a.m. EST for launch of Starlink from 39A, pending Range availability, to allow time for pre-launch checks and recovery vessels to get on station after offloading fairing halves from previous mission; team is monitoring recovery weather
That's the result of the delay, not the cause.
-
Thanks Jansen — I blew right by that post without it registering.
Still, I’m curious. What has happened that changed a 4+ hour launch gap into a 4-day gap? Unless I blew past another post without reading it correctly, the weather and vehicle/payload looked good to go.
-
Thanks Jansen — I blew right by that post without it registering.
Still, I’m curious. What has happened that changed a 4+ hour launch gap into a 4-day gap? Unless I blew past another post without reading it correctly, the weather and vehicle/payload looked good to go.
If they're still talking about pre-launch checks then either the pad, vehicle, or payload isn't completely good to go.
-
Thanks Jansen — I blew right by that post without it registering.
Still, I’m curious. What has happened that changed a 4+ hour launch gap into a 4-day gap? Unless I blew past another post without reading it correctly, the weather and vehicle/payload looked good to go.
If they're still talking about pre-launch checks then either the pad, vehicle, or payload isn't completely good to go.
Consider the aborted static fire issue earlier, I suspect they are spending extra time on data analysis.
-
https://twitter.com/TSKelso/status/1357548377865506816
-
Launch is now TBD. NOT going on the 7th.
-
NOTMAR cancellation:
[email protected]
11:49 AM (1 hour ago)
to NAVSAFETY1
051638Z FEB 21
NAVAREA IV 112/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
CANCEL NAVAREA IV 110/21 AND THIS MSG.
-
https://twitter.com/spacex/status/1357785626561572864
Standing down from this weekend’s launch attempt of Starlink from LC-39A for additional inspections before flying one of our fleet-leading boosters, as the team continues to drive toward a separate Falcon 9 launch of Starlink from SLC-40 at the end of next week.
-
https://twitter.com/spacex/status/1357785626561572864
Standing down from this weekend’s launch attempt of Starlink from LC-39A for additional inspections before flying one of our fleet-leading boosters, as the team continues to drive toward a separate Falcon 9 launch of Starlink from SLC-40 at the end of next week.
Sounds a little like a troubling problem that has yet to be figured out as to what is causing it. Troubleshooting can be quick or sometimes extremely elusive. But also they have hinted at it being the booster but have not come out and said it is the booster.
-
https://twitter.com/SpaceXFleet/status/1357792135735615488
That JRTI is coming all the way back to Port Canaveral indicates a substantial delay.
-
That JRTI is coming all the way back to Port Canaveral indicates a substantial delay.
I’m hearing it might be a 4-10 day delay. Don’t know what would take that long. Engine swap?
-
That JRTI is coming all the way back to Port Canaveral indicates a substantial delay.
I’m hearing it might be a 4-10 day delay. Don’t know what would take that long. Engine swap?
Rumored that some problems with the 1st stage - 3 checks - 3 different issues.
-
Cross-post; my bold:
Ben Cooper's Launch Photography (http://www.launchphotography.com/Launch_Viewing_Guide.html), February 5 update:
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the nineteenth Starlink batch from
pad 40 on February 12 at 12:25am EST. The launch time for Starlink launches gets 20-22 minutes
earlier each day. A Falcon 9 will launch the twentieth Starlink batch from pad 39A on February TBD
at around 1-3am EST. Upcoming launches include more Starlink missions on February TBA. The
next Crew Dragon mission, Crew-2, carrying four astronauts to the space station from pad 39A, is
targeted for April 20, around 5 or 6am EDT.
-
Cross-post; my bold:
Ben Cooper's Launch Photography (http://www.launchphotography.com/Launch_Viewing_Guide.html), February 5 update:
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the nineteenth Starlink batch from
pad 40 on February 12 at 12:25am EST. The launch time for Starlink launches gets 20-22 minutes
earlier each day. A Falcon 9 will launch the twentieth Starlink batch from pad 39A on February TBD
at around 1-3am EST. Upcoming launches include more Starlink missions on February TBA. The
next Crew Dragon mission, Crew-2, carrying four astronauts to the space station from pad 39A, is
targeted for April 20, around 5 or 6am EDT.
If we assume that L17 is still headed to the same place and extrapolate from the 4:30 am NET for a Feb 7 launch, "1-3am" gives a spread of 4-10 days or Feb 11-17 for the next launch target. As an educated guess, the lower end of that range would mesh more with demating the rocket/payload to inspect stage(s) or Starlink satellites. Upper end would be better explained by a booster engine swap, upper stage replacement, or even Starlink satellite removal or replacement.
-
https://twitter.com/SpaceXFleet/status/1359124137617276928
-
Next launch date is now NET 16 Feb ~06:17 UTC, alternatively 17-22 Feb, according to new Stage2 re-entry NOTAMs messages in Melbourne and Mauritius FIR.
MELBOURNE (FIR/FIC/ACC/COM/MET)
NOTAM #: F0487/21 Class: International Status: Active Issue Date UTC: 02/10/2021 2048 Start Date UTC: 02/16/2021 0811 End Date UTC: 02/22/2021 0655
F0487/21 NOTAMN
Q) YMMM/QWMLW/IV/BO/W/000/999/5220S09818E999
A) YMMM
B) 2102160811 C) 2102220655
D) 2102160811 TO 2102160904
2102170749 TO 2102170842
2102180728 TO 2102180821
2102190706 TO 2102190759
2102200645 TO 2102200738
2102210623 TO 2102210716
2102220602 TO 2102220655
E) ROCKET LAUNCH WILL TAKE PLACE
FLW RECEIVED FM GOVERNMENT OF UNITED STATES OF AMERICA:
HAZARDOUS OPS WILL BE CONDUCTED FOR ATMOSPHERIC RE-ENTRY AND
SPLASHDOWN OF LAUNCH VEHICLE FALCON-9 STARLINK V1.0-L17 AND
PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS:
FM 2943S06007E
TO 2455S06427E
TO 3845S08430E
TO 4512S09945E
TO 4946S11913E
TO 5042S13819E
TO 4850S15644E
TO 5146S15808E
TO 5442S14832E
TO 5620S13103E
TO 5552S10750E
TO 4911S08505E
TO 3432S06413E TO BEGINNING
PRI RE-ENTRY 2102160811 TO 2102160904
F) SFC G) UNL
-
Any word as to what the 3 issues are on the booster? Would they change boosters at some point?
-
Spaceflight Now, Next Spaceflight, and Ben Cooper all confirming.
Launch time: 0617 GMT (1:17 a.m. EST)
Launch site: LC-39A, Kennedy Space Center, Florida
-
Here's the Rocket Launching NGA notice along with calculated launch times.
Primary Day = Tuesday, February 16 at ~06:17 UTC.
Backup Day #1 = Wednesday, February 17 at ~05:55 UTC.
Backup Day #2 = Thursday, February 18 at ~05:34 UTC.
Backup Day #3 = Friday, February 19 at ~05:12 UTC.
Backup Day #4 = Saturday, February 20 at ~04:51 UTC.
Backup Day #5 = Sunday, February 21 at ~04:29 UTC.
Backup Day #6 = Monday, February 22 at ~04:08 UTC.
111705Z FEB 21
NAVAREA IV 128/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
160602Z TO 160720Z FEB, ALTERNATE
170540Z TO 170658Z, 180519Z TO 180637Z,
190457Z TO 190615Z, 200436Z TO 200554Z,
210414Z TO 210532Z AND 220353Z TO 220511Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL THIS MSG 220611Z FEB 21.
Additionally, earlier today I received a Space Debris notice. It only lists two days instead of seven days and the location is different, however the times in those two days match the NOTAM that Raul posted above.
111026Z FEB 21
HYDROPAC 494/21(GEN).
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
160811Z TO 160904Z FEB, ALTERNATE
170749Z TO 170842Z FEB
IN AREA BOUND BY
27-18S 062-23E, 46-52S 090-17E,
53-10S 120-02E, 52-53S 144-25E,
50-16S 157-27E.
2. CANCEL THIS MSG 170942Z FEB 21.
-
Right after I posted the above comment, I got a new Space Debris with seven days canceling and replacing the two-day one shown above.
111748Z FEB 21
HYDROPAC 496/21(GEN).
WESTERN SOUTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
160811Z TO 160904Z FEB, ALTERNATE
170749Z TO 170842Z, 180728Z TO 180821Z,
190706Z TO 190759Z, 200645Z TO 200738Z,
210623Z TO 210716Z AND 220602Z TO 220655Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 494/21.
3. CANCEL THIS MSG 220755Z FEB 21.
-
https://twitter.com/spacexfleet/status/1360151074397704195
Just Read the Instructions droneship is about to depart Port Canaveral for a second attempt at the Starlink V1 L17 mission.
-
L-4 launch weather forecast is 60% GO
-
We now have a one-day slip to this launch, to Wednesday, February 17 at ~05:55 UTC.
130526Z FEB 21
NAVAREA IV 135/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
170540Z TO 170685Z FEB, ALTERNATE
180519Z TO 180637Z, 190457Z TO 190615Z,
200436Z TO 200554Z, 210414Z TO 210532Z,
AND 220353Z TO 220511Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 128/21.
3. CANCEL THIS MSG 220611Z FEB 21.
130546Z FEB 21
HYDROPAC 510/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
170749Z TO 170842Z FEB, ALTERNATE
180728Z TO 180821Z, 190706Z TO 190759Z,
200645Z TO 200738Z, 210623Z TO 210716Z AND
220602Z TO 220655Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 496/21.
3. CANCEL THIS MSG 220755Z FEB 21.
-
Ben Cooper confirming:
Falcon 9 will launch the twentieth Starlink batch from pad 39A on February 17 at 12:55am EST
-
L-3 launch weather forecast is 80% GO
-
https://twitter.com/TSKelso/status/1361135065380524033
-
L-2 weather forecast: 80% 'Go' for Feb 17, 50% 'Go' for Feb 18; booster recovery weather risk is moderate both days.
-
Ben Cooper confirming:
Falcon 9 will launch the twentieth Starlink batch from pad 39A on February 17 at 12:55am EST
I like the cookie analogy. This is the 17 batch of the v 1.0 Starlink satellites made. Just because they didn’t get put on the tray and served before the next batch was made and put out for use doesn’t take away from their heritage in the production line.
-
11 launch delays might be a new record for Falcon 9.
-
11 launch delays might be a new record for Falcon 9.
To get a handle on it need to seperate the weather slips from the "other" slips/delays. Not all of the other slips/delays are due to a technical issue but can be support systems like ASDS availability and fairing catchers. Sometimes the slip/delay is a complex mixture of several items.
-
11 launch delays might be a new record for Falcon 9.
To get a handle on it need to seperate the weather slips from the "other" slips/delays. Not all of the other slips/delays are due to a technical issue but can be support systems like ASDS availability and fairing catchers. Sometimes the slip/delay is a complex mixture of several items.
While that is true, delays are delays, no matter the cause, and in the future they will slow the progress to Mars, just as they are slowing progress to operational Starlink today.
-
Possible launch delay due to failed booster landing this evening.
-
Possible launch delay due to failed booster landing this evening?
Telemetry was solid throughout the event, so unless they see something puzzling, I doubt it.
-
https://www.nasaspaceflight.com/2021/02/starlink-l19/
The next mission, as of 05:00 UTC February 16, is the oft-delayed Starlink v1.0 L17 mission, originally planned for late-January but now targeting the early morning hours of February 17 — though this is likely to slip based on the L19 booster issue.
-
Getting unofficial word that launch is delayed. Probably official confirmation in a few hours.
-
Next launch date slip to NET 19 Feb 05:12 UTC, alternatively 20-22 Feb, according to Stage2 re-entry NOTAM update in Melbourne FIR.
MELBOURNE (FIR/FIC/ACC/COM/MET)
NOTAM #: F0547/21 Class: International Status: Active Issue Date UTC: 02/16/2021 0857 Start Date UTC: 02/19/2021 0706 End Date UTC: 02/22/2021 0655
F0547/21 NOTAMR F0509/21
Q) YMMM/QWMLW/IV/BO/W/000/999/5220S09818E999
A) YMMM
B) 2102190706 C) 2102220655
D) 2102190706 TO 2102190759
2102200645 TO 2102200738
2102210623 TO 2102210716
2102220602 TO 2102220655
E) ROCKET LAUNCH WILL TAKE PLACE
FLW RECEIVED FM GOVERNMENT OF UNITED STATES OF AMERICA:
HAZARDOUS OPS WILL BE CONDUCTED FOR ATMOSPHERIC RE-ENTRY AND
SPLASHDOWN OF LAUNCH VEHICLE OP X0521 FALCON-9 STARLINK V1.0-L17 WI
THE FOLLOWING AREAS:
FM 2943S 06007E
TO 2455S 06427E
TO 3845S 08430E
TO 4512S 09945E
TO 4946S 11913E
TO 5042S 13819E
TO 4850S 15644E
TO 5146S 15808E
TO 5442S 14832E
TO 5620S 13103E
TO 5552S 10750E
TO 4911S 08505E
TO 3432S 06413E TO BEGINNING
PRI RE-ENTRY 19TH
BACKUP AS PER FIELD D
F) SFC G) UNL
-
Possible launch delay due to failed booster landing this evening?
Telemetry was solid throughout the event, so unless they see something puzzling, I doubt it.
This mission has seen at least one (and very probably several more) delay due to the need to inspect/change out something in the vehicle, additional inspections, and an actual aborted hot fire. The just-launched mission has also seen some delays seemingly related to something on the vehicle - and appears to have suffered an engine loss *during ascent* that led to loss of control during the subsequent burn, not being a "life leader" stage at its 5th flight (however amazing that statement reads anyway).
The last engine out triggered an investigation that uncovered a quality control issue with the discovery of a systematic (as opposed to one-off) defect: the lacquer/isopropyl affair.
Summing both factors together, it'd be unreasonable to expect no impact: they've clearly already seen "something puzzling".
-
The just-launched mission has also seen some delays seemingly related to something on the vehicle - and appears to have suffered an engine loss *during ascent* that led to loss of control during the subsequent burn, not being a "life leader" stage at its 5th flight (however amazing that statement reads anyway).
The telemetry comparison with the previous Starlink mission does not support a theory about the engine loss during ascent, rather during an entry burn: https://forum.nasaspaceflight.com/index.php?topic=52895.msg2192524#msg2192524
It doesn't mean it's not worth being thoroughly checked though, landing reliability is very important for the launch cadence.
-
The just-launched mission has also seen some delays seemingly related to something on the vehicle - and appears to have suffered an engine loss *during ascent* that led to loss of control during the subsequent burn, not being a "life leader" stage at its 5th flight (however amazing that statement reads anyway).
The telemetry comparison with the previous Starlink mission does not support a theory about the engine loss during ascent, rather during an entry burn: https://forum.nasaspaceflight.com/index.php?topic=52895.msg2192524#msg2192524 (https://forum.nasaspaceflight.com/index.php?topic=52895.msg2192524#msg2192524)
It doesn't mean it's not worth being thoroughly checked though, landing reliability is very important for the launch cadence.
Fair enough, but the pre-MECO "bucket" (in the interval [145,157] s) does look much more out of family than other recent flights (around 15-20% inferior), in spite of less noisy TM. See, for instance:
https://forum.nasaspaceflight.com/index.php?topic=46524.msg2167636#msg2167636 (https://forum.nasaspaceflight.com/index.php?topic=46524.msg2167636#msg2167636)
https://forum.nasaspaceflight.com/index.php?topic=52045.msg2170673#msg2170673 (https://forum.nasaspaceflight.com/index.php?topic=52045.msg2170673#msg2170673)
I would hesitate to claim "the telemetry comparison does not support a theory about engine loss during ascent" until post-MECO MET with the available data. That is not to say it unequivocally supports it either, so I should have better qualified that section of my statement.
I would also argue checking the engine issue thoroughly is a necessity regardless of the importance of recovery towards future launch cadence, since it could as well have popped up during ascent (even if it didn't in this situation, which again is debatable), unless the failure signature they have is exclusive of reentry conditions, if there's such a thing.
-
Discussion of the L19 flight should be in the L19 thread
-
TFRs for L17 have been pulled.
https://twitter.com/SpaceTfrs/status/1361676016855511041?s=20
https://twitter.com/SpaceTfrs/status/1361676746509201409?s=20
https://twitter.com/SpaceTfrs/status/1361677500544335872?s=20
https://twitter.com/SpaceTfrs/status/1361678252234985477?s=20
-
New notices from the NGA.
Primary Day = Friday, February 19 at ~05:12 UTC.
Backup Day #1 = Saturday, February 20 at ~04:51 UTC.
Backup Day #2 = Sunday, February 21 at ~04:29 UTC.
Backup Day #3 = Monday, February 22 at ~04:08 UTC.
162023Z FEB 21
NAVAREA IV 143/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
190457Z TO 190615Z, ALTERNATE
200436Z TO 200554Z, 210414Z TO 210532Z,
AND 220353Z TO 220511Z FEB
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-17-00N 079-50-00W,
29-11-00N 079-44-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-57-00N 076-56-00W, 33-17-00N 076-03-00W,
33-31-00N 074-59-00W, 33-10-00N 074-36-00W,
32-27-00N 074-46-00W, 31-42-00N 076-41-00W.
2. CANCEL NAVAREA IV 135/21.
3. CANCEL THIS MSG 220611Z FEB 21.
162035Z FEB 21
HYDROPAC 546/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
190706Z TO 190759Z, ALTERNATE
200645Z TO 200738Z, 210623Z TO 210716Z AND
220602Z TO 220655Z FEB
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 510/21.
3. CANCEL THIS MSG 220755Z FEB 21.
-
The NGA has canceled the above posted notices, so this launch is postponed indefinitely at this time.
170358Z FEB 21
NAVAREA IV 146/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
CANCEL NAVAREA IV 143/21 AND THIS MSG.
170408Z FEB 21
HYDROPAC 549/21(GEN).
SOUTHERN INDIAN OCEAN.
CANCEL HYDROPAC 546/21 AND THIS MSG.
-
https://twitter.com/spacexfleet/status/1362397593779789825
Droneship support ship GO Quest is returning to Port Canaveral which confirms that the Starlink V1 L17 mission won't be flying for at least four days.
-
Any Idea what is wrong with Starlink 17? Can the payload be removed for a static fire of the booster and find booster problems? Or change boosters?
-
Any Idea what is wrong with Starlink 17? Can the payload be removed for a static fire of the booster and find booster problems? Or change boosters?
L19.
-
Any Idea what is wrong with Starlink 17? Can the payload be removed for a static fire of the booster and find booster problems? Or change boosters?
This latest delay is likely caused by the investigation into what caused B1059 to be lost than an issue with L17's booster. Don't want to launch L17 if it shares the same fatal issue( whether hardware or refurb process).
-
Starlink v1.0 Flight 17: launch scheduled February 25 EST.
https://twitter.com/NASASpaceflight/status/1362807222313619458
Meanwhile, SpaceX is tracking two Starlink launches next Thursday - L-20 and L-17 about 19 hours apart! (Updated Cape schedule - Subject to change).
So the current take-home is an "understood issue" - although we've not heard what issue B1059.6 (L-19) suffered during its return.
After Chris posted the above tweet, the Starlink v1.0 Flight 20 was rescheduled to NET March 8 UTC.
***
The last announced launch time for this flight was February 17, 0555 UTC. February 26 UTC is 9 days later.
9 * (20 to 22 minutes earlier/day) = ~3 hours earlier.
New launch time = February 26 ~0300 UTC. = February 25 ~22:00 EST.
***
Ben Cooper (http://www.launchphotography.com/Launch_Viewing_Guide.html), as of February 20, still has TBD launch dates. My bold.
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the twentieth Starlink batch on February or March TBD. A Falcon 9 will launch the twenty-first Starlink batch on TBD. Upcoming launches include additional Starlink missions on TBD. The launch time for Starlink launches gets approx. 20-22 minutes earlier each day. The next Crew Dragon carrying four astronauts to the International Space Station is targeted for April 20, around 5 or 6am EDT.
-
https://twitter.com/SpaceXFleet/status/1363521579293020161
Just Read the Instructions droneship has returned to Port Canaveral!
No seagulls to report on this occasion.
The droneship was deployed for the Starlink V1 L17 mission which has been delayed.
Live via NSF Fleetcam
https://youtu.be/gnt2wZBg89g
-
Active NOTAM in MELBOURNE information region for Stage2 reentry of Starlink_v1.0-L17 mission with primary date planned NET March 01 in window between 02:41-05:14 UTC (calculated launch time approx. 01:37 UTC), backup dates March 02 to 03.
MELBOURNE (FIR/FIC/ACC/COM/MET)
NOTAM #: F0609/21 Class: International Status: Active Issue Date UTC: 02/22/2021 1848 Start Date UTC: 03/01/2021 0241 End Date UTC: 03/03/2021 0430
F0609/21 NOTAMN
Q) YMMM/QWMLW/IV/BO/W/000/999/4844S09947E999
A) YMMM
B) 2103010241 C) 2103030430
D) 2103010241 TO 2103010514
2103020219 TO 2103020452
2103030157 TO 2103030430
PRI RE-ENTRY 1ST MAR
E) ROCKET LAUNCH WILL TAKE PLACE
FLW RECEIVED FROM GOVERNMENT OF UNITED STATES OF AMERICA:
HAZARDOUS OPS WILL BE CONDUCTED FOR ATMOSPHERIC RE-ENTRY AND
SPLASHDOWN OF LAUNCH VEHICLE OP X0521 FALCON-9 STARLINK V1.0-L17 AND
PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS:
FM 2943S 06007E
TO 2455S 06427E
TO 3845S 08430E
TO 4512S 09945E
TO 4946S 11913E
TO 5042S 13819E
TO 4850S 15644E
TO 5146S 15808E
TO 5442S 14832E
TO 5620S 13103E
TO 5552S 10750E
TO 4911S 08505E
TO 3432S 06413E TO BEGINNING
F) SFC G) UNL
-
Cross-post; my bold:
http://www.launchphotography.com/Launch_Viewing_Guide.html
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the twentieth Starlink batch from pad 39A on February 28 earliest, at 8:37pm EST. The launch time for Starlink missions gets approx. 20-22 minutes earlier each day. A Falcon 9 will launch the twenty-first Starlink batch from pad 40 on March 7 earliest, around 10pm. Upcoming launches include additional Starlink missions on TBD. The next Crew Dragon carrying four astronauts to the International Space Station is targeted for April 20, around 5 or 6am EDT.
-
https://twitter.com/emrekelly/status/1364321537487175682
Falcon 9 and its Starlink payload went vertical at 39A about an hour ago. Launch window is no earlier than this weekend, but don’t bank on it – nothing solid right now.
-
Static fire test was performed at 3am EST
https://twitter.com/cbs_spacenews/status/1364489613054738435?s=19
-
https://twitter.com/SpaceX/status/1364552086629842947
Static fire test complete – targeting Sunday, February 28 at 8:37 p.m. EST for launch of Starlink from LC-39A
-
@SpaceX 7:25 AM · Feb 24, 2021
Static fire test complete – targeting Sunday, February 28 at 8:37 p.m. EST for launch of Starlink from LC-39A
That's the second static fire in preparation for this launch. The first (https://forum.nasaspaceflight.com/index.php?topic=52511.msg2185914#msg2185914) was in the early morning hours of Jan 31.
@SpaceX 9:16 PM · Jan 31, 2021
Static fire test complete – targeting Tuesday, February 2 at 6:19 a.m. EST for launch of 60 Starlink satellites from LC-39A; team is keeping an eye on launch and recovery weather
-
NGA notices:
Primary Day = Monday, March 1 at 01:37 UTC.
Backup Day #1 = Tuesday, March 2 at ~01:15 UTC.
Backup Day #2 = Wednesday, March 3 at ~00:53 UTC.
241028Z FEB 21
NAVAREA IV 171/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
010032Z TO 010330Z MAR, ALTERNATE
020010Z TO 020308Z AND 022348Z TO 030246Z MAR
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-26-00N 079-41-00W,
29-20-00N 079-35-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-44-00N 077-12-00W, 33-17-00N 076-03-00W
33-32-00N 074-59-00W, 33-10-00N 074-34-00W,
32-27-00N 074-46-00W, 31-25-00N 076-53-00W.
2. CANCEL THIS MSG 030346Z MAR 21.
241013Z FEB 21
HYDROPAC 622/21(61,75,76).
SOUTHEASTERN INDIAN OCEAN.
SOUTHERN INDIAN OCEAN.
DNC 03, DNC 04, DNC 05.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
010241Z TO 010514Z MAR, ALTERNATE
020219Z TO 020452Z AND
030157Z TO 030430Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL THIS MSG 030530Z MAR 21.
-
Hawk and OCISLY are underway for LZ
https://twitter.com/julia_bergeron/status/1364763547893440515?s=19
-
SpaceX has updated their Launches (https://www.spacex.com/launches/) webpage for this launch.
https://www.youtube.com/watch?v=DpsrExXlQrA (https://www.youtube.com/watch?v=DpsrExXlQrA)
-
SpaceX has updated their Launches (https://www.spacex.com/launches/) webpage for this launch.
Reused fairings :)
One on its fourth launch, the other on its third!
-
TFR for the launch has been posted:
https://tfr.faa.gov/save_pages/detail_1_8056.html
https://tfr.faa.gov/save_pages/detail_1_8059.html
-
SpaceX has updated their Launches (https://www.spacex.com/launches/) webpage for this launch.
Reused fairings :)
One on its fourth launch, the other on its third!
Now that is some serious reuse right there. Way to bring down the cost per launch.
If only there was a fully reuseable 2 stage vehicle, hmmmm
Edit: This one has been on the 'up next' list for so long I'm starting to forget about it. Hopefully this is the time, and get the booster back into the process for it's next cycle.
-
Something interesting ... a new Space Debris notice from the NGA. Unless I missed something, the only change to the actual hazard information is an additional hazard period for March 1 only.
Color and emphasis added.
260331Z FEB 21
HYDROPAC 639/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
010241Z TO 010514Z AND
010519Z TO 010611Z MAR,
ALTERNATE 020219Z TO 020452Z AND
030157Z TO 030430Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 622/21.
3. CANCEL THIS MSG 030530Z MAR 21.
Canceled:
241013Z FEB 21
HYDROPAC 622/21(61,75,76).
SOUTHEASTERN INDIAN OCEAN.
SOUTHERN INDIAN OCEAN.
DNC 03, DNC 04, DNC 05.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
010241Z TO 010514Z MAR, ALTERNATE
020219Z TO 020452Z AND
030157Z TO 030430Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL THIS MSG 030530Z MAR 21.
-
GO Quest has left Port Canaveral to support recovery efforts for this mission
https://twitter.com/SpaceXFleet/status/1365085857728909322?s=19
-
L-2 weather forecast: Primary = 80% 'Go', Backup = 70% 'Go'. Booster Recovery Weather Risk is Moderate both days.
-
Visual mission profile
-
GO Searcher and GO Navigator are enroute to LZ for fairing recovery operations as the fairing catchers are being worked on.
https://twitter.com/SpaceXFleet/status/1365331037639872522?s=19
-
Something interesting ... a new Space Debris notice from the NGA. Unless I missed something, the only change to the actual hazard information is an additional hazard period for March 1 only.
...
...and changed again:
261955Z FEB 21
HYDROPAC 660/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
010241Z TO 010514Z MAR,
ALTERNATE 020219Z TO 020452Z AND
030157Z TO 030430Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 639/21.
3. CANCEL THIS MSG 030530Z MAR 21.
-
https://twitter.com/spacexfleet/status/1365433724268142592
SpaceX recovery fleet status as of Feb 26th!
OCISLY droneship and GO Quest are supporting the Starlink booster landing.
GO Searcher and Navigator have signed on to recover the fairing from the water, replacing Ms. Chief/Tree who are having work done in Florida.
-
https://twitter.com/TSKelso/status/1365414475952660482
-
L-1 weather forecast is 90% GO
-
https://twitter.com/TSKelso/status/1365414475952660482
Subtracting the mission duration (1 hour, 4 minutes, 39 seconds) from the scheduled deployment time (02:41:43 UTC), the scheduled launch time should be 01:37:04 UTC on March 1st (8:37:04 PM EST on February 28th).
-
Three worldwide orbital launches in succession:
Amazônia-1 and 18 ride-share satellites launch from Sriharikota at 0454 February 28 UTC. (https://forum.nasaspaceflight.com/index.php?topic=50228.0)
Success!
Arktika-M no. 1 launches from Baikonur at 0655 February 28 UTC. (https://forum.nasaspaceflight.com/index.php?topic=32726.0)
Success!
And, this launch at 0137 March 1 UTC!
March 1 January late 27 29 30 31 February 1 early 2 3 4 5 7 mid February 16 17 NET 19 TBD 26 - Starlink flight 20 19 18 (x60) [v1.0 L17] - Falcon 9-109 8 (B1049.8 S) - Kennedy LC-39A - 01:37 ~13:00 12:24 12:02 11:41 ~11:00 11:19 10:57 10:36 10:14 09:31 ~06:00-08:00 06:17 05:55 05:12 TBD ~03:00
(Starlink: launch 20-22 minutes earlier/day)
Changes on January 8th
Changes on January 20th
Changes on January 22th
Changes on January 26th
Changes on January 28th
Changes on January 30th
Changes on January 31st
Changes on February 1st
Changes on February 2nd
Changes on February 3rd
Changes on February 4th
Changes on February 5th
Changes on February 9th
Changes on February 11th
Changes on February 13th
Changes on February 16th
Changes on February 17th
Changes on February 19th
Changes on February 22nd
zubenelgenubi
-
"Press Kit" capture with OCR, this time the website was bugged for me as none of the capture apps were able to auto-scroll through the page. Had to do a manual stitch, hopefully for the next launches the page works like before...
-
L0 launch weather forecast, still 90% GO
-
https://youtu.be/n4jNH1W36xU
-
https://twitter.com/emrekelly/status/1366170961674969088
Good evening from Kennedy Space Center, where Falcon 9 + Starlink are on the pad for tonight’s 2037 ET launch. T-minus two hours.
-
Mission Control Audio:
https://www.youtube.com/watch?v=d_D7EnfGjiM (https://www.youtube.com/watch?v=d_D7EnfGjiM)
-
Music has started
https://youtu.be/DpsrExXlQrA
-
No camera views from 1st stage being shown on this flight...
Sent from my SM-G975F using Tapatalk
-
No camera views from 1st stage being shown on this flight...
Interesting. I wonder if this has something to do with the light show we got when the engine failed / heat issues on the last Starlink...
Or something with the video feed hardware is on the fritz and they don’t think it’s important enough to fix.
-
Counting down through T-5 minutes. No issues.
-
No camera views from 1st stage being shown on this flight...
Interesting. I wonder if this has something to do with the light show we got when the engine failed / heat issues on the last Starlink...
Or something with the video feed hardware is on the fritz and they don’t think it’s important enough to fix.
I’d bet on not wanting to rush broadcasting problems.
They said they’d have telemetry but he didn’t specifically say that they’d be showing it on the screen.
-
Abort at T-1 minute:24 seconds!
Standing by for further information.
Next launch opportunity will be tomorrow, March 1, 8:15 pm EST = 0115 March 2 UTC. (That does not mean the launch is officiallyrescheduled for a 24 hour delay. It's only the next opportunity.)
End of SpaceX web cast.
Apparently, not enough time to resolve and restart countdown within the launch window. That's why the countdown clock reset to T-15:00.
-
I wonder if the strongback did not fully retract, or retracted too late. It didn't look quite right to me.
- Ed Kyle
-
Wow at the instant "they must not want to us to see them fail!!!" speculation on the no camera announcement.
As I recall, last time they did not show camera it was a regulatory issue with NOAA in regards to Earth imaging (it really was). Maybe they let their license run out?
-
Some catch-up posts to tonight's scrub:
SpaceX set to launch long-delayed Starlink mission (https://www.nasaspaceflight.com/2021/02/spacex-launch-delayed-starlink/), February 28, by Colin Fletcher
https://twitter.com/spacecoast_stve/status/1366192765223260161
Falcon 9 B1049 has been teasing us for the last month or so, but tonight, she is ready to loft 60 #Starlink satellites. This will be the 2nd booster to accomplish 8 flights!
https://twitter.com/NASASpaceflight/status/1366196129050857474
Falcon 9 B1049.8 enjoying her T-20 minute vent.
https://twitter.com/NASASpaceflight/status/1366198180975624193
No seagulls spotted.
https://twitter.com/NASASpaceflight/status/1366200812318384130
ABORT! Falcon 9 B1049.8 aborted at T-1:24.
https://twitter.com/NASASpaceflight/status/1366201147602649092
24 hour scrub turnaround, pending what caused the abort.
Great talk after the scrub from the NSF crew!
-
https://twitter.com/SpaceX/status/1366205026603950082
Auto-abort at T-1:24 ahead of tonight's Falcon 9 launch of Starlink; next launch opportunity is tomorrow, March 1 at 8:15 p.m. EST
-
https://twitter.com/TSKelso/status/1366204420225073152
Now expected to be approximately 255x287km.
-
No camera views from 1st stage being shown on this flight...
Interesting. I wonder if this has something to do with the light show we got when the engine failed / heat issues on the last Starlink...
Or something with the video feed hardware is on the fritz and they don’t think it’s important enough to fix.
My guess was that given the problems on L-19, they want to see every single sensor at every single timepoint, and that takes precedence over video in the telemetry stream. But this is only speculation.
-
Only 60% GO for launch conditions on March 1, with moderate booster recovery risk.
-
SpaceX has reupdated their Launches (https://www.spacex.com/launches/) webpage for this launch.
https://www.youtube.com/watch?v=d5DzoKuhdNk (https://www.youtube.com/watch?v=d5DzoKuhdNk)
-
New NGA notices, however the times for the Alternate days look wrong to me.
010438Z MAR 21
NAVAREA IV 181/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
020100Z TO 020308Z MAR, ALTERNATE
022348Z TO 030246Z, 032327Z TO 040225Z AND
042305Z TO 050203Z MAR
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-26-00N 079-41-00W,
29-20-00N 079-35-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-44-00N 077-12-00W, 33-17-00N 076-03-00W
33-32-00N 074-59-00W, 33-10-00N 074-34-00W,
32-27-00N 074-46-00W, 31-25-00N 076-53-00W.
2. CANCEL NAVAREA IV 171/21.
3. CANCEL THIS MSG 050303Z MAR 21.
010415Z MAR 21
HYDROPAC 676/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
020309Z TO 020452Z MAR,
ALTERNATE 030157Z TO 030430Z,
040136Z TO 040409Z AND
050114Z TO 050347Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 660/21.
3. CANCEL THIS MSG 050447Z MAR 21.
-
No camera views from 1st stage being shown on this flight...
Interesting. I wonder if this has something to do with the light show we got when the engine failed / heat issues on the last Starlink...
Or something with the video feed hardware is on the fritz and they don’t think it’s important enough to fix.
If it returns next launch then it could very well just be an issue with the camera on stage 1 that isn't worth fixing, if it doesn't return I think it's very fair to assume they don't want people seeing their boosters failing and having it shown off to the world.
I think it is the latter personally because they scrubbed due to a stage 2 camera issue that they wanted to check just in case. I'll be glad to be proven wrong but people got to remember spacex is more than allowed to try and hide failures or control the messaging to avoid bad press, no one was forcing them when they used to show off failures of Falcon 9.
-
... people got to remember spacex is more than allowed to try and hide failures or control the messaging to avoid bad press, no one was forcing them wen they user to show off failures of Falcon 9.
Of course they are allowed to try and hide their failures, but I would be utterly flabbergasted if this becomes their policy after 19 years, 111 orbital launches, and a few dozen test launches. During which time they never hid their successes or failures, even to the point of making a Video about how *not* to land a Falcon 9 booster.
Why I vaguely recall them livestreaming the two most excellent KaBooms just this year, already. That surely does not seem like someone who "try and hide failures" to me!
-
Elon Musk even specifically said that it was a mistake to cut away from the CRS-16 failure and that it would not happen in the future (meaning they'd always show their failures).
-
New NGA notices, however the times for the Alternate days look wrong to me.
The problem is an inconsistent offset between the beginning of the hazard periord and launch time. Accounting for that, here are my calculated launch times.
Primary Day = Tuesday, March 2 at 01:15 UTC.
Backup Day #1 = Wednesday, March 3 at ~00:53 UTC.
Backup Day #2 = Thursday, March 4 at ~00:32 UTC.
Backup Day #3 = Friday, March 5 at ~00:10 UTC.
-
Falcon 9 is horizontal at pad 39A after last night’s Starlink scrub. Scheduled to launch at 2015 ET tonight, but stay tuned.
https://twitter.com/EmreKelly/status/1366402811009916929
-
https://twitter.com/nasaspaceflight/status/1366412437117939717
Falcon 9 B1049.8's launch from KSC 39A with the L-17 Starlink mission is now in a 48 hour scrub turnaround stance.
New NET (No Earlier Than) March 2 at 19:53 Local, per KSC notices.
Photo: Stephen Marr (@spacecoast_stve) for NSF.
-
https://twitter.com/spacex/status/1366434925692542979
Due to poor weather conditions in the recovery area and to allow additional time for pre-launch checks, now targeting Tuesday, March 2 at 7:53 p.m. EST for launch of Starlink from LC-39A
-
011901Z MAR 21
NAVAREA IV 183/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
022348Z TO 030246Z, ALTERNATE 032327Z TO 040225Z AND
042305Z TO 050203Z MAR
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-26-00N 079-41-00W,
29-20-00N 079-35-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-44-00N 077-12-00W, 33-17-00N 076-03-00W
33-32-00N 074-59-00W, 33-10-00N 074-34-00W,
32-27-00N 074-46-00W, 31-25-00N 076-53-00W.
2. CANCEL NAVAREA IV 181/21.
3. CANCEL THIS MSG 050303Z MAR 21.
-
And the associated Space Debris notice:
011935Z MAR 21
HYDROPAC 684/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
030157Z TO 030430Z MAR,
ALTERNATE 040136Z TO 040409Z AND
050114Z TO 050347Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 676/21.
3. CANCEL THIS MSG 050447Z MAR 21.
-
Wow at the instant "they must not want to us to see them fail!!!" speculation on the no camera announcement.
As I recall, last time they did not show camera it was a regulatory issue with NOAA in regards to Earth imaging (it really was). Maybe they let their license run out?
That was on the Second Stage video feed. The first stage was still broadcast during that flight as it didn't show a wide swath of the Earth.
-
Replacement NGA notices with an additional hazard period inserted (emphasized) which look bogus to me.
012100Z MAR 21
NAVAREA IV 185/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
022348Z TO 030246Z, ALTERNATE 032327Z TO 040225Z
040500Z TO 041102Z AND 042305Z TO 050203Z MAR
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-26-00N 079-41-00W,
29-20-00N 079-35-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-44-00N 077-12-00W, 33-17-00N 076-03-00W
33-32-00N 074-59-00W, 33-10-00N 074-34-00W,
32-27-00N 074-46-00W, 31-25-00N 076-53-00W.
2. CANCEL NAVAREA IV 183/21.
3. CANCEL THIS MSG 050303Z MAR 21.
012112Z MAR 21
HYDROPAC 685/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
030157Z TO 030430Z MAR,
ALTERNATE 040136Z TO 040409Z, 040709Z TO 041102Z,
AND 050114Z TO 050347Z MAR IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 684/21.
3. CANCEL THIS MSG 050447Z MAR 21.
-
... people got to remember spacex is more than allowed to try and hide failures or control the messaging to avoid bad press, no one was forcing them wen they user to show off failures of Falcon 9.
Of course they are allowed to try and hide their failures, but I would be utterly flabbergasted if this becomes their policy after 19 years, 111 orbital launches, and a few dozen test launches. During that time they never hid their successes or failures, even to the point of making a Video about how *not* to land a Falcon 9 booster.
Why I vaguely recall them livestreaming the two most excellent KaBooms just this year, already. That surely does not seem like someone who "try and hide failures" to me!
Oh absolutely this isn't a very new policy. This was adopted when landings became routine in 2017 and 2018. In most of spacex's history they gladly showed off the faults of falcon 9 and 1 but mainly in recent history - even though Starship they gladly show off - they cut the feed (CRS-16) don't even show the feed at all (Starlink L5) or media blackouts (every fairing recovery failure in the past 18 months or more, every landing failure from STP-2 onwards).
Elon Musk even specifically said that it was a mistake to cut away from the CRS-16 failure and that it would not happen in the future (meaning they'd always show their failures).
And that's why I love the man, if it wasn't for Elon there would've been media silence on CRS-16 as well.He was also a major contributor to the How not to land an orbital rocket video, wasn't a SpaceX PR team made video. But to be fair Elon is kinda the SpaceX lead PR team member.
I will say it again, I will be glad to be proven wrong and they fix the camera during downtime or on the next flight the camera is working again. But people need to remember SpaceX doesn't owe us anything, just because they used to give us info and video on Falcon 9 failures doesn't mean they still have to.
-
Okay if this discussion needs to continue, then don't forget that the announcer also stated that the landing on the droneship would be broadcast as usual.
So they don't want us to have a camera view of a possibly failing booster in flight (when we really can't see anything all that dramatic) but are okay for us to see one slamming down on the droneship if the failure occurred in the last few seconds?
I just thought of another WAG that doesn't involve SpaceX suddenly becoming camera shy -- they repurposed a camera and video feed to watch something they wanted to see. Maybe those protective boots we heard were the cause of failure on the other one, maybe something else that they wanted eyes on if it failed and they couldn't recover the booster. But in this case yeah ITAR and their own trade secrets could keep them from wanting to show it to the public -- plus the fact it would probably not be very interesting.
SpaceX engineers have mentioned before how nice it is to be able to stick a Go Pro next to a part to be able to get a visual record of how it was behaving in flight, but if you don't get the Go Pro back you need to assign video bandwidth to it.
-
L-0 launch weather forecast is only 40% GO (but back to 90 for tomorrow)
-
https://twitter.com/SpaceflightNow/status/1366823182733357066
There won’t be a Falcon 9 launch tonight.
The next chances to launch the Falcon 9 from pad 39A will come at 3:24am EST (0824 GMT) or 5:42am EST (1042 GMT) Thursday.
The morning launch suggests SpaceX will target a different plane in the Starlink fleet.
-
NGA notices:
021932Z MAR 21
NAVAREA IV 188/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
040815Z TO 041142Z, ALTERNATE
050755Z TO 051122Z MAR
IN AREAS BOUND BY:
A. 28-39-10N 080-37-48W, 29-00-00N 080-14-00W,
29-15-00N 079-56-00W, 29-26-00N 079-41-00W,
29-20-00N 079-35-00W, 29-07-00N 079-47-00W,
28-50-00N 080-02-00W, 28-34-00N 080-22-00W,
28-30-21N 080-32-58W.
B. 31-44-00N 077-12-00W, 33-17-00N 076-03-00W
33-32-00N 074-59-00W, 33-10-00N 074-34-00W,
32-27-00N 074-46-00W, 31-25-00N 076-53-00W.
2. CANCEL NAVAREA IV 185/21.
3. CANCEL THIS MSG 051222Z MAR 21.
021948Z MAR 21
HYDROPAC 695/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
041024Z TO 041326Z MAR,
ALTERNATE 051004Z TO 051306Z MAR
IN AREA BOUND BY
29-43S 060-07E, 24-55S 064-27E,
38-45S 084-30E, 45-12S 099-45E,
49-46S 119-13E, 50-42S 138-19E,
48-50S 156-44E, 51-46S 158-08E,
54-42S 148-32E, 56-20S 131-03E,
55-52S 107-50E, 49-11S 085-05E,
34-32S 064-13E.
2. CANCEL HYDROPAC 685/21.
3. CANCEL THIS MSG 051406Z MAR 21.
-
https://twitter.com/spacex/status/1366854158599352320
Now targeting no earlier than Thursday, March 4 for launch of Starlink due to a Range conflict and unfavorable launch and recovery weather
-
What is the range conflict? There are no other orbital launches scheduled in that time slot.
Static Fire for the next Falcon 9 flight (launch March 8 UTC)?
Trident II test offshore (USA or UK)?
Previously scheduled range maintenance?
Now targeting no earlier than Thursday, March 4 for launch of Starlink due to a Range conflict and unfavorable launch and recovery weather.
-
Could this be the reason? Its far but who knows.
https://www.nasa.gov/image-feature/rocket-launch-scheduled-march-3-from-nasa-s-wallops-flight-facility
A three-stage suborbital sounding rocket is scheduled for launch the afternoon of March 3, 2021, for the Department of Defense from NASA’s launch range at the Wallops Flight Facility in Virginia.
-
Has anyone heard anything about the cause of the auto-abort of the countdown Sunday night? This thread has been far more interested in why the first stage camera views would not be made public than why the bird didn't fly.
I know I haven't seen anything from Elon in the twittersphere, but figured I could maybe ask if it's been discussed here, but in some other thread, where I wouldn't think to look...?
-
Three worldwide orbital launches in succession:
(Snip)
And, this launch at 0137 March 1 UTC!
March 1January[/s] late
2729 3031[/s] February[/s] 1 early234[/s] 57[/s] mid February[/s] 1617NET 19TBD[/s] 26[/s] - Starlink flight 20 19[/s] 18[/s] (x60) [v1.0 L17] - Falcon 9-109 8[/s] (B1049.8 S) - Kennedy LC-39A - 01:37 ~13:00[/s] 12:24[/s] 12:02[/s] 11:41 ~11:00[/s] 11:19[/s] 10:57[/s] 10:36[/s] 10:14[/s] 09:31[/s] ~[/s]06:00-08:00[/s] 06:17[/s] 05:55[/s] 05:12[/s] TBD[/s] ~03:00[/s]
(Starlink: launch 20-22 minutes earlier/day)
Changes on January 8th
Changes on January 20th
Changes on January 22th
Changes on January 26th
Changes on January 28th
Changes on January 30th
Changes on January 31st
Changes on February 1st
Changes on February 2nd
Changes on February 3rd
Changes on February 4th
Changes on February 5th
Changes on February 9th
Changes on February 11th
Changes on February 13th
Changes on February 16th
Changes on February 17th
Changes on February 19th
Changes on February 22nd
zubenelgenubi
I double dare you to update this!
But please no beige... ;D
-
Has anyone heard anything about the cause of the auto-abort of the countdown Sunday night?
FWIW, I've read no updates. We shall see.
-
Could this be the reason? Its far but who knows.
https://www.nasa.gov/image-feature/rocket-launch-scheduled-march-3-from-nasa-s-wallops-flight-facility
A three-stage suborbital sounding rocket is scheduled for launch the afternoon of March 3, 2021, for the Department of Defense from NASA’s launch range at the Wallops Flight Facility in Virginia.
wrong range and authority.
-
<snip all the fun "My Little Pony: Friendship Is Magic"-colored facts>
I double dare you to update this!
But please no beige... ;D
Oh, I shall.
I already adjusted the "OP" back in reply #29 with today's update, and changed the beige print to tan. Agree beige reads very poorly against a default white background.
FYI to the curious:
One can substitute further text colors beyond the pull-down pallette provided by manually substituting the color name, or by hexadecimal red/green/ blue code.
Fun with the 256 web colors! As the ponies sing: "Living in Color!"
-
Could this be the reason? Its far but who knows.
https://www.nasa.gov/image-feature/rocket-launch-scheduled-march-3-from-nasa-s-wallops-flight-facility
A three-stage suborbital sounding rocket is scheduled for launch the afternoon of March 3, 2021, for the Department of Defense from NASA’s launch range at the Wallops Flight Facility in Virginia.
wrong range and authority.
Isn't Wallops part of the Eastern Range for some purposes?
-
Isn't Wallops part of the Eastern Range for some purposes?
No. They coordinate with each other on ops that affect each other
-
Could this be the reason? Its far but who knows.
https://www.nasa.gov/image-feature/rocket-launch-scheduled-march-3-from-nasa-s-wallops-flight-facility
A three-stage suborbital sounding rocket is scheduled for launch the afternoon of March 3, 2021, for the Department of Defense from NASA’s launch range at the Wallops Flight Facility in Virginia.
wrong range and authority.
but if they use common assets
-
https://twitter.com/TSKelso/status/1366923633566748675
CelesTrak has updated the pre-launch SupTLEs for #Starlink-V1.0-17 for the next 2 launch opportunities on Mar 4 at 0824 & 1042 UTC. Second time is the primary (desired) launch time. Deployment is set for 09:29:39.360 & 11:47:33.360 UTC, respectively: https://celestrak.com/NORAD/elements/supplemental/
-
L-1 launch weather forecast still 90% GO
-
https://twitter.com/TSKelso/status/1366923633566748675
CelesTrak has updated the pre-launch SupTLEs for #Starlink-V1.0-17 for the next 2 launch opportunities on Mar 4 at 0824 & 1042 UTC. Second time is the primary (desired) launch time. Deployment is set for 09:29:39.360 & 11:47:33.360 UTC, respectively: https://celestrak.com/NORAD/elements/supplemental/
The two opportunities are into different planes, about 40 degrees apart. Is this the first time they have done that?
It has long seemed to me that more starlink launches could be scheduled for the convenience of things on the ground, such as launch crews, weather, or air traffic, rather than aiming to fill particular slots with particular launches. The repeat period is about two months, so if you mostly launch at, say, noon you can still fill the constellation over a year.
-
It has long seemed to me that more starlink launches could be scheduled for the convenience of things on the ground, such as launch crews, weather, or air traffic, rather than aiming to fill particular slots with particular launches. The repeat period is about two months, so if you mostly launch at, say, noon you can still fill the constellation over a year.
Which bad for business. Filling specific slots will give them better early coverage.
-
There may be a little flexibility on deployments right now as they've mostly filled the initial 36 planes and are early on deploying the next 36. The high flight rate also helps since there will be more launches soon that could backfill any gaps. To maximize the quality of service as they're going live they do have to make sure they focus on filling gaps as well as just putting up bulk numbers of satellites.
-
It has long seemed to me that more starlink launches could be scheduled for the convenience of things on the ground, such as launch crews, weather, or air traffic, rather than aiming to fill particular slots with particular launches. The repeat period is about two months, so if you mostly launch at, say, noon you can still fill the constellation over a year.
Which bad for business. Filling specific slots will give them better early coverage.
If you have several gaps it does not matter which which gap you fill. Most of the time they will have several choices that give equivalent coverage. They are only tightly constrained when they have an almost full layer.
OTOH improving launch reliability and reducing launch delays is usually a win.
-
It has long seemed to me that more starlink launches could be scheduled for the convenience of things on the ground, such as launch crews, weather, or air traffic, rather than aiming to fill particular slots with particular launches. The repeat period is about two months, so if you mostly launch at, say, noon you can still fill the constellation over a year.
Which bad for business. Filling specific slots will give them better early coverage.
If you have several gaps it does not matter which which gap you fill. Most of the time they will have several choices that give equivalent coverage. They are only tightly constrained when they have an almost full layer.
OTOH improving launch reliability and reducing launch delays is usually a win.
Not true. Before the constellation is even close to complete, they can target higher revenue areas for better coverage. GPS did something similar. Shotgunning doesn’t do any good.
Plus noon is a bad launch time.
-
Updated "press kit" capture. Had to do again the manual capture and stitch.
-
Any indication yet which of the two launch times they're shooting for? The Celestrak discussion above states that the second time, 10:42 UTC, is the preferred time. But NSF's Facebook page states that they will be covering the 8:24 UTC launch time.
I've been up since 4am, and need to take a nap. I'd *really* like to sleep until the later timeframe, and not have to get up for the earlier one "just in case"... if it is going to be the preferred launch time.
-
Our reporters were told to show up for the earlier time. (Which doesn't guarantee it will be the earlier time, but that seems to still be a valid option)
-
SpaceX seems to be targeting the earlier time and the later one is backup:
SpaceX is targeting 3:24 a.m. EST on Thursday, March 4 for launch of 60 Starlink satellites from Launch Complex 39A (LC-39A) at Kennedy Space Center in Florida. If needed, there are backup opportunities available at 5:42 a.m. EST on Thursday, March 4, as well as 3:03 a.m. EST and 5:21 a.m. EST on Friday, March 5.
https://www.spacex.com/launches/
-
https://youtu.be/d5DzoKuhdNk
-
SpaceX seems to be targeting the earlier time and the later one is backup:
SpaceX is targeting 3:24 a.m. EST on Thursday, March 4 for launch of 60 Starlink satellites from Launch Complex 39A (LC-39A) at Kennedy Space Center in Florida. If needed, there are backup opportunities available at 5:42 a.m. EST on Thursday, March 4, as well as 3:03 a.m. EST and 5:21 a.m. EST on Friday, March 5.
https://www.spacex.com/launches/
Okay, thanks. Yeah, it made no sense to me whatsoever the primary was the later timeframe, and the secondary was the earlier.
-
Plus noon is a bad launch time.
Why?
-
Another launch attempt!
March 4 January late 27 29 30 31 February 1 early 2 3 4 5 7 mid 16 17 NET 19 TBD 26 March 1 NET 2 3 - Starlink flight 20 19 18 (x60) [v1.0 L17] - Falcon 9-109 8 (B1049.8 S) - Kennedy LC-39A - 08:24 or 10:42 ~13:00 12:24 12:02 11:41 ~11:00 11:19 10:57 10:36 10:14 09:31 ~06:00-08:00 06:17 05:55 05:12 TBD ~03:00 01:37 01:15 00:53
(Starlink: launch 20-22 minutes earlier/day)
Changes on January 8th
Changes on January 20th
Changes on January 22th
Changes on January 26th
Changes on January 28th
Changes on January 30th
Changes on January 31st
Changes on February 1st
Changes on February 2nd
Changes on February 3rd
Changes on February 4th
Changes on February 5th
Changes on February 9th
Changes on February 11th
Changes on February 13th
Changes on February 16th
Changes on February 17th
Changes on February 19th
Changes on February 22nd
Changes on March 1st
Changes on March 2nd
Changes on March 4th
zubenelgenubi
-
https://twitter.com/TGMetsFan98/status/1367322253017415683
An unusual Starlink launch in a few hours, with two launch opportunities at 3:24 and 5:42 AM EST, respectively.
#SpaceX #Falcon9 #Starlink
Article by Colin Fletcher: https://nasaspaceflight.com/2021/03/spacex-launch-delayed-starlink/
Webcast:
https://www.youtube.com/watch?v=3KeqrkywDwA
-
https://youtu.be/y709S6dhmUE
-
NSF now live
-
Go for first launch window
https://twitter.com/spacex/status/1367382859271467010
T-30 minutes until launch of Starlink. Webcast will go live ~15 minutes before liftoff → spacex.com/launches
-
https://twitter.com/nasaspaceflight/status/1367385924506632192
T-20 minute vent for B1049.8 at KSC 39A.
youtube.com/watch?v=3Keqrk…
https://twitter.com/spacecoast_stve/status/1367387318697545729
-
As before, no live camera views from Stage 1
-
T-30 LD is go for Launch
-
And Lift Off!
-
https://twitter.com/nasaspaceflight/status/1367390767984111618
-
T+1:14 MAX Q
-
This no camera view is very weird
MECO Confirmed
Stage Sep Confirmed
SES1 Confirmed
-
MECO
MVac startup
Fairing separation
-
https://twitter.com/nasaspaceflight/status/1367391506840092674
-
Stage 1 Entry Burn Start Up
-
Stage 1 Entry Burn Shut-Down
-
Stage 1 Transonic
Hopefully no seagulls this time
-
Stuck the landing
Lost video feed though
-
Coverage resumes at T+45min with engine relight
-
https://twitter.com/nasaspaceflight/status/1367393326870253570
-
https://twitter.com/SpaceX/status/1367393156073857027
-
Were the interns running the webcast tonight or just a dead tired crew covering both starship and starlink launches? I don't think I've seen a SpaceX webcast this bad in years.
-
https://twitter.com/spacecoast_stve/status/1367395778378035202
Falcon 9 punches a hole in the low-hanging clouds around KSC to put 60 new #Starlink satellites into orbit. This was booster B1049’s 8th flight. Only the second booster to do it!
Mission overview by @c_fletcher22: nasaspaceflight.com/2021/03/spacex…
-
https://twitter.com/zshauladventure/status/1367396873934364675
I Do love some clouds, but this was a whole lot! #SpaceX #Starlink #Falcon9 Double landing for @SpaceX, even if #SN10 did explode afterwards! Big day for the teams!
📷: Me - @NextHorizonsSF
-
Burn successful, good orbit
Coasting until T+1:04
-
Deployment successful
-
https://twitter.com/NASASpaceflight/status/1367407296465297409
-
https://twitter.com/SpaceX/status/1367407265901285381
-
SpaceX launch photos from their website (I presume by Ben Cooper)
-
As before, no live camera views from Stage 1
The repressed conspiracy theorist inside me is looking at the repeated launch delays and the strange lack of live booster coverage and thinking "there's some national security stuff being tested on that booster". The only video we see of the booster is from fixed camera angles, with the booster in a known orientation.
-
For those keeping track, this flight was delayed a total of 17 times from its original launch date on January 27.
Can't recall another F9 launch postponed that many times.
-
As before, no live camera views from Stage 1
The repressed conspiracy theorist inside me is looking at the repeated launch delays and the strange lack of live booster coverage and thinking "there's some national security stuff being tested on that booster". The only video we see of the booster is from fixed camera angles, with the booster in a known orientation.
Or, one of the technical delays were due to a fault in the camera system (or such a fault was discovered during additional inspections). So they figured it was simpler to turn that system off instead of doing a lengthy repair to a non critical system.
They can fix it during refurbishment after this flight.
-
As before, no live camera views from Stage 1
The repressed conspiracy theorist inside me is looking at the repeated launch delays and the strange lack of live booster coverage and thinking "there's some national security stuff being tested on that booster". The only video we see of the booster is from fixed camera angles, with the booster in a known orientation.
Or more reasonably, this is a life-leader in the booster fleet and between ITAR and potentially commercially-sensitive info regarding long-life boosters, they have chosen to be conservative with their preflight testing and abort limits. Quite possibly they have also taken time to add additional sensors and reserve some of the limited downlink bandwidth for telemetry in case they didn’t land the booster.
Take off the tinfoil hat and think like an engineer.
-
Regular service was resumed last night, when Starlink L17 successfully launched 60 satellites, and landed the booster. The only significant difference from the L18 launch profile was that there was no throttle down during the S2 terminal guidance.
-
As before, no live camera views from Stage 1
The repressed conspiracy theorist inside me is looking at the repeated launch delays and the strange lack of live booster coverage and thinking "there's some national security stuff being tested on that booster". The only video we see of the booster is from fixed camera angles, with the booster in a known orientation.
Or more reasonably, this is a life-leader in the booster fleet and between ITAR and potentially commercially-sensitive info regarding long-life boosters, they have chosen to be conservative with their preflight testing and abort limits. Quite possibly they have also taken time to add additional sensors and reserve some of the limited downlink bandwidth for telemetry in case they didn’t land the booster.
Take off the tinfoil hat and think like an engineer.
As a (non-rocket) engineer, I am normally inclined to agree with you, but this wasn't just "no live camera views from Stage 1" it was no live camera views of stage 1. Your explanation fails to explain the complete lack of any vehicle tracking after lift-off. Not even tracking the vehicle off the pad is far more suspicious than the lack of on-vehicle views.
-
Have you seen the cloud cover and how low the cloud base was? Most space photographers trying to capture the launch were reporting that they were unable to see the launch at all. Watch the stream, the rocket is disappearing into the clouds around T+0:14. Afterwards, with no camera on the first stage, how were they supposed to show the rocket?
https://twitter.com/johnkrausphotos/status/1367392114171146241
-
As before, no live camera views from Stage 1
The repressed conspiracy theorist inside me is looking at the repeated launch delays and the strange lack of live booster coverage and thinking "there's some national security stuff being tested on that booster". The only video we see of the booster is from fixed camera angles, with the booster in a known orientation.
Or more reasonably, this is a life-leader in the booster fleet and between ITAR and potentially commercially-sensitive info regarding long-life boosters, they have chosen to be conservative with their preflight testing and abort limits. Quite possibly they have also taken time to add additional sensors and reserve some of the limited downlink bandwidth for telemetry in case they didn’t land the booster.
Take off the tinfoil hat and think like an engineer.
As a (non-rocket) engineer, I am normally inclined to agree with you, but this wasn't just "no live camera views from Stage 1" it was no live camera views of stage 1. Your explanation fails to explain the complete lack of any vehicle tracking after lift-off. Not even tracking the vehicle off the pad is far more suspicious than the lack of on-vehicle views.
Then look to simpler likely explanations: the multiple possible launch windows made scheduling staff to run the webcast challenging, especially a webcast for a very routine Falcon 9 flight; tracking cameras non-functional; someone made an error configuring the equipment for the webcast … etc.
You can’t disguise or hide a rocket launch into a dark sky from a populous part of the planet. There’s absolutely no reason to see some conspiracy in the lack of camera coverage from SpaceX.
EDIT: Or yeah, low clouds prevented visual tracking.
-
Worth noting that John Insprucker explicitly stated that he was not doing this launch because he'd already done two (!) Starship webcasts on the same "day". So in addition to everything else, it's possible the announcer was a last-minute-ish substitute for John.
https://twitter.com/jinsprucker/status/1367350152080461827?s=19
-
Have you seen the cloud cover and how low the cloud base was? Most space photographers trying to capture the launch were reporting that they were unable to see the launch at all. Watch the stream, the rocket is disappearing into the clouds around T+0:14. Afterwards, with no camera on the first stage, how were they supposed to show the rocket?
https://twitter.com/johnkrausphotos/status/1367392114171146241
Yes I have actually, and experienced the misery of it over the summer watching the OTV-7 atlas mission. Couldn’t see the rocket even from port and only ended up hearing a rumble.
-
Interesting... John Insprucker is a Doctor Who fan. ;D
-
For those keeping track, this flight was delayed a total of 17 times from its original launch date on January 27.
Can't recall another F9 launch postponed that many times.
Apparently, we are in the midst of a Launchscrubapalooza!
And as for the clouds and lack of visibility, been there, done that, have the teeshirt.
CRS-10. Between the derelict Shuttle Rotating Support Structure blocking the on-pad and ignition view and the cloud deck under 1000 feet it seemed we saw very little of the launch or RTLS landing.
Bummer!
-
As before, no live camera views from Stage 1
The cloud cover certainly made the absence of the usual Stage 1 video feed more stark.
LOL the conspiracy theories here, especially the national-security payload one [rolls eyes]. My own theory is that they decided to take the (limited) telemetry bandwidth and assign it to either A) a LOT more non-video instrumentation channels or B) a camera aimed at the engine bay (and not shown to us). I'm guessing that the recent engine failure on B1059.6 had them wanting to pay extra close to this flight, especially as one of the two life leaders, and hence the desire for extra data.
Note also that this was discussed ad nauseum after the first launch attempt, so go back in this thread to see that discussion (https://forum.nasaspaceflight.com/index.php?topic=52511.msg2197590#msg2197590).
-
I'm not so concerned about the lack of first stage video. The fact that this one got off the ground finally after so many delays, (not all delays were vehicle or SpaceX) is great.
get the booster and pad back into circulation for the next flight.
6 launches in just over 2 months, is a pace for 35-ish launches this year. That is a big manifest for the number of boosters available.
I remember driving home early to catch the Falcon 1 launches and it being months or years between each launch. so this is really exciting to see a flight every 7-10 days.
-
https://twitter.com/SpaceXFleet/status/1367637425778999296
B1049 has been secured and OCISLY droneship is en-route to Port Canaveral! ETA Sun/Mon (Roughly)
GO Searcher and Navigator are also en-route to Florida after conducting fairing recovery work.
-
https://twitter.com/SpaceXFleet/status/1367997781995106306
-
https://twitter.com/spacecoast_stve/status/1368199590420307982
GO Searcher has returned with an intact fairing half from Thursday’s Starlink mission.
The crew, hangin’ on the helipad, seems happy to be home. But my guess is they won’t be here long before they head out for the next mission.
Watch live on Fleetcam: youtu.be/gnt2wZBg89g
-
https://twitter.com/jconcilus/status/1368215418138157059
Go Navigator inbound with a little something on deck!
-
https://twitter.com/spacexfleet/status/1368217825991655426
Whilst GO Navigator arrives with the other fairing half, a crane has already lifted the first off of GO Searcher.
📸 Via NSF: youtube.com/channel/UCSUu1…
-
twitter.com/spacecoast_stve/status/1368221490701799436
Make that two successfully scooped fairing halves! GO Navigator is back, and that’ll make one whole fairing ready to be prepped for another flight.
https://twitter.com/spacecoast_stve/status/1368221828917952512
Looks like a spare fairing cradle up on the helipad.
-
https://twitter.com/SpaceXFleet/status/1368335738266337281
SpaceX recovery fleet status as of March 6th.
Estimating Of Course I Still Love You droneship arrival at Port Canaveral late tomorrow (7th) afternoon/evening or early Monday.
And, GO Quest at Port of Morehead City.
-
https://twitter.com/julia_bergeron/status/1368554857318219779
Of Course I Still Love You with B1049-8 is slowing making its way to Port Canaveral from the north. They will arrive later today. #SpaceXFleet
-
https://twitter.com/spacexfleet/status/1368616091367407628
OCISLY droneship and B1049 are sailing with the wind and back up to speed.
The droneship will be within the vicinity of Port Canaveral by 9pm ET tonight.
I'd expect them to wait offshore until dawn on Monday but that might not be the case.
-
https://twitter.com/SpaceXFleet/status/1368742335270518792
OCISLY and B1049 are going into a holding pattern off Port Canaveral until the morning.
The droneship tug is reporting an ETA of 7am ET but there will be other conflicting traffic that might make this earlier/later. (6 - 9am ET)
-
https://twitter.com/planet4589/status/1368739947889491968
-
twitter.com/spacexfleet/status/1368886836408573952
Hearing there may be some kind of issue related to the tow chain between Tug Hawk and OCISLY.
Divers are due out at 7:15am.
https://twitter.com/kyle_m_photo/status/1368891622545633280
Hawk and OCISLY are pretty far apart, I think the farthest I've seen before I wonder if they are even connected currently. #SpaceXFleet #SpaceX
Edit to add:
https://twitter.com/kyle_m_photo/status/1368906300319498241
Hawk and OCISLY are closer together now, it's possible they resolved any issues they had with the chain on thier own. #SpaceXFleet #SpaceX
-
https://twitter.com/kyle_m_photo/status/1368917600684670986
Looks like Octagrabber had a good deployment. #SpaceXFleet #SpaceX
-
https://twitter.com/spacexfleet/status/1368933277105594373
Tow chain is still an active issue for Tug Hawk and OCISLY. Sounds like it's getting worse the longer they wait.
Tanker is gone, Navy ship coming in now and then I think it will finally be time to bring the droneship in.
twitter.com/spacexfleet/status/1368933846645944321
One of SpaceX's fast-approach boats, used for Dragon recovery, is heading out to help it seems.
https://twitter.com/spacexfleet/status/1368934848560308226
Spotted by NSF Fleetcam... just.
youtube.com/watch?v=gnt2wZ…
Edit to add:
https://twitter.com/therealjonvh/status/1368936269372395520
High Speed #SpaceX Dragon recovery boat heads out. #SpaceXFleet
-
https://twitter.com/SpaceXFleet/status/1368943721832677381
-
https://twitter.com/Kyle_M_Photo/status/1368940522656722944
-
SpaceX has now landed 75 boosters and it is still amazing to watch the whole process play out.
Also 8th landing for this booster, that's incredible, I'm looking forward to seeing how far past 10 they can go with these booster.s
It's 5 years old now with this architecture, can't wait for Superheavy so every landing is a RTLS landing.
-
https://twitter.com/spacexfleet/status/1368947541040103429
Entering Port with a tow chain dragging underwater is an issue that requires approval from various places including the Coastguard.
OCISLY droneship cannot enter Port Canaveral until approval is granted, "hopefully this afternoon."
-
Presumably they can reel in the side hanging from the tug, but they don't have a winch on the ASDS to haul that side up?
And I'd assume the approval required is something like Dig Safe, where they need to vet the route to make sure the chain isn't going to tear up any lobster traps, communications cables, buoy anchors, etc as it passes.
-
https://twitter.com/SpaceXFleet/status/1369059285171376135
-
How expensive is this tow chain? Seems like a lot of boat time being used here. At some point it seems like it would make more sense just to cut and drop the side that's dragging somewhere out at sea?
-
https://twitter.com/planet4589/status/1368739947889491968
2211 has belatedly started orbit raising, so they must have debugged it
-
https://twitter.com/JConcilus/status/1369248476488470534
-
https://twitter.com/spacexfleet/status/1369269849554354176
Good morning! OCISLY is still offshore. The SpaceX fast boat went out to meet it at dawn.
Meanwhile, extra assistance - Tug Catherine - has arrived to help bring OCISLY in.
-
Given all the pre-launch delays for this mission, the delays in getting OCISLY into port just seem par for the course.
-
https://twitter.com/kyle_m_photo/status/1369334352707022865
After over a day of sitting off the coast because of issues with the main tow line Hawk, OCISLY, and B1049.8 are now entering Port Canaveral. #SpaceXFleet #SpaceX
https://twitter.com/kyle_m_photo/status/1369336115044507655
The main tow chain can be seen dragging in the water. #SpaceXFleet #SpaceX
-
Live on NSF fleetcam
https://youtu.be/gnt2wZBg89g
-
Given all the pre-launch delays for this mission, the delays in getting OCISLY into port just seem par for the course.
This mission needed more
on its patch!
I do love that toasty brown booster color though. White boosters are going to seem so archaic.
-
https://twitter.com/planet4589/status/1369349366620753924
It appears that the Falcon 9 second stage from the most recent Starlink launch (V1.0-L17) failed to deorbit itself, according to hobbyist obsevers
https://twitter.com/planet4589/status/1369350085742592000
If you had to guess, how long do you think it will take to decay?
a few weeks perhaps
Ted Molczan: http://www.satobs.org/seesat/Mar-2021/0074.html
Video observation: https://youtube.com/watch?v=JdbWWKalPwg
-
It appears that the Falcon 9 second stage from the most recent Starlink launch (V1.0-L17) failed to deorbit itself, according to hobbyist observers.
If you had to guess, how long do you think it will take to decay?
a few weeks perhaps
From Ted's SeeSat-l post: 281 X 282 km x 53 deg
The satellites' deploy was from circular orbit. Apparently, the de-orbit burn completely failed? Or ignited and immediately shut down?
***
Two static fires + multiple launch attempts + broken barge tow chain + 2nd stage de-orbit burn fail = Ad Astra Per Aspera!
-
https://youtu.be/uCR2OQTmYrA
-
https://twitter.com/FarryFaz/status/1369506198232391685
Was moved to the stand last night
-
https://twitter.com/julia_bergeron/status/1369684095387721733
Operation tow chain via Fleetcam
B1049-8 is secure on the stand while the port crane is doing something we normally don't see, recovering the tow line that delayed entry into port. Techs need to get OCISLY ready to leave port ahead of the weekend mission.
youtu.be/gnt2wZBg89g
-
Can someone tweet Elon and ask him to get that rusty hulk moved?
-
https://twitter.com/ken_kremer/status/1369748250908106755
-
Booster is horizontal and awaiting transport.
-
https://mobile.twitter.com/FarryFaz/status/1370412142910959619
There she goes to be prepared to become #B1049.9 Just amazing to this booster on the move. @SpaceIntellige3
@SpaceX
-
https://youtu.be/SJMSaz0uWT8
-
https://sattrackcam.blogspot.com/2021/03/failed-deorbit-of-starlink-18-falcon-9.html?m=1
-
https://sattrackcam.blogspot.com/2021/03/failed-deorbit-of-starlink-18-falcon-9.html?m=1
Reentry within less than a month basically means the stage doesn't pose any problem in regards to space debris. The only problem is the likely survival of COPV's and other temperature resistant dense components in an uncontrolled reentry.
As seen here:
https://spaceflight101.com/falcon-9-jcsat-16/spacex-rocket-parts-rain-down-over-indonesia/
-
https://twitter.com/planet4589/status/1375301028514500615
The Falcon 9 second stage from the Mar 4 Starlink launch failed to make a deorbit burn and is now reentering after 22 days in orbit. Its reentry was observed from the Seattle area at about 0400 UTC Mar 26.
-
Nice video of S2 reentry, but the commentary is a bit off ...
https://twitter.com/lucassmanning/status/1375297781338763268
Edit to add:
https://twitter.com/pnwswiftie/status/1375303872881643524
https://twitter.com/genevievereaume/status/1375300767167311875
-
View from almost directly beneath, posted in the Portland subreddit.
https://www.reddit.com/r/Portland/comments/mdgdxh/gif_of_the_lightsmeteorsatellite/
-
https://cimss.ssec.wisc.edu/satellite-blog/archives/40390
-
https://nbc16.com/news/local/debris-from-spacex-rocket-located-recovered-in-wash-state
COPV made it to the ground.
-
https://twitter.com/joroulette/status/1378062115248996353
A SpaceX Falcon 9 COPV left a "4-inch dent in the soil" of someone's farm this weekend near Beverly, Washington, over 100 miles inward from the Pacific coast, a PAO says. Sheriff's office called SpaceX and they picked it up the next day.
twitter.com/grantcosheriff/status/1378031863785263106
SpaceX recovered a Composite-Overwrapped Pressure Vessel from last week’s Falcon 9 re-entry. It was found on private property in southwest Grant County this week. Media and treasure hunters: we are not disclosing specifics. The property owner simply wants to be left alone.
-
https://twitter.com/joroulette/status/1378062115248996353
A SpaceX Falcon 9 COPV left a "4-inch dent in the soil" of someone's farm this weekend near Beverly, Washington, over 100 miles inward from the Pacific coast, a PAO says. Sheriff's office called SpaceX and they picked it up the next day.
twitter.com/grantcosheriff/status/1378031863785263106
SpaceX recovered a Composite-Overwrapped Pressure Vessel from last week’s Falcon 9 re-entry. It was found on private property in southwest Grant County this week. Media and treasure hunters: we are not disclosing specifics. The property owner simply wants to be left alone.
Some people have no imagination.
-
Some people have no imagination.
Great trophy if you can keep it under wraps, but I think it's still technically SpaceX property and more so, if lawyers waving ITAR regulations show up at your door, its game over.
-
The mission that just won't end.
https://www.upi.com/Odd_News/2021/04/13/Oregon-space-debris-SpaceX-Alsea-Bay/2761618332564/
-
So, two COPV's? Is there a good stage-2 cutaway drawing showing them?
-
So, two COPV's? Is there a good stage-2 cutaway drawing showing them?
A picture: https://forum.nasaspaceflight.com/index.php?topic=36440.msg1308196#msg1308196