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!
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
