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
Tesla has extended its Bay Area ride-hailing service to include pickups and drop-offs at San Francisco International Airport (SFO). The update, shared via the company’s official channels on July 21, allows users in the region to request rides directly to and from one of California’s busiest airports.
The expansion builds on Tesla’s secured limousine permit for SFO operations. Public records show the permit became effective March 20, 2026, and remains active through January 31, 2027. Tesla vehicles operating the service now display authorized limousine permits issued by the City and County of San Francisco.
Our Bay Area rideshare service now goes to SFO ✈️
— Tesla AI (@Tesla_AI) July 21, 2026
Tesla’s ride-hailing program in California relies on Model Y vehicles equipped with Full Self-Driving (Supervised) technology. Human safety drivers remain present in compliance with state regulations, distinguishing the service from fully driverless operations.
The Bay Area geofence covers a broad area spanning north of San Francisco to south of San Jose, offering extensive connectivity across the region.
UPDATE: Elon Musk reveals why Tesla didn’t say ‘Robotaxi’ upon California launch
This SFO addition follows earlier progress at other Bay Area airports. Tesla previously expanded service to San Jose Mineta International Airport (SJC) in late 2025. The company had engaged with SFO, SJC, and Oakland International Airport officials as early as September 2025 to secure necessary approvals for passenger transport.
The service provides a new option for travelers seeking electric, app-based transportation integrated with Tesla’s ecosystem. Rides are booked through Tesla’s dedicated ride-hailing application, which handles matching, routing, and payments. Pricing follows standard ride-hailing models, with potential adjustments based on distance, time, and demand.
Tesla’s California ride-hailing program launched in July 2025 with an initial invite-only rollout in the Bay Area. It started alongside operations in Austin, Texas, marking the company’s second major U.S. market.
The Bay Area remains a primary focus in California, with service centered on high-demand corridors connecting residential, commercial, and now major transportation hubs. This latest airport integration represents a practical step in Tesla’s broader mobility ambitions within the state.
Tesla has officially revealed its 2026 Summer Update, which comes with a variety of crazy new features, including Navigation fixes that owners have been wanting for months.
Tesla routinely releases a larger update with the Spring, Summer, Fall, and Winter updates, where it ships a variety of new features, bug fixes, and other additions to customer cars.
The 2026 Spring Update featured things like “Hey Grok” voice assistance, a redesigned self-driving app, Unreal Engine visual upgrades, and more.
🚨 TESLA’S SUMMER UPDATE FOR 2026 IS HERE:
Featuring:
✅ Self-Driving Stats in Mobile App
✅ Caraoke with Scoring
✅ Automatic Navigation
✅ Preferred Routes
✅ Set Arrival Energy from Mobile App
✅ Send Custom Wraps from Mobile App
✅ Rear Display Lock
✅ Other Improvements
🔌… https://t.co/C9IW3egEhH
— TESLARATI (@Teslarati) July 21, 2026
Tesla’s Summer Release has about ten new features; we’ll show you each and detail them below:
New Grok Voice Commands
“Grok can now make phone calls, search and play music, adjust climate, open the glovebox, and answer questions about your Tesla.”
Self-Driving Stats in Mobile App
“View and share self-driving stats from the mobile app.”
Caraoke With Scoring
“Caraoke now scores your singing while in Park. High scores are saved to your Tesla profile.”
Automatic Navigation
“Automatic Navigation now adapts to your routine.
In addition to Home, Work, and upcoming calendar events, your vehicle can now suggest and route to places you visit regularly – like a school drop-off on the way to work, or the gym on the way home.”
Preferred Routes
“For a more personalized experience, navigation now prioritizes routes that you’ve taken before”
Set Arrival Energy from Mobile App
“Set your desired Arrival Energy from your phone.”
Send Custom Wraps from Mobile App
“Skip the USB drive and upload a custom wrap of your car from the mobile app. Instructions for creating a custom wrap here: https://github.com/teslamotors/custom-wraps.”
Rear Display Lock
“Kids can watch content on the rear screen, but only the front row can control it through the rear screen app.”
Other Improvements
- Find Superchargers by name when searching for a destination
- Add Apple Music songs to queue from search and artist page
- Set your preferred zoom level for the Self-Driving visualization
- Intro animations for new Model 3 and Y
Tesla’s reason for Starlink integration on Cybercab might surprise you, as the company’s Head of AI, Ashok Elluswamy, finally shed some light on the reason they are putting a satellite internet terminal on its ride-hailing-geared vehicle.
On Monday, Tesla officially confirmed that it would integrate Starlink V5 terminals into Cybercab vehicles, something many Tesla fans had figured the company would do, as the vehicle is primarily geared toward giving rides without any passenger intervention.
Starlink V5 directly integrated in Cybercab pic.twitter.com/FxzTtzjB6I
— Tesla (@Tesla) July 20, 2026
The ability to access the internet would allow riders to work or play in the car with their devices. It seemed like a more-than-reasonable feature to add to the Cybercab, which made its way off the production lines for the first time earlier this year.
Tesla reveals first vehicle model to receive Starlink integration
However, the move is not for the rider, as Elluswamy confirmed on Monday night. Instead, it’s actually for Tesla to be able to have a constant connection to the cars in the Robotaxi fleet so it can troubleshoot issues, contact riders, or resolve other issues.
Elluswamy said:
“It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.”
It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.
— Ashok Elluswamy (@aelluswamy) July 20, 2026
Many initially assumed the option of constant connectivity would be enabled on the Cybercab for passenger entertainment or work. With the Cybercab, passengers won’t be doing anything but enjoying the ride, so it seemed more than logical that they would be hanging out with Starlink internet access as an amenity.
However, Tesla’s primary concern with Robotaxi is safety, and nailing these first unsupervised rides is a crucial step to setting a good narrative on how effective driverless transportation can be.
Being able to get in touch with passengers or a vehicle if something is wrong is a crucial part of the overall experience, and preventative measures are being taken by Tesla to ensure a smooth process, even in the worst-case.
Tesla expands ridesharing service in California to new hotspot
Tesla reveals 2026 Summer Update with crazy fixes to Nav and more
