FCC SHERPA technical

ERRATA, ERRATUM OR ADDENDUM submitted by Spaceflight, Inc.

Additional technical information

2016-03-22

This document pretains to SES-STA-20150824-00550 for Special Temporal Authority on a Satellite Earth Station filing.

IBFS_SESSTA2015082400550_1130609

REQUESTS FOR SPECIAL TEMPORARY AUTHORITY Spaceflight Inc. (“Spaceflight”), pursuant to Section 25.120 of the Commission’s Rules, hereby requests Special Temporary Authority (“STA”) to permit it to communicate with a spacecraft, known as SHERPA, and corresponding earth stations for a duration of up to twelve (12) hours to take place in a single occurrence between January 15, 2016 and April 15, 2016. 1 As described in greater detail in the attached Technical Annex, SHERPA is a non- propulsive, free-flying spacecraft intended to deploy auxiliary spacecraft from each of five ports. SHERPA itself is proposed to be affixed to the payload on a Falcon 9 launch that is currently scheduled to occur within above-stated launch period. SHERPA will be placed in a sun synchronous elliptical orbit of 720 x 450 km, 97.4 degree inclination. After its deployment from the launch vehicle, SHERPA will initiate a sequence of procedures to begin the deployment of its own payload and the communication that is the subject of the instant requests will commence. Spaceflight seeks authority to permit it to establish communications between SHERPA and three earth stations during the twelve-hour operational of the SHERPA payload. 2 The communications links, which will consist of two-way data transmissions, will permit the Spaceflight technical crew to track the launch and download status information from SHERPA. The proposed frequencies for communication to and from SHERPA are UHF frequencies authorized under the FCC’s Table of Frequency Allocations for space operations. The payload of SHERPA will consist of small spacecraft that are owned and to be operated by Spaceflight’s customers. Each customer is expressly required under its agreement with Spaceflight to obtain all licenses, authorization, clearances, and permits that may be necessary to operate its individual spacecraft. Spaceflight asserts that grant of the instant requests for Special Temporary Authority will be in the public interest. Such grant will permit Spaceflight to initiate a new and innovative deployment technology for small spacecraft, thereby providing a cost-efficient means for placing them into their designed orbits. 1 Recent developments in the spacecraft launch industry have resulted in a number of launch delays and uncertainties as to when future launches will occur. The timeframe set forth above reflects the current launch period assigned for the Spaceflight launch. Spaceflight has not yet been assigned an exact date of the SHERPA launch. Accordingly, Spaceflight is herein seeking STA to cover a period of three (3) months. However, as described herein, the actual communications for which STA is sought will occur over a period of only twelve (12) hours. Spaceflight will notify the Commission as its launch period is narrowed to a particular day as soon as that information is confirmed to it by the launch provider. 2 Spaceflight is submitting concurrently unique applications for space station STA to cover the communications of SHERPA and earth station STA to cover the ground station locations.

Technical Annex: Spaceflight SHERPA Spacecraft Description The Spaceflight SHERPA spacecraft is a non-propulsive, free-flying spacecraft intended to deploy auxiliary spacecraft from each of five ports. The spacecraft is primarily composed of commercial off the shelf (COTS) hardware, with the core structure being a custom ESPA Grande ring. Auxiliary satellites are integrated to each port using simple plates and separated using proven separation systems, such as the Planetary Systems Corporation (PSC) Motorized Lightband (MLB) and the Innovative Solutions in Space (ISIS) QuadPack. The configuration, shown in Figure 1, is intended to deploy three microsatellites using MLBs as well as several CubeSats and nanosatellites from twenty-one (21) QuadPack dispensers. Each QuadPack holds 12U worth of CubeSat payload. A CubeSat, based on the Cal Poly CubeSat standard, has nominal dimensions 10 x 10 x 10 cm. SHERPA runs flight software on COTS Andrews Space CORTEX avionics and it is equipped with its own power and power distribution system to deploy each auxiliary spacecraft in a pre-programmed sequence. The primary mission is satisfied by successful deployment of each auxiliary payload. The confirmation of successful payload deployment is given by the transmission of telemetry containing SHERPA state vectors taken upon each discrete deployment event. The SHERPA mission itself is expected to last approximately Figure 1. SHERPA Spacecraft shown twelve (12) hours. At launch, SHERPA is integrated beneath integrated with the Payload Attach Fitting the primary payload. The primary payload is launched into (below) and the Primary Payload Adapter 720 km circular sun synchronous orbit and then separated. (above) The upper stage, with SHERPA attached, executes a maneuver to lower the perigee of the orbit to 450 km and change the inclination to 97.4 degrees. At this orbit, SHERPA is separated from the upper stage. The separation event activates the SHERPA spacecraft through the closing of separation switches, which will turn on for the first time. After initialization, SHERPA begins a pre-programmed sequence of deployments. No uplink is necessary to begin deployments. For each deployment event time, position, and velocity (determined via GPS receiver) are logged in the form of a state vector to be transmitted. Upon completion of deployments, SHERPA transmits the telemetry to a ground station. SHERPA’s communication system utilizes an onboard UHF radio with 4 antenna. SHERPA batteries are expected to last for duration less than 20 hours until they’re expended. Ultimately, SHERPA de-orbits through orbital decay due to atmospheric drag approximately 20 years after launch.


Document Created: 2016-03-22 13:15:12
Document Modified: 2016-03-22 13:15:12
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC