News
SpaceX to shift Falcon 9’s next West Coast launch to Florida, the first of its kind in decades
According to NASASpaceflight spaceflight reporter Michael Baylor and an Argentinian government website, SpaceX appears to have decided to move its next West Coast launch from California to Florida, signifying the first East Coast polar launch in half a century could be just four months away.
Initially expected to launch out of SpaceX’s Vandenberg Air Force Base (VAFB) SLC-4E pad on a Falcon 9 rocket, the Argentinian space agency’s (CONAE) SAOCOM-1B Earth observation satellite was scheduled to lift off no earlier than February 2020. That launch window remains the same but Florida’s Cape Canaveral Air Force Station (CCAFS) has somehow arranged approval to reopen the United States’ Eastern polar launch corridor. The story behind the corridor’s closure is a bizarre one.
Having earned itself a bit of notoriety and fame over the years, the story of the closure of the Eastern polar launch corridor is simple on the outset. In November 1960, a Thor Able-Star rocket lifted off from Cape Canaveral for what was hoped to be a routine military launch. This particular mission carried GRAB II, a covert signals intelligence spacecraft designed to spy on radio communications around the globe.
Long story short: that Thor rocket suffered a failure that caused the booster to prematurely shut down and divert from its planned trajectory, forcing the range safety officer to manually trigger the rocket’s self-destruct mechanisms. Broken apart by explosives, one unlucky cow – standing in a Cuban field some 400 miles (650 km) downrange – was struck by rocket debris, killing the farm animal. Indeed, this might initially seem like an absurd reason to entirely end the practice of polar orbital launches from Cape Canaveral, but Cold War tensions were extremely high and President Fidel Castro leaped on the opportunity to hound the US.
An article published in a 2008 issue of the US Naval History Magazine covers this minor debacle in greater detail, shedding some much-needed light on why things played out how they did.
“In what somewhat inaccurately became known as “the herd shot around the world,” some of the falling rocket debris apparently splattered on a Cuban farm and killed a cow. “This is a Yankee provocation,” accused Revolucion, an official Cuban publication, insisting that the rocket was deliberately exploded over the country. Government radio stations cited the incident as further proof that the United States was trying to destroy the regime of Cuban President Fidel Castro. One cow was even paraded in front of the U.S. Embassy in Havana wearing a placard reading “Eisenhower, you murdered one of my sisters.”
Castro filed a complaint at the United Nations, and Washington sheepishly conceded the possibility that “fragments from the rocket booster” could have landed in Cuba. CIA Director George Tenet later quipped somewhat tastelessly that it was “the first, and last, time that a satellite had been used in the production of ground beef.” Further launches overflying Cuba were postponed, and improvements were made to the Cape Canaveral range-safety system. In any case, it was a dejected NRL group that returned to Washington.”
Naval History Magazine – April 2008
That overflight postponement was never withdrawn and VAFB – located on the coast of California – has supported all US polar launch** activity since late-1960. Public word of the possible reopening of the Eastern polar launch corridor came 57 years later when Wayne Monteith, commander of the 45th Space Wing, revealed that he had tasked analysts to determine whether the corridor could be reopened in light of wildfire troubles that closed VAFB’s Western Range in 2016. They concluded that there were no obvious technical showstoppers.
**There is a report that a Thor Delta C rocket performed two sun synchronous orbit (SSO; ‘nearly polar’) launches in the mid-1960s, overflying Cuba in the process, but it’s unclear if the trajectory used was the same as those used before Thor’s 1960 GRAB II failure.
A reporter who was present at the press conference said that SpaceX’s SAOCOM 1B launch hadn’t officially been put on on the Eastern Range’s planning schedule, indicating that some work remains before it can truly be said that the Eastern polar launch corridor has been reopened. Nevertheless, Douglas Schiess, the current commander of the 45th Space Wing, was obviously confident that those final steps are more technicalities than potential showstoppers and that 21st-century Eastern polar launches are now a question of “when”, not “if”.
In Monteith’s 2017 statement, it was stated that there is one major condition on the reopening: all launch vehicles intending to fly it must feature autonomous flight termination systems (AFTS). This is due to the risk that the rocket’s plume might prevent the reliable reception of radio telemetry at Florida-based tracking stations. SpaceX is currently the only launch provider in the world to have implemented AFTS and is thus the only provider currently capable of launching polar missions from Florida.
Time will tell just how extensive Florida’s polar launch capabilities are and how dramatically the new capability will impact Vandenberg’s commercial launch ecosystem. Speaking in 2017, Monteith was fairly blunt in his assessment that California was not only tepid on the subject of expanding VAFB’s commercial launch manifest, but was actively hostile at points. His point: if Vandenberg isn’t going to put effort into stimulating a commercial polar launch ecosystem, Cape Canaveral might as well try.
VAFB is currently in the throes of a four-month launch lull previously expected to last until SpaceX’s Feb. 2020 SAOCOM 1B launch. Depending on how things play out for startup Firefly Aerospace and how readily CCAFS can take to its new polar launch role, Vandenberg’s lull could easily stretch into the second half of 2020, perhaps more than a year between launches.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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 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.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
