At a minimum, an ERP must address the elements outlined in IS-BAO Section 4.1.4 and NBAA Management Guide Section 1.1.6: authority notification procedures, activation of the emergency operations center, internal notification chains, family communication protocols, on-site crew procedures, flight data preservation, media relations, regulatory cooperation, trauma support, and business continuity. Beyond compliance, effective plans include proactive flight tracking that detects overdue aircraft before local authorities are notified; pre-written family notification scripts reviewed by trauma experts; designated spokespeople with media training; established relationships with medical, security, and crisis communication resources in primary operating regions; and scenarios covering events not explicitly addressed by regulations, such as cyber incidents, security breaches, natural disasters affecting base operations, and incidents involving non-employee passengers. Clearly documented roles and responsibilities are essential. The ERP should specify who leads the response, who makes key decisions, and who is responsible for functions such as operations, communications, family assistance, regulator liaison, crew support, passenger care, insurance, legal matters, and record-keeping. For business jet operators, the most critical test is whether the ERP remains operational and usable at 2am with a small team.