News
SpaceX shifts Falcon 9 booster from landing pad to drone ship after anomaly
SpaceX officially confirmed that it will move the location of a Falcon 9 booster’s post-launch recovery in order to better preserve the site of Crew Dragon’s catastrophic April 20th failure.
Instead of returning the booster to one of SpaceX’s two Cape Canaveral Landing Zones (LZs), SpaceX has applied for an FCC permit to land the rocket less than 20 miles (~30 km) off the coast of Florida on the drone ship Of Course I Still Love You (OCISLY). The culprit for the last-second change of plans is a catastrophic failure of Crew Dragon that spread debris throughout SpaceX’s Landing Zone facilities, debris that will now be critical for the process of anomaly resolution. Landing a Falcon 9 booster at LZ-1 or 2 would invariably spread Crew Dragon’s debris and complicate the failure investigation even further.
Much like a tornado passing through a crime scene would likely hamper the value of that crime scene and any related investigations, a Falcon 9 booster landing at the scene of a fresh accident investigation would be an extremely unwelcome complication. Even with just one Merlin 1D engine firing during a Falcon 9’s landing burn, the engine exhaust departs the nozzle traveling approximately 2.7 km/s (1.7 mi/s) and could easily send Crew Dragon remnants hundreds or even thousands of feet away and incinerate smaller debris. Given that Crew Dragon’s explosion appears to have been highly energetic, many, many pieces will already be spread many hundreds – and perhaps thousands – of feet around the incident.
Crew Dragon is an extremely complex spacecraft. Even the tiniest of fragments could potentially be critical to the successful completion of the explosion investigation, especially if the fault began somewhere in capsule C201’s many hundreds of feet of plumbing. The pipes, valves, and pumps that make up Crew Dragon’s propellant management system have many hundreds (if not thousands) of small parts that must work without issue to safely pressurize and handle the spacecraft’s hypergolic propellant.


Cargo Dragon set for launch
Despite Crew Dragon’s serious failure and the need to change Falcon 9’s booster recovery plans at the last moment, SpaceX still appears to be working to maintain the planned launch date. The instantaneous window is set for 4:22 am ET (08:22 UTC), April 30th, delayed five days from the original April 25th target. Based on an update provided by NASA last week, those delays are the result of International Space Station (ISS) scheduling and additional time needed for payload preparations. Orbital-ATK’s (now “Northrop Grumman Innovation Systems” or NGIS) uncrewed Cygnus spacecraft successfully berthed with the ISS on April 19th, followed by the station’s astronauts unloading the three metric tons of cargo it contained over the next several days.
Once Cygnus operations have been completed, the ISS astronauts will be able to start preparing for Cargo Dragon’s CRS-17 resupply mission, likely carrying another three or four metric tons of pressurized cargo. Although the logistics of unloading, unpacking, and stowing the contents of hundreds of packages of consumables, hardware, tools, science experiments, and more is not exactly thrilling, the reality is that the task takes a surprising amount of time and care. Of the maximum six astronauts aboard the ISS at any given moment, only a few of them are able to focus exclusively on the cargo logistics at the same time as time-sensitive science experiments must be immediately set up to avoid ruining the data produced. Furthermore, although the ISS is truly massive, there are only a handful of berthing and docking ports and the actual habitable volume can be cramped, as are the ports between the station and visiting spacecraft.
An unknown Falcon 9 booster – perhaps B1056 – will perform a routine static fire test at SpaceX Launch Complex 40 (LC-40) five or so days before launch, likely within the next 48 hours. Soon after, Falcon 9 will be mated with CRS-17’s flight-proven Cargo Dragon capsule and expendable trunk before rolling back out to LC-40. If the FCC works fast and grants SpaceX’s updated booster recovery license in the next few days, CRS-17 should remain on track for an April 30th launch.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
SpaceX Starship Flight 13 aborted at Zero and Musk just told us what broke
Four Raptor engines failed to ignite at T-zero, forcing SpaceX to scrub Starship Flight 13 Thursday.
SpaceX scrubbed the Starship Flight 13 launch attempt Thursday evening at the last possible moment, after four of the Super Heavy booster’s 33 Raptor 3 engines failed to ignite during the startup sequence. The 90-minute window had opened at 6:45 p.m. EDT from Starbase in Boca Chica, Texas, and the countdown had proceeded without issue all day, with more than 11.5 million pounds of liquid methane and liquid oxygen being fully loaded into the rocket before the automated abort triggered. SpaceX’s launch directors posted on X, “Standing down from today’s flight test attempt,” and shut down the livestream shortly after.
Musk confirmed the root cause within hours. “Some of the engines didn’t start, triggering an automatic launch abort,” he wrote on X. “To be confident of a good flight, 2 Raptors will be removed and replaced. Most probable launch timing is early next week.” SpaceX engineers began draining propellant tanks immediately and Booster 20 was rolled back to its hangar for inspection.
The timing adds a layer of significance that did not exist during any of the previous 12 Starship flights. This is the first time SpaceX has attempted to launch Starship since the company made its stock market debut in June, listing under ticker SPCX at $135 per share. Public investors are now watching every Starship outcome in real time, and a last-second abort carries more visibility than it would have six months ago.
Flight 13 was designed to be one of the most consequential tests in the program’s history. It was set to carry 20 Starlink V3 satellites, the first operational payload Starship has ever attempted to deploy. Six of those satellites carried external cameras to photograph Starship’s heat shield from the outside during flight, which would act as a self-inspection approach SpaceX has never attempted before. The mission also needed to complete a Raptor engine relight in space, a step SpaceX skipped on Flight 12 in May after losing an engine during ascent. That Flight 12 booster also flipped 90 degrees off course during its boostback burn when five engines failed to reignite.
SpaceX has not announced an official next launch date. Musk’s “early next week” window points to July 21 or 22 at the earliest, pending the engine swap and a return to the pad.
News
Elon Musk secretly acquires $1B energy company to power the AI future
Elon Musk flew under the radar with his recent purchase of a $1 billion energy company, according to Federal Trade Commission (FTC) documents.
Transaction number 202612350 listed Tesla and SpaceX frontman Elon Musk as the acquiring party and CF APR Super Holdings LLC as the seller, with New APR Energy, LLC as the acquired entity. The deal, which closed without public announcement, came to light on May 14.
BREAKING: Elon Musk acquires Jacksonville power company APR Energy in a deal valued at more than $1,000,000,000.00.
— Polymarket Money (@PolymarketMoney) July 15, 2026
Analysts inferred the deal’s scale from minority stakeholder disclosures, including one report of a 5 percent interest sold for approximately $50.4 million. Fortress Investment Group had purchased APR’s assets in late 2024, rebranded the operation as New APR Energy, and subsequently transferred ownership to Musk.
APR Energy specializes in rapidly deployable power infrastructure. The company maintains one of the world’s largest fleets of mobile gas and diesel turbines, with more than 1.1 gigawatts of generation capacity. Its modular units, which are often trailer-mounted, enable turnkey installations ranging from 20 MW to over 500 MW.
APR provides full engineering, procurement, construction, operation, and maintenance services for behind-the-meter power plants, serving everything from data centers, utilities, and industrial clients.
The firm has expanded aggressively to meet surging demand, recently adding turbines and deploying over 100 MW for a major AI hyperscaler. Its solutions bridge critical gaps where grid interconnections face delays of two to five years, according to Yahoo.
The acquisition means something more for Musk. As he continues to expand projects in artificial intelligence, especially xAI, his AI venture, there is a greater need to supply energy-intensive supercomputing clusters, including the Colossus project, with what they need: reliable and high-capacity power.
Ownership of APR provides immediate access to flexible generation assets that can be deployed adjacent to data centers, reducing dependence on a strained infrastructure. It also complements Tesla’s energy storage business, so Musk will be able to pull from his own entities to address the rapid scaling demands of AI training and compute.
News
Tesla has to fix a big problem with its old headlights, NHTSA says
Tesla had a petition protesting a recall to fix a potential issue with 2017-2023 Model Y and Model 3 vehicles’ headlights was denied, as the National Highway Traffic Safety Administration (NHTSA) disagreed with the company’s opinion of things.
The recall covers approximately 19,917 Model Y and Model 3 vehicles built from 2017 to 2023. Tesla initially submitted a noncompliance report for the headlights on these vehicles on March 15, 2024. Tesla then petitioned for an exemption from the fix, which violated FMVSS No. 108 (40 CFR 571.108), arguing that the “noncompliance is inconsequential as it relates to motor vehicle safety.
🚨 Tesla was denied a petition by the NHTSA to avoid a recall of 19,900 2017-2023 Model 3 and Model Y vehicles.
The NHTSA found that the vehicles’ headlights may exceed maximum lighting levels. Tesla argued it was inconsequential and did not require a recall. pic.twitter.com/m8Jmm1teLL
— TESLARATI (@Teslarati) July 16, 2026
The NHTSA disagreed, stating that Tesla’s conclusion that the headlights do not increase any risk was not an opinion it shared. The agency said it disagreed with Tesla’s assumption that glare is not increased to surrounding traffic. This issue could be highlighted even more in certain weather conditions.
Tesla will be required to remedy the issue, the NHTSA ruled:
“In consideration of the foregoing, NHTSA has decided that Tesla has not met its burden of persuasion that the subject FMVSS No. 108 noncompliance is inconsequential to motor vehicle safety. Accordingly, Tesla’s petition is hereby denied, and Tesla is consequently obligated to provide notification of and free remedy for that noncompliance under 49 U.S.C. 30118 and 30120.”
The issue here appears to be the angle of the headlights and the brightness they emit during operation. The NHTSA report states that:
“Tesla’s headlamp supplier, Marelli Automotive Lighting, tested 25 right-hand and 25 left-hand lamps, and for this sample, found the maximum photometric intensity measured in the 10°U to 90°U and 90°L to 90°R zone was between 136.2 cd and 230.1 cd for the right-hand lamps and between 117.5 cd and 160.3 cd for the left-hand lamps. According to Tesla, these tests revealed that the photometric intensity of the right-hand and left-hand headlamp lower beam on the subject vehicles may measure as much as 230.1 cd in the 10°U to 90°U and 90°L to 90°R zone, exceeding the maximum photometric intensity by 105.1 cd. Additionally, Tesla states that a left-hand lamp tested by a Transport Canada recognized laboratory measured a maximum of 171.27 cd in the 10°U to 90°U and 90°L to 90°R zone. Despite these measurements exceeding the allowed photometric maximum of 125 cd, Tesla believes that the subject noncompliance is inconsequential to motor vehicle safety.”
Tesla also argued at some points that the headlights had not been deemed responsible for any complaints, accidents, or injuries related to the noncompliance.