SpaceX launches 21 Starlink satellites but loses first stage at landing

SpaceX last night successfully placed 21 Starlink satellites into orbit, its Falcon 9 rocket lifting off from Cape Canaveral in the early morning hours.

The first stage however fell over on its drone ship in the Atlantic after landing. This was its 23rd flight, which would have been a record reuse of a Falcon 9 booster had it landed successfully. Because of this failure, SpaceX rescheduled another Starlink launch, delaying it one day until August 30, 2024, as engineers assessed the stage data to determine the cause of the problem. From the video is appears that one leg on the far side, out of sight, either failed to deploy or collapsed after landing.

To be clear, SpaceX anticipates only a one day delay in all its launches because of this issue.

The leaders in the 2024 launch race:

84 SpaceX
35 China
10 Rocket Lab
9 Russia

American private enterprise now leads the rest of the world combined in successful launches 99 to 53, while SpaceX by itself leads the entire world, including American companies 84 to 68.

11 comments

Manned Polaris Dawn launch delayed due to weather

SpaceX tonight scrubbed the launch of Jared Isaacman’s manned Polaris Dawn orbital mission due to poor weather predicted in the splashdown zones off the coast of Florida when the mission would have ended.

The flight has tentatively set now for August 30, 2024, but that remains a very preliminary date.

SpaceX however is not sitting on its hands while it waits for good weather for this manned mission. Tonight it has two Starlink launches scheduled a little more than an hour apart, one from Cape Canaveral in Florida followed by the second from Vandenberg in California. If the first launch is successful its Falcon 9 first stage will set a new record, flying for its 23rd time.

0 comments

D-Orbit newest orbital tug deploys four smallsats

The Italian orbital tug company D-Orbit has now successfully deployed four smallsats from its newest tug, having been launched on August 16, 2024 on a SpaceX Falcon 9 rocket.

The tug still has one more satellite to deploy, after which it will remain in orbit as it also carries four additional customer “hosted” payloads that are using the tug itself as their service module.

This is D-Orbit’s second demo mission, the first flying in 2023. It also appears be completely successful, which puts this company in an excellent position to garner future contracts from many small satellite companies. It is also a partner in a $256 million Italian project to test in-orbit robotic satellite repair.

0 comments

ABL completes investigation into launchpad fire in July

The rocket startup ABL yesterday released the results of its investigation into launchpad fire in July that destroyed its RS1 rocket during a static fire test prior to an orbital test launch.

In a statement, ABL Space Systems said it ignited the E2 engines in the first stage of the RS1 rocket in the test, but aborted the test after just half a second because of a low pressure reading in one engine that the company said was caused by a faulty pressure sensor. The engines shut down, but a fire then broke out under the base of the vehicle, fed by fuel leaks from two engines. That fire was contained but could not be extinguished by either water or inert gas systems, and the company started offloading kerosene and liquid oxygen propellants from the vehicle.

The launch pad the company uses at Kodiak does not have its own water supply, with the company instead using mobile tanks that ran out of water 11 and a half minutes after ignition. That caused the fire to spread “and a progressive loss of pad systems,” the company stated, including the inability to continue detanking the rocket and eventually telemetry from the rocket.

ABL’s first launch attempt of this rocket in January 2023 failed when the first stages shut down immediately after lift-off and the rocket crashed on the launchpad. It completed its investigation of that failure in October 2023 and was ready for its second launch attempt this summer when the fire described above occurred.

The company has raised several hundred million dollars, with its chief investor being Lockheed Martin, which has also signed a contract for as many as 58 RS1 launches. It increasingly appears those launches might very well go to other providers.

0 comments

Firefly delivers its first Blue Ghost lunar lander for final environmental testing

Blue Ghost in clean room
Blue Ghost in clean room

Firefly this week completed the integration of the ten customer payloads onto its first Blue Ghost lunar lander and shipped the lander to JPL in California for final environmental testing before its planned launch before the end of this year.

Following final testing, Firefly’s Blue Ghost will ship to Cape Canaveral, Florida, ahead of its launch on a SpaceX Falcon 9 rocket scheduled for Q4 2024. Blue Ghost will then begin its transit to the Moon, including approximately a month in Earth orbit and two weeks in lunar orbit. This approach provides ample time to conduct robust health checks on each subsystem and begin payload operations during transit.

Blue Ghost will then land in Mare Crisium, a basin in the northeast quadrant on the Moon’s near side, before deploying and operating 10 instruments for a lunar day (14 Earth days) and more than 5 hours into the lunar night.

Once launched, Firefly will become the third American company, after Astrobotic and Intuitive Machines, to build a privately owned lunar lander and attempt a lunar landing. Since the other two companies were not entirely successful in their landing attempts, Firefly has the chance to be the first to succeed.

0 comments

SpaceX blasts its satellite competitors for lobbying the government to shut down Starlink/T-Mobile partnership

SpaceX on August 22, 2024 responded harshly to the effort by its satellite competitors to get the FCC to shut down the planned partneship of Starlink and T-Mobile, whereby Starlink will fill the gaps in T-Mobile’s coverage.

You can read SpaceX’s letter here. Its language however is quite blunt:

While the petitions from AT&T, Verizon, DISH/EchoStar, and Omnispace lack technical basis or legal merit, their game is clear. AT&T and Verizon seek to hamstring their competitor T-Mobile by talking out of both sides of their mouths, on one hand demanding without technical support that T-Mobile and SpaceX operate at unnecessarily low power levels that will force Americans to sacrifice service, while giving their own partner AST a free pass. AT&T goes so far as to claim to have conducted a secret study it refuses to show the Commission to support suppressing SpaceX’s out-of-band emissions to an interference-protection level ten times below the limit sufficient to protect terrestrial networks, while allowing its partner AST to exceed that limit.

DISH/EchoStar repeats its demand to siphon proprietary information from SpaceX to aid its own flailing ambitions, while stoutly refusing SpaceX’s repeated requests to engage in actual good faith coordination the way a company with actual technical concerns would.

And although it still has no commercial satellite service anywhere in the world, Omnispace continues to make unfounded claims of prospective harmful interference to prop up a decade-old spectrum play that it fears will lose financial value if American consumers can enjoy ubiquitous mobile connectivity using the PCS G Block downlink.

Fortunately, none of these unfounded arguments present any reasonable basis to delay swift grant of SpaceX’s request to bring ubiquitous mobile connectivity to American consumers.

The FCC has not yet responded to any of these demand letters. Nor has it yet issued the waiver SpaceX had requested in June 2024 allowing its Starlink system to operate beyond its licensed radio frequencies in order to facilitate cell surface with T-Mobile.

2 comments

Rocket Factory Augsburg releases footage of 1st stage failure during static fire test

The German rocket startup Rocket Factory Augsburg today released the film footage it took during the failed 9-engine static fire test of its 1st stage last week.

I have embedded that footage below.

As the company’s CEO noted two days ago, the company has identified the cause as a fire in an oxygen pump which they think was unrelated to the engine design. This explanation remains puzzling, however. If the problem was not engine design, it suggests instead some other quality control error, which it is even more important to identify in order to prevent such errors in the future.

The video provides numerous angles of the failure, including one that captured the moment when the first stage fell over. As the CEO noted, it fortunately fell in the right direction, missing critical launchpad equipment and thus reducing significantly the damage to the pad.
» Read more

2 comments

Starliner will return unmanned; crew will return in February 2025 on Dragon

Starliner docked to ISS
Starliner docked to ISS.

In a briefing today, NASA’s administrator Bill Nelson announced that Boeing’s Starliner capsule, launched in June on its first manned mission, will return unmanned and that the two astronauts it brought to ISS — Butch Wilmore and Suni Williams — will return in February 2025 as part of the crew of the next Dragon manned mission, scheduled to launch in late September.

Nelson made it a point to note that NASA’s past inactions to protect astronauts on two different shuttle missions, thus leading to their deaths, was a factor in this decision. The agency now decided safety must come first, and since Starliner’s return abilities still carry uncertainties that relate directly to safety, it decided to use a more reliable and tested Dragon capsule to return those astronauts back to Earth. During the entire briefing and Q&A session it became very clear that NASA is now paying very close attention to its engineers and their conclusions, rather than dismissing those conclusions because of other management concerns, as it did during those previous two shuttle failures.

Nelson also stated that NASA still wants to use Starliner as a second crew vehicle to ISS. He noted that he has spoken to Boeing’s new CEO, who apparently committed to getting Starliner fixed and operating. It remains undecided whether another test manned flight will be required of Boeing (at Boeing’s cost) before NASA certifies it as an operational vehicle. Whether any other customers will be willing to use the capsule remains unlikely until Boeing has flown a lot of Starliner NASA flights with no problems.

At this moment they are looking to bring Starliner back in early September, using a simplified undocking system to get the vehicle away from ISS quickly. The next Dragon mission will launch no earlier than September 24th carrying two astronauts and two empty flight suits that Wilmore and Williams use during their return.

34 comments

NASA adds three orbital tug startups to its contract bid list

NASA yesterday added three orbital tug startups to its contract bid list, allowing these companies to bid on projects that require the deployment of NASA smallsats to different orbits after launch.

NASA announced Aug. 22 that it selected Arrow Science and Technology, Impulse Space and Momentus Space for its Venture-Class Acquisition of Dedicated and Rideshare (VADR) contract. That selection allows them to compete for task orders for launching specific missions, typically small satellites willing to accept higher levels of risk in exchange for lower launch costs.

Arrow provides small satellite companies the deployment equipment used to release the satellite after launch. Impulse and Momentus have orbital tugs that not only deploy smallsats, but move them to their preferred orbit after the tug’s release from its launch rocket.

This NASA announcement allows its smallsats to be launched on either a dedicated small rocket that puts the satellite in its desired orbit or as part of a larger rideshare launch with many satellites that then uses the tug to get the satellite where it needs to be.

0 comments

Amazon commits almost $20 million more to expanding its satellite production facility

Amazon yesterday revealed it is going to spend an addition $19.5 million to expand its satellite production facility at the Kennedy Space Center in Florida in order to overcome the long multi-year delay in getting production started.

The company said Aug. 22 the investment will support a secondary, 3,900-square-meter support facility at the site, which would help accelerate launch cadence amid a looming regulatory deadline to deploy half the constellation by July 2026. The building would join a 9,300-square-meter satellite processing facility Amazon announced last year at Kennedy’s runway-equipped Launch and Landing Facility, bringing total investment in the site to nearly $140 million.

The company hopes to open this additional facility by next year. It will need it, because its FCC license for its Kuiper internet constellation — conceived to be similar to SpaceX’s Starlink — requires it to launch half of the constellation of 3,200+ satellites by 2026 and have the entire constellation in orbit by 2029. Meeting that first deadline will be challenging at this point, though the company hopes to be launching frequently in the next few years. It has contracts to launch satellites 46 times on ULA rockets (8 on Atlas-5 and 36 on Vulcan), 27 times on Blue Origin’s New Glenn, 18 times on ArianeGroup’s Ariane-6, and 3 times on SpaceX’s Falcon-9. To provide payloads for those launches however it will need to be able to quickly build a lot of satellites, and that’s what this additional investment is for.

It must be noted again that the Kuiper constellation was first proposed by Amazon at almost the exact same time as Elon Musk proposed his Starlink constellation. SpaceX now has several thousand satellites in orbit and is earning several billion dollars per year from several million signed up customers. Amazon in comparison has only launched two test satellites and zero operational satellites in that same time frame.

2 comments

Norway approves spaceport license for Andoya

Proposed spaceports surrounding Norwegian Sea
Proposed spaceports surrounding Norwegian Sea

The Norwegian government announced yesterday that the Andoya spaceport that has been used for decades for suborbital test launches, has been given a spaceport license to conduct orbital launches from the site.

According to a statement from the Norwegian ministry, the license allows the spaceport to conduct up to 30 launches a year, including four during overnight hours. Those launches, to be overseen by the Civil Aviation Authority of Norway, can take place on azimuths between 280 and 360 degrees, supporting missions primarily to polar and sun-synchronous orbits.

The German rocket startup Isar Aerospace already has a 20-year lease to conduct orbital launches from Andoya, and hopes to do the first orbital test launch of its Spectrum rocket there. According to the Norway government, the first launch is planned for this year, but that likely will only be a suborbital test, not a full orbital launch. Of the three rocket startups from Germany, Isar is the only one that has not yet done any engine tests (as far as we know) or suborbital test launches of its rocket engine or design. Hyimpulse has done a suborbital test launch from an Australian spaceport, and Rocket Factory Augsburg have done numerous tests both in Germany and at the Saxaford spaceport. This license to Andoya will likely signal the start of those public tests by Isar.

A fourth European rocket startup, PLD from Spain, is presently prepping its own launchpad in French Guiana, and hopes to conduct its own first orbital test launch next year.

Until this week it appeared that Rocket Factory was in the lead to be the first European rocket startup to attempt an orbital launch. That changed when the rocket’s first stage was destroyed during a static fire launchpad engine test earlier this week. Right now it is not clear who is in the lead.

2 comments

Rocket Factory identifies cause of failure during rocket static fire test

According to Rocket Factory Augsburg, its investigation into the explosion during the first full nine-engine static fire test of its RFA-1 rocket earlier this week has identified the cause of the failure.

In an update on LinkedIn on 22 August, RFA COO Dr. Stefan Brieschenk announced that the company had completed an initial internal review. In what Dr. Brieschenk describes as “very preliminary” findings, he explains that the company has identified an “oxygen fire in one of the turbopumps” as the root cause of the incident. “That engine and that turbopump have run before without issues, wrote Dr. Brieschenk. “Eight engines ignited. We had multiple back-up and safety systems in place that were supposed to shut everything down – but things did not align on Monday as planned.”

As he notes, this is very preliminary. The company probably still does not know why the fire occurred in that turbopump, and it will need to find out in order to fix the problem. And without that fix, it is almost certain the UK’s Civil Aviation Authority (CAA) will not issue the company a launch license when a new first stage is built and delivered to the Saxavord spaceport in the Shetland Islands where the launch is planned.

All in all, expect a delay of at least one year before that launch can occur. Base on the CAA’s past history, that delay could easily extend to two years.

0 comments
1 135 136 137 138 139 784