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.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
