X-band and Ka-band carry high-volume Earth observation imagery and science data. L-band carries weather broadcasts and rebroadcasts, while VHF near 137 MHz has been used for lower-rate weather pictures. S-band commonly handles tracking, telemetry and command, although its role depends on the mission. NASA lists Earth-exploration downlinks at 8025–8400 MHz and near-Earth Ka-band downlinks at 25.5–27 GHz. ESA’s published Sentinel-2 configuration illustrates the split: X-band for imagery, S-band for spacecraft control and health information. [1][2]
These are communication bands, not the bands used to observe Earth. Sentinel-1, for example, senses with C-band radar at 5.405 GHz but returns payload data through X-band and an optical relay link. An instrument’s sensing frequency does not identify the receiver needed to download its images. [3]
Table of Contents
Earth Observation Downlink Bands at a Glance
| Data path | Band | Documented example |
|---|---|---|
| Bulk imagery directly to a ground station | X-band | Sentinel-2: 560 Mbit/s payload downlink. NASA lists 8025–8400 MHz for Earth-exploration downlinks. [2][1] |
| High-volume direct downlink or relay-to-ground delivery | Ka-band; optical may serve the spacecraft-to-relay leg | NASA lists 25.5–27 GHz for direct-to-Earth service. ESA describes Sentinel-to-EDRS optical links followed by a Ka-band link to Earth. [1][2] |
| Spacecraft command and housekeeping telemetry | S-band in the cited missions | Sentinel-2: 64 kbit/s uplink and 2 Mbit/s downlink. [2] |
| Polar weather direct broadcast | L-band | WMO lists Metop-B AHRPT at 1701.3 MHz and 3.5 Mbit/s. [4] |
| Geostationary weather rebroadcast | L-band | GOES Rebroadcast: 1686.6 MHz, with two 15.5 Mbit/s streams. [5] |
| Legacy lower-rate weather pictures | VHF near 137 MHz | NOAA POES used Automatic Picture Transmission (APT); this is a historical example, not a current reception target. [6] |
The examples above describe different systems, not interchangeable channels. Service status matters as much as frequency: NOAA’s POES constellation was decommissioned, and its status page is preserved as an archive of operations ending on August 19, 2025. [7]
X-Band for Bulk Imagery
X-band is a common direct-to-Earth choice for large imagery files. NASA’s Near Space Network table lists 8025–8400 MHz for Earth-exploration downlinks and, separately, 8450–8500 MHz for space-research downlinks. The first range spans 375 MHz, calculated by subtracting its endpoints. That is the width of the listed range, not bandwidth available to every satellite or permission to transmit anywhere within it. [1]
Mission documentation must take precedence over a letter-band label. WMO lists Metop-B’s global data service at 7800 MHz and 70 Mbit/s, below the nominal 8 GHz lower edge of X-band in NASA’s general band table. A receiver specified only for 8025–8400 MHz would therefore miss that carrier. [4][1]
For a moving low-orbit satellite, the receive antenna must maintain the required pointing through the pass. With LEO/MEO tracking antennas, the usable frequency range must extend through the complete receive chain, including the antenna feed network, filters and receiver. A suitable reflector alone does not establish compatibility.
Ka-Band for High-Volume Links
Ka-band provides another route for high-volume science data; it is not merely a backup used after an X-band link fills up. NASA lists 25.5–27 GHz for near-Earth direct downlinks and gives a 3.5 Gbit/s NISAR example in its network capability table. That example is mission-specific, not a rate guaranteed by the band. [1]
The relay architecture is different. ESA describes Sentinel spacecraft sending data optically to EDRS, which then relays it to Earth over Ka-band. A Ka-band ground receiver in that arrangement receives the relay satellite, not the Sentinel’s optical transmission. The frequencies for a direct link and a relay link must be checked separately. [2]
NASA’s general table labels Ka as 27–40 GHz, while its service table calls the 25.5–27 GHz near-Earth downlink Ka-band. This difference in naming is another reason to specify numerical coverage rather than buying equipment by band name alone. [1]
S-Band for Control and Telemetry
In the Sentinel examples, S-band carries tracking, telemetry and command rather than the main imagery stream. S-band is not restricted to this role: NASA’s network documentation also includes S-band data-return services. The payload-versus-control split must be established from the mission specification. [2][3][1]
Direction also matters. WMO lists Metop-B telecommand and ranging at 2053.4583 MHz Earth-to-space, with telemetry at 2230 MHz space-to-Earth. These are different links, not two alternative receive channels. A shared reflector can use multiband microwave feedhorns, but each frequency, polarization and transmit/receive interface still needs a matching specification. [4]
L-Band and VHF for Weather Data
GOES Rebroadcast and Sensor Relays
GOES Rebroadcast (GRB) distributes weather products at 1686.6 MHz in L-band. NOAA specifies two 15.5 Mbit/s streams, totaling 31 Mbit/s, using dual polarization and 9.8 or 10.9 MHz per polarization. A dual-polarized feed uses polarization-separation components such as an orthomode transducer; the complete feed must support the required polarization arrangement, not just the center frequency. [5]
GOES also relays measurements from surface platforms through its Data Collection System (DCS). This is a separate service from GRB imagery. NOAA documents the GOES-R-era DCS downlink change from 1696 to 1679 MHz and platform data rates of 300 and 1200 bit/s. A receiver configured for GRB is not automatically a DCS receiver. [5]
Polar Direct Broadcast and Legacy VHF
WMO lists Metop-B AHRPT at 1701.3 MHz, 3.5 Mbit/s and right-hand circular polarization, with a backup carrier at 1707 MHz. Its data-access description identifies AHRPT as a direct-broadcast service. The same page tabulates a 137.1 MHz, 72 kbit/s LRPT design entry but explicitly says LRPT is not available. A frequency table alone is therefore not evidence that a service is transmitting. [4]
NOAA’s older POES documentation describes VHF APT and L-band HRPT, including HRPT at 1698 or 1707 MHz and 665.4 kbit/s. These remain useful examples of weather-link design, but the constellation’s retirement means they should not be presented as currently available NOAA reception services. [6][7]
Where Ku-Band Fits
Ku-band also appears in NASA’s space-relay forward and return services. It is relevant when the selected mission uses that relay architecture, but it is not the direct imagery downlink in the Sentinel examples above. Identify the endpoints of the particular link before assigning it a band. [1][2]
A Worked Reception-Planning Example
Suppose a receive system is being sized for the published Sentinel-2 X-band rate of 560 Mbit/s. For an assumed uninterrupted 10-minute transfer at that rate, the arithmetic is 560 million bit/s × 600 s ÷ 8 = 42 GB, using decimal gigabytes. At the published 2 Mbit/s S-band rate, the same interval represents only 0.15 GB, a 280:1 rate ratio. This is a rate-times-duration illustration, not a measured pass, a prediction of usable image volume or a claim that imagery is available over the S-band link. Acquisition time, interruptions, framing and processing can change the usable result. [2]
Two documented operational details help turn that calculation into a sensible equipment check. First, ESA describes Sentinel-2 as capable of operating on stored commands for 15 days in a nominal scenario. A receiving station does not need to establish its own S-band command uplink before every imagery pass. Second, the Metop-B LRPT entry shows why service availability must be checked before hardware is bought: a receiver can match a published frequency perfectly yet receive nothing from an unavailable service. [2][4]
- Define the station’s role: receive imagery, receive a weather broadcast, or provide authorized spacecraft control. Do not add a transmitter merely because the mission also has an uplink.
- Confirm the actual service: satellite, carrier, current availability, polarization, modulation and coding. Record spacecraft-to-ground and ground-to-space directions separately.
- Check the entire data path: feed and receiver coverage, tracking requirements, decoding support, storage and onward network capacity.
- Check authorization and access: a listed frequency range is not a transmission license, and a technically receivable signal does not by itself establish access rights. NASA treats frequency licensing as a separate ground-system design requirement. [1]
Bottom Line
For bulk Earth observation imagery, start with X-band and Ka-band. For weather distribution, examine L-band and the mission’s direct-broadcast or rebroadcast service; treat older VHF examples as historical unless a live service is confirmed. S-band commonly supports spacecraft control, while Ku-band can serve relay links. The final receiver specification must name the satellite and service, not just the letter band.
Planning a ground-station feed?
Share your operating frequencies, polarization, receive or transmit role, and reflector interface for a component review.
References
- NASA: Ground Data Systems and Mission Operations. General band definitions, Near Space Network frequency and capability tables, link design and licensing.
- ESA: Sentinel-2 operations. Archived mission configuration, communication rates, EDRS link architecture and autonomous operation.
- Copernicus SentiWiki: Sentinel-1 Mission. Radar sensing frequency and payload/control communication paths.
- WMO OSCAR: Metop-B. Telecommand, telemetry, global data and direct-broadcast frequencies; LRPT availability restriction.
- NOAA NESDIS: GOES-R Data Access and Unique Payload Services. GRB frequencies, rates and polarization bandwidths; DCS service changes.
- NOAA: Polar-orbiting Operational Environmental Satellites booklet. Historical APT and HRPT service descriptions.
- NOAA OSPO: POES Instrument and Subsystem Performance Status. Archival notice and constellation decommissioning status.
