NASASpaceFlight.com Forum
SpaceX Vehicles and Missions => SpaceX Falcon Missions Section => Topic started by: Jansen on 03/04/2021 10:26 am
-
Discussion thread for Starlink v1.0 Launch 23
NSF Threads for Starlink v1.0 L23: Discussion (https://forum.nasaspaceflight.com/index.php?topic=53237.0)
NSF Articles for Starlink v1.0 L23:
https://www.nasaspaceflight.com/2021/04/spacex-launch-starlink-l23/
Launched successfully April 7, 2021 at 12:34pm EDT (1634 UTC) on Falcon 9 (booster 1058.7) from CCSFS SLC-40. ASDS landing on OCISLY, towed by tugboat Finn Falgout. Recovery support ship was GO Quest. Fairing recovery of one half from the water by MV Shelia Bordelon.
Payload: A batch of 60 Starlink satellites. Expected deployment orbit of approximately 280x262 km.
The Falcon 9 first stage rocket booster supporting this mission previously supported launch of NASA astronauts Bob Behnken and Doug Hurley to the International Space Station, ANASIS-II, CRS-21, Transporter-1, and two 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 supported launch of AMOS-17 and two Starlink missions, and the other previously supported a Starlink mission.
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 to near global coverage of the populated world by 2021. Additional information on the system can be found at starlink.com.
-
1897-EX-ST-2020 (https://apps.fcc.gov/oetcf/els/reports/STA_Print.cfm?mode=current&application_seq=104487) Starlink RF Mission 6-1 STA application
1897-EX-ST-2020 (https://apps.fcc.gov/els/GetAtt.html?id=265974) Starlink RF Mission 6-1 Grant
-
Cross-post and bump; my bold:
http://www.launchphotography.com/Launch_Viewing_Guide.html Updated March 3
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the twentieth Starlink internet satellite batch from pad 39A on March 4 at either 3:24am or 5:42am EST. Then, a Falcon 9 will launch the twenty-first Starlink batch from pad 40 on March 7 at 10:41pm EST. The launch time for Starlink missions gets approx. 20-22 minutes earlier each day. A Falcon 9 will launch the twenty-second Starlink batch from pad 39A on March TBD. Upcoming launches include Starlink batches on March TBD. The next Crew Dragon carrying four astronauts to the International Space Station is targeted for late April around 6am EDT. Sunrise is 6:49am. The launch time gets 22-26 minutes earlier each day.
-
There is sufficient boosters available for a launch L21 ~18 Mar (39A) and L22 on or just before 1 Apr (40).
But the next booster 1049.9 would not be available L2L of 28 days NET 2 Apr but more likely 1049 would not be up and ready for another launch until 35-45 days or 7-17 Apr. Making it possible that it would likely launch on 10 Apr on (40) 10 days after launching L22 on (40) very late March.
But also by 6 Apr 1058.7 at 28 days L2L would possibly become available. So 2 boosters for L23 is likely to be available for a launch in first half of April. Because of the complication of launching early enough on 39A prior to the April 22 date for Crew 2 to keep from causing a problem and booster unavailability likely until April 10 or even later.
It is likely only one launch from 39A (Crew 2 ) would occur in April. But it is likely that a second launch L24 on 40 would happen 24 April or later. By then several boosters would be available. May launch schedule will not be as constrained and would likely have as many as 3 launches of Starlink (L25, L26 and L27) on both 39A and 40. With only 2 launches using the booster pool in April there would be 2 booster available at the beginning of May with a third by the middle to late May.
[zubenelgenubi: Manifest discussion cross-posted and continues in dedicated thread here (https://forum.nasaspaceflight.com/index.php?topic=52191.msg2201279#msg2201279).]
-
It might be better to discuss booster assignments in the manifest discussion thread rather than spreading the conversation over multiple mission threads.
-
It might be better to discuss booster assignments in the manifest discussion thread rather than spreading the conversation over multiple mission threads.
Sorry got carried away with other impacts to other launches by boosters in April and May. Should have stopped with the first paragraph. Wanted to show how booster availability and confluence of pads availability to show that the best dates for L23 would likely be and that L23 either early mid April or in late April. Booster availability is the main problem for L23 launch date for April.
-
https://spaceflightnow.com/2021/03/11/spacex-adds-more-satellites-to-starlink-internet-fleet/
SpaceX has at least two more Starlink missions scheduled for launch before the end of March, and possibly more.
Not sure if they can get B1049 refurbished in time, but I won’t bet against SpaceX.
-
My gosh, that would be 5 flights, 300 satellites in 1 calendar month.
Global Starlink service roll out, here we come.
-
A 28 day L2L for 1049 for a launch date of 1 April would be a real April fools joke on the rest of us. Because we would have such a hard time believing that SpaceX was able to cycle 1049 that fast. But 28 day L2L's are possible. Just if that is applicable to 1049 or not is something to be seen.
-
https://twitter.com/nextspaceflight/status/1370400469479161860
Based on the LV integration timeline, this is probably the earliest launch we could see B1063.
-
I would say that we're waiting to hear if this launch will be conducted from LC-39A in the near future, before Crew-2 launch preparations "take custody" of the launch complex.
Or, if this launch will take place from SLC-40 after the Flight 22 launch (currently March 24) from same, followed by a pad recycle.
I am also interested to learn what mission B1063 will be assigned to.
-
I would say that we're waiting to hear if this launch will be conducted from LC-39A in the near future, before Crew-2 launch preparations "take custody" of the launch complex.
Or, if this launch will take place from SLC-40 after the Flight 22 launch (currently March 24) from same, followed by a pad recycle.
I am also interested to learn what mission B1063 will be assigned to.
The NASA Commercial Crew launch workflow takes about 15-20 days at a pad, so they have a bit of time.
-
If you can figure out when 1063 arrived (should have got there the 16/17). And where it was stashed. Some of the answers for L23 could be obvious. It takes about 14 days to prepare a booster and launch it. Checkout, US mate, TL mate, Payload mate, move to pad, and launch. 14 days from the 17th is 31 Mar. Having a couple of extra days for weather or other difficulties slips would be a good thing else they would have to de-mate from the TL to then be able to finish the process with the 1061 at around Crew 2 T-10 days.
Else if launched from LC40 which could be as early as 2 Apr and still could be with 1063. 9 days L2L for the pad cycle.
Regardless the first week of April looks good for L23.
-
State of play on the Space Coast for the immediate future:
April 7 NET very late March or earlyApril - Starlink flight 24 (x60) [v1.0 L23] - Falcon 9-113 (1058.7 S) - Canaveral SLC-40 - 16:34
(Starlink: launch 20-22 minutes earlier/day)
NET April 22 - USCV-2: Dragon v2 Crew 2 - Falcon 9 (B1061.2 S) - Kennedy LC-39A - 10:11
(ISS flights: launch 22-26 minutes earlier/day)
April Q2 - Starlink flight 25 (x60) [v1.0 L24] - Falcon 9 (S) - Canaveral SLC-40 / Kennedy LC-39A?
(Starlink: launch 20-22 minutes earlier/day)
April Q2 - Starlink flight 26 (x60) [v1.0 L25] - Falcon 9 (S) - Canaveral SLC-40 / Kennedy LC-39A?
(Starlink: launch 20-22 minutes earlier/day)
April? Q2 - Starlink flight 27 (x60) [v1.0 L26] - Falcon 9 (S) - Kennedy LC-39A / Canaveral SLC-40
(Starlink: launch 20-22 minutes earlier/day)
Changes on March 13th
Changes on March 24th
Changes on March 26th
Changes on April 4th
zubenelgenubi
-
Now officially NET April per Ben Cooper. No big surprise there.
http://www.launchphotography.com/Launch_Viewing_Guide.html
-
https://spaceflightnow.com/2021/03/24/spacex-launches-25th-mission-to-build-out-starlink-internet-network/
SpaceX’s next Falcon 9 launch is scheduled for early April to deliver another batch of Starlink satellites to orbit, continuing a rapid-fire cadence of missions
-
SpaceFlight Now has details:
April 7
Starlink V1.0-L23
Launch time: 1634 GMT (12:34 p.m. EDT)
Launch site: SLC-40, Cape Canaveral Space Force Station, Florida
-
SpaceFlight Now has details:
April 7
Starlink V1.0-L23
Launch time: 1634 GMT (12:34 p.m. EDT)
Launch site: SLC-40, Cape Canaveral Space Force Station, Florida
Is the pad confirmed or is it an assumption based on non-interference with Crew-2 activities?
-
SpaceFlight Now has details:
April 7
Starlink V1.0-L23
Launch time: 1634 GMT (12:34 p.m. EDT)
Launch site: SLC-40, Cape Canaveral Space Force Station, Florida
Is the pad confirmed or is it an assumption based on non-interference with Crew-2 activities?
Verified by multiple sources
-
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the Starlink 23 internet satellite
batch from pad 40 on April 7 at 12:34pm EDT
Confirmations from Ben Cooper and Next SpaceFlight.
-
NOTMARs for launch NET 07 Apr 16:34 UTC
Alternative launch days in approximate times: 08 Apr 16:12 | 09 Apr 15:51 | 10 Apr 15:29 | 11 Apr 15:08 | 12 Apr 14:46 | 13 Apr 14:24 | 14 Apr 14:03 | 15 Apr 13:41 |
020846Z APR 21
NAVAREA IV 279/21(11,26).
WESTERN NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
071530Z TO 071724Z APR, ALTERNATE
081530Z TO 081709Z, 091530Z TO 091654Z,
101530Z TO 101654Z, 111403Z TO 111701Z,
121341Z TO 121639Z, 131320Z TO 131618Z,
141258Z TO 141556Z AND 151236Z TO 151534Z APR
IN AREAS BOUND BY:
A. 28-39-14N 080-37-51W, 29-07-00N 080-05-00W,
29-00-00N 079-57-00W, 28-34-00N 080-24-00W,
28-30-07N 080-32-51W.
B. 31-27-00N 077-29-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-15-00N 077-17-00W.
2. CANCEL THIS MSG 151634Z APR 21.
020903Z APR 21
HYDROPAC 1005/21(61,75,76).
SOUTHERN INDIAN OCEAN.
DNC 03, DNC 04, DNC 05.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
071740Z TO 071912Z APR, ALTERNATE
081740Z TO 081857Z, 091740Z TO 091842Z,
101740Z TO 101842Z, 111613Z TO 111849Z,
121551Z TO 121827Z, 131530Z TO 131806Z,
141508Z TO 141744Z AND 151446Z TO 151722Z APR
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 151822Z APR 21.
Map of Launch Hazard Areas (https://www.google.com/maps/d/viewer?hl=en&mid=1CCc2GEEGG08j6fMUrkBEbDA5QFscr2bD&ll=30.749966946666923%2C-76.42617895925308&z=7), with booster landing ~615km downrange, fairing recovery ~667km downrange and S2 reentry south of Australia, implied double S2 burn launch profile again.
-
twitter.com/spacexfleet/status/1378414580351766537
Of Course I Still Love You has departed for the next Starlink mission. Tug Finn Falgout is towing the droneship 633 km downrange.
Recovery Details: SpaceXFleet.com/next
https://twitter.com/nasaspaceflight/status/1378415337788612611
Some clips. I like how it has its own Starlink dish.
-
Tim Dodd is reporting B1058.7
https://everydayastronaut.com/starlink-23/
-
Tim Dodd is reporting B1058.7
Tim Dodd has often been wrong about booster assignments. I’d like to see confirmation from Next SpaceFlight.
-
Tim Dodd is reporting B1058.7
Tim Dodd has often been wrong about booster assignments. I’d like to see confirmation from Next SpaceFlight.
Me too. No offense to Tim, though.
-
A TFR has just posted for April 8th. This may have slipped a day to the right unless it's just a backup-TFR that got posted before the main one:
The backup TFR did indeed get posted before the primary one, all is well.
https://twitter.com/SpaceTfrs/status/1378698816573034498?s=20
https://twitter.com/SpaceTfrs/status/1378691985758912513?s=20
-
L-3 launch weather forecast is 90% GO
-
NextSpaceflight confirms B1058.7 !
-
For those counting, an on-time launch would see B1058 narrowly miss B1060's 27d 4h record with a 27d 8h turnaround.
-
twitter.com/spacexfleet/status/1379040654945292288
Fairing recovery ship Shelia Bordelon has just departed from Port Canaveral for the upcoming Starlink mission. This will be the second mission for the pink and blue new recruit.
Photos via NSF YT: youtube.com/channel/UCSUu1…
https://twitter.com/spacexfleet/status/1379040795123126275
And some amazing video footage as well!
-
L-2 weather forecast: 90% for Primary, 80% for Backup #1.
-
https://twitter.com/TSKelso/status/1379280865058938880
-
L-1 weather forecast: Primary Day has improved to >90% 'Go' but now has a moderate upper-level wind shear risk. Backup Day #1 has improved to 90% 'Go'.
-
SpaceX official launch website has been updated.
https://www.spacex.com/launches/index.html
SpaceX is targeting Wednesday, April 7 for launch of 60 Starlink satellites from Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station in Florida. The instantaneous window is at 12:34 p.m. EDT, or 16:34 UTC, and a backup opportunity is available on Thursday, April 8 at 12:12 p.m. EDT, or 16:12 UTC.
The Falcon 9 first stage rocket booster supporting this mission previously supported launch of NASA astronauts Bob Behnken and Doug Hurley to the International Space Station, ANASIS-II, CRS-21, Transporter-1, and two 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 supported launch of AMOS-17 and two Starlink missions, and the other previously supported a Starlink mission.
1058.7 confirmed (no surprise), it will be a 4th and a 2nd flight for the fairing halves.
https://www.youtube.com/watch?v=Uy9Jn-3vuPs
-
https://twitter.com/SpaceX/status/1379555200722038786
-
"Press kit" capture with OCR
-
Some stats from https://www.boostertracker.com/
-
I don’t get the difference between the second and third stat above. How is “re-flight of a booster” different than “flight with a flight-proven booster.”
-
I don’t get the difference between the second and third stat above. How is “re-flight of a booster” different than “flight with a flight-proven booster.”
Pretty sure this was asked and answered somewhere before (most likely on L22 ), something to do with FH boosters counting as reflight of a booster but not counting as a F9 flights
Edit: link to explanation in the L22 thread https://forum.nasaspaceflight.com/index.php?topic=53068.msg2209914#msg2209914 (see a few additional posts there on the subject)
-
I don’t get the difference between the second and third stat above. How is “re-flight of a booster” different than “flight with a flight-proven booster.”
Pretty sure this was asked and answered somewhere before (most likely on L22 ), something to do with FH boosters counting as reflight of a booster but not counting as a F9 flights
Edit: link to explanation in the L22 thread https://forum.nasaspaceflight.com/index.php?topic=53068.msg2209914#msg2209914 (see a few additional posts there on the subject)
I think more, an FH with two used side boosters is one flight with a flight proven booster, but would be two re-flights of a booster. The wording is not perfect in any case.
I blame the Brits. They invented this language.
-
Visual mission profile by ElonX.net
-
New article:
https://twitter.com/TGMetsFan98/status/1379780372691570690
Today's Starlink mission will utilize a booster making its seventh flight and two flight proven fairing halves.
Lee Kanayama (@Falcon_1e) previews:
https://www.nasaspaceflight.com/2021/04/spacex-launch-starlink-l23/
-
As I understand it, they are calling the Falcon 9 first stage a booster, regardless of if it is used as Falcon 9 (single stick) or as a side booster to Falcon Heavy. And the side boosters for 2 FH launches have been flight proven. So 55 flight proven Falcon 9 launches (single stick, data point 2 on the list) and 4 flight proven Falcon 9 cores (boosters) used as the side boosters on FH, gives 59 Flight proven booster launches total (data point 3 on the list).
Respectfully,
James
-
I don’t get the difference between the second and third stat above. How is “re-flight of a booster” different than “flight with a flight-proven booster.”
The word 'booster' is the source of confusion. Too many people say booster meaning first stage. A booster is a helper, such as a SRB, so a F9 has no booster and a FH has two.
It seems more than a bit late to try to make that distinction. Practically everyone is the community is referring to the first stage of the Falcon 9 as, at different times, but by the same person, either the first stage or the booster. And it's already the case that the SuperHeavy is being described as a booster.
And then as a point of logic, distinguishing between the first stage of the Falcon Heavy and its boosters seems a little awkward given that they are almost the same thing. And then it's claimed, although we haven't seen it happen yet, that the boosters of the Falcon Heavy can be readily converted into first stages for the Falcon 9.
And then to add to the confusion, the Russians have all along named their 'boosters' first stages and their second stages first stages. So if we followed the Russian terminology, the Falcon Heavy's two side boosters are first stages and the center core is the second stage.
And then finally given the generalized meaning of the word booster, it does seem more descriptive of what a reusable first stage, or booster, is doing. So I'm for one not unhappy to see this shift in meaning.
-
Booster 1058.7 is vertical
-
https://twitter.com/emrekelly/status/1379811188058509314
Good morning from Kennedy Space Center, where we can see a SpaceX Falcon 9 rocket on the pad at nearby Launch Complex 40. Liftoff of 24th Starlink set for 1234 ET.
Slight return to normalcy here. MLP rolling around, parking lots fuller than usual, KSCVC tour buses out and about.
-
https://youtu.be/9DNxd-vqkzA
-
https://youtu.be/8-qMAuWzbM0
Edit to add: NSF now live
-
NSF live coverage has begun
-
https://twitter.com/emrekelly/status/1379825386289266693
-
LD go for prop load
-
https://twitter.com/spacex/status/1379828046333505536
T-30 minutes until launch of Starlink; Falcon 9 and weather are looking good for flight. Webcast will go live ~15 minutes before liftoff → spacex.com/launches
-
https://twitter.com/NASASpaceflight/status/1379830330895515648
-
SpaceX coverage has begun, with Jessie Anderson hosting.
-
https://twitter.com/spacexfleet/status/1379833063220334592
Shelia Bordelon received her first shoutout on the launch webcast, note carefully wording as a "contracted recovery vessel"
Further backing my speculation that Shelia is not the permanent recovery ship going forward.
-
Strongback retraction
-
Falcon in startup
-
https://twitter.com/NASASpaceflight/status/1379835141577715713
-
Stage separation and fairing separation, no onboard video
-
No onboard video came as a surprise to the ost so maybe wasnt planned
-
No onboard vid, good telemetry still however.
-
No video from either stage... seems a bit odd.
-
Entry burn successful
-
Video back
-
Booster stuck the landing
-
and boy was the video good when it came back
maybe they trying something new
-
https://twitter.com/NASASpaceflight/status/1379837307587530760
-
Live coverage resumes in 34 mins
-
and boy was the video good when it came back
maybe they trying something new
I suspect the loss of video was an issue on the receiving end since both stage feeds came back at once.
-
and boy was the video good when it came back
maybe they trying something new
I suspect the loss of video was an issue on the receiving end since both stage feeds came back at once.
Was there an AOS callout right around that time?
I also wonder if the support ships had tracking and were relaying it through starlink, based on getting video all the way down to the deck of OCISLY.
-
No video from either stage... seems a bit odd.
S1 trajectory and re-entry profile was substantially different from previous instances.
Topped out about 126km + ~14km over usually and entry burn ended at ~100-200 km/h faster around 6000km/h
-
https://twitter.com/trevormahlmann/status/1379838805725872129
The steamroller rolls on, SpaceX flies its 10th mission of 2021🚀 (click/tap for full image)
📸 for @ArsTechnica - my 63rd launch!! (holy cow)
⚙️/⬇️/🖼: tmahlmann.com/photos/Rockets…
-
I also wonder if the support ships had tracking and were relaying it through starlink, based on getting video all the way down to the deck of OCISLY.
Very likely, since the video feed from the drone ship was 2-3 seconds behind. (if it was routed through the drone ship the two video feeds should be synced)
-
Interesting, the original SpaceX host, Jessie Anderson, disappears about 5:30 into launch and is replaced by another young lady. High turnover rate?
-
Good orbit
Back at T+01:03:00
-
https://twitter.com/NASASpaceflight/status/1379846678044377093
-
Here for Steve: (Also SES-2 and good orbit)
-
Too many people were trying to intercept SpaceX telemetry (and publish it on the twitters)
Probably led to the issues with camera views
https://twitter.com/r2x0t/status/1379843322152431622
Now these same people want to try to decrypt it
-
Nice profile of the Inspiration4 crew before launch and outline of their respective roles during the mission.
-
Too many people were trying to intercept SpaceX telemetry (and publish it on the twitters)
Probably led to the issues with camera views
https://twitter.com/r2x0t/status/1379843322152431622
Now these same people want to try to decrypt it
I *seriously* doubt that had anything whatsoever to do with the SpaceX video feed issues at launch and continuing through the first few minutes of flight. Otherwise you’re claiming SpaceX can’t decrypt their own video feed. Bear in mind that serious video feed encryption is literally consumer-grade technology at this point.
-
Too many people were trying to intercept SpaceX telemetry (and publish it on the twitters)
Probably led to the issues with camera views
https://twitter.com/r2x0t/status/1379843322152431622
Now these same people want to try to decrypt it
I *seriously* doubt that had anything whatsoever to do with the SpaceX video feed issues at launch and continuing through the first few minutes of flight. Otherwise you’re claiming SpaceX can’t decrypt their own video feed. Bear in mind that serious video feed encryption is literally consumer-grade technology at this point.
If they implement new encryption in the feed, the receiving end must be on the same page, so it's at least possible that this is what caused the missing video, it took them a few minutes for someone to walk the key on a usb stick over to the video desk. (not saying what happened, just saying it's plausible)
-
I've done written too much software to discount it. Adding an extra feature, which "should" work, but is low priority and isn't tested "live" until the rocket is in the air---I 100% believe that someone discovered in real time the 1 remaining place in the production video pipeline that didn't have the proper decryption key provisioned. I wouldn't expect this to recur, once fixed it's fixed.
-
Good deployment
-
https://twitter.com/NASASpaceflight/status/1379851301425704961
-
Booster 1058 is really a work horse, it could get to 8 flights in under 12 months.
That's simply amazing.
Great job SpaceX making the launch and deployment of 60 satellites look so routine!
-
https://twitter.com/SpaceX/status/1379851411840593925
SpaceX confirms deployment successful
-
Too many people were trying to intercept SpaceX telemetry (and publish it on the twitters)
Probably led to the issues with camera views
https://twitter.com/r2x0t/status/1379843322152431622
Now these same people want to try to decrypt it
I *seriously* doubt that had anything whatsoever to do with the SpaceX video feed issues at launch and continuing through the first few minutes of flight. Otherwise you’re claiming SpaceX can’t decrypt their own video feed. Bear in mind that serious video feed encryption is literally consumer-grade technology at this point.
SpaceX also build their own cameras, and some mission they don't work... Also comparing consumer-grade radio links to ones in the orbit is like me saying my tractor has turbomachinery in it and it's very reliable; why can't SpaceX build as reliable Raptor turbopumps.
-
I've done written too much software to discount it. Adding an extra feature, which "should" work, but is low priority and isn't tested "live" until the rocket is in the air
As a software developer myself, I can concur. Losing a single 1st or 2nd stage camera could be down to hardware or telemetry issues. Losing both was suspicious, regaining both at virtually the same time even more so, especially as both stages are separated a fair bit by that point in time for tracking purposes. Somewhere along, in the pipeline chain, there was a snafu regarding this change, that much should be fairly evident. Wouldn't even be the first time this kind of snafu happened. First FH launch had 2 copies of the same side booster camera feed. The mission ground track visualization was delayed many seconds on at least one FH launch, etc.
Oh well, I was waiting for this to happen - them encrypting the streams - despite some people arguing they wouldn't as there would be no point in doing so. After all, if they wanted people seeing prolonged shots of the LOX tank, they wouldn't have been cutting away from live video any time the onboard feed switched to that camera.
-
F9 "Tokyo Drift" ;D (see image)
It is interesting to watch the seconds after this to see the rocket pretty quickly change attitude to prepare for stage separation.
-
Chris G said on the stream at 25:30 for this launch that you can't launch Starship to a polar orbit for Starlink launches. I'm pretty sure that's false. Boca Chica juts out a decent amount into the Gulf of Mexico and the coastline south of that location is almost due south so a dogleg wouldn't even be needed much. Starship should be able to launch polar starlink launches from that location without issue.
Chris G also gave out some other misinformation and stated that the facility at Boca Chica is being designed to "not attract lightning strikes" which is fundamentally impossible. Lightning strikes strike anything tall, no matter the material. Before it became common to put lightning rods on buildings, brick and wooden buildings used to burn down because of lightning strikes hitting them. He also compared to airlines saying airlines are designed to not attract lightning strikes which is also incorrect. Lightning doesn't strike airliners much because they're not grounded to the ground.
-
The S2 view appeared at T+7:07 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1564s), and the S1/S2 split screen at T+07:23 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1580s), but the Booster camera was visible on the Mission Control screen seen behind Youmei Zhou (Dragon Propulsion Engineer and today's launch co-host) when they cut to her at T+06:33 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1530s), with the Entry Burn Startup visible 10 seconds later, though they cut away from her at T+06:56 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1553s) before the burn was complete.
It might have been just a production issue, with the onboard camera feeds not initially available to the webcast video engineer.
SpaceX Falcon 9 B1058-7 lands on OCISLY.
Great onboard view for this one!
...
Yes, and at T+08:05 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1622s), OCISLY can be seen sneaking into view at the inboard left corner of the left grid fin.
-
Chris G said on the stream at 25:30 for this launch that you can't launch Starship to a polar orbit for Starlink launches. I'm pretty sure that's false. Boca Chica juts out a decent amount into the Gulf of Mexico and the coastline south of that location is almost due south so a dogleg wouldn't even be needed much. Starship should be able to launch polar starlink launches from that location without issue.
I doubt it. The extended overflight over Mexico would be a much risker than a narrow Cuba and Panama flyover. Perhaps when Starship flights are well established, but that might be a while. But this not the topic for this discussion I think.
-
Chris G said on the stream at 25:30 for this launch that you can't launch Starship to a polar orbit for Starlink launches. I'm pretty sure that's false. Boca Chica juts out a decent amount into the Gulf of Mexico and the coastline south of that location is almost due south so a dogleg wouldn't even be needed much. Starship should be able to launch polar starlink launches from that location without issue.
I doubt it. The extended overflight over Mexico would be a much risker than a narrow Cuba and Panama flyover. Perhaps when Starship flights are well established, but that might be a while. But this not the topic for this discussion I think.
It wouldn't overfly Mexico until near the southern part of Mexico, when the vehicle is close to orbital velocities. The IIP wouldn't be over land for very long. (Starlink doesn't even technically need a 90 degree inclination to have full coverage of the South Pole either.) There's also no need for downrange recovery.
-
The S2 view appeared at T+7:07 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1564s), and the S1/S2 split screen at T+07:23 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1580s), but the Booster camera was visible on the Mission Control screen seen behind Youmei Zhou (Dragon Propulsion Engineer and today's launch co-host) when they cut to her at T+06:33 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1530s), with the Entry Burn Startup visible 10 seconds later, though they cut away from her at T+06:56 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1553s) before the burn was complete.
It might have been just a production issue, with the onboard camera feeds not initially available to the webcast video engineer.
Yeah. Not surprising at all that they tested the "real" pipeline, the one they use for video in mission control, and the oversight was in reconfiguring the separate webcast video pipeline.
-
SpaceX launch photos by Ben Cooper
-
Here is a comparison of the public booster telemetry from Starlink L22 and L23.
Unlike recent missions, the L23 booster appears to maintain a high AoA all the way to MECO (normally the rocket pitches down (more) just before MECO). As a result, the ballistic coast has an apogee about 10km higher at 126km, and consequently the booster lands some 18km further downrange at 633km.
Additionally, you can see that although the entry burns both peak at around 4.5g, the velocity after the entry burn is higher for L23, as is the acceleration due to drag as it hits the sensible atmosphere. For L23, the peak acceleration is over 5g, and will mean increased heating compared to previous Starlink missions.
Edit: For completeness, I've added the S2 telemetry, which confirms L23's more lofted trajectory, as well as the very similar insertion altitude and velocity (within about 4m/s).
-
Here is a comparison of the public booster telemetry from Starlink L22 and L23.
Unlike recent missions, the L23 booster appears to maintain a high AoA all the way to MECO (normally the rocket pitches down just before MECO). As a result, the ballistic coast has an apogee about 10km higher at 126km, and consequently the booster lands some 18km further downrange at 633km.
No, watch the sequence again, it definitely pitches down. Maybe not all the way, but it does most of the way.
-
I heard some info that SpaceX choose not to show webcams from 1st stage during ascends of Starlinks missions. It could lower chances of getting issues. They have had them.
-
What was the splash that happened in the top right of the feed at T=+8:53 (27:58 in the webcast)
https://youtu.be/Uy9Jn-3vuPs?t=1678 (https://youtu.be/Uy9Jn-3vuPs?t=1678)
-
https://twitter.com/TSKelso/status/1380080100750675971
-
What was the splash that happened in the top right of the feed at T=+8:53 (27:58 in the webcast)
I believe that was a digital hitch in the video, because it disappeared instantly.
-
Here is a comparison of the public booster telemetry from Starlink L22 and L23.
Love your graphs! Keep it up, please.
One suggestion: post them in PNG format for sharpness and smaller file size.
-
What was the splash that happened in the top right of the feed at T=+8:53 (27:58 in the webcast)
YouTube time-links don't work when embedded by the forum software.
One workaround is using the full "youtube.com/watch?v=...&t=..." format without the leading "www." to suppress embedding:
* https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1671 (Linked a few second earlier.)
As for your "splash" ... I don't know, but I think it may just be a compression artifact.
Note how it disappears entirely from one frame to the next, three frames prior to T+09:00.
(However the sudden disappearance could itself be a compression artifact.)
Whatever it is, if forms from left to right and is present for about five seconds, and if I didn't know any better I'd say it was the booster venting inline with the visible horizon. But while the F9 booster does vent from a number of locations shortly after landing, I don't think it does so at that location.
-
What was the splash that happened in the top right of the feed at T=+8:53 (27:58 in the webcast)
YouTube time-links don't work when embedded by the forum software.
One workaround is using the full "youtube.com/watch?v=...&t=..." format without the leading "www." to suppress embedding:
* https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1671 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1671) (Linked a few second earlier.)
As for your "splash" ... I don't know, but I think it may just be a compression artifact.
Note how it disappears entirely from one frame to the next, three frames prior to T+09:00.
(However the sudden disappearance could itself be a compression artifact.)
Whatever it is, if forms from left to right and is present for about five seconds, and if I didn't know any better I'd say it was the booster venting inline with the visible horizon. But while the F9 booster does vent from a number of locations shortly after landing, I don't think it does so at that location.
It was accompanied by a venty/splash/fizzy type noise.
-
What was the splash that happened in the top right of the feed at T=+8:53 (27:58 in the webcast)
YouTube time-links don't work when embedded by the forum software.
One workaround is using the full "youtube.com/watch?v=...&t=..." format without the leading "www." to suppress embedding:
* https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1671 (https://youtube.com/watch?v=Uy9Jn-3vuPs&t=1671) (Linked a few second earlier.)
As for your "splash" ... I don't know, but I think it may just be a compression artifact.
Note how it disappears entirely from one frame to the next, three frames prior to T+09:00.
(However the sudden disappearance could itself be a compression artifact.)
Whatever it is, if forms from left to right and is present for about five seconds, and if I didn't know any better I'd say it was the booster venting inline with the visible horizon. But while the F9 booster does vent from a number of locations shortly after landing, I don't think it does so at that location.
It was accompanied by a venty/splash/fizzy type noise.
It's compression artifacts. End of story.
Consecutive Frames, 5 artifacts instantly introduced and develop before disappearing.
-
It was accompanied by a venty/splash/fizzy type noise.
That does come at about the right time, doesn't it? But unfortunately, we don't get any sound from those cameras. The noise is either coming from the Hawthorne production floor, or from a cartload of dishes being bussed to their cafeteria scullery. (It is quite common to hear cafeteria background noises during launch commentary.)
-
https://twitter.com/SpaceXFleet/status/1380271652307615750
-
Here is a comparison of the public booster telemetry from Starlink L22 and L23.
Love your graphs! Keep it up, please.
One suggestion: post them in PNG format for sharpness and smaller file size.
Thanks for the feedback. I used to post them as .png files, but a couple of months ago there were some display issues with .png on the site, so I swapped to .jpg. Perhaps a mod can tell me the preferred site format?
-
Thanks for the feedback. I used to post them as .png files, but a couple of months ago there were some display issues with .png on the site, so I swapped to .jpg. Perhaps a mod can tell me the preferred site format?
By the way, the files you posted are in BMP format, not JPG (despite the extension being JPG), which explains the large file size. Here are the file sizes with different formats for "StarlinkS1-L22-23.bmp".
BMP: 6.4 MB (original file size and type)
JPG: 133 KB
GIF: 62.8 KB
PNG: 105 KB
So, I would recommend posting using GIF, which does not add artefacts like JPG and has better compression than PNG for images with simple colours and shapes. I use IrfanView to convert the various images. Just open the file using IrfanView -> File -> Save As... -> Save as type: -> GIF - Compuserve GIF -> Save. The File -> Save as... operation can be called by just typing S on your keyboard.
https://www.irfanview.com/
-
https://twitter.com/spacexfleet/status/1380502177605689348
Shelia Bordelon is now under one hour away from Port Canaveral with the fairing from the Starlink mission earlier this week.
-
https://twitter.com/gregscott_photo/status/1380527869990993926
SpaceX's new recovery ship the Shelia Bordelon arrived back in port early this morning with only 1 fairing from the recent Starlink 23 mission. The fairing appeared in good shape but the disposition of the 2nd fairing is unknown. #spaceX #NASA #Science #SpaceXFleet
-
https://twitter.com/SpaceXFleet/status/1380638470562054146
OCISLY droneship and B1058-7 still closing in on Port Canaveral.
Droneship should be within the vicinity of Port Canaveral around midnight, setting up an arrival after dawn tomorrow morning.
-
https://twitter.com/spacexfleet/status/1380824125271314435
Good Morning ☀
OCISLY and B1058 are just offshore and preparing to arrive at Port Canaveral in the next couple of hours
-
twitter.com/spacexfleet/status/1380858618837405702
Falcon 9 B1058-7 has arrived at Port Canaveral.
Watch live: youtube.com/watch?v=gnt2wZ…
https://twitter.com/spacexfleet/status/1380859216446038021
-
Closer Fleetcam shots attached
https://youtu.be/gnt2wZBg89g
-
https://twitter.com/gregscott_photo/status/1380867013631954951
SpaceX's Booster B1058.7 & OCISLY arrived at Port Canaveral just after sunrise this morning from this weeks #spaceX Starlink 23 mission The booster is getting extremely sooty with the NASA worm barely visible anymore but appears in good shape #NASA #Science @elonmusk #spacexfleet
Edit to add:
https://twitter.com/julia_bergeron/status/1380864344242716678
twitter.com/spacecoast_stve/status/1380866566938628099
Possibly the most famous of all the Falcon 9 boosters, B1058 has returned from her 7th mission.
This booster began its life returning human spaceflight to the Space Coast last May during the DM-2 mission. These days, she passes the time sending Starlink satellites to orbit.
https://twitter.com/spacecoast_stve/status/1380866590204428290
Worm vs meatball? Why not both?!
-
https://twitter.com/delta_iv_heavy/status/1381684152144162818
Thats odd. They just set 1058 on the ground instead of the stand they use to raise the legs.
https://twitter.com/delta_iv_heavy/status/1381696342448291840
Its over the stand now, guess they just set it down for some reason.
NSF live Fleetcam shot attached
Edit to add:
https://twitter.com/abernnyc/status/1381683737193222152
-
https://twitter.com/jennyhphoto/status/1381708433234272266
#SpaceX #Falcon9 #booster B1058 returns after its 7th flight. #spacexfleet
-
https://twitter.com/spacecoast_stve/status/1382033090013462530
Holy levitating Falcon, Batman!
B1058 is moments away from being placed on the transporter to be rolled away and prepped for another mission.
But if you’re watching Fleetcam, you already knew that.
youtu.be/gnt2wZBg89g
https://twitter.com/abernnyc/status/1382017815411109891
B1058 spent the majority of the morning working on its legs. Now that they've all been retracted, we're just waiting on the second crane to attach and lay the booster on its side.
Another beautiful day at the port.
-
B1058 has left the port.
-
Retention rods probably spotted reentering over central Spain:
https://mobile.twitter.com/Marco_Langbroek/status/1388071468802715649