SC-04: Multi-Authority
| Field | Value |
|---|---|
| Scenario ID | PER-001-SC-04 |
| Context / Trigger | Julia submits a flight authorization request for a mapping mission that spans two jurisdictions: the county and an adjacent airport authority. The automated rules cannot fully approve the request; it requires manual review by both authorities (Further Coordination). |
Narrative
Julia submits the request 5 days before the scheduled mission. The FAS evaluates the request against both jurisdictions’ rules. The county’s automated rules pass, but the airport authority’s rules flag the request for manual review because the flight volume intersects the airport’s extended centerline. The FAS transitions the authorization to Pending state (UERQ-SYS-1412) and routes it to both authorities (UERQ-SYS-1413).
Julia receives a notification: “Your request requires manual authority review. Expected processing time: up to 90 days. Request will be auto-cancelled if not resolved 24 hours before proposed start time. No guarantee of resolution.” (UERQ-SYS-1415). The app shows the authorization in Pending state with a progress indicator showing which authorities have responded.
Over the next 2 days, Julia receives status update notifications (UERQ-SYS-1457): the county authority approves their portion. The airport authority’s decision is still pending. On day 3, the airport authority approves with an additional condition: altitude ceiling 200ft AGL within 1nm of the airport boundary. The FAS records both decisions (UERQ-SYS-1417), transitions the authorization to Accepted with the combined conditions, and notifies Julia.
Julia reviews the accepted authorization in the app. The combined conditions are clearly displayed: county conditions plus the airport’s 200ft ceiling restriction. She adjusts her mission plan to accommodate the lower ceiling near the airport and proceeds with the mission on the scheduled date.
Traceability
| Linked End Goals | Know exactly who needs to approve the flight and their status during manual review. |
| Linked Capabilities | Pending State Entry (UERQ-SYS-1412), Manual Review Routing (UERQ-SYS-1413), Manual Review Timeline Communication (UERQ-SYS-1415), Partial Authority Decision Handling (UERQ-SYS-1417), Pending Status Update Notifications (UERQ-SYS-1457), Overlapping Approval Jurisdictions (UERQ-SYS-1402). |
| Safety Relevance | Yes: The multi-authority approval chain is a safety process. Julia needs transparency into the chain to plan her mission and avoid launching without full authorization. |