Attachment STA Request

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

IBFS_SESSTA2015040600200_1082362

April 2, 2015

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

          Re:     Request for Special Temporary Authority
                  Castle Rock, Colorado Earth Station KL92

Dear Ms. Dortch:

Intelsat License LLC (“Intelsat”) herein requests a grant of Special Temporary Authority (“STA”)1 for
30 days, commencing April 29, 2015, to use its Castle Rock, Colorado Ku-band earth station—call sign
KL92—to provide launch and early orbit phase (“LEOP”) services for the MexSat-G1 satellite.
MexSat-G1 is expected to be launched on April 29, 2015.2 The LEOP period is expected to last
approximately ten days.3

The MexSat-G1 LEOP operations will be performed in the following frequency bands: 13249.0 MHz
(LHCP) and 12751.0 MHz (RHCP) in the uplink, and 11201.0 MHz and 11202.0 MHz in the downlink
(LHCP & RHCP). 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 MexSat-G1 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

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 MexSat-G1, which Intelsat understands is licensed by Mexico, will be at
113.0° W.L. The in-orbit testing location will be 113.1° W.L.
3
    Intelsat is seeking authority for 30 days to accommodate a possible launch delay.
4
    Boeing, the manager of the MexSat-G1 LEOP mission, will handle the coordination.


Ms. Marlene H. Dortch
April 2, 2015
Page 2


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 MexSat—G1
LEOP mission, it is seeking to operate in the frequencies listed in the request at power levels not to
exceed 22 dBW. The technical information submitted with this STA request reflects a power level as
high as 28 dBW because Intelsat might operate at this level in the event an emergency necessitates the
use of a 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 MexSat—G1 LEOP mission, Boeing will serve as the mission
manager. Boeing 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 Boeing. Intelsat will
perform the ranging sessions by sending a tone to the spacecraft periodically. Intelsat will remain in
control of the baseband unit, RF equipment, and antenna.

Grant of this STA request will allow Intelsat to help launch the MexSat—G1 satellite. This, in turn, will
help will provide additional capacity at the 113.0° W.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,




  Cprti=JHucty.
Cynthia J. Grady
Regulatory Counsel
Intelsat Corporation




ce: Paul Blais



Document Created: 2015-04-02 13:27:55
Document Modified: 2015-04-02 13:27:55

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