SpaceX
SpaceX’s Starlink satellite lawyers refute latest “flawed” OneWeb critique
After years of relentless legal badgering from internet satellite constellation competitor OneWeb, SpaceX’s regulatory and legal affairs team appears to have begun to (in a professional manner) lose patience with the constant barrage.
On February 21st, SpaceX published a withering refutation of 
SpaceX’s Starlink modification request
In late 2018, SpaceX filed a request with the FCC (Federal Communications Commission) that would allow the company to significantly modify parts of its Starlink satellite constellation license, cutting 16 spacecraft from the original total of 4425 and moving Phase 1’s now-1584 satellites from an operating altitude of ~1100-1300 km (680-810 mi) to just 550 km (340 mi). Aside from further reducing the latency of communications, SpaceX also argues that “the principal reason” behind lowering the operational altitude of the first ~37% of Starlink satellites was “to [further] enhance the already considerable space safety attributes of [the] constellation.”

The safety benefits of a significantly lower orbit come into play when the potential dangers of space debris come into play. Put simply, satellites in lower orbits – particularly orbits below ~1000 km – end up experiencing far more drag from the upper vestiges of the Earth’s atmosphere, drag that acts like an automatic switch in the event that a given LEO satellite loses control. At 500 km and below, even small spacecraft with enough surface area will automatically reenter Earth’s atmosphere within just a few years (~5), while orbits around 1000-1500 km can stretch the time to reentry by a factor of 5-10, often taking decades. In other words, SpaceX’s desire to lower the initial operating orbit of ~1600 Starlink satellites would end up dramatically reducing the consequences the failure of one or several satellites would have on other spacecraft operating in the same orbital regions
“Rather than base its critiques on facts in SpaceX’s application or evidence in the record, OneWeb relies entirely on a collection of flawed assumptions cobbled together into an equally-flawed fictional scenario.
Overall, OneWeb rested its interference analysis entirely on incorrect assumptions and overlooked basic operational distinctions in the actual effect of the proposed SpaceX modification.”
A step further, there is a great deal more irony to be found in
SpaceX never explicitly says as much but it becomes eminently clear that the authors behind this latest response are rapidly losing patience with OneWeb’s years of shoddy attempts at legally suppressing competition. Given that lowering the orbits of almost 40% of SpaceX’s first round of Starlink satellites would end up working in
“OneWeb is now challenging SpaceX’s plan to reduce altitude to further enhance the space safety attributes of its system. Considering OneWeb’s frequent request that SpaceX take this exact step of moving farther away from OneWeb’s proposed constellation, one is left to wonder whether OneWeb would be satisfied with SpaceX operating at any altitude whatsoever.“
SpaceX, 02/21/2019

SpaceX takes a different approach
Aside from seemingly hollow concerns about the “safety” of SpaceX’s request to lower Starlink satellite orbits, OneWeb further criticized SpaceX for what it perceived to be “operational setbacks” after launching a duo of prototype Starlink spacecraft, known as Tintin A and B. In essence, it appears that OneWeb made the bizarre decision to cite officially-unconfirmed and often-disputed reports that SpaceX’s prototypes were unable to reach their originally planned operational orbits of ~1125 km, effectively trapped at the ~515 km orbit they were dropped off in as a result of their shared launch.
“SpaceX originally expected to operate these satellites at approximately 515 km and then raise them to an altitude of 1,125 km for further testing, but chose not to do so. From this, OneWeb leaps to an unsupported conclusion that SpaceX’s experimental satellites faced “operational setbacks.” To the contrary, SpaceX made a conscious decision to remain at this optimal altitude for further experimentation.
Far from facing setbacks, the experimental program has validated SpaceX technology – including the Hall-effect thruster propulsion system and the capabilities of the communications payload. Thus, unlike OneWeb, SpaceX has successfully tested its spacecraft design in advance of initiating deployment of its commercial constellation.”
SpaceX, 02/21/2019
While there was, in fact, some plausible evidence in mid-2018 that at least tentatively suggested that the spacecraft may have had issues with their first-generation ion thruster prototypes, it soon became clear that SpaceX and several major investors were sticking to the narrative that the Tintin twins were operating in fine health in orbit. It’s possible that SpaceX’s legal team and government relations executives are trying to aggressively spin on-orbit difficulties with the prototypes into good news, and the fact that SpaceX is requesting a modification to 550 km instead of Tintin A and B’s ~520 km orbits remains more than a little odd. However, including such brazen and open-faced lies in official legal/regulatory documents would be a deathwish SpaceX’s Starlink license in its entirety, while also begging for major SpaceX-aimed lawsuits and a general black cloud forming over the company.
If the FCC ultimately chooses to permit SpaceX’s Starlink license modification, the company’s first more or less operational Starlink launch – likely carrying anywhere from 10 to 30 satellites – could occur as early as late April or early May.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
SpaceX wants to catch Starship for launch 14, Elon Musk says
Just hours after Starship Flight 13 achieved a successful soft splashdown of its upper stage in the Indian Ocean on July 24, Elon Musk announced an ambitious next step for the company’s next launch of the rocket.
“Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on [the] next flight,” the SpaceX CEO posted on X on Friday.
That “next flight” is expected to be Flight 14. The plan involves returning the Starship upper stage, commonly called the “ship,” to the Starbase launch tower in Texas and catching it mid-air using the same mechanical “chopsticks” arms that have already proven themselves with the Super Heavy booster.
Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on next flight
— Elon Musk (@elonmusk) July 25, 2026
A successful catch would mark the first time an orbital-class upper stage has been recovered this way, advancing SpaceX’s goal of full and rapid reusability for the entire vehicle.
SpaceX has already demonstrated the tower-catch technique multiple times with Super Heavy. The first successful catch came on Flight 5 in October 2024, when Booster 12 was plucked from the sky by the Mechazilla arms. Subsequent flights, including those involving Boosters 14 and 15, repeated the feat. Several of those recovered boosters were later inspected, refurbished, and flown again, proving the system’s viability for quick turnaround.
Traditional reusable rockets, such as SpaceX’s own Falcon 9 or Blue Origin’s New Shepard, land on legs either on land or droneships. Rocket Lab has recovered its small Electron first stages by helicopter, but those are far lighter vehicles.
SpaceX Starship just nailed something it’s never done before
The China Academy of Launch Vehicle Technology (CALT), a subsidiary of the China Aerospace Science and Technology Corp. (CASC), completed a catch of its booster on July 10. They are the only entity besides SpaceX to attempt and complete the feat.
Flight 13 provided encouraging data. The ship executed a controlled reentry, flipped, and soft-landed intact in the ocean after deploying Starlink satellites, offering the first clear post-splashdown views of an undamaged heat shield. The Super Heavy booster, meanwhile, experienced a harder splashdown in the Gulf of Mexico.
Musk has previously stressed that ship catches would only follow multiple successful soft ocean landings to minimize risk of debris over land.
If Flight 14 succeeds, SpaceX would take a major stride toward routine, rapid reuse of both stages—critical for lowering launch costs and supporting ambitious plans for lunar and Mars missions. For now, teams are reviewing the Flight 13 data. Should everything check out, the next Starship flight could deliver one of the most spectacular recoveries in aerospace history.
Elon Musk
SpaceX Starship just nailed something it’s never done before
SpaceX’s Starship flew successfully Friday, landing both stages and deploying its first Starlink V3 satellites.
Starship’s thirteenth test flight delivered exactly what SpaceX needed with a clean liftoff, two successful stage recoveries, and the first real payload the vehicle has ever carried to space. Booster 20 and Ship 40 lifted off at 5:51 p.m. CT from Starbase, and by the time the mission wrapped roughly an hour later, both halves of the rocket had done exactly what they were supposed to do.
Booster 20 separated from Ship 40 a few minutes into the flight and stuck a controlled splashdown in the Gulf of Mexico about six minutes after liftoff. That is a meaningful turnaround from Flight 12 in May, when the booster lost several engines during its boostback burn before a hard water landing attempt.
Starship as seen from Starlink satellites pic.twitter.com/e2hvfmnewh
— Elon Musk (@elonmusk) July 25, 2026
Starship 40’s performance was arguably the bigger win. The vehicle deployed the first 20 operational Starlink V3 satellites Starship has ever carried, then flew a suborbital arc to a landing in the Indian Ocean that SpaceX commentator Dan Huot called the company’s softest splashdown yet. “This is a dream scenario for this team that’s trying to get this heat shield data,” Huot said on the live broadcast, according to Space.com’s live coverage. “I’m a little over the moon right now. Wow. Lucky number 13.”
Unlike the mass simulators SpaceX flew on Flight 12, these were production Starlink V3 satellites, meant to extend solar arrays and antennas and attempt to link with the broader constellation before reentering minutes later. Getting real hardware through a full deploy sequence on only the second flight of the V3 generation keeps Starship on schedule for the payload work NASA is counting on for future Artemis lunar landings.
What an awesome launch, really seems like everything went super well and it was all incredibly smooth.
SpaceX is awesome. Very interested to see how the market will respond on Monday pic.twitter.com/KSHmyBfV55
— TESLARATI (@Teslarati) July 25, 2026
— TESLARATI (@Teslarati) July 25, 2026
The flight also arrives at a moment when SpaceX needed a win. SPCX has traded below its $135 IPO price since mid-July, as Teslarati reported when the mission slipped to Friday, and short interest has climbed to roughly a third of the tradable float. A clean flight will not fix a balance sheet, but it does answer the one question SpaceX absolutely needed answered this week: whether the fixes made after the July 16 abort would hold up under real flight conditions. They did, on both stages, on the first try after the redesign.
SpaceX has not set a target date for Flight 14, though the company has said it wants to push toward an orbital attempt on the next mission. After Friday, that goal looks a lot more within reach.
News
SpaceX Starship Flight 13 faces wrath of the Texas skies
SpaceX pushed Starship Flight 13 to Friday, blaming weather instead of the previous engine issues.
SpaceX called off Thursday’s launch attempt of Starship Flight 13, pushing the mission to Friday because of weather tied to Tropical Storm Bertha. The company confirmed the delay on X, noting “Now targeting Friday, July 24 for Starship’s thirteenth flight test, due to weather. A key objective for the flight test is to get clear imagery from the ground of Starship’s heatshield as it flies at a higher dynamic pressure during ascent, which won’t be possible with today’s weather conditions.”
This is the second delay for Flight 13 in two weeks. SpaceX first tried to launch the mission on July 16, but the countdown ended in an automated abort at T-0 when four of Super Heavy Booster 20’s 33 Raptor engines failed to ignite. Musk said at the time that two Raptors would need to be removed and replaced, as Teslarati reported. The company spent the following week destacking Ship 40 and Booster 20, swapping engines, and running leak checks before restacking the vehicle on Pad 2 Wednesday night, according to Spaceflight Now’s live coverage.
Unlike the engine problem, Thursday’s delay has nothing to do with the hardware. SpaceX wants clean footage of Starship’s heat shield captured from the ground as the vehicle flies through max dynamic pressure, something the storm’s cloud cover over South Texas would not allow. The company said visibility should improve for Friday’s attempt, with the same 90 minute window opening at 5:45 p.m. CT.
Flight 13 will be the second outing for the V3 versions of Starship and Super Heavy, following their debut on Flight 12 in May. The mission carries 20 production Starlink V3 satellites, the first time SpaceX has flown operational satellites rather than mass simulators on Starship. Six of those satellites are fitted with cameras to inspect the heat shield from a different angle during ascent, giving engineers a second data source beyond the ground imagery the weather is currently blocking.
Booster 20 will attempt a boostback burn and a splashdown landing burn in the Gulf of America, while Ship 40 follows a suborbital trajectory toward a landing in the Indian Ocean. The flight plan largely mirrors Flight 12, though the booster will run a more aggressive ascent burn after max Q this time, and the ship’s heat shield includes load sensing tiles meant to measure stress at the higher dynamic pressure SpaceX is targeting.
If Friday’s attempt succeeds, Flight 13 could be the last suborbital test in the program. SpaceX is already looking to push for an orbital flight on Flight 14.



