<nav class="guide-toc" aria-label="Table of contents">
    <p class="toc-label">In this guide</p>
    <ol>
      <li><a href="#do-you-need-a-license">Do you need a license?</a></li>
      <li><a href="#station-types">Types of ground stations</a></li>
      <li><a href="#fcc-licensing">How to file FCC Form 312 for ground station licensing</a></li>
      <li><a href="#frequency-coordination">Frequency coordination</a></li>
      <li><a href="#esims">Earth Stations in Motion</a></li>
      <li><a href="#blanket-licensing">Blanket licensing</a></li>
      <li><a href="#ntia">NTIA and federal spectrum coordination</a></li>
      <li><a href="#local-permits">Local permits, zoning, and FAA</a></li>
      <li><a href="#gaas">Ground Station as a Service</a></li>
      <li><a href="#costs">Ground station licensing costs breakdown</a></li>
      <li><a href="#common-mistakes">Common mistakes</a></li>
      <li><a href="#faq">Ground station licensing FAQs</a></li>
    </ol>
  </nav>

  <!-- Do you need a license? -->
  <section id="do-you-need-a-license" class="guide-section">
    <h2>Do You Need a License?</h2>
    <p>The answer depends on one question: <strong>does your ground station transmit?</strong></p>

    <div class="decision-table-wrap">
      <table class="decision-table">
        <thead>
          <tr>
            <th>Station type</th>
            <th>Transmits?</th>
            <th>FCC license required?</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td>Transmit/receive earth station</td>
            <td>Yes</td>
            <td><strong>Yes.</strong> File Form 312 + Schedule B</td>
          </tr>
          <tr>
            <td>Receive-only earth station</td>
            <td>No</td>
            <td><strong>No</strong>, but optional registration provides interference protection</td>
          </tr>
          <tr>
            <td>Consumer satellite dish (≤1m)</td>
            <td>No</td>
            <td><strong>No.</strong> Exempt from licensing</td>
          </tr>
          <tr>
            <td>VSAT remote terminal</td>
            <td>Yes</td>
            <td>Covered under network operator's <strong>blanket license</strong></td>
          </tr>
          <tr>
            <td>ESIM (ship, aircraft, vehicle)</td>
            <td>Yes</td>
            <td><strong>Yes</strong>, blanket license under 47 CFR 25.228</td>
          </tr>
          <tr>
            <td>Amateur satellite station</td>
            <td>Yes</td>
            <td>Covered under <strong>Part 97</strong> amateur radio license ($35)</td>
          </tr>
        </tbody>
      </table>
    </div>

    <p>Receive-only stations, including ground-based remote sensing data receive stations, can operate without any FCC authorization. However, registering with the FCC (Form 312 + Schedule B, 15-year term, automatically granted) gives you legal protection against interference from terrestrial microwave stations in shared frequency bands. Without registration, you have no right to interference protection.</p>
  </section>

  <!-- Station types -->
  <section id="station-types" class="guide-section">
    <h2>Types of Ground Stations</h2>
    <p>Ground stations range from handheld amateur setups to multi-million-dollar teleport complexes, and the licensing requirements scale accordingly:</p>

    <h3>Fixed Satellite Service (FSS) earth stations</h3>
    <p>Traditional large-dish stations used for video distribution, enterprise connectivity, and satellite backhaul. Antenna sizes range from 2.4 meters (Ku-band) to 18+ meters (C-band). Licensed individually at a specific location via Form 312. These are the workhorses of the satellite industry. Teleport operators like SES, Intelsat, and Telesat run networks of these facilities worldwide.</p>

    <h3>Gateway and teleport facilities</h3>
    <p>Multi-antenna complexes that serve as the ground-side hub for satellite networks. No separate "gateway license" exists; each antenna is licensed as a standard earth station, with multiple antennas covered under one authorization using multiple Schedule B pages. NGSO constellation operators like SpaceX (Starlink) and Amazon (Kuiper) need dozens of geographically distributed gateway sites to maintain continuous connectivity as satellites pass overhead. Starlink operates an extensive global gateway network (exact count not publicly confirmed, but FCC filings list over 100 U.S. sites).</p>

    <h3>Earth Stations in Motion (ESIMs)</h3>
    <p>Terminals that operate while moving: on ships (<a href="/the-downlink/glossary/#term-esim">ESV</a>), aircraft (ESAA), and vehicles (VMES). Blanket-licensed by terminal type rather than location, since they don't stay in one place. Governed by <strong>47 CFR 25.228</strong>. All three categories require a U.S. point of contact available 24/7 with authority to cease emissions.</p>

    <h3>VSAT networks</h3>
    <p>Hub-and-spoke satellite networks where small remote terminals (0.75m–2.4m dishes) communicate through a central hub station. The network operator holds a blanket license covering the hub plus all remote terminal types. Individual remote sites don't need separate licenses. Used for enterprise WAN, ATM/POS networks, SCADA monitoring, maritime connectivity, and rural broadband.</p>

    <h3>TT&C stations</h3>
    <p>Tracking, <a href="/the-downlink/glossary/#term-telemetry">Telemetry</a>, and Command stations monitor satellite health, track position, and send commands. Essential during launch, orbit-raising, on-orbit operations, and decommissioning. Licensed on the same Form 312 as other earth stations, with TT&C-specific parameters in Schedule B. A subset of gateway sites often doubles as TT&C stations.</p>

    <h3>Remote sensing receive stations</h3>
    <p>Stations that only receive data <a href="/the-downlink/glossary/#term-downlink">downlinked</a> from Earth observation satellites. No FCC license required, though optional registration provides interference protection. Note that the satellite system operator still needs a <a href="/the-downlink/noaa-remote-sensing-license/">NOAA remote sensing license</a> for the space segment.</p>

    <h3>Amateur satellite stations</h3>
    <p>Any FCC amateur radio licensee (Technician class or higher, $35 exam fee) can operate a satellite ground station under <strong>Part 97</strong>. No commercial use permitted. Equipment costs range from a few hundred dollars for a handheld with a directional antenna to several thousand for a motorized tracking station. AMSAT coordinates amateur satellite operations.</p>

    <h3>Direct-to-device ground infrastructure</h3>
    <p>An emerging category supporting satellite-to-smartphone services under the FCC's Supplemental Coverage from Space (SCS) framework. Consumer handsets are "licensed by rule" (no individual device licensing). But the feeder link gateway stations connecting satellites to the mobile core network still need standard earth station licensing. SpaceX and T-Mobile received the first SCS license in December 2025.</p>
  </section>

  <!-- FCC licensing -->
  <section id="fcc-licensing" class="guide-section">
    <h2>How to File FCC Form 312 for Ground Station Licensing</h2>
    <p>The <a href="/the-downlink/glossary/#term-fcc">FCC</a> licenses <a href="/the-downlink/glossary/#term-earth-station">earth stations</a> under <strong>47 CFR <a href="/the-downlink/glossary/#term-part-25">Part 25</a></strong>. All applications are filed electronically on <strong>Form 312</strong> with <strong>Schedule B</strong> (the technical exhibit) through the <strong>International Communications Filing System (ICFS)</strong>.</p>

    <h3>What Schedule B captures</h3>
    <p>Schedule B is the technical core of your application. It includes your frequency assignments, <a href="/the-downlink/glossary/#term-eirp">EIRP</a> (effective isotropic radiated power), antenna characteristics, emission designators, and <strong>points of communication</strong> (the specific satellites your station will talk to). Each antenna at your site gets its own Schedule B page.</p>

    <h3>Two processing tracks</h3>
    <ul>
      <li><strong>Routine processing:</strong> Applications that meet all Part 25 Subpart C technical standards (antenna performance per 25.209, EIRP density limits per 25.218). Placed on public notice within 30 days, then a 30-day comment period. Typically granted in <strong>2 to 6 months</strong>.</li>
      <li><strong>Non-routine processing.</strong> Applications with non-conforming antennas, waiver requests, or non-standard parameters. Requires individual technical review under 25.220. No fixed timeline, and can take significantly longer.</li>
    </ul>

    <h3>The simplified path: Form 312EZ</h3>
    <p>For single fixed stations communicating with GSO satellites in standard frequency bands (C-band uplink, Ku-band uplink, Ka-band uplink) that meet all technical criteria: <strong>deemed granted 35 days after public notice</strong> if no objection is filed. This is the fastest path to authorization.</p>

    <h3>What you need before filing</h3>
    <ul>
      <li><strong>Frequency coordination report.</strong> Required for all transmitting stations in bands shared with terrestrial services. Must be less than 6 months old at filing. Prepared by an FCC-certified frequency coordinator.</li>
      <li><strong>Radiation hazard analysis:</strong> Demonstrates RF exposure compliance per FCC OET Bulletin 65. Required for all transmitting stations.</li>
      <li><strong>Antenna radiation patterns</strong>, required for Ka-band GSO FSS transmit applications.</li>
    </ul>

    <h3>License term</h3>
    <p>Earth station licenses are valid for <strong>15 years</strong> from grant (the proposed Space Modernization <a href="/the-downlink/glossary/#term-nprm">rulemaking</a> would extend this to 20 years). Renewals are filed on Form 312R no earlier than 90 days and no later than 30 days before expiration.</p>
  </section>

  <!-- Frequency coordination -->
  <section id="frequency-coordination" class="guide-section">
    <h2>Frequency Coordination</h2>
    <p>If your earth station operates in a frequency band shared with terrestrial microwave services, you must coordinate before filing your FCC application. This is governed by <strong>47 CFR 25.203</strong>.</p>

    <h3>How it works</h3>
    <ol>
      <li>Hire an <strong>FCC-recognized frequency coordinator</strong> (firms like Comsearch, Micronet Communications, or Lumos).</li>
      <li>The coordinator computes <strong>great circle coordination distance contours</strong> for your proposed station per 47 CFR 25.251.</li>
      <li>They perform <strong>interference analysis</strong> for every terrestrial station within the contour, both existing stations and pending applications.</li>
      <li>The result is a <strong>Frequency Coordination and Interference Analysis Report</strong> submitted as an exhibit with your Form 312.</li>
    </ol>
    <p>The report must be <strong>less than 6 months old</strong> at the time of filing. If your application sits too long before submission, you'll need to redo the coordination, an expensive delay.</p>

    <h3>Which bands require coordination?</h3>
    <div class="decision-table-wrap">
      <table class="decision-table">
        <thead>
          <tr>
            <th>Band</th>
            <th>Frequencies</th>
            <th>Coordination required?</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><a href="/the-downlink/glossary/#term-c-band">C-band</a></td>
            <td>3.7–4.2 GHz / 5.925–6.425 GHz</td>
            <td><strong>Yes.</strong> Shared with terrestrial fixed service</td>
          </tr>
          <tr>
            <td><a href="/the-downlink/glossary/#term-ku-band">Ku-band</a></td>
            <td>11.7–12.2 GHz / 14.0–14.5 GHz</td>
            <td><strong>Yes</strong>, shared with terrestrial FS (no NTIA coordination)</td>
          </tr>
          <tr>
            <td><a href="/the-downlink/glossary/#term-ka-band">Ka-band</a> (standard)</td>
            <td>18.3–20.2 GHz / 28.35–30.0 GHz</td>
            <td><strong>No.</strong> Not shared with terrestrial services</td>
          </tr>
          <tr>
            <td>Ka-band (shared)</td>
            <td>20.2–21.2 GHz / 30–31 GHz</td>
            <td><strong>Yes</strong>, shared with government systems (requires NTIA)</td>
          </tr>
          <tr>
            <td><a href="/the-downlink/glossary/#term-s-band">S-band</a></td>
            <td>2.025–2.110 / 2.200–2.290 GHz</td>
            <td><strong>Yes.</strong> Shared with NASA/DoD (requires NTIA)</td>
          </tr>
          <tr>
            <td><a href="/the-downlink/glossary/#term-v-band">V-band</a></td>
            <td>37.5–51.4 GHz</td>
            <td>Varies by sub-band</td>
          </tr>
        </tbody>
      </table>
    </div>

    <p>Ka-band-only operations in the standard sub-bands are the simplest from a coordination perspective: no terrestrial sharing means no coordination report required.</p>

    <h3>ESIM-specific coordination</h3>
    <p>Earth Stations in Motion in the 14.0–14.2 GHz band must coordinate with NASA if operating within 125 km (ESV/VMES) or radio line of sight (ESAA) of NASA TDRSS facilities. All ESIMs in 14.47–14.5 GHz must protect radio astronomy observatories through NSF coordination.</p>
  </section>

  <!-- ESIMs -->
  <section id="esims" class="guide-section">
    <h2>Earth Stations in Motion</h2>
    <p>ESIMs are mobile terminals that communicate with satellites while in motion. The FCC consolidated ESIM rules under <strong>47 CFR 25.228</strong>, with service-specific requirements layered on top.</p>

    <div class="decision-table-wrap">
      <table class="decision-table">
        <thead>
          <tr>
            <th>Category</th>
            <th>Platform</th>
            <th>Key rule</th>
            <th>Notable requirements</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><strong>ESV</strong></td>
            <td>Ships and vessels</td>
            <td>25.228(e), (h)</td>
            <td>Coordinate within 200 km of U.S. coastline with fixed service operators</td>
          </tr>
          <tr>
            <td><strong>ESAA</strong></td>
            <td>Aircraft</td>
            <td>25.228(f), (i)</td>
            <td>All terminals in U.S. airspace must be FCC-licensed, including non-U.S. aircraft</td>
          </tr>
          <tr>
            <td><strong>VMES</strong></td>
            <td>Land vehicles</td>
            <td>25.228(g), (j)</td>
            <td>Trains, buses, emergency vehicles; must maintain pointing accuracy</td>
          </tr>
        </tbody>
      </table>
    </div>

    <p>All ESIMs are <strong>blanket-licensed</strong>, meaning one authorization covers the entire fleet of terminals. All three categories must maintain a <strong>24/7 U.S. point of contact</strong> with authority to cease emissions if interference occurs. ESIM applicants can designate the FCC's <strong>Permitted Space Station List</strong> as their point of communication, providing flexibility to work with any authorized satellite without amending the license.</p>
  </section>

  <!-- Blanket licensing -->
  <section id="blanket-licensing" class="guide-section">
    <h2>Blanket Licensing</h2>
    <p>Blanket licensing lets an operator cover multiple terminals of the same type under a single FCC authorization, instead of licensing each site individually.</p>

    <h3>Who uses it</h3>
    <ul>
      <li><strong>VSAT network operators.</strong> The primary use case. One license covers the hub station(s) plus all remote terminals in the network. Individual remote sites don't need separate licenses.</li>
      <li><strong>ESIM operators:</strong> All ESIMs are blanket-licensed by nature, since they move.</li>
      <li><strong>Direct-to-user terminal operators</strong>, such as Starlink user terminals, which operate under SpaceX's blanket authorization.</li>
    </ul>

    <h3>How it works</h3>
    <p>File a single Form 312 with separate Schedule B pages: one for each hub station antenna and one for each different type of remote terminal. Hub stations (typically 5m+) get individual radio station authorizations. Remote terminals get blanket authorization by terminal type. The key requirement: terminals must meet <strong>routine processing criteria</strong> (conforming antennas, standard EIRP density limits). Non-conforming terminals generally must be individually licensed.</p>

    <h3>Why it matters</h3>
    <p>Without blanket licensing, deploying a 10,000-terminal VSAT network would require 10,000 individual license applications. Blanket licensing reduces that to one. It's what makes large-scale commercial satellite networks operationally feasible.</p>
  </section>

  <!-- NTIA -->
  <section id="ntia" class="guide-section">
    <h2>NTIA and Federal Spectrum Coordination</h2>
    <p>When your earth station operates in frequency bands shared between commercial and federal government users, the FCC will not grant your license until coordination with <strong>NTIA</strong> (National Telecommunications and Information Administration) is complete.</p>

    <h3>The process</h3>
    <ol>
      <li>You file Form 312 with the FCC as normal.</li>
      <li>The FCC routes your application to NTIA.</li>
      <li>NTIA's Office of Spectrum Management distributes it to the <strong>IRAC Frequency Assignment Subcommittee</strong>.</li>
      <li>The <strong>Spectrum Planning Subcommittee (SPS)</strong> coordinates with affected federal agencies (DoD, NASA, NOAA).</li>
      <li>SPS reports back to the FCC. The FCC will not act until SPS confirms coordination is accomplished.</li>
    </ol>
    <p>The FCC <strong>strongly encourages</strong> informal pre-coordination with NTIA before filing. Engaging federal agencies early significantly reduces processing delays.</p>

    <h3>Which bands trigger NTIA coordination?</h3>
    <ul>
      <li><strong>S-band</strong> (2.025–2.290 GHz), heavily used by <a href="/the-downlink/glossary/#term-nasa">NASA</a> and DoD for space operations TT&C</li>
      <li><strong>X-band</strong> (8.025–8.400 GHz). Primarily government; commercial access very limited</li>
      <li><strong>Ka-band shared segments</strong> (20.2–21.2 GHz / 30–31 GHz): government satellite systems</li>
    </ul>
    <p>Standard Ku-band and Ka-band commercial sub-bands do <strong>not</strong> require NTIA coordination. Those bands only require coordination with terrestrial services under 25.203.</p>

    <h3>The C-band transition</h3>
    <p>The FCC's 3.7 GHz Order (FCC 20-22) repurposed 280 MHz of C-band spectrum from satellite downlink to 5G, compressing FSS operations into the upper 220 MHz (3.98–4.2 GHz). The transition deadline was December 2025. As of early 2026, the FCC has proposed repurposing an additional 100–180 MHz of the upper C-band for terrestrial wireless, with an <strong>application freeze</strong> on new or modified earth station filings across 3.7–4.2 GHz currently in effect. If you're planning a C-band earth station, this is a moving target. Track GN Docket No. 25-59.</p>
  </section>

  <!-- Local permits -->
  <section id="local-permits" class="guide-section">
    <h2>Local Permits, Zoning, and FAA</h2>
    <p>An FCC license authorizes your radio operations. Building the physical station may require additional approvals.</p>

    <h3>Federal preemption of local zoning</h3>
    <p>The FCC limits what local governments can restrict:</p>
    <ul>
      <li><strong>Antennas ≤2 meters</strong> in commercial/industrial zones: local regulations are <strong>presumed unreasonable and preempted</strong> (47 CFR 25.104)</li>
      <li><strong>Antennas ≤1 meter</strong> in any zone, including residential, protected under the <strong>OTARD rule</strong> (47 CFR 1.4000)</li>
      <li><strong>Larger commercial antennas.</strong> Local zoning applies, but must be "reasonable" and serve a clearly defined health, safety, or aesthetic objective</li>
    </ul>

    <h3>What local permits you may need</h3>
    <ul>
      <li><strong>Building permits</strong> for antenna foundations, equipment shelters, fencing</li>
      <li><strong>Conditional use / special use permits</strong> in zones where telecom facilities aren't permitted by right</li>
      <li><strong>Environmental review:</strong> NEPA compliance if the site is in sensitive areas (wetlands, historic sites, tribal lands)</li>
    </ul>
    <p>The FCC does not require a construction permit for earth stations. Construction may begin before license grant, <strong>at your own risk</strong>.</p>

    <h3><a href="/the-downlink/glossary/#term-faa">FAA</a> coordination</h3>
    <p>FAA notification (Form 7460-1) is required if your antenna structure:</p>
    <ul>
      <li>Exceeds <strong>200 feet above ground level</strong>, or</li>
      <li>Penetrates an <strong>imaginary surface</strong> extending from a nearby public-use or military airport runway</li>
    </ul>
    <p>File at least <strong>45 days before construction</strong> via oeaaa.faa.gov. The FAA conducts an aeronautical study and issues a Determination of No Hazard (or Hazard, which may require obstruction marking and lighting). Most earth station antennas are well under 200 feet, so FAA review is typically triggered only for stations near airports.</p>
  </section>

  <!-- GaaS -->
  <section id="gaas" class="guide-section">
    <h2>Ground Station as a Service</h2>
    <p>You don't have to build a ground station to use one. Ground Station as a Service (GaaS) providers hold the earth station licenses and offer antenna time on demand.</p>

    <h3>Major providers</h3>
    <ul>
      <li><strong>AWS Ground Station.</strong> Pay-per-minute antenna time integrated with AWS cloud. Narrowband (&lt;54 MHz): $3–$10/min. Wideband (54+ MHz): $10–$22/min. Data ingests directly into S3/EC2 with no backhaul costs. Partnered with KSAT for global coverage.</li>
      <li><strong>KSAT</strong> (Kongsberg Satellite Services): ~25 ground station sites globally, including polar stations in Svalbard and Antarctica. Serves government, commercial, and scientific missions.</li>
      <li><strong>SSC</strong> (Swedish Space Corporation). Global network including Esrange (Sweden) and stations across multiple continents. Full TT&C and data reception services.</li>
    </ul>
    <p>Microsoft Azure Orbital was retired in October 2024, with antenna assets sold to SLI (an SSC subsidiary).</p>

    <h3>What GaaS changes about licensing</h3>
    <p>The GaaS provider holds the earth station license, not you. As a satellite operator, you need only your <a href="/the-downlink/satellite-licensing-guide/">space station license</a> and market access. GaaS eliminates capital expenditure, site acquisition, local permitting, and frequency coordination. You give up direct control over your ground segment and take on per-minute costs that can exceed own-station economics at high utilization rates. Industry estimates place the GaaS market at over $1 billion and growing rapidly (source: NSR, Euroconsult reports).</p>
  </section>

  <!-- Costs -->
  <section id="costs" class="guide-section">
    <h2>Ground Station Licensing Costs Breakdown</h2>

    <div class="decision-table-wrap">
      <table class="decision-table">
        <thead>
          <tr>
            <th>Cost category</th>
            <th>Range</th>
            <th>Notes</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td>FCC application fee</td>
            <td>$425 – $7,650</td>
            <td>Single-site vs. multi-site; per FCC FY 2025 fee schedule; adjusted annually</td>
          </tr>
          <tr>
            <td>FCC annual regulatory fee</td>
            <td>$575/authorization</td>
            <td>Plus $575 per associated hub station</td>
          </tr>
          <tr>
            <td>Frequency coordination</td>
            <td>$10,000 – $30,000</td>
            <td>Required for C-band, Ku-band; not for Ka-band standard sub-bands</td>
          </tr>
          <tr>
            <td>Small Ku/Ka station (single antenna)</td>
            <td>$200,000 – $700,000</td>
            <td>2.4–4.5m antenna + RF chain + site prep</td>
          </tr>
          <tr>
            <td>Full teleport facility</td>
            <td>$5M – $50M+</td>
            <td>Multiple antennas, C/Ku/Ka, fiber, power, building</td>
          </tr>
          <tr>
            <td>NGSO gateway site</td>
            <td>$2M – $10M+</td>
            <td>10+ tracking antennas; fiber backhaul a major cost driver</td>
          </tr>
          <tr>
            <td>VSAT remote terminal</td>
            <td>$1,000 – $5,000</td>
            <td>Per terminal; hub station $500K–$2M+</td>
          </tr>
          <tr>
            <td>Amateur/educational station</td>
            <td>$2,000 – $50,000</td>
            <td>DIY UHF/VHF to basic S-band receive</td>
          </tr>
          <tr>
            <td>GaaS (AWS Ground Station)</td>
            <td>$3 – $22/min</td>
            <td>Pay-per-use; discounts for annual commitments</td>
          </tr>
          <tr>
            <td>Annual operations (staffed teleport)</td>
            <td>$500K – $5M+</td>
            <td>Staff, power, maintenance, backhaul</td>
          </tr>
        </tbody>
      </table>
    </div>

    <p>The cost asymmetry between filing fees and actual build costs is dramatic. The FCC application fee for a single earth station is a few hundred dollars. The antenna, RF electronics, site preparation, frequency coordination, and fiber backhaul to make it operational can cost hundreds of thousands to millions. For many operators, especially those launching their first satellite, GaaS is the pragmatic starting point.</p>
  </section>

  <!-- Common mistakes -->
  <section id="common-mistakes" class="guide-section">
    <h2>Common Mistakes</h2>
    <p>The FCC publishes its own list of common defects in earth station filings. These are the mistakes that cause the most delays:</p>

    <ol class="mistakes-list">
      <li>
        <strong>Submitting a stale frequency coordination report.</strong>
        The report must be less than 6 months old at filing. If your application preparation drags on, you'll need to redo the coordination at full cost. Time the coordination work to your filing schedule.
      </li>
      <li>
        <strong>Listing the wrong frequency bands.</strong>
        Applicants often list every band their antenna is capable of, rather than the bands actually authorized on their target satellite. Your Schedule B should match the satellite's authorization, not the antenna's spec sheet.
      </li>
      <li>
        <strong>Missing the radiation hazard analysis.</strong>
        Required for every transmitting station. Omitting it is an automatic deficiency that sends your application back to the queue.
      </li>
      <li>
        <strong>Inconsistent technical parameters.</strong>
        The FCC flags applications where maximum EIRP density per carrier is listed as less than average EIRP density, a mathematical impossibility. Double-check your Schedule B numbers.
      </li>
      <li>
        <strong>Skipping NTIA pre-coordination in shared bands.</strong>
        If you're operating in S-band, X-band, or shared Ka-band segments, the FCC will not grant your license until NTIA coordination is complete. Engaging NTIA informally before filing can save months.
      </li>
      <li>
        <strong>Assuming receive-only means zero paperwork.</strong>
        You don't need a license, but without registration, you have no legal protection against interference. If you're investing significant capital in a receive station, register it.
      </li>
      <li>
        <strong>Ignoring local zoning for large antennas.</strong>
        The FCC preempts local rules for small antennas, but a 9-meter C-band dish needs local approval. Some operators discover zoning restrictions after they've already poured the foundation.
      </li>
      <li>
        <strong>Not budgeting for frequency coordination.</strong>
        At $10,000–$30,000 per report, coordination is a material cost, especially if you need to redo it because the first report expired. Ka-band standard sub-bands avoid this entirely.
      </li>
    </ol>
  </section>

  <!-- FAQ -->
  <section id="faq" class="guide-section">
    <h2>Ground Station Licensing FAQs: FCC Rules &amp; Costs</h2>

    <div class="faq-list">
      <details class="faq-item">
        <summary>Do I need a license to operate a satellite ground station?</summary>
        <p>If your ground station transmits, yes. You need an FCC earth station license filed on Form 312 with Schedule B through ICFS. Receive-only earth stations do not require a license, but can optionally register with the FCC to receive interference protection from terrestrial microwave stations in shared frequency bands.</p>
      </details>

      <details class="faq-item">
        <summary>How much does it cost to license an earth station?</summary>
        <p>FCC application processing fees range from roughly $425 for a single-site transmit/receive station to $7,650 for multi-site applications. Annual regulatory fees are $575 per authorization. Beyond filing fees, frequency coordination reports cost $10,000 to $30,000, and total ground station construction costs range from $200,000 for a small Ku-band station to $50 million or more for a full teleport.</p>
      </details>

      <details class="faq-item">
        <summary>How long does it take to get an earth station license?</summary>
        <p>There is no statutory deadline. Routine applications typically process in 2 to 6 months. The simplified Form 312EZ path is deemed granted 35 days after public notice if no objection is filed. Non-routine applications can take significantly longer.</p>
      </details>

      <details class="faq-item">
        <summary>What is blanket licensing?</summary>
        <p>Blanket licensing covers multiple terminals of the same type under a single FCC authorization. It's used for VSAT networks (one license for the hub plus all remotes) and ESIMs that move between locations. Terminals must meet routine processing criteria.</p>
      </details>

      <details class="faq-item">
        <summary>What is the difference between a fixed earth station and an ESIM?</summary>
        <p>A fixed earth station operates at a specific location and is licensed on a site-by-site basis. An ESIM operates while moving and is blanket-licensed by terminal type. ESIMs come in three categories: ESV (maritime), ESAA (aeronautical), and VMES (land-mobile), all governed by 47 CFR 25.228.</p>
      </details>

      <details class="faq-item">
        <summary>Do I need local permits to build a ground station?</summary>
        <p>Possibly. The FCC preempts local zoning for antennas 2 meters or smaller in commercial/industrial zones and 1 meter or smaller in any zone. Larger antennas are subject to local zoning, building permits, and potentially FAA obstruction review. Environmental review under NEPA may be required for sensitive sites.</p>
      </details>

      <details class="faq-item">
        <summary>Can I skip building a ground station and use Ground Station as a Service?</summary>
        <p>Yes. GaaS providers like AWS Ground Station, KSAT, and SSC hold the licenses and offer antenna time on a pay-per-minute basis. AWS charges $3–$22/min depending on bandwidth. GaaS eliminates capital expenditure and licensing burden, but at high utilization rates, your own station may be more cost-effective.</p>
      </details>

      <details class="faq-item">
        <summary>What's changing with the FCC's Space Modernization rulemaking?</summary>
        <p>The proposed Part 100 framework would replace Part 25 with performance-based standards, introduce Nationwide Non-Site Licenses for certain earth stations (registration instead of full licensing), extend license terms to 20 years, and create streamlined processing paths. Comment periods closed in early 2026; no final rule has been adopted yet.</p>
      </details>
    </div>
  </section>

  <!-- Further Reading -->
  <section class="guide-section guide-further-reading">
    <h2>Further Reading</h2>
    <ul>
      <li><a href="/the-downlink/satellite-licensing-guide/">How Satellite Licensing Works: A Complete Guide</a>. The companion guide covering FCC, FAA, NOAA, and ITU licensing for the space segment</li>
      <li><a href="/the-downlink/glossary/">Space Regulatory Glossary</a>: Definitions for the terminology used throughout this guide</li>
      <li><a href="/the-downlink/the-fcc-five-year-deorbit-rule/">The FCC 5-Year Deorbit Rule</a>, covering how the FCC's orbital debris mandate affects LEO mission planning</li>
      <li><a href="/the-downlink/faa-part-450-explained/">FAA Part 450: The New Era of Launch Licensing</a>. The performance-based framework for launch and reentry</li>
      <li><a href="/the-downlink/us-space-regulatory-compliance/">The Operator's Playbook</a>. The complete four-agency regulatory guide for commercial space missions</li>
      <li><a href="/the-downlink/noaa-remote-sensing-license/">NOAA Remote Sensing License</a>. What Part 960 actually requires for commercial Earth observation</li>
      <li><a href="/the-downlink/the-trust-problem/">The Trust Problem</a>. Why AI-generated regulatory data needs architectural safeguards</li>
      <li><a href="/downloads/ground-station-licensing-guide-viventine.pdf" download>Download this guide as PDF</a></li>
    </ul>

    <hr />

    <p class="guide-references-label"><strong>Key Regulatory References</strong></p>
    <ul class="guide-references">
      <li><a href="https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25" rel="noopener noreferrer" target="_blank">47 CFR Part 25 -Satellite Communications (FCC)</a></li>
      <li><a href="https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25/subpart-C/section-25.228" rel="noopener noreferrer" target="_blank">47 CFR 25.228 -ESIM Operating and Coordination Requirements</a></li>
      <li><a href="https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25/subpart-C/section-25.203" rel="noopener noreferrer" target="_blank">47 CFR 25.203 -Choice of Sites and Frequencies</a></li>
      <li><a href="https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25/subpart-A/section-25.104" rel="noopener noreferrer" target="_blank">47 CFR 25.104 -Preemption of Local Zoning</a></li>
      <li><a href="https://www.fcc.gov/space/overview-earth-station-licensing-and-license-contents" rel="noopener noreferrer" target="_blank">FCC Overview of Earth Station Licensing</a></li>
      <li><a href="https://www.fcc.gov/general/common-defects-earth-station-application-filings" rel="noopener noreferrer" target="_blank">FCC Common Defects in Earth Station Filings</a></li>
      <li><a href="https://docs.fcc.gov/public/attachments/FCC-25-69A1.pdf" rel="noopener noreferrer" target="_blank">FCC-25-69 -Space Modernization NPRM</a></li>
    </ul>
  </section>

</div>