Tesla’s Autopilot probe being carried out by the National Highway Traffic Safety Administration (NHTSA) has expanded following a Model 3 crash in Orlando, Florida, that occurred last weekend.
In mid-August, the NHTSA launched an investigation involving eleven instances of Tesla electric cars crashing into emergency vehicles. The vehicles were operating on Autopilot, according to the investigations, but there is some evidence that some vehicles involved in the eleven accidents were not being properly operated under Tesla’s Autopilot operational standards, which require drivers to remain in control of the vehicle. Two of the accidents resulted in arrests for driving under the influence of alcohol, while another driver was operating the car on a suspended license.
Nevertheless, the NHTSA has made it clear that it will investigate each of these instances to determine whether the Level 2 ADAS system was responsible for the accidents. All four currently available Tesla models are under investigation: Model 3s from 2017-2021, Model S vehicles from 2014-2021, Model X vehicles from 2015-2021, and Model Ys from 2019-2021.
The investigation is now expanding from eleven to twelve accidents after a motorist struck a Florida Highway Patrol vehicle during the early morning hours of Saturday, August 28th. The Highway Patrol officer was pulled over on the side of the road to assist a disabled vehicle, but his car was struck by a Model 3 operating on Autopilot. The driver stated the vehicle was utilizing Autopilot at the time of the accident.
The driver of the Model 3 and the occupant of the disabled vehicle were both reported as having minor injuries. The FHP officer was unharmed.
NHTSA launches Tesla Autopilot investigation over crashes with emergency vehicles
A new letter released this morning and obtained by Teslarati indicates that the Orlando accident is the most recent addition to the Autopilot investigation. An accident in San Diego that occurred on July 10th is the second-most recent occurrence.
The NHTSA writes in the letter to Tesla Field Quality Director Eddie Gates:
“This letter is to inform you that the Office of Defects Investigation (ODI) of the National Highway Traffic Safety Administration (NHTSA) has opened a Preliminary Evaluation (PE21-020) to investigate crashes involving first responder scenes and vehicles manufactured by Tesla, Inc. (Tesla) that were operating in either Autopilot or Traffic Aware Cruise Control leading up to the incident, and to request certain information.
This office is aware of twelve incidents where a Tesla vehicle operating in either Autopilot or Traffic Aware Cruise Control struck first responder vehicles / scenes, leading to injuries and vehicle damage. In each case, NHTSA has reviewed the incidents with Tesla. A list of the twelve incidents has been included for reference.”
The NHTSA is requesting significant information regarding each of the vehicles involved in the twelve incidents, including: Vehicle identification number (VIN); b. Model; c. Model Year; d. Subject component trade / trim name, part number and design version installed as original equipment; including: Software version; Firmware version; Hardware version; Date of manufacture; Date warranty coverage commenced; Date and mileage at which the “Full Self Driving” (FSD) option was enabled; The State in the United States where the vehicle was originally sold or leased (or delivered for sale or lease); Latest known vehicle mileage and commensurate date; Cumulative mileage covered with the subject system engaged; and Date and identities of the most recent software, firmware, and hardware updates.
Tesla is required to respond with the information by Friday, October 22nd, 2021, or it could have fines of up to nearly $115 million.
What do you think? Let us know in the comments below, or be sure to email me at joey@teslarati.com or on Twitter @KlenderJoey.
News
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.