​
Standard ACARS Submission

The primary method for submitting flight reports is through Pegasus ACARS, which automatically captures your flight details and submits them to our system.

1

Complete your flight

Finish your flight by:

  • Landing at your destination airport
  • Taxiing to your assigned gate
  • Shutting down engines
  • Setting parking brakes
2

End flight in ACARS

  1. Click “End Flight” in Pegasus ACARS
  2. Wait for the system to process your flight data
  3. Review the flight summary displayed
  4. Add any additional comments about your flight (optional)
3

Submit PIREP

  1. Click “Submit Flight Report” to finalize
  2. Confirm submission when prompted
  3. Wait for the “Submission Successful” message
4

Verify submission

  1. Your flight should appear in your logbook within a few minutes
  2. The status will initially show as “Pending” while the system processes it
  3. Once processed, it will update to “Accepted” or note any issues

ACARS automatically captures essential flight data including route, aircraft, fuel consumption, landing rate, and flight duration. This is the preferred method for submitting PIREPs.

​
Manual PIREP Submission

If you encounter issues with ACARS or if your flight data wasn’t properly recorded, you can submit a manual PIREP through the Pilot Portal.

1

Access the Manual PIREP form

  1. Log in to the Pilot Portal
  2. Navigate to “Flight Center”
  3. Select “Manual PIREP / File a Claim”
2

Complete the form

Fill in all required fields:

  • Departure Airport: Select your departure airport (e.g., “Toronto Pearson International Airport”)
  • Arrival Airport: Select your destination airport (e.g., “Orlando International Airport”)
  • Departure Time: Enter the UTC/Zulu time of your departure in format dd.mm.yyyy, —:— (be as accurate as possible)
  • Message: Explain why you’re submitting a manual PIREP and provide any relevant details about the flight
3

Provide proof

Upload evidence of your completed flight:

  1. Click “Add to proof”
  2. Select files that demonstrate your flight completion (screenshots showing:)
    • Aircraft at departure gate
    • Cruising at assigned altitude
    • Aircraft at arrival gate
    • Flight plan or route
    • Simulator flight log (if available)

Manual PIREPs without sufficient proof may be rejected. Providing multiple pieces of evidence increases the likelihood of approval.

4

Submit and wait for review

  1. Review all information for accuracy
  2. Click “Submit” to send your manual PIREP
  3. The staff team will review your submission (typically within 24-48 hours)
  4. You’ll receive a notification when your PIREP is approved or rejected

​
When to Submit a Manual PIREP

Manual PIREPs should only be submitted in specific circumstances:

  • ACARS crashed or malfunctioned during your flight
  • Simulator crashed near the end of an otherwise completed flight
  • Technical issues prevented normal PIREP submission
  • You flew on a network (VATSIM/IVAO) but ACARS wasn’t tracking the flight

ACARS Troubleshooting

If you’re experiencing problems with ACARS, check the troubleshooting guide for solutions before submitting a manual PIREP.

​
PIREP Review Process

All PIREPs, whether submitted through ACARS or manually, go through a review process:

  1. Automated check - System verifies flight parameters against requirements
  2. Manual review (if needed) - Staff team reviews flagged flights
  3. Approval - Accepted flights are added to your flight log and hours/stats
  4. Rejection - If issues are found, the PIREP may be rejected with an explanation

Most ACARS-submitted PIREPs are processed automatically within minutes. Manual PIREPs always require staff review and take longer to process.

​
Tips for Successful PIREPs

  • Ensure ACARS is properly connected to your simulator before starting a flight
  • Don’t exit your simulator until ACARS has confirmed your PIREP was submitted
  • For manual PIREPs, provide as much detail and evidence as possible
  • If you’re uncertain about a flight’s status, check your logbook before submitting a duplicate PIREP
  • When flying on online networks, take additional screenshots as evidence