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.
Elon Musk broke his silence regarding the jury decision to throw out the case against OpenAI and Sam Altman. The Tesla, SpaceX, and xAI frontman has already indicated that an appeal will be filed regarding the decision, which went against him yesterday.
A Federal jury dismissed this high-profile lawsuit after less than two hours of deliberation due to a statute-of-limitations issue.
In a strongly worded post on X on May 18, Musk addressed the federal jury’s dismissal of his high-profile lawsuit against OpenAI, vowing to appeal the ruling to the Ninth Circuit Court of Appeals. The decision, according to Musk, was centered not on the substantive claims but on a statute-of-limitations technicality.
Musk’s lawsuit, filed in 2024, accused OpenAI co-founders Sam Altman and Greg Brockman of breaching the organization’s original nonprofit mission. OpenAI was established in 2015 as a non-profit dedicated to developing artificial intelligence for the benefit of all humanity, with Musk as a key early donor and co-founder before departing in 2018.
Musk alleged that Altman and Brockman improperly shifted the company toward a for-profit model, enriched themselves through massive valuations and partnerships (including with Microsoft), and betrayed founding agreements.
In his post, Musk emphasized that the judge and jury “never actually ruled on the merits of the case, just on a calendar technicality.” He stated unequivocally: “There is no question to anyone following the case in detail that Altman & Brockman did in fact enrich themselves by stealing a charity. The only question is WHEN they did it!”
Regarding the OpenAI case, the judge & jury never actually ruled on the merits of the case, just on a calendar technicality.
There is no question to anyone following the case in detail that Altman & Brockman did in fact enrich themselves by stealing a charity. The only question…
— Elon Musk (@elonmusk) May 18, 2026
Musk argued that allowing such actions to stand without review sets a dangerous precedent. “I will be filing an appeal with the Ninth Circuit, because creating a precedent to loot charities is incredibly destructive to charitable giving in America,” he wrote. He reiterated OpenAI’s founding purpose: “OpenAI was founded to benefit all of humanity.”
The jury’s unanimous advisory verdict found that Musk’s claims of breach of charitable trust and unjust enrichment were filed outside California’s three-year statute of limitations. U.S. District Judge Yvonne Gonzalez Rogers adopted the finding and dismissed the case. OpenAI hailed the outcome as vindication, while Musk’s legal team immediately signaled plans to appeal.
The trial, which featured testimony from Musk, Altman, Brockman, Microsoft CEO Satya Nadella, and others, exposed deep rifts in Silicon Valley over AI’s direction.
Musk has long warned that profit-driven AI development, especially with closed models and powerful corporate ties, risks endangering humanity—contrasting it with OpenAI’s original open, safety-focused charter. OpenAI countered that the suit stemmed from business rivalry and that Musk himself had explored for-profit paths earlier.
Musk’s appeal could prolong the saga, potentially affecting OpenAI’s valuation (reportedly over $800 billion) and IPO ambitions. Supporters view his stance as defending nonprofit integrity, while critics see it as sour grapes from a competitor whose own xAI is racing in the AI arena.
Regardless of the legal outcome, the case has spotlighted critical questions about trust, governance, and mission drift in the rapidly evolving AI industry. Musk’s willingness to fight on suggests this chapter is far from closed, with broader implications for how charitable organizations—and the tech giants born from them—operate in the future.
Elon Musk
NASA updated Artemis III and SpaceX’s role just got more complicated
SpaceX’s Starship is the key to NASA’s Moon plan and the timeline is already slipping.
SpaceX has been at the center of NASA’s Moon ambitions for five years, and the updated Artemis III plan recently released by NASA makes that relationship more visible than ever. In April 2021, NASA awarded SpaceX a $2.89 billion contract to develop the Starship Human Landing System, selecting it as the sole provider to land astronauts on the Moon under Artemis III. Blue Origin filed legal protests, lost, and eventually received its own contract, but SpaceX was always the program’s primary lander contractor.
The original plan called for Starship to land two astronauts on the lunar south pole. That mission slipped as Starship development ran behind schedule, and in February 2026, NASA officially revised the Artemis III architecture entirely. The mission will now remain in low Earth orbit and serve as a crewed rendezvous and docking test between the Orion spacecraft and both the SpaceX Starship HLS pathfinder and Blue Origin’s Blue Moon Mark 2 pathfinder, with the actual Moon landing pushed to Artemis IV in 2028.
What makes SpaceX’s position particularly significant is the direct line between this week’s Starship V3 launch and the Artemis timeline. The Starship HLS is essentially a modified version of the V3 upper stage, meaning SpaceX cannot realistically prepare a lander for a 2027 docking test until it has demonstrated that the base vehicle flies reliably at scale. Flight 12, targeting this week, is the first data point in that sequence.
NASA has spent nearly $7 billion on Human Landing System development since awarding contracts to SpaceX and Blue Origin in 2021 and 2023, and NASA administrator Jared Isaacman has indicated a desire to drive down costs going forward. As Teslarati reported, before Starship HLS can put anyone on the Moon it has to solve a problem no rocket has demonstrated at scale, which is refueling in orbit, requiring approximately ten tanker launches worth of propellant loaded into a depot before the lander has enough fuel to reach the lunar surface.
The Artemis III mission described by NASA is essentially a stress test for every system that needs to work before any of that happens.
SpaceX has gone from a launch contractor to the single most critical hardware provider in America’s return-to-the-Moon program. With an IPO targeting a $1.75 trillion valuation and Elon Musk’s compensation tied directly to Mars colonization, the pressure on every Starship milestone between now and 2028 has never been higher.
Tesla is continuing to refine and improve its Robotaxi program from A to Z, and it is now going to make some sweeping changes to the smartphone app portion of the suite.
The company is aiming to make some sweeping changes with the release of Robotaxi app version 26.4.5, which was recently decompiled by Tesla App Updates on X. The update reveals significant new code, focused on remote operations, safety protocols, and seamless autonomous ride-hailing.
These improvements evidently signal Tesla’s preparations for scaling unsupervised Cybercab deployments, particularly the steering wheel-less variants spotted in production. The enhancements emphasize providing a reliable experience that gives passengers support when needed, along with operational efficiency.
Version 26.4.5 of the Robotaxi app has been de-compiled and we’ve got some interesting things added this update (https://t.co/jInbED7fOv):
– Remote Operator Voice Calls 📞
– Proactive Remote Assistance 🤖
– Manual Override + Remote Start for wheel-less Cybercabs 🎮
-…
— Tesla App Updates (iOS) (@Tesla_App_iOS) May 16, 2026
Remote Operator Voice Calls
One standout addition is support for remote operator voice calls. The app now includes a dedicated native voice-communication system linking passengers directly to Tesla teleoperators via the vehicle’s cabin microphone and speakers.
This feature allows real-time assistance during rides, addressing issues like navigation questions or comfort adjustments without disrupting the autonomous journey. It builds on existing support protocols, making human intervention more accessible and intuitive.
Proactive Remote Assistance
The update introduces proactive remote assistance capabilities. Rather than waiting for passenger-initiated requests, the system can anticipate and offer help based on monitored conditions.
This might include something like suggesting route changes, climate adjustments, or addressing potential delays. By integrating AI-driven monitoring with human oversight, Tesla aims to deliver a smoother, more attentive experience that exceeds traditional ride-sharing services.
Manual Override and Remote Start for Steering Wheel-less Cybercabs
A key highlight for the wheel-less Cybercab fleet is manual override plus remote start functionality. Fleet operators and technicians can now temporarily take control or remotely start vehicles lacking steering wheels. This is crucial for lower-speed maneuvers, such as getting vehicles from tight parking situations or even performing maintenance.
Controls are strictly limited for safety–typically to speeds under 2 MPH–ensuring these interventions remain emergency measures only.
Tesla is adding a secure “Enable Manual Drive” mode that will allow those fleet operators or others to take control temporarily.
Additionally, a Remote Start feature, which authorizes an empty vehicle to begin a driverless ride alone.
Ride-Hailing and Dispatch Features
Ride dispatch has been enhanced with soft-matching and multi-stop support. The app can intelligently pair riders with available Cybercabs while accommodating multiple destinations in a single trip.
This optimizes fleet utilization, reduces wait times, and improves efficiency for shared rides. Soft-matching likely considers factors like proximity, rider preferences, and vehicle availability for better user satisfaction.
Rider-Cabin Sync, Real-Time Routing
New synchronization tools allow the rider’s app to mirror and control cabin settings like seating, climate, and entertainment directly from their phone. Real-time routing updates adapt dynamically to traffic or road conditions, while dynamic safety monitoring continuously assesses the environment.
The app can now push updates directly to the main screen, enabling Center Display Control. Additionally, there is a dedicated navigation protocol sharing the exact coordinates of road closures and construction, which could prevent the car from getting stuck and needing manual override.
These features create a cohesive, responsive experience where the vehicle and app work in harmony.
Kill Switch
A high-security command lets Tesla completely freeze a vehicle’s ability to drive. This would take the vehicle out of the Robotaxi fleet for any reason Tesla sees fit, and would not allow it to be put into gear even with the correct equipment, like valid keys.
Elon Musk breaks silence on OpenAI trial decision
NASA updated Artemis III and SpaceX’s role just got more complicated
