AutoReject Rules

AutoReject rules are automatic evaluations that run after PIREP scoring to flag, reject, or invalidate PIREPs that don't meet quality or safety criteria. Unlike scoring rules which award or deduct points within a scoring group, autoreject rules are airline-wide — they apply to every PIREP regardless of fleet or scoring group. They save staff time by catching problematic PIREPs automatically.

Accessing AutoReject Rules

In Orwell, go to HQ → Rewards → AutoReject Rules. You need the Can See Score Settings permission.

How AutoReject Rules Work

1. A pilot files a PIREP via Pegasus

2. The PIREP is scored by the fleet's scoring group rules (points calculated)

3. AutoReject rules evaluate the scored PIREP

4. If any rule triggers, the PIREP status changes and an action record is created

5. When multiple rules trigger, the harshest outcome applies

Rule Outcomes

Each autoreject rule is configured with one of three possible outcomes:

Outcome	Effect	Points	Hours	Staff Review
Failed	Sent for staff review	Pending	Pending	Required
Rejected	Automatically rejected	None	Credited	Not required
Invalidated	Automatically invalidated	None	None	Not required

Reply Needed — an optional flag available on Failed rules. When enabled, the pilot must leave a reply on the PIREP before they can book new flights. The PIREP is only sent for staff review after the pilot has replied.

Silent rules — rules can be marked as silent so they do not appear in the PIREP scorer or comments visible to the pilot. The rule still triggers and changes the PIREP status, but the pilot does not see which specific rule was responsible.

Adding an AutoReject Rule

To add a rule, click the create button and select a rule from the available list (grouped by category). Only rules not already enabled for your airline appear in the list. Once added, a rule cannot be changed to a different type — delete and re-add instead.

Each rule is configured with:

• Name — how the rule appears in the PIREP scorer when triggered

• Action — Failed, Rejected, or Invalidated. Some rules have a fixed action that cannot be changed.

• Reply Needed — only available when action is Failed

• Rule-specific parameters — thresholds, tolerances, and other settings that vary by rule type

Fleet Overrides

Many threshold-based rules support per-fleet parameter overrides. This lets you set different thresholds for different aircraft types — for example, a stricter landing rate limit for turboprops than for widebodies.

Each override specifies:

• Fleet(s) — which fleet type codes this override applies to

• Name — optional custom rule name for this fleet (overrides the main rule name in the scorer)

• Parameter overrides — fleet-specific values for the rule's threshold parameters

Rules that support fleet overrides are noted in their descriptions below.

Aircraft AutoReject Rules

Livery Name

Tracks aircraft liveries used in flights. When a pilot flies with a livery not previously seen on the fleet, the PIREP is flagged for staff review so the livery can be approved or rejected. If the livery has been used before by any pilot on the same fleet, the rule does not trigger — regardless of the livery's current approval status.

• Action must be set to Failed with Reply Needed off

• Pair with Rejected Livery Rejector to handle liveries that have been explicitly rejected

Rejected Livery Rejector

Triggers if the pilot flies with a livery that has been explicitly rejected by staff. Action can be set to any outcome.

Flight Length AutoReject Rules

Excessive Flight Length (Average)

Triggers if total flight time exceeds a dynamically calculated threshold based on historical data. The baseline is the average actual flight time from your airline's accepted PIREPs on the same route and fleet, or the published route time — whichever is longer. Two cutoffs are calculated: baseline + Maximum Time grace, and baseline multiplied by Coefficient. The larger value is used as the threshold.

• Maximum Time — fixed grace period added to the baseline (HH:MM:SS)

• Coefficient — multiplier applied to the baseline (e.g. 1.2 = 20% longer than baseline)

Example: baseline 3,900 seconds + 600s grace = 4,500s; or 3,900s x 1.2 = 4,680s. The larger value (4,680s) is used as the threshold.

Excessive Flight Length (Scheduled)

Same logic as the average variant but uses the route's published scheduled flight time as the baseline instead of historical averages.

• Maximum Time — fixed grace period (HH:MM:SS)

• Coefficient — multiplier

Excessive Taxi In

Triggers if taxi-in time exceeds a calculated threshold. The baseline is determined by priority: the airport's configured taxi-in time, then the airline average from 20+ historical PIREPs at the same airport, then the Maximum Time parameter as a fallback. The threshold is the baseline multiplied by the Coefficient.

• Maximum Time — fallback duration if no airport data exists (HH:MM:SS)

• Coefficient — multiplier applied to the baseline

Excessive Taxi Out

Same logic as Excessive Taxi In but evaluates departure airport taxi-out time.

Time Acceleration Use

Triggers if time acceleration (sim rate) was detected at any point during the flight. No configurable parameters.

Fuel AutoReject Rules

Fuel Increase in Air

Triggers if a fuel increase is detected while the aircraft is airborne — an impossible scenario in real aviation that indicates data tampering or a simulator issue. No configurable parameters.

Pushback Fuel Outside Planned Range

Triggers when pushback fuel deviates from the SimBrief planned ramp fuel beyond the configured tolerance.

• Over Tolerance (kg) — allowance above planned fuel

• Under Tolerance (kg) — allowance below planned fuel

• Fleet overrides supported

Landing Fuel Below Reserve

Triggers when the pilot lands with less fuel than the SimBrief final reserve fuel amount. No configurable parameters beyond name and action.

Takeoff Fuel Outside Planned Range

Triggers when takeoff fuel deviates from the SimBrief planned takeoff fuel beyond the configured tolerance. Same parameters as Pushback Fuel Outside Planned Range.

Takeoff AutoReject Rules

Liftoff Pitch Angle Is Excessive

Triggers when the pitch angle during rotation falls outside the configured range.

• Min Degrees / Max Degrees — acceptable pitch range

• Fleet overrides supported

Liftoff Roll Angle Is Excessive

Triggers when the roll angle during rotation exceeds the configured maximum. Uses the absolute value, so it applies to both left and right roll.

• Max Degrees — maximum acceptable roll magnitude

• Fleet overrides supported

Takeoff Above MTOW

Triggers when the takeoff weight exceeds the SimBrief Maximum Takeoff Weight plus the configured tolerance.

• Over Tolerance (kg) — allowance above MTOW

• Under Tolerance (kg) — allowance below MTOW

• Fleet overrides supported

Landing AutoReject Rules

Excessive Landing (FPM)

Triggers if the landing rate is harder (more negative) than the configured threshold. You can add multiple instances with different thresholds and actions — for example, -500 FPM to Reject and -1000 FPM to Invalidate. When multiple landing rate rules trigger on the same PIREP, only the most severe action applies.

• Heavier Than — FPM threshold (e.g. -500). A PIREP with exactly this value triggers the rule.

• Fleet overrides supported

Excessive Landing (G-Force)

Same concept as the FPM variant but uses G-force values. Triggers when G-force at landing meets or exceeds the threshold.

• Heavier Than — G-force threshold (e.g. 2.0). A PIREP with exactly this value triggers the rule.

• Fleet overrides supported

Soft Landing (FPM)

Triggers if the landing rate is softer (closer to 0) than the configured threshold.

• Lighter Than — FPM threshold (e.g. -100). A PIREP with exactly this value triggers the rule.

• Fleet overrides supported

Soft Landing (G-Force)

Triggers when G-force at landing is at or below the threshold. Pegasus v2 only.

• Lighter Than — G-force threshold (e.g. 1.0)

• Fleet overrides supported

Gear Up Landing

Triggers if any touchdown is detected with the landing gear up. No configurable parameters.

Multiple Landings

Triggers if more than one touchdown is detected — for example, a bounced landing or go-around. Action should be set to Failed with Reply Needed on, as the pilot may have a valid explanation.

Landing Above MLW

Triggers when landing weight exceeds the SimBrief Maximum Landing Weight plus the configured tolerance.

• Over Tolerance (kg) / Under Tolerance (kg)

• Fleet overrides supported

Landing Away From Destination

Triggers when the pilot lands at an airport other than the scheduled destination (diversion detected). This rule integrates with the vAMSYS diversion system. Action should be set to Failed with Reply Needed on.

Touchdown Pitch Angle Is Excessive

Triggers when the pitch angle at touchdown falls outside the configured range.

• Min Degrees / Max Degrees — acceptable pitch range

• Fleet overrides supported

Touchdown Roll Angle Is Excessive

Triggers when the roll angle at touchdown exceeds the configured maximum. Uses the absolute value, so it applies to both left and right roll.

• Max Degrees — maximum acceptable roll magnitude

• Fleet overrides supported

Points AutoReject Rules

Negative Points

Triggers when the PIREP's final score (after all scoring rules have been evaluated) is negative. No configurable parameters.

General AutoReject Rules

Force Review

Unconditionally flags every PIREP for staff review. No configurable parameters — useful for airlines that want to manually review all PIREPs.

Force Empty Route Review

Flags PIREPs where the route has no VA-provided waypoints. Silent rule option available.

Force Charter Flight Review

Flags all charter flight PIREPs for review. Silent rule option available.

Force Training Flight Review

Flags all training flight PIREPs for review. Silent rule option available.

Force Repositioning Flight Review

Flags all repositioning flight PIREPs for review. Silent rule option available.

ACARS Comment Rejector

Flags PIREPs that were filed with a comment in Pegasus. Useful for catching PIREPs where the pilot noted an issue during the flight.

Random Chance Review

Flags PIREPs for review based on a random percentage chance. Useful for spot-checking SOP compliance across your airline.

• Chance — percentage (1–100%)

Paused During Flight (Absolute)

Triggers if the simulator was paused for more than a set number of seconds during the flight.

• More Than (seconds) — pause time threshold in seconds

Paused During Flight (Percentage)

Triggers if pause time exceeds a percentage of total airborne time. For example, on a 2-hour flight with 1% configured, the rule triggers if the pilot paused for more than 72 seconds.

• More Than Percent — percentage of airborne time (1–100%)

Paused During Flight (Distance-Based)

Triggers if pause time exceeds a threshold that varies by flight distance. Longer flights get more pause tolerance. You configure multiple distance/time thresholds and the system selects the appropriate one based on the flight's distance.

• Distance Thresholds — repeater with the following fields per threshold:

• Min Distance (nm) — minimum flight distance for this threshold to apply

• Allowed Seconds — maximum pause time allowed at this distance

Example: 0–999nm = 60 seconds allowed, 1000–1999nm = 120 seconds, 2000nm+ = 180 seconds.

Taxi AutoReject Rules

Taxi Overspeed

Triggers when taxi overspeed is detected for longer than the configured duration.

• Evaluation Type — "Single Event" (any single overspeed event exceeding the threshold) or "All Events" (total overspeed time across all taxi events)

• Threshold Seconds — duration before triggering (1–600 seconds)

Permissions

Permission	Grants
Can See Score Settings	Access to AutoReject Rules (shared with Scoring Groups and Scoring Rules)

Related

• Scoring Groups — group scoring rules by fleet

• Scoring Rules — configure point-based PIREP scoring

• PIREPs — review PIREPs affected by autoreject rules

• Fleet — fleet types referenced by fleet overrides

• Liveries — manage aircraft liveries (related to Aircraft autoreject rules)