SpaceX F9 : Starlink v1.0 L15 : CC SLC-40 : Nov 24 2020 (Nov 25 0213 UTC)

[gongora]

Discussion thread for Starlink v1.0 Flight 15.

Check the Starlink Index Thread for links to more Starlink information.

NSF Threads for Starlink v1.0 Flight 15: Discussion

Successful launch November 24, 2020 at 9:13pm EST (02:13 UTC on the 25th) on Falcon 9 (booster 1049.7) from SLC-40 at Cape Canaveral.  Successful booster ASDS landing on OCISLY (being towed by Hawk).  Expected elliptical deployment orbit of approximately 210x360 km.

The Falcon 9 first stage rocket booster supporting this mission previously flew on six other missions: the Telstar 18 VANTAGE mission in September 2018, the Iridium-8 mission in January 2019, and four Starlink missions in May 2019, January 2020, June 2020, and August 2020. 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 supported a mission, and the other half previously two.

Payload: A batch of 60? Starlink satellites.

Please use the Starlink Discussion Thread for all general discussion on Starlink.

L2 SpaceX:
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.

[Jansen]

A lot of launches (external customers) have priority ahead of this one, but the cascading delays mean that this launch could happen as early as 01 November from LC-39A.

It all depends on when the engine issues from GPS III-SV04 are resolved. The backlog from the following launches could push L15 into late December.

Priority list:
NROL-108
Crew-1
GPS III-SV04
SXM 7
CRS 21
Turksat 5A
Transporter 1

[Jansen]

Successful launch of Starlink v1.0 L13 frees up LC-39A. Two week turnaround means possible launch on 01 November.

Crew-1 is still on the manifest for 11 November. A nine day turnaround is the quickest so far on the same pad, but I suspect they would need additional time for a crewed mission.

Priority goes to external customers, so everything still depends on the engine investigation from GPS III SV04.

NROL-44 as a National Security mission would also have priority when they resolve their issues.

[klod]

Starlink v1.0 L14 would be 3 day turnaround.

[Jansen]

Starlink v1.0 L14 would be 3 day turnaround.

That’s from a different launchpad.

KSC has the ability to launch the same type of spacecraft from different launchpads within hours.

[wannamoonbase]

Starlink v1.0 L14 would be 3 day turnaround.

That’s from a different launchpad.

KSC has the ability to launch the same type of spacecraft from different launchpads within hours.

With the GPS and Crew-1 boosters waiting for resolution of the gas generator issue they could pull some missions like Starlink 15 forward.

[Jansen]

With the GPS and Crew-1 boosters waiting for resolution of the gas generator issue they could pull some missions like Starlink 15 forward.

Yes, that was the point I was making in the posts above. L15 was going to be in December before the issues with SV04 came up.

With L13 launched and L14 launching soon, I’m not sure how much of a backlog of F9s is staged and ready. Time is still needed for vehicle assembly, integration, and testing.

As a point of reference, the quickest turnaround so far has been 9 days on SLC-40 and 12 days on LC-39A.

[klod]

Starlink v1.0 L14 would be 3 day turnaround.

That’s from a different launchpad.

KSC has the ability to launch the same type of spacecraft from different launchpads within hours.

Main limitation is SpaceX by themselves. Hight rank commander said earlier this year that CCAFS is capable of 1 launch per day. I assume that SpaceX has 1 dedicated team for Starlink's missions. 3 days - that is quickest turnaround between their own missions. Although we should consider lots of delays for 2 monthes. It mean that Starlinks were ready for launch for long time. And now we have situation when 2 missions are commmencing and they need to prepare next launch. I would consider 9 days - is optimal for now, but this year they delayed so many launches that thay would need to speed up.

[Jansen]

No, the shortest time between SpaceX launches was just under 48 hours with SSO-A and CRS-16. There was an attempt earlier this month that would have seen two launches within 12 hours.

Weather has been the number one reason for delays. That goes back decades.

Of course there are capacity constraints at the PPF for LV Processing, integration, and testing. This chart indicates the typical schedule, though several F9s go through concurrently.

Based on the chart we should see the booster being moved to the hanger soon.

[Jansen]

Based on availability, the booster will either be B1049.7 or B1059.5, with the former being more likely.

[Jansen]

B1049 was spotted in KSC on October 16. I'm guessing it's going to launch on Starlink v1.0 L15 in November.

Source: Reddit (I cropped the image)

[klod]

No, the shortest time between SpaceX launches was just under 48 hours with SSO-A and CRS-16. There was an attempt earlier this month that would have seen two launches within 12 hours.

Weather has been the number one reason for delays. That goes back decades.

Of course there are capacity constraints at the PPF for LV Processing, integration, and testing. This chart indicates the typical schedule, though several F9s go through concurrently.

Based on the chart we should see the booster being moved to the hanger soon.

between their own missions - meant Starlink.

[zubenelgenubi]

Cross-post; my bold:

http://www.launchphotography.com/Delta_4_Atlas_5_Falcon_9_Launch_Viewing.html

FALCON 9

The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the 15th Starlink batch from pad 40 on October 22 at 12:14pm EDT. A Falcon 9 will launch NROL-108 for the National Reconnaissance Office on late October TBA; the launch date and period are TBA. The first stage will land back at the Cape about eight minutes after launch. A Falcon 9 from pad 40 will launch the fourth Block III GPS satellite for the U.S. Air/Space Force on early November TBA, around 6 or 7pm EST. The launch windows stretches 15 minutes. Other upcoming launches are TBA. A Falcon 9 will launch the SiriusXM-7 communications satellite on November TBD, likely in the middle of the night EST. A Falcon 9 from pad 39A will launch Crew-1 to the ISS, on mid-November TBD, in the evening EST. The launch window is instantaneous. The launch time gets 22-26 min. earlier each day. A Falcon 9 will launch the 16th batch of Starlink satellites on November TBD. And a Falcon 9 will launch the first cargo Dragon 2 to the ISS, CRS-21, on November 22 at the earliest, or early December, at around 4:30pm EST if 22nd. The launch time gets 22-26 min. earlier each day.

[Jansen]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.

Note that there is an error in the text.  "311355Z TO 31652Z OCT" should be "311355Z TO 311652Z OCT".

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
   311355Z TO 31652Z OCT, ALTERNATE
   011355Z TO 011652Z NOV
   IN AREAS BOUND BY:
   A. 28-39-43N 080-38-12W, 29-02-00N 080-15-00W,
      28-57-00N 080-08-00W, 28-40-00N 080-11-00W,
      28-27-00N 080-24-00W, 28-26-52N 080-32-07W.
   B. 30-12-00N 079-06-00W, 30-28-00N 078-56-00W,
      30-54-00N 078-52-00W, 31-14-00N 078-13-00W,
      31-06-00N 077-36-00W, 30-47-00N 077-22-00W,
      30-27-00N 077-26-00W, 30-08-00N 078-20-00W,
      30-03-00N 078-58-00W.
2. CANCEL THIS MSG 011752Z NOV 20.

Possibly NROL-108 or Starlink v1.0 L15

[Ken the Bin]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.

Note that there is an error in the text.  "311355Z TO 31652Z OCT" should be "311355Z TO 311652Z OCT".

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
   311355Z TO 31652Z OCT, ALTERNATE
   011355Z TO 011652Z NOV
   IN AREAS BOUND BY:
   A. 28-39-43N 080-38-12W, 29-02-00N 080-15-00W,
      28-57-00N 080-08-00W, 28-40-00N 080-11-00W,
      28-27-00N 080-24-00W, 28-26-52N 080-32-07W.
   B. 30-12-00N 079-06-00W, 30-28-00N 078-56-00W,
      30-54-00N 078-52-00W, 31-14-00N 078-13-00W,
      31-06-00N 077-36-00W, 30-47-00N 077-22-00W,
      30-27-00N 077-26-00W, 30-08-00N 078-20-00W,
      30-03-00N 078-58-00W.
2. CANCEL THIS MSG 011752Z NOV 20.

Possibly NROL-108 or Starlink v1.0 L15

As I noted in the NROL-108 topic, the launch parameters are not consistent with a Starlink launch.  While I'm not certain that it is NROL-108, I am 99.999% certain that it is not Starlink.

[cwr]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.

Note that there is an error in the text.  "311355Z TO 31652Z OCT" should be "311355Z TO 311652Z OCT".

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
   311355Z TO 31652Z OCT, ALTERNATE
   011355Z TO 011652Z NOV
   IN AREAS BOUND BY:
   A. 28-39-43N 080-38-12W, 29-02-00N 080-15-00W,
      28-57-00N 080-08-00W, 28-40-00N 080-11-00W,
      28-27-00N 080-24-00W, 28-26-52N 080-32-07W.
   B. 30-12-00N 079-06-00W, 30-28-00N 078-56-00W,
      30-54-00N 078-52-00W, 31-14-00N 078-13-00W,
      31-06-00N 077-36-00W, 30-47-00N 077-22-00W,
      30-27-00N 077-26-00W, 30-08-00N 078-20-00W,
      30-03-00N 078-58-00W.
2. CANCEL THIS MSG 011752Z NOV 20.

Possibly NROL-108 or Starlink v1.0 L15

I'm not an expert but these coordinates seem to be very similar to the Starlink L14 hazardous ops warning.
I think it's describing the area for landing on a drone ship and the area where the fairings are recovered.

While we also know that NROL 108 is supposed to be a RTLS hence wouldn't have a drone ship landing.
But that expectation could be wrong.

So it seems most likeley that this is the warning for Starlink v1.0 L15.


Carl

[Ken the Bin]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.

Note that there is an error in the text.  "311355Z TO 31652Z OCT" should be "311355Z TO 311652Z OCT".

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
   311355Z TO 31652Z OCT, ALTERNATE
   011355Z TO 011652Z NOV
   IN AREAS BOUND BY:
   A. 28-39-43N 080-38-12W, 29-02-00N 080-15-00W,
      28-57-00N 080-08-00W, 28-40-00N 080-11-00W,
      28-27-00N 080-24-00W, 28-26-52N 080-32-07W.
   B. 30-12-00N 079-06-00W, 30-28-00N 078-56-00W,
      30-54-00N 078-52-00W, 31-14-00N 078-13-00W,
      31-06-00N 077-36-00W, 30-47-00N 077-22-00W,
      30-27-00N 077-26-00W, 30-08-00N 078-20-00W,
      30-03-00N 078-58-00W.
2. CANCEL THIS MSG 011752Z NOV 20.

Possibly NROL-108 or Starlink v1.0 L15

I'm not an expert but these coordinates seem to be very similar to the Starlink L14 hazardous ops warning.
I think it's describing the area for landing on a drone ship and the area where the fairings are recovered.

While we also know that NROL 108 is supposed to be a RTLS hence wouldn't have a drone ship landing.
But that expectation could be wrong.

So it seems most likeley that this is the warning for Starlink v1.0 L15.


Carl

This is a "ROCKET LAUNCHING" notice.  There are separate "SPACE DEBRIS" notices for things coming back from space.  (Even the SpaceX Demo-2 capsule return was classified as "SPACE DEBRIS".)

[zubenelgenubi]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.
<snip>

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
<snip>

Possibly NROL-108 or Starlink v1.0 L15

As I noted in the NROL-108 topic, the launch parameters are not consistent with a Starlink launch.  While I'm not certain that it is NROL-108, I am 99.999% certain that it is not Starlink.

I'm not an expert but these coordinates seem to be very similar to the Starlink L14 hazardous ops warning.
I think it's describing the area for landing on a drone ship and the area where the fairings are recovered.
While we also know that NROL 108 is supposed to be a RTLS hence wouldn't have a drone ship landing.
But that expectation could be wrong.
So it seems most likely that this is the warning for Starlink v1.0 L15.
Carl

This is a "ROCKET LAUNCHING" notice.  There are separate "SPACE DEBRIS" notices for things coming back from space.  (Even the SpaceX Demo-2 capsule return was classified as "SPACE DEBRIS".)

Turns out, the notice was for NROL-108.

[Ken the Bin]

I received this notice from the NGA.  I'm not certain that it is for this launch, but it seems the most likely.
<snip>

260250Z OCT 20
NAVAREA IV 1033/20(11,26).
<snip>

Possibly NROL-108 or Starlink v1.0 L15

As I noted in the NROL-108 topic, the launch parameters are not consistent with a Starlink launch.  While I'm not certain that it is NROL-108, I am 99.999% certain that it is not Starlink.

I'm not an expert but these coordinates seem to be very similar to the Starlink L14 hazardous ops warning.
I think it's describing the area for landing on a drone ship and the area where the fairings are recovered.
While we also know that NROL 108 is supposed to be a RTLS hence wouldn't have a drone ship landing.
But that expectation could be wrong.
So it seems most likely that this is the warning for Starlink v1.0 L15.
Carl

This is a "ROCKET LAUNCHING" notice.  There are separate "SPACE DEBRIS" notices for things coming back from space.  (Even the SpaceX Demo-2 capsule return was classified as "SPACE DEBRIS".)

Turns out, the notice was for NROL-108.

Which is where I posted it.  My quoted post above was copied from that topic.

Edit: I'm referring of course to the innermost post with the quote of the NGA.

[zubenelgenubi]

Which is where I posted it.  My quoted post above was copied from that topic.
Edit: I'm referring of course to the innermost post with the quote of the NGA.

I'm sorry about my lack of clarity.

Ken, you were right from the get-go (in the NROL-108 thread).

Others, in this thread, ignored your stated reasoning in the other thread, and your re-statements here.  Therefore, they came to the wrong conclusions in this thread.  Thus, my wink .

One of my faulty assumptions was that if someone investigated your OP of this splinter thread (clicked on it, read the hyperlink), they would see that your OP was in the NROL-108 thread.