News
Elon Musk’s Twitter trial delay request denied, but addition of whistleblower complaint gets approval
Elon Musk’s request to delay his trial against Twitter has been denied by a Delaware court. However, Musk’s request to include the claims put forth by whistleblower and former Twitter security chief Peiter “Mudge” Zatko in his countersuit against the social media company has also been approved.
The ruling was outlined by Chancellor Kathaleen McCormick in a letter. With this in mind, Elon Musk has gained a small win and a loss in his initial session with Twitter in court. Musk’s legal team had requested to push the trial back to mid-November, but with the rejection of the request, the trial is still expected to begin on October 17, 2022.
“Defendants’ motion to extend the case schedule is denied… In arguing that trial should be delayed by at least four weeks, Defendants contend that no external deadline creates any urgency. They observe that the merger agreement’s “termination date of October 24, 2022is automatically stayed if litigation is commenced, and debt financing has an outside date of April 25, 2023.”
“They adduce, therefore, that ‘any prejudice to Twitter can be easily mitigated by . . . continu[ing] the trial date.’ But the opposite is true. I previously rejected Defendants’ arguments in response to Twitter’s motion to expedite, making clear that the longer the delay until trial, the greater the risk of irreparable harm to Twitter. Indeed,Twitter has represented that the anticipated risk of harm has materialized over the course of this litigation.
“Twitter ‘has suffered increased employee attrition,’ which ‘undermin[es]the company’s ability to pursue its operations goals. The company has been forced for months to manage under the constrains of a repudiated merger agreement, including Defendants’ continued refusal to provide any consents for matters under the operating covenants. ‘I am convinced that even four weeks’ delay would risk further harm to Twitter too great to justify,” McCormick wrote.
But while Musk’s efforts to delay the trial were unsuccessful, the Tesla CEO’s efforts to augment his countersuit with former Twitter security chief Peiter Zatko’s whistleblower complaint were successful. Zatko had accused Twitter of fraud while also noting that the social media company did not really care to find out how many of its users were spam or fake accounts. Twitter, for its part, has been dismissive of Zatko’s whistleblower complaints.
Twitter lawyers, during their session in a Delaware Chancery court on Tuesday, claimed that Zatko’s accusations do not meet the legal standard to nullify its merger contract with Musk even if they were true. Twitter’s legal team also noted that while Zatko did raise security concerns during his tenure with the company, Twitter investigated the issues internally and found that the security chief’s concerns were “without merit.”
McCormick, however, does not seem to agree with Twitter’s legal team on the issue.
“Defendant’s motion to amend is granted… The newly published Whistleblower Complaint would be grounds in most instances to permit an amendment under the low bar of Rule 15(a). Twitter argues that the amendment would be futile, but their arguments falter against the exceedingly movant-friendly standard of Rule 15(a). I am reticent to say more concerning the merits of the counterclaims at this posture before they have been fully litigated. The world will have to wait for the post-trial decision.
“Twitter also argues that the amendment would be prejudicial to the extent it would expand discovery and extend the case schedule, and Twitter’s arguments to this effect are far more forceful than Twitter’s futility arguments. But that prejudice can be mitigated by cabining additional discovery to the new allegations and maintaining the existing case schedule. So that is what I will do,” McCormick wrote.
Chancellor Kathaleen McCormick’s letter can be viewed below.
Letter Decision Resolving Defendants' Motion for Leave to Amend and Extend Case Schedule (003) by Simon Alvarez on Scribd
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
