A Tesla robotaxi got stuck repeatedly playing fart sounds through its cabin speakers during a live ride, according to an October 13, 2026 report from the San Francisco Standard. The malfunction, tied to a built-in novelty feature Tesla calls “Emissions Testing Mode,” turned a routine robotaxi trip into a viral moment and reopened a bigger question hanging over Tesla’s driverless ambitions: what happens when the software stack glitches mid-ride, and who is actually in control when it does.
The incident landed at an awkward moment for Tesla. The company is racing to scale its Cybercab fleet in Austin, fending off a federal safety review tied to alleged school-zone speeding, and trying to convince investors that robotaxi economics justify its valuation. A stuck sound-effects loop is not a safety failure in the way a missed stop sign would be, but it put a spotlight on how little visibility riders have into what Tesla’s vehicles are doing, and how slow the fix can be when something inside the car goes wrong.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Is Tesla’s “Fart Mode,” and Why Was It Running Nonstop?
Tesla’s fart-sound feature is not new. The San Francisco Standard’s report traces it back to a December 2018 holiday software update, when Tesla added a joke feature that owners nicknamed “fart mode.” Officially, Tesla calls it Emissions Testing Mode inside the vehicle’s settings menu. Drivers can pick from a library of different sound effects, adjust volume, aim the sound at a specific seat, trigger it by voice command, or set it to fire automatically when a passenger sits down and makes contact with the seat sensor.
In a personally owned Tesla, that is a harmless gag a driver can show off to friends. In a robotaxi carrying a paying stranger, with a human safety monitor on board but no owner physically present to reach the settings screen, the same feature becomes a liability if it misfires. According to the San Francisco Standard’s account, the sound got stuck on and kept repeating during the ride, and the onboard safety driver was unable to immediately stop it.
Tesla has not issued a public technical explanation for why the setting became stuck, and the exact rider, date, route, and duration of the malfunction have not been independently confirmed beyond the original report. What is confirmed is that the feature exists exactly as described, that it has existed in Tesla’s software for roughly eight years, and that it made its way, by design or accident, into a vehicle operating as part of Tesla’s commercial Robotaxi service.
Inside the Ride: What the Safety Driver Told the Passenger
The most telling detail from the San Francisco Standard’s reporting is not the joke itself but how little the human on board could do about it. Quoted in the piece, an unnamed Tesla robotaxi safety driver offered a short, almost resigned response when the passenger asked how long the sound would continue: “No idea.” Asked again about the ongoing noise, the driver said only, “Sorry.” When pressed further on what was happening, the driver added, “It’s the first time I’m experiencing this,” before apologizing a third time with a simple “I’m sorry.”
Taken together, those four lines describe a scenario where the human safety monitor, whose job is to supervise the vehicle and intervene if something goes wrong, had no clear path to silence a setting that should be trivial to toggle off. That is a minor glitch in isolation. But it is also exactly the kind of software-control gap that matters more the moment something more serious than audio malfunctions.
Tesla’s Official Support Channels: What Riders Are Supposed to Be Able to Do
Tesla’s own Cybercab rider guide lays out how a passenger is meant to interact with the vehicle during a trip. Riders can reach Tesla Robotaxi Support at (877) 798-3752 for in-ride issues, and Tesla’s materials describe two ways to flag a problem: through the cabin touchscreen or through the Robotaxi app itself, either of which can be used to request that the vehicle pull over.
Separately, Tesla maintains a dedicated channel for emergency responders. According to coverage of Tesla’s first-responder documentation from The Autopian, Tesla Robotaxi First Responder Support can be reached at (844) 837-5255, a number distinct from the general rider line. That same documentation reportedly states that connectivity or hardware issues can cause a Cybercab to attempt to pull over at the nearest safe stopping location automatically, which is the kind of fail-safe behavior Tesla has built in for more serious malfunctions than a stuck sound effect.
None of that machinery appears to have been the fix in the fart-mode incident. A stuck audio loop is not a connectivity failure or a hardware fault in the sense Tesla’s own documents describe, so the automatic pull-over protocol likely never triggered. The ride, by the available account, continued with the noise playing rather than ending early. That is a gap between what Tesla’s support infrastructure is built to catch and what an actual in-cabin software quirk looks like in practice.
Why a Joke Feature Is Suddenly a Serious Story
On its own, a stuck fart sound is a punchline. It became national news because it landed in the middle of a much bigger, much more consequential debate about whether Tesla’s robotaxi software is ready for the scale Tesla wants to reach. Elon Musk has repeatedly framed Robotaxi as central to Tesla’s next phase of growth, pointing to expanding service areas and a fast-growing Cybercab fleet. At the same time, regulators, reporters, and even some Wall Street analysts have raised pointed questions about reliability, oversight, and what happens when the software does something unexpected.
That tension was already building before the fart-mode story broke. Federal regulators opened a formal review of Tesla’s robotaxi operations earlier in October tied to allegations the vehicles exceeded speed limits in school zones, a matter covered in detail in our report on the NHTSA review of roughly 1,000 Tesla robotaxis. The fart-mode incident is a much lower-stakes event by comparison, but it feeds the same narrative: that Tesla’s driverless systems are still producing surprises its own safety drivers do not know how to resolve on the fly.
The NHTSA School-Zone Review, in Brief
Road & Track reported that the National Highway Traffic Safety Administration opened a safety review on October 9, 2026, after receiving a defect petition alleging that Tesla’s self-driving Model Y and Cybercab robotaxis exceeded posted limits in active school zones. NHTSA’s filing reportedly estimated the potentially affected fleet at roughly 1,000 vehicles, based on a petition that cited one formal complaint and three videos purportedly showing the speeding behavior. As of the available reporting, NHTSA was still evaluating whether to escalate the matter into a full defect investigation, which is a distinct and more serious step than an initial review.
Asked generally about reports of erratic robotaxi behavior, NHTSA said in a statement that it is “aware of the referenced incidents and is in contact with the manufacturer to gather additional information,” according to a report cited by the BBC. That is a standard early-stage regulatory response, not a finding of fault, but it confirms federal attention is already focused on Tesla’s robotaxi program at the exact moment the fart-mode story is drawing consumer attention to the same vehicles.
Robotaxi’s Fleet Math: From 59 Vehicles to a Fast-Growing Cybercab Rollout
The scale of Tesla’s robotaxi operation has shifted dramatically over 2026, and that shift is part of why a single bad ride now carries more weight. The Los Angeles Times reported in June 2026 that Tesla’s entire robotaxi fleet stood at just 59 vehicles, limited to three Texas cities, undercutting Musk’s public framing of rapid expansion. By October, the picture looked different. Tesla launched Cybercab service in Austin on September 3, 2026, and the company subsequently reported more than 300 Cybercabs serving Austin by October 10. Our coverage of Tesla’s Austin buildout found the Cybercab fleet there alone had grown roughly eightfold in 30 days to more than 300 vehicles, a pace documented in our report on the Austin Cybercab fleet’s 8x growth.
Wall Street analyst Dan Ives, cited in reporting from Ad-Hoc News, described Robotaxi as now operating in six U.S. cities with paid rides approaching 2.5 million miles, and noted that Nevada has approved up to 5,000 vehicles for future deployment. Ives also pointed to Full Self-Driving take rates exceeding 55% on new North American deliveries and said Cybercab production has begun. That is a bullish read. Other outlets, including The Verge, have pushed back on the framing, arguing that robotaxi mileage has looked closer to flat than fast-growing for stretches of 2026 even as Tesla’s public messaging emphasized growth.
Tesla’s own support page lists a narrower official footprint than some analyst accounts suggest: limited service in Miami, Orlando, and Tampa, Florida, plus Austin, Dallas, and Houston, Texas, six cities in total. Other reporting, including trackers dated October 22, 2026, describes Tesla Robotaxi as operating in seven U.S. metropolitan areas, a footprint that includes the San Francisco Bay Area, where Tesla reportedly still relies on a human safety driver rather than the unsupervised rides reported in the six Texas and Florida cities. That discrepancy, six officially listed cities versus a broader informal footprint, is itself a small symptom of the same transparency gap the fart-mode story exposed: riders and the public often know less about how a given robotaxi ride is actually being operated than Tesla’s own marketing implies.
Where the Robotaxi Rollout Heads Next
Tesla’s materials from October 21, 2026 describe a service that is still widening. Tesla’s purpose-built Cybercab is being added to the Robotaxi fleet, alongside Model Y-based Robotaxis. Ashok Elluswamy, Tesla’s Vice President of AI Software, said the same software would then scale to additional cities and Model Y Robotaxis.
Tesla’s Robotaxi safety materials named Las Vegas, Jacksonville, Phoenix and San Antonio as coming markets. Tesla also said it expects to reach 24/7 Robotaxi operation by the end of 2026, while also expanding to higher-speed roads, more weather conditions and additional cities. For riders, longer operating hours and more cities mean more trips where the support line and the pull-over request described earlier could matter, so it is worth knowing both before a first ride.
Looking further out, Tesla expects to begin incorporating privately owned customer vehicles into the Robotaxi network around Q2 2027, subject to operational and geographic adaptations. Lars Moravy, Vice President of Vehicle Engineering, said the company is targeting customer Cybercab deliveries before the end of 2026, though this remains a target, not a confirmed delivery date. If customer-owned cars do join the fleet, the question this incident raised, which in-car features should stay reachable during a commercial ride, becomes harder to set aside.
How Many Incidents Has Tesla Actually Reported?
Safety-incident counts for Tesla’s robotaxi program vary depending on the source and the reporting window, which is itself worth noting. The Los Angeles Times reported that Tesla had disclosed 17 incidents to NHTSA, including two low-speed crashes that occurred while remote employees had taken control of the vehicles. A separate analysis put the figure at approximately 18 incidents, with 56% attributed to other drivers rather than Tesla’s own systems. Tesla’s VP of AI Software, Ashok Elluswamy, is tied to a different statistic entirely: Tesla reportedly cited roughly 3.1 million miles without a safety monitor from January 22 through October 18, 2026, with no reported injuries, airbag deployments or pedestrian or cyclist strikes in its published safety data.
Those numbers are not necessarily contradictory. “Zero notable incidents” and “17 incidents reported to NHTSA” can both be technically accurate depending on how a company defines notable versus reportable, and whether low-speed, no-injury events tied to remote intervention count the same as an on-road collision. But the gap between Tesla’s public safety framing and the incident counts showing up in regulatory filings is now a recurring theme, one that predates the fart-mode story and will likely outlast it.
Q3 2026 Deliveries and What They Signal for Robotaxi’s Timeline
Tesla reported 486,532 total vehicle deliveries for the third quarter of 2026 on October 2, roughly 2% below the same period a year earlier but ahead of analyst expectations by a few percentage points. Deliveries are not a robotaxi-specific metric, but they matter here because Robotaxi and Cybercab both depend on Tesla’s broader manufacturing and software pipeline, including the FSD stack that underpins the autonomous driving functions. A dip in deliveries, even a modest one beating estimates, suggests Tesla is managing softer core vehicle demand at the same time it is trying to scale an unrelated, software-dependent robotaxi business. That dual pressure, selling cars while also proving out driverless software at scale, is part of why every public misstep, including a stuck sound effect, gets outsized attention right now.
Tesla Robotaxi vs. Waymo: A Different Approach to the Same Problem
Tesla and Waymo are chasing the same market with opposite philosophies. Waymo built its service around purpose-equipped vehicles loaded with lidar and other dedicated sensor hardware, expanding market by market with fully driverless operation as the default once it is approved. Tesla has bet on a camera-based system running on the same FSD software stack sold to consumers, layering in human safety drivers in markets where fully unsupervised operation is not yet approved, as reporting suggests remains the case in the Bay Area.
That approach gives Tesla a lower-cost path to scale, since it can theoretically activate Robotaxi features on cars already in the consumer fleet rather than building dedicated hardware from scratch. The tradeoff shows up in exactly the kind of incident this story covers: a consumer-facing software feature, built for personally owned cars and casual fun, ended up running inside a commercial robotaxi because the underlying software platform is shared rather than purpose-built. Waymo’s more specialized stack is less likely to carry over a novelty feature like a fart-sound setting into its paid service in the first place, simply because its software was never designed around consumer entertainment extras.
Historical Context: Fart Mode’s Eight-Year Journey From Easter Egg to Headline
Tesla has leaned into playful software extras since Musk took direct control of the company’s product messaging, and fart mode has been one of the more enduring examples. It shipped as part of a December 2018 holiday update, alongside other seasonal jokes Tesla has rolled out over the years, and became something of a signature quirk associated with Tesla ownership. For most of its life, the feature lived entirely within personally owned vehicles, where an owner could enable it, show it off, and turn it off just as easily.
Robotaxi changes that equation because the car is no longer purely a personal device. It is a shared commercial vehicle carrying a paying stranger, supervised by an employee rather than owned by the person inside it. Features designed for an owner’s living-room-style control over their own car do not automatically translate well into a commercial fleet context, and this incident is the clearest public example yet of that mismatch. Tesla’s broader push to rebrand its driver-assistance features, including dropping the FSD name in Europe in favor of more conservative terminology, reflects a similar awareness that language and framing built for enthusiast owners does not always fit a regulated commercial service.
Market and Investor Reaction
There is no indication the fart-mode story moved Tesla’s stock in any measurable way, and analysts have not cited it as a material risk factor. The bigger market conversation remains split along the lines Ad-Hoc News described: bulls like Dan Ives pointing to expanding mileage, growing Cybercab production, and regulatory approvals like Nevada’s 5,000-vehicle allowance, against skeptics highlighting flat-to-shrinking fleet figures at points earlier in the year and a steady drumbeat of regulatory scrutiny. The school-zone review and the fart-mode story both add to the skeptic side of that ledger, even if neither amounts to a financially material event on its own. Tesla released its third-quarter 2026 financial results on October 21, 2026, and indicated Robotaxi could begin having a noticeable effect on company results around Q2 2027. Investors will likely still want clarity on fleet size, incident counts, and regulatory status in one consistent set of numbers rather than the scattered, sometimes conflicting figures that have circulated through 2026.
Tesla Robotaxi Service Footprint and Fleet Snapshot
| City / Market | State | Service Status (per reporting) |
|---|---|---|
| Austin | Texas | Official Tesla service area; Cybercab fleet reported above 300 vehicles |
| Dallas | Texas | Official Tesla service area |
| Houston | Texas | Official Tesla service area |
| Miami | Florida | Official Tesla service area |
| Orlando | Florida | Official Tesla service area |
| Tampa | Florida | Official Tesla service area |
| San Francisco Bay Area | California | Reported in some accounts; described as safety-driver supervised rather than unsupervised |
| Nevada (statewide) | Nevada | Approved for up to 5,000 vehicles per analyst reporting; not yet an active service market |
Tesla Robotaxi Key Figures Timeline
| Date / Period | Metric | Figure |
|---|---|---|
| June 2026 | Total robotaxi fleet size | 59 vehicles, 3 Texas cities (LA Times) |
| 2026 (cumulative) | Incidents reported to NHTSA | 17 incidents, including 2 low-speed crashes under remote control (LA Times) |
| 2026 (cumulative, alt. count) | Incidents, attribution split | Approx. 18 incidents; 56% attributed to other drivers |
| October 2, 2026 | Q3 2026 vehicle deliveries | 486,532 units, down ~2% year over year, above analyst estimates |
| October 9, 2026 | NHTSA school-zone review opened | ~1,000 vehicles potentially affected; 1 complaint, 3 videos cited |
| October 13, 2026 (reported “30 days”) | Austin Cybercab fleet growth | Roughly 8x growth to 300+ vehicles |
| October 13, 2026 | Fart-mode malfunction reported | San Francisco Standard publishes account of stuck Emissions Testing Mode |
| October 2026 (analyst estimate) | Cumulative paid robotaxi mileage | Approaching 2.5 million miles across six cities (Dan Ives / Ad-Hoc News) |
What Tesla Needs to Fix Before the Next Viral Glitch
The practical lesson from this story is less about fart jokes and more about software architecture. Entertainment features designed for an owner-operated car, with full menu access and no time pressure, were apparently never fully re-evaluated for a commercial robotaxi context where a safety driver may not have the same settings access an owner would, and where a stuck setting cannot simply wait until the next time the car is parked at home. Tesla has already shown it is willing to pull consumer-facing features out of markets when regulatory or branding pressure demands it, as seen in its decision to retire the FSD name across the European Union in favor of more conservative language tied to ongoing changes to its underlying autonomy hardware. A similar audit of which consumer software features should even be reachable inside a commercial robotaxi build seems like a logical next step.
There is also a staffing dimension to this. Musk has publicly called for more engineering talent to join Tesla’s autonomy and chip teams, a recruitment push covered in our report on Musk’s call for chip engineers to join Tesla and SpaceX. Software reliability bugs like a stuck entertainment feature are the kind of long-tail edge case that more engineering depth is specifically meant to catch before it reaches a paying customer, rather than after a reporter happens to be in the car.
Predictions: Where This Story Goes From Here
- Tesla will likely push a quiet software patch addressing the Emissions Testing Mode bug within weeks, given the public attention, without a formal recall since the issue is not safety-critical in the way a braking or steering fault would be.
- The NHTSA school-zone review remains the more consequential regulatory thread to watch; if additional video evidence surfaces beyond the three clips already cited, expect pressure toward a full defect investigation rather than a preliminary review.
- Expect continued disagreement between bullish analysts citing expanding mileage and fleet counts and critics pointing to incident disclosures and fleet-size inconsistencies, a gap that is unlikely to close before Tesla’s next quarterly update.
- Tesla will likely continue scaling Cybercab production and the Austin fleet aggressively, since the company has shown it is willing to grow fast even while regulatory questions remain open elsewhere; Tesla said Cybercab would launch in Dallas in November 2026.
- Watch for Tesla or competing robotaxi operators to publicly clarify which consumer-oriented software features are disabled or restricted in commercial fleet vehicles, since this incident creates reputational pressure to show that distinction exists.
The Bigger Picture for Driverless Car Trust
None of this means Tesla’s robotaxi program is unsafe. The incident at the center of this story is, by every account available, an audio glitch rather than a driving failure, and it did not involve a crash, an injury, or a traffic violation. But public trust in driverless vehicles is built in small increments, and it is also lost in small increments. A rider stuck listening to fart sounds for an uncomfortable stretch of a ride, with a safety driver admitting “no idea” when asked how to stop it, is a vivid, shareable, faintly embarrassing example of exactly the kind of unpredictability that makes people hesitant to trust a car with no human behind the wheel in the traditional sense.
Coverage from TeslAnt’s ongoing FSD and Autopilot news tracking shows this is one entry in a long, continuous stream of robotaxi-related developments throughout 2026, from fleet expansions to regulatory reviews to software updates. The fart-mode story will likely fade from headlines within days. The underlying pattern, Tesla scaling a software-dependent commercial service faster than its support and oversight systems can fully account for, is the part worth watching.
Frequently Asked Questions
What exactly happened with the Tesla robotaxi fart mode story?
The San Francisco Standard reported on October 13, 2026, that a Tesla robotaxi became stuck playing fart sound effects through its speakers during a ride, and the onboard safety driver was unable to immediately stop it.
What is Tesla’s “fart mode” officially called?
Tesla calls it Emissions Testing Mode inside its vehicle software. It was introduced as part of a December 2018 holiday update and lets users choose sounds, set volume, target a specific seat, or trigger it by voice or seat contact.
Is this the same as the NHTSA investigation into Tesla robotaxis?
No. The fart-mode incident is a separate story from the NHTSA school-zone speeding review opened on October 9, 2026, which examines allegations involving roughly 1,000 vehicles. The two stories are unrelated beyond both involving Tesla’s robotaxi program during the same month.
How do I contact Tesla if something goes wrong during a Robotaxi ride?
Tesla’s rider guide lists Tesla Robotaxi Support at (877) 798-3752. Riders can also use the vehicle’s touchscreen or the Robotaxi app to request that the car pull over.
Which cities currently have Tesla Robotaxi service?
Tesla’s official support page lists limited service in Miami, Orlando, and Tampa, Florida, and Austin, Dallas, and Houston, Texas. Some reporting describes additional, more limited operation in the San Francisco Bay Area using safety-driver supervision.
How big is Tesla’s robotaxi fleet right now?
Figures vary by source and date. The Los Angeles Times reported just 59 vehicles in June 2026 across three Texas cities, while later reporting on Tesla’s Austin Cybercab rollout described roughly eightfold fleet growth to more than 300 vehicles within 30 days.
Has Tesla’s robotaxi service had other safety incidents?
Reported figures differ by source. The Los Angeles Times cited 17 incidents reported to NHTSA, including two low-speed crashes during remote-employee control, while a separate count put the figure near 18 incidents with 56% attributed to other drivers.
Will Tesla issue a recall over the fart mode glitch?
There is no indication of a recall tied to this incident. The malfunction involved an entertainment feature rather than a safety-critical driving system, so a software patch rather than a formal recall is the more likely outcome based on how Tesla has handled similar non-safety software issues in the past.
