The IS-BAO Emergency Response Plan Requirement: What Asian Flight Departments Document Versus What Auditors Actually Test on the Day
Most Asian flight departments treat the IS-BAO Emergency Response Plan (ERP) requirement as a documentation exercise. They produce a well-formatted plan, file it in their Safety Management System binder, and consider the box ticked. What IS-BAO auditors actually test on the day is something quite different: they look for evidence that real people, in real roles, with real contact details and practiced responses, can activate the plan under pressure. That gap between documented intention and demonstrated capability is where most flight departments in Asia lose points at Stage 1 and stall at Stage 2.
TL;DR
- IS-BAO’s ERP requirement is not satisfied by a written plan alone; auditors probe activation readiness, role clarity, and drill records.
- Asian flight departments commonly over-invest in formatting the ERP and under-invest in testing it.
- The three areas auditors examine most closely are the Crisis Management post structure, communication trees, and evidence of recent exercises.
- Documented plans that reference outdated contacts, unnamed “designates,” or unexercised procedures are the most common findings.
- Closing the gap requires treating the ERP as a living operational document, not a compliance artifact.
About the Author: Private Aviation Technology Ltd. (PATL) supports private flight departments and aircraft operators across Asia in designing audit-ready Safety Management Systems, including IS-BAO Stage 1, 2, and 3 preparation. PATL’s lead IS-BAO auditor, Ray Wilson, holds Stage 3 credentials with 15 years of leadership across military, commercial, and business aviation.
What Does IS-BAO Actually Require in an Emergency Response Plan?
The IS-BAO standard requires that an operator maintain a documented ERP that is integrated into its Safety Management System and is tested at regular intervals [nbaa.org]. The plan must identify specific post-holders responsible for managing an emergency, define how internal and external communications flow, and address coordination with authorities, medical services, and family contacts [aircrewacademy.com]. The standard does not prescribe a single format, but it does prescribe function: the plan must be operational, not merely descriptive.
IS-BAO aligns with ICAO guidance on SMS emergency preparedness, which requires that ERPs address multiple emergency categories including accidents, fires, hazardous material events, and security incidents [aviationsafetyblog.asms-pro.com]. For flight departments operating across Asia, that ICAO alignment matters because it ties the IS-BAO ERP directly to what national civil aviation authorities expect to see if an incident actually occurs.
Key ERP components IS-BAO auditors look for:
- A defined Crisis Management post with a named individual (not a job title alone)
- A Communications post responsible for managing media, family, and authority contact
- An Operations post responsible for site coordination and continuing flight safety [flightsafety.org]
- Written procedures for each post, not just a responsibility list
- A contact directory that is current, tested, and accessible outside of normal working hours
- Evidence of at least one tabletop or live drill within the review period [medaire.com]
What Do Asian Flight Departments Typically Submit?
Building on the requirements above, the harder question is why well-resourced flight departments still arrive at audits with materially deficient ERPs. The answer is structural: most Asian operators model their ERP on a document template rather than on an activation scenario.
Common patterns in submitted documentation across the region:
| What the Document Contains | What Auditors Find Insufficient |
|---|---|
| Three named posts with job titles | No named individual; role is vacant or the holder has left |
| A communication tree diagram | Diagram lists office numbers, not personal mobiles |
| ”Annual drill to be conducted” | No drill record, no date, no participants listed |
| Coordination with “relevant authorities” | No specific authority names, no MOU or contact established |
| ”Family Liaison Officer to be assigned” | Position unnamed; no training record |
| Reference to a “go-bag” with documents | Go-bag contents not listed; location not specified |
The documentation looks structured. The underlying readiness requires testing and validation.
One pattern specific to Asia is that flight departments managed by a single chief pilot or a small team tend to consolidate all three ERP posts into one or two people. That is permissible under IS-BAO for small operations, but auditors then expect more rigorous evidence that the named individuals have actually rehearsed both their own role and a backup role. That evidence is rarely present.
What Do Auditors Actually Test on the Day?
Stepping back from the document review, a separate concern is the audit method itself. IS-BAO auditors do not simply read plans. They interview post-holders to verify that the individuals named in the plan know what the plan says and can describe what they would do in the first thirty minutes of an activation [flightsafety.org].
Specific probes auditors use in practice:
- “Walk me through what you do in the first call.” This tests whether the named Communications post holder has a scripted or practiced initial response, or whether they are improvising from the document.
- “Who covers this role if you are aboard the aircraft?” This tests whether deputy assignments exist and are documented.
- “When was your last drill? What scenario did you run?” This tests whether drill records exist, what scenarios were chosen, and whether findings from the drill were captured and addressed [medaire.com].
- “Where is the ERP positioned in your Safety Management System?” This tests integration, not isolation. An ERP filed separately from the SMS is a finding.
- “What is the first external call you make, and to whom?” This tests whether authority contacts are specific and current.
A finding at this level does not mean the flight department is unsafe. It means the operator cannot demonstrate that safety intent translates into practiced capability. That distinction matters to IS-BAO Stage 2 and Stage 3 assessors, who expect progressive improvement in drill fidelity and cross-post rehearsal as an operator matures through the stages [lvoyage.aero].
How Should Flight Departments Close the Gap?
Closing the gap is less about writing a better plan and more about designing the ERP as an operational document that is maintained and exercised on a calendar. A practical approach:
- Assign named individuals, not positions. Every post in the ERP must have a first name, a personal mobile number, and a designated backup.
- Run a tabletop drill at least once per year. Use a realistic scenario specific to your operation and geography (e.g., an incident at a secondary airport in a jurisdiction where your AOC does not have a direct relationship with the local authority). Record who attended, what decisions were made, and what gaps were identified [medaire.com].
- Log all drill findings and close them. An open finding from a prior drill that appears at the next audit is a red flag. Closed findings with dates are evidence of a functioning SMS.
- Cross-reference the ERP with your SMS documentation index. Auditors expect to see the ERP cited in the SMS and navigable from the SMS table of contents [nbaa.org].
- Review the contact directory every six months. Contacts go stale. Authorities change liaison personnel. A communication tree with dead numbers fails at the worst possible moment.
- Brief all post-holders on IS-BAO’s specific language. When an auditor asks “what is your role under the ERP,” the answer should reflect IS-BAO’s three-post structure, not a generic description of crisis management [aircrewacademy.com].
Frequently Asked Questions
What is the difference between an ERP and an SMS emergency procedure? The ERP is a standalone activation document that defines who does what in a declared emergency. SMS emergency procedures are the broader category of policies governing how the safety management system responds to safety events. The ERP is a required component of the SMS, not a synonym for it [aviationsafetyblog.asms-pro.com].
Does IS-BAO require a live drill or is a tabletop exercise sufficient? IS-BAO accepts tabletop exercises as evidence of ERP testing, provided they are structured, recorded, and followed by a review of findings [medaire.com]. Live drills are not mandatory at Stage 1 but are expected to increase in fidelity as an operator progresses through the stages.
Can a small flight department merge the three ERP posts into one person? Small operations may have one or two individuals covering multiple posts, but each post’s responsibilities must still be documented separately, and the individual(s) must demonstrate familiarity with each role during the audit interview [flightsafety.org].
How far in advance should an operator prepare the ERP before an IS-BAO audit? The ERP should be in place and exercised before the audit, with at least one drill record available. Preparing an ERP in the weeks immediately before the audit, with no drill history, is a common finding and auditors can identify it [aircrewacademy.com].
What happens if an auditor finds the ERP deficient? Deficiencies are recorded as findings. Minor findings require a corrective action plan. Major findings can prevent stage certification until resolved. Recurring ERP findings across audit cycles signal systemic SMS weakness.
Is the ERP requirement different for IS-BAH (helipad) operators? IS-BAH has its own ERP requirements aligned with helipad-specific risks. The structural logic is similar (named posts, communication trees, drill records), but the scenarios and authority contacts differ. PATL supports IS-BAH preparation separately from IS-BAO engagements.
Do Asian regulators require an ERP independently of IS-BAO? Yes. ICAO Annex standards, which most Asian civil aviation authorities have adopted, independently require operators and airport entities to maintain ERPs [aviationsafetyblog.asms-pro.com]. IS-BAO compliance supports but does not replace regulatory ERP obligations under national law.
About Private Aviation Technology Ltd.
Private Aviation Technology Ltd. (PATL) is an independent, strictly confidential firm that helps private flight departments, aircraft owners, and operators across Asia design and validate Safety Management Systems for IS-BAO Stage 1, 2, and 3 certification, AOC compliance across multiple registries, operations design, and the documentation and tooling that make safety intent demonstrable on the day of an audit. PATL is the sister company of L’VOYAGE (founded 2014), which operates the client-facing private aviation travel and charter side of the business across Asia. PATL focuses on the technical and operational architecture-regulatory compliance, costing architecture, operations design, and audit readiness-that sits underneath client-facing work. The team combines aviation leadership, enterprise technology expertise, and military and commercial aviation backgrounds within a single firm, so clients receive end-to-end operational architecture rather than an isolated audit service.
Ready to close the gap between your ERP documentation and audit-day readiness? Visit privateaviationtech.com to speak with PATL’s IS-BAO specialists.