News
SpaceX attempts second Falcon fairing drop test with a helicopter and Mr. Steven
Following a few days of rest in port, SpaceX fairing recovery vessel Mr. Steven has continued a likely campaign of controlled drop tests with a second fairing recovery attempt, using a helicopter, spotter plane, and support vessel to pick up a Falcon fairing and drop it, theoretically allowing it to paraglide into Mr. Steven’s net.
While it’s nearly impossible to determine what happened without line-of-sight visual confirmation or an official announcement from SpaceX, it appears that Mr. Steven kicked off real catch attempts on October 11th, evidenced by his close interaction with a Blackhawk helicopter over the course of an hour or so. Another similar attempt occurred today, October 17th, and culminated with Mr. Steven returning once more to Port of San Pedro with the same test-focused fairing half on board, albeit not resting in his retracted net.
- SpaceX’s dedicated test fairing seen at Berth 240 on Oct. 15, a few days after its first apparent drop test. (Pauline Acalin)
- Mr. Steven and a recent arrival, barge PTS 185. The fairing cradle on deck suggests that this is probably the platform helicopters grab the fairing half off of. (Pauline Acalin)
After October 11th’s testing was completed, Mr. Steven returned to Port of San Pedro. On October 13th, he was docked at SpaceX’s Berth 240 facilities with net lowered and the test fairing half wrapped up on the docks, preventing confirmation of whether he carried the fairing half back from the testing region. A mid-sized barge also recently appeared at Berth 240 with a distinct Falcon fairing cradle onboard, perhaps explaining the presence of a tugboat (named Sir Richard) a few miles away from where this test campaign has been stationed – a barge would offer a flat, safe surface for a helicopter to hover over and pick up an unwieldy object such as a payload fairing.
Nearly identical to the October 11th test, Mr. Steven, tug Sir Richard, a Cessna chase plane, and a Blackhawk helicopter all converged around 100 miles southwest of Port of Los Angeles around 2pm PDT on October 17th prior to beginning recovery test operations. Mr. Steven and the tug Sir Richard – likely towing a barge being temporarily used to move a fairing half – arrived several hours beforehand at the test’s planned location.
- As of late, SpaceX technicians and engineers have going through quite a range of activities related to fairing recovery. (Pauline Acalin)
- A gif demonstrates just how taut Mr Steven’s net can be, thanks to mechanized rigging. 08/13/18 (Pauline Acalin)
- Mr. Steven returned to Port of San Pedro around 7pm on October 8th after a day spent at sea, apparently with a Falcon fairing half in tow. This is the second known time that a fairing has been in Mr. Steven’s net. (Pauline Acalin)
- One half of SpaceX’s Iridium-6/GRACE-FO just moments before touchdown on the Pacific Ocean. (SpaceX)
Eventually, a UH-60A Blackhawk helicopter – the same helicopter used on October 11 – lifted off from Catalina Island’s Avalon airport, taking about half an hour to reach Mr. Steven and Sir Richard. Once there, the helicopter very distinctly slowed down, eventually hovering just ~20 feet off the surface of the ocean, if not outright landing or perching on the aforementioned barge under the tug’s control. After several minutes in that state, the Blackhawk lifted off and immediately began climbing, reaching a peak of ~11,000 ft before (presumably) dropping its fairing payload and immediately diving down to follow its descent.
It’s undoubtedly an imperfect fit, but the helicopter appeared to follow Mr. Steven very closely over the course of the recovery attempt, sticking just a ~1500 ft or less above and a few hundred feet beside him as he raced to catch the falling fairing half. In fact, at least as a very rough approximation, the helicopter’s descent may be useful to judge the fairing’s behavior while gliding: taking ~14 minutes to travel descend 11,000ft and travel perhaps 2 miles (~10,500ft) horizontally, the fairing would dropped at a reasonable 13.1 feet per second (~4 m/s) once its parafoil opened and seemed to travel approximately one foot forward for every one foot down, also known as a 1:1 glide slope ratio.
And here's a little overview of the helicopter's path, mixed with a speed/altitude graph! Added some rough annotations to give an idea of what happened and in what time frame 😀 pic.twitter.com/e1rwZtkNHA
— Eric Ralph (@13ericralph31) October 18, 2018
Depending on wind conditions, parafoils can nominally be expected to achieve average glide slope ratios between 0 (high winds; falling like a literal rock) and 4 (no winds; almost as good as a bad airplane), meaning that Falcon fairings – judging from tangential data gathered from the helicopter following its descent – fly much like a parafoil, which is to say not great but better than a brick. The trick with parafoil control – which includes tweaking angles of attack and glide slope – lies more in the art of trading forward velocity for vertical velocity (or vice versa) at key moments. Assuming their control mechanisms have enough authority, paragliding fairings could ‘flare’ as they near Mr. Steven’s net, essentially angling upwards to briefly hover before dropping quickly, maybe giving the boat enough time to swoop in and place its net just beneath it.
In this way, a parafoil’s flexible, inflated wing (airfoil, to be precise) can allow it to maneuver quite a lot like a bird, at least more so than most other methods of flying humans have access to. Time will tell if SpaceX is having any luck perfecting the guidance and recovery of Falcon fairings, particularly with this campaign of under-the-radar drop tests. Even if Mr. Steven returns with a fairing half resting in his net, it will be more than a little ambiguous if it was placed there or he caught it, and any certainty will rely on official confirmation from SpaceX itself.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
News
Tesla Cybercab gets crazy change as mass production begins
Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.
Tesla Cybercab has evidently received a pretty crazy change from an aesthetic standpoint, as the company has made the decision to offer an additional finish on the vehicle as mass production is starting.
Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.
VIN Zero—the very first production Cybercab—showcases a vibrant champagne gold exterior with a high-gloss finish, a dramatic departure from the flat, matte-wrapped prototypes that debuted at the 2024 “We, Robot” event.
Presenting VIN Zero — the very first production Cybercab built at Giga Texas. pic.twitter.com/8bXo4CJAlr
— TechOperator (@TechOperator) April 23, 2026
This glossy sheen is a pretty big pivot from what was initially shown by Tesla. The company has maintained a pretty flat tone in terms of anything related to custom colors or finishes.
A specialized clear coat or process delivers the deep, reflective gloss without conventional painting. The result is a premium, mirror-like shine, and it looks pretty good, and gives the compact two-seater a more luxurious and futuristic presence than the subdued matte prototypes.
Photos shared by Tesla community members reveal VIN Zero in a showroom-like setting at Giga Texas, highlighting refined panel gaps, large aero wheel covers, and the signature no-steering-wheel, no-pedals interior optimized for full autonomy.
The open frunk in some images offers a glimpse of practical storage, while the overall build quality appears more polished than that of test mules.
This glossy evolution aligns with Tesla’s broader production ramp. After the first unit in February 2026, the company has shifted to volume manufacturing, with dozens of units already spotted in outbound lots. CEO Elon Musk and the team aim for hundreds per week, paving the way for unsupervised FSD robotaxi networks that could slash ride costs to pennies per mile.
The Cybercab holds Tesla’s grand ambitions of operating a full-service ride-hailing service without any drivers in its grasp. Tesla has yet to solve autonomy, but is well on its way, and although its timelines are usually a bit off, improvements often come through the Over-the-Air updates to the Full Self-Driving suite.
News
Tesla confirms Cybercab with no steering wheel enters production
Tesla has confirmed today that its steering wheel-less and pedal-less Cybercab, the vehicle geared toward launching the company’s autonomous ride-hailing hopes, has officially entered production at its Giga Texas production facility outside of Austin.
The Cybercab is a sleek two-door, two-passenger coupe engineered from the ground up as an electric self-driving vehicle. It features no steering wheel or pedals, relying instead on Tesla’s advanced vision-only Full Self-Driving system powered by multiple cameras and artificial intelligence.
Purpose-built for autonomy
Cybercab in production now at Giga Texas pic.twitter.com/Y9qG3KyWBa
— Tesla (@Tesla) April 23, 2026
The minimalist cabin centers on a large display screen that serves as the primary interface for passengers, creating an open, futuristic space optimized for comfort during unsupervised rides. A compact 35-kilowatt-hour battery pack delivers exceptional efficiency at 5.5 miles per kilowatt-hour, providing an estimated 200-mile range.
Additional innovations include inductive charging compatibility and a lightweight design that enhances aerodynamics and performance.
Production at Giga Texas builds on earlier prototypes and initial units completed earlier in 2026. The facility, already a hub for Model Y and Cybertruck assembly, now ramps up dedicated lines for the Cybercab.
This shift to volume manufacturing reflects Tesla’s strategy to scale affordable autonomous vehicles rapidly.
By focusing on a dedicated platform rather than adapting existing models, the company aims to keep costs low while prioritizing safety and reliability through continuous AI improvements.
The Cybercab’s debut in production carries broad implications for urban mobility. As the cornerstone of Tesla’s Robotaxi network, it promises on-demand, driverless rides that could slash transportation expenses, reduce traffic accidents caused by human error, and lower emissions through its all-electric powertrain.
Accessibility features, such as space for service animals or assistive devices, further broaden its appeal. Regulators and cities worldwide will soon evaluate its deployment, but the vehicle’s design already addresses key hurdles in scaling unsupervised autonomy.
Challenges persist, including full regulatory clearance and building charging infrastructure. Yet this production launch signals momentum. With Cybercabs poised to roll out in increasing numbers, Tesla edges closer to a future where personal ownership meets shared fleets of intelligent vehicles.
The start of Cybercab production is more than just a new vehicle entering mass manufacturing for Tesla, as it’s a signal autonomy is near. Being developed without manual controls is such a massive sign by Tesla that it trusts its progress on Full Self-Driving.
While the development of that suite continues, Tesla is making a clear cut statement that it is prepared to get its fully autonomous vehicle out in public roads as it prepares to revolutionize passenger travel once and for all.
News
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.
Tesla Assisted Smart Summon (ASS) improvements
There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:
“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.
This caused me to sprint across the lot to retrieve the vehicle:
It was pouring when I left the gym so I tried to Summon my Model Y
It turned the opposite way and drove out of range, stopping here and forcing me to walk even further across the lot in the rain for it 🤣
One day pic.twitter.com/iD10c8sriB
— TESLARATI (@Teslarati) April 5, 2026
Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.
It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:
🚨 Tesla FSD v14.3.2 ASS testing part 1
This was a significant improvement than recent tries using ASS. The parking lot was pretty empty but getting it to come to my location in one singular motion and maneuver was encouraging. https://t.co/vF7TS48GGV pic.twitter.com/sYt8tyHgNn
— TESLARATI (@Teslarati) April 23, 2026
Tesla Full Self-Driving v14.3.2 ASS testing part 2 https://t.co/lxfWfnLUxf pic.twitter.com/2R0r3ohI3M
— TESLARATI (@Teslarati) April 23, 2026
I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.
It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.
New Disengagement Categories
This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.
I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.
I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.
I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.
I chose to label this Navigation error as “Critical” while testing FSD v14.3.2
Here’s why:
✅ This intervention wasn’t “preference,” as the maneuver FSD routed was illegal
✅ If a police officer saw this maneuver, it would result in a ticket https://t.co/znhHb4haAo pic.twitter.com/bZOiLwWmQa— TESLARATI (@Teslarati) April 23, 2026
Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.
Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.
Inconsistency with Regional Traffic Patterns
Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.
In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.
🚨 Tesla FSD v14.3.2 attempts the “Except Right Turn” stop sign: https://t.co/W5MjAybaNK pic.twitter.com/P6oeUsk4PN
— TESLARATI (@Teslarati) April 23, 2026
Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.
This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.
Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.
“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”
This could be one of those examples that Tesla just has to figure out.
Highway Operation
Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.
However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:
🚨 Tesla FSD v14.3.2 highway operation: generally happy with the performance here, especially behavior near the exit
Love that the car got over in the right lane after its final pass, and stayed there as the off ramp was approaching https://t.co/qVRVhg6XGR pic.twitter.com/1ELwHf2XKS
— TESLARATI (@Teslarati) April 23, 2026
Better Maneuvering at Stop Signs
Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.
I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.
This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.
FSD seems to have worked through this particular maneuver:
🚨 Tesla FSD v14.3.2 with a singular stop at the correct spot
No double stopping anymore in my experience https://t.co/Wd0TaNjc1R pic.twitter.com/CdQPvJHaAM
— TESLARATI (@Teslarati) April 23, 2026
FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.





