Connect with us

News

Tesla Texas Crash: NTSB report says ‘Autosteer not available’ where crash occurred

Credit: Matt Dougherty/Twitter

Published

on

The National Transportation Safety Board has released a preliminary report regarding the Tesla Model S crash in Texas that occurred last month. The NTSB said that testing of an exemplar car at the crash location revealed that Autosteer “was not available on that part of the road.” However, Tesla’s Traffic Aware Cruise Control “could be” engaged by the NTSB during its testing.

The crash occurred on April 17th, 2021, near Spring, Texas. Initial reports indicate that the vehicle was equipped with the capability to operate with Autopilot, Tesla’s advanced driver assistance system. However, Autopilot is not available for utilization on every public road in existence. While mainstream media reports quickly jumped to the conclusion that Autopilot was responsible for the crash after claims that the Model S was “driverless,” the NTSB and NHTSA announced that an investigation would take place to determine whether the vehicle was operating with Autopilot at the time of the crash.

NTSB findings via a security camera at the owner’s home showed that the owner entered the driver’s seat and the passenger entered the front passenger’s seat. ” The video also shows the car slowly entering the roadway and then accelerating down the road away from the camera and out of sight,” the NTSB added.

Tesla alleged “driverless” crash in Texas: What is known so far

The crash was violent, and after colliding with a tree, the Model S caught fire, and both occupants of the vehicle were killed. The vehicle fire was started upon impact with the high-voltage lithium-ion battery case, the report states. The fire destroyed the car, but it was put out in less time than was initially reported. Palmer Buck, Fire Chief for the Woodland Township Fire Department, spoke to the media regarding some reports that the fire raged on for four hours. This was false, and Chief Buck stated that it took two to three minutes for the fire to be extinguished.

However, the main concern of the wreck was whether the vehicle was operating on Autopilot or not. The NTSB tested a very similar “exemplar” vehicle of the Model S that was involved in the crash, and the agency found that it could not be activated where the accident took place.

Advertisement
-

The NTSB wrote explicitly:

“The vehicle was equipped with Autopilot, Tesla’s advanced driver assistance system. Using Autopilot requires both the Traffic Aware Cruise Control and the Autosteer systems to be engaged. 2 NTSB tests of an exemplar car at the crash location showed that Traffic Aware Cruise Control could be engaged but that Autosteer was not available on that part of the road.”

The agency could not recover several elements within the car, including the Onboard Storage Device inside the Infotainment console. However, the car’s restraint module that gives information on vehicle speed, belt status, acceleration, and airbag deployment was recovered but damaged by fire. The restraint control module was taken to the NTSB) recorder laboratory for evaluation, the report states.

The investigation continues, and the NTSB is collecting data to analyze crash dynamics, postmortem toxicology test results, seat belt use, occupant egress, and electric vehicle fires.

The NTSB added:

“All aspects of the crash remain under investigation as the NTSB determines the probable cause, with the intent of issuing safety recommendations to prevent similar crashes. The NTSB is working alongside the Harris County Texas Precinct 4 Constable’s Office, which is conducting a separate, parallel investigation. The National Highway Traffic Safety Administration and Tesla are supporting the NTSB in the investigation.”

Advertisement
-

The NTSB’s preliminary report is available below.

HWY21FH007 Preliminary Report by Joey Klender on Scribd

Joey has been a journalist covering electric mobility at TESLARATI since August 2019. In his spare time, Joey is playing golf, watching MMA, or cheering on any of his favorite sports teams, including the Baltimore Ravens and Orioles, Miami Heat, Washington Capitals, and Penn State Nittany Lions. You can get in touch with joey at joey@teslarati.com. He is also on X @KlenderJoey. If you're looking for great Tesla accessories, check out shop.teslarati.com

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