News
SpaceX uses robot dog to inspect Starship after first engine test in months
SpaceX’s first orbital-class Starship prototype has survived the first of several expected Raptor tests, kicking off an engine test campaign that could mark a number of new milestones.
With just 20 minutes left in a seven-hour test window, Starship prototype S20 (Ship 20) appeared to either unsuccessfully attempt its first Raptor static fire test or complete its first intentional Raptor preburner test around 11:40 pm CDT (UTC-5) on Monday, October 18th. Rather than a violent jolt and roar kicking up a cloud of dust, Ship 20 came to life with a (relatively) gentle fireball that lasted for several seconds.
In pursuit of maximum efficiency, Starship’s Raptors require two separate closed-cycle gas generators known as preburners to – as the name suggests – turn its cryogenic (very cold) liquid oxygen and methane propellant into a hot gas mixture that the engine re-ignites to produce thrust. A preburner test, if that’s what Starship S20 completed on Monday night, thus involves activating only the first half of that equation, rapidly producing a giant cloud of flammable gas without actually igniting to produce meaningful thrust.
Preburner tests have become increasingly rare as SpaceX’s sea-level Raptor design matured over the course of tens of thousands of seconds of ground testing and, later, thousands of seconds of ground and flight testing on Starship prototypes. Starship S20 had two engines during its first test. One Raptor was the sea-level optimized variant SpaceX has built dozens of and fired for 30,000+ seconds on the ground. The other, however, was a vacuum-optimized Raptor with a much larger nozzle – the first of its kind to participate in any kind of test while installed on a Starship prototype.
It’s possible that Raptor Vacuum (RVac) engines have even more design tweaks outside of their larger expansion nozzles. Regardless, SpaceX has only built and tested around 10 RVac prototypes over the last year, making it a less mature engine than its sea-level cousins. That could explain why SpaceX appears to have chosen to perform a preburner test first instead of jumping straight into a wet dress rehearsal and static fire. That also means that October 18th’s test was likely the first time a Raptor Vacuum engine has (partially) ignited while installed on a Starship.
The above view from a uniquely situated LabPadre camera all but guarantees that Starship S20’s first engine test was a Raptor Vacuum preburner test and doesn’t offer any strong evidence that it was a two-engine test. Ship 20 still has a number of crucial tests ahead of it before SpaceX can even begin to consider it (or its general design) qualified for flight. That includes multiple static fires, including the first side-by-side static fire of two Raptor variants (RVac and Raptor Center), the first simultaneous static fire of more than three engines, and the first Starship static fire with a full six engines installed.
Ship 20’s preburner test is SpaceX’s first Starbase Raptor test since the first Super Heavy booster static fire in mid-July, almost exactly three months ago.


With any luck, S20’s first preburner test has opened the door for an inaugural static fire of one or both installed engines later this week. However, during that preburner test, the giant fireball Raptor Vacuum emitted appeared to ignite several pieces of pad hardware. SpaceX took advantage of one of at least two Boston Dynamics Spot robots on-site to physically walk a camera up to the active pad and inspect several secondary fires. Ultimately, SpaceX appears to have successfully safed Starship with no damage to the vehicle itself, but odds are good that the sources of those secondary fires will need to be fixed and any pad damage repaired before Ship 20 proceeds into static fire testing. SpaceX has two more 5pm-12am test windows scheduled on October 19th and 20th.
Lifestyle
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
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.
News
Tesla Roadster event gets delayed due to unfavorable weather
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