Recommended Posts

So let me get this right. One of the engines blew up but the rocket was able to keep going and it made it to orbit and everything including the capsule is on course as planned? really? I can't get my head around it? Wow amazing if I understand this correctly?

Approximately one minute and 19 seconds into last night?s launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket?s nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued immediately. We know the engine did not explode, because we continued to receive data from it. Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure release, and that none of Falcon 9?s other eight engines were impacted by this event.

As designed, the flight computer then recomputed a new ascent profile in real time to ensure Dragon?s entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there was no effect on Dragon or the cargo resupply mission.

Falcon 9 did exactly what it was designed to do. Like the Saturn V, which experienced engine loss on two flights, Falcon 9 is designed to handle an engine out situation and still complete its mission.

Yeah, the semi-conical fairings at the corners pf the 3x3 engine grid. In the coming Falcon 9 v-1.1 these will be absent because of its octagonal + 1 center engine arrangement. It debuts 2 flights from now and will be much larger - this F9 was 157 feet tall and the v-1.1 bird will be 229 feet tall and have an all new engine.

Update;

SpaceX statement. No explosion, just a rather exciting shutdown sequence.

Of note: Apollo 6 lost 2 engines on its second stage and Apollo 13 lost the center engine of its first stage.

The Dragon spacecraft is on its way to the International Space Station this morning and is performing nominally following the launch of the SpaceX CRS-1 official cargo resupply mission from Cape Canaveral, Florida at 8:35PM ET Sunday, October 7, 2012.

Approximately one minute and 19 seconds into last night's launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket's nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued. We know the engine did not explode, because we continued to receive data from it. Panels designed to relieve pressure within the engine bay were ejected to protect the stage and other engines. Our review of flight data indicates that neither the rocket stage nor any of the other eight engines were negatively affected by this event.

As designed, the flight computer then recomputed a new ascent profile in real time to ensure Dragon's entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there was no effect on Dragon or the cargo resupply mission.

Falcon 9 did exactly what it was designed to do. Like the Saturn V (which experienced engine loss on two flights) and modern airliners, Falcon 9 is designed to handle an engine out situation and still complete its mission. No other rocket currently flying has this ability.

It is worth noting that Falcon 9 shuts down two of its engines to limit acceleration to 5 g's even on a fully nominal flight. The rocket could therefore have lost another engine and still completed its mission.

We will continue to review all flight data in order to understand the cause of the anomaly, and will devote the resources necessary to identify the problem and apply those lessons to future flights. We will provide additional information as it becomes available.

Dragon is expected to begin its approach to the station on October 10, where it will be grappled and berthed by Akihiko Hoshide of the Japan Aerospace Exploration Agency and Expedition 33 Commander Sunita Williams of NASA. Over the following weeks, the crew will unload Dragon's payload and reload it with cargo to be returned to Earth. Splashdown is targeted for October 28.

Update on the engine failure says that its fuel dome cracked or perforated. This is analogous to a car engine suffering a cracked or prrforated cylinder head vs. a blown engine where the block fractures and the bolts let go.

The gases leaked ny the fuel dome caused the combustion chamber pressure drop that triggered the engine shutdown, and these same gases caused a pressure increase in the #1 engines bay that caused the safety panels to be jettisoned to reduce said pressure - just as they were supposed to do.

So, this was not an engine explosion but a series of safety mechanisms doing what they were supposed to do.

In this wireframe of the Merlin engine the fuel dome is the larger red portion at the top of the blue combustion chamber.

aa78b394999ce40837b114a0b6357678.jpg

Current NASA TV timings:

October 10, Wednesday

4 a.m. - Coverage of the Grapple of the SpaceX/Dragon CRS-1 at the International Space Station (Grapple scheduled at 7:22 a.m. ET) - JSC (All Channels)

9:15 a.m. - Coverage of the Berthing of the SpaceX/Dragon CRS-1 to the International Space Station (Berthing begins at 9:40 a.m. ET) - JSC (All Channels)

All times Eastern

  • 3 weeks later...

Dragon CRS-1/SPX-1 has safely returned to Earth, and so close to the recovery ship SpaceX tweeted this just after splashdown -

If we keep landing this precisely, we're going to have to start issuing the recovery team titanium umbrellas. #Dragon

NASA press release -

RELEASE: 12-381

SPACEX DRAGON RETURNS FROM SPACE STATION WITH NASA CARGO

HOUSTON -- A Space Exploration Technologies (SpaceX) Dragon spacecraft splashed down in the Pacific Ocean at 2:22 p.m. CDT Sunday a few hundred miles west of Baja California, Mexico. The splashdown successfully ended the first contracted cargo delivery flight contracted by NASA to resupply the International Space Station.

"With a big splash in the Pacific Ocean today, we are reminded American ingenuity is alive and well and keeping our great nation at the cutting edge of innovation and technology development," NASA Administrator Charles Bolden said. "Just a little over one year after we retired the Space Shuttle, we have completed the first cargo resupply mission to the International Space Station. Not with a government owned and operated system, but rather with one built by a private firm -- an American company that is creating jobs and helping keep the U.S. the world leader in space as we transition to the next exciting chapter in exploration. Congratulations to SpaceX and the NASA team that supported them and made this historic mission possible."

The Dragon capsule will be taken by boat to a port near Los Angeles, where it will be prepared for a return journey to SpaceX's test facility in McGregor, Texas, for processing. Some cargo will be removed at the port in California and returned to NASA within 48 hours. This includes a GLACIER freezer packed with research samples collected in the orbiting laboratory's unique microgravity environment. These samples will help advance multiple scientific disciplines on Earth and provide critical data on the effects of long-duration spaceflight on the human body. The remainder of the cargo will be returned to Texas with the capsule.

The ability to return frozen samples is a first for this flight and will be tremendously beneficial to the station's research community. Not since the space shuttle have NASA and its international partners been able to return considerable amounts of research and samples for analysis.

The Dragon launched atop a SpaceX Falcon 9 rocket from Cape Canaveral Air Force Station in Florida, on Oct. 7. It carried 882 pounds of cargo to the complex, including 260 pounds of crew supplies, 390 pounds of scientific research, 225 pounds of hardware and several pounds of other supplies. This included critical materials to support 166 scientific investigations, of which 63 were new. Returning with the Dragon capsule was 1,673 pounds of cargo, including 163 pounds of crew supplies, 866 pounds of scientific research, and 518 pounds of hardware.

The mission was the first of at least 12 cargo resupply missions to the space station planned by SpaceX through 2016 under NASA's Commercial Resupply Services contract.

SpaceX is one of two companies that built and tested new cargo spacecraft under NASA's Commercial Orbital Transportation Services (COTS) program. Orbital Sciences is the other company participating in COTS. A demonstration flight of Orbital's Antares rocket and Cygnus spacecraft to the station is planned in early 2013.

NASA initiatives like COTS and the agency's Commercial Crew Program are helping develop a robust U.S. commercial space transportation industry with the goal of achieving safe, reliable and cost-effective transportation to and from the space station and low-Earth orbit. In addition to cargo flights, NASA's commercial space partners are making progress toward a launch of astronauts from U.S. soil in the next 5 years.

While NASA works with U.S. industry partners to develop and advance these commercial spaceflight capabilities, the agency also is developing the Orion spacecraft and the Space Launch System (SLS), a crew capsule and heavy-lift rocket to provide an entirely new capability for human exploration. Designed to be flexible fo launching spacecraft for crew and cargo missions, SLS and Orion will expand human presence beyond low-Earth orbit and enable new missions of exploration in the solar system.

For more information about the International Space Station, visit:

http://www.nasa.gov/station

For more information about NASA's commercial space programs, visit:

http://www.nasa.gov/exploration/commercial

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!