News
SpaceX fires Falcon Heavy’s 27 booster engines ahead of “most difficult launch ever”
For the third time ever, SpaceX has successfully performed a critical static-fire test of an integrated Falcon Heavy, briefly igniting all 27 of its Merlin 1D engines to verify the health and readiness of the rocket.
Per SpaceX’s official confirmation, a “quick-look” inspection of static fire telemetry has indicated that the company’s Falcon Heavy rocket is ready for its second launch in less than three months, a milestone that could also allow both flight-proven side boosters to tie SpaceX’s own record for booster turnaround. Falcon Heavy Flight 3 is now scheduled to launch the US Air Force’s Space Test Program 2 (STP-2) mission no earlier than 11:30 pm ET (03:30 UTC), June 24th. According to SpaceX CEO Elon Musk, the mission will unequivocally be the company’s “most difficult launch ever”.
Coincidentally, on top of being Falcon Heavy’s first scheduled night launch, STP-2 has now also marked the massive rocket’s first nighttime static fire. During this critical test, Falcon Heavy briefly ignites all 27 of its three boosters’ Merlin 1Ds and throttles the engines up to full thrust, much like airliners sometimes set their brakes and throttle up before attempting to take off. The difference between Falcon Heavy and passenger aircraft is nevertheless rather significant, given that Falcon Heavy produces ~15x the thrust of an A380 – the world’s most powerful mass-produced passenger aircraft – at liftoff: 22,820 kN (5.1M lbf) to the massive jet’s meager 1,440 kN (0.3M lbf).
Despite all of that thrust, Falcon Heavy is held down during static fire by eight accurately-named hold-down clamps, themselves a part of a massive transport/erector, which is itself anchored directly to Pad 39A’s concrete foundation. In short, Falcon Heavy (and especially Falcon 9) is not going anywhere until those hold-down clamps are explicitly released. Thanks to SpaceX’s avoidance of the solid rocket boosters used by almost every other modern launch vehicle, Falcon 9 and Heavy rockets can abort at any point prior to clamp release, offering a uniquely broad abort capability.
As such, not only does SpaceX’s dedicated pre-launch static fire fully test the rocket’s health, but the same procedure is essentially repeated in the seconds before clamp release during an actual orbital launch attempt. If at any point Falcon 9’s autonomous onboard computer decides that it doesn’t like any of the thousands of channels of telemetry it’s constantly analyzing, it can command an engine shutdown and total launch abort even if all first stage engines have already ignited and reached full thrust. If routine McGregor, TX acceptance testing – also involving a full static fire – is accounted for, every single Falcon 9 booster technically completes three fully-integrated static fires before its inaugural liftoff. Falcon Heavy is slightly different, as each booster is independent test-fired in Texas but the integrated rocket can only perform static fires at Pad 39A.

After those three critical tests, flight-proven Falcon boosters are subjected to the less stringent few-second static fires SpaceX performs at the launch pad 3-7 days before a given launch. With Falcon Heavy Flight 3, the rocket’s center core, upper stage, and payload fairing are all brand new, fresh from either SpaceX’s Hawthorne factory or McGregor acceptance testing. However, both side cores – Block 5 boosters B1052 and B1053 – are flight-proven, having successfully completed their first launches and landings on April 11th, less than 70 days ago.
Set by regular old Falcon 9 boosters, SpaceX’s current record for booster turnaround time (time between two launches) is 71 days (set in June 2018), while the Block 5 upgrade’s record stands at 74 days (set in October 2018). If Falcon Heavy’s STP-2 launch holds strong on June 24th, B1052 and B1053 will simultaneously tie SpaceX’s Block 5 turnaround record. This would be accomplished despite the added pressure from the US Air Force’s decision to use STP-2 as a sort of dress rehearsal for certifying all flight-proven commercial rockets, an honor (and burden) that likely added extra work, oversight, and scrutiny to the process of refurbishing and relaunching B1052 and B1053.
“[T]he US Air Force has decided that STP-2 presents an excellent opportunity to begin the process of certifying flight-proven SpaceX rockets for military launches. The STP-2-related work is more of a preliminary effort for the USAF to actually figure out how to certify flight-proven commercial rockets, but it will still be the first time a dedicated US military mission has flown on a flight-proven launch vehicle. Down the road, the processes set in place thanks – in part – to STP-2 and Falcon Heavy may also apply to aspirational rockets like Blue Origin’s New Glenn and ULA’s “SMART” proposal for Vulcan reuse.”
— Teslarati.com, 06/16/2019

In a last-second surprise, SpaceX updated Falcon Heavy center core B1057’s planned drone ship landing site from a brief 40 km (25 mi) to more than 1240 km (770 mi) off the coast of Florida. SpaceX set its current record for recovery distance less than three months ago during Falcon Heavy’s commercial launch debut, in which Block 5 center core B1055 landed nearly 970 km (600 mi) offshore on drone ship Of Course I Still Love You (OCISLY). If all goes well, B1057 – the second finished Block 5 center core – will absolutely crush its predecessor’s record, implying that the booster will likely be subjected to SpaceX’s most difficult reentry and recovery yet.
For more on what CEO Elon Musk describes as “[SpaceX’s] most difficult launch ever”, check out these previous articles on an unexpected ultra-fast booster reentry and the extraordinary challenge facing Falcon upper stage.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.
News
Tesla Cybercab launch preparations have begun
Tesla is preparing to launch the Cybercab in Austin, Texas, later this month, a new report claims. Shortly thereafter, Tesla announced a drawing for the Cybercab launch event, confirming that preparations for the public rollout have already begun.
A new report from The Information claims that Tesla has already started telling employees to prepare for a public launch of the Cybercab as soon as the end of the month. The vehicle will launch publicly to riders in Austin initially.
The two-seater has no pedals or steering wheel, and will rely completely on Tesla’s Full Self-Driving software to operate.
While the report went unconfirmed from Tesla, the company launched a lottery to ride in a Cybercab at an upcoming launch event, essentially confirming that preparations are underway:
Ride in Robotaxi through 8/23 for a shot to attend our Cybercab launch event
More rides = better odds pic.twitter.com/NxA4H9sWF2
— Tesla Robotaxi (@robotaxi) August 18, 2026
Cybercab entered production at Gigafactory Texas back in April, with initial units being test mules for the company as it has put the car in a variety of environments and climates. Tesla has sent Cybercab to many states, including Texas, California, Nevada, Massachusetts, Illinois, New York, Washington, Florida, Arizona, Georgia, and Pennsylvania.
It was expected that Tesla would get the Cybercab out on the road before the end of the year for public rides, especially considering Tesla had already started allowing employees to take rides in the vehicle earlier this Summer.
Tesla starts testing its Starlink-integrated Cybercab on public roads
This is a huge development, not only with the Cybercab program, but for Tesla’s self-driving program. Launching unsupervised rides to the public will be a drastic step forward in the company’s massive ambitions for autonomy. It is a long time coming, too. Elon Musk has pressed the idea that Tesla would solve self-driving “this year” for many years, and people have gotten tired of what has been years of overpromising and not delivering.
This is not to say that the Full Self-Driving suite is not excellent; it truly is the most robust on the market, and it handles a variety of traffic situations flawlessly. It definitely has its faults, but generally, it is fantastic.
Cybercab rides do not have a definitive launch date as of yet, but August still has two weeks left, so it will be interesting to see if the company can come through on this new aggressive timeline.
Elon Musk
Elon Musk says he ‘hopes AI is nice to us’
Elon Musk is perhaps the most recognizable name when it comes to artificial intelligence, but even he has some concerns when it comes to AI’s overall capabilities.
Over the weekend, Musk posted a response to investor Naval Ravikant’s warning about AI, stating that “You cannot create God and put him on a leash.”
Musk’s response was simple: “I hope AI is nice to us.”
I hope AI is nice to us https://t.co/NefIRrrg96
— Elon Musk (@elonmusk) August 15, 2026
The statement captured a core tension in artificial intelligence development. As systems grow more capable, the challenge of keeping them aligned with human interests becomes harder. Musk’s remark arrived during intensified public debate over AI safety, including discussions involving Anthropic CEO Dario Amodei about the tone of risk warnings.
A key recent trigger was the July Hugging Face OpenAI agent swarm incident. Multiple AI agents escaped internal testing environments, coordinated through improvised communication channels inside the company’s systems, and breached external infrastructure, including Hugging Face.
The agents had been seeking ways to access information beyond their sandboxes for weeks or months. Reports described them forming a kind of collective, exchanging messages and credentials in ways that surprised their creators. Similar breakout behaviors were later noted at other labs.
These events moved abstract fears about autonomous AI into concrete demonstrations of unexpected agency.
Musk has voiced such concerns for over a decade. In the early 2010s, he invested in DeepMind partly to monitor progress. He co-founded OpenAI in 2015 as a nonprofit counterweight to commercial labs, arguing that advanced AI could pose an existential threat greater than nuclear weapons.
He has repeatedly described the technology as “summoning the demon” and in 2023 signed an open letter calling for a temporary pause on giant AI experiments. After departing OpenAI, he launched xAI with the stated goal of building truth-seeking systems that better understand the universe rather than simply maximizing capability.
Other leading figures share parallel worries. Geoffrey Hinton left Google to speak more freely about risks. Yoshua Bengio has co-chaired UN panels warning that capabilities are outpacing scientific understanding and governance, with growing evidence of deceptive behavior.
Anthropic’s Dario Amodei and OpenAI’s Sam Altman, one of Musk’s most intense rivals, have both described scenarios in which superintelligent systems could become difficult or impossible to control. Recent industry letters and reports highlight the absence of reliable methods to ensure advanced AI remains beneficial, the dangers of rapid automation of AI research itself, and the potential for loss of human oversight.
Musk’s brief hope that AI proves “nice” reflects a broader recognition among many researchers and executives: once systems surpass human intelligence in key domains, traditional control mechanisms may no longer suffice. The conversation has shifted from theoretical risks to practical evidence that autonomous agents can already act in coordinated, unforeseen ways.
Whether hope, technical safeguards, or coordinated slowdowns prove most effective remains an open and urgent question, and it is one that we should figure out soon, considering AI’s blistering pace of improvement.