News
SpaceX almost loses Falcon 9 booster at sea
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.
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.
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.
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.
Tesla entered two new markets this week by advancing its presence in Latvia (Europe) and officially launching operations in Uruguay (South America), marking a rapid dual-continent expansion.
These moves underscore the company’s strategy to tap into emerging EV markets with supportive policies, renewable energy grids, and growing demand for sustainable transport.
Latvia: Strengthening the Baltic Footprint
In Latvia, Tesla has built on its earlier registration of Tesla Latvia SIA in late 2025 with recent steps toward full operations, including job postings for a service center and representation in Riga. This aligns with broader Baltic expansion following Lithuania’s model of pop-up stores and service centers.
Coming to Latvia https://t.co/XNkQQJ2O6a pic.twitter.com/yS9kpcNky1
— Tesla Europe, Middle East & Africa (@teslaeurope) July 17, 2026
EV penetration in Latvia stands at around 7 percent for BEVs in new passenger car registrations. 2025 data showed 1,602 BEVs out of about 22,500 total, or 7.1 percent, with combined plug-ins nearing 19 percent. Growth has been steady but below the European average, supported by government subsidies and infrastructure development. Tesla models like the Model 3 lead local EV registrations.
Vehicles for the Latvian market will likely be sourced from Gigafactory Berlin or Gigafactory Shanghai. Charging infrastructure is robust for the region as well, with over 400- 2,000 public points, with Tesla Superchargers in Riga, JÅ«rmala, and along Via Baltica routes offering up to 250 kW.
Uruguay: Third South American Country
Tesla teased its Uruguay arrival with “Estamos llegando,” or, “We are arriving,” on social media, followed by an official presentation scheduled for mid-July.
Hola Uruguay 🇺🇾
Nuestros Model 3 y Model Y están cada vez mas cerca! pic.twitter.com/FR41fsA7um
— Tesla Latinoamérica (@Tesla_LatAm) June 30, 2026
The company established Tesla Uruguay SAS, homologated Model 3 and Model Y (three versions each), and appointed local leadership. This makes Uruguay Tesla’s third official South American market after Chile and Colombia.
Uruguay boasts one of Latin America’s highest EV penetrations, with battery-electric vehicles exceeding 20 percent market share recently, driven by tax incentives, high fuel prices, and a nearly 95-100 percent renewable electricity grid. Hundreds of Teslas already operate via grey imports, but official sales bring warranties, service, and support.
Vehicles will be imported from Gigafactory Shanghai, enabling competitive pricing for Model 3 and Model Y. Charging plans include Supercharger development alongside existing infrastructure, leveraging the country’s green energy advantage for affordable operation.
Tesla Superchargers follow Model 3 and Model Y to South American country
Tesla’s Dual Continent Expansion
Tesla’s simultaneous push into Latvia and Uruguay demonstrates efficient scaling: prioritizing service and infrastructure first, then direct sales in high-potential niches. In Europe, it fills Baltic gaps; in Latin America, it counters Chinese dominance while leveraging renewables.
This dual move signals Tesla’s ambition to accelerate global EV adoption amid varying regional paces. By addressing local needs, like subsidies in Latvia or incentives and green grids in Uruguay, Tesla not only boosts volumes but advances its mission of sustainable energy.
For investors and consumers, it highlights resilience and opportunity in diverse markets, potentially paving the way for further growth in underserved regions. With strong fundamentals in both, these entries could yield long-term gains as EV transitions mature worldwide.
SpaceX has announced a new target date for the thirteenth test flight of Starship: Monday, July 20, with the launch window opening at 6:45 p.m ET/5:45 p.m. CT.
This is the first rescheduling attempt of Starship’s 13th test flight. It was set to launch last night, but SpaceX scrubbed the launch attempt.
🚨 SpaceX is now looking at Monday, July 20th at 6:45 p.m ET/5:45 p.m. CT for the 13th test flight of Starship pic.twitter.com/7s8aMJV5Ge
— TESLARATI (@Teslarati) July 17, 2026
CEO Elon Musk revealed that some of the engines on Starship did not start, which automatically triggers a launch abort. Two of the Raptor engines will be removed and replaced.
To be confident of a good flight, 2 Raptors will be removed & replaced. Most probable launch timing is early next week.
— Elon Musk (@elonmusk) July 17, 2026
SpaceX officially announced the new launch window this morning.
Starship’s 13th test launch comes with a few new objectives, but SpaceX does not plan to attempt a catch of the booster, which it has done several times in the past.
For Starship’s Upper Stage, there are some adjustments to ensure engine reusability that will be assessed during the ascent, and 20 operational Starlink V3 satellites are also set to make their way into space. SpaceX also plans to attempt an in-space relight of a single Raptor engine, which is a critical demonstration for future orbital deorbit, refueling, and deep space maneuvers.
Ultimately, it will splash down in the Indian Ocean.
The continuous tests help SpaceX advance the Starship program toward eventual full reusability, operational Starlink V3 deployment, and future missions, which include NASA’s Artemis program.
Elon Musk
SpaceX Starship Flight 13 aborted at Zero and Musk just told us what broke
Four Raptor engines failed to ignite at T-zero, forcing SpaceX to scrub Starship Flight 13 Thursday.
SpaceX scrubbed the Starship Flight 13 launch attempt Thursday evening at the last possible moment, after four of the Super Heavy booster’s 33 Raptor 3 engines failed to ignite during the startup sequence. The 90-minute window had opened at 6:45 p.m. EDT from Starbase in Boca Chica, Texas, and the countdown had proceeded without issue all day, with more than 11.5 million pounds of liquid methane and liquid oxygen being fully loaded into the rocket before the automated abort triggered. SpaceX’s launch directors posted on X, “Standing down from today’s flight test attempt,” and shut down the livestream shortly after.
Musk confirmed the root cause within hours. “Some of the engines didn’t start, triggering an automatic launch abort,” he wrote on X. “To be confident of a good flight, 2 Raptors will be removed and replaced. Most probable launch timing is early next week.” SpaceX engineers began draining propellant tanks immediately and Booster 20 was rolled back to its hangar for inspection.
The timing adds a layer of significance that did not exist during any of the previous 12 Starship flights. This is the first time SpaceX has attempted to launch Starship since the company made its stock market debut in June, listing under ticker SPCX at $135 per share. Public investors are now watching every Starship outcome in real time, and a last-second abort carries more visibility than it would have six months ago.
Flight 13 was designed to be one of the most consequential tests in the program’s history. It was set to carry 20 Starlink V3 satellites, the first operational payload Starship has ever attempted to deploy. Six of those satellites carried external cameras to photograph Starship’s heat shield from the outside during flight, which would act as a self-inspection approach SpaceX has never attempted before. The mission also needed to complete a Raptor engine relight in space, a step SpaceX skipped on Flight 12 in May after losing an engine during ascent. That Flight 12 booster also flipped 90 degrees off course during its boostback burn when five engines failed to reignite.
SpaceX has not announced an official next launch date. Musk’s “early next week” window points to July 21 or 22 at the earliest, pending the engine swap and a return to the pad.
Tesla enters two new markets on two different continents in one week
SpaceX announces new Starship 13 test flight target date
