1. Emergency Response

Information and training on this aspect of emergency procedures is found under O-5009 — Demonstrate the ability to initiate emergency procedures for a lost link, battery failure, or other in-flight emergency

2. Reporting a Safety Significant Occurrence (SSO)

<aside> 💡 From P-2014 — Discuss CAP Liability Coverage and SSO Reporting

</aside>

  1. Emergency Response. Use available checklists and crew actions to resolve the emergency.
  2. Did the emergency result in an SSO? If there is damage greater than broken propellers, or damage to personal property of You or Others, or injury to crew members or non-participants, that qualifies as an SSO. Proceed with steps 3, 4.
  3. Gather information about the SSO. CAP publishes the SSO Information Collection Worksheet that helps you collect the Who, What, When, Where, Why and How. It can be found (here). Integrate this into your UIF.
  4. Notify. Each Wing usually has a safety pyramid with instructions on who to call right after an SSO occurs. Work with your unit’s safety officer to obtain this pyramid ahead of time and include in the UIF for quick reference. When an SSO happens, call the appropriate party to notify.
  5. Report the SSO. Contact your Unit’s Safety Officer. They will help. Use the CAPSIS Safety Reporting Guide found (here). You have 48 hours to file a report.

<aside> ⚠️

Regarding NTSB notification, CAP has released mandatory WMIRS messages clarifying that CAP HQ is "The Operator" during any SSO's. Individual pilots should not contact NTSB. CAP/SE contacts NTSB.

</aside>