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

    • Microsoft further improving Windows 11 Taskbar with latest builds by Sayan Sen Microsoft has released new Windows 11 builds for users flighting the Experimental channels. The new builds are 26300.8758 for Windows 11 26H2, 28120.2374 for 26H1, and 29617.1000 for future platforms. There are improvements related to the Taskbar, File Explorer and more with the new update. The full changelogs are given below: First we have the build 26300.8758: Changes and improvements gradually being rolled out [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience. UI showing the new Taskbar Size setting in Settings. We've also made refinements to the transitions between taskbar sizes for a smoother overall experience. [File Explorer] We've improved the reliability of thumbnail previews for cloud files in the Details pane. The pane has also been reorganized so file properties are easier to find and review at a glance. Fixed an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run in administrative mode. Fixed an issue where the confirmation dialog might display an internal Recycle Bin file name instead of the original file name when permanently deleting a file. [Sounds] Improved system sounds when using Windows in dark mode. Up next we have build 28120.2374: Changes and improvements gradually being rolled out This update includes a small set of general improvements and fixes [Mobile Device Settings] You can add and manage your mobile devices in Settings under Bluetooth & Devices > Mobile Devices. On this page, you can manage features such as using your device as a connected camera or accessing your device's files in File Explorer. [Remote Recovery Management] Added a recovery remote management plug-in to extend WinRE management capabilities for MDM providers. [Input] The emoji panel (Windows key + period (.)) now uses GIPHY as the GIF provider, delivering a smoother GIF browsing and sharing experience following the deprecation of the Tenor API. Finally we have the changelog for Windows 11 build 29617.1000: Changes and improvements gradually being rolled out [Windows Update] As announced in the Windows Update announce blog, we are now bringing a new unified update experience to reduce the number of reboots you see per month. We are starting by coordinating driver, .NET, and firmware updates to align with the monthly quality update, reducing the update experience to a single monthly restart. See the blog for more information. [Windows Magnifier] Magnifier now gives you more control over how you zoom. You can type an exact zoom percentage directly in the magnifier toolbar to land on precisely the level you need. We've also added preset step increments (5%, 10%, 25%, 50%, 100%, 150%, 200%, and 400%) to the Settings dropdown, so you can jump to common levels in a single click. Whether you need a subtle boost or a dramatic close-up, Magnifier adapts to how you want to zoom. Enter an exact percentage or jump to preset steps —5% up to 400%. Feedback: Share your thoughts in Feedback Hub (WIN + F) under Accessibility > Magnifier. [Accessibility] We're introducing screen tint, a new accessibility setting that applies a color overlay across your entire display, softening its intensity so it's easier on your eyes throughout the day. If bright, saturated screens leave you with tired or sensitive eyes by the end of a long session, screen tint can help. Screenshot showing UI for screen tint in Accessibility, with color presets and a strength slider. To get started, open Settings > Accessibility (or press WIN + U) and look for screen tint under the Vision section. From there, you can: Pick from six preset colors or choose a custom color of your own. Adjust the tint strength slider from a subtle wash to full intensity. Night light warms your display to reduce blue light that can interfere with sleep. Screen tint reduces overall screen intensity to ease eye fatigue and light sensitivity during the day. They tackle different problems and you can use both at the same time, one working on warmth and the other on intensity. Note that turning on screen tint will disable color filters, and vice versa. If you currently rely on color filters, you might need to keep screen tint turned off. Feedback: Share your thoughts in Feedback Hub (WIN + F) under Accessibility > Narrator. [Voice Access] Voice Access now supports Portuguese (Portugal), Portuguese (Brazil), and Korean (South Korea). [Audio] Continuing our work on improving Sound Settings, we've made a few more updates in this build: We've adjusted the description text for the Allow option in properties for audio devices to include the current state of the device, to improve the clarity of the text and the purpose of the button actions. "Listen to this device" is now available in properties for audio devices, so you don't need to enter Control Panel for this functionality. [Multiple Desktops] Improved explorer reliability when switching between multiple desktops. [Storage] We've updated the dialog when creating a Dev Drive to now support specifying the size in GB instead of only MB. This has also been added when changing the size of volumes under Settings > System > Storage. [Personalization] This update improves color selection accuracy when adjusting your accent color to match your wallpaper when automatic accent color selection is enabled in Personalization settings. This update improves wallpaper persistence reliability across restarts and upgrades, including better support for large-resolution wallpapers and other scenarios to prevent solid color wallpaper fallback. [Display and Graphics] Improves the reliability and persistence of applying color profiles. You can view the official blog posts here (link1, link2, link3) on Microsoft's site.
    • Windows 11 is getting redesigned taskbar settings in new build by Taras Buria Microsoft is rolling out new Windows 11 preview builds in the Insider program, offering users new features and changes to try ahead of public release. In the Experimental channel (formerly Dev), Microsoft is shipping build 26300.8758, while in the Beta channel, users can download build 26220.8754. The changelogs do not contain much, but there is an important update to taskbar settings. Here is what is new in build 26220.8754: [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience. We've also made refinements to the transitions between taskbar sizes for a smoother overall experience. [File Explorer] We've improved the reliability of thumbnail previews for cloud files in the Details pane. The pane has also been reorganized so file properties are easier to find and review at a glance. Fixed an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run in administrative mode. Fixed an issue where the confirmation dialog might display an internal Recycle Bin file name instead of the original file name when permanently deleting a file. [Sounds] Improved system sounds when using Windows in dark mode. And here is what is new in build 26220.8754: [Smart card removal policy] Administrators can now configure Azure Virtual Desktop (AVD) and Windows 365 sessions that use Microsoft Entra ID (RDS AAD Auth) authentication to automatically disconnect when a redirected smart card is removed. This extends smart card removal policy enforcement to Microsoft Entra authenticated remote sessions, helping organizations meet security and compliance requirements. [File Explorer] Fixed an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run in administrator mode. [Taskbar] Improved reliability of loading the system tray area of the taskbar. [Sounds] Improved system sounds when using Windows in dark mode. You can find release notes for build 26300.8758 here and for build 26220.8754 here.
    • Correct. Thank you unfortunately commenting on this stupid article we bring a possible more crap like that. If it gets click they post it
    • Firefox 152.0.3 by Razvan Serea Firefox is a fast, full-featured Web browser. It offers great security, privacy, and protection against viruses, spyware, malware, and it can also easily block pop-up windows. The key features that have made Firefox so popular are the simple and effective UI, browser speed and strong security capabilities. Firefox has complete features for browsing the Internet. It is very reliable and flexible due to its implemented security features, along with customization options. Firefox includes pop-up blocking, tab-browsing, integrated Google search, simplified privacy controls, a streamlined browser window that shows you more of the page than any other browser and a number of additional features that work with you to help you get the most out of your time online. Firefox key features Enhanced Tracking Protection (ETP) – Blocks trackers, cookies, cryptominers, and fingerprinters by default. Private Browsing Mode – Deletes history, cookies, and temporary files when closed. Lightweight & Fast Performance – Optimized memory usage with efficient page loading. Cross-Platform Sync – Sync bookmarks, passwords, history, and open tabs across devices. Customizable Interface – Toolbars, themes, and extensions can be tailored to user needs. Strong Privacy Controls – Options to manage cookies, permissions, and site data easily. Reader Mode – Strips away clutter for distraction-free reading. Pocket Integration – Save and read articles offline with Pocket built into Firefox. Picture-in-Picture (PiP) – Watch videos in a floating window while multitasking. Extensions & Add-ons – Vast library for productivity, security, and personalization. Built-in PDF Viewer – No need for external software to view PDFs. Firefox Monitor – Alerts users if their email is part of a known data breach. Multi-Account Containers – Isolate browsing sessions (e.g., work, personal, shopping). Performance & Resource Efficiency – Uses fewer system resources than some competitors. Open Source & Community-Driven – Transparent development with global contributions. Firefox 152.0.3 fixes: Fixed an issue that could cause extreme memory usage and freezing on startup for users with language packs installed. (Bug 2049845) Download: Firefox 64-bit | Firefox 32-bit | ARM64 | ~70.0 MB (Freeware) Download: Firefox for MacOS | 146.0 MB View: Firefox Home Page | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      440
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!