> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the ASAP Program

> Submit, review, and resolve Aviation Safety Action Program reports through the Event Review Committee workflow, including MOU compliance and corrective action tracking.

By following this guide, you will submit ASAP reports, manage the Event Review Committee (ERC) review workflow, track corrective actions through resolution, and maintain compliance with your Memorandum of Understanding (MOU).

<Info>
  ASAP is a voluntary reporting program authorized under FAA Advisory Circular 120-66C. It requires
  a signed MOU between the certificate holder, the FAA, and (optionally) the employee group. Contact
  your safety manager to verify your organization's ASAP MOU status before submitting reports.
</Info>

## Submit an ASAP Report

<Steps>
  ### Step 1: Open the ASAP submission form

  Navigate to **Safety > ASAP** in the sidebar and click **New ASAP Report**. The submission form opens with fields specific to the ASAP program requirements.

  ### Step 2: Enter event details

  Complete the required fields:

  * **Event date and time** -- when the event occurred (must be within the MOU reporting window, typically 24 hours).
  * **Event type** -- select the category that best describes the event (e.g., altitude deviation, runway incursion, airspace violation, procedural non-compliance).
  * **Narrative description** -- provide a factual account of what happened, including contributing factors and the operational context.
  * **Suggested corrective action** -- describe what you believe would prevent recurrence.

  ### Step 3: Attach supporting evidence

  Upload any relevant documentation: ATC communications, flight data excerpts, photographs, or other evidence that provides context for the ERC review.

  ### Step 4: Submit the report

  Click **Submit**. The report enters `submitted` status and is assigned a tracking code. You receive a confirmation with the tracking code for follow-up.

  <Tip>
    ASAP reports must be submitted within the timeframe specified in your MOU (typically 24 hours of
    the event). Late submissions may not qualify for ASAP protections. The submission timestamp is
    recorded automatically.
  </Tip>
</Steps>

## Review Reports as an ERC Member

The Event Review Committee (ERC) reviews each ASAP report to determine acceptance, corrective actions, and whether the event qualifies for ASAP protections under the MOU.

<Steps>
  ### Step 1: Access the ERC review queue

  Navigate to **Safety > ASAP**. Reports awaiting ERC review appear in the **Pending Review** tab, sorted by submission date.

  ### Step 2: Review the event details

  Open a report to review the narrative, contributing factors, attached evidence, and the reporter's suggested corrective action. The detail view shows the event timeline and any related safety reports or investigations.

  ### Step 3: Determine ASAP acceptance

  Assess whether the event meets your MOU acceptance criteria. Common criteria include: the report was timely, the event was inadvertent, and the reporter is not involved in criminal activity or substance abuse. Record the ERC determination:

  * **Accepted** -- the event qualifies for ASAP. Proceed to corrective action.
  * **Referred to management** -- the event does not meet MOU criteria and is referred outside the ASAP program.

  ### Step 4: Assign corrective actions

  For accepted reports, create corrective actions directly from the report detail page. Each corrective action links to the CPA lifecycle for tracking and verification. Assign an owner, set a due date, and describe the expected outcome.

  ### Step 5: Close the review

  Once corrective actions are assigned (or the report is referred), close the ERC review. The report moves to `resolved` status and the reporter is notified of the outcome.
</Steps>

## Track ASAP Metrics

The ASAP index page displays program-level metrics:

| Metric                  | Description                                               |
| ----------------------- | --------------------------------------------------------- |
| Reports submitted       | Total ASAP reports submitted in the selected time period. |
| Acceptance rate         | Percentage of reports accepted by the ERC.                |
| Average time to resolve | Mean days from submission to ERC closure.                 |
| Open corrective actions | Number of ASAP-linked CPAs not yet verified as effective. |

Use these metrics to demonstrate program health during FAA surveillance and MOU renewal discussions.

<Warning>
  **AI suggestions are advisory only.** Per 14 CFR Part 5, all safety assessments, investigation
  findings, and risk evaluations require independent human evaluation by qualified personnel. AI
  recommendations should be used as one factor among many in decision-making, not as the sole basis
  for any safety, operational, or maintenance action. See [Legal
  Notices](/en/reference/legal-notices#ai-and-automated-features-disclaimer).
</Warning>

## Related

<CardGroup cols={2}>
  <Card title="ASAP Program Reference" href="/reference/asap-program">
    ASAP statuses, MOU requirements, ERC composition, and regulatory basis.
  </Card>

  <Card title="Manage ASAP" href="/how-to/sms/manage-asap">
    Quick-start guide for ASAP report submission and review.
  </Card>

  <Card title="Create a CPA" href="/how-to/sms/create-cpa">
    Create corrective and preventive actions from ASAP findings.
  </Card>

  <Card title="Just Culture Framework" href="/reference/just-culture-framework">
    How accountability decisions are made for reported events.
  </Card>
</CardGroup>