Connect with us

News

SpaceX almost loses Falcon 9 booster at sea

Published

on

After more than a week at sea, the SpaceX Falcon 9 booster responsible for the company’s 100th successful landing finally returned to port on Wednesday, revealing that it nearly toppled into the sea during the recovery process.

Falcon 9 B1069 completed its first launch without issue early on December 21st, carrying a reused Cargo Dragon capsule into space and sending it on its way towards orbit and the International Space Station (ISS). Nine minutes after liftoff, it touched down on drone ship Just Read The Instructions (JRTI) without any apparent issue, more or less hitting the platform’s painted bullseye. While it’s difficult to determine with certainty, B1069 appeared to be in fine condition after landing, standing roughly straight up with all nine Merlin 1D engines well above the drone ship’s deck.

That was decidedly not the case when the once-flown Falcon 9 booster finally sailed into Port Canaveral eight and a half days later.

B1069 after its first landing. (SpaceX)

There remains plenty of ambiguity about how exactly things transpired after the landing but when B1069 was finally within eyeshot, the booster was significantly damaged, riding low on all four legs, inches away from falling off the drone ship’s deck, and only partially attached to the “Octagrabber” robot tasked with securing it. Based on photos of the damaged rocket taken by Teslarati photographer Richard Angle, most or all of B1069’s nine Merlin 1D (M1D) engines suffered likely irreparable damage to their fragile bell nozzles.

From the ragged nature of the damage to those nozzles, it appears that B1069 somehow fell on top of the drone ship’s Octagrabber robot during or after its recovery attempt, as the creases would be far cleaner if the booster had merely landed hard and pressed its M1D nozzles against the deck. But a very short fall onto Octagrabber still doesn’t quite explain the apparent damage to one of the booster’s landing legs or the fact that it’s sitting lower to the deck than usual – both potentially indicative of a hard landing.

Falcon 9 B1069 nearly broke from of the steel I-beam ‘fence’ that surrounds drone ship’s JRTI’s deck. (Richard Angle)

What is clear, though, is that SpaceX struggled to secure the rocket shortly after its first landing. Per the CRS-24 webcast, B1069 landed just shy of dead center. Likely as a result of poor sea conditions, SpaceX was unable to quickly grab the booster with Octagrabber, which uses giant clamps and its own weight to hold Falcon first stages in place. B1069 then clearly slid around drone ship JRTI’s deck at the whim of the ocean. Before SpaceX could secure it, the booster slammed into the side of the drone ship hard enough to partially flatten a steel safety barrier that runs along its port and starboard beams – a barrier specifically put in place to prevent wayward boosters from sliding off the deck.

Thankfully, above all else, there is no obvious reason that SpaceX won’t be able to repair the damage that was wrought. Replacing all nine of B1069’s engines will heavily delay the booster’s return to flight and probably singlehandedly cost SpaceX at least $5-10 million, but that cost is still far less than scrapping it and building a new booster. Aside from that, it’s possible that B1069’s fall will preclude strict customers like NASA or the US military from reusing the booster to launch their payloads, which the booster would have otherwise been a shoo-in for with just a single NASA launch on its record.

B1061.5, December 14th. (Richard Angle)

While CRS-24 and B1069’s dramatic return was SpaceX’s last launch and booster recovery of the year, the company did safely recovery several other boosters sans damage in the days and weeks prior. On December 14th, Falcon 9 B1061 was spotted being craned onto dry land after its fifth launch – NASA’s tiny IXPE X-ray space telescope.

Falcon 9 booster B1067 arrived at Port Canaveral not long after but spent most of the winter holiday sitting on drone ship A Shortfall of Gravitas (ASOG) as many SpaceX employees took a well-deserved break. The thrice-flown booster was ultimately lifted onto the dock and broken over a few days before B1069 finally sailed into port, setting it up for a fourth launch in the very near future.

Ultimately, while the damage B1069 and JRTI’s Octagrabber seemingly suffered are a significant annoyance and will take a good deal of time and money to fix, SpaceX still has ten other operational Falcon 9 boosters ready to support a potentially record-breaking 2022 launch manifest.

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