Fusion F3C. Everything the FCC database should be.
A spectrum coordination platform built on the federal licensing record — 100 million entries, answered in seconds, not an afternoon.
The problem
The FCC publishes everything and organizes nothing. The data is free, and it costs you a day — inconsistent formats, keys that don't join, queries that time out, and a coordination deadline that doesn't move.
Coordination doesn't happen at a desk. Neither should the database.
F3C was built for people who have to be right the first time — coordinators walking a venue the morning of a show, with no second pass at the frequency plan. Every query is answered in seconds, from any device, against the same federal record a regulator would check.
Four steps from a venue address to a clean spectrum plan.
Anchor the venue
Drop a point by coordinates or geocode a street address. That location anchors every search, scan, and terrain profile that follows — and it persists, so the same venue is one click away next season.
Read the RF environment
One scan catalogs every known transmitter inside your radius across the bands you care about — VHF, UHF, ISM, DECT, Wi-Fi, C-band, 5 and 6 GHz, microwave — pulling licensed ULS records and DTV allocations into a single picture. It finishes in seconds.
Clear the spectrum
Include or exclude transmitters, set hard and soft exclusion zones, and let guard bands size themselves against transmitter power. Ambient sources the FCC never sees — IEMs, walkies, intercom — get entered by hand and folded into the intermodulation math.
Keep the evidence
Save the search, export the exclusions, archive the environment. When the next event lands at the same venue you start from what actually worked — and you can still show which records the plan was built on.
Everything spectrum work needs, against one record.
Each capability runs on the same federal dataset — synchronized weekly, indexed for spatial query, and normalized into something you can actually join on.
Radius search on real geometry
PostGIS-backed radius search from 0.1 to 500 km, returning every licensed transmitter sorted by distance and bearing — at the precision the licensee actually filed.
Frequency, service, status
Filter by frequency range in MHz, emission designator, ERP and EIRP, antenna height, license status, and 140+ radio service codes spanning aviation, broadcast, cellular, maritime, and public safety.
Line of sight, not line of hope
Elevation profiles between your location and any transmitter, drawn from high-resolution terrain data — so the obstruction that kills a path shows up before the truck rolls.
Guard bands and IMD
Guard bands scale automatically with transmitter power. Sources outside the federal record are entered by hand and carried into intermodulation analysis, so mixing products surface on paper instead of on air.
Authorizations, by FCC ID
Search the equipment authorization database by manufacturer, model, grantee code, or full FCC ID — frequency bands, power output, and modulation for every approved device in the plan.
Public data is not the same thing as usable data.
The FCC's Universal Licensing System is one of the most complete spectrum records in the world. It is also forty-odd tables of bulk exports, refreshed on a schedule you have to track yourself, with formatting that shifts without notice and keys that don't reliably join.
Free data still has a price. It is paid in coordinator hours, in transcription errors that survive into the frequency plan, and in the one filing that missed its deadline because a query took all afternoon to come back wrong.
F3C does the unglamorous part once, on everyone's behalf: ingest, normalize, key, index, and re-sync every week — so the question you ask is about spectrum, not about schema.
The data was always there. Finding it was the job.
Why F3C, and not the raw ULS download.
The federal record, kept current
Over 100 million ULS license records across more than 40 FCC tables, re-synchronized every week without anyone having to remember. What you search is what the regulator has on file.
One environment per venue, kept for good
Scans, exclusions, ambient sources, and transmitter decisions live together as a saved RF environment. Re-activate it next season, or archive it and see how the spectrum around a venue changed.
Designed around coordination, not lookup
Most FCC front-ends stop at search. F3C carries the work through to the decision — what to exclude, how wide the guard band, which mixing products to design around, and why.
Programmatic access where it mattered
Enterprise accounts drive the same data through an authenticated API, so spectrum records feed planning tools directly instead of being re-keyed by hand.
100M+
FCC License RecordsUniversal Licensing System, synced weekly
40+
Federal Tables IndexedNormalized, keyed, and searchable
~30s
Typical Query ResponseAgainst the full national record
The frequency plan is finished. Can you prove what it was built on?
The platform, the ingest pipeline, and the coordination methodology behind them are all ours — built in-house, run in-house, against the same federal record you are accountable to.
If your work depends on that record, we would rather show you what we built than describe it.
Every frequency you assign is a claim about the record.
The record only helps you if you can read it.
Ask us for the walkthrough.
What teams ask about F3C and the federal record.
The questions frequency coordinators, broadcast engineers, and spectrum managers bring to us — and how F3C answers them.
How do I get access to F3C?
We run F3C for demonstrations and for coordination engagements rather than as an open sign-up product. That starts with a short conversation, so we can point the system at a venue and a band that actually matter to you.
If you would like to see it, or talk about the coordination work behind it, get in touch and we will arrange a walkthrough.
What data does F3C actually search?
The FCC Universal Licensing System — over 100 million license records across more than 40 federal tables, re-synchronized weekly. Alongside it, F3C indexes the FCC equipment authorization database and DTV broadcast allocations, so a single scan can cover licensed transmitters and television channel assignments together.
How is this different from searching the FCC's own site?
The FCC's data is authoritative but not operational. It arrives as bulk exports with shifting formatting and keys that don't reliably join, and its search surface has no concept of "every transmitter within 12 km of this stage".
F3C ingests the same records, normalizes them, gives them real primary keys, and indexes the coordinates for spatial query — which turns a day of data wrangling into a search that returns in about thirty seconds.
What is an RF environment scan?
A snapshot of the spectrum at a location. You pick the bands — VHF, UHF, ISM, DECT, Wi-Fi, C-band, 5 and 6 GHz, microwave — set a radius, and choose your sources, and F3C catalogs every known transmitter in that area with frequency, power, distance, and bearing.
That scan is the foundation for coordination: you cannot assign frequencies safely until you know what is already on the air.
Can it account for sources that aren't in the FCC database?
Yes. In-ear monitors, production walkies, and intercom systems never appear in a federal licensing record, and they are exactly the equipment most likely to collide with yours. F3C lets you enter those ambient sources by hand and carries them into the intermodulation analysis alongside licensed transmitters, so mixing products are caught during planning rather than during the show.
Who is F3C built for?
Frequency coordinators, broadcast and live event engineers, spectrum managers, and the in-house teams responsible for RF at venues that host many events a year. It grew out of Fusion Collective's own coordination work on productions — up to and including Presidential debates — where the spectrum plan has to be right the first time.
Want to see F3C? Ask, and we'll show you.
Tell us what you coordinate and we will walk you through the system against a venue and a band you actually care about — not a slide deck.