News
SpaceX Starship aborts Raptor engine test, briefly catches fire
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.
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.
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
Investor's Corner
Tesla Robotaxi gets a massive upgrade in Nevada
Nevada regulators just approved a massive expansion of Tesla’s robotaxi fleet across the entire county.
Tesla’s robotaxi footprint in Nevada just grew by roughly 500 times in a single regulatory vote.
The Nevada Transportation Authority approved Tesla’s full Autonomous Vehicle Network Company permit on Thursday, clearing the way for the company to deploy up to 5,000 driverless vehicles across Clark County over the next 12 months. The decision came during a four hour general session meeting that Tesla investor Sawyer Merritt watched live and reported on X, noting the vote replaces the interim order that had limited Tesla to just 10 robotaxis on a narrow stretch of the Las Vegas Strip.
EXCLUSIVE: Tesla has just officially received approval for its full Autonomous Vehicle Network Company permit in Nevada, clearing the way for Tesla to launch a paid public Robotaxi service in Las Vegas.
This officially allows @Tesla to deploy up to 5,000 robotaxis over the next… pic.twitter.com/DPs5UtUlrE
— Sawyer Merritt (@SawyerMerritt) August 20, 2026
That earlier cap, covered here after it surfaced on August 13, came with restrictions that looked stricter than what Tesla runs in Austin: a 45 mph speed ceiling, no airport pickups, and a geofence confined to the Strip corridor. The new approval extends Tesla’s operating authority to all of Clark County, with room to request an even wider geofence across the state.
Tesla representatives at the meeting said they have no intention of putting 5,000 cars on the road right away. Commercial rides are expected to start within 30 days, pending vehicle inspections, insurance filings, and fare approval, the standard steps every robotaxi operator in Nevada has had to clear.
Tesla’s own Robotaxi account replied to the news with a short line, The golden future is upon us.
The timing lines up with Tesla’s broader robotaxi push this month. The company is preparing to open Cybercab rides to the public in Austin as soon as this month, and it opened a sweepstakes for riders to win a seat at the launch event. Tesla filed its original application for a 5,000 vehicle Nevada fleet back in June, a request regulators trimmed to 10 vehicles when they issued the interim order in July. Thursday’s vote effectively grants the number Tesla asked for from the start.
Zoox, the Amazon owned robotaxi operator, has run in Nevada since 2025 and was capped at 100 vehicles before Thursday’s decision. Tesla’s new ceiling puts it well ahead of that comparison on paper, though the company has said its actual fleet size will depend on how quickly FSD v15 rolls out, the software update executives have called the gateway to scaling unsupervised robotaxi operations nationwide.
News
Tesla admits to slow Model Y Robotaxi integration, but for a good reason
Tesla welcomed JPMorgan analysts to one of its factories earlier this month, with the Wall Street firm highlighting its findings in a new note to investors. One of the more pertinent pieces of information is that Tesla admitted to slowly integrating Model Y vehicles into its Robotaxi fleet, but it has a good reason.
JPMorgan analysts recently toured Tesla’s Fremont Factory and met with the company’s investor relations team, emerging with a clearer picture of the automaker’s Robotaxi strategy. According to the bank’s note, Tesla is intentionally limiting the addition of Model Y vehicles to its existing Robotaxi fleet.
The firm’s analysts said:
“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change in performance, comparable to the leap from V13 to V14. The V15 upgrade encompasses seven core technologies, with ~40% of those currently being tested in the robotaxi fleet, where initial feedback has been encouraging.”
JPMorgan after meeting with Tesla recently in Fremont:
“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change… pic.twitter.com/W9yGCWRT3C
— Sawyer Merritt (@SawyerMerritt) August 20, 2026
Far from signaling delays or doubts about autonomy, the move reflects strong management confidence in the near-term scalability of the purpose-built Cybercab.
Tesla has operated its Robotaxi service primarily with modified Model Ys since launching in Austin and expanding to other markets. Yet the company is now deliberately holding back further Model Y conversions. The rationale is straightforward: leadership believes the Cybercab, a two-seat, steering-wheel- and pedal-free vehicle optimized for high utilization, can ramp production and deployment more efficiently in the coming months.
This dedicated form factor promises better unit economics for the majority of rides, which typically involve one or two passengers, while freeing consumer Model Y inventory for retail sales.
Supporting this pivot is Full Self-Driving (FSD) software version 15, which Tesla describes as a genuine step-change in performance, comparable to the leap from V13 to V14. The update incorporates seven core technologies; roughly 40 percent are already undergoing real-world testing in the current Robotaxi fleet, with early feedback described as encouraging.
Tesla is carefully managing software development to minimize regressions in core driving functions as new capabilities are added. Management positions V15 as the primary gateway to scaling unsupervised FSD. Importantly, the existing AI and Hardware 4 stack is already capable of running V15 and supporting unsupervised operation.
Cybercab itself is only the first vehicle on the platform. Tesla reiterated that additional form factors will follow, pointing to concepts such as the earlier “Robovan” demonstration as examples of how the architecture can evolve.
Tesla’s mysterious Robovan makes a sneak peek with Optimus in Terafab video
Parallel progress continues on the Optimus humanoid robot, which remains on track for start of production in the coming months, with commercial sales possible as early as the second half of 2027. Generation 3 details will be revealed closer to production to preserve competitive advantages, while Generation 4 scope will draw on real-world Gen 3 experience.
JPMorgan left the meeting with a deeper appreciation for Tesla’s manufacturing automation and maintained its $475 price target. The decision to slow Model Y Robotaxi integration is therefore not a setback but a calculated prioritization of a more efficient, purpose-built solution that management believes is ready to scale.
Elon Musk
Elon Musk gives a timeline for SpaceX’s first Starship catch attempt
SpaceX CEO Elon Musk announced today that the company will likely attempt to catch the Starship upper stage with its launch tower arms “in a few months.”
In a post on X, Musk wrote, “Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.” He added that the first reflight of a Starship vehicle is expected by the end of 2026 or early 2027, describing it as “a fork in the road of history for consciousness reaching the stars.”
Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.
First reflight of the ship will be either end of this year or early next. That will be a fork in the… https://t.co/O5g9pqrzyo
— Elon Musk (@elonmusk) August 20, 2026
Musk’s prediction comes amid ongoing progress toward full reusability of the Starship system, a two-stage rocket designed for rapid turnaround and dramatically lower launch costs. Catching the upper stage, known simply as “ship,” with the Mechazilla tower’s mechanical arms would mark a major milestone. It would allow both stages to return directly to the launch site for quick refurbishment and reuse, eliminating the need for ocean recovery.
Musk has previously signaled plans for a ship catch. In July, shortly after SpaceX’s wildly successful Starship 13 mission, he stated that the company would attempt to catch the ship with the tower on the next flight unless problems emerged in the mission data review. Earlier comments also outline conditions such as successful soft ocean landings before attempting a land recovery to minimize risk.
SpaceX has solved Starship’s biggest challenge, Elon Musk says
The latest update from Musk adjusts this timeline to a few months, reflecting the iterative nature of the test campaign.
SpaceX has already demonstrated the tower catch technique successfully with the Super Heavy booster on a couple of occasions. The first successful booster catch occurred during Flight 5 in October 2024, when the massive first stage returned to the Starbase pad in Texas and was plucked from the air by the tower arms.
Additional catches followed on later flights, including Flight 7, proving the concept for the booster and building confidence in the system as a whole.
Achieving a similar catch for the upper stage would represent a significant step forward. The ship returns from much higher speeds and greater heat loads after orbital or near-orbital flight. Success would advance SpaceX’s goal of full and rapid reusability, potentially reducing the cost of access to orbit by a factor of 100 or more and supporting ambitions for frequent satellite deployments, lunar missions, and eventual Mars flights.
Musk has long emphasized that true reusability, refueling rather than discarding hardware, is essential for making humanity a multi-planetary species.
As SpaceX continues refining Starship through successive test flights, the coming months will test whether the ambitious catch timeline can be met. The combination of prior booster successes and improving ship landing precision suggests the company is steadily closing in on this historic capability.