Attachment STA Request

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

IBFS_SESSTA2016052600460_1137014

May 26, 2016

Ms. Marlene H. Dortch
Secretary
Federal Communications Commission
445 12th Street, S.W.
Washington, D.C. 20554

          Re:     Request for Special Temporary Authority
                  Hagerstown, Maryland Earth Station KA275

Dear Ms. Dortch:

Intelsat License LLC (“Intelsat”) herein requests a grant of Special Temporary Authority (“STA”)1 for
30 days, commencing June 8, 2016, to use its Hagerstown, Maryland C-band earth station—call sign
KA275—to provide launch and early orbit phase (“LEOP”) services for the BRISat satellite. BRISat is
expected to be launched June 8, 2016.2 The LEOP period is expected to last approximately 10 days.3

The BRISat LEOP operations will be performed in the following frequency bands: 6416.5 MHz and
6418.5 MHz in the uplink (LHCP), and 4193.5 MHz and 4195.5 MHz in the downlink (LHCP). The
LEOP operations will be coordinated with all operators of satellites that use the same frequency bands
and are in the LEOP path.4 All operators of satellites in that path will be provided with an emergency
phone number where the licensee can be reached in the event that harmful interference occurs.

The 24x7 contact information for the BRISat LEOP mission is as follows:

Ph.:      (703) 559-7701 – East Coast Operations Center (primary)
          (310) 525-5591 – West Coast Operations Center (back-up)

Request to speak with Harry Burnham or Kevin Bell.

In further support of this request, Intelsat hereby attaches Exhibits A and B, which contain technical
information that demonstrates that the operation of the earth station will be compatible with its
electromagnetic environment and will not cause harmful interference into any lawfully operating
terrestrial facility, as well as a waiver request. Intelsat also notes that for purposes of the BRISat LEOP

1
 Intelsat has filed its STA request, an FCC Form 159, a $195.00 filing fee, and this supporting letter
electronically via the International Bureau’s Filing System (“IBFS”).
2
 The permanent orbital location for BRISat, which Intelsat understands is licensed by Indonesia, will be at 105.5°
E.L. The in-orbit testing location will be 150.65° E.L.
3
    Intelsat is seeking authority for 30 days to accommodate a possible launch delay.
4
    Space Systems Loral (“SSL”), the manager of the BRISat mission, will handle the coordination.


Ms. Marlene H. Dortch
May 26, 2015
Page 2


mission, it is seeking to operate in the frequencies listed in the request at power levels not to exceed 25.5
dBW. The technical information submitted with this STA request reflects a power level as high as 34.0
dBW because Intelsat might operate at this level in the event an emergency necessitates the use ofa
higher power level in order to command the satellite. In the extremely unlikely event that harmful
interference should occur due to transmissions to or from its earth station, Intelsat will take all
reasonable steps to eliminate the interference.

Finally, Intelsat clarifies that during the BRISat LEOP mission, SSL will serve as the mission manager.
SSL will build and send the commands to the Intelsat antenna, which will process and execute the
commands. Telemetry received by Intelsat will be forwarded to SSL. Intelsat will perform the ranging
sessions by sending a tone to the spacecraft periodically. Intelsat will remain in control ofthe baseband
unit, RF equipment, and antenna.

Grant of this STA request will allow Intelsat to help launch the BRISat satellite. This, in turn, will result
in the provision of C—band and Ku—band coverage of Indonesia and South East Asia from the 105.5° E.L.
orbital location and thereby promotes the public interest.

Please direct any questions regarding this STA request to the undersigned at (703) 559—6949.

Respectfully submitted,




Aptbsg)Porly
Regulatory Counsel
Intelsat Corporation



ce: Paul Blais



Document Created: 2016-05-26 10:23:03
Document Modified: 2016-05-26 10:23:03

© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC