Telecom Tower REITs · FCC
FCC Data Hub Licensing and Tower Data
Datadory delivers fcc data hub licensing and tower data data covering the federal Antenna Structure Registration: roughly 8.7 million positional rows behind 1.09 million FAA no-hazard determinations reaching back to 1990 - coordinates, heights, registrants and treatments, rebuilt weekly with daily change files. Get a sample cut to your states.
API, files, or your warehouse. Daily, weekly, or hourly.
- Where it covers
- United States and territories - every FCC-registered antenna structure, with city and state on determination rows and coordinates nationwide; the federal floor beneath the trade count of roughly 158,500 purpose-built US towers
- How far back
- Registrations reach back to 1990 - the earliest working-set record dated January 5, 1990 - with the complete snapshot rebuilt weekly (files stamped August 15-16, 2026) and per-weekday change packages landing between rebuilds
- How fine
- One row per registration action, coordinate set, entity or hazard determination - nothing pre-aggregated, so collocation counts and state-by-state height histograms are group-bys, not estimates
What is the FCC Data Hub Licensing and Tower Data?
The regulator's file cabinet turns out to be the deepest single well of American tower ground truth. data.fcc.gov hosts the Universal Licensing System bulk archive under /download/pub/uls/, and inside it the Antenna Structure Registration - the federal ledger of every registered tower, mast and rooftop-mounted structure in the United States and its territories.
Scale first. a_tower.zip (208 MB zipped) unpacks into pipe-delimited .dat files totaling roughly 8.7 million rows: CO.dat with 1.49 million coordinate rows in NAD-27 degrees-minutes-seconds plus earth-centered X/Y/Z, EN.dat with 2.77 million entity rows naming registrants down to contact and address, HS.dat with 2.49 million history rows, RA.dat with 1.47 million registration actions, and AT.dat's 59,727 application attachments. Beside it, d_tower.zip (56 MB) packages the obstruction-evaluation flow - 1.09 million determination-of-no-hazard cases spread over 3.4 million DE/DP/DR rows, each with position, heights and registrant.
Within Datadory's catalog of 1,744 datasets averaging 7.81, this record scores 9 out of 10 - the highest in the telecom tower REITs slice - on verified definitions, shipped samples and public-domain rights. Get a sample of this dataset cut to your states before anything else.
What do sample rows look like?
One line, one positional record, no header row:
DE|89-ASO-2235-OE||36|4|5.20||129845.20|89|20|31.20||321631.20|100.6|57.9|158.5|01/05/1990|||01/22/1990||DYERSBURG|TN|MAXCELL TELECOM PLUS, INC.
CO|APP|A0099939|1204700|3482621|T|47|48|9.0|N|172089.0|103|16|52.7|W|371812.7||
AT|APP|A0463140|1250054|2918248|O|Completed FAA 7460-1|09/08/2005Read the anatomy rather than the raw strings. Each line opens with a file code - DE for a determination, CO for coordinates, AT for an application treatment, EN for an entity, HS for history - and everything after the pipes lands in fixed order. The determination row carries the case number (89-ASO-2235-OE), the DMS position, three height measures, two dates, city, state and registrant: a complete vertical fingerprint of one structure in one line. The coordinate row adds the earth-centered triplet, so a GIS load needs no projection math.
Datadory ships these flattened into typed tables - one row per determination, per coordinate set, per entity - with the dictionary unchanged and decimal-degree conversions alongside the survey originals. The Dyersburg line above is also the oldest record in the working set, filed January 5, 1990 by MAXCELL TELECOM PLUS, INC.: thirty-six years of American vertical infrastructure in one continuous format.
Which fields does the dictionary define?
Ten fields carry every registry record, definitions verified against actual .dat rows during the August 2026 pass:
- file_code - the record type switch: AT, CO, EN, HS, RA, DE. Parse order follows it.
- file_number - the ASR identifier in the
AA-XX-YYYY-OEpattern. One string joins a structure's coordinates, entities, history and determinations. - latitude / longitude in DMS - NAD-27 degrees, minutes, decimal seconds and hemisphere, the survey-form position every conversion starts from.
- geocentric X/Y/Z - the earth-centered triplet appended in CO.dat, pre-computed so distance and visibility math skips the projection step.
- registration_date - MM/DD/YYYY, the axis any build-out series runs on.
- city / state - uppercase locality from the determination files, the coarse filter before coordinates take over.
- overall_height_ft - height above ground level alongside ground elevation and height with appurtenances.
- registrant_name - the landlord of record from EN.dat and DE.dat.
- treatment_code - FAA 7460-1 obstruction paperwork per application.
Folded under additional fields on request: HS history rows, RA actions, environmental notices, condition codes, the l_cell.zip cellular-license tables and the a_lease.zip spectrum-manager leases that tie tenants to structures. Derived decimal-degree columns ride along on every delivery.
Where does coverage reach, and at what grain?
Geography - the United States and its territories, every FCC-registered antenna structure. Set against the trade's roughly 158,500 purpose-built US towers, the registry nets far more: buildings, rooftops, water tanks and poles that never surface in commercial inventories still register here.
Temporal - back to 1990, with the earliest working-set registration dated January 5, 1990. Freshness is structural rather than aspirational: the complete snapshot rebuilds weekly - files stamped August 15-16, 2026 during cataloging - and per-weekday change packages land between rebuilds, giving deterministic delta handling no scraped page can match.
Granularity - one row per registration action, coordinate set, entity or hazard determination. Nothing arrives pre-aggregated, so collocation counts, state-by-state height histograms and registrant league tables are group-bys rather than estimates.
Where it ranks among its neighbors: best telecom tower REITs datasets, with the pooled view on the telecom tower REITs data hub.
How is the data delivered through Datadory?
API, files, or your warehouse. Daily, weekly, or hourly.
The upstream archive rebuilds weekly with daily change files; your delivery cadence gets set separately, to match the decision being fed. Rows arrive typed and keyed on the ASR file number, so this quarter's pull joins last quarter's without hand-mending - and when a column shifts or a registrant renames, the change ships flagged rather than discovered mid-model.
Every delivery flattens the headerless positional extracts into tables with the field dictionary above unchanged, decimal-degree conversions beside the DMS originals, and sample rows for validation before the first join. Name the states, record families and cadence when you request a sample of this dataset; the ongoing arrangement follows once the rows validate.
Who builds on FCC registry data, and for what?
Six jobs the registry earns its keep on:
- National inventory construction - every registered structure with coordinates, heights and owners in one keyed table. It anchors the best telecom tower REITs datasets ranking for exactly this reason: it is the only record attributing structures to entities at national scale.
- Registered-versus-active analysis - registry steel joined against observed radios, the disagreement itself the finding.
- Ownership rollups - 2.77 million entity rows grouped by registrant into who-holds-what tables, or worked as outreach lists.
- Collocation screening - height bands, localities and determination status shortlist structures before an engineer ever opens a CAD tool.
- Build-signal research - registration activity through time as physical-capex evidence beside REIT disclosure.
- Competitor mapping - rivals' filed structures visible ahead of earnings commentary.
Each job maps to a persona below, and the sample validates whichever one you came for.
Which personas get the most value?
Competitive intelligence and product teams see filings before commentary: rival structures, heights and registrations land in the registry quarters before they reach an investor deck.
Investors and quants read registration flows as infrastructure-build evidence - a public-domain series continuous since 1990.
Data scientists get stable coordinate-height-entity features on a single identifier spine.
Market researchers count structures by state and height band with federal denominators. Sales teams turn entity rows into call lists, and journalists, academics and students cite government data with no licensing friction.
The common thread: everyone who needs to know what steel exists and who filed it starts here, whatever they join onto it next.
How does it compare within telecom tower REITs data?
This record anchors the slice; the honest differences are about shape and scope:
- FCC Open Data Portal - Wireless Datasets - the query-first sibling: a SODA API over about 56 hosted tables, JSON and CSV out, but no ASR registry. The head-to-head runs in the Data Hub vs Open Data Portal comparison.
- TowerMaps US Cell Tower Database - 600,000-plus consolidated commercial sites with owner-side commerce: availability, zoning, sales agents. The market's own book beside the regulator's ledger.
- OpenCellID Bulk Downloads - millions of observed cells worldwide; proves which filed structures actually carry live radios.
If the job starts 'enumerate American steel,' start here; if it starts 'query one table cheaply,' the portal; if it starts 'who owns and sells the structure,' TowerMaps.
What should you know before requesting a sample?
Four things, stated plainly.
First, the files are headerless and positional. Parsing them yourself means writing a positional reader against undocumented layout pages - www.fcc.gov returned 403 to scripted clients throughout research, so field meanings here were verified by inspecting real rows. Datadory ships the parse done, with the dictionary attached.
Second, two access caveats survive at the edges: the legacy License View JSON API now redirects to www.fcc.gov and returns Akamai Access Denied, and some l_*.zip license files respond 302 to plain curl clients. The bulk zips remain the reliable path.
Third, cells of paperwork are not towers - a structure accrues many rows across CO, EN, HS and DE files, and deduplication onto physical structures is part of the delivery, not your homework.
Fourth, rights are clean: general public catalog under 17 USC 105, redistribution permitted without attribution. Get a sample scoped to your states and record families before anything is scheduled.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| Field | Type | Definition | Example |
|---|---|---|---|
file_code | enum | Record type switch opening every pipe-delimited row: AT attachment, CO coordinates, EN entity, HS history, RA action, DE determination. | CO |
file_number | string | ASR identifier in the AA-XX-YYYY-OE pattern - the spine joining a structure's coordinates, entities, history and determinations. | 89-ASO-2235-OE |
lat_deg / min / sec / hemi | number | NAD-27 latitude in degrees, minutes, decimal seconds and hemisphere, carried in CO.dat and echoed on determinations. | 47|48|9.0|N |
lon_deg / min / sec / hemi | number | NAD-27 longitude in the same survey form - the pair every map drop starts from after conversion. | 103|16|52.7|W |
geocentric_x / y / z | geo | Earth-centered Cartesian triplet appended after the DMS pair in CO.dat, pre-computed so GIS loads skip projection math. | 371812.7 |
registration_date | date | Registration or determination date in MM/DD/YYYY form - the axis any build-out time series runs on. | 01/05/1990 |
city / state | string | Uppercase structure locality from the determination files - the coarse filter before coordinates take over. | DYERSBURG|TN |
heights_ft | number | Overall height above ground level alongside ground elevation and height with appurtenances on determination rows. | 100.6|57.9|158.5 |
registrant_name | string | Owner or applicant entity from EN.dat and DE.dat - the landlord-of-record key ownership rollups join on. | MAXCELL TELECOM PLUS, INC. |
treatment_code | string | Attachment treatment code in AT.dat with description text - the FAA 7460-1 obstruction paperwork trail. | O|Completed FAA 7460-1 |
Additional fields on request | - | HS history rows (2.49M), RA registration actions (1.47M), EC/RE environmental notices, RS/SC codes, l_cell.zip cellular licenses, a_lease.zip spectrum-manager leases, plus derived decimal-degree columns - spellings locked against live records at sampling. | - |
Coverage summary
| Dimension | Coverage |
|---|---|
| Geographic | United States and territories - every FCC-registered antenna structure, city and state on determination rows; the federal floor beneath the ~158,500 purpose-built US tower trade count |
| Temporal | Registrations from January 5, 1990 forward; complete snapshot rebuilt weekly (files stamped August 15-16, 2026) with per-weekday change packages between rebuilds |
| Granularity | One row per registration action, coordinate set, entity or hazard determination - unaggregated, so histograms and league tables are group-bys |
| Scale | a_tower.zip 208 MB (~8.7M rows, nine .dat files); d_tower.zip 56 MB (3.4M determination rows, 1.09M cases); l_cell.zip 24.8 MB; a_lease.zip |
What teams do with it
- National tower inventory construction Assemble every registered structure - coordinates, heights, owners - into one keyed inventory. This is the only national-scale record attributing structures to owning entities.
- Registered-versus-active gap analysis Join registry steel against observed cells from OpenCellID extracts; structures with no measurable radio, and radios on no listed structure, are both findings.
- Ownership rollups and outreach Group the 2.77 million-row entity files by registrant to size who holds what, or turn the entity table into owner and applicant outreach lists.
- Collocation screening and siting studies Filter by height band, locality and determination status to shortlist structures where a new attachment plausibly clears obstruction review.
- Infrastructure-build signal work Registration activity through time reads as physical capex evidence - a ground-truth series to set beside REIT disclosure and guidance.
- RF planning and propagation features Coordinates, heights and geocentric values drop straight into coverage and interference models as typed physical-layer inputs.
Questions buyers ask
What does the FCC Data Hub licensing and tower data contain?
The Antenna Structure Registration as bulk files: roughly 8.7 million positional rows across nine .dat components - 1.49 million coordinate rows, 2.77 million registrant entities, 2.49 million history rows and 59,727 treatments - feeding 1.09 million FAA no-hazard determinations, plus cellular-license and lease files.
How many towers are in the FCC data?
Far more than the trade count of roughly 158,500 purpose-built US towers, because registration captures rooftops, water tanks, poles and buildings that commercial inventories skip. The rows document structures behind 1.09 million determination cases, attributed to owning entities at national scale.
Does the FCC data show who owns or operates a tower?
Yes. Entity rows name the registrant of record with company, contact, city, state and ZIP, and determination rows echo the applicant. Spectrum-manager lease registrations tie tenants to structures, which is how tower analysts approximate collocation and tenancy from a public file.
How current is the data?
Structurally fresh: the complete ULS snapshot rebuilds weekly - files were stamped August 15-16, 2026 during cataloging - and per-weekday change packages land between rebuilds. Registrations themselves reach back to January 5, 1990, so one continuous source spans thirty-six years of American steel.
Do I need an access credentials or account?
No. The bulk zips serve from plain HTTP directory listings with no key and no registration, and the data is general public catalog under 17 USC 105. Two caveats: the legacy License View JSON API now returns Akamai Access Denied, and some license zips redirect plain curl clients.
What format does the data arrive in?
Upstream: zip archives of pipe-delimited .dat files with no header row, parsed positionally, accompanied by a counts manifest listing row totals and creation dates. Through Datadory: typed tables with the field dictionary attached, decimal-degree conversions beside the DMS originals, and sample rows for validation.
Can FCC tower records join to my own asset inventory?
They are built for it. Registry rows carry DMS positions plus geocentric X/Y/Z, the ASR file number keys every record type, and entity rows supply registrant names. Most clients match on rounded coordinates within a tolerance, then confirm on file number and registrant.
How does this differ from the commercial tower databases?
Scope and commerce. The registry is exhaustive on filed structures but carries no leasing or availability attributes; consolidations such as TowerMaps attach owner-side commerce and rooftop installs the federal regime excludes. Running both ledgers and diffing them is the honest play.
Notes on this record
- Highest score in the slice 9/10 against a 7.31 slice average across 13 records and a 7.81 catalog mean - verified definitions, shipped samples and public-domain rights.
- Headerless by design Pipe-delimited .dat files parsed positionally, with no published layout docs reachable to scripts - field meanings here were verified against real rows, and the parse ships done.
- Weekly full, daily deltas Complete snapshot rebuilt weekly with per-weekday change packages between - deterministic delta handling no scraped page can offer.
- Rights are clean US Government general public catalog under 17 USC 105 - no key, no registration, commercial redistribution permitted without attribution.
Datasets that pair with this one
- TowerMaps US Cell Tower Database 600,000-plus consolidated sites with availability, zoning and sales agents - run it beside the registry and diff the two ledgers.
- telecom tower REITs data hub The pooled slice view - registries, property layers and market data for the tower complex in one place.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.