News
Do autonomous cars make us worse drivers?
Autonomous cars are coming. So is the first fatality associated with them. Statistically, that milestone should occur in the next 18 months. What will happen then?
On May 31, 2009, an Airbus 330 on its way from Rio de Janiero to Paris plunged from an altitude of 35,000 feet into the Atlantic, killing all 228 people on board. Just prior to the crash, the airplane was operating in autopilot mode. A reconstruction of the disaster revealed input from several sensors had been compromised by ice that caused them to give false readings. Updated sensors that were less susceptible to ice accumulation were waiting to be installed after the plane arrived in Paris.
Because of the false readings the autopilot system disengaged returning control to the pilots however the senior pilot was sleeping at the time. The two junior pilots were not as highly trained in high altitude flight as they might have been, partly because the use of machines to control aircraft under those conditions was the norm.
Faced with the unexpected, the pilots behaved poorly. At one point they are heard to say on the cockpit recorder, “We completely lost control of the airplane, and we don’t understand anything! We tried everything!” While they tried to rouse the sleeping senior pilot, the nose of the aircraft climbed until a stall was induced. Stall is the point at which the wings become barn doors instead of airfoils. The Airbus 330 dropped from the sky like a rock.
In his excellent story about the crash published on Vanity Fair, William Langewiesche offered this conclusion: “Automation has made it more and more unlikely that ordinary airline pilots will ever have to face a raw crisis in flight—but also more and more unlikely that they will be able to cope with such a crisis if one arises.”
The Tesla community has seen similar instances lately. The driver in Salt Lake City who accidentally activated Summon, causing his car to drive into the back of a truck. The woman on a freeway in California who rear ended a car that suddenly slowed in front of her. The man in Europe who crashed into the back of a van that had stalled in the high speed lane of a highway. He at least had the courage to admit his error. “Yes, I could have reacted sooner, but when the car slows down correctly 1,000 times, you trust it to do it the next time to. My bad.”
After each of these incidents, the tendency has been for many to defend the machine and blame the human. But in a recent article for The Guardian, author Martin Robbins says, “Combine an autopilot with a good driver, and you get an autopilot with, if not a bad driver, at least not such a good one.” He says that statistically, the time when a car operating in autonomous mode causes a fatality is rapidly approaching.
On average, a person is killed in a traffic accident in the United States once every 100 million miles. Elon Musk says Tesla’s Autopilot is half as likely to be involved in a collision as a human driver. That would suggest that somewhere around the 200 million mile mark someone will die as a result of an automobile driven by a machine.
Tesla has already passed the 100 million mile mark for cars driving in Autopilot mode and continues to log 2.6 million miles driven per day. Statistically speaking, the time when a self driving car kills somebody is rapidly approaching. And since most autonomous cars on the road are Teslas, the odds are excellent it will be a Tesla that is involved in that first fatality.
What will happen then? Robbins goes back in history to look for an answer to that question. In 1896, Bridgit Driscoll became the first person in England to be killed by a motor car. The reaction among the public and the press was a fatalistic acceptance that progress will have a price. Within a few years, the speed limit in England was raised from 8 mph — which is was when Ms. Driscoll was killed — to 20 mph. This despite the fact that thousands of road deaths were being recorded on English roads by then.
Regulators around the world are racing to catch up with the explosion of new autonomous driving technology. But Robbins concludes, “By the time they do, it’s likely that the technology will already be an accepted fact of life, its safety taken for granted by consumers, its failures written off as the fault of its error-prone human masters.”
The point is that injuries and fatalities will continue to occur as cars come to rely more and more on machines for routine driving chores. But in that transition period between now and the time when Level 4 autonomy becomes the norm — the day when cars come from the factory with no way for humans to control them directly — we need to accept that complacency and an inflated belief in the power of machines to protect us from harm may actually render us less competent behind the wheel.
We will need to remain vigilant, if for no other reason than telling a jury “It’s not my fault! The machine failed!” is not going to insulate us from the legal requirement to operate our private automobiles in a safe and prudent manner.
News
Tesla Full Self-Driving release in the EU gets delayed
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.
News
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.
SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.
A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.
Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.
Launch rehearsal complete ahead of Starship Flight 14 pic.twitter.com/h5LBYyBqi4
— SpaceX (@SpaceX) September 24, 2026
Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.
Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.
The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.
Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”
Elon Musk
Google just picked SpaceX for its first step into orbital AI
Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.
Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.
The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.
The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.
MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.
SpaceX and Google mull massive partnership on Musk’s orbital data dream: report
Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.
The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.
Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”
Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.
