Recommended Posts

Date: January 11, 2020

Time: TBA, but likely in the AM

 

Doing this from the top of a screaming booster rocket at MaxQ - the highest launch loads,

 

 

NASA....

 


KENNEDY SPACE CENTER, Fla. (NASA PR)  NASA and SpaceX are targeting no earlier than Jan. 11, 2020, for a critical In-Flight Abort Test of the Crew Dragon spacecraft from Launch Complex 39A at the Kennedy Space Center, Florida, pending U.S. Air Force Eastern Range approval.

As part of the test, SpaceX will configure Crew Dragon to trigger a launch escape shortly after liftoff and demonstrate Crew Dragons capability to safely separate from the Falcon 9 rocket in the unlikely event of an in-flight emergency. The demonstration also will provide valuable data toward NASA certifying SpaceXs crew transportation system for carrying astronauts to and from the International Space Station.

The demonstration of Crew Dragons launch escape system is part of NASAs Commercial Crew Program and is one of the final major tests for the company before NASA astronauts will fly aboard the spacecraft.

The In-Flight Abort Test follows a series of static fire engine tests of the spacecraft conducted Nov. 13 near SpaceXs Landing Zone 1 on Cape Canaveral Air Force Station in Florida. SpaceX will also conduct a static fire test of its Falcon 9 rocket ahead of the In-Flight Abort Test.

  • Like 1
7 hours ago, FloatingFatMan said:

Ridiculous.  Dragon 2 should be using it's SuperDraco's to LAND as well as escape the pad... Parachute should just be there as yet another backup...

 

I completely agree but NASA made the certification process so expensive, requiring several orbital test launches and reentries, SpaceX decided to put those funds into Starship.

 

Background,

 

When SpaceX proposed propulsive landings in the 2011 concept video NASA never thought SpaceX would follow through. Next thing NASA knows Crew Dragon is doing hover tests & landing boosters and it's "OH, S**T! They're actually going to do it!!." In comes the expensive test program to "discourage" SpaceX from using propulsive in Commercial Crew.

 

NASA got the desired result, but now SpaceX is far more willing to develop Starship and future vehicles without NASA strings. They'll do like Falcon Heavy; develop it, fly it publicly with a big splash - gathering tons of telemetry, then slap it on the table and take orders.

  • Like 2
  • 3 weeks later...
2 hours ago, anthdci said:

how far down range is it likely to get before separation? you can normally eyeball it at max q can't you? We will therefore have a good view of it weather depending.

 

The abort should happen at or about T+58 seconds, which is when DM-1 hit MaxQ. Crew Dragon's planned touchdown is about 31km down range.

 

 

On 1/7/2020 at 10:26 AM, anthdci said:

how far down range is it likely to get before separation? you can normally eyeball it at max q can't you? We will therefore have a good view of it weather depending.

Been reading T+88 ... which I believe is around 14km or so up (though I believe it will launching on an ISS trajectory).

Animation

 

 

So from that... looks like 90 seconds after launch, at an altitude of ~21km and a downrange distance of ~3km, the fun happens. Dragon will reach an apogee of ~40km and splashdown ~32km downrange.

 

 

 

The test appears to be all successful.  

 

RIP B1046 (from reddit)... 

Quote

B1046 is the first Block 5 Falcon 9 booster. It features a bolted octaweb (as opposed to welded), SpaceX proprietary heat shielding on inconel mountings, titanium grid fins, retractable black landing legs, man-rated Merlin 1D engines (boasting a ~10% thrust increase over previous versions), COPV 2.0, and a black interstage. The upgrade allows Falcon 9 man-rating while affording a performance boost. It is hoped that the block 5 upgrades will enable rapid and routine reusability of Falcon 9 1st stages. On August 7, 2018, B1046 became the first-ever Falcon 9 booster to fly two consecutive GTO missions. On December 3, 2018, B1046 became the first-ever Falcon 9 booster to fly a third time (SSO-A mission). In April 2019, the booster was first mentioned as being manifested to fly the Crew Dragon In-Flight Abort Test, which was previously slated to fly on B1048. Booster recovery has been deemed impractical for the abort test, which will mark B1046's fourth and final flight.

 

Also, to me it looks like they remote detonated it (vs. it breaking up).  Would be nice if that was confirmed. (Edit: Nope, it was not detonated...it broke apart as planned)

 

 

Capture.thumb.PNG.5f13248b305f3433073226bd8164c59d.PNG

They kept mentioning that the computers determine the best time for the Dragon to abort after it hits Max Q, but in a real life situation it wouldn't have to wait until it hit Max Q correct?  They were just looking for the worse case scenario and were making sure it would pass that test?

It can escape anytime from pad throughout ascent ... this test was conducted when the vehicle was under max stress: 

 

"SpaceX has configured Crew Dragon to intentionally trigger a launch escape after Max Q, the moment of peak mechanical stress on the rocket."  SpaceX Press Kit

  • Thanks 1

Now that we have a successful test (after boeings failures) NASA can start planning the Crew launch.

 

We should now see how many articles we can find over the next few days trying to make out that the explosion was a bad thing or that the test was a failure. I've already seen a couple with misleading titles, but correctish content.

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

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!