News
Startup fined $900k for launching illegal satellites, points to future space law challenges
Swarm Technologies, Inc., a satellite startup aiming to create the world’s lowest-cost satellite network, has been fined $900,000 by the U.S. Federal Communications Commission (FCC) for illegally launching and deploying four unauthorized satellites into orbit in January 2018 on a commercial Indian satellite launch vehicle. The satellites in question were Swarm’s SpaceBEE vehicles, which measure one quarter the size of a traditional CubeSat, a class of small satellites measuring 10 cm in height, width, and depth. In December 2017, the FCC deemed the SpaceBEE size too small for the U.S. Air Force’s traditional technology to track with routine methods and declined a license, but the satellites were placed into orbit regardless. With satellite and rocket launch startups proliferating as space access becomes more affordable, the debate over ensuring safety in this international arena is likely expand.
Swarm requested an experimental license from the FCC in April 2017, a first step for any satellite operator to ensure compliance with current international space laws, and their plan was to launch in September 2017, although that date was later delayed. Spaceflight Industries was next hired to connect Swarm with a launch provider and ensure its integration with the rest of the rocket’s payload. After the FCC declined the license in December 2017, Swarm applied for a new license in January 2018 for satellites meeting CubeSat specifications, but the original SpaceBEEs were already loaded onto the contracted Indian Polar Satellite Launch Vehicle (PSLV) and subsequently launched on January 12, 2018.
When news of the SpaceBEE deployment broke, concerns over regulatory backlash spread throughout the satellite community. The FCC issued an Enforcement Advisory on April 12, 2018 warning about consequences for communications companies failing to comply with licensing requirements, including a note to launch providers on how launch activities may be impacted if an unauthorized satellite payload needs to be removed. In a decision released December 20, 2018, Swarm Technologies was ordered to pay the fine and implement a five-year compliance plan.
Since the very first satellite was successfully launched by the Soviet Union on October 4, 1957, activities in space have been largely conducted by national governments and companies affiliated with them. However, the new space era is quickly changing that environment, rapidly opening up the beyond-Earth domain to private citizens. Billionaires like Elon Musk of Tesla and SpaceX, Jeff Bezos of Amazon and Blue Origin, and Richard Branson of Virgin and Virgin Galactic have mostly been the face of private/commercial space industry in recent years, but the technologies they’ve developed are also ushering in a new wave of affordable access to space, and with it, new technologies that don’t fit the traditional mold of “old space”.
The legal foundation for current space laws is the 1967 Treaty on Principles Governing the Activities of States in the Exploration and Use of Outer Space, including the Moon and Other Celestial Bodies, i.e., the “Outer Space Treaty”. Under this Treaty and subsequent treaties and laws arising from it, states, or nations, rather, are responsible for any space activities conducted by their own nationals, meaning a regulatory process that must be enforced. Where access to space was once expensive and difficult, the significantly lowered threshold has brought in a field full of players ready to take their shot at participating in the coming space economy and maybe, as seen with Swarm Technologies, even take a few risks to get there.
While the illegal launch of Swarm’s satellites was caught rather quickly (first by the community of amateur space trackers) and action was taken to penalize it, what’s to stop nations in the future from lowering standards to attract private customers? As stated in the FCC’s Enforcement Advisory, “Satellites authorized by an administration other than the United States do not require any FCC approval if Earth station operations are exclusively outside the United States.” Pressure from the international community to comply with treaties will only work to the extent that 1) the penalties deter the profit potential from the industry; 2) the international community agrees the activity is actually unsafe; and 3) the resistance to reforming regulations to permit the activity in question is deemed justified. Innovation, especially out of Silicon Valley, has a history of breaking rules to bring about significant change; however, some would argue that space isn’t the place for that approach.
-
- The thrice-flown, Falcon 9 Block 5 rocket that put Swarm’s recent 3 satellites in orbit (all FCC approved): SpaceBEE-5, 6, and 7. | Credit: Pauline Acalin
The thrice-flown, Falcon 9 Block 5 rocket that put Swarm’s recent 3 satellites in orbit (all FCC approved): SpaceBEE-5, 6, and 7. | Credit: Pauline Acalin
The problem seems to be a simple matter of ethics: Don’t launch things into space that aren’t safe for Earth’s occupants. But according to the FCC, Swarm’s proposed satellites were merely “below the size threshold at which detection by the Space Surveillance Network (SSN) can be considered routine.” The licensing issue seemed to generally only be safety-related because of the satellites’ irregularity, not from the lack of actual tracking capability, something that is only going to increase as more players enter the new space arena.
Another point worth consideration is that Swarm’s SpaceBEE satellites are actually trackable using the same SSN network the FCC cited in its rejection of Swarm’s license request, and live tracking is ongoing via an independent tracking service called LeoLabs. According to Dr. Sara Spangelo, one of the co-founders of Swarm Technologies, the satellites are equipped with radar retro-reflector technology, something developed by a US-Navy research and development lab, which makes their radar signature as bright as a CubeSat. The FCC has also granted the company a temporary experimental authorization to test the previously-illegal satellites’ orbital and tracking data. Thus, the question for the future is not so much whether the safety concerns are valid, but whether preventative rules will be waived where newer technology can demonstrate their compliance outside traditional standards.
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 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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
