News
SpaceX’s flight-proven Falcon 9 and drone ship fleet ready for duo of launches
SpaceX is gearing up for a duo of flight-proven Falcon 9 launches and drone ship landings on both coasts of the United States, set for liftoff from Cape Canaveral’s Kennedy Space Center and Vandenberg Air Force Base no earlier than (NET) November 15th and 19th, respectively.
#SpaceXArmada: Moments ago, outbound tugboat Hawk with droneship OCISLY in tow in @PortCanaveral. Destination: Booster core landing/recovery LZ of Thursday's #Eshail2 launch, approx 408 mi E of @NASAKennedy. pic.twitter.com/n5FvBdIvpt
— Cowboy Dan (@CowboyDanPaasch) November 12, 2018
East Coast activities
On the East Coast, drone ship Of Course I Still Love You departed from Port Canaveral late last night (Nov 11) as Falcon 9 B1047 rolled onto Pad 39A for a preflight static fire test, where the rocket will be filled with a full complement of fluids (TEA/TEB, helium, nitrogen, oxygen, kerosene) and all nine Merlin 1D engines are ignited in order to replicate the seconds just prior to a real launch. That static fire test was originally expected to occur on November 10 or 11 but has obviously been pushed back a day to Nov. 12, likely meaning that the rocket’s launch – carrying Qatari communications satellite Es’hail-2 – will slip 24 hours to 3:46pm EST (08:46 UTC) on the 16th,
Following the unfortunate loss of Amos-6 during a preflight static fire in September 2016, SpaceX has since made a reasonable move away from performing static fires with payloads integrated atop the rocket, unless the customer specifically requests that it be done that way to save time. As such, Falcon 9 must be brought horizontal, rolled back to the hangar, inspected, and finally have the payload and fairing attached to the rocket, a sensitive process that demands nuance and time. Combined with an analysis of data gathered during the static fire, this process – when all goes as planned – can take at least 48 hours from start to finish, and longer still if any minor off-nominal behavior is observed or the launch customer has additional requirements (typically reserved for NASA and national security-related missions).
- B1047 horizontal at Pad 39A, November 11. (Tom Cross)
- B1047 made an extraordinary ring vortex rainbow as it smashed through Max Q, the point of highest aerodynamic stress on the rocket. (Tom Cross)
- B1046 seen mid-static fire at Pad 39A ahead of Falcon 9 Block 5’s launch debut, May 2018. (Tom Cross)
Because rockets like Falcon 9 are extraordinarily intricate and finely-tuned machines, perfectly nominal launch-related events are few and far between. In reality, the time between static fire rollout and launch readiness is rarely less than three days (72 hours), not including the process of rolling the fully-integrated rocket back out to the pad, aligning and securing the vehicle and transporter-erector (TE) over the flame trench, and finally attaching all umbilical connections and verifying vehicle health. Speaking generally, four to five days is a good rule of thumb for the time it takes to complete Falcon 9’s static fire and return the rocket to the pad after attaching the payload.
Still, it’s always a good sign when a drone ship leaves port, much like OCISLY did on the evening of the 11th. The journey to its destination will take 2-3 days, meaning that the drone ship will be ready to catch Falcon 9 whenever the rocket is ready to launch.

Drone ships and sooty rockets, oh my!
On the West Coast, SpaceX is also getting ready for drone ship Just Read The Instructions (JRTI) to depart Port of San Pedro in anticipation of a presumed sea recovery of Falcon 9 following the NET Nov 19 launch of a multi-satellite rideshare mission known as SSO-A. While SpaceX currently holds two recovery licenses for the booster, one by sea and one at the land-based LZ-4 pad, it’s possible that the company will be forced to use JRTI despite the fact that Falcon 9 will have plenty of propellant left to return itself to the launch site (RTLS). United Launch Alliance’s (ULA) next Delta IV Heavy rocket is currently on-pad with a presumably very expensive National Reconnaissance (NRO) satellite attached roughly 1.5 miles northeast of SpaceX’s LZ-4 – the rest of the gaps are easy enough to fill in.
- Falcon 9 Block 5 booster B1046 seen during both of its post-launch landings. (SpaceX/SpaceX)
- B1047 completed its first successful launch in July 2018. (Tom Cross)
- B1047 seen rolling into 39A’s integration hangar for refurbishment on July 31st. (Reddit – Kent767)
JRTI was spotted by Teslarati photographer Pauline Acalin performing some rare sea trials on November 10 after spending several weeks berthed at port for routine maintenance and deck repairs. Fairing recovery vessel Mr. Steven has also been undergoing some unusual modifications, now proudly sporting what can only be described as a steel horn recently installed on the tip of his bow deck. After sitting out a catch attempt during the launch of SAOCOM 1A to prepare for controlled helicopter drop tests performed over a period of several weeks in October, Mr. Steven will most likely be ready for another stab at operational fairing recovery during SSO-A.
Both rockets – B1047 to the East and (presumed) B1046 to the West – are flight-proven, meaning that they have flown operational orbital missions prior to their upcoming launch attempts, B1047 launched communications satellite Telstar 19V in July 2018, while B1046 has actually performed two successful launches already, Bangabandhu-1 in May and Telkom 4 (Merah Putih) in August.
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 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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.






