News
SpaceX's in-flight rocket engine failure threatens NASA astronaut launch debut
An in-flight rocket engine failure during SpaceX’s March 18th Starlink launch could pose a threat to the company’s imminent NASA astronaut launch debut according to a statement provided by the space agency yesterday.
SpaceX and NASA are currently working around the clock to prepare a Falcon 9 rocket and Crew Dragon spacecraft for the company’s inaugural astronaut launch, a flight known as Demonstration Mission 2 (Demo-2/DM-2). All launch vehicle and spacecraft hardware – including booster B1058, an expendable upper stage, a spacecraft trunk, and the Crew Dragon capsule itself – are already believed to be at SpaceX’s Florida launch and processing facilities.
Prior to March 18th, the biggest gating items were believed to be a few final parachute tests and a whole lot of paperwork and reviews, as well as some important but less showstopping astronaut training. Unfortunately, SpaceX has suffered two unforeseen issues of varying severity in the last few days, both of which are now all but guaranteed to impact Crew Dragon’s astronaut launch debut schedule.
“According to the CCtCap contracts, SpaceX is required to make available to NASA all data and resulting reports. SpaceX, with NASA’s concurrence, would need to implement any corrective actions found during the investigation related to its commercial crew work prior to its flight test with astronauts to the International Space Station. NASA and SpaceX are holding the current mid-to-late May launch timeframe, and would adjust the date based on review of the data, if appropriate.”
NASA — March 25th, 2020
On March 18th, less than three minutes after liftoff and shortly before stage separation was scheduled, Falcon 9 booster B1048 – on its historic fifth launch attempt – suffered an engine failure visible on SpaceX’s official webcast. By all appearances, Falcon 9’s autonomous flight computer accounted for the engine’s failure, shutdown, and the resultant loss of thrust by burning B1048’s eight remaining engines for several seconds longer than planned.
While that extra few seconds of burn time likely ensured that the rocket’s upper stage was able to make it to the correct orbit after stage separation, roughly five minutes after B1048’s extremely rapid engine failure, contact was lost. For the first time ever, there were no landing burn-related call-outs from SpaceX launch operators, the first sign that something was seriously wrong. A few minutes later, SpaceX’s webcast hosts acknowledged that the booster had been lost, perhaps lacking the propellant it needed to attempt a landing.
For reference, Merlin 1D engines likely consume some ~270 kg (600 lb) of fuel each second. Falcon 9’s landing propellant reserves are believed to be on the order of 50+ metric tons (110,000 lb). Excluding the failed engine, eight Merlin 1Ds burning at full thrust for an additional 5 seconds would consume 20% of the propellant needed for landing; 10 seconds and it would use 40%.
The anomaly was Merlin 1D engine’s first in-flight failure ever. The 2012 failure of one of an original Falcon 9 V1.0’s rocket’s nine Merlin 1C engines is SpaceX’s only other in-flight failure.
It’s likely that B1048’s engine failure was primarily related to the fact that the booster was SpaceX’s pathfinder for a fifth-flight reusability milestone, making it the most reused rocket booster ever launched. NASA currently requires all of its Crew Dragon missions to launch on new Falcon 9 rockets, hopefully mitigating direct corollaries between the Starlink L6 anomaly and astronaut launches. Regardless, the space agency says that the company will now have to complete its internal failure review and implement necessary hardware, software, or rule changes before it’s allowed to launch NASA astronauts.
That investigation could take a matter of weeks, possibly even less, but it’s entirely possible that it could take months – let alone fixing the problems that allowed the in-flight Merlin 1D engine failure to happen in the first place. Ultimately, it will almost certainly make even the first flights of Falcon 9 and Heavy rocket boosters safer, but it could substantially delay SpaceX’s Demo-2 astronaut launch debut. Still targeted no earlier than (NET) mid-to-late May 2020, it’s safe to say that it’s reasonable to expect that schedule to slip over the next 4-6 weeks. Stay tuned for updates.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
