Recommended Posts

If that is the case then  yeah I would expect bad things to happen.

 

FAA certification only goes to 150% .I know the FAA doesn't have jurisdiction here, but is NASA requiring 200%?  Is this for that ###### LOC rate they require? 

 

4 hours ago, Skiver said:

Still no news on this? I'm so used to SpaceX's quick and open explanations on some of the "failures" they've had in the past, the lack of information on this makes it feel worse than it probably is.

Government is involved.  Could be why it's taking longer?

SpaceX's Hans Koenigsmann re: Crew Dragon test failure. Sounds like plumbing.

Powered up nominally.

Completed 2 Draco thruster firings, 5 seconds each. 

Just before the SDs fired there was an anomaly which destroyed the vehicle.

Indications this happened while the SDs were "activating". Too soon to speculate about root cause.

COPVs are not pressurized during SD activation

Confidence in SDs - 600 tests including integrated;  pad abort and hovers.

Large amount of data; high speed film, sensors and telemetry. 

 

Video does not include the Q&A

 

Edited by DocM
9 hours ago, Skiver said:

Still no news on this? I'm so used to SpaceX's quick and open explanations on some of the "failures" they've had in the past, the lack of information on this makes it feel worse than it probably is.

Well....when the Falcon blew up on the launch pad it took about three weeks before a lengthy statement (aside from ones apologizing for loss of the AMOS-6) and preliminary speculation on the cause.  About 4 months before everything was done...with updates about every month.

 

I wouldn't read too much into them not giving out information at this point.  

 

Just hoping it isn't a design flaw...but we'll know eventually.

  • Like 2

From the above article...

Quote

///

In the company's most expansive comments to date, Koenigsmann said the "anomaly" occurred during a series of tests with the spacecraft, approximately one-half second before the firing of the SuperDraco thrusters. At that point, he said, "There was an anomaly and the vehicle was destroyed."

 

During the activation phase, the SuperDraco thruster system is pressurized, and valves are opened and closed. Since the accident there has been speculation that there may have been some issue with the composite overwrap pressure vessels, or COPVs, which store rocket fuels at extremely high pressures. The COPVs on Crew Dragon are different from those on the Falcon 9, and they would not have been overly stressed at that moment, Koenigsmann said. "I'm fairly confident that the COPVs are going to be fine," he said.

///

He also went on to say that  "We have no reason to believe there’s an issue with the SuperDracos themselves,"

  • 4 weeks later...
  • 4 weeks later...
  • 4 weeks later...

WRT the Crew Dragon explosion

 

https://twitter.com/SpaceflightIns/status/1150825006663897088

 

SpaceFlight Insider @SpaceflightIns
SpaceX has a teleconference set for later today. Most agencies / companies give a couple days notice @SpaceX gave less than 3 hours. Topic is explosion of their @CommercialCrew offering @CrewDragon2

 

SpaceX press release

 


On Saturday, April 20, 2019 at 18:13 UTC, SpaceX conducted a series of static fire engine tests of the Crew Dragon In-Flight Abort test vehicle on a test stand at SpaceXs Landing Zone 1, Cape Canaveral Air Force Station in Florida.

Crew Dragons design includes two distinct propulsion systems  a low-pressure bi-propellant propulsion system with sixteen Draco thrusters for on-orbit maneuvering, and a high-pressure bi-propellant propulsion system with eight SuperDraco thrusters for use only in the event of a launch escape. After the vehicles successful demonstration mission to and from the International Space Station in March 2019, SpaceX performed additional tests of the vehicles propulsion systems to ensure functionality and detect any system-level issues prior to a planned In-Flight Abort test.

The initial tests of twelve Draco thrusters on the vehicle completed successfully, but the initiation of the final test of eight SuperDraco thrusters resulted in destruction of the vehicle. In accordance with pre-established safety protocols, the test area was clear and the team monitored winds and other factors to ensure public health and safety.

Following the anomaly, SpaceX convened an Accident Investigation Team that included officials from the National Aeronautics and Space Administration (NASA), and observers from the Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB), and began the systematic work on a comprehensive fault tree to determine probable cause. SpaceX also worked closely with the U.S. Air Force (USAF) to secure the test site, and collect and clean debris as part of the investigation. The site was operational prior to SpaceXs Falcon Heavy launch of STP-2 and landing of two first stage side boosters at Landing Zones 1 and 2 on June 25, 2019.

Initial data reviews indicated that the anomaly occurred approximately 100 milliseconds prior to ignition of Crew Dragons eight SuperDraco thrusters and during pressurization of the vehicles propulsion systems. Evidence shows that a leaking component allowed liquid oxidizer  nitrogen tetroxide (NTO) to enter high-pressure helium tubes during ground processing. A slug of this NTO was driven through a helium check valve at high speed during rapid initialization of the launch escape system, resulting in structural failure within the check valve. The failure of the titanium component in a high-pressure NTO environment was sufficient to cause ignition of the check valve and led to an explosion.

In order to understand the exact scenario, and characterize the flammability of the check valves titanium internal components and NTO, as well as other material used within the system, the accident investigation team performed a series of tests at SpaceXs rocket development facility in McGregor, Texas. Debris collected from the test site in Florida, which identified burning within the check valve, informed the tests in Texas. Additionally, the SuperDraco thrusters recovered from the test site remained intact, underscoring their reliability.

It is worth noting that the reaction between titanium and NTO at high pressure was not expected. Titanium has been used safely over many decades and on many spacecraft from all around the world. Even so, the static fire test and anomaly provided a wealth of data. Lessons learned from the test  and others in our comprehensive test campaign  will lead to further improvements in the safety and reliability of SpaceXs flight vehicles.

SpaceX has already initiated several actions, such as eliminating any flow path within the launch escape system for liquid propellant to enter the gaseous pressurization system. Instead of check valves, which typically allow liquid to flow in only one direction, burst disks, which seal completely until opened by high pressure, will mitigate the risk entirely. Thorough testing and analysis of these mitigations has already begun in close coordination with NASA, and will be completed well in advance of future flights.

With multiple Crew Dragon vehicles in various stages of production and testing, SpaceX has shifted the spacecraft assignments forward to stay on track for Commercial Crew Program flights. The Crew Dragon spacecraft originally assigned to SpaceXs second demonstration mission to the International Space Station (Demo-2) will carry out the companys In-Flight Abort test, and the spacecraft originally assigned to the first operational mission (Crew-1) will launch as part of Demo-2.

  • Like 2

This is why testing happens. :yes: It'll be a far safer vehicle with this new change.

 

Apollo used the "burst disk" methodology as a safety feature too on its' engines. ALL of them. I'm surprised that SpaceX hadn't employed them also; but hey -- experience becomes the best teacher and this kind of thing won't be overlooked in the future.

 

Better that this happened now rather than later. (Y) 

  • Like 3

Yep, saw this.

 

Crew Dragon does have the capability to land anywhere, but of course won't be allowed to land anywhere but water unless it's an emergency. Frankly I think ocean landings are "old school" and need to be rethought. Big waste of resources for recovery not to mention refurbishing the spacecraft (considering how much havoc seawater causes).

 

Seriously, set up a 50 x 200 mile touchdown area in the Western or Southern U.S. (or both) designated as a Recovery Area so that Commercial Crew spacecraft can land on land. I've disliked the idea that we must use the ocean since I've been a kid following space stuff. No, really -- Crew Dragon especially; those four parachutes are overkill. Touching down on land is gonna be easy peasy. Scuff the heat shield up a bit ... so what. Better than seawater.

 

/shrug

16 minutes ago, Unobscured Vision said:

Yep, saw this.

 

Crew Dragon does have the capability to land anywhere, but of course won't be allowed to land anywhere but water unless it's an emergency. Frankly I think ocean landings are "old school" and need to be rethought. Big waste of resources for recovery not to mention refurbishing the spacecraft (considering how much havoc seawater causes).

 

Seriously, set up a 50 x 200 mile touchdown area in the Western or Southern U.S. (or both) designated as a Recovery Area so that Commercial Crew spacecraft can land on land. I've disliked the idea that we must use the ocean since I've been a kid following space stuff. No, really -- Crew Dragon especially; those four parachutes are overkill. Touching down on land is gonna be easy peasy. Scuff the heat shield up a bit ... so what. Better than seawater.

 

/shrug

Boeing agrees that seawater is no good for their Starliner capsule, there are better ways to get them down :) 

 

 

https://en.wikipedia.org/wiki/Boeing_CST-100_Starliner

9 hours ago, Steven P. said:

Boeing agrees that seawater is no good for their Starliner capsule, there are better ways to get them down :) 

 

 

https://en.wikipedia.org/wiki/Boeing_CST-100_Starliner

 

Assuming the heat shield separates so the bags can inflate. If not, things get bumpy.

  • Like 1
  • Thanks 1
  • 4 weeks later...
  • 3 weeks later...
  • 3 weeks later...

The Crew Dragon In-Flight Abort test FCC permit is in.

 

Pad LC-39A

Simulated second stage

 

The start date further indicates the Starship pad mods should be done by then.

 

Start date: November 23, 2019
End date: May 23, 2020

 

Quote


Please explain in the area below why an STA is necessary:

This application uses information from previous grant, 1829-EX-ST-2019. This STA is necessary to authorize launch vehicle communications for SpaceX Mission 1357, a launch from Complex 39a, Kennedy Space Center. The application includes a sub-orbital first stage, and a simulated orbital second stage. Trajectory data shall be provided directly to NTIA, USAF, and NASA. All downrange Earth stations are receive-only. Launch licensing authority is FAA Office of Commercial Space Transportation.

  • 2 weeks later...

SpaceX now has TWO vessels capable of recovering Crew Dragon; GO Searcher and GO Navigator. 

 

And in a rather ambiguous tweet Musk simply said "A Shortfall Of Gravitas." Will it still be a droneship? "Yes" 

 

Starship capable? We'll see.

 

 

 

 

 

  • Like 1
On 10/9/2019 at 2:08 PM, DocM said:

SpaceX now has TWO vessels capable of recovering Crew Dragon; GO Searcher and GO Navigator. 

 

And in a rather ambiguous tweet Musk simply said "A Shortfall Of Gravitas." Will it still be a droneship? "Yes" 

 

Starship capable? We'll see.

 

 

 

 

 

What do you mean by "Starship capable"?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      228
    3. 3
      PsYcHoKiLLa
      163
    4. 4
      Steven P.
      76
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!