When an aircraft has a mechanical issue on the ramp, a passenger medical event during boarding, or a fuel discrepancy discovered mid-turn, the single biggest predictor of a clean outcome is not the severity of the event itself. It is whether the ramp agent standing next to the aircraft knows, without hesitation, who has the authority to make the next call. Private Aviation Technology Ltd. (PATL) builds emergency response procedures for ground handlers and operators across Asia that answer that question in writing, before the event happens, so the first ten minutes of an irregular operation follow a decision chain instead of a debate.
This matters because aviation authorities including EASA and the FAA, aligned with ICAO Annex 19, require ground handling organizations to document a clear chain of command within their Safety Management System (SMS) Emergency Response Plans (ERPs). The requirement is not paperwork for its own sake. It exists because the moment an irregular operation starts, every additional minute spent figuring out who decides is a minute the aircraft, passengers, or crew are exposed to unmanaged risk.
TL;DR
- IATA defines an irregular operation (IROPS) as any event that pushes actual operations off the published schedule, but it does not set a universal response-time standard; that is left to individual SLAs and local regulation.
- ICAO Annex 19 and Doc 9859 require ERPs to name, in writing, who holds decision authority at each stage of an emergency, not just what steps to follow.
- AOC holders in jurisdictions like Hong Kong (HKCAD) and Singapore (CAAS) remain responsible for outsourced ground handling and must be able to trace every incident back through documented agreements and SMS records.
- PATL designs decision-authority maps and escalation trees as a distinct deliverable from generic emergency checklists, built around the specific fleet, base, and contractor relationships of each client.
- The output is not a training manual; it is an audit-ready operational document that ramp staff, ground handlers, and AOC holders can point to when a regulator asks who decided what, and when.
About the Author: This article draws on PATL's work designing operations documentation and audit-ready SMS structures for aircraft operators and ground handling partners across Asia, including direct IS-BAO Stage 3 audit experience and multi-registry AOC compliance work led by team members with 15 years of combined military, commercial, and business aviation leadership.
What Counts as an Irregular Operation on the Ramp?
An irregular operation (IROPS) is any event that causes actual operations to deviate from the published schedule, whether that is severe weather, a mechanical failure, a ground equipment malfunction, or a medical incident during turnaround. IATA's definition is deliberately broad because the category has to cover everything from a fifteen-minute fueling delay to a full ramp evacuation. What IATA does not do is prescribe how fast an organization must respond or who must respond first; those specifics come from each operator's own service level agreements and the regulatory requirements of the jurisdiction where the aircraft sits.
That gap is exactly where problems show up in practice. A ground handler might have a technically compliant emergency manual that lists every conceivable scenario, yet still produce confusion on the ramp because the manual describes procedures without pinning a named role to each decision point. Staff can read what to do, but not who is allowed to say "do it." PATL's operations design work treats this distinction as the core problem to solve, not an afterthought to a checklist.
Why Does "Who Decides" Matter More Than "What To Do" in the First Ten Minutes?
The first ten minutes of an irregular operation are dominated by ambiguity, not by lack of information. Ramp staff usually know the mechanical symptom, the weather condition, or the medical complaint. What they often do not know instantly is whether they are authorized to hold the aircraft, call for emergency services, notify the AOC holder, or wait for a supervisor. Under ICAO Annex 19 and its supporting Safety Management Manual (Doc 9859), the ERP must document exactly this delegation of authority, assigning specific decision-making responsibility to named roles so the organization moves from normal to emergency operations without a gap in command.
Think of it the way a ship's watch schedule works. Every sailor on deck knows the tide tables and the weather forecast, but a ship does not turn because someone notices a storm; it turns because the officer of the watch, a specific named authority, gives the order. Remove that named authority and the same information produces hesitation instead of action. Ground handling is no different. A ramp agent who correctly identifies a fuel discrepancy but has no documented authority to stop the push-back is functionally in the same position as a sailor without an officer of the watch: correct observation, no sanctioned action.
This is the layer PATL adds to standard emergency documentation: an explicit decision-authority map, not just a procedural flowchart. Each scenario gets tied to a named role (ramp supervisor, duty manager, station manager, AOC holder representative) with the specific action that role is authorized to take, and the point at which authority escalates upward.
How Does PATL Translate Regulatory Language Into a Ramp-Level Decision Chain?
Regulatory text describes obligations at the level of the organization; ramp staff need direction at the level of the individual. PATL's operations design process bridges that gap in three stages.
- Map the regulatory obligation to a named role. If HKCAD or CAAS rules place ultimate responsibility for outsourced ground handling with the AOC holder, that obligation has to be translated into a specific reporting line between the ground handler's shift supervisor and the AOC holder's operations control, not left as a general statement of accountability.
- Sequence the escalation by time, not just severity. A decision tree built only around severity ("minor, major, critical") tends to blur under stress. PATL structures escalation around elapsed time from event detection, so the ramp team has a concrete answer to "what should have happened by now" at the two-minute, five-minute, and ten-minute marks.
- Attach the communication protocol to each decision point. Every handoff of authority includes who must be notified, by what channel, and within what window, closing the loop that regulators specifically look for during SMS reviews.
The table below illustrates the structural difference between a generic checklist and a decision-authority map for the same scenario.
| Element | Generic Emergency Checklist | PATL Decision-Authority Structure | |---|---|---| | Format | Sequential task list | Named role tied to each decision and time window | | Authority | Implied or assumed | Explicitly documented per ICAO Annex 19 / Doc 9859 | | Escalation trigger | Severity-based only | Severity plus elapsed time from detection | | Traceability | Task completion | Full record linking decision, decider, and timestamp | | Audit readiness | Requires reconstruction | Built for direct regulator or AOC holder review |
What Role Does AOC-Holder Traceability Play in Ground Handling Emergencies?
Traceability is the requirement that ties the ramp-level decision chain back to the AOC holder's legal accountability. Under AOC compliance regimes in jurisdictions such as Hong Kong (HKCAD) and Singapore (CAAS), the AOC holder retains ultimate responsibility for ground handling even when that work is outsourced to a third-party handler. That responsibility requires documented ground handling agreements, integration of the contractor's incident reporting into the AOC holder's SMS, and auditable records that show safety performance and corrective actions over time.
In practice, this means the decision-authority map PATL builds for a ground handler cannot exist in isolation. It has to interlock with the AOC holder's own SMS reporting structure, so that when a ramp supervisor makes a call at minute three of an irregular operation, that decision is captured in a record the AOC holder can produce during an IS-BAO or regulatory audit months later. This is the same discipline Ray Wilson applies as an IS-BAO Stage 3 auditor: the question an auditor asks is rarely "did something go wrong," it is "can you show me who decided, when, and on what authority."
How Should an Operator Start Building This Kind of Decision Chain?
Start by testing the current emergency documentation against a single question: for the three most likely irregular operations at your busiest station, can a ramp agent name the person authorized to make the first call within two minutes of detection? If the answer requires checking a manual, the authority is not documented clearly enough, regardless of how detailed the procedural steps are.
- Identify the five or six most probable IROPS scenarios for the specific fleet and station, not a generic industry list.
- Assign a named role, not a department, to the first decision point in each scenario.
- Set explicit time windows for escalation rather than relying on severity judgment alone under stress.
- Confirm the escalation path connects to the AOC holder's SMS reporting, closing the traceability loop regulators check for.
- Test the chain with the actual ramp team, not just management, since gaps usually surface at the point of execution.
Building on that structural detail, the harder problem for most operators expanding across multiple stations in Asia is keeping this decision chain consistent when local ground handlers, airport authorities, and staffing levels differ from base to base. That consistency work, translating one operator's authority structure across several jurisdictions without losing audit-readiness at any single station, is where PATL's combination of AOC compliance expertise, IS-BAO audit experience, and enterprise data integration knowledge from Bernard Lee's background becomes distinct from a general aviation advisory engagement.
Frequently Asked Questions
Is an irregular operation the same as an emergency? No. IROPS covers any deviation from published schedule, including routine delays from weather or mechanical issues. An emergency is a subset of IROPS involving direct risk to safety, but the decision-authority principles apply across both.
Who is legally responsible when a ground handler makes the wrong call during an IROPS event? Responsibility depends on the ground handling agreement and jurisdiction, but under regimes like HKCAD and CAAS, the AOC holder retains ultimate responsibility for outsourced ground handling and must be able to trace the incident through its own SMS records.
Does IATA require a specific response time for irregular operations? No. IATA defines IROPS but leaves specific response timeframes to individual SLAs and local regulatory requirements rather than setting one universal standard.
What is the difference between an ERP and an SMS? The SMS is the organization's overall framework for managing safety risk. The ERP is a specific component of the SMS that documents how the organization responds to emergencies, including the delegation of decision authority under ICAO Annex 19.
Can a small ground handling operation use the same decision-authority structure as a large one? The principle scales down, though the roles may be fewer. A single-station handler still needs a named decision-maker for each scenario; the structure just involves fewer layers of escalation than a multi-station operator.
How often should this documentation be reviewed? Review frequency should follow changes in fleet, station, staffing, or contractor relationships, and should also align with IS-BAO or internal audit cycles rather than a fixed calendar interval alone.
Does this apply to FBOs as well as ground handlers? Yes. FBOs face the same first-response ambiguity during irregular operations and are within PATL's expansion focus alongside aircraft owners and operators.
About Private Aviation Technology Ltd.
Private Aviation Technology Ltd. (PATL) is an independent consulting firm based in Hong Kong that solves the operational and regulatory problems underlying private aviation, including costing architecture, operations design, AOC compliance support, and IS-BAO and IS-BAH audit preparation. The firm's engagements are strictly confidential, and its team combines Ray Wilson's IS-BAO Stage 3 audit and multi-registry AOC experience, Jolie Howard's background as a former Asia private aviation CEO, and Bernard Lee's enterprise systems and data integration expertise. As the sister company of L'VOYAGE (founded 2014), a Hong Kong private aviation consultancy, PATL draws on more than a decade of regional operator relationships and regulatory familiarity while building toward global expansion beyond Asia and into FBO and ground handler markets.
If your ground handling or operations documentation cannot yet answer who decides in the first ten minutes of an irregular operation, that gap is worth closing before an auditor or a regulator finds it first. Get in touch with PATL at https://www.privateaviationtech.com/ to talk through your specific fleet, stations, and contractor structure.