The United Auto Workers union, sixteen states, and four environmental groups recently filed lawsuits against the United States Postal Service (USPS). The groups aim to stop the Postal Service’s plan to purchase and produce gas-powered delivery vehicles to update its fleet.
Background
The USPS announced it would spend up to $11.3 billion on up to 165,000 gas-powered NGDVs. The Biden Administration urged the Postal Service to reconsider its plans. President Biden had ordered federal agencies to phase out the purchase of gas-powered vehicles, and the USPS makes up a third of the U.S. government fleet.
In March, the USPS received criticism from U.S. lawmakers in the House Oversight Committee for its gas-powered Next Generation Delivery Vehicles (NGDV). The Committee sent a letter to the USPS Inspector General requesting an investigation into the agency’s NGDV order. According to the Committee’s letter, the Environmental Protection Agency (EPA), the White House Council for Environmental Quality (CEQ), and numerous environmental stakeholders were concerned that the USPA did not meet NEPA obligations with its gas-powered NGDV fleet.
The USPS responded to EPA feedback with a record of decision (ROD), which outlined the Postal Service’s decision to purchase and deploy 50,000 to 165,000 NGDVs over the next ten years. The agency stated that the NGDV fleet would be a mix of ICE and battery electric delivery vans. Electric vehicles would make up at least 10% of the agency’s fleet. However, the Postal Service also determined that ICE NGDVs were the “most achievable” replacements for its existing fleet.
USPS Lawsuits by States
As per Reuters, sixteen states, led by New York and California, filed a lawsuit against the USPS for its flawed and unlawful environmental analysis of the NGDV program. The lawsuit also accuses the Postal Service of signing the contracts to purchase the gas-powered NGDV before completing a draft environmental review.
According to the CEQ, the Postal Service’s final review for the NGDV program was “flawed in some ways that cannot be so easily remedied.” For example, USPS estimated that the gas-powered NGDVs would get 29.9 miles per gallon, but the EPA discovered that the vehicles would only get 14.7 miles per gallon or less.
UAW and NRDC Lawsuit
Besides the states lawsuit, the UAW filed a joint lawsuit with the Natural Resources Defense Council (NRDC), claiming the USPS “failed on multiple levels” when it evaluated and finalized the contract for the NGDVs. The two parties demand that the agency stop producing the next-generation delivery vehicles. As per the complaint, the UAW and NRDC stated that the NGDV contract is “based on an unlawfully deficient environmental analysis issued after the Postal Service had already decided on a course of action.”
The two parties also criticized the agency’s Environmental Impact Statement (EIS). The UAW and NRDC claim that the Postal Service did not consider the impact NGDV production — opposed to the operation — would have on the local environment. The EIS did not disclose that the vehicles would be produced in South Carolina by Oshkosh Defense, a Wisconsin-based contractor.
“With this contract, USPS and Oshkosh Defense abandoned the Wisconsin workers that built the company and failed taxpayers with a sham process to evaluate the environmental and community impacts of these vehicles. The USPS’s Next Generation Delivery Vehicle is an opportunity for the Biden administration to reverse-court and make real investments in both a cleaner future and good union jobs The contract as it currently stands fails on both accounts. It’s time to halt production and start the procurement process over,” said Ray Curry, president of the United Auto Workers.
The Teslarati team would appreciate hearing from you. If you have any tips, reach out to me at maria@teslarati.com or via Twitter @Writer_01001101.
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 has expanded its Robotaxi program in Florida to include two new cities: Tampa and Orlando.
This marks the second and third cities to be added to the company’s available locations for autonomous ride-hailing in the Sunshine State, joining Miami, which was the first Florida city to offer Robotaxi rides.
Tesla announced the addition of Orlando and Tampa to the Robotaxi program on Tuesday morning. The cities now join Austin, Dallas, Houston, Miami, and the San Francisco Bay Area as locations where Tesla can operate its Robotaxi platform:
Robotaxi now in Tampa & Orlando! pic.twitter.com/fYtmXgJq3O
— Tesla Robotaxi (@robotaxi) July 21, 2026
These rides are unsupervised, as AI Head Ashok Elluswamy confirmed the suite in Florida is operating without safety drivers or anyone within the cabin to assist with operation.
Orlando Tesla Robotaxi Operation
The geofence in Orlando covers a prominent irregular shaded zone on the map, roughly 4-6 miles across in key dimensions, so it likely measures somewhere between 25 and 45 square miles, which is comparable to other early Tesla launches in other cities.
It encompasses central and southern areas bounded by major highways including SR-417 and SR-528, including parts of the Orlando metro core, tourism-adjacent zones, and residential/commercial districts. This represents an initial targeted rollout in a tourist-heavy region, positioned for quick expansion via Tesla’s software updates.
Tampa Tesla Robotaxi Operation
In Tampa, the shape of the geofence is a shaded polygon covering key neighborhoods, explicitly including West Tampa, Tampa Heights, Hyde Park, and downtown Tampa proper, with boundaries along major roads and the Hillsborough River area.
This focuses on high-demand central zones and will offer tourists and citygoers rides without drivers.
Robotaxi Progress
Tesla has been operating Robotaxi since last June, when it launched in Austin. The geofences in most regions have already expanded several times since their launch last year, but the bigger complaint is vehicle availability. Tesla has been working to add more Robotaxi-enabled vehicles to its fleet.
The company still plans to utilize its Cybercab, a new vehicle that is being produced at Gigafactory Texas, for the Robotaxi suite alongside the Model Y, which has been the vehicle of choice for Tesla with early operations.
News
Tesla’s AI Chief just hinted at something big for FSD v14 lite owners
Tesla’s AI chief suggests the newest FSD v14 Lite build may finally go wide release.
Tesla’s head of AI, Ashok Elluswamy, noted on Sunday that the newest FSD v14 Lite build rolling out to Hardware 3 cars is likely the version that goes to wide release, the strongest signal yet that Tesla is near to closing out an early access phase that Hardware 3 owners have waited more than a year for.
Elluswamy made the comment in response to an extensive review from Tesla owner Zack, known on X as @BLKMDL3, who tested software version 2026.20.6.10 and detailed the changes in a lengthy post. “FSD v14 Lite (for Tesla AI3 hardware vehicles) review.
The update restarts a rollout that had stalled after its initial release. Tesla began pushing FSD v14 Lite to Hardware 3 early access drivers on June 29, bringing driving behavior learned on the newer Hardware 4 computer down to the more limited chip that has powered Tesla vehicles built between 2019 and early 2023. That release, as we covered in detail, gave roughly 4 million HW3 vehicles their first meaningful update since being frozen on version 12.6 in early 2025.
Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features
The latest build adds features that bring Hardware 3 closer in line with what Hardware 4 owners already have. FSD can now start directly from park without a brake pedal confirmation, a change Zack called a small but meaningful quality of life improvement. The interface also picks up the blue “P” park icon, approaching destination alerts, and a dedicated Self-Driving app with streak tracking, all details previously exclusive to the AI4 branch of v14, as outlined in Tesla’s original release notes.
The stakes around Hardware 3 go beyond software polish. Tesla sold the Full Self-Driving package for years on the promise that every vehicle equipped with it had the hardware needed to eventually drive itself without supervision. That promise broke down during Tesla’s Q1 2026 earnings call, when Musk acknowledged HW3 cars could not run unsupervised FSD, prompting Tesla to offer trade-in discounts and hardware retrofits alongside the Lite software track.
Tesla confirmed HW3 can’t do Unsupervised FSD but there’s more to the story
Tesla has continued to frame v14 Lite as the primary path forward for the HW3 fleet, telling owners in April that international markets would follow the U.S. rollout once regulatory approvals came through. For now, HW3 owners in the early access group are the only ones running the new build. A broader rollout would mark the second major software delivery to the legacy fleet since Tesla first released FSD v14 to Hardware 4 vehicles, and the first sign since June that the Lite program is still moving rather than stuck in early access limbo.
Tesla’s reason for Starlink integration on Cybercab might surprise you
Tesla Robotaxi program expands in Florida to two new cities
