News
SpaceX wins FCC approval to launch first polar Starlink satellites amidst rideshare chaos
In a sign of the regulatory agency’s growing confidence in SpaceX, the FCC has rapidly approved a request to add ten Starlink satellites to an imminent Falcon 9 rideshare launch.
Known as Transporter-1 and originally scheduled to launch as early as December 2020 or January 14th, SpaceX delayed its first dedicated Smallsat Program mission to January 21st for unknown reasons last week. While there is no confirmed cause, any one of several recent events could have easily contributed to or fully caused the delay. In a rare ground processing failure, DARPA (Defense Advanced Research Projects Agency) revealed that two “risk reduction” technology demonstrator satellites were damaged on January 4th when their deployment mechanism was accidentally triggered during processing.
In other words, the two spacecraft may have been shot out of their dispensers by their spring-loaded deployment mechanisms, falling onto a processing bench or even off of the much taller payload stack. Meanwhile, on the very same day, space tug startup Momentus Space announced that it was removing its first Vigoride tug from Transporter-1 “for additional time…to secure FAA approval of…payloads.” Finally, once more on January 4th, SpaceX filed a request with the FCC to manifest and launch its first polar Starlink satellites to better take advantage of Transporter-1’s full capacity.
If launched, the ten spacecraft would be the first of several hundred planned polar Starlink satellites necessary for SpaceX’s massive internet constellation to serve some of the most remote communities on Earth. Referring to an orbit centered more around Earth’s north and south poles than its equator, the polar Starlink launch opportunity is available because SpaceX’s Transporter-1 mission – set to carry several dozen small satellites – is headed for a nearly polar “sun-synchronous orbit” (SSO).
For Starlink, sun-synchronous and polar orbit satellites will allow the constellation to serve customers and communities in high northern latitudes – possibly up to and including the Arctic and Antarctic once fully deployed.
SpaceX supported the US East Coast’s first polar launch in more than half a century in August 2020, effectively opening the same polar corridor that’s now allowing the company to launch Transporter-1 – and polar Starlink satellites – from the same pads it launches almost every other mission. It remains to be seen if SpaceX will one day perform dedicated polar Starlink launches from its West Coast launch pad – reactivated in November 2020 after spending almost a year and a half mothballed.
Perhaps the most impressive aspect of Starlink’s imminent polar launch debut is just how quickly both SpaceX and the FCC acted to make it happen. When SpaceX requested permission on January 4th, then just 10 days from the launch date, the historical odds of the FCC responding at all – let alone approving the request – in time were practically zero. Instead, the agency got back to SpaceX with a lengthy conditional approval (PDF) four days later. Although the FCC has yet to approve a request to move almost all of SpaceX’s 4,408 Phase 1 Starlink satellites to much lower orbits, the agency was apparently chomping at the bit to allow a limited trial at those lower orbits.
Dropped from an orbital altitude of ~1200 km (~750 mi) to 560 km (~350 mi), the ten Starlink satellites SpaceX now has permission to launch on Transporter-1 likely represent less than 20% of one polar ‘plane’ of Starlink satellites. In simpler terms, those ten satellites will only be capable of supporting a very limited test of polar Starlink internet, likely resulting in intermittent, unreliable coverage that won’t be viable for civil use until the FCC permits SpaceX to launch one or several full planes. Still, receiving approval to launch any number of satellites mere days after filing a request suggests that full FCC approval is a now question of “when,” not “if.”
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
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 Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
