TDRSS support was originally also scheduled in the long-range planning time frame for all scenarios; however, cost constraints and changes to the plan in the short term dictated the need for a policy change.
It was determined more efficient to schedule TDRSS at the daily planning time, except in the case of unmated scenarios, where the timing and the more definite guarantee of contacts was crucial.
First, our launch delay created the need to replan all existing long-range plans to shift both AFSCN and TDRSS requests.
In the morning of daily planning, the SRP would receive the list of contacts lost to other spacecraft and any suggested additions to replace these losses, and he or she would also receive the most up-to-date list of TDRSS availabilities.
4) TDRSS support was originally requested in advance for all long-range planning, but as cost became an issue for unused contacts, the requests for TDRSS became part of the daily planning process.
1) A sounding rocket could expose an LO to as much as 30 g of acceleration, potentially causing loss of communications to the TDRSS and, therefore, loss of valuable information.
As a result, a device with the capability to monitor and quantify the acceleration sensitivity of a crystal oscillator is necessary to implement a cost-effective, stable TDRSS transceiver.
One solution would be to use NASA's existing network of seven TDRSS satellites to communicate with these sounding rockets.
A TDRSS transceiver placed onboard each sounding rocket would provide a cheaper, more efficient method of transmitting data back to earth.