Boeing V Band Applic

LETTER submitted by The Boeing Company

Notification Letter

2018-11-05

This document pretains to SAT-AMD-20170929-00137 for Amended Filing on a Satellite Space Stations filing.

IBFS_SATAMD2017092900137_1568149

51 LOUISIANA AVENUE, N.W. • WASHINGTON, D.C. 20001.2113 TELEPHONE: +1.202.879.3939 • FACSIMILE: +1.202.626.1700 Direct Number: (202) 879-3630 bolcott@jonesday.com November 5, 2018 Jose Albuquerque, Chief International Bureau, Satellite Division Federal Communications Commission 445 12th Street SW Washington, DC 20554 Re: The Boeing Company IBFS File Nos. SAT-LOA-20170301-00028, SAT-AMD-20170929-00137 and SAT-AMD-20180131-00013 (call sign S2993) Dear Mr. Albuquerque: On July 31, 2018, The Boeing Company (“Boeing”), through its attorneys, filed a letter with your office indicating, inter alia, that Boeing may file an additional amendment to the above reference application to make certain changes to its proposal to launch and operate a non- geostationary satellite orbit (“NGSO”) fixed satellite service (“FSS”) system operating in the V- band, IBFS File Numbers SAT-LOA-20170301-00028, SAT-AMD-20170929-00137 and SAT- AMD-20180131-00013 (call sign S2993). Boeing hereby informs the Commission that it will refrain from filing a further amendment at this time to its pending application and asks that the Commission treat the application as acceptable for filing. Please contact the undersigned if you have any questions about this matter. Sincerely, Bruce A. Olcott Counsel to The Boeing Company ALKHOBAR • AMSTERDA M • ATL ANTA • BEIJING • BOSTON • BRUSSEL S • CHICAGO • CLEV EL AND • COLUMBUS • DALL AS DUBAI • DÜSSELDORF • FRANK FUR T • HONG KONG • HOUSTON • IRV INE • JEDDAH • LONDON • LOS ANGELES • MAD RID MEXICO CIT Y • MIAMI • MI L AN • MOSCOW • MUNICH • NEW YORK • PARI S • PITTSBURGH • RIYADH • SAN DIEGO SAN FRANCISCO • SÃO PAULO • SHANGHAI • SILICON VALLEY • SINGAPORE • SYDNEY • TAIP EI • TOKYO • WASHING TON


Document Created: 2018-11-05 08:22:15
Document Modified: 2018-11-05 08:22:15
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC