Recommended Posts

5 hours ago, philcruicks said:

CRS 10 has slipped again to:

18th Feb 1501 GMT (10:01 a.m. EST)

Even better! 

 

52 minutes ago, jjkusaf said:

I love me some Sat/Sun launches...especially the morning ones.  Eat some pancakes, drink some coffee and watch a controlled explosion.

Amen! 1501UTC is a great time for a beer, some chips and a lovely bright Landing.

Especially when it'll be the first daylight landing at LZ-1. :yes: Worthy of tailgate parties and grills ... I know I'd rather tailgate one of these than football or [barf.suppression=1] Nascar. It'll be "full glory" mode this time.

  • Like 2

So long ago already, seems a bit unreal when you let that sink in :)

 

Also still remember everything from the COTS-2 demo mission as if it only happened just recently. Especially since Dutch astro Andre Kuipers was part of the capture team that very first time around :)

  • Like 2

My understanding is they want LC-40 back up and running by June or July. I'm expecting August or September, there's a lot of GSE that got trashed in the mishap that they want to upgrade (since they're doing work there anyway).

A bit OT, but what the hey 

 

http://www.teslarati.com/craft-brewery-opens-spacexs-backyard-creates-beer-employees/

 

Quote

 

When their shifts are over, SpaceX employees in Hawthorne, CA only have to walk a short way to their favorite new hangout: Los Angeles Ale Works. The soft opening of the area’s first craft brewery a couple of weeks ago has allowed SpaceX employees to personally sample a variety of what will be the house signatures brews — two-dozen taps pouring a wide variety of styles of small batch beer. Starting Thursday, when the grand opening will take place, crowds will descend upon the former industrial building and Hawthorne’s first brewery and tasting room. For now, a bunch of the SpaceX employees and locals have been savoring Los Angeles Ale Works’ inviting space.

 

Los Angeles Ale Works already serves two varieties named after SpaceX: a low-alcohol session India Pale Ale named Space XPA and a Space XPA Full Thrust double IPA.

 

 

SpaceX-beer-Hawthorne-Aleworks.jpg

  • Like 2

After all the handwriting by Andy Pasztor in WSJ, the GAO report on SpaceX  turbopump cracks is out.

 

For SpaceX the risks are getting enough Block 5 flights in before certification and the turbopump now non-issue  

 

Quote

During qualification testing in 2015, SpaceX identified cracks in the turbines of its engine. Additional cracks were later identified. Program officials told us that they have informed SpaceX that the cracks are an unacceptable risk for human spaceflight. SpaceX officials told us that they are working closely with NASA to eliminate these cracks in order to meet NASA’s stringent targets for human rating. Specifically, SpaceX has made design changes that, according to its officials, did not result in any cracking during initial life testing.

  • Like 2

I smell a deliberate stalling attempt here. Not once has a SpaceX Falcon-9 engine failed during launch. This is, at most, an issue of reuse -- which SpaceX have already said they wouldn't reuse for anything that would be flying people on-board, NASA regulations aside -- and those S1's would follow a recertification process before being flown again.

 

SpaceX have addressed the issue and they appear to have corrected it, however slight that issue was. They're SpaceX -- nothing left to chance. But what it says to my mind is that whomever initiated this whole fiasco (let's call it what it is) was acting on the interests of others. They had to be. There's no other explanation for anyone to be digging around inside the reports like this and making such a huge deal out of it when it was already being dealt with internally. Only someone who knew what they were looking for could find reports like this -- and since the Merlin designs are available for scrutiny, all it takes is a couple of Engineers who are familiar with such problems to point out design shortcomings. And turbopump cracking is an easy one. That's happened to just about every Jet and Rocket engine that uses turboprops or turbopumps. Same basic idea behind turbocharged anything, really.

 

When we look at who would benefit from such a delay and the time it takes in addressing the turbopump cracking "issue" -- something that never was made an issue during the Shuttle Program -- the usual players are right there, playing in their sandbox trying to look innocent.

 

I think someone in OldSpace initiated this fiasco as a way to stall for time. SpaceX have been making too many leaps in too short a time and OldSpace is getting stressed out about their inabilities to meet milestones or even get their gear to work properly.

 

And anyone who has ever had to deal with Mil/Gov Contractors knows how absolutely dirty they can be if they've been backed into a corner and are on a deadline. I've seen VP's shout down Majors before. Absolutely vicious ... ehh .. "people". They're used to getting their way and will go to some pretty extraordinary ends to do it.

 

Of course there will never be any "fessing up" about Industrial Harassment or anything. It's not illegal to harass your competitor -- regardless of it being generally bad behavior, and unprofessional as hell -- but more and more I get the sense that OldSpace just can't keep up, and will start resorting to tactics like these more often just to level the playing field unless some sort of "business arrangement" is made.

 

Like ULA and Orbital-ATK did. Talk about having cake and eating it .... yeeesh. That's a whole other subject.

There was one launch that did have an engine failure. It was one of the early Falcon 9 missions and the mission overall was successful even with the 1/9 failure. I can't remember which one but will try to look it up.

 

Edit: It was CRS-1

 

Having said that, I agree with everything you said. I think there is a level of "well that's just business" especially when there are billions of dollars at stake but it is still pretty sad that the industry as a whole pretty much stopped innovating in the 70s until SpaceX came along.

  • Like 1
7 minutes ago, rdlenk said:

There was one launch that did have an engine failure. It was one of the early Falcon 9 missions and the mission overall was successful even with the 1/9 failure. I can't remember which one but will try to look it up.

 

Edit: It was CRS-1

 

Having said that, I agree with everything you said. I think there is a level of "well that's just business" especially when there are billions of dollars at stake but it is still pretty sad that the industry as a whole pretty much stopped innovating in the 70s until SpaceX came along.

Yep... One engine failure... but it wasn't the turbo pump iirc, but a material defect in the chamber.  Cool thing about that failure is it didn't lead to RUD. :)

  • Like 1
16 minutes ago, jjkusaf said:

Yep... One engine failure... but it wasn't the turbo pump iirc, but a material defect in the chamber.  Cool thing about that failure is it didn't lead to RUD. :)

If anything it showed that the rocket would be fine if one/some did fail, and that the engine could power out without destroying itself

  • Like 2

CRS-1 was a partial failure as its secondary cargo (Orbcomm-2) had to be released early to meet ISS safety regulations and burned up in the atmosphere. Overall it did show the F9 to be very robust and demonstrated its engine-out capability. The secondary payload was only lost because of an abundance of cation (fully deserved when dealing with human life) for objects that might potentially get close to the ISS orbit. Orbcomm knew about this regulation and that it increased the chance of losing their payload but the agreed to it because they got a discount on launch fees. 

 

I brought this up only because Unobscured Vision said the F9 had never had an engine failure during launch which just isn't the case.  Maybe 'failure' is a strong word for CRS-1 as the engine actually just shut itself down due to a detected pressure drop in the chamber and did not really 'fail'. So if anything, it just reinfored how well F9 can deal with issues and gracefully handle anomalies.

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

    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
    • Windows 11 gets new audio improvements in the latest builds by Taras Buria Today's Experimental builds (26H1 and Future Platforms, formerly Canary) pack several audio-related improvements. If your device is enrolled in the Experimental Channel (26H1), you can download build 28120.2315, while those in the Future Platforms version have build 29613.1000 to try. Here is what is new in build 29613.1000: [Audio] Following up on our previous improvements, we’re making some more adjustments to Settings > System > Sounds based on your feedback. Namely, we’ve updated the “All sound devices” page so: You now have the ability to change default devices from this page. Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. We’ve adjusted the page design slightly so now you can filter whether you’re viewing input or output devices. We’ve added toggles so you can choose if you want to hide or show disabled, disconnected, and unplugged devices on this page. We’ve also updated the input and output audio properties page for devices in Settings to now include jack information for those that need it. And here is the changelog for build 28120.2315: This update includes a small number of minor bug fixes and improvements. [Accessibility] This update improves caption style responsiveness by redrawing captions immediately for caption style changes. If no current caption is visible, a sample caption string is displayed. [Audio] This update improves the reliability of the inbox HD Audio driver. You can find the official release notes for build 28120.2315 here and for build 29613.1000 here.
    • I agree with what I think you are saying, just not in the way you are saying it. Like any tool, the amount it represents your work is perorational to the effort you put into it. It is similar to why 2nd grade math students learning to add and subtract are not allowed to use calculators, but a high-school calculous student is. For the 2nd grader, that tool would completely replace the work they are doing, for the calculous student the same tool allows them to work far more effectively while in no way replacing their effort or knowable. If you spend 30 seconds writing a prompt, then the image that comes out is no more "yours" than if you found the same image with a Google Image search. However, many of these generative tools also support highly iterative processes that allow back and forth, and merging generated images with photos or human created images. I am sure you would agree that a human spending hours of time working on a project, even if AI was involved in the process, still reflects that human's work.
    • Windows 11 version 26H2 is now available for testing in the latest preview build by Taras Buria Friday Windows 11 preview builds are here. Insiders in the Experimental (formerly Dev) and Beta Channel can download builds 26300.8697 and 26220.8690. There are no new features, but Microsoft is officially moving the Experimental Channel to version 26H2. In addition, Microsoft is improving the copy dialog in File Explorer, the Start menu reliability, and fixing virtualization issues. Here is the changelog: [General] With today’s build, Windows Insiders in the Experimental channel will see the versioning updated under Settings > System > About (and winver) to version 26H2. For more information, see the Windows Insiders blog. [File Explorer] We’ve improved the visual consistency and reliability of the Copy dialog in Dark mode, including its launch experience and the expanded progress view. [Start menu] - Also available in Beta Improved reliability of Start menu reflecting newly installed or removed apps without requiring sign-out or restart. [Taskbar] Fixed an issue for Insiders using the new smaller taskbar option, where the system tray might get cut off or pushed off screen. [Settings] - Also available in Beta Improved reliability of Settings > Apps > Startup. [Virtualization] - Also available in Beta This update addresses an issue that could result in bugchecks citing HYPERVISOR_ERROR (0x20001) and KMODE_EXCEPTION_NOT_HANDLED (0x1E) errors after installing the latest flights on some devices during system restarts, virtual machine operations, or while running some gaming applications. You can find the official changelog for the Experimental build here and for the Beta build here.
    • I've always preferred this possibility. There is something that feels good about the idea that all matter in the universe will eventually come back together and maybe even result in another big bang. The idea that the universe would fizzle out over the eons and forever drift apart is a little depressing. I realize it is not logical to let a basic human desire for life to have a grand everlasting meaning change the way I feel about a scientific theory, but I am human, so that is how I feel :-).
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • 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
  • Popular Contributors

    1. 1
      +primortal
      577
    2. 2
      +Edouard
      190
    3. 3
      Michael Scrip
      77
    4. 4
      PsYcHoKiLLa
      76
    5. 5
      Steven P.
      73
  • Tell a friend

    Love Neowin? Tell a friend!