Media accreditation is now open for a SpaceX Starlink mission from Space Launch Complex 40 (SLC-40) at Cape Canaveral Air Force Station in Florida. The launch is targeted for no earlier than December.
Then, a Falcon 9 is scheduled to launch the next set of Starlink internet constellation satellites on late December TBD.
https://spacenews.com/spacex-working-on-fix-for-starlink-satellites-so-they-dont-disrupt-astronomy/QuoteShotwell said the next batch has one satellite “where we put a coating on the bottom.” She noted that this is just an experiment and could not predict if it will work. “We’re do trial and error to figure out the best way to get this done,” said Shotwell. ... “It definitely changes the performance of the satellite, thermally. It’ll be some trial and error but we’ll fix it.”
Shotwell said the next batch has one satellite “where we put a coating on the bottom.” She noted that this is just an experiment and could not predict if it will work. “We’re do trial and error to figure out the best way to get this done,” said Shotwell. ... “It definitely changes the performance of the satellite, thermally. It’ll be some trial and error but we’ll fix it.”
So apparently SpaceX is trying to schedule a New Years Eve launch again (after a famous early example way back in.2013)....SFN shows this launch as on December 30, 11:40 pm EST = December 31, 04:40 UTC.
F3810/19 - 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 STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001040502 TO 2001040620 2001050440 TO 2001050538, 04 JAN 05:02 2020 UNTIL 05 JAN 05:38 2020. CREATED: 20 DEC 20:05 2019
Delayed NET jan4QuoteF3810/19 - 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 STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001040502 TO 2001040620 2001050440 TO 2001050538, 04 JAN 05:02 2020 UNTIL 05 JAN 05:38 2020. CREATED: 20 DEC 20:05 2019
Quote from: tehwkd on 12/21/2019 12:53 amDelayed NET jan4QuoteF3810/19 - 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 STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001040502 TO 2001040620 2001050440 TO 2001050538, 04 JAN 05:02 2020 UNTIL 05 JAN 05:38 2020. CREATED: 20 DEC 20:05 2019Are those UTC times for second stage reentry? If so then launch would be on the 3rd local time, 4th UTC.
Quote from: gongora on 12/21/2019 01:25 amQuote from: tehwkd on 12/21/2019 12:53 amDelayed NET jan4QuoteF3810/19 - 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 STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001040502 TO 2001040620 2001050440 TO 2001050538, 04 JAN 05:02 2020 UNTIL 05 JAN 05:38 2020. CREATED: 20 DEC 20:05 2019Are those UTC times for second stage reentry? If so then launch would be on the 3rd local time, 4th UTC.Ben Cooper on his page has it as January 3, ~10:45 pm Eastern (January 4, ~03:45 UTC).
ATLANTIC OCEAN - FLORIDA - CAPE CANAVERAL: EASTERN RANGE OP# A4230 FALCON 9 STARLINK v1.0-L2Eastern Range will be conducting hazardous operations surface to unlimited within portions of Warning Areas W137F, W138E, W139E,W140E/F, W122, W497A, W497B and the following hazard areas.From 2836 41.22N 8035 47.84WTO 2904N 8003WTO 2858N 7958WTO 2827 25.90N 8031 31.79WTO 2831 44.67N 8033 38.28W to beginningFrom 3201N 7649WTO 3348N 7523WTO 3342N 7424WTO 3244N 7431WTO 3140N 7630W beginningHazard periods for primary launch day and backup launch day;Primary launch day: 04 / 0309Z thru 04 / 0427Z Jan 20. Preferred T-0 is 0313Z.Backup launch day: 05 / 0247Z thru 05 / 0405Z Jan 20. Preferred T-0 is 0252Z.ATLANTIC OCEAN – FLORIDA – CAPE CANAVERAL: SPACE LAUNCH ZONES (VIRTUAL- AIS PRIVATE AID TO NAVIGATION)The U.S. Coast Guard has approved the use of a Virtual Automatic Identification System Private Aid to Navigation (V-AIS PATON) to mark arestricted navigation area during a space launch. The Coast Guard authorized the Space Exploration Technologies Corporation, better known asSpaceX, to use Virtual-AIS PATONs to inform mariners of non-charted restricted zones around launch areas. While the Coast Guard does notapprove Virtual-AIS PATON for all restricted areas, particularly charted ones, the space launch zones are non-charted, dynamic and temporary.Safety zones designed to keep vessels from entering the launch area while an active rocket launch is taking place.The Captain of the Port Jacksonville, FL will activate Safety Zone "B" located near Cape Canaveral, as described in 33 CFR 165.775(a)(2), 45minutes prior to the opening of the scheduled launch window. At that time, SpaceX will transmit Virtual-AIS aids marking the corners of theactive safety zone. The virtual-AIS aids will remain transmitting until the Captain of the Port Jacksonville has deactivated the safety zone. TheVirtual-AIS aids will be labeled:N 28° 48.8’ W 80° 28.9’ (28.813333 -80.481667) N1*X*33CFR165.775 (A) (2), MMSI# 993663027N 28° 29.7’ W 80° 18.9’ (28.495000 -80.315000) E2*X*33CFR165.775 (A) (2), MMSI# 993663028N 28° 29.7’ W 80° 31.6’ (28.495000 -80.526667) S3*X*33CFR165.775 (A) (2), MMSI# 993663029N 28° 40.1’ W 80° 38.4’ (28.668333 -80.640000) W4*X*33CFR165.775 (A) (2), MMSI# 993663030If a vessel equipped with AIS is determined to be entering the launch hazard area, an addressed safety message 14 with the text "REGULATEDAREA 33 CFR 165.775 ACTIVE STAY CLEAR" will be transmitted to the vessel. All provisions of the safety zone remain in effect; no person orvessel may enter, pass through or remain within the safety zone unless authorized by the Captain of the Port. Mariners are required to contactthe Coast Guard via VHF FM channel 16 to arrange for this authorization.
Issued NOTMAR Launch Hazard Areas of #SpaceX #Starlink v1.0-L2 mission. Droneship landing 629km downrange. Fairing capture attempt approx.730km downrange.. as previous Starlink launch. Stage2 Reentry Debris Area south of Australia on the second orbit. bit.do/LHA10
F3828/19 - ROCKET LAUNCH WILL TAKE PLACE REVIEW FLW RECEIVED FROM GOVERNMENT OF UNITED STATES OF AMERICA: HAZARDOUS OPS WILL BE CONDUCTED FOR ATMOSPHERIC RE-ENTRY AND SPLASHDOWN OF LAUNCH VEHICLE STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001040502 TO 2001040620 2001050440 TO 2001050558, 04 JAN 05:02 2020 UNTIL 05 JAN 05:58 2020. CREATED: 23 DEC 19:56 2019
The next SpaceX Falcon 9 rocket from Cape Canaveral is scheduled to launch the next set of Starlink internet constellation satellites from pad 40 on January 3 at 10:24pm EST. The launchwindow is instantaneous. The launch time gets 21-22 minutes earlier each day.
The corrected launch hazard has been issued. Backup of only a day.This launch will put another batch of #Starlink satellites into orbit, as part of @SpaceX constellation to bring internet and communications to the world.
Departure! Of Course I Still Love You is underway for the Starlink-L2 mission. The droneship is heading 629 km downrange.
Saw her passing our cruise ship. Fair winds and calm waters!
Recovery technicians are experimenting with a fairing half today. I can also confirm that Ms.Chief will not take part in the upcoming Starlink mission. GO Navigator will recover the fairing half from the water.
http://www.launchphotography.com/Delta_4_Atlas_5_Falcon_9_Launch_Viewing.htmlQuoteThe next SpaceX Falcon 9 rocket from Cape Canaveral is scheduled to launch the next set of Starlink internet constellation satellites from pad 40 on January 6 at 9:19pm EST. The launch window is instantaneous.
The next SpaceX Falcon 9 rocket from Cape Canaveral is scheduled to launch the next set of Starlink internet constellation satellites from pad 40 on January 6 at 9:19pm EST. The launch window is instantaneous.
It may be new year's day but the fleet is hard at work! Here's a look at OCISLY's progress since Monday.The droneship has deviated away towards calmer seas now that the launch date has slipped to NET Jan 7th at 02:19 UTC. There's no requirement to be at the LZ so early.
Departure! GO Quest and GO Navigator are underway for the Starlink L2 mission. GO Quest will support the droneship landing whilst GO Navigator will recover a fairing half from the water. Ms Chief will not take part in this mission because of minor damage sustained last time out
Haha Yess!! It is indeed 'Fairing Time'.
Scheduled Launch Date and Time (UTC)December 31, 2019 04:40January 4, 2020 03:24The launch time has regressed 19 minutes/day between the two data points. (76 minutes / 4 days = 19 min/d)If the change of launch time is a linear relation, then this can be extrapolated to future dates.
The launch time gets 21-22 minutes earlier each day.
Launch day probability of violating launch weather constraints: < 10%Primary concern(s): Cumulus Cloud RuleDelay day probability of violating launch weather constraints: 20%Primary concern(s): Cumulus Cloud Rule
F0023/20 - ROCKET LAUNCH WILL TAKE PLACE REVIEW FLW RECEIVED FROM GOVERNMENT OF UNITED STATES OF AMERICA: HAZARDOUS OPS WILL BE CONDUCTED FOR ATMOSPHERIC RE-ENTRY AND SPLASHDOWN OF LAUNCH VEHICLE STARLINK V1.0-L2 AND PARTICIPATING SUPPORT ACFT WI THE FOLLOWING AREAS: 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. SFC - UNL, 2001070357 TO 2001070515 2001080335 TO 2001080453, 07 JAN 03:57 2020 UNTIL 08 JAN 04:53 2020. CREATED: 02 JAN 19:09 2020
SpaceX Starlink status Jan 3, 6 PM: The #SpaceX #Falcon9 is now raised at sunset at #pad40 for 3rd @SpaceX #Starlink batch of 60 sats. Static fire test this weekend ahead of launch NET Jan 6, 919 PM ET
Fair winds and following seas GO Ms. Tree. They have begun the Starlink mission before the morning weather catches up to them. #SpaceXFleet #Starlink
Starlink L2 Fleet Update!GO Navigator is heading towards the Port of Morehead City, having peeled away from OCISLY.The droneship and accompanying ship GO Quest are not too far behind and could possibly follow the same.
Rough seas. Trying to avoid them whilst waiting for launch day
1/5 Using a pre-launch state vector provided by SpaceX, we used STK's HPOP to propagate the orbit and fit Supplemental TLEs (SupTLEs) for the first 8 hours following deployment. Data can be found at https://celestrak.com/NORAD/elements/supplemental/.2/5 Data assumes nominal launch on Jan 7 at 02:19:21 UTC and deployment at 03:20:32.598 UTC. TLEs are produced for the full stack and for a single object to provide a range of drag characteristics....5/5 Visualization of the orbit--which can be viewed in real-time mode--is available via the globe icon next to the TLE data. A link to a short YouTube video showing how to use Orbit Viz can be found at https://youtube.com/watch?v=SmI5gx7ifS0.
Is this the first time since Amos6 that SpaceX has static fired the booster WITH the payload attached?
Quote from: Brian45 on 01/04/2020 06:20 pmIs this the first time since Amos6 that SpaceX has static fired the booster WITH the payload attached?Starlink 0.9 also did a static fire with payload attached.
Quote from: ThomasGadd on 01/04/2020 06:56 pmQuote from: Brian45 on 01/04/2020 06:20 pmIs this the first time since Amos6 that SpaceX has static fired the booster WITH the payload attached?Starlink 0.9 also did a static fire with payload attached.DM-1 as well IIRC.
Quote from: Tommyboy on 01/04/2020 07:15 pmQuote from: ThomasGadd on 01/04/2020 06:56 pmQuote from: Brian45 on 01/04/2020 06:20 pmIs this the first time since Amos6 that SpaceX has static fired the booster WITH the payload attached?Starlink 0.9 also did a static fire with payload attached.DM-1 as well IIRC.As well as Falcon Heavy Demo and IIRC STP-2.
Rare to see a night launch pic from an airplane.
Here you go - #SpaceX #StarLink from about 120 miles north of Cape Canaveral. Love me a night launch just for this type of shot!
Once we have individual SupTLEs and associated IDs, @SpaceX has reported that their “DarkSat” will be STARLINK-1130.
SpaceX: Ms. Tree was unsuccessful in catching the payload fairing half.
Did anyone else notice some verbiage about Space Force upon liftoff from the SpaceX web cast?
It is interesting that this is the third time we have a loss of video exactly when deployment occurs.
Sounds like they’re enjoying their new name.
We are live! Join us as we watch history in the making. First launch of US Space Force!
Why is it so hard to catch the fairing? Is it the wind or something?
Just for reference...https://twitter.com/SpcPlcyOnline/status/1214369681412435968QuoteSounds like they’re enjoying their new name.edit..forgot another quote..QuoteWe are live! Join us as we watch history in the making. First launch of US Space Force!
Quote from: tleski on 01/07/2020 02:30 amIt is interesting that this is the third time we have a loss of video exactly when deployment occurs.I'm beginning to believe the tension rods/separation system is proprietary which is why the video cuts.
Despite the slightly higher satellite deployment altitude, SpaceX appear to have performed essentially the same launch profile for their first two Starlink 1.0 missions. I can't split them.
This was the 48th Falcon 9 launch from SLC 40, not including the AMOS 6 accident. Titan 3C/34D/4 flew 55 times from this site from 1965 to 2005. Soon, probably this year, Falcon 9 will surpass the Titan numbers (after only a decade of service). (Atlas 5 has long-surpassed Titan at SLC 41 - there've been 66 Atlas 5 launches versus only 27 for Titan 3C/3E/4.) - Ed Kyle
Latest @SpaceX ephemerides are available for 57 of the 60 latest #Starlink satellites, including STARLINK-1130 (DARKSAT): https://celestrak.com/NORAD/elements/supplemental/table.php?tleFile=starlink&title=Starlink&orbits=0&pointsPerRev=90&frame=1
Quote from: tleski on 01/07/2020 02:30 amIt is interesting that this is the third time we have a loss of video exactly when deployment occurs.Yeah, seriously, I'd rather they just say it's proprietary or whatever instead of saying the transmission cuts.One final possibility, though - haven't all three Starlink launches so far been launched in exactly the same initial orbit? Is it possible that there really is a coverage blackout at exactly that point? Maybe someone could check the ground station callouts to get a sense if that's possible?
Quote from: thirtyone on 01/07/2020 03:58 pmQuote from: tleski on 01/07/2020 02:30 amIt is interesting that this is the third time we have a loss of video exactly when deployment occurs.Yeah, seriously, I'd rather they just say it's proprietary or whatever instead of saying the transmission cuts.One final possibility, though - haven't all three Starlink launches so far been launched in exactly the same initial orbit? Is it possible that there really is a coverage blackout at exactly that point? Maybe someone could check the ground station callouts to get a sense if that's possible?They haven't lost telemetry, there was a clear callout for confirmation of tension rod release during the video cutout, it is possible that the spinning of the stage puts the high data rate antenna out of position at the moment of deployment. I agree 3 times in a row is getting suspicious. It might really be due to unintended datalink issues, but it is not coincidence whether intentional or not.What I would like to know (and if there was an explanation, I missed it) why do they wait 15 minutes between the final burn and separation? Typically this isn't immediate, as the stage does final checks and changes to the desired deployment orientation, but this seems unusually long, and has been consistent for each Starlink launch.
Quote from: meberbs on 01/07/2020 06:54 pmQuote from: thirtyone on 01/07/2020 03:58 pmQuote from: tleski on 01/07/2020 02:30 amIt is interesting that this is the third time we have a loss of video exactly when deployment occurs.Yeah, seriously, I'd rather they just say it's proprietary or whatever instead of saying the transmission cuts.One final possibility, though - haven't all three Starlink launches so far been launched in exactly the same initial orbit? Is it possible that there really is a coverage blackout at exactly that point? Maybe someone could check the ground station callouts to get a sense if that's possible?They haven't lost telemetry, there was a clear callout for confirmation of tension rod release during the video cutout, it is possible that the spinning of the stage puts the high data rate antenna out of position at the moment of deployment. I agree 3 times in a row is getting suspicious. It might really be due to unintended datalink issues, but it is not coincidence whether intentional or not.What I would like to know (and if there was an explanation, I missed it) why do they wait 15 minutes between the final burn and separation? Typically this isn't immediate, as the stage does final checks and changes to the desired deployment orientation, but this seems unusually long, and has been consistent for each Starlink launch.IIRC didn't they say on Starlink V0.9 they expect to lose video coverage due to going to a place with bad connection. I agree 15 minutes is quite long especially seeing how they've done it a lot now. I have a feelings it's done intentionally there to avoid having to intentionally cut feed and also hide deployment. Whether to hide company secrets, or avoid bad PR by releasing two bits of debris, I don't know.
As for the fifteen minutes between the burn and deployment, there's all sorts of stuff that needs to happen until the stack is spun up properly. The whole thing weighs over 20 tons, with 30 joints in a row at one end, sloshing fuel in the other and not a lot of maneuvering thrust.
https://twitter.com/TSKelso/status/1214562257889136645QuoteLatest @SpaceX ephemerides are available for 57 of the 60 latest #Starlink satellites, including STARLINK-1130 (DARKSAT): https://celestrak.com/NORAD/elements/supplemental/table.php?tleFile=starlink&title=Starlink&orbits=0&pointsPerRev=90&frame=1
Quote from: gongora on 01/07/2020 04:20 pmhttps://twitter.com/TSKelso/status/1214562257889136645QuoteLatest @SpaceX ephemerides are available for 57 of the 60 latest #Starlink satellites, including STARLINK-1130 (DARKSAT): https://celestrak.com/NORAD/elements/supplemental/table.php?tleFile=starlink&title=Starlink&orbits=0&pointsPerRev=90&frame=1Just in case someone mistaken this to mean 3 out of 60 didn't work, the celestrak page now has data for all 60 Starlink satellites, just to go the link in the tweet and search for "2020-001".
Quote from: su27k on 01/09/2020 03:42 amQuote from: gongora on 01/07/2020 04:20 pmhttps://twitter.com/TSKelso/status/1214562257889136645QuoteLatest @SpaceX ephemerides are available for 57 of the 60 latest #Starlink satellites, including STARLINK-1130 (DARKSAT): https://celestrak.com/NORAD/elements/supplemental/table.php?tleFile=starlink&title=Starlink&orbits=0&pointsPerRev=90&frame=1Just in case someone mistaken this to mean 3 out of 60 didn't work, the celestrak page now has data for all 60 Starlink satellites, just to go the link in the tweet and search for "2020-001".2020-001BM 71144 STARLINK-1144 90.40 53.00 295 294 0.0001000 N/A 0.202019-029A 44235 STARLINK-31 95.23 53.00 531 529 0.0001459 0.21This data is prelaunch, supplemental info, I don't think SpaceX reported the actual positions yet.
Anybody know what happened to the fairing half they were trying to catch? I thought they were going to try to catch one and fish the other out of the water. I saw the comment about a parafoil hanging from one of the arms but wouldn't they still try to fish the second one out of the water if they missed catching it?
Quote from: sferrin on 01/10/2020 10:59 amAnybody know what happened to the fairing half they were trying to catch? I thought they were going to try to catch one and fish the other out of the water. I saw the comment about a parafoil hanging from one of the arms but wouldn't they still try to fish the second one out of the water if they missed catching it? It may have hit the water too hard but there's no way to know unless SpaceX release something.
Seeing the parachute was in the net ...
Quote from: AndrewRG10 on 01/11/2020 12:34 amSeeing the parachute was in the net ...I have utterly failed in finding any photos of the latest attempt. Any links to the chute in the net?TIA, and have a good one,Mike
Have the satellites spread out enough yet for the darksat to be individually identified? Would be interesting to know how much the reflection is being cut down. Of course, the real result won't be known until it reaches final altitude.
...would it make sense to have a single tracking thread for all of Starlink?
I have several threads for Starlink that keep hovering near the top of the list because of tracking updates. Instead of having these tracking updates spread across multiple threads, which is going to continue to multiply throughout the year, would it make sense to have a single tracking thread for all of Starlink? That would let the individual launch threads go quiet and avoid having two dozen of the update threads sitting on top of the missions page. I'm not sure if the combined thread belongs in "missions" or "general", but I feel like having it spreads across potentially dozens of threads is not going to work long term.
The main launch manifest thread has a table of recent and future launches. Would it make sense for a Starlink tracking thread to maintain a list of satellites showing details like launch date, status, and plane (if we can come up with a numbering scheme)? The list would get rather long once once this years slate of launches are complete but it might give a good overview of the constellation.
