Exact Contract Story
A KA-BAND SATELLITE COMMUNICATIONS FLIGHT TERMINAL WILL BE DESIGNED FOR USE BY NASA TERRESTRIAL BALLOONS TO PROVIDE 10-MBPS TO 1-GBPS SATELLITE COMMUNICATIONS TRANSMIT LINKS AND LOW DATA RATE COMMAND RECEIVE LINKS USING EITHER COMMERCIAL KA-BAND SATELLITES OR NASA TDRSS SATELLITES. THE TRANSMIT KA-BAND FREQUENCIES OF NASA TDRSS SATELLITES GO UP TO 27.5-GHZ AND ARE ADJACENT TO THE COMMERCIAL KABAND SATELLITE FREQUENCIES STARTING AT 27.5-GHZ, SO THIS SINGLE KA-BAND FLIGHT TERMINAL WILL BE ABLE TO TUNE TO BOTH THE NASA TDRSS AND COMMERCIAL KA-BAND SATELLITE FREQUENCIES. THIS KA-BAND FLIGHT TERMINAL WILL BE SHOWN TO HAVE A LOWER SIZE, WEIGHT, AND POWER (SWAP) TO THE EXISTING NASA BALLOON SATCOM TERMINALS. A RELATIVELY LOW-COST 2-DIMENSIONAL ELECTRONIC BEAMFORMING ANTENNA WILL BE TESTED FOR ITS CAPABILITY TO POINT A HIGH-GAIN ANTENNA BEAM AT THE EXISTING COMMERCIAL OR TDRSS KA-BAND SATELLITES IN GEOSTATIONARY ORBIT (GEO) AS THE TERRESTRIAL BALLOON IS MOVING SLOWLY IN RELATION TO THOSE GEO SATELLITES. TESTING WILL ALSO BE PERFORMED ON THE ABILITY OF THIS SAME BEAMFORMING ANTENNA TO POINT AT AND TRACK EXISTING O3B MIDDLE EARTH ORBIT (MEO) AND TELESAT AND SPACEX LOW EARTH ORBIT (LEO) KA-BAND SATELLITES THAT WILL BE MOVING MUCH FASTER RELATIVE TO THE BALLOON. THE PERFORMANCE OF THIS KA-BAND FLIGHT TERMINAL WILL CHANGE DRAMATICALLY FROM 10-MBPS TO 1-GBPS DEPENDING ON WHICH KA-BAND SATELLITE AND WHICH SATELLITE BEAM IN WHICH GEO, MEO, OR LEO ORBIT THE BALLOON'S TERMINAL DECIDES TO ACCESS. SOFTWARE DEFINED RADIO (SDR) WAVEFORM FIRMWARE AND FLIGHT RADIO HARDWARE WILL BE TESTED THROUGH A CHANNEL SIMULATOR THAT USES SOFTWARE TO SIMULATE A MOVING NASA BALLOON SUCCESSFULLY CLOSING SATCOM LINKS THROUGH SATELLITES WITH DIFFERENT LINK CHARACTERISTICS. BEAM TO BEAM HANDOVERS, FREQUENCY CHANNEL INTERFERENCE MITIGATION, AND THE DIFFERENT DOPPLER SHIFT COMPENSATION NEEDED FOR THE DIFFERENT GEO, MEO, AND LEO ORBITS WILL BE TESTED IN THESE SIMULATIONS OF THE SDR FIRMWARE AND HARDWARE..
A KA-BAND SATELLITE COMMUNICATIONS FLIGHT TERMINAL WILL BE DESIGNED FOR USE BY NASA TERRESTRIAL BALLOONS TO PROVIDE 10-MBPS TO 1-GBPS SATELLITE COMMUNICATIONS TRANSMIT LINKS AND LOW DATA RATE COMMAND RECEIVE LINKS USING EITHER COMMERCIAL KA-BAND SATELLITES OR NASA TDRSS SATELLITES. THE TRANSMIT KA-BAND FREQUENCIES OF NASA TDRSS SATELLITES GO UP TO 27.5-GHZ AND ARE ADJACENT TO THE COMMERCIAL KABAND SATELLITE FREQUENCIES STARTING AT 27.5-GHZ, SO THIS SINGLE KA-BAND FLIGHT TERMINAL WILL BE ABLE TO TUNE TO BOTH THE NASA TDRSS AND COMMERCIAL KA-BAND SATELLITE FREQUENCIES. THIS KA-BAND FLIGHT TERMINAL WILL BE SHOWN TO HAVE A LOWER SIZE, WEIGHT, AND POWER (SWAP) TO THE EXISTING NASA BALLOON SATCOM TERMINALS. A RELATIVELY LOW-COST 2-DIMENSIONAL ELECTRONIC BEAMFORMING ANTENNA WILL BE TESTED FOR ITS CAPABILITY TO POINT A HIGH-GAIN ANTENNA BEAM AT THE EXISTING COMMERCIAL OR TDRSS KA-BAND SATELLITES IN GEOSTATIONARY ORBIT (GEO) AS THE TERRESTRIAL BALLOON IS MOVING SLOWLY IN RELATION TO THOSE GEO SATELLITES. TESTING WILL ALSO BE PERFORMED ON THE ABILITY OF THIS SAME BEAMFORMING ANTENNA TO POINT AT AND TRACK EXISTING O3B MIDDLE EARTH ORBIT (MEO) AND TELESAT AND SPACEX LOW EARTH ORBIT (LEO) KA-BAND SATELLITES THAT WILL BE MOVING MUCH FASTER RELATIVE TO THE BALLOON. THE PERFORMANCE OF THIS KA-BAND FLIGHT TERMINAL WILL CHANGE DRAMATICALLY FROM 10-MBPS TO 1-GBPS DEPENDING ON WHICH KA-BAND SATELLITE AND WHICH SATELLITE BEAM IN WHICH GEO, MEO, OR LEO ORBIT THE BALLOON'S TERMINAL DECIDES TO ACCESS. SOFTWARE DEFINED RADIO (SDR) WAVEFORM FIRMWARE AND FLIGHT RADIO HARDWARE WILL BE TESTED THROUGH A CHANNEL SIMULATOR THAT USES SOFTWARE TO SIMULATE A MOVING NASA BALLOON SUCCESSFULLY CLOSING SATCOM LINKS THROUGH SATELLITES WITH DIFFERENT LINK CHARACTERISTICS. BEAM TO BEAM HANDOVERS, FREQUENCY CHANNEL INTERFERENCE MITIGATION, AND THE DIFFERENT DOPPLER SHIFT COMPENSATION NEEDED FOR THE DIFFERENT GEO, MEO, AND LEO ORBITS WILL BE TESTED IN THESE SIMULATIONS OF THE SDR FIRMWARE AND HARDWARE..
Discovery Data
- Mission
- SpaceX Program
- Awarded on
- 2018-07-27
- Obligated amount
- $122,158
- Agency
- U.S. Government
- Customer
- U.S. Government
- Recipient
- PEERSAT LLC
- Actions
- 1
- Notices
- 0
- Spending points
- 1
- Bidders
- 0
- Exact source records
- 1
Links
Exact Source Evidence
Exact external records already attached to this contract story.
USASpending award
1 linked80NSSC18P2079
Latest Award Actions
Mod 0 • 2018-07-27
Delta: $122,158 • Cumulative: $122,158
Spending Timeline
FY 2018 M07
Obligations: $122,158 • Outlays: N/A
Contract Detail FAQ
Search-first answers for this contract entity and its source identifiers.
- What sources feed the contract data on this site?
- Contract entities combine USAspending award references with SAM.gov-normalized procurement records (including PIID-linked actions, notices, and spending rows when available).
- Why is there a canonical /contracts URL when program pages already exist?
- Program pages keep mission context, while /contracts URLs consolidate duplicate contract entities into one indexable canonical URL so search engines attribute ranking signals to a single record.
- Which identifiers should I search to find a specific government contract?
- Use any of these identifiers: USAspending Award ID, PIID, contract key, solicitation ID, notice ID, recipient/awardee name, or agency/customer name.
- How often do contract pages update?
- Contract pages revalidate on a 10-minute cadence, while upstream source data refresh timing depends on ingest jobs and source-side publication timing.
- What is the difference between SAM.gov and USAspending in these records?
- USAspending primarily provides award and obligation visibility, while SAM.gov captures procurement lifecycle context such as solicitation notices and related action thread signals.
- Why can the contract amount differ from another source?
- Amounts can differ across snapshots because some sources report base award value while others include modification deltas, cumulative obligations, or later adjustments.
- Can one contract appear in more than one program section?
- Yes. A contract may appear in multiple program contexts; canonical entities are designed to consolidate those overlaps into a single URL for indexing and discovery.
- What is a PIID on a contract detail page?
- PIID stands for Procurement Instrument Identifier. It is the contracting identifier used to track related awards, actions, and notices across a procurement thread.
- Where should I verify the official source record for this contract?
- Use the Source record link on the contract detail page. The page also links back to the program-native detail page and, when available, the Artemis story page for thread context.
- Why are actions, notices, or spending rows sometimes missing?
- Missing rows usually mean no matched records were returned yet for that identifier set in the current source snapshot, not that the contract entity itself is invalid.
- What exact terms should I search to verify this specific contract?
- Use these identifiers in search: USASPENDING-80NSSC18P2079 | 80NSSC18P2079. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.