KSAT announced an October 30, 2026 partnership with Morehead State University to strengthen its lunar communications network. The announcement identifies existing 21-meter and 12-meter-class antennas in Morehead, Kentucky. For a mission team assessing the news, the next useful question is which station and service would support its particular link.
KSAT’s October 30 Morehead partnership announcement
Separate the network description from the station record
KSAT’s Lunar service page describes several network groups. It associates the 13-meter-class network with S-band and X-band services, while its partner-network description lists a combination of S-band, X-band and Ka-band services. A list of bands across a network should not be copied into every individual station’s row as a verified capability.
KSAT Lunar: network groups and service descriptions
The Morehead announcement names the antennas but does not supply a station-by-station frequency-band table. Treat that detail as something to confirm with the provider. Antenna diameter is a useful identifier in the announcement; it is not a substitute for a confirmed service specification.
Keep the construction programme distinct
In a separate September 2 update, KSAT described development of three 20-meter antennas in the United States, Spain and Western Australia, designed for near-continuous lunar coverage. That dated construction update and the October Morehead partnership describe different parts of the network’s development.
KSAT’s September 2 infrastructure-development update
Keep each source’s date and scope visible in a briefing. A later partnership announcement does not, by itself, establish that every item in an earlier construction programme has entered service. Ask for current readiness information for the actual station under consideration.
Try a fictional mission worksheet
Imagine a fictional spacecraft team seeking an X-band data return during a proposed mission window. Its worksheet should name the requested service, station, band, time window and evidence confirming the match. This is an invented planning exercise, not a KSAT booking or an assessment of any real spacecraft.
If a network overview lists X-band but the proposed station’s details remain unresolved, leave the station row unverified. Ask the provider to confirm the relevant configuration and availability. Do not turn an overview-level description into a mission-specific commitment.
Add separate fields for the requested data rate, required interfaces and the person responsible for technical confirmation. These are suggested questions for a qualified mission team and provider to resolve, not service levels established by this article.
Record what would close the question
A useful review record pairs each requirement with its dated supporting document and any unresolved condition. Keep a proposed contact window separate from confirmed scheduling evidence. If the selected station or configuration changes, revisit the corresponding requirement rows.
The partnership is relevant news about US ground infrastructure. Its practical value for an individual mission depends on the confirmed technical and operational match. No antenna, radio link, mission schedule or service agreement was tested or booked for this guide.
Check the station-specific evidence
