Attachment 2002Hughes-Comm ltr

2002Hughes-Comm ltr

REQUEST submitted by IB,FCC

LTR

2002-02-27

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

IBFS_SATLOA1995092900128_869635

Federal Communications Commission Washington, D.C. 20554 March 27, 2002 VIA FACSIMILE AND U.S. MAIL John P. Janka, Esq. Latham & Watkins 555 11"" Street, NW Suite 1000 Washington, D.C. 20004—1304 Re: Hughes Communications Galaxy, Inc., File Nos. IBFS No.SAT—LOA—19931203—00040/41; IBFS No. SAT—LOA—19950929—00125/00129; IBFS No. SAT— LOA—19950929—00137. Dear Mr. Janka: On January 28, 2002, the Satellite Division requested certain information concerning the milestone obligations set forth in Hughes Communications Galaxy, Inc.‘s (Hughes) Ka—band authorization. Specifically, we requested a copy of an executed contract verifying that construction has commenced and the Hughes satellites will be built within the time frame specified in Hughes‘s license. On February 8, 2002, Hughes submitted a copy of a contract dated December 17, 1999. The parties to the contract are Hughes Network Systems, Inc. and Boeing Satellite Systems. Because the licensee is Hughes Communications Galaxy, Inc., we are requesting additional information concerning the relationship between the licensee and Hughes Network Systems that evidences the licensee‘s obligation to commence construction pursuant to its Ka—band license. Please submit this explanation, supported by the relevant documentation, to the Commission‘s Secretary by April 3, 2002, with a hand delivered or electronic courtesy copy to Alyssa Roberts (aroberts@fee.gov) of my staff. Failure to provide this information by this date shall render Hughes‘s Ka—band license null and void. Please contact Alyssa Roberts at (202) 418—7276 if you have any questions. Sincerely, [ .MAAA o( . s c 6. s ets tyfi ef 8. L — Fern J. Jarmulnek Deputy Chief Satellite Division


Document Created: 2019-04-08 13:37:34
Document Modified: 2019-04-08 13:37:34
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC