Recommended Posts

So EchoStar is now after CRS-10

Latest dates are:

Feb 14 - Falcon 9 - CRS 10 (was 8th Feb)

Late Feb - Falcon 9 - EchoStar 23 (possibly 28th Feb, was Jan)

and now March - Falcon 9 - SES 10 (was 22nd Feb)

 

 

 

1 hour ago, philcruicks said:

So EchoStar is now after CRS-10

Latest dates are:

Feb 14 - Falcon 9 - CRS 10 (was 8th Feb)

Late Feb - Falcon 9 - EchoStar 23 (possibly 28th Feb, was Jan)

and now March - Falcon 9 - SES 10 (was 22nd Feb)

 

 

 

Aye, time are as follows too: 

Feb 14th 2017 16:34 UTC SpX CRS-10

Feb 28th 05:27-07:57 UTC Echostar 23

 

Hopefully SES-10 is daytime too, would love seeing some decent shots of the core coming back (again!)

4 hours ago, philcruicks said:

So EchoStar is now after CRS-10

Latest dates are:

Feb 14 - Falcon 9 - CRS 10 (was 8th Feb)

Late Feb - Falcon 9 - EchoStar 23 (possibly 28th Feb, was Jan)

and now March - Falcon 9 - SES 10 (was 22nd Feb)

Yup. NASA pulled rank. They want Dragon up as soon as the lab mice are old enough, which is the 14th.  SpaceX may well have been able to launch Echostar 23 next week and done a fast turnaround, all the stages and payloads are at the cape, but NASA has its calandar checked.

FCC STA to test Falcon 9 and Falcon Heavy at McGregor. The F9's are likely the reused FH boosters with FH specific telemetry hardware.

 

FAA....

 


Operation Start Date: 02/10/2017
Operation End Date: 08/10/2017
>
This STA is required for testing of the Falcon 9 and Falcon Heavy launch vehicle systems from the SpaceX Rocket Development and Test Facility in McGregor, Texas.

  • Like 1
56 minutes ago, DocM said:

Operation Start Date: 02/10/2017
Operation End Date: 08/10/2017
>
This STA is required for testing of the Falcon 9 and Falcon Heavy launch vehicle systems from the SpaceX Rocket Development and Test Facility in McGregor, Texas.

If I see another 6 month related timescale for FH I'll flip out ;) 

 

Quote

Congressional Investigators Warn of SpaceX Rocket Defects

 

Government Accountability Office’s preliminary findings show persistent cracking of vital propulsion-system components

 

So, who is the Rogozin of the U.S. Space Industry? :D 

Quote

The newspaper says the report has found a "pattern of problems" with the turbine blades within the turbopumps, which deliver rocket fuel into the combustion chamber of the Merlin rocket engine. Some of the components used in the turbopumps are prone to cracks, the government investigators say, and may require a redesign before NASA allows the Falcon 9 booster to be used for crewed flights. NASA has been briefed on the report's findings, and the agency's acting administrator, Robert Lightfoot, told the newspaper that he thinks “we know how to fix them.”

 

A spokesman for SpaceX, John Taylor, said the company already has a plan in place to fix the potential cracking issue. "We have qualified our engines to be robust to turbine wheel cracks," Taylor said. "However, we are modifying the design to avoid them altogether. This will be part of the final design iteration on Falcon 9." This final variant of the Falcon 9 booster, named Block 5, is being designed for optimal safety and easier return for potential reuse. According to company founder Elon Musk, it could fly by the end of this year.

 

ArsTechnica

 

Quote

In an email to Reuters, SpaceX said it has "qualified our engines to be robust to turbine wheel cracks. However, we are modifying the design to avoid them altogether,” said spokesman John Taylor.

 

In addition to flying cargo to the International Space Station, SpaceX has NASA contracts to begin flying astronauts to the orbiting research laboratory as early as 2018.

 

"SpaceX has established a plan in partnership with NASA to qualify engines for manned spaceflight," Taylor said.

 

Reuters

Andy Pasztor has written critical articles about SpaceX in the past.

  • Like 1
4 hours ago, Mirumir said:

So, who is the Rogozin of the U.S. Space Industry? :D 

As +jjkusaf said, Andy Pasztor trolls SpaceX on a regular basis. 

 

Microcracking in turbo machinery is not new, and most jet engines have blades with microcracks due to heating and cooling cycles. In a rocket engine shutdowns and then restarting with hot blades and cryogenic propellants are a big factor, such as doing the F9 boostback burn shortly after MECO. The Space Shuttle Main Engines exhibited them too.

 

You design the blades to be tolerant of microcracking, sometimes with shot-peening treatments which help change the surface region to resist microcrack propogation. 

 

NASA and SpaceX have been working on the final fix for F9 Block 5, which is what will fly people and those won't be reused stages.

 

Key points to remember:

 

300+ flown Merlin's, zero pump failures.

 

During Merlins qualification tests, they tossed steel nuts into a running Merlin's pumps and they didn't fail.

 

The JCSat 14 stage has had its engines fired for individual engine qualification, the full 9 for the preflight stage burn, the static fire, launch and recovery, and 8 more mission burns at McGregor with no refurbishment between firings and it's still going. They plan to keep firing it to engine or tank failure.

 

 

  • Like 2

Following up....

 

And btw: this issue was first reported months ago, understood fully and is mainly a re-use issue.

 

IMO, as usual wrt SpaceX and other commercial operators Andy P. got hold of an illegally leaked draft copy of the report, made a pretzel of its context and here we are.

 

Andy P. and Loren Thompson at Forbes, who is a paid "consultant" for the major aerospace companies, need to be taken with a large portion of salt when theyre writing about NewSpace.

 

http://uk.reuters.com/article/us-space-spacex-idUKKBN15H307

 

Quote

 

SpaceX says fix underway for rocket turbine wheel cracking

 

By Irene Klotz | CAPE CANAVERAL, FLA. SpaceX's final version of the Falcon 9 rocket, which Elon Musk aims to launch before the end of the year, will fix a potential problem with cracks in its turbopumps, the company said on Thursday. Its statement followed a report that the U.S. Government Accountability Office will flag turbine wheel cracks in the rocket's turbopumps as a safety issue. NASA, the U.S. space agency, and the Air Force are among SpaceX's customers.

 

The GAO’s preliminary findings were reported by the Wall Street Journal on Thursday.

 

In an email to Reuters, SpaceX said it has "qualified our engines to be robust to turbine wheel cracks. However, we are modifying the design to avoid them altogether,” said spokesman John Taylor.

 

In addition to flying cargo to the International Space Station, SpaceX has NASA contracts to begin flying astronauts to the orbiting research laboratory as early as 2018.

 

"SpaceX has established a plan in partnership with NASA to qualify engines for manned spaceflight," Taylor said.

 

GAO investigators found that the Falcon 9 turbopumps, which are part of the system that delivers propellants to the engine, have blades that are prone to cracking, the newspaper said.

 

SpaceX last month resumed flights following a 4-1/2-month investigation into why a rocket blew up as it was being fueled for a routine pre-launch test in Florida.

 

The cause of the accident was traced to a burst canister of helium in the rocket’s second stage liquid oxygen tank. It was unrelated to the issue with the rocket’s turbopumps.

 

The accident was SpaceX's second since the Falcon 9 debuted in June 2010. The company's next launch is targeted for Feb. 14.

 

 

  • Like 2

That turbopump microcracking issue is something that has happened to every jet and rocket engine ever produced -- EVER. It's not something new. What IS new-ish is the fact that only, only two vehicles have ever, in history, have reused rocket engines -- the Space Shuttle and now the Falcon 9 S1 -- and it's only now becoming an issue, 40 years later?

 

SSME's have had a single failure during flight unrelated to turbopumps. The Merlin-D has not. They've re-fired the recovered S1's a lot and not a single one of them has failed to do its' job. Full-cycle firings too.

 

The "dirt-throwing" is by those favorable to ULA and OldSpace interests. That's all it is. I wouldn't give it much credence ... but SpaceX is going to do the responsible thing anyway because they're SpaceX. They'll eliminate a potential failure point because it's a challenge, and because they don't want something biting them in the ass later on that they could have done something about. It's an abundance of caution, and SpaceX isn't about to be accused of being "negligent".

  • Like 2

And another point -- whoever leaked that confidential GAO/OIG report?? THEY DESERVE THEIR ####### HEAD ON A PLATTER. Inexcusable that a confidential report dell into the hands of someone who isn't even in the INDUSTRY, let alone someone who doesn't have the credentials to handle such material in the first place. Industrial Espionage at minimum, regardless of who it is -- that's not something to be taken lightly. SpaceX should be ###### that it fell into the hands of someone who shouldn't have it.

 

This is another example -- yet another example -- that the "swamp needs draining". I'm someone who knows what the regs were in the early 90's at least -- and this is serious. I don't like this a bit. Leaking classified ANYTHING is a problem. This is meant to be handled internally, through the correct channels and by correct procedures. SpaceX was already notified.

  • Like 1

I would assume that NASA will take this breach of confidence in hand and do a little digging. This activity is not acceptable towards any company..period.

 

Very bad manners....insert +John avatar shaking finger at them....bad...bad bad bad...:woot:

I'm not sure that NASA will be the ones handling this. If it's a GAO leak it'll be handled by them; if it's OIG it'll be their ball. But I suspect that whoever let it out is going to wish they hadn't.

 

Sorry to keep on about this, but it's a very serious matter that I'm particularly sensitive to. /shrug

  • Like 1
Just now, Unobscured Vision said:

I'm not sure that NASA will be the ones handling this. If it's a GAO leak it'll be handled by them; if it's OIG it'll be their ball. But I suspect that whoever let it out is going to wish they hadn't.

 

Sorry to keep on about this, but it's a very serious matter that I'm particularly sensitive to. /shrug

I am not impressed by the leaks as well...no company would be.  This must be addressed.

  • Like 1

Well I'm sure that SpaceX is right p####d about it. They don't like or need any tarnishing of their name by true asshats who are only out to throw dirt on behalf of OldSpace. And if the article is correct (and I assume it is), SpaceX are already working on the fix(es) for the Block-5 variants of the Merlin engines. Who knows -- this might end up working in their favor; some overlooked performance gains that are garnered from a redesigned turbopump would sure justify the hassle. :yes: 

 

Silver linings, potentially. They eliminate a failure point and improve the performance at the same time? Winner winner chicken dinner.

  • Like 1

Micro fractures are a fact of life with turbines. In fact anything operating at high speeds and temperature extremes. The issue will be dealt with...in the meantime, ask the others launchers to return a stage for inspection......."crickets"

 

One stage has been tested under full duration runs for 8 times, including a launch and return....of course this unit also has micro cracks and is apparently misbehaving because it's still intact.

 

This is an old non story...the news smear and leak are the issue.

  • Like 2

Yep, exactly. A fact of life with these types of engines. The RS-25's had the same problems, same reports, and never a failure with those either.

 

I doubt seriously that we'd ever get the other manufacturers to hold to these standards. This is territory that is really in a space (no pun intended) that few have ventured ... and SpaceX is displaying the sheer robustness of their hardware openly. Their stuff is on the table, and peer review is encouraged. The RS-25's didn't have this level of openness until MUCH later.

 

So yeah.

 

I agree with you, DD. The smear and leak are the real issue here.

  • Like 1

Just to give a little context, passenger aircraft will show turbine micro cracks during major inspection every few years. How many passengers will that aircraft have safely delivered. And yes, the reference is a valid one, the time scales are different.

 

I am not stating that it needs to be ignored, the situation is being addressed. The advantage is the modern manufacturing techniques, comprehensive data sets, the likes of which no one else has in this field, and enhanced material science that is available.

 

:)

 

As a side note, do you think that a SpaceX astronaut would have issues going for a ride...they'd laugh and say..."buckle up" it's show time.

  • Like 1
This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • 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.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

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

    Love Neowin? Tell a friend!