E-Mail generated [Aug 4 2016]

0038-EX-PL-2016 Correspondence

Georgia Institute of Technology

2016-08-04ELS_180341

Douglas Young From: Douglas Young Sent: Thursday, August 04, 2016 3:49 PM To: 'david.spencer@ae.gatech.edu' Subject: Request for Info - File #0038-EX-PL-2016 Attachments: Questions on Prox 1.docx Importance: High The following issues need to be addressed: 1. ODAR needs to be finalized and signed. 2. SpaceCap API contains two transmitting earth stations (W4AQL and Georgia Tech SSDL); however, Form 442 only shows one transmitting earth station (which appears to be W4AQL); please add the other transmitting earth station (Georgia Tech SSDL) that will be operating in this mission in the form 442 and make sure both form 442 and SpaceCap API are consistent with their technical parameters. 3. ODAR Section 4.4‐1: limiting risk of accidental explosions under 4.4‐1 limiting risk to other space systems from accidental explosions, the propulsion system was NOT consider as a possible explosion or failure; please add the propulsion system in this section as a potential risk to explosion or failure. 4. Section 5: Spacecraft potential for collisions: a Nanosat Terminator Tape is used to help the CubeSat in re‐entry. The terminator tape when deployed extends out of the spacecraft; this extension does not appears that was considered as in a potential collision and we feel that it be considered; see attached document for more detail. 5. the SpaceCap API boxes for RR 4.4 are blank and are NOT marked “Y”; the filing identify the station as Amateur (EA); for short mission like this one, typically applicant operate under RR 4.4 (Non‐interference basis and no protection basis); please let us know if your intention is to operate under RR 4.4 (NIB/NPB) and update the SpaceCap API accordingly or if you are seeking status (protection). Note that if you seek status, the systems needs to operate in accordance with the radio regulation and it will require coordination (domestically and internationally). 6. Form 442 list the frequency bands 430‐438 MHz uplink and 2280‐2310 downlink; the SpaceCap API list the 2298‐2299 MHz frequency range as the downlink; if the frequency range identify in the SpaceCap API is correct, please update form 442 to reflect this frequency range. Also, note that NASA may have some concerns with the 2298‐2299 MHz frequency range because the 2290‐2300 MHz is for space research service (deep space) in the space‐to‐Earth direction. If the applicant wishes to pursue this frequency range, we advise to pre‐coordinate with NASA as soon as possible. Please review carefully the downlink frequency and update the appropriate document accordingly. 7. the SpaceCap API emission designators and transmit power (on the uplink only) don’t match and are not encompass with the values in Form 442; please review both document and ensure that both are consistent with their parameters. 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 4, 2016 may result in application dismissal pursuant to Section 5.67 and forfeiture of the filing fee pursuant to Section 1.1108. 1


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