Attachment STA Request

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

IBFS_SESSTA2016071300656_1143380

July 13, 2016

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

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

Dear Ms. Dortch:

Intelsat License LLC (“Intelsat”) herein requests an additional 30 days, beginning July 27, 2016, of the
Special Temporary Authority (“STA”)1 previously granted Intelsat to use its Castle Rock, Colorado Ku-
band earth station—call sign KL92—to provide launch and early orbit phase (“LEOP”) services2 for
Intelsat 31; telemetry, tracking, and command (“TT&C”) during in-orbit testing (“IOT”) at 132.0° W.L;
and TT&C during the drift of Intelsat 31 to and at its final location of 95.05° W.L.3 Intelsat 31 was
launched on June 9, 2016. The LEOP period is completed; IOT and drift are expected to last
approximately three and two weeks, respectively.

The Intelsat 31 operations will continue to be performed using the following frequencies: 13998.50
MHz, and 14006.0 MHz in the uplink (LHCP, H); and 11194.25 MHz, 11195.5 MHz, 11196.25 MHz,
and 11196.75 MHz in the downlink (RHCP, V). The operations will be coordinated with all operators
of satellites that use the same frequency bands and are in the LEOP path, the drift path, or are potentially
affected by these operations at the IOT location.4 The TT&C operations at 95.05° W.L. will be
consistent with Intelsat’s coordination agreements for the nominal 95° W.L. location. All operators of
potentially affected satellites 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 Intelsat 31 mission is as follows:


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
 See Satellite Communications Services Information; Actions Taken, Report No. SES-01864, File No. SES-
20160622-00571 (June 29, 2016) (Public Notice); Satellite Communications Services Information; Actions Taken,
Report No. SES-015751856, File No. SES-STA-20160503-00393 (June 1, 2016) (Public Notice).
3
 See Policy Branch Information; Actions Taken, Report No. SAT-01052, File No. SAT-LOA-20140410-00038
(November 7, 2014) (Public Notice). At 95.05º W.L., Intelsat 31 will be co-located with Intelsat 30 (S2887) and
Galaxy 3C (S2381).
4
    Intelsat will handle the coordination.


Ms. Marlene H. Dortch
July 13, 2016
Page 2


                 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 further extension request, Intelsat incorporates by reference Exhibit A ofits
initial STA request which contains 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, or into Federal systems operating in the 13.75
—14.00 GHz band. 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.

Grant of this STA further extension request will allow Intelsat to safely complete the testing and drift of
the Intelsat 31 satellite. This, in turn, will help ensure continuity of service at the 95.05° 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,



  lssn 4. Ay
Cynthia J. Grady
Regulatory Counsel
Intelsat Corporation




ce: Paul Blais



Document Created: 2016-07-13 14:39:40
Document Modified: 2016-07-13 14:39:40

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