Learn how virtual airline PIREPs work, what details to record, how to submit one by ACARS or manually, and how to avoid common rejections.
In flight simulators generally, a virtual airline PIREP is the post-flight record used to credit a pilot’s flight, hours and operating statistics. File it through the airline’s ACARS tracker or manual web form, using the booked flight number, aircraft, route, block times and fuel figures, then submit it for validation.
PIREP means pilot report. In real aviation, that term commonly describes an airborne weather report; within a virtual airline, it means the operational record of a completed simulated flight. A booking selects the flight, a flight plan describes what you intend to fly, and the PIREP records what actually happened.
The accepted report may update your hours, rank, route history and the airline’s statistics. Our overview of flight assignments and hour tracking in virtual airlines explains where PIREPs fit into the wider operation.
What information goes in a virtual airline PIREP?
A virtual airline PIREP normally identifies the pilot, scheduled flight and aircraft, then records the actual times, route, fuel use and result.
- Flight identity: pilot ID, flight number or callsign, date and any booking reference.
- Route: departure and destination ICAO codes, route flown, cruise altitude and diversion airport where applicable.
- Aircraft: type, variant and sometimes the assigned registration.
- Times: OUT, OFF, ON and IN times, or at least the resulting block time.
- Fuel: departure fuel, arrival fuel or fuel used, with the correct unit.
- Flight data: landing rate, simulator, online network and event log when captured by a tracker.
- Remarks: ATC reroutes, go-arounds, diversions, technical interruptions or another event that explains unusual data.
Block time usually runs from leaving the departure stand to reaching the arrival stand; airborne time runs only from take-off to landing. Airlines and trackers define the OUT and IN triggers differently, sometimes using movement, parking-brake or engine states, so follow your airline’s definition rather than substituting take-off and touchdown times.
How do I file a virtual airline PIREP?
Book the correct flight, record it from the departure stand through arrival, verify the resulting data and submit the report once.
- Read the reporting rules. Check whether the airline requires its tracker, allows manual PIREPs and restricts simulator rate, pausing, slewing, refuelling or aircraft substitutions.
- Book or bid on the flight. Match the flight number, departure, destination and approved aircraft. A technically perfect report can still be rejected if it does not match the assigned sector.
- Start the record before moving. With ACARS-style software, connect it to the simulator, select the booked flight and start tracking at the stand. For a manual report, note the actual OUT time and starting fuel.
- Keep the flight record running. Do not close the tracker after take-off or start a second session if it briefly loses its simulator connection. Reconnect through the same session where possible and note any interruption.
- Complete the arrival properly. Taxi to the correct airport stand, set the parking brake and perform any shutdown actions the tracker requires. Wait for it to register IN before ending the session. Manual reporters should record the arrival time and remaining fuel.
- Review and submit once. Confirm the airport codes, aircraft, date, time zone, block time and fuel units. Add a concise factual remark for a diversion, reroute or tracker fault, then submit and check that the report appears in your pilot log.
Some systems submit automatically when the flight ends; others produce a draft for you to review. If the page appears to hang, check your pilot log before pressing Submit again—a delayed response is a common cause of duplicate PIREPs.
Should I use ACARS or file the PIREP manually?
Use the airline’s ACARS tracker when it is required or supported; use a manual report only when the airline permits it and you can supply accurate flight data.
| Method | Choose it when | Main limitation |
|---|---|---|
| ACARS-style tracker | The airline mandates tracking or you want automatic times, fuel, landing and event data | It must support your simulator and remain connected throughout the flight |
| Manual PIREP | The airline allows manual filing, your platform lacks a compatible tracker or an approved technical failure occurred | You must record the data yourself, and some airlines require supporting details |
Virtual airlines use the term ACARS for simulator-connected tracking software inspired by airline communications systems. It reads simulator data, builds the event log and transmits the report; our explanation of how ACARS software automates PIREP collection covers that basic model.
Manual filing is not a way to bypass tracker rules. If a tracker fails, retain its log where possible and use the airline’s correction or support process instead of inventing missing figures.
Why was my virtual airline PIREP rejected?
Most rejected PIREPs contain a schedule mismatch, incomplete tracker record, incorrect time or fuel entry, prohibited simulator event, or arrival that does not match the booked flight.
- Wrong assignment: the flight number, airport pair, aircraft or registration differs from the booking.
- Tracker started or stopped late: the report lacks the departure phase, landing or completed arrival at the stand.
- UTC and local time were mixed: the report shows a negative or implausible duration, especially across midnight.
- Fuel units were confused: kilograms were entered as pounds, or remaining fuel was placed in the fuel-used field.
- Disallowed events were logged: excessive simulator rate, slewing, teleporting, mid-flight refuelling, a crash or a landing beyond the airline’s limit.
- No explanation was supplied: the flight ended at an alternate, followed an amended route or contains a telemetry gap without a remark.
An ATC reroute, go-around, diversion or network disconnection does not automatically make a flight invalid. Report what happened honestly and let the airline apply its policy. If a report is rejected for editable data, correct the original where permitted rather than filing an unchanged duplicate.
What happens after a PIREP is submitted?
A submitted PIREP is normally marked pending, accepted or rejected after automatic checks, staff review or both.
An accepted report credits the eligible flight time and may affect rank, awards, finances, schedules or aircraft statistics. A pending report has not yet completed validation, while a rejected one normally credits nothing until corrected or successfully reviewed. For the effect on progression, see our explanation of how accepted flights build a virtual airline career.