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

    • 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
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • 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
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!