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

# PIREP Statuses

> Understand each vACA PIREP status from Processing to Accepted or Rejected, plus common failure rules and review triggers.

## PIREP Processing Overview

All <Tooltip tip="Pilot Report" cta="See glossary" href="/aops/additional-resources/glossary/pirep">PIREPs</Tooltip> submitted are processed automatically. A PIREP may take up to ten (10) minutes to be processed, during the course of which, your PIREP will go through several states.

<Note>
  PIREPs with the status of 'Reply Needed' require prompt attention by you. You will not be able to start any new flights until after you respond to these PIREPs.
</Note>

Leaving a PIREP Comment, whether via Pegasus or vAMSYS, will automatically result in your PIREP being sent for staff review.

PIREPs in the Processing or Scoring state need no action from you - you can book your next flight and start flying without waiting for processing or scoring to complete.

<Tip>
  Some PIREPs are randomly selected for a manual spot review, even when no issues are detected. This is perfectly normal and part of our routine quality checks. The team usually approves these within 45 minutes.
</Tip>

## PIREP Status Definitions

| PIREP Status    | Description                                                                                        | Your Action Needed                       |
| --------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| Accepted        | PIREP has been Reviewed and Accepted by the Team. Hours and Points are awarded.                    | None. Book another Flight and Fly.       |
| Complete        | PIREP completed automated processing and no red flags were detected. Hours and Points are awarded. | None. Book another Flight and Fly.       |
| Rejected        | Team has reviewed the PIREP and it was Rejected. Hours are awarded, but points are not.            | None. Book another Flight and Fly.       |
| Invalidated     | Team has reviewed the PIREP and it was Invalidated. No Hours and no points are awarded.            | None. Book another Flight and Fly.       |
| Awaiting Review | PIREP has satisfied one of the Failure Conditions and is now awaiting review by the Team.          | None. Book another Flight and Fly.       |
| Reply Needed    | PIREP needs your urgent input before it can be reviewed by the Team                                | Look into the PIREP As Soon As Possible. |
| Processing      | PIREP is undergoing Processing phase.                                                              | None. Book another Flight and Fly.       |
| Scoring         | PIREP is undergoing Scoring phase.                                                                 | None. Book another Flight and Fly.       |

## Common Reasons for Review

PIREPs may be flagged for review for various reasons, including:

* Landing fuel outside recommended ranges
* Improper engine cool-down procedures
* Excessive flight speed or G-forces
* Unstable approaches
* Simulator pausing or time acceleration
* Disconnections from the tracking system

## Failure Rules

The following table outlines specific conditions that will trigger a PIREP review or automatic action:

| Rule Name                                 | Condition                                                          | PIREP Action          | Your Intervention |
| ----------------------------------------- | ------------------------------------------------------------------ | --------------------- | ----------------- |
| Mid-air Refueling                         | Fuel Increase Detected Mid-Flight                                  | Sent for Staff Review | Required          |
| Longer than anticipated Flight Length     | Flight took longer than average time by more than 24:00:00 or 100% | Sent for Staff Review | Required          |
| Diversion Detected                        | Landed not at the Destination Airport                              | Sent for Staff Review |                   |
| Negative Points                           | Awarded Points is less than 0                                      | Sent for Staff Review |                   |
| Rejected due to Excessive Landing Rate    | Landing Rate More Than -900 FPM                                    | Sent for Staff Review | Required          |
| Time Acceleration                         | Time Acceleration was Detected                                     | Sent for Staff Review |                   |
| Excessive Taxi Out Time                   | Taxi Out Time longer than Anticipated                              | Sent for Staff Review |                   |
| Gear Up Landing                           | Landed with Gear in Up position                                    | Rejected              |                   |
| New Livery/Airframe                       | New Livery Detected                                                | Sent for Staff Review |                   |
| Rejected Livery/Airframe                  | Flown Livery is Rejected                                           | Sent for Staff Review |                   |
| Invalidated due to Excessive Landing Rate | Landing Rate More Than -600 FPM                                    | Sent for Staff Review |                   |
| Multiple Landings or Bounce Detected      | Multiple Landings or Bounces Detected                              | Sent for Staff Review |                   |

## Flight Scoring System

<Card title="Learn About Flight Scoring" icon="chart-line" href="https://vamsys.io/phoenix/documents/scores" arrow={true} cta="Learn More">
  Understand how flights are tracked and scored in our ACARS system. Learn about performance metrics, validation requirements, and how to maximize your pilot score.
</Card>

## Need Help?

If you have questions about your PIREP status or the review process, our operations team is available to assist.

<CardGroup cols={2}>
  <Card title="Discord Community" icon="discord" href="https://links.canadava.com/kgNgqfb" cta="Join Discord" arrow={true}>
    Get answers to your questions in our active Discord community
  </Card>

  <Card title="Email Support" icon="envelope" href="mailto:support@canadava.com" cta="Contact Us" arrow={true}>
    Contact our support team for personalized assistance
  </Card>
</CardGroup>
