Connect with us

News

The saga continues with Model X driver involved in Montana crash

Published

on

Mr. Pang is back this time with a second open letter to Tesla

The Tesla Model X driver involved in a Montana crash while using Autopilot is stirring up controversy once again this time asking Tesla Motors to reveal additional details from the incident. It seems that language differences play a large role in this dispute. Acting as his representative, Steven Xu sent us a second open letter Mr. Pang penned to Elon Musk, in which he takes issue with Tesla’s account of the accident. The open letter reads as follows:

Here is the second letter from my friend, Mr.Pang.

To Tesla Team:

It has been weeks since I published the letter. No one has ever tried to contact us and discus about the crash. To fully understand the reason that caused this crash is critical for all tesla drivers. After awhile tesla published a response towards our letter. Most of parts are fit into the story. However there are few points that I would like to point out.

“From this data, we learned that after you engaged Autosteer, your hands were not detected on the steering wheel for over two minutes. This is contrary to the terms of use when first enabling the feature and the visual alert presented you every time Autosteer is activated.”

I admit that my hands were out of steering wheel after I engaged autopilot. The reason that I was doing that is because I put too much faith in this system. I also believe most Tesla driver would do the something when they
engage autopilot including Elon. The problem here is that Tesla had over advertised this feature by calling it “autopilot”. This feature should named “advance driving assistant”. It is possible that Tesla had known accident like this would come sooner or later. Tesla might think that setting up the term by saying “please put hands on steering wheel at all time” would be response free for Tesla.

Advertisement
-

2、 As road conditions became increasingly uncertain, the vehicle again alerted you to put your hands on the wheel.

The road condition was better than fine. Lane mark is absolutely clear. Road is flat and there is no incoming car. No matter what my sight was never out of the road. However everything was happened too fast for me to take control. Everything happened in less than a second.

3、No steering torque was then detected until Autosteer was disabled with an abrupt steering action. Immediately following detection of the first impact, adaptive cruise control was also disabled, the vehicle began to slow, and you applied the brake pedal.

No one should avoid the cause of the malfunction of autopilot feature. Since you start explaining it, I realize that you are implying that some sort of force was applied to the steering wheel by me. I had no idea how Tesla got this clue. There are two points I want to make here. First, my hands were not on the steering wheel. Second no obstacle was on the road to alter the steering wheel direction. The one and the only one that was taking control of this entire vehicle and steering it away from the road is autopilot software itself. Somehow I realize if my hands were on the steering wheel with a force, would Tesla blame me for the collision? To me it looks like that if an accident occur by autopilot, either hands are on or not on the steering wheel, Tesla can always find a way out by saying “abrupt steering action”.

Tesla also claimed that “abrupt steering adaptive cruise control was also disabled, the vehicle began to slow.”

This is nowhere near the truth. The real thing is that vehicle was NEVER attended to slow from hitting the first pole towards the last. It only took about a second to hit 12 wood poles. I believe if it wasn’t me who brake the vehicle it would continued cruising. Mr. Huang was injured severely due to high speed impact.

Advertisement
-

Tesla as a global impact company should respect the truth of every incident. Nothing is more important hand human life. Lying or manipulating towards public about what really happened is unacceptable.

Weeks ago I got contacted by Tesla regarding this accident. Since you cannot find a mandarin translator, we rearranged the call again in four hours. However that was the last time when Tesla tries to contact me. What I am asking is to fully reveal the driving data from the collision. Reliability of Autopilot software matters to hundreds and thousands of Tesla drivers. I wish to know the entire story about what really happened on us on that collision.

Thanks

Sincerely
Mr. Pang

Steven Xu pointed us to comments being made on the Tesla Motors Club forum that seemingly offers Mr. Pang no support at all. In fact, based on those comments, there almost seems to be a cultural bias in play in this situation. One wonders if perhaps things would seem different if they were driving a car in China that only displayed instructions in Mandarin.

Pang’s complaint is very similar to one lodged by a Chinese customer last month whose Tesla crashed on the highway on the way to work. He claimed that the salesman he spoke to before purchasing his car told him specifically that the car could drive itself and proved it by driving with his hands off the wheel during a test drive. Tesla later amended the language it uses to describe its Autopilot system on its Chinese website. It’s possible that same linguistic confusion has a bearing on Mr. Pang’s unfortunate accident.

Advertisement
-

At this point, it seems the matter will be handled by insurance companies and lawyers. Tesla apparently has had no further contact with Pang. Through Steven, Pang says, “Weeks ago I got contacted by Tesla regarding this accident. Since you cannot find a Mandarin translator, we re-arranged the call again in four hours. However, that was the last time when Tesla tries to contact me.

“What I am asking is to fully reveal the driving data from the collision. Reliability of Autopilot software
matters to hundreds and thousands of Tesla drivers. I wish to know the entire story about what really happened on us on that collision.”

"I write about technology and the coming zero emissions revolution."

Advertisement
Comments

News

Tesla Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

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.”

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

Advertisement
-

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.

Continue Reading

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.

Published

on

By

Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX
Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX

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.


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.

Advertisement
-

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.”

Continue Reading

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.

Published

on

By

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.

Advertisement
-

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.

Continue Reading