PIREP Logging and Operational Standards

I. General Logging Requirements

All pilots are required to comply with the following standards when submitting a PIREP:

• All PIREPs must be logged using the approved ACARS client, phpVMS ACARS.
• The flight route submitted through the Crew Centre must be accurately reflected in the ACARS log. Direct airport-to-airport routing without waypoints or standard SIDs/STARs is prohibited.
• Flights must be operated on a valid WJA Virtual scheduled route using a WJA-approved aircraft type.
• Flight time may not be logged for credit with any other virtual airline or organization simultaneously.

---

II. Operational Limits

Operational limits are enforced automatically by the ACARS system to reflect realistic airline operations.

The maximum permitted landing rate is -900 feet per minute (fpm), and this limit applies to both the initial touchdown and any subsequent touches.

Any stall event may result in PIREP rejection. Pilots are expected to avoid stalls, overspeeds, and excessive bank or pitch angles at all times. The use of Active Pause in MSFS 2020/2024 is prohibited, as it is known to incorrectly trigger stall events.

Pilots must not exceed 250 knots indicated airspeed (KIAS) below 10,000 feet MSL. Violations of this procedure may result in PIREP rejection depending on the duration and severity of the exceedance.

---

III. Flight Time and Simulation Integrity

Time acceleration is strictly prohibited.

Flight Manipulation

The use of any feature that skips or alters normal flight progression is strictly prohibited, including but not limited to:

• Jump to next waypoint
• Jump to descent
• Use of simulator Slew Mode

---

IV. Fuel Management

Prohibited Fuel Settings

The following are strictly forbidden:

• Unlimited Fuel in any simulator
• In-flight refueling

Minimum Landing Fuel

All flights must land with a minimum of 4,500 lbs of fuel remaining.

Fuel Reserve Expectations

During all airline transport operations, pilots are required to maintain adequate fuel reserves for:

• Emergency procedures
• Holding
• Unforeseen operational delays

---

V. Flight Discrepancies and Manual Submission Requirements

Diversions

In the event of a required diversion due to weather, emergency, or ATC instruction, the pilot must clearly note the diversion airport and the reason in the Comments section of the ACARS client before submission.

Technical Glitches

If the primary ACARS system fails, a pilot may submit a manual PIREP. This manual submission must include verifiable flight tracking proof, such as a flight log and/or screenshot, from approved third-party trackers such as Volanta or Elevatex.

Submission Standards

• Block time and route must match the booked flight.
• The PIREP must be submitted within the time limit set in the Crew Centre, such as 24 to 48 hours.

---

VI. Administrative Discretion

WJA Virtual Administration reserves the right to review, approve, or reject any PIREP at its discretion in order to maintain operational integrity, even where all automated criteria have been met. A clear reason for any rejection will be provided in the PIREP comments.