News
SpaceX loses record-breaking rocket booster after sixth successful Starlink launch
SpaceX has suffered its second rocket landing failure of 2020 despite the fact that both lost Falcon 9 boosters successfully launched 60 Starlink satellites, an anomaly that CEO Elon Musk says will need a “thorough investigation”.
After a rare last-second launch abort on March 15th and a three-day range-related delay, Falcon 9 booster B1048 lifted off with 60 upgraded Starlink v1.0 satellites on its fifth orbital-class mission. At least for the first two and half minutes, the booster performed precisely as intended, carrying a fueled upper stage and its ~16 metric ton (36,000 lb) payload to an altitude of 55 km (34 mi) and a velocity of 1.8 km/s (1.1 mi/s). However, about 10 seconds before the booster reached main engine cut-off (MECO) and stage separation, something went wrong.
While there is some ambiguity in his response, according to Musk, at least one of Falcon 9 B1048’s nine Merlin 1D engines performed an early shutdown before MECO. The rocket’s computer immediately accounted for the anomaly, extending the remaining eight-engine booster burn 5-7 seconds beyond the nominal timeline to ensure mission success. While the booster’s loss is still disappointing and the premature engine shutdown more than a little concerning, it’s critical to remember that mission success was ensured. Just 15 minutes after liftoff, the rocket’s upper stage successfully spun up and deployed another 60 Starlink satellites, bringing SpaceX’s operational constellation to an incredible ~350 satellites.



Based on live views available from SpaceX’s launch webcast, it appears that Falcon 9’s “early engine shutdown” is more of a euphemism for a fairly violent engine failure that triggered an instantaneous cutoff, preventing damage elsewhere. While SpaceX would certainly rather avoid in-flight engine failures, Falcon 9’s nine Merlin 1D booster engines are installed inside an aluminum ‘octaweb’ structure that transmits their thrust to the rest of the rocket but also effectively quarantines each engine in a blast-proof bunker.

Nevertheless, the rocket’s highly-attuned software and affected octaweb engine bunker did their jobs, instantly shutting the failing engine down while also preventing the explosion and resulting shrapnel from damaging the rest of the rocket. More likely than not, B1048’s autonomous decision to always put mission success before booster recovery lead the booster to expend a majority of the propellant needed for its landing attempt to make up for the 10 or so seconds operating at only ~89% thrust.
As a result, B1048 may have simultaneous subjected itself to a much more extreme atmospheric reentry and run out of propellant before it could complete (or maybe even start) its drone ship landing burn. There’s also a chance that the engine that failed was one of the three engines required for reentry and landing burns, an asymmetry that would be impossible to overcome on the fly. Ultimately, the booster likely impacted the ocean at a near-supersonic velocity, smashing it into aluminum confetti. Thankfully, the late B1048 had a record-breakingly productive career as an orbital-class booster, placing dozens of tons of payload into orbit over five successful launches. Its loss is regrettable but the booster has more than earned its keep.

Aside from two twice-flown Falcon Heavy Block 5 side boosters of unknown status and 2-3 new boosters assigned to critical NASA and US Air Force missions, SpaceX’s fleet is now down to just three flightworthy Falcon 9 boosters. This could dramatically limit its options for near-term commercial flights, as none of those rockets – even assuming flawless launch and landing debuts – will likely be ready for their first reuses until May or June. Meanwhile, B1051 and B1049 have three and four missions under their respective belt and both completed their last launches just 50-70 days ago, while B1059 flew for the second time just two weeks ago. Despite the fact that it successfully completed its fifth mission, B1048’s in-flight engine failure will almost certainly delay upcoming launches, although the degree of those delays is up for debate.
Up next for SpaceX is SAOCOM 1B, an Argentinian radar satellite set to become the first payload launched into a polar orbit from the US East Coast in half a century. Before B1048’s anomaly, the mission was scheduled to launch no earlier than March 30th and could use any of unassigned boosters described above
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
SpaceX just locked up a NASA record no other U.S. spacecraft can touch
SpaceX’s Crew-13 Dragon reached the ISS in under eight hours, and NASA confirmed a record.
SpaceX now owns every spot on the list of the five fastest trips a U.S. spacecraft has ever made to the International Space Station, and its newest entry beat the old mark by more than four hours.
Crew Dragon Grace docked to the forward port of the station’s Harmony module at 7:05 p.m. ET on October 1, just 7 hours and 55 minutes after lifting off from Space Launch Complex 40 at Cape Canaveral. NASA confirmed the milestone in a space station blog update, writing that the flight “marked the fastest launch‑to‑docking of a U.S. spacecraft in the history of the International Space Station.”
The previous U.S. record also belonged to Dragon. SpaceX’s uncrewed CRS-31 cargo mission reached the station in a little over 12 hours in November 2024. The fastest crewed trip before last week was Crew-11, which took 14 hours and 43 minutes in August 2025, according to Space.com.
A post that Elon Musk reposted on Monday filled out the rest of the ranking. Behind Crew-13, CRS-31 and Crew-11 sit Axiom’s Ax-2 mission at 15 hours and 35 minutes and NASA’s Crew-4 at 15 hours and 44 minutes. All five flew on Dragon.
SpaceX turned a heralding moment for Starship into its greatest
Crew-13 carried NASA astronauts Jessica Watkins and Luke Delaney, Canadian Space Agency astronaut Joshua Kutryk, and Roscosmos cosmonaut Sergey Teteryatnikov. NASA had projected a docking around 8 p.m. ET, as Teslarati reported the day before launch, and Dragon arrived nearly an hour early. Our launch day coverage noted that the flight was lined up to be the quickest Crew Dragon transit yet.
The speed came from timing more than hardware. SpaceX’s Julianna Scheiman said the station “was in an opportune spot in space,” which let Dragon start closing the gap almost immediately after reaching orbit. “This is close to the fastest it could be,” she added. Most Crew Dragon flights still take close to a day, using a series of Draco thruster burns to raise and phase their orbit before arrival.
Dragon’s next job at the station is a departure. NASA said Monday it is targeting 8:05 a.m. ET on Wednesday, October 7, for Crew-12 to undock, setting up a splashdown off the coast of California around 11:34 a.m. on Thursday. Clearing that port makes room for CRS-35, a cargo Dragon carrying the final set of iROSA solar arrays.
Dragon remains NASA’s only operational ride to the station while Boeing’s Starliner stays grounded, and the agency recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification.
Elon Musk
Elon Musk teases TSMC as potential Terafab partner
Elon Musk has acknowledged that early discussions with Taiwan Semiconductor Manufacturing Company (TSMC) could bring the company into his ambitious Terafab semiconductor project, signaling a possible partnership with the world’s leading contract chipmaker.
Musk confirmed that early talks are underway, but as of right now, they are “just discussions.” There is no confirmation of a deal nor dismissal of the possibility of one, leaving open the prospect of one of the largest advanced-chip collaborations under discussion in the U.S.
@wholemars Just discussions, but something may come of it
— Elon Musk (@elonmusk) October 3, 2026
The report that speculated on potential discussions between Terafab and TSMC comes from Tim Culpan, who outlined a few ways the collaboration could operate. One is TSMC using the project as an “anchor customer” for future facilities in Texas, potentially contributing process expertise, operational know-how, or capacity while Terafab provides capital, long-term purchase commitments, or both.
Tesla and SpaceX jointly developed the Terafab project, with Intel already participating on the tech side. Elon Musk announced the project in March, and it intends to produce more than one terawatt of AI compute capacity annually once fully built.
Company statements place the first phase at approximately $16.8 billion in cost, with later filings pointing to a total that could reach well into the tens of billions across multiple stages.
Intel joined the effort in April 2026 and is expected to supply its 14A manufacturing process for the full-scale plant.
Musk has said existing suppliers, including Samsung and TSMC, remain important for near-term needs; Tesla already has production arrangements with Samsung for AI5 and AI6 chips, but that future demand from Optimus robots, Cybercab vehicles, and planned space-based data centers will eventually exceed what the global industry can currently deliver.
Terafab is positioned as the long-term answer to that projected shortfall, and Tesla did something similar during COVID to avoid a chip shortage. This is just a much larger-scale solution.
If the partnership were to materialize, it would add TSMC’s industry-leading strategies to a project that already combines Tesla’s and SpaceX’s capital and offtake with Intel’s process technology. For now, the only public confirmation is Musk’s brief acknowledgement that conversations are occurring.
News
Tesla reveals early Robotaxi charging strategy, showing scrappy DNA
Tesla’s early strategy for charging units operating within its Robotaxi fleet reveals that the company surely has not lost any of that scrappy DNA that took it from an unlikely success story to the most valuable carmaker in the world.
An observer at a Tesla Supercharger in Austin spotted ten total Robotaxi vehicles arrive: one Cybercab and nine Model Y units. A Tesla employee was waiting at the lot and allowed each unit to park itself; every car that arrived had nobody in it.
Tesla wins FCC approval for wireless Cybercab charging system
The Tesla employee would walk around and plug each car in, adjusting the parking if needed:
So look at what I found. This is how Tesla charges unsupervised robotaxis at a public supercharger. Here is a driverless Cybercab showing up with no one in it. There are 9 other Model Ys that showed up too. A Tesla employee is walking around and plugging each of them in. She also moves the cars if they are not positioned well enough to charge. I love this process. One person charges multiple robotaxis at once
— Abhimanyu Yadav (@WorldlyReviewer) October 3, 2026
It’s a very interesting strategy, but extremely understandable at this early point in the Robotaxi program. It’s only been out for about 15 months, and Cybercab just entered the fleet in early September.
On top of that, Tesla is still working tirelessly on its wireless charging apparatus, and a new patent was just published regarding that product last week.
However, this is just another example of how Tesla still has plenty of that scrappy DNA leftover from the “production hell” days, when CEO Elon Musk slept on the floor of the factory, employees were working crazy hours, Tesla was building Sprung Structures to build cars in, and the company was tiptoeing on the brink of bankruptcy.
@Teslarati Sheer magnitude of the entire production system is hard to appreciate. Almost every element of production is >75% automated. Only wire harnesses & general assembly, which are <10% of production costs, are primarily manual.
— Elon Musk (@elonmusk) October 12, 2020
For now, Tesla is utilizing a simple system for recharging its ride-hailing vehicles, and that is a Tesla employee doing it manually until another solution presents itself. Sure, it’s not the most high-tech thing, and it certainly is not what people might have expected at this point in time, but it works, and it’s keeping the entire suite running.