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 Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Tesla Full Self-Driving lands in a new country, its 7th
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
