When officials at the Federal Communications Commission (FCC) denied launch authorization for four innovative satellites from startup Swarm Technologies last December, the agency was unequivocal as to the reason. “The applicant proposes to deploy and operate four spacecraft that are smaller than 10 centimeters in one of their three dimensions,” read a letter to Swarm’s CEO and founder Sara Spangelo. “These spacecraft are therefore below the size threshold at which detection by the Space Surveillance Network can be considered routine.”
The FCC was worried about collisions in space, where even the smallest objects traveling at orbital velocities can inflict massive damage on satellites or, in a worst-case scenario, manned spacecraft. It thought Swarm’s SpaceBees satellites, measuring 10 by 10 by 2.5 cm, would be just too small to track.
When Swarm launched them anyway, on an Indian rocket in January, the FCC was furious. It rescinded permission for the company’s next satellite launch, due later this month, and questioned whether Swarm was a suitable company to hold a communications license at all. If the FCC comes down hard on Swarm, the company’s ambitious plans for a constellation of Internet of Things communications satellites could be doomed.
So why did Swarm take such a risk in launching its SpaceBees, or even building them in the first place? Perhaps because the FCC’s position on small satellites has been bizarrely inconsistent.
An investigation by IEEE Spectrum has revealed that the FCC licensed multiple satellites smaller than 10 cm over the past five years, including some as small as 3.5 by 3.5 by 0.2 cm. But the commission has also changed its mind from one application to the next, refusing launch permission for satellites that were virtually identical to ones previously authorized. This uncertainty has led to at least one satellite maker exporting his technology rather than risk being denied a license in the U.S.
The Smaller, the Better
Most satellites are essentially smartphones in space. They have sensors such as cameras and magnetometers to gather data, radio transmitters and receivers for communication, processors to crunch the numbers, and batteries to power everything. And like smartphones, satellites have benefited from decades of technological advances such as those whose progress runs on Moore’s Law’s timeclock.
But miniaturization is even more important for satellites than it is for iPhones. Launching a kilogram payload to low earth orbit (LEO) currently costs at least $3000. Multiply that by the 12,000 satellites that SpaceX is planning for its Starlink constellation of communications satellites, and it is clear that lighter and smaller is almost always better.
When Stanford University astronautics professor Bob Twiggs first came up with the idea of a modular “CubeSat” in 1999, he settled on a small 10-by-10-by-10-cm design. Most CubeSats are multiples of this, but their standard 10-by-10-cm footprint allows them to be launched from the same device, regardless of their length.
By the time Twiggs moved to Kentucky’s Morehead State University in 2009, technological advances had accumulated to the point that he proposed an even smaller building block called “PocketQube,” measuring just 5 by 5 by 5 cm.
Four PocketQube satellites were launched on a Russian rocket in late 2013. One of them, the QubeScout-S1 (aka QubScout-S1), was a 5-by-5-by-10-cm sun sensing satellite built by researchers at the University of Maryland. Because of its American roots, the QubeScout is officially a U.S. spacecraft and thus required launch permission from the FCC.
As part of this process, the researchers supplied the FCC with an Orbital Debris Assessment Report (ODAR), a form designed by NASA to assess the danger posed by a satellite to other spacecraft or people on Earth. The standard ODAR covers the likelihood of a satellite hitting something in its orbit, breaking up, or re-entering the Earth’s atmosphere. It does not include any minimum size requirements.
Sprites in Space
Small as the QubeScout was, Zac Manchester thought he could go smaller. Much smaller. While a graduate student in Aerospace Engineering at Cornell University, Manchester had developed a wafer-thin spacecraft he calls Sprite. It measured just 3.5 by 3.5 by 0.2 cm, and weighed less than 5 grams. Sprites, he imagined, would be modern-day Sputniks, transmitting their names and a few bytes of data to receivers on the ground.
“The idea was to push the limits, to see how small we could really build a satellite,” says Manchester. “One reason is that they can be extremely cheap. We can now talk about launching a satellite for a couple of hundred bucks.”
In 2011, Manchester launched a Kickstarter campaign to build a CubeSat mothership that would deploy 128 Sprites into low Earth orbit. He quickly raised nearly $75,000 and secured a position on a NASA-sponsored launch due for 2014.
“We thought about tracking and debris concerns from the outset,” says Manchester. “We got vetted by the NASA Orbital Debris Program Office (ODPO), the people who spend their lives dedicated to making sure we don’t make Earth orbit uninhabitable. We also spoke with the Department of Defense and the Joint Space Operations Center who operate tracking radars.” Manchester even ran a statistical Monte Carlo analysis to determine the collision risks.
“At the end of the day, everyone signed off on it and said you guys are OK,” he says. The FCC did too, authorizing Manchester’s KickSat satellite in the spring of 2014 without raising any concerns.
In the summer of 2014, the FCC licensed yet two more tiny satellites: AeroCube-6A and -6B. They are a pair of 5-by-10-by-10-cm satellites designed to measure space radiation impinging on spacecraft. These small satellites, dubbed “picosatellites,” were produced by the Aerospace Corporation, a federally funded R&D center for the U.S. Air Force’s Space and Missile Systems Center. Like the PocketQubes before them, the AeroCubes were launched and are still being tracked successfully. Picosatellites seemed to be flying high.
A Kick in the Sats
But space can be cruel. Although Manchester’s KickSat mothership launched perfectly on a SpaceX Falcon 9, it was released in an extremely low orbit where atmospheric drag would cause it to re-enter and burn up in a matter of weeks. The Sprite deployment then had to be delayed by 16 days to allow for the possibility of a manned Soyuz mission to the International Space Station going wrong. (If the mission aborted, its planners would not want the capsule to return to Earth through the cloud of tiny satellites). While the Soyuz mission went off without a hitch, something went wrong aboard the KickSat in the meantime and it burned up without having released its Sprites.
Luckily, Manchester had enough spare parts to piece together a replacement mothership and a second flock of Sprites, and NASA said that it would support another mission. Manchester submitted a new FCC application in 2015, almost identical to the first.
As before, the tiny Sprites would operate for less than a week before burning up in the atmosphere and, as before, Manchester had gotten the go-ahead from NASA’s space junk experts. “For KickSat-2, releasing 100 Sprites from 325 km altitude has no long-term negative impact to the environment. The ODPO is fine with the plan,” wrote Jer-Chyi Liou, NASA’s Chief Scientist for Orbital Debris. But this time the FCC’s response was very different.
Towards the end of May 2016, Manchester was preparing the KickSat-2 mothership in Ithaca, New York, for its flight to Houston’s Johnson Space Center, where it would be integrated into the launch rocket. The weekend before he was due to fly, Manchester got an email and then a phone call from the FCC, saying that the agency was not going to licence the satellite.
The letter from the head of the FCC’s experimental licensing branch spelled out its thinking: “We are not able to approve your request due to concerns regarding the overall risk and uncertainties associated with your experiment. There are concerns about the trackability and operational impacts of these satellites (Sprites), and of this type of satellite in general.”
“This is a crazy thing to happen two days from delivering a satellite,” says Manchester. “We had already been vetted by the NASA office that actually does this for a living. It wasn’t a problem before and it’s not really a technical problem. It’s more of an unfortunate bureaucratic situation... regulation gone awry.”
While Manchester attempted to reason with the FCC, his NASA contacts tried to pull strings within the federal government, but to no avail. As months ticked into years, Manchester realized that an FCC license might never be forthcoming.
Eventually, NASA adopted KickSat-2 as an official NASA mission. Due to a regulatory quirk, NASA’s own satellites are overseen by the National Telecommunications and Information Administration (NTIA) rather than the FCC. KickSat-2 is now slated for launch late this year or early next. “But it’s taken us three years and lots of lawyers to figure out,” says Manchester.
IEEE Spectrum could find no record of any satellite smaller than 10 cm on any side having been licensed for launch by the FCC since the KickSat-2 fiasco. We gave the FCC multiple opportunities to explain its inconsistent approach to licensing small satellites, but it has yet to reply.
Tom Walkinshaw, founder and CEO of Alba Orbital, a start-up based in Scotland that develops and sells PocketQube satellites, calls the FCC’s erratic picosat licensing decisions “a head-scratcher.” He says, “Is one part of the organization acting one way, and another part another? I don’t think anyone’s too sure right now. Everyone’s looking for clarification.”
The FCC attempted to shed some light on its thinking last month, with a proposed rule-making for streamlining the licensing procedures for small satellites. The main aim of the new rules, welcomed by every expert IEEE Spectrum spoke to, is to reduce the paperwork and time needed to license the launches of small, experimental satellites and CubeSats. But the rules explicitly exclude picosats, requiring satellites to be no less than 10 cm on any side “to ensure that the satellite will be trackable as a space object.”
Walkinshaw points out that not only are all of today’s PocketQube satellites (and Swarm’s SpaceBees) being successfully tracked by existing technology, a new S-Band “Space Fence” due to be deployed by the United States later this year will explicitly monitor objects with dimensions as small as 5 cm.
A bigger problem, thinks Manchester, is that “the FCC has been unwilling to consider licensing anything smaller than a CubeSat through the normal application process, and this new process does not seem to address that broader issue in any way.”
When the Breakthrough Starshot initiative approached Manchester in 2015 offering to develop his Sprites into miniscule interstellar spacecraft for a journey to Alpha Centauri, it wanted to test them in Earth orbit first. “We didn’t even try to go through the FCC,” says Manchester. “We got an export licence from the State Department, which took a couple of weeks, and then I just took the satellites to Germany in my carry-on.”
Last summer, the London-based Breakthrough launched six Sprites on a German satellite from an Indian launch vehicle, far outside the FCC’s jurisdiction. Germany has no minimum size regulations for satellites.
“I want to be responsible around debris concerns,” says Manchester. “But because of the situation with the FCC, it’s now advantageous for a company that wants to [work with small satellites] to relocate and do it as a foreign company. And that’s probably not great for the U.S. long term.”
Update 15 April 2018: After publication, Neil Grace, a spokesperson for the FCC, sent this statement in response to an earlier request for comment: “Size isn’t the only criteria that the FCC considers when granting experimental licenses for small satellites. Due to the number of variables to consider, the Commission takes a wholistic case-by-case approach when granting authorizations for satellites of this size.”
Mark Harris is an investigative science and technology reporter based in Seattle, with a particular interest in robotics, transportation, green technologies, and medical devices. He’s on Twitter at @meharris and email at mark(at)meharris(dot)com. Email or DM for Signal number for sensitive/encrypted messaging.