E-Mail generated [Aug 5 2016]

0311-EX-PL-2016 Correspondence

Georgia Institute of Technology

2016-08-05ELS_180370

To: Brian Gunter E-Mail: brian.gunter@aerospace.gatech.edu From: Doug Young Date: August 05, 2016 Subject: Request for Info - File #0311-EX-PL-2016 ---------------------------------------------------------------------------------------------------------------------------- Message: Submit a response to the issues the FCC’s International Bureau has identified below: - Please provide a description of the concept of operations for formation flying (including target range between the satellites) and provide information concerning the risk of collision between the two satellites, and any steps taken to mitigate this risk. - Please provide “who” will be operating the ground based laser. - On the ODAR document it showed the summary of analysis of zeros Joules (KE) for re-entering debris. However, on the second to last page of the ODAR it clearly shows debris surviving with a KE of 125.910988 Joules which is inconsistent with the summary analysis of debris re-entry. Perhaps, the applicant can undertake a higher fidelity analysis that may establish the material component demise on reentry. Review of Form 442 and SpaceCap documents - Unfortunately, the SpaceCap file provided is not in the proper format; it appears to be a CR/Notification format which is not the correct format; we need the format to be an Advanced Publication Information (API), so we ask the applicant to resubmit the SpaceCap in an API format. -also the Radio Regulation provision reference in box BR3a is incorrect (it should be Section II of Article 9, Sub-section IA.); this provision will be in-line with the API format. - Moreover, the SpaceCap file whole spacecraft emitter page is missing (this is the downlink information). - On the SpaceCap file receiver page, the box RR No. 4.4 was not checked with “Y”; please make sure all the boxes with RR No. 4.4 are checked "Y"; - Furthermore, on the SpaceCap file receiver page, the following data is missing: class of station, nature of service, polarization, noise temperature, max pwr dens value, etc.; please check that all the information in the SpaceCap file and ensure that Form 442 and the SpaceCap file data are consistent. - On the SpaceCap file, the emission designator "OMNI" is not correctly written; it should be identical to the emission designator in form 442. Please check this entry and make the necessary changes as appropriate. - FCC Form 442 does contain the downlink information for the CubeSat and this information needs to be incorporated in the SpaceCap API file along with its associated earth station(s). Please ensure that all the data for each CubeSat is reflected in the SpaceCap API file and it is consistent with Form 442. The items indicated above must be submitted before processing can continue on the above referenced application. Failure to provide the requested information within 30 days of August 05, 2016 may result in application dismissal pursuant to Section 5.67 and forfeiture of the filing fee pursuant to Section 1.1108. DO NOT Reply to this email by using the 'Reply' button. In order for your response to be processed expeditiously, you must upload your response via the Internet at https://apps.fcc.gov/oetcf/els/index.cfm by clicking on the "Reply to Correspondence" hyperlink.

Responses to this correspondence must contain the Reference number : 33429


Document Created: 2016-08-05 11:19:04
Document Modified: 2016-08-05 11:19:04
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC