Connect with us

News

SpaceX grapples with failed Falcon 9 landing as Starlink launches slip

Late Falcon 9 booster B1059's failed Starlink-19 landing appears to have delayed all of SpaceX's near-term launch plans. (Richard Angle)

Published

on

The follow-on effects of SpaceX’s failed February 15th booster landing have begun to roll in, triggering at least one to two weeks of delays for several upcoming Starlink launches.

Already delayed a few days and leapfrogging an even more beleaguered Starlink-17 launch originally scheduled as far back as late January, SpaceX Falcon 9 booster B1059 lifted off for the sixth time without issue last Monday. The rocket seemed to perform fine, separating as planned around 150 seconds after launch and leaving Falcon 9’s expendable upper stage to continue on its way to orbit with a ~16-ton (~35,000 lb) batch of 60 Starlink satellites.

During B1059’s “reentry burn,” a period where Falcon boosters reignite three of their Merlin 1D engines to both slow down and create a sort of shield with the rocket exhaust that burn produces, something went wrong. Unusual sparks quite literally flew during and after the last few seconds of the burn and the bright flare produced by Falcon 9’s engines dissipated far slower than usual. Eventually, when B1059 was expected to fire up for one final landing burn, all that was visible from a live camera on SpaceX’s drone ship was two flashes of warm light.

It’s hard to say for sure without an official comment from SpaceX but those flashes may have been the drone ship camera capturing the mid-air breakup and fast-fire (or explosion) of the Falcon 9 booster some 20-30 seconds before a planned soft landing. The odd behavior observed during and after the reentry burn could have also indicated a partial loss of thrust in one or more of B1059’s three reentry engines.

Unofficial analysis of the telemetry data included in SpaceX’s public webcasts more or less aligns with that theory, suggesting that Falcon 9 B1059 reentry burn lasted a nominal duration but didn’t slow the rocket down as much as it should have. As a result, B1059 would have been traveling faster and at a lower altitude relative to a nominal Starlink mission, which is exactly what’s observed in a comparison between Starlink-18 and Starlink-19, virtually identical launches completed 11 days apart.

That same telemetry also suggests that Falcon 9 B1059 may have lost thrust before its first burn completed, possibly explaining why the timing of launch events on SpaceX’s webcast and an official SpaceX.com launch timeline began to drastically diverge after MECO. MECO itself occurred about five seconds behind that schedule, gradually ballooning to a difference of more than half a minute for Starlink satellite deployment an hour after launch.

That observation increases the similarity between Starlink-5 and Starlink-19, both of which seemingly suffered a boost phase anomaly, off-nominal reentry burn performance, and booster loss well before landing. SpaceX’s Starlink-5 engine-out anomaly and failed booster landing grounded the company for about five weeks before it eventually returned to flight on April 22nd, 2020.

SpaceX appears to be working to mitigate the impact from Starlink-19 but a delay of at least 1-2 weeks is in order based on current schedules. Perhaps the most chronically delayed SpaceX launch of all time, Starlink-17 – originally scheduled to fly as early as “Jan. 29, Jan. 30, Jan. 31, Feb. 1, Feb. 2, Feb. 4, Feb. 5, Feb. 7, Feb. 17,” and Feb. 25 – is now on the calendar for no earlier than (NET) February 28th. Starlink-20, planned to launch in the last week of February, has been tentatively pushed to no earlier than March 7th. Both dates are assuredly subject – and likely – to change as SpaceX works to close out its Starlink-19 anomaly investigation and implement any necessary changes.

Advertisement
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

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 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.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

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.”

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.

Continue Reading

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.

Published

on

By

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.

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.

Continue Reading