Instructions for the Certificate of Waiver or Authorization
The 7711-2 form is required for beyond visual line of sight (BVLOS) UAS/drone operators who are seeking waivers and/or exemptions for Part 91 operations. Drone operators seeking waivers or exemptions for Part 107 operations should consult the corresponding Waiver Safety Explanation Guidance.
UAS operators requesting a Certificate of Waiver or Authorization for an aviation event or other advanced operations will need to complete Certificate of Waiver or Authorization (Form FAA 7711-2). It is important that the applicant read the Form directions carefully and provide all necessary information.
The FAA has created the below step-by-step application guide to assist applicants in navigating the complex fields and ensure an efficient review process.
How do I apply?
Applicants should fill out the Certificate of Waiver or Authorization application. Applicants may find that some items are not relevant to their operation and are not required to fill out those fields. The relevant fields should be filled out thoroughly and completely.
Send the completed form, supporting documents, and/or any questions via email to 9-UAS-91.113Waivers@faa.gov.
How will my application be evaluated?
The FAA does not consider the application complete until it is determined that all necessary information has been provided. Guidance for filling out the form can be found below. It is important for applicants to carefully review the instructions for Item 7, which asks for a detailed description of the proposed operation and the multiple topics to include. Addressing each topic area in the order it is listed will assist in the determination of thoroughness and efficient review of the application.
Form Field Guidance
1-3. Applicants should provide current contact information.
- Name of organization
- Name of responsible person
- Permanent mailing address
- House number and street or route number
- City State and ZIP code
- Telephone No.
Email addresses may also be provided, either in this section or under Remarks (following the signature line on the last page of this form).
4. State whether the applicant or any of its principal officers/owners has an application for waiver pending at any other office of the FAA.
- Provide details for other waiver requests, such as a request number or other identifying information provided by FAADroneZone, or the FAA point of contact for other requests.
5. State whether the applicant or any of its principal officers owners has ever had its application for waiver denied, or whether the FAA has ever withdrawn a waiver from the applicant or any of its principal officers/owners.
- Provide details for any previously denied waiver requests, such as a request number or other identifying information provided by FAADroneZone, or the FAA point of contact for those requests.
6. FAR section and number to be waived
In addition to the specific section and number for which you are seeking a waiver, indicate the following, either in this Item or under Item 7:
- Identify if this operation is a Public Part 91 (PAO) or a Civil operation.
- For PAO, does the operation meet 49 U.S.C. § 40125 requirements?
- For Civil operations, what certification will the operation take part under?
- List any certification request that has been initiated for the operation under the indicated part. (e.g., Part 135, Part 137)
- List any other prior agreements or approvals provided by the FAA for your equipment or operation (e.g., LOA, COA, Equipment Certifications, licenses, etc.).
7. Detailed description of proposed operation (Attach supplement if needed)
This item seeks a “detailed description of proposed operation.” Applicants should consider the following topics in response to this item. A full Concept of Operations (ConOps) document is not required. Additional information that is not directly related to the safety case for the intended operation, and that does not address any of the following topic areas, is generally not necessary.
Spectrum
- Make, model, and FCC Equipment ID Number for each piece of RF Equipment used for the operation (onboard or external).
- Equipment authorization grant.
- Note: FAA generally does not accept experimental licenses or grants for BVLOS operations.
- Documentation of any licenses held for equipment used for the operation.
Inflight Operations
- Identify if the UAS will operate above 400 ft. AGL or above UAS Facility Map Altitudes.
- Altitude range that the operation will take place [i.e., Minimum Altitude (MSL), Minimum Altitude (AGL), Maximum Altitude (MSL), and Maximum Altitude (AGL)].
- Operating speed range of the UAS.
- RPIC location at the point of launch/takeoff.
- Describe how preflight checks and preparations are conducted if RPIC is not co-located at the point of takeoff.
- Class(es) of airspace that the operation will be conducted in [e.g., Class A, B, C, D, E, G, High E (Above FL600), SUA, Restricted].
- List all mitigations that are being proposed to satisfy the requirements of 14 C.F.R. § 91.113 and § 91.155. Some examples are identified below, but may not be all-inclusive:
- Tactical collision avoidance (DAA) using:
- Onboard hardware/software
- Ground-based hardware/software, not including FAA systems (includes UTM or third-party services)
- FAA-overseen/managed ground-based hardware/software, including surveillance sensors or other data sources
- Chase plane
- Separation services based on ATO policy and procedures
- Coordination/communication with ATC facilities
- Airframe-based solutions (e.g., lighting, markings)
- Pilot/operator training, qualifications or procedures
- Geofencing/containment systems to remain within a defined volume (or to avoid a defined volume)
- Operator use of NAS-based information
- Navigation using NAS systems/technology
- Charting provided by the FAA
- Visual observers for collision avoidance
- Visual observers qualified to assess meteorological conditions
- Onboard meteorological/optical sensors
- Official aviation weather sources or products (e.g., METAR, TAF, ASOS/AWOS, NWS/CWSU forecasts, etc.)
- Personal weather stations
- Commercial weather forecast services
- Other means of collision avoidance
- Other means of assessing meteorological conditions
- Provide additional details for each mitigation to 14 C.F.R. § 91.113(b) and § 91.155 (e.g., Documentation of technical capabilities, adherence to applicable standards, procedures that apply to flight operations personnel, etc.).
Cargo Information
- If not operating under Part 135, identify if the UAS will be used for cargo transport.
- Will the cargo contain any hazardous materials?
- What type of hazardous cargo will be transported by the UAS?
Command and Control
- Command and Control (C2) Link type (e.g., Wi-Fi, Radio, Satellite/Iridium, Bluetooth, Cell Network, etc.).
- C2 Lost Link Latency Threshold (in seconds).
- C2 Lost Link Procedure Type (e.g., Continue Flight, Hover in place until connection reestablished, Return to launch site, Enter a holding pattern until connection reestablished, Land at a designated waypoint, Land Immediately, etc.).
- Any additional details on lost link procedures.
Navigation Information
- List type of navigation system(s) that are used by the UAS (e.g., GNSS, Optical, Inertial).
- Latency threshold for navigation failure/degradation (in seconds).
- Contingency procedure for navigation failure/degradation (e.g., Continue Flight, Hover in place until connection reestablished, Return to launch site, Enter a holding pattern until connection reestablished, Land at a designated waypoint, Land Immediately, etc.).
- Additional details about contingency procedure for navigation failure/degradation.
- Geofencing during the operations.
- Type (i.e., horizontal and/or vertical).
- Geofencing area (expressed in feet).
- Any additional details of use of Geofencing during the operation.
Aircraft and Crew
- Identify if the design of the UA enables it to break apart on impact.
- List all other crewmembers to be utilized (e.g., Visual Observers, GCS Operators, Safety Official, Manager, etc.).
- Identify how crewmembers will communicate (e.g., Radio, Landline, Cell Phone).
- Will communication be continuous or as needed?
- Level of automation in use for the operation. Examples include:
- Manual: Human control of the UA via remote device.
- Semi-Automatic: Operator initiated, pre-programmed mission where the operator can regain manual control.
- Automatic: Operator initiated, pre-programmed mission where the operator cannot regain manual control but may relay pre-determined commands (e.g., land, RTB, etc.).
- Semi-Autonomous: Operator or aircraft initiated, capable of carrying out a dynamic mission without human intervention but cannot perform actions beyond pre-programmed tasks.
- Autonomous: UAS is able to conduct a safe flight without the intervention of a pilot. It does so with the help of artificial intelligence, enabling it to cope with all kinds of unforeseen and unpredictable emergency situations.
Operational Details
- Description of the performance characteristics of the UAS planned for the operation.
- Description of operational and communications procedures.
- Description of the safety protocols in place.
- High-level description of the proposed mission and overall purpose.
- Identification of the safety- and hazard-related data and metrics that will be collected in the course of operations.
Assumptions, Hazards, and Risks
- Identification of the assumptions, hazards, and risks to the operation.
- Assumptions being applied to the operation.
- Identified Risks and/or Hazards in performing the operation(s) in the manner being requested.
8. Area of operation (Location, altitudes, etc.)
This information can be represented in many different ways, as the examples below show. In general, the more specific the information, the more accurately FAA can assess ground and air risk factors, as well as the suitability of the applicant’s mitigation measures.
- State(s)
- City(s)/Town(s)
- Or nearest city(s)/town(s) if not conducted within the boundaries of a city/town.
- Boundaries of the operation
- Latitude/longitude for the boundary points or radius from a central point for the proposed operation area.
- If the intended flight is a route(s) of flight from point to point, the intended flight path(s).
- Visual representation of the operations area boundaries or route of flight overlaid on a visual geospatial product (e.g., Google Maps, aeronautical chart overlay, etc.).
- Latitude/longitude coordinates represented as degrees, minutes, and seconds.
- If the intended operation originates and/or terminates at an airport:
- Airport(s) where the operation(s) will take place.
- How will the UAS takeoff from the airport (e.g., conventional rolling, vertical liftoff, catapult, etc.)? (may be addressed under Item 7)
- How will the UAS land or be recovered at the airport (e.g., conventional rolling, vertical landing, catch, etc.)? (may be addressed under Item 7)
9a-b. Beginning and ending time (Date and hour)
Applicants may also indicate general time ranges (e.g., daylight hours only) if a specific time or date is not applicable or has yet to be determined. An ending date should be provided if one exists; otherwise, indicate that the operation is ongoing indefinitely.
10. Aircraft details
- Make and model (10a)
- Pilot's Name (10b)
- Certificate number and rating (10c)
- Home address (Street, City, State) (10d)
Note: Further details about the aircraft may also be addressed under Item 7.
Aircraft Information:
- Type (e.g., Multi-rotor, Fixed Wing, Single Rotor, Tilt Rotor, Hybrid, Lighter than Air)
- Make
- Model
- Registration Number
- Serial Number
- Aircraft Weight (in pounds)
- Without Payload/Cargo
- Max Payload/Cargo
11-16. These items need not be completed for UAS operations, unless the operation is in for an air show or race.
I applied, what comes next?
Once the application is complete, the FAA will begin tracking the length of the review and approval period. The instructions provided above are intended to reduce the need for the FAA to request additional information from the UAS applicant, which can often delay the processing of waiver requests.