27
Starship Development Thread #53
(sh.itjust.works)
submitted
10 months ago* (last edited 8 months ago)
by
threelonmusketeers@sh.itjust.works
to
c/spacex@sh.itjust.works
Portions of this thread copied from the Starship Dev thread on r/SpaceX.
FAQ
- When next launch? IFT-3 is NET Mid-March, and after completion of the IFT-2 mishap investigation. Candidate vehicles are Booster 10 and Ship 28.
- When previous launch? (IFT-2)? Booster 9 and Ship 25 launched on 2023-11-18.
- What was the result? Successful lift off with minimal pad damage. Successful booster operation with all engines to successful hot stage separation. Booster destroyed by AFTS after attempted boost-back. Ship fired all engines to near orbital speed then destroyed by AFTS. No re-entry attempt.
- Was IFT-2 a complete failure? No. As part of an iterative test programme, many milestones were achieved. Perfection is neither expected nor desired at this stage.
---
Quick Links
RAPTOR ROOST | LAB CAM | SAPPHIRE CAM | SENTINEL CAM | ROVER CAM | ROVER 2.0 CAM | PLEX CAM | NSF STARBASE
Starship Dev 52 | Starship Dev 51 | Starship Dev 50 | Starship Dev 49 | Starship Dev 48
Official SpaceX Starship Update Video (2024-01-12)
Status
Road Closures
Type | Start (CDT) | End (CDT) | Status |
---|---|---|---|
Primary Date | 2024-02-15 08:00 | 2024-02-15 20:00 | Closure revoked. |
Backup Date | 2024-02-16 08:00 | 2024-02-16 20:00 | Closure scheduled. |
Backup Date | 2024-02-20 08:00 | 2024-02-12 20:00 | Possible closure. |
Up to date as of 2024-02-19
Vehicle Status
As of 2024-02-20
Follow Ring Watchers on Twitter and Discord for more.
Ship | Location | Status | Comment |
---|---|---|---|
S24 | Gulf of Mexico | Destroyed | April 20th (IFT-1): Destroyed by flight termination system after successful launch. |
S25 | Atlantic Ocean | Destroyed | Mostly successful launch and stage separation |
S26 | Rocket Garden | Mysterious | Static fire Oct. 20. No fins or heat shield, multiple mysterious changes. Completed 3 cryo tests, latest on Oct 10. |
S28 | Suborbital test stand | Awaiting testing | Static fired Dec 29th. Stacked on B10 on Feb 13th. Partial WDR conducted Feb 14th and 16th. Destacked Feb 18th. Spin prime Feb 26th. |
S29 | High Bay | Pending engine install | 3x cryo |
S30 | High Bay | Pending engine install | 2x cryo: Jan 3rd and Jan 5th |
S31 | High Bay | Aft flaps installed | |
S32 | Rocket Garden | Resting | Fully stacked, fore flaps installed but not aft flaps |
S33-34 | Build Site | Parts spotted | To be scrapped in preparation for Starship V2 |
Booster | Location | Status | Comment |
---|---|---|---|
B7 | Gulf of Mexico | Destroyed | Destroyed by flight termination system after successful launch. |
B9 | Gulf of Mexico | Destroyed | Successfully launched, destroyed during Boost back attempt. |
B10 | Megabay 1 | Awaiting testing | Static fired Dec 29th. Hotstaging ring installed Jan 26th. Partial WDR conducted Feb 14th and 16th. |
B11 | Megabay 1 | Finalizing | Completed 2 Cryo tests. |
B12 | Megabay 1 | Finalizing | Cryo x2 |
B13 | Megabay 1 | Fully stacked | Chine installation underway |
B14 | Build Site | Assembly | Assorted parts spotted |
B15 | Build Site | Assembly | Potential aft end spotted Jan 5th |
Resources
- LabPadre Channel | NASASpaceFlight.com Channel
- NSF: Booster 7 + Ship X (likely 24) Updates Thread | Most Recent
- NSF: Boca Chica Production Updates Thread | Most recent
- NSF: Elon Starship tweet compilation | Most Recent
- SpaceX: Website Starship page | Starship Users Guide (2020, PDF)
- FAA: SpaceX Starship Project at the Boca Chica Launch Site
- FAA: Temporary Flight Restrictions NOTAM list
- FCC: Starship Orbital Demo detailed Exhibit - 0748-EX-ST-2021 application June 20 through December 20
- NASA: Starship Reentry Observation (Technical Report)
- Hwy 4 & Boca Chica Beach Closures (May not be available outside US)
- Production Progress Infographics by @RingWatchers
- Raptor 2 Tracker by @SpaceRhin0
- Acronym definitions by Decronym
- Everyday Astronaut: Starbase Tour with Elon Musk, Part 1 | Part 2 | Part 3
- Everyday Astronaut: 2022 Elon Musk Interviews, Starbase/Ship Updates | Launch Tower | Merlin Engine | Raptor Engine
Have you considered migrating to a magazine on Kbin/MBin?
The daily updates are quite useful but currently my means of finding them is via your posts in Reddit. The post views in Lemmy discourage you to go into spaces and I don't think thread pinning translates accross instances.
KBin/Mbin support the short message format in Activity Pub so creating a thread on that platform should reflect into Mastodon and Mastodon comments will come through into the post. If you add a couple of hashtags it would also help discoverability.
Your posts are the most useful ones for daily summaries and probably the most useful contribution to the reddit starship dev thread.
Interesting, I had not considered migrating to a Kbin/Mbin magazine.
From a brief look, thread pinning seems to federate across Lemmy instances, but not to Kbin.
Thanks! Glad people find them useful.
I'm not too familiar with Kbin/Mbin, so I do not feel ready to migrate the entire community at this time. However, if you were to create a SpaceX magazine, I could probably post these updates there as well. If the magazine gains more traction, we could reconsider migrating this community at a later date.
What are your thoughts? Anything I should know about Kbin/Mbin? (What's the difference?) What are the "short message format" and a "thread" in those contexts? Do they have Lemmy analogues?
I shall have a think where it makes sense to create one. Lits were created a while back and seem to have been purged
Short Message Format = Tweet Thread = post
KBin calls a community a "magazine" and Magazine mods can associate hashtags with the Magazine.
The idea is from your instance you can look at the thread view or microblog (tweet) view.
KBin was started by a person called Ernest, he doesn't seem particularly great at accepting outside help. A number of people who wanted to contribute but found their work stuck for review for months forked KBin and called it MBin.