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

Elon Musk

Elon Musk’s AI Grok Bot can now handle banking while your Tesla FSD handles the road

Elon Musk says Grok Bot can manage your finances through linked bank and investment accounts.

Published

on

By

Concept of SuperGrok Bot handling banking in a Tesla via Grok
Concept of SuperGrok Bot handling banking in a Tesla via Grok

Grok Bot now wants access to your wallet, with SpaceXAI rolling out a new Finance integration for its agent platform that lets users link bank, credit card and investment accounts thereby letting their Bots help manage spending, investments and more. Elon Musk amplified the announcement on X with a short endorsement, “Grok Bot can manage your finances.”

The feature builds on two earlier steps. In early September, Grok gained the ability to answer questions about spending, savings, investments and cash flow using accounts connected through Plaid, starting with users in the U.S. Before that, on August 28, SpaceXAI let Grok Bot buy things online through Link, with users approving every spend request and the Bot receiving a single use card for each payment.

Musk has already shown how far he wants users to push it. In late August, when Tesla investor account Teslaconomics said he was weighing whether to give Grok Bot access to his bank accounts, Musk replied, “Try it out. If Grok Bot messes up, we will make you whole.” That promise goes beyond SpaceXAI’s consumer terms, which make users responsible for what their agents do and generally cap the company’s liability at the greater of fees paid or $100. SpaceXAI’s own documentation recommends requiring approval for purchases and financial transfers.

For Tesla owners, the update lands five days after Tesla brought Grok Bot into its vehicles, letting drivers hand off errands by voice while FSD (Supervised) handles the road. Bot access inside the car is currently limited to SuperGrok Heavy subscribers, though Connectors are open to anyone signed into Grok. With Finance linked, a driver could ask for a spending summary or a check on upcoming bills during the commute.

Grok’s role in the car has grown quickly since Tesla’s Summer Update let it control cabin features by voice. We have been using Grok Bot in our own Tesla for several weeks, and here’s how our latest test went.

Advertisement
-
Continue Reading

Elon Musk

SpaceX just got the green light Starship has waited years for

The FAA has cleared Starship Flight 14, setting up SpaceX’s first orbital attempt on Monday.

Published

on

By

SpaceX has cleared the last regulatory hurdle standing between Starship and its first trip to orbit. The Federal Aviation Administration issued the launch license for Starship Flight 14 late Saturday, keeping the mission on track for liftoff Monday, September 28, from Pad 2 at Starbase, Texas.

The 75 minute launch window opens at 7:15 a.m. Central, and Boca Chica Beach closures are also scheduled for September 29 and 30 as backup dates. This will be Starship’s first revenue generating mission.

The license was the missing piece after SpaceX completed a full wet dress rehearsal with Booster 21 and Ship 41 on September 24. At the time, the company said the flight remained on track pending regulatory approval. Because Flight 14 flies an orbital profile, the FAA had to sign off on a modified license that met its safety, payload and financial responsibility requirements.

Observers combing through the new FAA paperwork also noticed that lightning no longer appears among Starship’s listed launch hazards. If that holds, it matters more for where Starship is headed than for Monday’s attempt. Florida and Louisiana, home to LC-39A and the planned Starbase Louisiana site, see some of the most frequent lightning in the United States.

SpaceX tells the FCC that Starship Flight 14 is going to orbit

Flight 14 is the mission SpaceX has been building toward for months. Ship 41 will carry 26 Starlink V3 satellites, the first operational V3 units to be deployed, and attempt roughly six orbits at about 275 kilometers over a flight lasting just under 10 hours. SpaceX says the ship will only perform its orbital insertion burn after flight controllers confirm enough hardware redundancy remains for the deorbit burn at the end of the mission. Ship 41 is targeting a splashdown in the Pacific west of Chile, while Super Heavy will return to the Gulf of Mexico.

The date carries some symbolism as well. A Monday launch would come 10 years and one day after Elon Musk first presented the Interplanetary Transport System, the design that became Starship, at the International Astronautical Congress in Guadalajara, Mexico.

Advertisement
-

SpaceX has not announced what comes next, but air traffic planning slides reported this week, list Flight 15 no earlier than October 19 and a first Starship launch from LC-39A in Florida no earlier than October 30. Both dates depend on how Monday goes.

Continue Reading

News

SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout

SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.

Published

on

By

US Golden Dome space defense system (Concept render by Grok)

SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.

Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.

USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.

Starlink’s Starshield wins contract with US Space Force

The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.

Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.

The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.

Continue Reading