News
SpaceX schedules second Starship static fire after first test ends prematurely
Update: SpaceX appears to have plans for a second triple-Raptor static fire for Starship SN9 after the rocket’s first test was cut short for unknown reasons.
Identical to previous road closure windows, SpaceX will have an opportunity to test Starship SN9 from 8 am to 5 pm CST (UTC-6) on Friday, January 8th, potentially paving the way for a high-altitude launch attempt early next week if the second static fire goes as planned. Stay tuned for updates!
In what is likely one of the last steps before SpaceX’s next high-altitude Starship launch attempt, the company appeared to successfully put Starship serial number 9 (SN9) through its first triple-Raptor static fire test.
Relatively late into a test window that opened at 8 am CST (UTC-6) but was later pushed to noon, SpaceX’s first Starship SN9 static fire attempt began in earnest around 3:15 pm CST. Signified by venting activity at the propellant farm tasked with preparing and loading liquid oxygen and methane on Starships, slight tweaks in the test flow were observed but the static fire occurred more or less when expected at 4:07 pm.
SN9 ignited all three of its Raptors in quick succession and shut the engines down over the course of 1.5-2 seconds – extremely short relative to all previous nominal Starhopper or Starship-mounted Raptor static fires. Long-time followers immediately noted that small discrepancy, speculating that it could either have been a post-ignition abort or intentionally shortened to avoid damaging the pad’s concrete surface (an incident that’s occurred several times during recent tests).
Not long before the short static fire, SpaceX extended the end of its January 6th test window (in the form of road closure notices) from 5 pm to 8 pm. Oddly, rather than the expected response of detanking Starship and reopening the road after a successful test, SpaceX essentially recycled SN9 and began a separate test around 6 pm. The road was never reopened and a SpaceX team never headed back to the pad between the tests, implying that the company may have run into a minor hardware or software bug earlier in the day.
It’s unclear what the actual goal of the second attempt was and it’s more or less impossible to know for sure with confirmation from CEO Elon Musk. It’s possible – if unlikely – that the first static fire went exactly as planned and the follow-up test was meant to be a simple data-gathering wet dress rehearsal (WDR). Either way, after a surprise downpour briefly engulfed Starship SN9 minutes prior, the second test appeared to abort about 30 minutes into propellant conditioning and loading, precluding both a complete WDR and/or static fire.
According to a test notice received on January 6th by NASASpaceflight contributer and photographer Mary (bocachicagal), SpaceX has another test window available on January 7th in the event that Wednesday’s testing was partially unsuccessful. In a rare case, SpaceX’s hand-distributed warning for residents preceded any additional planned road closures, the last of which lifted on January 6th.
On January 5th, SpaceX received a trio of Temporary Flight Restrictions (TFRs) from the FAA that will allow the company to restrict access to nearby airspace for high-altitude Starship launch attempts on January 8th, 9th, and 10th. Lacking an unequivocally successful static fire, it’s highly unlikely – but not impossible – that Starship will be ready for a launch attempt during any of those three windows. Still, it’s safe to say that SN9 is probably less than a week away from its first flight – expected to be a carbon copy of SN8’s 12.5 km (7.8 mi) launch and landing attempt – if SpaceX can complete a full-duration static fire in the next day or two.
Elon Musk
Tesla confirmed HW3 can’t do Unsupervised FSD but there’s more to the story
Tesla confirmed HW3 vehicles cannot run unsupervised FSD, replacing its free upgrade promise with a discounted trade-in.
Tesla has officially confirmed that early vehicles with its Autopilot Hardware 3 (HW3) will not be capable of unsupervised Full Self-Driving, while extending a path forward for legacy owners through a discounted trade-in program. The announcement came by way of Elon Musk in today’s Tesla Q1 2026 earnings call.
🚨 Our LIVE updates on the Tesla Earnings Call will take place here in a thread 🧵
Follow along below: pic.twitter.com/hzJeBitzJU
— TESLARATI (@Teslarati) April 22, 2026
The history here matters. HW3 launched in April 2019, and Tesla sold Full Self-Driving packages to owners on the understanding that the hardware was sufficient for full autonomy. Some owners paid between $8,000 and $15,000 for FSD during that period. For years, as FSD’s AI models grew more demanding, HW3 vehicles fell progressively further behind, eventually landing on FSD v12.6 in January 2025 while AI4 vehicles moved to v13 and then v14. When Musk acknowledged in January 2025 that HW3 simply could not reach unsupervised operation, and alluded to a difficult hardware retrofit.
The near-term offering is more concrete. Tesla’s head of Autopilot Ashok Elluswamy confirmed on today’s call that a V14-lite will be coming to HW3 vehicles in late June, bringing all the V14 features currently running on AI4 hardware. That is a meaningful software update for owners who have been frozen at v12.6 for over a year, and it represents genuine effort to keep older hardware relevant. Unsupervised FSD for vehicles is now targeted for Q4 2026 at the earliest, with Musk describing it as a gradual, geography-limited rollout.
For HW3 owners, the over-the-air V14-lite update is welcomed, and the discounted trade-in path at least acknowledges an old obligation. What happens next with the trade-in pricing will define how this chapter ultimately gets written. If Tesla prices the hardware path fairly, acknowledges what early adopters are owed, and delivers V14-lite on the June timeline it committed to today, it has a real opportunity to convert one of the longest-running sore subjects among early adopters into a loyalty story.
Elon Musk
Tesla isn’t joking about building Optimus at an industrial scale: Here we go
Tesla’s Optimus factory in Texas targets 10 million robots yearly, with 5.2 million square feet under construction.
Tesla’s Q1 2026 Update Letter, released today, confirms that first generation Optimus production lines are now well underway at its Fremont, California factory, with a pilot line targeting one million robots per year to start. Of bigger note is a shared aerial image of a large piece of land adjacent to Gigafactory Texas, that Tesla has prominently labeled “Optimus factory site preparation.”
Permit documents show Tesla is seeking to add over 5.2 million square feet of new building space to the Giga Texas North Campus by the end of 2026, at an estimated construction investment of $5 billion to $10 billion. The longer term production target for that facility is 10 million Optimus units per year. Giga Texas already sits on 2,500 acres with over 10 million square feet of existing factory floor, and the North Campus expansion is being built to support multiple projects, including the dedicated Optimus factory, the Terafab chip fabrication facility (a joint Tesla/SpaceX/xAI venture), a Cybercab test track, road infrastructure, and supporting facilities.
Credit: TESLA
Texas makes strategic sense beyond the existing infrastructure. The state’s tax structure, lower labor costs relative to California, and the proximity to Tesla’s AI training cluster Cortex 1 and 2, both located at Giga Texas and now totaling over 230,000 H100 equivalent GPUs, means the Optimus software stack and the factory producing the hardware will share the same campus. Tesla’s Q1 report also confirmed completion of the AI5 chip tape out in April, the inference processor designed specifically to power Optimus units in the field.
As Teslarati reported, the Texas facility is intended to house Optimus V4 production at full scale. Musk told the World Economic Forum in January that Tesla plans to sell Optimus to the public by end of 2027 at a price between $20,000 and $30,000, stating, “I think everyone on earth is going to have one and want one.” He has previously pegged long term demand for general purpose humanoid robots at over 20 billion units globally, citing both consumer and industrial use cases.
Tesla (NASDAQ: TSLA) reported its earnings for the first quarter of 2026 on Wednesday afternoon. Here’s what the company reported compared to what Wall Street analysts expected.
The earnings results come after Tesla reported a miss on vehicle deliveries for the first quarter, delivering 358,023 vehicles and building 408,386 cars during the three-month span.
As Tesla transitions more toward AI and sees itself as less of a car company, expectations for deliveries will begin to become less of a central point in the consensus of how the quarter is perceived.
Nevertheless, Tesla is leaning on its strong foundation as a car company to carry forward its AI ambitions. The first quarter is a good ground layer for the rest of the year.
Tesla Q1 2026 Earnings Results
Tesla’s Earnings Results are as follows:
- Non-GAAP EPS –Â $0.41 Reported vs. $0.36 Expected
- Revenues –Â $22.387 billion vs. $22.35 billion Expected
- Free Cash Flow –Â $1.444 billion
- Profit –Â $4.72 billion
Tesla beat analyst expectations, so it will be interesting to see how the stock responds. IN the past, we’ve seen Tesla beat analyst expectations considerably, followed by a sharp drop in stock price.
On the same token, we’ve seen Tesla miss and the stock price go up the following trading session.
Tesla will hold its Q1 2026 Earnings Call in about 90 minutes at 5:30 p.m. on the East Coast. Remarks will be made by CEO Elon Musk and other executives, who will shed some light on the investor questions that we covered earlier this week.
You can stream it below. Additionally, we will be doing our Live Blog on X and Facebook.
Q1 2026 Earnings Call at 4:30pm CT https://t.co/pkYIaGJ32y
— Tesla (@Tesla) April 22, 2026
Tesla confirmed HW3 can’t do Unsupervised FSD but there’s more to the story
Tesla isn’t joking about building Optimus at an industrial scale: Here we go
