United Launch Alliance may seek certification from the Space Force after one flight.
See full article...
See full article...
But what happens if the payload is not ready for Cert-2, as increasingly looks likely to be the case?
Project Kuiper recently launched two prototype satellites, and tests from the mission have helped validate our satellite design and network architecture. We are preparing to start satellite manufacturing ahead of a full-scale deployment beginning in the first half of 2024, and we expect to have enough satellites deployed to begin early customer pilots in the second half of 2024.
Simply my opinion, but I think that dummy payload is an "easier" decision for a private company, a company looking to get in on the gov contract and/or a company in the middle of innovate approaches to space.I believe SpaceX would just launch a dummy payload and get it over with.
On NASA's internal schedule for missions to the International Space Station, the Dream Chaser mission to supply cargo to the orbiting laboratory currently has a "planning" date of September. However, this is not a firm date and is subject to slippage.
In fact, there is skepticism within the space agency about a fall launch. According to one source, during a recent meeting to integrate planning for space station activities, there were significant inconsistencies in the schedule that Sierra Space officials laid out for NASA.
100 million of pure cost is not a small amount, not even for a rocket company.Simply my opinion, but I think that dummy payload is an "easier" decision for a private company, a company looking to get in on the gov contract and/or a company in the middle of innovate approaches to space.
They would be more willing to bite the bullet, if you will, and do the dummy payload, take the potential profit lose to show that they are ready.
One the other hand, you have some companies that are so used to public/government dollars - they are loathe to spend a single dime of their own money.
A dummy payload on a ULA rocket is a lost profit opportunity. A month's long delay must be better than the dummy payload option according to their accounting team.
Or so it would seem to me..
I don't know if I agree with your assessment on ULA screwing over Kuiper. The Centaur explosion certainly delayed Vulcan, but the lack of BE-4 engine availability from BO had already resulted in years of delays to Vulcan and its missions. And apparently BO still doesn't have engine production where it needs to be. As for Kuiper ... I don't even know if they have satellites to launch yet. If they do, I wonder why they aren't loading up an Atlas or Vulcan already? And if they don't have satellites ready, then I'd argue that Centaur's explosion really didn't impact their ability to start launching the constellation.If I had to guess what to do in that situation, I would go bang on Kuiper door and ask if they have something, anything to launch. ULA already screwed them over with Vulcan, they can be nice now and do a free lift of 2, 5 or 10 Kuiper sats to test.
EDIT:
This is from December 1st 2023. If they are planning to begin deployment in H1 2024, they probably can be convinced to launch something on July 2024 on Vulcan.
If that 14-flight option means no paperwork, I'd go for that. Damn the expense!There is also a six-flight option and even a 14-flight option for certification. The latter option essentially means that if your rocket flies 14 times, it earns certification.
For certain companies, any amount of paperwork is easier than finding customers for 14 launches without relying on defense contracts.If that 14-flight option means no paperwork, I'd go for that. Damn the expense!
Yeah this was my thought as well. There is massive demand from constellations just go that routeIf I had to guess what to do in that situation, I would go bang on Kuiper door and ask if they have something, anything to launch. ULA already screwed them over with Vulcan, they can be nice now and do a free lift of 2, 5 or 10 Kuiper sats to test.
EDIT:
This is from December 1st 2023. If they are planning to begin deployment in H1 2024, they probably can be convinced to launch something on July 2024 on Vulcan.
Until they are not certified and miss out on some government launches because they don’t get another launch soon enough. They could end up in the same place as Boeing with SpaceX as DOD re-arranges the launch split to favor the company that is actually certified to launch.A dummy payload on a ULA rocket is a lost profit opportunity. A month's long delay must be better than the dummy payload option according to their accounting team.
Or so it would seem to me..
It will soon turn into "May we please have more engines, pretty please, if you don't mind, dear wonderful boss?"I'll be honest, I thought "where are my engines, Jeff" was dead by now.
So far the BE-4 engines used for the qualification trials and as the flight engines on CERT-1 have been largely hand built. Blue Origin has not yet demonstrated the ability to mass produce BE-4s in a manner similar to how SpaceX produces Merlins and Raptors.I am also a bit surprised that ULA is still waiting on engines from Blue Origin, I had seen people post convincing arguments that that problem was solved. I am also surprised ULA didn't have a backup payload, since I thought they said they did.
Another argument for ULA to buy BO, since I don't think there are antitrust concerns any more for a rocket maker owning the capability to build their own rocket engines, unlike aircraft makers back in the day. . .
I don't know if I agree with your assessment on ULA screwing over Kuiper. The Centaur explosion certainly delayed Vulcan, but the lack of BE-4 engine availability from BO had already resulted in years of delays to Vulcan and its missions. And apparently BO still doesn't have engine production where it needs to be. As for Kuiper ... I don't even know if they have satellites to launch yet. If they do, I wonder why they aren't loading up an Atlas or Vulcan already? And if they don't have satellites ready, then I'd argue that Centaur's explosion really didn't impact their ability to start launching the constellation.
My point isn't that OB and Amazon are the same, just that BO is the one responsible for the bulk of the delay. In fact, IIRC the new Centaur upper stage wouldn't have been a gating factor if the BE-4s were delivered earlier, and if those two weren't flown with Astrobotic, that's Astrobotic's fault.The delay from Vulcan made Kupier waste one of the Atlas flights that they had hired to launch just 2 Kuiper sats that were going to be launched with Astrobotic.
Yeah, forced to waste a full Atlas launch on 2 test sats is kind of screwed.
BO is a separated company from Amazon. So any problems caused by BO shouldn't be paid by Kuiper.
A little while ago when there was a flurry of New Glenn publicity, one of the points that was loudly repeated was that the 7 BE-4s for NG were stated to be in either in testing or delivered, and those commenters took that as proof that BE-4 production was a solved problem, and would no longer cause delays. Of course, Vulcan and NG use different variants of the BE-4, and we still have seen no evidence of either being produced at scale.I am also a bit surprised that ULA is still waiting on engines from Blue Origin, I had seen people post convincing arguments that that problem was solved. I am also surprised ULA didn't have a backup payload, since I thought they said they did.
Another argument for ULA to buy BO, since I don't think there are antitrust concerns any more for a rocket maker owning the capability to build their own rocket engines, unlike aircraft makers back in the day. . .
Vulcan's flight manifest is almost solely DoD missions and Kuiper missions. They can't launch DoD missions until they get certified, and they need to successfully fly 1 more time to do this.I don't understand the problem.
Wasn't Vulcan having a large manifest of flights already?
Why wait for Dream Chaser if they can launch other commercial customers in the meantime?
Like Kuiper satellites, for example?
Vulcan is firmly in the medium lift range until you put 4 or 6 solids on it. The VC2 that launched the Astrobotic lander could put 16 t to ISS, which is the same as F9 with a recovered booster.How many heavy lift launches per year can the market actually sustain right now? The Falcon Heavy barely flies as it is, and Starship will probably spend most of its time on Starlink satellites. Sure you have space stations and big telescopes, but they only come around so often.
This explains quite a bit for me. All indications that I've heard have been that Dream Chaser is moving into the last phase of testing (thermal vacuum testing), which should mean we would be hearing noise about launch preparations... and the fact that we haven't heard anything of the sort was raising some flags.
I don't think that'd help with this launch, though. Even if they'd included a SMART reuse demo into Cert-1 (the Peregrine launch), the recovered engines would probably have been torn apart and every little piece examined, rather than being in any condition to be reused for Cert-2.Imagine if they weren't dumping the first state and the BE-4 engines into the ocean on each flight. There are many ways to solve supply chain bottlenecks...
14 flights requires 28x BE-4 engines. With that sort of time scale, Kuiper payloads become an option but I am not convinced the military will wait that long.If that 14-flight option means no paperwork, I'd go for that. Damn the expense!
There is always paperwork....If that 14-flight option means no paperwork, I'd go for that. Damn the expense!
Remember previous Ars reporting of when Blue had brought in consultants to examine the company processes and found that there were major issues in accounting for costs and complexity of manufacturing process, with design decisions being made with no consideration of how difficult it would make it to produce.So far the BE-4 engines used for the qualification trials and as the flight engines on CERT-1 have been largely hand built. Blue Origin has not yet demonstrated the ability to mass produce BE-4s in a manner similar to how SpaceX produces Merlins and Raptors.
That being said, I am surprised they are already having issues. I had expected BO would be able to deliver the engines for CERT-2. I did not expect the bottleneck to show itself this early. I thought the problem would be further down the road, when ULA starts launching Kuiper satellites and tried to ramp up their launch cadence. Another potential long term issue will be when BO starts testing New Glenn and needs additional BE-4s for that.
Simply my opinion, but I think that dummy payload is an "easier" decision for a private company, a company looking to get in on the gov contract and/or a company in the middle of innovate approaches to space.
They would be more willing to bite the bullet, if you will, and do the dummy payload, take the potential profit lose to show that they are ready.
One the other hand, you have some companies that are so used to public/government dollars - they are loathe to spend a single dime of their own money.
A dummy payload on a ULA rocket is a lost profit opportunity. A month's long delay must be better than the dummy payload option according to their accounting team.
Or so it would seem to me..