Connect with us

News

SpaceX Falcon 9 launch and landing imminent as drone ship heads to sea

Drone ship OCISLY returned to port on November 15th after a successful Falcon 9 landing. On December 1st, the ship departed for its next booster recovery. (Richard Angle)

Published

7 years ago

on

SpaceX’s next Falcon 9 launch and landing is well into the late stages of preparation, leaving the company approximately 24-48 hours away from its next mission to orbit. To support the surprise ocean landing, a drone ship has already been dispatched and recently departed Port Canaveral.

After a frenetic week of preparation, tugboat Hawk departed with drone ship Of Course I Still Love You (OCISLY) on December 1st, preparing for its second recovery attempt in roughly three weeks and SpaceX’s second drone ship landing after a rare, six-month rocket landing lull. In the days leading up to the anticipated departure, workers could be seen performing a routine procedure often nicknamed a “FOD-walk” in which a given surface is scoured for Foreign Object Debris (FOD). This is most commonly performed on runways (including aircraft carriers) and attempts to mitigate or fully prevent damage from rocks and other small debris.

In the case of Falcon booster landings, the rocket’s Merlin 1D engine exhaust velocity is just shy of 3000 m/s (6700 mph), meaning that a tiny rock or leftover rocket piece could almost immediately become a high-subsonic or supersonic projectile in the seconds before touchdown. The drone ship itself is most at risk, but those theoretical projectiles could potentially bank off the platform’s exhaust shields and hit the booster itself, causing far costlier damage.

And hence the FOD-walk pictured above. Once complete, OCISLY was cleared for departure and has since made it about 75% of the way to its planned landing zone coordinates. SpaceX is currently scheduled to launch Cargo Dragon resupply mission CRS-19 on a Falcon 9 rocket no earlier than 12:51 pm EST (16:51 UTC) on December 4th, although a specific weather condition may delay the instantaneous window by 24 hours. Hawk and OCISLY should thus arrive on station one or two days before launch.

As it turns out, this Falcon 9 landing is a bit of mystery: it’s unclear why exactly SpaceX has decided to land the booster at sea instead of the usual Landing Zone recoveries that have followed most recent Cargo Dragon launches. Typically, the low insertion orbit (~200 km x ~390 km) and relatively low mass of Cargo Dragon (less than 10 tons or 22,000 lb) means that Falcon 9 has (literally) tons of propellant left over, giving it the margins needed to flip around, cancel out a huge amount of horizontal velocity, and boost 100+ km (62+ mi) back to shore.

Instead, new Falcon 9 booster B1058 is scheduled to land aboard drone ship OCISLY some 350 km (220 mi) downrange, an unusual distance. For reference, SpaceX’s May 2019 CRS-17 mission is the only time Falcon 9 has landed at sea after a CRS launch since CRS-8, the rocket’s first successful drone ship recovery. That scenario was forced because LZ-1/2 had coincidently been showered in Crew Dragon debris after C201 exploded during testing. Even then, OCISLY was stationed just 20 or so kilometers offshore, meaning that Falcon 9 B1056 still performed a routine Return To Launch Site (RTLS) landing in spirit.

B1056 returned to port on May 4th after a rare post-CRS drone ship landing. (Teslarati)

In short, the ~350-km-downrange landing plan suggests that this Cargo Dragon launch may have a much smaller propellant margin than essentially every similar mission preceding it. This could be explained in a few ways. Maybe after Falcon 9 B1050’s surprise landing failure, SpaceX decided that all new Falcon 9 boosters will attempt drone ship landings after their first flight, minimizing the risk to Cape Canaveral in the event of a CRS-16 repeat. Another possibility, Crew Dragon capsule C205 – scheduled to support the spacecraft’s In-Flight Abort (IFA) test late this month or early next – may still be close to the Cape’s Landing Zones, another reason to avoid even the slightest chance of a catastrophic Falcon landing failure.

CRS-18’s Falcon 9 upper stage featured an unusual gray finish over its RP-1 propellant tank, said by SpaceX to be a test of its insulation properties.

Finally, it’s also possible that CRS-19 will follow in the footsteps of CRS-18, which sported a prototype Falcon 9 upper stage designed to push the enveloped of its orbital longevity. Falcon 9 B1056 still managed to land at LZ-1 after CRS-18, but a more ambitious follow-on test could potentially require much more propellant, accounting for the drone ship’s position further downrange. With any luck, we’ll find out more later today during SpaceX, NASA, and the US Air Force’s routine pre-launch press conference – stay tuned!

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement
-
-
Related Topics:

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

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

2 hours ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

20 hours ago

on

August 1, 2026

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

21 hours ago

on

August 1, 2026

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading