Launch and/or Deployment Notification Form

OMB Control Number: 0648-0174

Expiration Date: XX/XX/20XX

CUI//PRVCY/PROPIN//FEDCON

when filled in

Licensee Exempt from CUI Handling and Dissemination Restrictions

UNITED STATES DEPARTMENT OF COMMERCE
National Oceanic and Atmospheric Administration

Office of Space Commerce
Commercial Remote Sensing Regulatory Affairs
Washington, D.C. 20230

Launch and/or Deployment Notification Form

Pursuant to 15 C.F.R. § 960.8(e)(1), each licensee must “Notify the Secretary in writing of each of the following events, no later than seven days after the event: The launch and deployment of each system component, to include confirmation that the component matches the orbital parameters and data collection characteristics of the system, as described in Part D of the license.”

Instructions

This form may be filled out in multiple formats, including by email in Word document format by replacing blue guidance text with your responses using blue text or by filling out an electronic form associated with holding an account. If responding by Word document:

• Please remove all guidance text prior to submission.

• If you wish to submit the launch notification in Word document format through encrypted communications, please email crsra@noaa.gov for instructions.

If filling out the form electronically in an information system, confirmation of accessing a U.S. Government system may be required.

Any questions regarding this form should be directed to crsra@noaa.gov.

Privacy Act Statement

PRIVACY ACT STATEMENT: The authorities for the collection of the following information and the intended uses of the information are detailed online at the following link: CRSRA Privacy Act Statement. You may request a copy of the linked Privacy Act Statement by emailing crsra@noaa.gov.

• Confirmation of having read the Privacy Act Statement is required if filling out form in electronic format.

Notification Content

1. Operator name: (conditional)

This information is required for Word format submissions only and requires entry of the licensed operator name.

2. System: (required)

In the electronic user-account format, the operator will be able to select from their licensed systems. In the Word format, the operator is required to enter the name of the relevant system as it exists on the license.

3. Internal component (satellite) designator, if a part of a multi-spacecraft system: (required)

This field requires the operator to input their designator (“tail number” or name) for the specific satellite launched or deployed.

4. Does this notification pertain to a launch, a deployment, or both? (required)

Launch/Deployment/Both

5. Date upon which component launched: (conditional/required)

6. Date upon which component deployed: (conditional/required)

7. Does the component match the orbital parameters described in Part D of the license? (required)

Yes/No/Unable to Confirm

If selecting “No,” the user will be required to submit a modification request form at the conclusion of the notification form.

8. Please provide a description regarding why confirmation of orbital parameters cannot be provided: (conditional/required)

Text field entry if response to #7 is “Unable to Confirm.”

9. Does the component match the data collection characteristics described in Part D of the license? (required)

Yes/No/Unable to Confirm

If selecting “No,” the user will be required to submit a modification request form at the conclusion of the notification form.

10. Please provide a description regarding why confirmation of data collection characteristics cannot be provided: (conditional/required)

Text field entry if response to #9 is “Unable to Confirm.”

11. United States designator of the object (NORAD ID): (optional)

12. Are there any anomalies associated with launch, deployment, or early operations to report? (required)

Yes/No

13. Please provide a description of any anomalies experienced. (conditional)

Text field entry if response to #12 is “Yes.” Textual description of any unexpected event or abnormal characteristic affecting the operations of the system that could indicate a significant technical malfunction, including any deviation from the orbital parameters or data collection characteristics of the system.

14. Is a modification to the license requested? If so, please provide the accurate material facts and reason for modification request. (conditional/required)

In the event the response to #7 or #9 is “No,” or an anomaly reported in #12 and #13 affects the orbital parameters or data collection characteristics of the system, a modification request will be prompted or required, depending upon the circumstance.

15. Is there any additional information the operator would like to provide? (optional)

Operator will be able to provide additional information and attachments.

PRA Burden Statement:

A Federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with an information collection subject to the requirements of the Paperwork Reduction Act of 1995 unless the information collection has a currently valid OMB Control Number. The approved OMB Control Number for this information collection is 0648-0174. Without this approval, we could not conduct this information collection. Public reporting for this information collection is estimated to be approximately 30 minutes per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the information collection. All responses to this information collection are mandatory pursuant to 15 C.F.R § 960. This information is used by NOAA to record the details of a launch or deployment of a licensed remote sensing system. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden to the NOAA, 1401 Constitution Ave., NW Washington, D.C. 20230, Attn: CRSRA Director, Dr. Sarah Brothers, sarah.brothers@noaa.gov.

CUI//PRVCY/PROPIN//FEDCON

when filled in

Licensee Exempt from CUI Handling and Dissemination Restrictions