How to Design an Operational Approval Hierarchy for Private Aviation: Who Can Authorise a Flight When the Accountable Executive Is Unreachable?
When the Accountable Executive (AE) is unreachable, a private aviation operation without a formally documented approval hierarchy either grounds the aircraft unnecessarily or, more dangerously, authorises the flight through informal channels that leave no audit trail. The approval hierarchy is the pre-defined chain of authority that specifies exactly who holds delegated power to approve a flight, a route change, or a crew substitution at each level of operational urgency, and under what documented conditions that authority activates. Designing this hierarchy correctly is not a governance formality; aviation oversight explicitly evaluates the continuing competence of the management team and the Accountable Manager’s role caa.co.uk, while IS-BAO applies an SMS framework tailored to business aviation ibac.org.
TL;DR
- An operational approval hierarchy defines who can authorise key flight decisions when the AE is unavailable, and it must be documented, not assumed.
- The hierarchy must cover three distinct decision types: flight authorisation, route changes, and crew substitutions, each with different risk profiles and approval thresholds.
- Delegation of authority is only valid when it is pre-authorised in writing, role-specific, and traceable in the operations manual.
- IS-BAO Stage 2 and Stage 3 audits specifically examine whether the authority chain functions without the AE present.
- Gaps in this hierarchy are among the most common findings in operational audits of private flight departments across Asia.
About the Author: Private Aviation Technology Ltd. (PATL) designs operational approval structures and compliance frameworks for private aviation operators across Asia. PATL’s team includes Ray Wilson, an IS-BAO Stage 3 auditor with 15 years of leadership across military, commercial, and business aviation, giving the firm direct, fieldwork-grounded expertise on exactly the audit findings and operational failures this article addresses.
Why Does the Accountable Executive’s Absence Create an Operational Risk?
The AE is the single individual who bears ultimate regulatory accountability for the safety of an air operator’s operations. Under IS-BAO and most civil aviation authority frameworks governing private operators, the AE’s authority is personal and cannot be informally passed to another person in the moment. This matters because private flight operations do not pause for schedule conflicts, time-zone gaps, or medical unavailability.
The failure mode is predictable: without a pre-documented hierarchy, operations staff escalate to whoever is senior and available, decisions are made without recorded authority, and the operator cannot demonstrate to an auditor that the correct approval chain was followed. In IS-BAO Stage 2 and Stage 3 assessments, this gap surfaces repeatedly as a non-conformance, not because the decision itself was wrong, but because the authority to make it was not architecturally assigned in advance.
What Are the Three Decision Types That Require Separate Authority Mapping?
Building on the risk above, the harder design question is that “flight approval” is not a single decision. Private aviation operations present at least three structurally different decision types, each carrying a different risk weight and therefore requiring a separately calibrated authority threshold.
| Decision Type | Core Risk | Why It Needs a Separate Authority Level |
|---|---|---|
| Flight Authorisation | Airworthiness, crew fitness, load, weather | Highest risk; requires a qualified Nominated Person or DO-equivalent |
| Route Change | Airspace, overflight permits, alternates, fuel | Operational risk depends on change magnitude; minor vs. significant deviations need different thresholds |
| Crew Substitution | Crew currency, type rating, rest compliance, pairing rules | Regulatory compliance risk; wrong substitution can breach AOC conditions |
Each of these must have its own named role (or role-type) assigned in the operations manual, with explicit conditions under which the substitution authority activates. Mapping all three to the same person at the same threshold produces a bottleneck and, in many Asian operations where a single Director of Operations covers multiple bases, a single point of failure.
How Should Delegated Authority Be Documented to Be Audit-Valid?
A delegated authority is only as defensible as its paper trail. “The Chief Pilot can approve flights when the AE is away” is not documentation; it is an assumption. Audit-valid delegation requires four elements:
- Pre-authorisation in writing: The AE (or the Board, for corporate flight departments) must sign a formal Delegation of Authority document before the absence, not during it.
- Role-specificity: Authority is assigned to a role, not a named individual, so that personnel changes do not automatically void the delegation.
- Scope boundaries: The document must state what the delegate can and cannot authorise. An Operations Manager delegated to approve domestic route changes is not automatically authorised to approve international re-routings that trigger new overflight permits.
- Traceability to the operations manual: Every delegation must reference the relevant section of the Operations Manual or Safety Management System (SMS) document set, so an auditor can trace authority from the manual to the individual decision record.
PATL’s operations design engagements routinely find that operators have informal understandings of who covers for whom, but fewer than half have those understandings written into the operations manual in a form that would survive an IS-BAO audit without a finding.
What Is the Practical Structure of a Four-Tier Authority Hierarchy?
Stepping back from documentation mechanics, the structural design question is how many tiers the hierarchy needs. A single-aircraft operator in Hong Kong has different constraints than a multi-aircraft, multi-registry operator across several Asian jurisdictions. However, a four-tier model provides a practical starting framework that scales in both directions:
Tier 1 - Accountable Executive: Full authority across all decision types. Unreachable trigger activates Tier 2.
Tier 2 - Nominated Person / Director of Operations: Pre-authorised to approve flight authorisations and significant route changes. Crew substitution authority limited to within-type substitutions that do not affect AOC currency requirements.
Tier 3 - Chief Pilot / Senior Nominated Crew Member: Pre-authorised to approve crew substitutions and minor route changes (alternates, holding fuel adjustments). Cannot authorise a flight from scratch without Tier 2 confirmation except under a declared operational contingency.
Tier 4 - Pilot-in-Command (PIC): Authority is aircraft-based and legally established under the relevant civil aviation rules. The PIC retains final safety authority over the aircraft but is not a substitute for the organisational approval chain above.
The explicit unreachability trigger between tiers is the design detail most operators omit. “Unreachable” must be defined: Does it mean no response within 30 minutes? One hour? Via which channels? A well-designed hierarchy specifies the escalation timeline and the communication method (phone, email, secure operations platform) before authority passes to the next tier.
How Does This Connect to IS-BAO Audit Readiness?
A related but distinct concern from day-to-day operations is what this hierarchy looks like to an auditor. IS-BAO Stage 2 and Stage 3 assessments evaluate not only whether the documents exist, but whether the hierarchy has been tested and whether staff can demonstrate they know their authority boundaries without referring to a manual for the first time.
Ray Wilson, PATL’s IS-BAO Stage 3 auditor, notes that auditors look specifically for evidence of the hierarchy functioning under realistic conditions: Are there decision records that show Tier 2 or Tier 3 authority was exercised? Does the SMS include a post-exercise review of those decisions? Operators who have built the hierarchy but never tested it typically fail this portion of the Stage 3 assessment.
Frequently Asked Questions
Can the AE verbally delegate authority during a call? Verbal delegation creates no audit trail and is unlikely to satisfy a civil aviation authority or IS-BAO auditor. Pre-written, role-specific delegation documents are the minimum standard.
Does the PIC’s legal authority replace the need for an organisational hierarchy? No. PIC authority governs aircraft safety decisions once airborne. The organisational approval chain governs whether the flight should be authorised to depart at all. These are separate authority domains.
How often should the delegation documents be reviewed? At minimum annually, and immediately following any change in personnel in a nominated role. Changes to the AOC or operations manual trigger a mandatory review.
What happens if Tier 2 is also unreachable? The hierarchy must define a contingency rule for this scenario, which typically includes a mandatory stand-down unless the PIC invokes a declared operational safety emergency. This contingency must also be documented.
Is a four-tier model suitable for a single-aircraft owner-operator? For very small operations, Tiers 1 and 2 may be the same individual. The documentation principle still applies; the AE must still pre-authorise a named fallback for each decision type.
Does this apply to FBOs and ground handlers? FBOs and ground handlers have a narrower scope of operational authority, but service authorisation hierarchies (who can approve a late gate access request, a fuel uplift override, or a de-icing decision) follow the same documentation and traceability principles.
How does multi-registry operation affect the hierarchy design? Each registry may impose its own requirements on who holds nominated post-holder authority. A multi-registry operation may need parallel delegation documents that satisfy each registry independently, a complexity that PATL’s multi-registry AOC compliance work specifically addresses.
About Private Aviation Technology Ltd.
Private Aviation Technology Ltd. (PATL) is an independent, strictly confidential consulting firm that designs operational and compliance architectures for private aviation operators, flight departments, and aircraft owners across Asia, with active expansion toward global markets and FBO/ground handler clients. PATL’s team combines Ray Wilson’s IS-BAO Stage 3 auditing credentials and 15 years of military, commercial, and business aviation leadership, Jolie Howard’s experience as a CEO in the Asia private aviation sector, and Bernard Lee’s enterprise systems and data integration expertise, a combination no single-discipline audit or advisory firm replicates. PATL is the sister company of L’VOYAGE, which has operated in Hong Kong private aviation since 2014, giving PATL direct access to a decade of on-the-ground operator network experience and regulatory familiarity across the region. Where other firms offer point-in-time audits or generic compliance checklists, PATL embeds the approval hierarchy into the operations manual, the SMS, and the operator’s workflow tooling so the structure functions under real conditions.
If your operation lacks a formally documented, audit-tested approval hierarchy, or if a recent assessment identified gaps in your authority chain, contact Private Aviation Technology Ltd. at https://www.privateaviationtech.com/ to discuss how an operational design engagement can resolve the gap before your next audit.