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
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.
Thank you for the pointer. Fixed.
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 |
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
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.
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.
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.
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".
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."
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.