Attachment condition 7 ltr

condition 7 ltr

SUBMISSION FOR THE RECORD submitted by Pegasus

condition 7 ltr

2004-03-31

This document pretains to SAT-LOA-20031119-00336 for Application to Launch and Operate on a Satellite Space Stations filing.

IBFS_SATLOA2003111900336_367417

                                                                                              ORIGINAL
March 30, 2004                               PEGASUS
                                                   COMMUNICATIONS
VIA HANDDELIVERY
                                                                                         RECElVED
Marlene H. Dortch
Office of the Secretary                                                                   MAR 3 0 2004
Federal Communications Commission
                                                                                ‘ ~ W U LCOMMUWICATIONS C O M M I ~ O ~ ~
445 12th Street, S.W.                                                                    OFFICE OF THE SECRETARY
Washington, D.C. 20554

               Re:     Pegasus Development Corporation
                       Statement Regarding Condition 7 of its Ka-band License
                       Call Sign S2603                      I




Dear Ms. Dortch:

         On January 30, 2004. the Con7m.ission granted Pegasus Development Corporation (“Pegasus”)
an authorization to launch and operate a Ka-band satellite system at 87”W. See SAT-LOA-200311 19-
003366. Condition 7 of the authorization requires Pegzsus to submit a statement regarding measures
that would be taken to prevent in-orbit collisions with other satellites in the geostationary orbit.
Specificallv, the condition requires Pegasus to consider methods for the avoidance of collisions with
satellites “!ocated a:, or planned to be located at, Pegasus Development Corporation’s assigned orbital
locations, or assigmd ir: the vicinity of that location such that the station-keeping volume of the
resFective satttlli tc:; mighi overlap.”

       In order to determine the jp9cecr;lft that mr~e,tbe considered, Pegasus h a searched the ITU
Space Network Systems Onl.nc and fcicnck t k ta!l=;wit?g in-orbit space stations:

       Name                    Locatio9            Licenses



        Additionally: Pegasus found a n!.mber df pclrsntial future satellites that may be deployed in the
vicinity of 8’7“W. NCJX  were listed in i-heexpec:ed launch manifest listed in the Federal Aviation
Administration’s Corrirnerciai Spacc Tr’msp@fiatioi?. Forecast dared May 2003.

       Yam                    Location             Administration

                              87“W

       BSAT K                 87”W                 IJnited I(:n,u,dom

       Roebuck47              87“W                 Australia
                                                                     S2603               SAT-LOA-20031119OO336          1B2003002351
       U SA SAT - 4 3u’       87”W                 US A              Pegasus Development Corporation
                                                                     Pegasus IA


                            225 City line Avenue    Suite   200 Bc
                             Tel                           ._
                                   610-934-7000Fax 610-934-7          .. , . , , r a ”   _-


         Pegasus believes that a coordination agreement can be achieved with the SES-Americom
satellite at 87"W. Furthermore, to the extent that additional authorized satellites begin operations at
87"W, Pegasus will take steps to coordinate a mutual collision threat avoidance policy and procedure
with that operator. Coordination activity will start approximately two years prior to the expected
launch of the Pegasus satellite.


                                                     Very truly ours,

                                                    74
                                                     V a c y W. Summers
                                                     Ylce President of Technology



Document Created: 2004-04-06 18:06:43
Document Modified: 2004-04-06 18:06:43

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