Connect with us

News

Tesla owner explains Autopilot behavior at Model X accident scene

[Credit: Privater/YouTube]

Published

on

A Tesla owner recently shared a theory on factors that might have led up to the fatal Model X accident near Mountain View, CA, on March 23. Driving on the same stretch of road on Autopilot, the Tesla owner observed that there were deviations on the street’s markings and repair cuts — things which might have caused the electric car’s sensors to misread the highway’s lanes.

The 36-second clip was uploaded and shared on YouTube by Privater, who included annotations to the video highlighting his observations. At the 0:05-second mark on the clip, the Tesla owner noted that the markings on the road deviated from their original line due to the beginning of a repair cut. Further into the street (0:12 into the clip), Privater noted that the repair cuts in the road became very prominent. This could have confused Autopilot into thinking that it was a lane, especially under the direct glare of the sun.

As the barrier where the fatal Model X accident took place in came into view (0:23 into the video), Privater noted that the section of the road leading up to the crash cushion was marked by solid white lines. As could be seen in the Tesla owner’s clip, the lines were almost wide enough to be a lane, which could have also been misread by Autopilot.

The Tesla owner noted that he had been driving on the same stretch of road on Autopilot for almost two years. During that time, Privater stated that his car had misread the road marks and nearly collided with the crash cushion once or twice. He described his experiences as a response to a comment on his YouTube video.

A Tesla owner suggests a possible explanation for the fatal Model X accident on March 23, 2018. [Credit: Privater/YouTube]

“On the video, my car is on Autopilot. I drive the same section for nearly two years, (and) 99.9% of (the) time, I’m on Autopilot. However, this kind of error only happened to me once or twice. It’s scary enough for me to keep high alert on this intersection,” he wrote.

In an update to its first statement about the fatal Model X accident, Tesla confirmed that the ill-fated electric SUV was on Autopilot when it collided with the highway barrier. According to Tesla, the Model X driver had received several visual warnings and one audible hands-on warning earlier during the drive. The ill-fated electric SUV’s driver had also not placed his hands on the steering wheel for 6 seconds before the fatal accident. Overall, the Model X driver had about 5 seconds and 150 meters of unobstructed view to steer the car away from the highway divider before the collision occurred.

In a statement to Reuters, NTSB spokesman Chris O’Neil expressed the agency’s disagreement about the Elon Musk-led company’s decision to release information about the investigation to the public.

Advertisement
-

“The agency needs the cooperation of Tesla to decode the data the vehicle recorded. In each of our investigations involving a Tesla vehicle, Tesla has been extremely cooperative on assisting with the vehicle data. However, the NTSB is unhappy with the release of investigative information by Tesla,” O’Neil said.

As we noted in a previous report, the Model X crash was so severe because a crash attenuator, a highway safety device designed to absorb the impact of a colliding vehicle, had not been repaired by CalTrans since a 2010 Toyota Prius smashed into the safety device 11 days before the Tesla accident. In a statement to ABC7 News, Caltrans stated that the standard timeline for a crash attenuator’s repair is 7 days or 5 business days after an accident. The safety device’s repairs were delayed, however, due to storms in the area. 

Watch Privater’s Autopilot drive-by in the video below.

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote

AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.

Published

on

By

Starlink D2D direct to device vs Verizon, AT&T (Concept render by Grok)

AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.

The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.

That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.

The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.

Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.

Advertisement
-

SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.

The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.

Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.

Continue Reading

News

Tesla Semi catches fire in California: what we know

Published

on

Credit: KTVU

A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.

The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.

There were no injuries reported.

The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.

However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.

At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.

The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.

The truck’s driver said that the Semi caught fire, but he did not have an explanation.

An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.

Continue Reading

News

Tesla’s ‘Emergency Drive Away’ function gets its first use in the real world

Published

on

Credit: Tesla

Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.

A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.

“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”

Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.

Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.

Tesla constitutes the following situations as reasonable justifications for activating the feature:

  • You face an immediate threat to your life or personal safety.
  • You must leave the area immediately.
  • Exiting the vehicle is unsafe.
  • Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.

After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.

Continue Reading