News
SolarCity Struggles: National Gridlock (Part III)
In this final post within my SolarCity Struggles series I’ll be outlining the additional complexities that surfaced after our local power company, National Grid, got involved.
National Grid-Lock
Having already experienced some delays on my solar project due to architectural redesigns, National Grid jumped into the mix to make things even worse by throwing up one road block after another. There was a conflict of interest for National Grid to assist on the project since we would be shifting more than $170,000 of revenue from them to SolarCity. I’d only see a tiny slice of that by way of my energy savings. Despite many city mandates to be “More Green”, the utility companies clearly have no interest in assisting customers to go solar since it would be counter productive for them.
Roadblock #1
National Grid would not allow “net metering” (where you can re-supply energy through solar power) for two different meters at the same address. SolarCity stepped up and offered to join my two meters and upgrade my panel (from 400A to 600A) in order to support net metering. Accounting issues aside, I agreed to the proposed change and moved forward with yet another site visit that would lead to an engineering redesign.
Roadblock #2
Having (verbally) moved past this, National Grid then reported that the transformer for my area was only capable of handling 23kW of generated power and could not support SolarCity’s proposed 56kW system. This was by the most serious setback since it would require a design that would cut my generation down to 23kW or less. This meant dropping the farm completely and scaling the house from 35kW to 23kW.
A 23kW design called for the front of my house to have solar panels while only a portion of the rear of the house would be retrofitted with panels. This would have looked really odd so we decided to scale back the design to a 18kW system and only include panels on the front of the house.
National Grid informed me that the transformers support between 8 – 12 houses in my area so any neighbors that undergo a solar project will be limited to the remaining 5kW that the transformer can support.
Next Steps
Going from a 56kW to 18kW (a 68% drop in planned production) system will reduce my energy coverage to 32% of my power needs through solar. This is unfortunately the case due to National Grid’s limitation despite my property having enough roof surface to generate 100% of my energy needs.
I will save approximately $56,000 over the next 20 years with this smaller set up, a far departure from the original projected savings of $105,000 but still worth pursuing.
A friendly note from SolarCity arrived on September 1st letting me know that my installation was scheduled for December 8th and 9th because of the magnitude of the project. Considering this 18kW system is a third of what would have been, I couldn’t help but wonder how SolarCity would have handled the original plans. I can’t imagine starting this project in the dead of a New England winter. SolarCity indicated that the project would require 4-6 weeks before the “go live” date which meant I wouldn’t be completing until January 2015. That puts the project at about 10 months from start (initial consultation) to finish and assuming all goes well from here on out.
Summary
SolarCity has made a number of mistakes on this project since the beginning; from improperly sizing the system to not knowing the requirements and restrictions of the local power company; to not following owner requests on layout; to not understanding power generation limits imposed by the power company.
My experience with SolarCity has led me to conclude that they’re not ready for widespread adoption outside of key markets and have a lot of work and learning to do before they will be ready for that next stage of growth.
I truly hope the project moves forward. My next updates will be on the post installation experience which will hopefully take place sometime between now and the end of this year. Stay tuned.
SolarCity Struggles Series – Read from the beginning
Image Source: Sun Powered EVs
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
News
Tesla crosses major Unsupervised Self-Driving milestone
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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.
