Connect with us

News

SpaceX Starship aborts Raptor engine test, briefly catches fire

Starship SN8 is pictured here shortly before liftoff in December 2020. Largely identical, Starship SN11 is working towards its own flight test as early as this week. (SpaceX)

Published

on

Update: On March 15th, SpaceX got within milliseconds of Starship serial number 11’s (SN11) first Raptor engine test but suffered an abort just before full ignition, briefly leaving the rocket on fire.

Around 12:26 pm CDT, after an otherwise nominal static fire flow, Starship SN11 momentarily ignited one or two of its three Raptor engines’ preburners, referring to a central component that burns cryogenic liquid propellant into gas that’s ready for combustion. As with all preburner tests, intentional or otherwise, the end result looked a bit like a weak static fire and produced a small but visible amount of flame and thrust. Unlike intentional preburner tests, the static fire abort seemingly ignited something hidden inside Starship SN11’s and appeared to burn for at least another 30-40 seconds.

Starship SN8 intentionally performed a preburner test representative of SN11’s abort back in October 2020.

Raptor has proven itself to be an extremely durable engine, up to and including surviving visible onboard fires during actual Starship flight tests. Nevertheless, depending on the source of SN11’s post-abort fire and what it may or may not have burned or damaged, it’s no surprise that SpaceX ended testing for the day instead of quickly trying again, which it’s done several times prior. If the fire was largely harmless, SpaceX has already distributed notices suggesting a second attempt could happen as early as 6am to 12pm CDT (UTC-5) on Tuesday, March 16th. If more time is needed, SpaceX has the rest of the week to conduct any necessary repairs or swap out SN11’s Raptor engines.

Public documents show that SpaceX has plans to static fire and launch its latest Starship prototype within a two-day period that could begin later today.

SpaceX shipped Starship SN11 from its Boca Chica, Texas rocket factory to test and launch facilities a mile down the road on March 8th, less than five days after Starship SN10 exploded minutes after touchdown. The very next day, SpaceX completed ambient-temperature proof testing, filling Starship with benign nitrogen gas to check for leaks and verify system health. Two days after that, Starship SN11 appeared to complete a several-hour cryogenic proof test – swapping nitrogen gas for its supercool liquid form – without issue.

Despite the seemingly successful ‘cryo proof,’ something prevented a subsequent static fire test planned on March 12th before any attempt could be made, delaying the next attempt until after the approaching weekend. An agreement between SpaceX, Cameron County, and the state of Texas currently prevents road closures (and thus rocket testing) on weekends falling between Labor Day and Memorial Day, rules meant to preserve some level of public access to Boca Chica Beach.

Advertisement
-

As a result, unless SpaceX is already ready to launch (it has waivers for three such weekend closures for launch attempts), the company has to wait until Monday even if a minor issue fixable in hours or a day or so scrubs Friday test plans. While inconvenient, it’s worth noting that the existence of that public beach and the strong regulations that protect its public domain is likely one of the only reasons the general public can still get as close as they can to SpaceX’s Boca Chica ‘Starbase’.

For whatever reason, that road closure agreement does still mean that SpaceX will (in theory) be able to test and launch any day of the week from May 31st to September 6th, save for a few holidays, effectively boosting the number of opportunities by 40% for those 14 weeks. Until then, SpaceX is doing everything it can to take full advantage of the five days a week it is allowed to test Starship prototypes. N

Notably, although Starships SN8 and SN9 both hit a few weeks of technical and regulatory snags while preparing for their high-altitude launch attempts, SpaceX has been gradually speeding up that process over time. Starship SN10, the first prototype of its kind to land in one piece, took just 33 days to go from pad arrival to liftoff and spent just 8 days between its first static fire and launch attempts. The same feats took Starship SN8 77 and 50 days, respectively, with SN9 splitting the difference at 43 days from transport to liftoff and 28 days between its first static fire and launch attempts.

Road closure requests, a safety warning for residents, and a Temporary Flight Restriction (TFR) filed with the FAA all suggest that SpaceX’s current plan is to attempt Starship SN11’s first triple-Raptor static fire between 6am and 12pm CDT on Monday, March 15th. If that test goes almost perfectly, SpaceX wants to turn the rocket around for a 10 km (6.2 mi) launch attempt on Tuesday, March 16th – the very next day. Given the past performance of high-altitude Starship prototypes, that target is decidedly ambitious and likely to incur delays, but it still reveals the true scope of SpaceX’s goals even at this early stage of development.

If Starship SN11 does manage to launch within a few days of its first static fire attempt, SpaceX would still crush SN10’s 33-day record by a factor of three. Stay tuned for updates on Monday’s possible Starship static fire and rapid Tuesday turnaround attempt

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Tesla may test customer-owned Robotaxis as early as next month, Musk says

Published

on

Credit: @AdanGuajardo/X

Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.

In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:

“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”

The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.

This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.

Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.

December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.

Tesla Cybercab goes on sale for $29,990, slated for December deliveries

Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.

The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.

Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.

For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.

Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.

Continue Reading

Elon Musk

FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says

Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.

Published

on

By

Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “As I was saying … Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” Musk wrote on X Monday.

Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.

The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.

Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.

Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.

Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.

Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.

Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.

Continue Reading

News

Tesla makes $3.3 billion Cybercab bet at Giga Berlin

Published

on

Credit: Tesla

It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.

Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.

The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.

Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.

The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).

This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.

The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.

The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.

For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.

They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.

Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.

Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.

Continue Reading