Recommended Posts

7 hours ago, IsItPluggedIn said:

I have no idea what this says. Can we please have this in English or French, I can do French. 

i think @DocM got it right :) (we've the long road of discussions) but if you'd like to know: Clowns never have been good for Rocketry Science.  By the way..

Quote

Additionally, a November supply delivery to the International Space Station (ISS) under a contract SpaceX signed with NASA also had to be scrapped. (There are other companies and international space agencies that can deliver supplies to the ISS.)

http://www.csmonitor.com/Business/2016/1208/Will-SpaceX-lose-more-customers-after-September-rocket-explosion

the're high probability that 2017th will become last year for Musk.

No astros on Dragon2 next year :'(

 

First crewed flight slipped to at least may 2018. First uncrewed flight currently planned for November 2017.

 

http://www.floridatoday.com/story/tech/science/space/spacex/2016/12/12/spacexs-first-launch-astronauts-slips-2018/95354964/

Edited by Beittil

From the CCtCap

 

NASA updated Crew Dragon & Starliner schedules.

Slips due to NASA bureaucracy delays and dev issues (mainly Starliner, as discussed) 

SpaceX Demonstration Mission 1 (No Crew): November 2017
Boeing Orbital Flight Test (No Crew: June 2018
SpaceX Demonstration Mission 2 (Crew): May 2018
Boeing Crew Flight Test (Crew): August 2018

 

/sigh ....

 

So SpaceX needs to slow down (again) because NASA and everyone else can't keep up. The CCtCap is now four years behind schedule

 

Now it's just getting ridiculous. ULA, LH/M & Boeing are whining because they can't finish tasks on time, so they hold up the show. By the time they're ready to actually fly, SpaceX will be ready to test ITS. Or maybe that's the whole objective?

 

Looks like there's another swamp that needs draining ... the one at NASA. The culture that allows crap like this to happen is why the U.S. Space Program is the mess that it currently is.

  • Like 1

Well, hopefully the "climate" will shift beginning this Spring once the new Administration has had time to settle in and get things organized. This first six months is likely going to be just sorting out the messes (and there are many) and getting new Management up to speed.

 

Once there's been time to really take a good, thorough look at NASA, I guarantee that things are gonna avalanche ... and OldSpace ain't gonna like it one bit. Elon Musk might just end up in charge of NASA.

 

Crazy? It could happen, and isn't as far-fetched as it sounds ... :yes: 

The most discussed candidates for NASA Admin. are Rep. Jim Bridenstine (R-Oklahoma), who wrote a very interesting NASA reform proposal; Scott Pace, Director of the Space Policy Institute at George Washington University, a stay the course type; and....drumroll....Mike "The Stick" Griffin, daddy of Ares I. An outside shot of former Rep. Bob Graham, a member of the transition team and space advocate.

Brindenstine = okay choice ...

 

Pace I don't know much about, but if it's "stay the course" then it's a "nope" from me (followed by "wouldn't be prudent" hand gestures) ...

 

Mike Griffin = nausea and moon-shot barfing. Wasn't he already NASA Admin? (Okay, here comes the long-distance record ... this might be the "moon-shot" ... :rofl:)

1 hour ago, jjkusaf said:

Not really an update ... but one year ago today.  First time the first stage or an orbital rocket successfully landed vertically.

 

still gives me chills watching that. Cant wait for them to get flying again.

  • Like 1

From NASA's 2016 Commercial Crew progress review,

 

Quote

>
The year marked a substantial transition from design of critical elements and systems in previous years to the manufacturing of the spacecraft and launch vehicles, substantial modifications to launch complexes in Florida and the first integrated simulations of the teams that will oversee the flights. Along the way, advances were overseen by NASA engineers and the astronauts who will fly the spacecraft into orbit for the flight tests.
>
SpaceX performed five drop tests to evaluate the parachutes that must deploy to allow a returned Crew Dragon to land safely in the water. The SuperDraco engines that will be used on the first flight test were also hot-fired to qualify them for flight.

The company also ran a series of qualification tests on the spacesuits astronauts will wear during missions aboard Crew Dragon spacecraft. The evaluation included putting the suit in a vacuum chamber to see how it withstood conditions similar to those found in space outside a spacecraft.
>
SpaceX continued extensive modifications at Launch Complex 39A during 2016, which included pad structures being refurbished or rebuilt to serve Falcon 9 and Falcon Heavy rockets instead of the space shuttles that previously launched from it. Additionally, the Crew Access Arm has been built, and SpaceX expects to bolt it into place on the tower in 2017. The fixed service structure and its foundations were strengthened to handle higher-force hurricane winds and to provide a stronger base for the vertical integration crane planned for the complex in the future.


If the original plan holds, 2 more levels will be added to the FSS as well.

  • Like 2

Also,

 

These are being built in the new Dragon Hatchery in the former Triumph Aerostructures-Vought plant down the street from the SpaceX Hawthorne factory.

 

Quote

SpaceX has five Crew Dragon spacecraft in different levels of assembly. The company built and successfully tested one module to prove its environmental and life support systems and another as a structural test article. The three spacecraft that will fly the flight tests and the first operational mission to the space station are in various stages of production in SpaceX’s manufacturing facilities in Hawthorne, California.

Edited by DocM
  • Like 1

ITAR-compatable version of the AMOS-6 report. 

Return to flight: Iridium NEXT on January 8 from Vandenberg AFB.

January 2, 2017, 9:00am EST



Over the past four months, officials at the Federal Aviation Administration (FAA), the U.S. Air Force (USAF), the National Aeronautics and Space Administration (NASA), the National Transportation Safety Board (NTSB), along with several industry experts, have collaborated with SpaceX on a rigorous investigation to determine the cause of the anomaly that occurred September 1 at Space Launch Complex 40 (SLC-40) at Cape Canaveral Air Force Station in Florida. This investigation team was established according to SpaceX's accident investigation plan as approved by the FAA. As the primary federal licensing body, the FAA provided oversight and coordination for the investigation.

Investigators scoured more than 3,000 channels of video and telemetry data covering a very brief timeline of events – there were just 93 milliseconds from the first sign of anomalous data to the loss of the second stage, followed by loss of the vehicle. Because the failure occurred on the ground, investigators were also able to review umbilical data, ground-based video, and physical debris. To validate investigation analysis and findings, SpaceX conducted a wide range of tests at its facilities in Hawthorne, California and McGregor, Texas.

The accident investigation team worked systematically through an extensive fault tree analysis and concluded that one of the three composite overwrapped pressure vessels (COPVs) inside the second stage liquid oxygen (LOX) tank failed. Specifically, the investigation team concluded the failure was likely due to the accumulation of oxygen between the COPV liner and overwrap in a void or a buckle in the liner, leading to ignition and the subsequent failure of the COPV.

Each stage of Falcon 9 uses COPVs to store cold helium which is used to maintain tank pressure, and each COPV consists of an aluminum inner liner with a carbon overwrap. The recovered COPVs showed buckles in their liners. Although buckles were not shown to burst a COPV on their own, investigators concluded that super chilled LOX can pool in these buckles under the overwrap. When pressurized, oxygen pooled in this buckle can become trapped; in turn, breaking fibers or friction can ignite the oxygen in the overwrap, causing the COPV to fail. In addition, investigators determined that the loading temperature of the helium was cold enough to create solid oxygen (SOX), which exacerbates the possibility of oxygen becoming trapped as well as the likelihood of friction ignition.

The investigation team identified several credible causes for the COPV failure, all of which involve accumulation of super chilled LOX or SOX in buckles under the overwrap. The corrective actions address all credible causes and focus on changes which avoid the conditions that led to these credible causes. In the short term, this entails changing the COPV configuration to allow warmer temperature helium to be loaded, as well as returning helium loading operations to a prior flight proven configuration based on operations used in over 700 successful COPV loads. In the long term, SpaceX will implement design changes to the COPVs to prevent buckles altogether, which will allow for faster loading operations.

SpaceX is targeting return to flight from Vandenberg's Space Launch Complex 4E (SLC-4E) with the Iridium NEXT launch on January 8. SpaceX greatly appreciates the support of our customers and partners throughout this process, and we look forward to fulfilling our manifest in 2017 and beyond.

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • 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
  • Popular Contributors

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

    Love Neowin? Tell a friend!