A former Tesla manager who oversaw the company’s Full Self-Driving test fleet in Houston has filed a wrongful-termination lawsuit, claiming that a single person was expected to monitor 38 vehicles across shifts – a ratio so high it turned the cars into “rolling hazards on public streets.” The suit, filed by Javier Medrano in Houston federal court and first reported by Electrek, alleges that exhaustion directly contributed to a March 2025 collision where Medrano mishandled the emergency call while physically asleep.

The Allegations: 38 Vehicles, One Manager

By mid-2024, Medrano had become the sole operational manager for Tesla’s Houston FSD fleet. When he started, the operation numbered around 15 vehicles and operators. Then Tesla roughly doubled the load to 38 vehicles and operators, all running 24 hours a day in three shifts, according to the complaint.

The filing states that Tesla’s own internal safety benchmark called for a 15-to-1 vehicle-to-manager ratio. In Houston, Medrano was handling 38-to-1. His responsibilities included auditing hours of camera footage, conducting weekly ride-alongs with safety drivers, and investigating any incidents. Doing that for 38 vehicles around the clock, alone, meant corners were inevitably cut, the complaint argues.

Other test cities, Medrano says, had multiple safety leads. Houston had just him. And the drivers themselves were not spared: the lawsuit says they routinely worked 60 to 80 hours a week and remained on call through weekends.

The March 30 Crash and Exhaustion

The complaint ties the staffing shortfall directly to a specific incident. On March 30, 2025, at 2:05 a.m., one of Tesla’s autonomous test vehicles struck a member of the public. According to subsequent reporting by BGR, the Tesla vehicle was sideswiped by another car; the exact cause is not detailed in the lawsuit. Medrano received the emergency call but says he was so sleep-deprived that he “processed the phone call while physically asleep,” gave unsafe guidance, and later had “no recollection” of the exchange. The safety driver remained at the scene for about an hour.

Medrano’s account does not establish fault for the crash, but it places the human oversight component of autonomous-vehicle testing under a harsh spotlight. Even as Tesla works to remove the driver entirely, human supervisors are still critical to its validation process. In this case, the one person responsible for that supervision was, by his own description, incapacitated by exhaustion.

What Tesla’s Own Safety Standard Required

The complaint asserts that Tesla had a mandated 15:1 safety baseline for test-fleet management. If that number is accurate, Houston’s operation was running at more than double the company’s own limit. Medrano says he raised staffing concerns in February 2025 and was given a performance ultimatum instead of additional personnel. He also claims an HR representative suggested he put his phone on “Do Not Disturb” rather than address the understaffing.

Tesla fired Medrano on May 1, 2025 – just days before a stock award was scheduled to vest. The lawsuit says the Autopilot director blamed Medrano for failing to delegate, even though, according to the filing, there was no one available to delegate to. After his termination, Tesla promoted one of Medrano’s subordinates into the role and brought in two additional team leads from Dallas – effectively creating the three-person management structure Medrano had been requesting.

Tesla has not responded to media requests for comment, and none of the claims have been proven in court. Medrano, now working for a rival EV company, is seeking reinstatement, back pay, damages for emotional and financial distress, and litigation costs.

What It Means for Houston Drivers and Tesla Owners

For the public, the most immediate takeaway is that Tesla’s aggressive push to launch a driverless robotaxi service – which debuted in Houston and Dallas in April 2026 – relied on a test-fleet oversight model that a former insider describes as dangerously thin. While the vehicles in the test fleet had human safety drivers, the quality of the data and the safety culture that produced it are now under a legal microscope.

If Medrano’s account is accurate, the understaffing meant fewer hours spent reviewing driver behavior, less rigorous incident investigation, and a higher chance that software bugs or unsafe driving patterns slipped through. That broader concern matters even if you never step into a robotaxi. Tesla uses data from its entire fleet to train and validate its FSD software, which powers semi-autonomous features on millions of consumer vehicles. Validation shortcomings in one city could, in theory, affect system-wide updates.

For everyday drivers in Houston and Dallas, the lawsuit serves as a reminder that autonomous test vehicles operate on public roads under varying degrees of oversight. While robotaxis now carry no human driver, the period leading up to that launch was, by Medrano’s account, less supervised than Tesla’s own rules required.

How Testing Practices Came Under Scrutiny

This lawsuit lands against a backdrop of increasing litigation and regulatory attention on Tesla’s driver-assistance systems. Unlike the more familiar wrongful-death or injury lawsuits that target Autopilot or FSD’s direct performance, this case comes from the inside – from the person Tesla put in charge of keeping the test fleet safe.

The complaint underscores a recurring tension in autonomous-vehicle development: the push to gather miles and validate quickly can outrun the human infrastructure needed to monitor that process. Tesla’s Houston fleet was the foundation for its robotaxi launch in two major Texas cities. If safety oversight was compromised, it could invite regulators to ask harder questions about how self-driving capabilities are proven safe, and whether companies are cutting corners in the race to market.

A pretrial conference is now scheduled for November 19, 2026, according to BGR, at which point the judge and attorneys will discuss next steps and whether the case will proceed.

What You Can Do Now

For Houston and Dallas residents, the practical steps are straightforward:

  • Stay alert around test vehicles. Even if robotaxis are now fully driverless, the aftermath of this suit may mean more scrutiny from regulators. Report any erratic behavior from autonomous vehicles to local authorities and, if you can identify it, Tesla.
  • Know your rights if involved in a collision. Document everything – photos, witness information, and any data from your own vehicle’s cameras. Contact the police and your insurance company immediately.
  • If you own a Tesla with FSD, continue to use the system as instructed: keep your hands on the wheel and remain ready to take over. Monitor software release notes for safety-related improvements. While this lawsuit doesn’t change your immediate day-to-day, it’s a reminder that the software you’re using is trained and validated through processes that are now being challenged.

Beyond individual action, the case may also prompt a wider conversation about labor practices in tech testing. If you work in a field that involves safety-critical monitoring or testing, know your rights regarding overtime and working conditions, and escalate concerns internally or to appropriate agencies if they are ignored.

Outlook: The Road to November 2026

The pretrial conference later this year will determine whether Medrano’s lawsuit moves forward and what evidence both sides must produce. Tesla will eventually have to answer the allegations – or choose to settle. The outcome could influence not only the company’s legal exposure but also public trust in its ability to safely test and deploy autonomous vehicles.

For now, the legal process will provide the next real window into whether Tesla’s Houston operation was an isolated mistake or a symptom of a broader push-to-production culture. As the robotaxi service expands, expect regulators and consumer advocates to watch closely.