News
SpaceX’s Mr. Steven returns with Falcon fairing half in net after drop test practice
Captured in a series of photos taken by Teslarati photographers Pauline Acalin and Tom Cross over several days, SpaceX Falcon fairing recovery vessel Mr. Steven and recovery technicians and engineers have been preparing and practicing for a campaign of controlled fairing drop tests.
By using a helicopter to lift and drop a fairing into Mr. Steven’s net, SpaceX will be able to gather an unprecedented amount of data and control far more variables that might impact the success of recoveries. If the fairing is not destroyed in the process, this test series could be as long-lived as SpaceX’s Grasshopper program, used to work the largest up-front kinks out of Falcon 9 booster recovery.
Mr Steven looks ready. Should be leaving port at some point today ahead of SAOCOM-1A launch scheduled for Sunday, Oct 7, 7:21pm PT #mrsteven #SpaceX pic.twitter.com/Hk7HLmMDra
— Pauline Acalin (@w00ki33) October 6, 2018
Although SpaceX technicians managed to reassemble and install Mr. Steven’s net and arm fairing recovery mechanisms in just a handful of days, finishing less than 48 hours before the West Coast launch of SAOCOM 1A, the ship remained in port for the mission, passing up its fifth opportunity to attempt recovery of one of Falcon 9’s two fairings halves. Why exactly Mr. Steven never left port is unclear and unconfirmed, although SpaceX did mention that recovery would not be attempted this time around during its official launch webcast.
The most likely explanation is mundane – sea states with average swells as large as 4m (13ft) were forecasted (and later recorded) at and around the optimal fairing recovery zone. As a Fast Supply Vessel (FSV) explicitly designed to rapidly and reliably resupply oil rigs and other maritime work areas almost regardless of weather conditions, 4m waves would normally be a tiny pittance for ships as large and heavy as Mr. Steven and would be a nonsensical reason to halt deep-sea operations.
- Thanks to their relatively high angle of attack, Mr. Steven’s newest arms should not seriously impact his stability, but there is a chance that they limit his operational envelope in high sea-states. (Chuck Bennett)
- Mr. Steven seen listing roughly 5 degrees to port during arm installation, July 10th. (Pauline Acalin)
- A few-degree list seen during fairing recovery practice, August 13th. (Pauline Acalin)
On the other hand, Mr. Steven is without a doubt the most unusual FSV in existence thanks to his massive arms and net, stretching at least 60m by 60m. Based on photos of the arm installation process, significant lists of 5+ degrees are not uncommon when arms are unbalanced during normal staggered (one-at-a-time) installations, and SpaceX quite clearly installs the first two arms on opposite sides and orientations in order to minimize installation-related listing. This indicates that his newest arms have significant mass and thus leverage over the boat’s roll characteristics, perhaps explaining why Mr. Steven has performed anywhere from 5-10 high-speed trials at sea both with and without arms installed.
Most recently, however, Mr. Steven spent a solid six weeks armless at Berth 240 while some sort of maintenance, analysis, or upgrade was undertaken with those four arms and their eight shock-absorbing booms. It’s hard to know for sure, but there are no obvious visual changes between the arms installed in July and August and those now present on his deck, and the net also looks almost identical.
Fairing drop tests?
What’s less familiar these days is an oddly arranged Falcon 9 payload fairing half that has been floating around SpaceX’s Port of Los Angeles berths for the last two or so weeks. Up until October 4th, the purpose of that single half was almost entirely unclear. On October 4th, Teslarati’s entire space team (Tom, Pauline, and I) coincidentally arrived at the same time as 5-10 SpaceX technicians were working on the fairing, attaching a series of guylines and harnesses and inspecting a number of actuating mechanisms on the half.

Just minutes after we arrived, a worker called out a short countdown and a wholly unexpected crashing noise sounded, followed immediately by several loud clangs as the harness connection mechanisms swung back and connected with metallic parts of the fairing. After the adrenaline wore off, the initial crashing noise was almost certainly the sound of the same mechanical jettison mechanism used to separate fairing halves ~3 minutes after the rocket lifts off.
Once photos of the event could be examined more carefully, that was exactly what we found – the six harness connections were attached to the fairing by way of the same mechanical interface that allows two halves to safely attach to each other. What we had witnessed was a harness separation test, using pressurized gas stored in COPVs (the gold striped cylinders) to rapidly actuate a latch, allowing the metal harness connectors to fall away. This is further evidenced by the presence of neon orange zip-ties connecting the ends of those harnesses to any sturdy fairing structure near the connection port, an easy and (presumably) affordable way to prevent those heavy connectors from swinging down and damaging sensitive piping and components.
- An overview of the weird fairing test article just before the harnesses were jettisoned. (Pauline Acalin)
- Note the taut, yellow ropes connected to the fairing at its original serparation connector ports. (Pauline Acalin)
- Zip-ties prevented the harness connectors from smashing (too hard) into the fairing’s innards. (Pauline Acalin)
- A Falcon 9 fairing during encapsulation, when a launch payload is sealed inside the fairing’s two halves. This small satellite is NASA’s TESS, launched in April 2018. (NASA)
According to someone familiar with these activities, the purpose of that testing is to prepare for true fairing drop tests from a helicopter. The jettisonable harness would be a necessity for easy drop testing, allowing the helicopter to carry a basic cargo hook and line while technicians inside communicate with the fairing to engage its built-in separation mechanism, all while ensuring that it immediately begins a stable glide or free-fall after dropping.
Observed on October 4th, it was at least moderately disappointing to see Mr. Steven remain in port during the spectacular Falcon 9 launch of SAOCOM 1A, October 7th. Reasons aside, roughly 12 hours after launch, Mr. Steven left on a 10+ hour cruise ~100 miles off the coast, where he repeatedly met up with tugboat Tommy and circled Santa Catalina Island once before heading back to port. Just 24 hours before launch (Oct. 6), the test fairing seen above was placed in Mr. Steven’s net for communications and harness testing – 24 hours after launch, Mr. Steven returned to Port of San Pedro after his 10-hour cruise with the same fairing half resting in his net.
- 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)
- An overlay of the paths of travel of a test-related helicopter and Mr. Steven, both on Oct. 8. The yellow plane is the heli at the beginning of a hover, while the gap between blue triangles in the lower left is where Mr. Steven was during that hover. (MarineTraffic + Flightradar24)
How and why it got there is unknown, as is the purpose of half a day spent boating around with the half in his net. However, a helicopter known to be involved in fairing drop tests was seen hovering and flying around Mr. Steven at the same time. Perhaps the two were practicing for real drop attempts, or perhaps the helicopter actually dropped a Falcon fairing (from > 2000 feet) and Mr. Steven successful caught it.
What is clear is that SpaceX is just getting started with efforts to perfect fairing recovery and eventually make the practice as (relatively) routine as Falcon 9 booster recovery and reuse is today. The latter was hardwon and the former will clearly be no easier.
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 crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.








