Spectrum coordination is the part of satellite mission planning that engineers often leave to lawyers, and lawyers often leave to consultants, and consultants sometimes leave until it's far too late to matter. In our work with early-stage operators, we've seen the ITU filing timeline cause more mission delays than hardware procurement, launch scheduling, and software development combined. That's not hyperbole — it's a structural reality of how the international regulatory framework operates, and understanding it early makes the difference between a mission that launches on schedule and one that waits 18 months for a frequency coordination letter.
This piece covers the mechanics of how frequency coordination actually works, what the ITU filing timeline looks like in practice, and where operators can take steps to reduce schedule risk.
The ITU Frequency Coordination Framework
The International Telecommunication Union, through its Radiocommunication Bureau (BR), administers the Radio Regulations — the international treaty framework governing use of the radio frequency spectrum and orbital positions. For satellite missions, the relevant process is Article 9 coordination, which applies when a planned satellite network could cause harmful interference to other administrations' registered networks operating in the same band and orbital arc.
The process begins when an administration submits an Advance Publication Information (API) filing to the ITU BR at least 2 years before the planned deployment date. This triggers a 3-month publication window during which other administrations can identify potential interference concerns. The API is followed by a Request for Coordination (RfC) filing, which formally notifies potentially affected administrations and opens the bilateral coordination process.
Bilateral coordination can take anywhere from several months to several years depending on how many administrations have potentially affected networks and how motivated all parties are to resolve interference concerns. Once coordination is complete with all affected parties, the operator files for notification, and upon favorable finding by the ITU BR, the frequency assignment is recorded in the Master International Frequency Register (MIFR). Recording in the MIFR gives the assignment international recognition and protection against later entrants.
The full timeline from API to recorded notification — assuming no contested coordination — typically runs 3-5 years. For complex cases with multiple affected administrations or disputed interference claims, 7 years is not unusual.
The Commercial Reality for NewSpace Operators
The 3-7 year ITU timeline was designed for geostationary satellites where planning horizons are decade-scale and orbital slots are scarce geopolitical assets. For a LEO CubeSat constellation with a 5-year operational design life, a 7-year coordination process is a fundamental mismatch.
The practical response from most commercial LEO operators has been to use frequency bands that already have coordination completed by their national administration, or to operate under an existing coordination umbrella held by their launch or licensing partner. In the US, the FCC licenses commercial satellite operators for space and earth station operations, and the US administration handles ITU filings on behalf of US licensees. That shifts the coordination burden to the FCC licensing process, which typically runs 6-18 months for a straightforward LEO mission — still significant, but more tractable than the full ITU timeline.
The key insight for operators: frequency licensing is not a single process. There is a national regulatory layer (FCC in the US, Ofcom in the UK, JAXA/MIC in Japan, etc.) and an international coordination layer (ITU). Both must be addressed, and the timelines interact. Starting the national licensing process early is necessary but not sufficient — you also need to understand where your planned frequency bands sit in the ITU coordination landscape.
Band Selection and Coordination Complexity
Not all frequency bands are equally burdened by coordination requirements. The coordination complexity for common CubeSat bands varies considerably:
| Band | Common CubeSat Use | Coordination Complexity | Notes |
|---|---|---|---|
| UHF (435-438 MHz) | TT&C (amateur) | Low | Amateur satellite service; ITU coordination not required but throughput very limited (~9.6 kbps) |
| S-band (2.0-2.3 GHz) | TT&C + low-rate downlink | Medium | Coordination typically needed; well-established allocation; FCC licensing 6-12 months for LEO |
| X-band (8.025-8.4 GHz) | Payload data downlink | Medium-High | Earth Exploration Satellite Service (EESS) allocation; FCC process 12-18 months; ITU coordination with existing EESS operators |
| Ka-band (26.5-40 GHz) | High-throughput downlink | High | Dense with existing GEO operators; coordination complex; recommend early legal counsel engagement |
ITAR, EAR, and the US Export Control Layer
For US operators and non-US operators using US-manufactured components (which describes most commercial CubeSat missions), ITAR (International Traffic in Arms Regulations) and EAR (Export Administration Regulations) add a compliance layer on top of spectrum licensing. Ground station operations across international borders can trigger export control review requirements even when the satellite itself is US-licensed.
Using a shared ground network with stations in multiple jurisdictions means that each ground site's operation relative to a US-licensed satellite must be reviewed for ITAR/EAR compliance. This is typically handled through Technical Assistance Agreements (TAAs) or license exceptions, but the specifics depend on what data is being downlinked and where. Payload data from optical EO missions often falls under ITAR jurisdiction; telemetry-only passes frequently qualify for license exceptions.
We encounter this issue regularly with operators onboarding to the Orbitvein network who haven't yet mapped their export control obligations to their ground contact geography. Getting the ITAR/EAR analysis done before you schedule your first international pass is considerably less painful than doing it after the fact.
Practical Steps to Reduce Schedule Risk
Given the regulatory timeline constraints, here are the actions that actually move the needle for early-stage operators:
- Start the national licensing process at PDR, not CDR. For US operators, this means FCC space station and earth station license applications. The FCC has a streamlined process for LEO smallsats under the Part 25 rules, but it still takes time and requires detailed technical documentation that you won't have until the design is reasonably mature — which is exactly why PDR is the right trigger point.
- Choose frequency bands with existing national coordination. If your administration already has ITU coordination for the bands you intend to use, you don't need to start a new coordination process — you operate under the existing coordination envelope. This is the single biggest timeline shortcut available.
- Understand your ITU filing obligation before launch, not after. Operating without proper ITU coordination exposes you to interference claims from other operators and, in extreme cases, can result in your signals being classified as harmful interference — legally requiring you to cease transmission.
- Engage a spectrum consultant early if you're operating in X-band or Ka-band. These bands have the most complex coordination landscapes and the highest stakes for getting the analysis wrong.
The regulatory framework governing satellite spectrum is not designed to be navigated quickly. It was built for an era of large, expensive satellites operated by national agencies with decade-long planning horizons. The commercial NewSpace sector has been working to adapt these rules — the FCC's streamlined smallsat licensing rules are a product of that effort — but the ITU framework moves more slowly than commercial innovation timelines. Working within it effectively means understanding the constraints early enough that they become engineering inputs rather than late-stage surprises.
