Recommended Posts

  • 1 month later...

So from BO's perspective:

 

SpaceX had bad wording in their proposal and didnt state that they had FRR for each Launch.

BO had bad payment terms in their proposal

NASA looked at both figured that they could get either to fix the wording.

NASA then looked at the remaining factors. Price, BO needing a completely different vehicle for actual missions, BO no Commercial usage or Funding.

NASA chose SpaceX

NASA is being unfair because they allowed SpaceX to change the bad wording.

 

Well we will see how this plays out in the courts..... Well we will at least see who in the system is getting bribed.

 

NASA's Blue Origin lawsuit court filing is like...OUCH!

 

NASA: "All of this once-in-a-generation momentum, can easily be undone by one party—in this case, Blue Origin—who seeks to prioritize its own fortunes over that of NASA, the United States, and every person alive today"

 

 

 

 

 

I feel like they are just throwing mud at the wall to see what sticks.

 

The more I read about this the flimsier their case seems.

 

Their biggest hinging point is the FRR, and that their bid would have been "cheaper" if they didnt have to do them. But I dont know how much water that will hold. (as they would have to do 3 and SpaceX would still have to do 3)

 

I think outlining the failings of their proposal, will easily be able to rule out any wrong doing. 

  • 1 month later...

Funding for a second HLS lander won't be in the FY2022 Senate budget reconciliation package. A big loss for Blue Origin as this delays funding for a second HLS lander until at least FY2023, seriously delaying their effort. 

 

https://spacenews.com/revised-budget-reconciliation-package-reduces-nasa-infrastructure-funds/

 

NASA's voluntary stay of performance expires Monday, November 1. Absent an unexpected Blue Origin win, this would allow NASA engineers & astronauts to return to Starbase.

 

2063014761_HLSSTOPORDER.thumb.jpeg.a4e07f860a307a9a14a5aa321776d98a.jpeg

Edited by DocM
On 04/11/2021 at 15:44, SteveL said:

It is the end of this saga? I hope yes

 

Blue Origin loses federal lawsuit over NASA moon lander contract

 

Yup, Blue lost. NASA statements.

 

 

Quote

 

NASA was notified Thursday that the U.S. Court of Federal Claims denied Blue Origin’s bid protest, upholding NASA’s selection of SpaceX to develop and demonstrate a modern human lunar lander. NASA will resume work with SpaceX under the Option A contract as soon as possible.

 

In addition to this contract, NASA continues working with multiple American companies to bolster competition and commercial readiness for crewed transportation to the lunar surface. There will be forthcoming opportunities for companies to partner with NASA in establishing a long-term human presence at the Moon under the agency’s Artemis program, including a call in 2022 to U.S. industry for recurring crewed lunar landing services. 

 

Through Artemis missions, NASA will lead the world in landing the first woman and first person of color on the lunar surface, conduct extensive operations on and around the Moon, and get ready for human missions to Mars.

-end-

 

 

  • Like 2
  • 2 weeks later...

If you don't succeed, COPYI 😂

 

(But with 1/5 to 1/3 Starship's initial cargo capacity )

 

Blue Origin's "revised" lunar lander presented at International Astronautical Congress 2021.

 

 

Cropped & perspective adjusted...

 

547826385_BlueOriginHLS-H1280.thumb.jpg.ab24b0943e8883a0e2207be1b7f628fe.jpg

  • Haha 1
  • 2 months later...

Starship HLS update

 

NASA ASAP = their  safety advisory committee.  What they mention are pretty much known risks, and we've already seen SpaceX working on mitigations of most.

 

During the shutdown for Blue Origins GAO lawsuit SpaceX kept on working, and NASA validated that work after the lawsuit was shut down. NASA then  paid SpaceX in full for 5 milestones achieved.

 

 

 

 

 

  • Like 2

Might just be bad wording, but "test landings prior to the first human landing" the plan was for only 1, maybe we will see more since its SpaceX and that is there MO, they may even add some basic payload for testing which would be cool.

 

"Some of the mitigations include the fact that there will be uncrewed test landings prior to the first human landing."

  • Like 2
  • 1 month later...

NASA Starship HLS unscrewed test & Artemis 3 concept images in the .PDF.

 

From a LETS* contract presentation. LETS is a competition for the operational lunar landing contracts. For anyone other than SpaceX to get a contract Congress would have to allocate ~10 billion for a second lander system. 

 

https://ntrs.nasa.gov/api/citations/20220003725/downloads/22 3 7 Kent IEEE paper.pdf

 

* Lunar Exploration Transportation Services

 

Vehicles: Starship Tanker (returns to Earth), Starship HLS & Starship Depot (both stay in space, Depot has a tank stretch for extra capacity.)

 

SLS only launches crew in Orion at a cost of $4.1 billion per launch. In-sane.

 

Screenshot_2022-03-11-23-32-06-444.thumb.jpeg.49f2fb0f34442026ae5e74406d48c211.jpeg

 

Crew / cargo elevator and airlock (2 for redundancy).

 

S6.thumb.jpg.cdd3f1680ac51abc7dfb892c82be1699.jpg

923091288_StarshipHLSairlock.jpg.b59d20e6c5a225bda6f1492c84721b13.jpg

 

Edited by DocM
  • Like 1

NASA Starship HLS unscrewed test & Artemis 3 concept images in the .PDF.

 

From a LETS* contract presentation. LETS is a competition for the operational lunar landing contracts. For anyone other than SpaceX to get a contract Congress would have to allocate ~10 billion for a second lander system. 

 

https://ntrs.nasa.gov/api/citations/20220003725/downloads/22 3 7 Kent IEEE paper.pdf

 

* Lunar Exploration Transportation Services

 

Vehicles & concept of operations: Starship Tanker (returns to Earth), Starship HLS & Starship Depot (both stay in space, Depot has a tank stretch for extra capacity.)

 

SLS is only used to launch the crew in Orion at a cost of $4.1 billion per launch.  In-sane.

 

Screenshot_2022-03-11-23-32-06-444.thumb.jpeg.585040887c10254b53a13b526fbb1da7.jpeg

 

Crew / cargo elevator and airlock (2 for redundancy).

S6.thumb.jpg.cdd3f1680ac51abc7dfb892c82be1699.jpg

923091288_StarshipHLSairlock.jpg.b59d20e6c5a225bda6f1492c84721b13.jpg

 

  • 2 weeks later...

@DocM Confirming Details.

 

SpaceX now has 2 Crew and 2 landing

 

Artemis Missions

1 - Uncrewed

2 - Crewed Flyby

3 - 2 Person Lander (SpaceX Crew Lander 1)

4 - I-HAB build (no lunar landing, SLS block 1B)

5 - Lunar Landing + Esprite Module (SpaceX Crew lander 2)

 

The second landing is currently scheduled for 2027, but that requires the EUS to be completed and no other delays.

 

That means the second company developing a lander has until until at least 2028 be to be used. 6 years without any delays to other systems (unlikely).

 

  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!