1. What is Flight Release
Flight Release is the process whereby a designated “Approval Authority” evaluates an sUAS team’s operational plan, gives the final Go-No Go, then signs a document affirming the sortie is approved.
- Release is required for all sorties.
- A sortie release counts for all flights within the sortie.
- If, during the course of a sortie, situations change and risk level increases substantially, an amended flight release is needed and should be requested from the Approval Authority.
2. Who Can Release Flights
The decision for who can provide release is currently measured against the CAPR 70-4R sUAS Operational Risk Management Matrix, which has three levels of approval:
RISK LEVEL |
APPROVAL AUTHORITY REQUIRED |
LOW RISK (14‐27) |
BRIEFING OFFICER APPROVAL |
- The Remote Pilot in Command may authorize their own Low Risk Sorties during skill or proficiency training and flight evaluations.
- During an OPEX or an actual Corporate/AFAM Mission, you must seek authorization and Signature from whoever is overseeing your sUAS team. |
| MODERATE RISK (28‐37) | Ground Branch Director (GBD), Air Operations Branch Director (AOBD), Operations Section Chief (OSC) |
| HIGH RISK (38‐49) | Wing Commander (WING CC), Wing Director of Operations (WING DO), Wing Unmanned Systems Officer (WING DOU), Incident Commander (IC) of the OPEX or Mission. |
<aside>
💡 Releases can be done in-person or through the telephone, but cannot be done solely through text or email.
</aside>
<aside>
💡 Telephone releases may require digital signature of documents. Teams can streamline that process by familiarize themselves with methods for e-Signature.
</aside>