News
SpaceX Falcon 9 launch up next after ULA spy satellite mission hits snag
On Wednesday, November 3, a United Launch Alliance (ULA) Atlas V 531 rocket was set to launch the NROL-101 mission – a classified payload for the National Reconnaissance Office (NRO) of the United States government – from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station. At neighboring Space Launch Complex 40 (SLC-40) a SpaceX Falcon 9 stood ready and waiting to launch a US military GPS satellite just a day later.
Ultimately, due to an anomaly with launchpad ground support equipment, the ULA launch attempt of the Atlas V NROL-101 mission was scrubbed Wednesday evening. Admittedly, the weather did not look promising either with ground winds remaining a concern throughout the countdown window.
With an hour and forty-seven minutes to go – just five seconds after a planned fifteen-minute hold was released – the launch teams announced that an anomaly had been discovered with “a ground valve issue with the liquid oxygen system for the Atlas V first stage.” The discovery initiated an immediate stop to the countdown and launch teams entered into an unplanned hold that would delay the targeted launch time.
At first, ULA conducted remote troubleshooting, but the anomaly was not remedied and a return-to-pad team would be required to enter the secured launchpad to physically investigate.
An anomaly team was deployed to investigate the valve that was restricting the flow of liquid oxygen (LOx) to the first stage of the Atlas V rocket. The hold remained for over an hour allowing the propellant lines to warm to a temperature that would be needed to be re-cooled prior to resuming the countdown.
Eventually, the return-to-pad team was able to evacuate the pad securing it for launch once again. Chill-down procedures to return the propellant lines back to an operational temperature began but were halted almost immediately. The anomaly had not been completely rectified and not enough time remained in the launch window to re-address it and re-chill the propellant lines. This led to the scrubbed launch attempt.
Typically, a scrubbed ULA mission for the NRO means that a neighboring SpaceX mission has to wait until the problem is fixed and ULA gets its rocket off of the nearby launchpad. However, that was not the case with Wednesday’s scrub. ULA stood down for a 48 hour recycle – rather than a typical 24 hour recycle – to attempt to launch the Atlas V 531 again on Friday, November 6.
This cleared the way for SpaceX to keep its targeted launch date of Thursday, November 5 during a launch window that extends approximately fifteen minutes from 6:24 – 6:39 p.m. EST (2324-2339 UTC) from SLC-40.
Following a successful static fire test of all nine Merlin 1D engines, SpaceX will attempt to launch the GPSIII-SV04 satellite for the United States military for a second time on Thursday, November 5.
The previous launch attempt on Friday, October 2 was thwarted at T-2 seconds due to anomalous engine start-up behavior. The unexplained early start-up of two Merlin 1D engines was eventually determined to be caused by “unexpected pressure rise in the turbomachinery gas generator” as explained by SpaceX CEO Elon Musk.
The engine anomaly prompted a thorough investigation of all Merlin 1D engines on the launch vehicle, as well as, a thorough investigation of the engines on two Falcon 9 launch vehicles designated for future NASA missions – the first operational rotation mission of the Commercial Crew Program, Crew-1, and the launch of the NASA and European Space Agency Earth-observation satellite, the Micheal Freilich Sentinel-6. Engines were eventually replaced on all three Falcon 9 launch vehicles.
A live hosted webcast of Thursday’s launch attempt will be provided on the company website and is expected to be available for viewing approximately fifteen minuted before liftoff.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
