pigeonberry

joined 1 year ago
 

SpaceX's social media people are really outdoing themselves lately. This video is, I think, the second one showing recent Starlink deployment. The mirrored surface reflected the second stage so well is stunning.

 

I saw this somewhere on Xitter or The Other Place. I hadn't heard that there had been any sort of re-evaluation or more documents. The first document is dated 14 April 2023, so just before the first test, IFT-1:

WRITTEN RE‐EVALUATION OF THE 2022 FINAL PROGRAMMATIC ENVIRONMENTAL ASSESSMENT FOR THE SPACEX STARSHIP/SUPER HEAVY LAUNCH VEHICLE PROGRAM AT THE BOCA CHICA LAUNCH SITE IN CAMERON COUNTY, TEXAS

Starship/Super Heavy Vehicle Ocean Landings and Launch Pad Detonation Suppression System

and following letters and documents are below it, dated as early as October 2022. 122 pages, oy vey, but a lot of repetition. I don't know enough to know whether there was anything significant, unless the FAA saying (paraphrasing) "these are some changes and considerations, but they don't have significant impact". There were changes expanding the landing zones, and more biological details, and lots more math about sound effects.

 

The first image, of Super Heavy + Starship at night reflecting the launch tower -- is astonishing. Image 1

Image 2: stack against a partly cloudy sky near sunrise

Image 3: towards the top of the stack near sunset

[–] pigeonberry 4 points 1 year ago* (last edited 1 year ago) (2 children)

An easier way to reach the app in Android is the Google Play store. It's named Austin 311 from City of Austin. Some negative reviews, though, like (20 Jan 2023) "You can't report when your trash doesn't get picked up - easily 99% of the reason I ever call 311" and (9 June 2022) "App sucks. The categories are very limited and hard to locate. I should be able to search on a keyword and your app suggests appropriate categories. Where do i report a malfunctioning pedestrian cross signal, for example. Very disappointing!"

I just checked out the Web page. That has a search capability (I don't see one in the app), both built in via a Search text box, and the browser's own facility (except there are not many items per page). I think I prefer it, even on my phone.

But the Android app at least has a map of recent reports, which is a nice feature; I don't see it in the web page. It also has one central place to enter the reporter's info; it looks like the Web page has it on each request.

 

It's an interview with Brian Fuchs, a climatologist with the National Drought Mitigation Center, which publishes the Drought Monitor map. He talks about the center itself, He talks about how they determine drought, considering lots of different factors and their impacts. There's a distinction between short-term and long-term drought. He compares the current situation with 2011, which was actually the peak of a long drought that lasted until 2015 or so.

 

Article by Jacek Krywko, 13 September 2023. No intro here, but a much older article says "a science and technology writer based in Warsaw, Poland. He covers space exploration and artificial intelligence research, and he has previously written for Ars about facial-recognition screening, teaching AI-assistants new languages, and AI in space.".

WOW! I have no knowledge of the field, but it looks informative. As articles go, it's fairly long.

It's about efforts to get "bioregenerative life-support systems", living life-support systems as needed for long space journeys and bases over yonder.

The first efforts its lists were plant-based, BIOS (Soviet) and CELSS (US).

BIOS-3 experiments showed how much labor it took to operate this system. Results were bleak. Astronauts basically worked like full-time farmers just to keep it going.... There was very little control over what exactly the biological component was doing.

Then MELiSSA was proposed and implemented. It is bacteria-based. The great advantage is that each bacteria species does about one thing, and responds immediately to conditions, so humans can have much much more control. But it was a huge project:

The project quickly grew into a gargantuan effort backed by 14 countries and over 50 institutes, universities, and companies.

Then

In 2017, NASA founded the Center for Utilization of Biological Engineering in Space (CUBES), a conglomerate of federal agencies, industry, and academia, with the goal of building a demonstration biosystem for a future Mars colony....

While MELiSSA was focused on fine-tuning the hardware and software and left biology intact, CUBES involves engineering all three to make them work seamlessly together.

So bacteria-based, but now with genetic engineering. Also looking at producing more, like plastics or papers or more.

It talks about one drawback of that approach: "The problem is that life, when pushed, sometimes fights back." The changes for more productions of nitrites or fatty acids or whatever are not adaptive for the organism, so it has an incentive to mutate back towards its original if that can breed faster.

There's also discussion of multiple stages with more and more capability.

And also discussion of funding. MELiSSA has continuing funding and is looking for a human prototype. CUBES has had some design work, "with, like, $15 million USD in five years".

Anyway, well worth considering, and the comments are more valuable than in many comment sections. I did see fuzzyfuzzyfungus noting his own lay experience in existing bioreactors (amplifying a point above), specifically "the occasions when very, very unhappy science types announce that we'll be shutting down production because some undesired strain that's a lot less useful but a lot better at survival than the desired strain had snuck in and it was time to bleach out the tanks and sterilize everything to hell and back were just a thing that happened on occasion".

Edit: other items mentioned in the comments:

A City on Mars: Can we settle space, should we settle space, and have we really thought this through?: upcoming book from the Weinersmiths.

Thriving in Space: Ensuring the Future of Biological and Physical Sciences Research: A Decadal Survey for 2023-2032

Curiosity Finds Fairly Benign Radiation Environment on Mars

Covid on Mars: SF essay by Charlie Stross

 

This is related to @[email protected]'s post about SpaceX no longer taking losses to produce Starlink satellite antennas. The article below refers to that one.

ArsTechnica, in "SpaceX projected 20 million Starlink users by 2022—it ended up with 1 million".

It's based on a Wall Street Journal article, which seems like a bit of a hit piece. The headline claim is absurd, as some comments pointed out: the projection was in 2015! It also points out that skeptics had always said that Starlink would not do well in cities, which would be a more valid criticism if Musk and Starlink didn't point it out first.

But there was this reported number:

Actual Starlink revenue for 2022 was $1.4 billion, up from $222 million in 2021, according to the report. The documents apparently didn't specify whether Starlink is profitable.

It mentions numbers that Shotwell had previous provided and that may have been reported here. I'll add them to have more data in one place:

SpaceX President and COO Gwynne Shotwell said in February that Starlink is expected to turn a profit this year. While Starlink's specific profit or loss is unknown, the WSJ previously reported that SpaceX overall "eke[d] out a small profit in the first three months of [2023] after two annual losses." SpaceX's Q1 2023 numbers reportedly included a $55 million profit on $1.5 billion in revenue.

The CNBC article had this, partially quoted in this ArsTechnica article,

The company last provided an update on its global Starlink user base in May, when it said it had about 1.5 million customers. Hofeller did not specify what that total is now but said Starlink is "well over" that 1.5 million mark. The figure includes both consumer and enterprise customers around the world ...

[–] pigeonberry 2 points 1 year ago

I got the impression from reading the few posts about it that it's going to start as a backup for the existing crew Dragon tower. Whether it could ever become Son of Mechazilla in the long run I don't know, and I doubt it. I suspect, though on no evidence other than prior practice and the 5-step algorithm, that SpaceX would rather debug the first model some before building a second.

[–] pigeonberry 3 points 1 year ago

This is a link to my separate story post: "(Reuters) US could advance SpaceX license as soon as October after rocket exploded in April", including a bit of interpretation.

 

WASHINGTON, Sept 13 (Reuters) - The acting head of the Federal Aviation Administration said on Wednesday the agency could advance a launch license as early as next month for the SpaceX Starship rocket after a prior one exploded following a test launch in April.

"We're working well with them and have been in good discussions. Teams are working together and I think we're optimistic sometime next month," acting FAA Administrator Polly Trottenberg told reporters on the sidelines of a conference.

SpaceX would still need a separate environmental approval from the U.S. Fish and Wildlife Service before a launch. Trottenberg did not say how long that might take.

It has been noted that the last paragraph doesn't say that Trottenberg said that. It might have been the reporter's inference that it is needed, and Trottenberg may not have addressed it at all. Also, for the PEA, the FAA handled all of it, including interfacing with the U.S. FWS and all other governmental entities.

 

The xeet just had "Made on Earth by humans" and the picture. Sep 13, 2023 · 5:48 PM UTC, after the Starship first flight test, and we hope the second one will be soon.

[–] pigeonberry 2 points 1 year ago

Thank you for the pointer. Fixed.

 

Ozan Bellik @BellikOzan Sep 12, 2023 · 5:37 AM UTC:



Months between 1st launch and 4th successful launch of every medium or heavier launch vehicle family that debuted in past 30 years & had 4+ successful flights:

  • Atlas V: 28

  • H-II: 30

  • Falcon [9]: 33

  • Vega: 36

  • Delta IV: 42

  • Atlas III: 43

  • CZ-5: 44

  • Ariane 5: 51

  • CZ-7: 59

  • PSLV: 97

  • GSLV: 172

Starship had its first full stack launch in April. If it matches Atlas V's 28 months, 4th successful flight would be in August '25.

Vulcan's maiden flight is NET December.

If it actually flies then (doubtful) and matches the quickest 4th flight of the past 30 years, we'd see that flight in April '26

(As a reminder, they're aiming to be flying ~twice a month by the end of '25.)

H2 '26 would by this measure be highly optimistic for the 4th successful flights of Ariane 6, New Glenn, and Neutron.

Let's not even get into Terran R.

As fast as RocketLab moves (22 mo.s for Electron for above metric), even Rutherford reportedly took ~3 years from first test firing to flight qualification, and 1 more year to fly.

Full engine firing of Archimedes is expected NET late '23. Flight before '27 is optimistic.

[replying to "A question/request: could you please list on which launch attempt each of the rockets achieved their respective 4th SUCCESSFUL launch?"]

  • Atlas V: 4

  • H-II: 4

  • Falcon: 5

  • Vega: 4

  • Delta IV: 5

  • Atlas III: 4

  • CZ-5: 5

  • Ariane 5: 6

  • CZ-7: 5

  • PSLV: 6

  • GSLV: 9



In later xeets,

Saturn V: 16 (Apollo 4 11/67, A6, A8, Apollo 9 3/69)

Are we talking New Glenn? It's certainly possible [that it'll shatter records]. On the other hand it's their first orbital rocket, and I'm not even expecting a maiden flight in '24.

[replying to: And people are deluded if they think a new entrant will do much better] Absolutely

They might all do better. I'm not expecting much better. And I'm only expecting 2 of them to have had a launch by the end of next year.

[Starship flights this year] I think that barring major regulatory obstacles, 1 more is likely, 2 more is plausible (if IFT-2 goes smoothly; even if no pad damage, if it doesn't fly true, there will be a mishap investigation). 3 seems like a stretch.

He bundles Falcon Heavy with Falcon 9 as the same family, but excludes Falcon 1.

They include test flights

[–] pigeonberry 3 points 1 year ago* (last edited 1 year ago) (2 children)

I copied and pasted it here. Thanks to @[email protected] for pointing me back at the RES extension so I could get the source.

Each item is on its own line. C## is the ID#. If there's text before it on its line, that's its Observation / Description section name; if it's at the start of the line, the Observation / Description string is the next one above.

List of Actions:

| Observation / Description | ID# | Corrective Action Description | Status | | ---------------------------------- |


| --------------------------------------------------------------------------------------------- | ------------- | | Tank sensing | C1 | Replace certain fittings with welds inside tank | Complete | | Aft end cavity environment failure | C2 | Increase fire suppression capacity by 15x | Complete | | | C3 | Replace certain manifolds with dedicated drain per corresponding valve | Complete | | | C4 | Replace certain flanges with better seals and improve joint design | Complete | | | C5 | Replace certain fittings with welds in specific location | Complete | | Booster leak | C6 | Replace accessible valves of a certain type with new design | Complete | | mitigation | C7 | Replace certain flange bolts with higher strength bolts and increase torque | Complete | | | C8 | Disallow certain seal re-use, and add cameras to monitor all engines during ground operations | Complete | | | C9 | Increased scrutiny on leak checks | Complete | | | C10 | 90+ cameras added to detect leakage during operations | Complete | | | C11 | Add leak capture and drain hardware for valves of a certain type | Complete | | | C12 | Add leak check and screen for porosity on igniter units | Complete | | | C13 | Improved igniter seal design | Future Action | | | C14 | Weld certain alignment bolt holes shut | Complete | | Raptor leak | C15 | Reassess k-factor and torque for engine hot joint #1, add leak capture and route overboard | Complete | | mitigation | C16 | Reassess k-factor and torque for engine hot joint #2 | Complete | | | C17 | Add safety cable to certain fluid lines on high risk locations | Complete | | | C18 | Add one methane sensor per engine bay | Complete | | | C19 | Ground test campaign to better characterize typical engine leakage | Complete | | | C20 | Improve structural FEA/fatigue analysis for all medium to high criticality lines | Complete | | | C21 | Add insulation to engine lines sensitive to thermally driven loads | Complete | | Collateral | C22 | Add insulation to avionic harnessing | Complete | | damage from fire | C23 | Add backup wire to specific harness | Complete | | | C24 | Improve thermal protection of avionics tray | Complete | | | C25 | Change routing to flight computers | Complete | | | C26 | Replace sensor with more reliable units | Complete | | | C27 | Coat gimbal assembly with lubricant | Complete | | | C28 | Add pump pressure sensors to certain location | Complete | | | C29 | Add pump temperature sensors to certain location | Complete | | Booster reliability | C30 | Replace certain bolts, and increase torque for certain flanges | Complete | | improvement | C31 | New seal design for certain areas of booster | Complete | | | C32 | Add electric actuation system | Complete | | | C33 | Better manage engine bay pressure by increasing fire suppression capacity by | Complete | | | C34 | Change certain booster valve timing | Future Action | | | C35 | Add final leak checks for critical joints | Complete | | | C36 | Add support bracket for certain sensor | Complete | | | C37 | Add support bracket for certain sensor | Complete | | | C38 | Add check valves to certain areas of engine | Complete | | | C39 | Improve oxygen valve design | Future Action | | | C40 | Improve oxygen valve seal design | Future Action | | Raptor reliability | C41 | Improve design of hot manifold | Future Action | | improvement | C42 | Change nitrogen shutdown usage | Complete | | | C43 | Change engine shutdown logic | Complete | | | C44 | Increase capability for ground leakage mitigation | Complete | | | C45 | Redesign fire suppression system | Complete | | | C46 | Change conditions around bolts | Complete | | | C47 | Change timing of specific valve actuation | Complete | | Avionics reliability | C48 | Eliminate certain type of connector | Complete | | improvement | C49 | Redesign network architecture | Future Action | | Risk Process | C50 | Improve risk tracking process | Complete | | | C51 | Implement improvements to safety system | Complete | | Safety System | C52 | Verify flight safety system design improvements using additional type of test article | Complete | | | C53 | Verify flight safety system design improvements via analysis | Complete | | | C54 | Perform component testing | Complete | | | C55 | Review and improve operations surrounding flight safety system | Complete | | | C56 | Improve CAD controls | Complete | | Control | C57 | Add engineering walkdown | Complete | | Change | C58 | Improve use of change management system | Complete | | | C59 | Redesign of launch pad deck | Complete | | Pad Design | C60 | Improve assumptions for new pad deck design | Complete | | | C61 | Add water cooled pad deck | Complete | | Pad Design Process | C62 | Improve pad deck design documentation | Complete | | | C63 | Improve pad design process | Complete |

[–] pigeonberry 2 points 1 year ago* (last edited 1 year ago) (3 children)

A readable text version of the 63-item list can be see on Reddit here and a reply.

[–] pigeonberry 3 points 1 year ago (1 children)

Tesla Owners Silicon Valley @teslaownersSV Sep 9, 2023 · 12:17 AM UTC

Starship is the biggest rocket ever built 🤯

Elon Musk @elonmusk / Replying to @teslaownersSV Sep 9, 2023 · 6:20 AM UTC

Likely to be 10% to 20% longer in later versions

[–] pigeonberry 3 points 1 year ago

Musk noted Sep 9, 2023 · 12:20 AM UTC

In fairness to the FAA, it is rare for them to cause significant delays in launch.

Overwhelmingly, the responsibility is ours.

[–] pigeonberry 4 points 1 year ago

Oddly, he replied Sep 9, 2023 · 12:20 AM UTC

In fairness to the FAA, it is rare for them to cause significant delays in launch.

Overwhelmingly, the responsibility is ours.

[–] pigeonberry 5 points 1 year ago

Top-level posts just added:

[SpaceX] September 8, 2023: Upgrades Ahead Of Starship’s Second Flight Test That is, it's a statement from SpaceX itself about the major problems it saw on Starship test 1, and several changes it has made.

[Chris Bergin, Abhi Tripathi @SpaceAbhi] SpaceX LEADS the investigation It's not appreciated that SpaceX did the investigation, decided on corrections, and wrote the report. The FAA provides feedback, but we don't know how much.

 

Taking the liberty of copying the text from Chris Bergin - NSF @NASASpaceflight Sep 8, 2023 · 2:08 PM UTC:


Additional background on the release:

The FAA oversaw the SpaceX-led investigation to ensure the company complied with its FAA-approved mishap plan and other regulatory requirements.

The FAA was involved in every step of the mishap investigation and granted NASA and the National Transportation Safety Board official observer status.

The mishap investigation report contains proprietary data and U.S Export Control information and is not available for public release.


And Abhi Tripathi @SpaceAbhi, way emphasizing the "SpaceX-led investigation" part:


I've seen dozens of "Twitter experts" misunderstand this (often time by adding "Breaking..." to their post for extra clicks) so let me reiterate and further explain what Chris details below.

SpaceX LEADS the investigation. SpaceX issues the corrective actions. They pre-write a mishap investigation plan before they even launch. Then they execute their plan if they have an actual mishap. The FAA formally reviews the plan and also the investigation results and SpaceX-recommended corrective actions (but...informally they already know what's coming because of close coordination). The FAA provides feedback, and could recommend adding something if warranted. Their main job is to verify and enforce that SpaceX does what SpaceX said it will do once they approve the final report. In reality, 90% or more of corrective actions may be finished before the report is even formally submitted. Just depends on how well the root cause(s) are understood and easy to fix.

The general public often believes the FAA writes all the corrective actions and has a large team of people conducting the investigation with a heavy hand (e.g. "the big bad government"). No way. I doubt that will ever be the case for any mishap or anomaly. That is simply not how the government is staffed.

The FAA (and their NASA colleagues who have the relevant technical expertise) are typically in super close contact with the SpaceX team through the head of SpaceX Flight Reliability (where the chief engineers reside).

The statements released by the government are usually kept vague but factual, often to the great dismay of social and traditional media (as well as "stans") who want a juicy bite, ideally brimming with conflict. It is in a government agency's best interest to maintain flexibility and work with who they are overseeing...while keeping the politicians and click-bait journalists and influencers away. Inflammatory statements could rally politicians to one side or the other, and then SpaceX and the FAA's job could become charged and harder. Many people want to see that happen for many reasons.

If the final approval stalls, often times it is over a corrective action that was too open to interpretation. As an example of what I mean, if a corrective action is worded as such: "Redesign of the launch pad to increase its robustness." Ooh boy. So you want to break that down into discrete actions defining what "robustness" means.

If you want to learn more about the FAA's role, read their website here: https://www.faa.gov/space/compliance_enforcement_mishap

 

TL;DR Flight Test 1:

  • During ascent, the vehicle sustained fires from leaking propellant in the aft end of the Super Heavy booster, which eventually severed connection with the vehicle’s primary flight computer. This led to a loss of communications to the majority of booster engines and, ultimately, control of the vehicle.
  • unexpected delay following AFSS activation

Changes:

  • implemented leak mitigations and improved testing on both engine and booster hardware ... expanded Super Heavy’s pre-existing fire suppression system in order to mitigate against future engine bay fires
  • enhanced and requalified the AFSS to improve system reliability
  • hot staging
  • new electronic Thrust Vector Control (TVC) system for Super Heavy Raptor engines
  • upgrades to the orbital launch mount and pad system: include significant reinforcements to the pad foundation and the addition of a flame deflector

I had trouble accessing it -- for a while, it didn't show me today's post (8 Sep 2023). So I'm going to take the liberty of pasting it here.


September 8, 2023

Upgrades Ahead Of Starship’s Second Flight Test

The first flight test of a fully integrated Starship and Super Heavy was a critical step in advancing the capabilities of the most powerful launch system ever developed. Starship’s first flight test provided numerous lessons learned that are directly contributing to several upgrades being made to both the vehicle and ground infrastructure to improve the probability of success on future Starship flights. This rapid iterative development approach has been the basis for all of SpaceX’s major innovative advancements, including Falcon, Dragon, and Starlink. SpaceX has led the investigation efforts following the flight with oversight from the FAA and participation from NASA and the National Transportation and Safety Board.

Starship and Super Heavy successfully lifted off for the first time on April 20, 2023 at 8:33 a.m. CT (13:33:09 UTC) from the orbital launch pad at Starbase in Texas. Starship climbed to a maximum altitude of ~39 km (24 mi) over the Gulf of Mexico. During ascent, the vehicle sustained fires from leaking propellant in the aft end of the Super Heavy booster, which eventually severed connection with the vehicle’s primary flight computer. This led to a loss of communications to the majority of booster engines and, ultimately, control of the vehicle. SpaceX has since implemented leak mitigations and improved testing on both engine and booster hardware. As an additional corrective action, SpaceX has significantly expanded Super Heavy’s pre-existing fire suppression system in order to mitigate against future engine bay fires.

The Autonomous Flight Safety System (AFSS) automatically issued a destruct command, which fired all detonators as expected, after the vehicle deviated from the expected trajectory, lost altitude and began to tumble. After an unexpected delay following AFSS activation, Starship ultimately broke up 237.474 seconds after engine ignition. SpaceX has enhanced and requalified the AFSS to improve system reliability.

SpaceX is also implementing a full suite of system performance upgrades unrelated to any issues observed during the first flight test. For example, SpaceX has built and tested a hot-stage separation system, in which Starship’s second stage engines will ignite to push the ship away from the booster. Additionally, SpaceX has engineered a new electronic Thrust Vector Control (TVC) system for Super Heavy Raptor engines. Using fully electric motors, the new system has fewer potential points of failure and is significantly more energy efficient than traditional hydraulic systems.

SpaceX also made significant upgrades to the orbital launch mount and pad system in order to prevent a recurrence of the pad foundation failure observed during the first flight test. These upgrades include significant reinforcements to the pad foundation and the addition of a flame deflector, which SpaceX has successfully tested multiple times.

Testing development flight hardware in a flight environment is what enables our teams to quickly learn and execute design changes and hardware upgrades to improve the probability of success in the future. We learned a tremendous amount about the vehicle and ground systems during Starship’s first flight test. Recursive improvement is essential as we work to build a fully reusable launch system capable of carrying satellites, payloads, crew, and cargo to a variety of orbits and Earth, lunar, or Martian landing sites.--

[–] pigeonberry 6 points 1 year ago

Scott Manley had comments starting with Sep 7, 2023 · 12:42 AM UTC:

Elon: we’re ready, just waiting on the license from the FAA

FAA: funny you should say that, we’re just waiting on you guys to fix the problems you had.

Sure it’s easy to think of the FAA as being a bunch of bureaucrats who should loosen up and cut SpaceX some slack, but after the rock tornado and wimpy FTS SpaceX has used up any slack it might have had.

Furthermore, the FAA is being sued alleging that it cut SpaceX too much slack on the environmental review surrounding Starbase. Any action they take could end up in court and they need to be sure it’s defensible before a jury https://www.space.com/spacex-faa-seek-dismiss-starship-lawsuit

Though someone else replied,

Setting aside that this answer is the same the FAA would give regardless of whether it was the day after IFT-1 or the day before they issued a license.

and Scott replied, "Correct".

 

Reported by Chris Bergin - NSF @NASASpaceflight on Xitter, video at Sep 6, 2023 · 10:32 PM UTC

Here comes the first section of the new Crew Tower for SLC-40! Initially will be used for Cargo Dragon launches from SLC-40, but eventually also for crew. It adds redundancy to 39A.

nsf.live/spacecoast

then this video

Tower on the loose at KSC!

then this video

Passing the grown-up Towers.

then this video

SLC-40 Tower section passing 39A's historic FSS and the new Starship Tower.

[–] pigeonberry 2 points 1 year ago (1 children)

From Ars Technica:

(Note: at 6 pm ET on Wednesday, the FAA issued the following statement).

"The SpaceX Starship mishap investigation remains open," the agency stated. "The FAA will not authorize another Starship launch until SpaceX implements the corrective actions identified during the mishap investigation and demonstrates compliance with all the regulatory requirements of the license modification process."

view more: ‹ prev next ›