Scoring Rules

Complete reference for all available scoring rules — from landing rates and engine sequences to fuel management and network connectivity.

Staff
Last verified: February 19, 2026

Scoring rules are the individual evaluations applied to PIREPs within a scoring group. Each rule awards or deducts points based on specific aspects of pilot performance during a flight. Rules are added and configured within a Scoring Group, and you can customise names, points, and rule-specific parameters for each one.

Every scoring rule shares three common fields:

  • Name — how the rule appears in the PIREP scorer (staff view)

  • UI Name — how the rule appears on the Phoenix Scores page (pilot view). If empty, defaults to Name.

  • Points — how many points to award (positive) or deduct (negative). Some rules use thresholds instead of a single points value.

General Scoring Rules

Starting Points

Base points awarded to every PIREP. This is the simplest rule — every filed PIREP gets this score regardless of performance.

  • Points — integer value awarded

Step Climb/Descent

Points awarded if a step climb or step descent is detected during the flight. This triggers once per PIREP regardless of how many step changes occurred.

  • Points — integer value awarded

Multiple Flights Per Day

Bonus points for filing multiple PIREPs in a single day (using the VA's configured timezone). Only the highest matching threshold is awarded — thresholds do not stack. PIREPs across all fleets count towards the daily total, not just the fleet using this scoring group. Claims also count.

  • Thresholds — repeater with the following fields per threshold:

  • Apply from PIREP # — which flight number triggers this threshold (inclusive, e.g. 2 = second flight onwards)

  • Name — threshold name shown in the scorer

  • Points — points to award for this threshold

  • Apply as Bonus Points — toggle; if enabled, points are added as bonus points instead of regular points

Rank Points

Awards points based on the pilot's current rank at the time the PIREP is processed.

  • Ranks — repeater with the following fields per entry:

  • Rank(s) — one or more ranks to match

  • Points — points to award for pilots holding those ranks

  • Apply as Bonus Points — toggle; if enabled, points are added as bonus points instead of regular points

Engine Scoring Rules — Sequence

Engine sequence rules check that engines were started in the correct order. Pick the most applicable sequence for the fleets using the scoring group. Only one engine sequence rule can be added per scoring group.

Each sequence rule shares these parameters:

  • Time between engine starts — minimum time that must elapse between each engine start (HH:MM:SS)

  • Points — base points awarded if the sequence is correct

  • Penalise Out of Sequence — toggle; if enabled, deducts points when engines are started in the wrong order

  • Name — how the penalty shows in the scorer

  • Points — penalty points (negative)

  • Penalise Insufficient Time — toggle; if enabled, deducts points when the time between starts is too short

  • Name — how the penalty shows in the scorer

  • Points — penalty points (negative)

Available engine start sequences:

Rule

Engine Start Order

Any Engine Started

Any engine (base rule)

Number 1 First of 2

1 → 2

Number 2 First of 2

2 → 1

Number 1 First, Then 2

1 → 2

Number 1, Then 2, Then 3

1 → 2 → 3

Number 1, Then 2, Then 3, Then 4

1 → 2 → 3 → 4

Number 1, Then 2, Then 4, Then 3

1 → 2 → 4 → 3

Number 1, Then 3, Then 2

1 → 3 → 2

Number 2 First, Then 3 Dual

2 → 3 (dual spool)

Number 2, Then 3, Then 1, Then 4

2 → 3 → 1 → 4

Number 3 First of 3

3 → (others)

Number 3, Then 1, Then 2

3 → 1 → 2

Number 3, Then 2, Then 1

3 → 2 → 1

Number 3 First, Then 4

3 → 4

Number 3, Then 4, Then 2, Then 1

3 → 4 → 2 → 1

Number 4, Then 2, Then 1, Then 3

4 → 2 → 1 → 3

Number 4 First, Then 3

4 → 3

Number 4 First, Then 3 Dual

4 → 3 (dual spool)

Number 4, Then 3, Then 2, Then 1

4 → 3 → 2 → 1

Engine Scoring Rules — General

Engines Shut Before Filing

Points awarded if all engines are turned off before the PIREP is filed.

  • Points — integer value awarded

Selected Engine Taxi In

Points awarded if selected engines remained running after landing for a minimum duration before the other engines are shut down. This rewards pilots who taxi in on reduced engines to save fuel.

  • Engines — comma-separated engine numbers (e.g. "1,2")

  • Time — minimum run time after landing (HH:MM:SS)

  • Points — integer value awarded

Selected Engine Taxi Out

Points awarded if selected engines remain off during taxi out, with a minimum time between turning on other engines and turning on the selected engines. This rewards single-engine taxi out procedures.

  • Engines — comma-separated engine numbers

  • Time — minimum time between starts (HH:MM:SS)

  • Points — integer value awarded

Engines Cooled Down

Points awarded if engines remain running for the minimum time after landing. This evaluates whether the pilot allowed sufficient engine cool-down time before shutdown.

  • Minimum Time — required cool-down duration (HH:MM:SS)

  • Points — integer value awarded

Engines Not Cooled Down

Points deducted if engines are not running for the minimum time after landing.

  • Minimum Time — required duration (HH:MM:SS)

  • Taxi Time Aware — toggle; when enabled, ignores the rule if taxi time is less than the minimum time (avoids penalising pilots who parked at a gate near the runway)

  • Points — integer value (typically negative)

Engines Warmed Up

Points awarded if engines are properly warmed up before takeoff — that is, they have been running for at least the minimum time before the aircraft departs.

  • Minimum Time — required warm-up duration (HH:MM:SS)

  • Conditional Warmup — toggle. When enabled, warmup is only required after a long turnaround. If the aircraft has been on the ground for less than the threshold hours, it is assumed the engines are still warm and the points are awarded automatically.

  • Turnaround Threshold Hours — hours on ground before warmup is required (default: 2.0)

  • Taxi Time Aware — toggle; ignores the rule if taxi time is less than the minimum time

  • Points — integer value awarded

Engines Not Warmed Up

Points deducted if engines are not properly warmed up before takeoff. Has the same parameters as Engines Warmed Up.

  • With Conditional Warmup enabled: short turnarounds (below threshold) receive no penalty, while long turnarounds (at or above threshold) are penalised if warmup time is insufficient.

Flap Scoring Rules

Flaps Retracted Before Parking

Points awarded if flaps are set to 0 after landing.

  • Timer Start — when the evaluation begins: "Last Touchdown" or "30kts"

  • Points — integer value awarded

Flaps Not Retracted Before Parking

Points deducted if flaps are NOT set to 0 after landing. Same parameters as the award variant.

Flaps Set Before Takeoff

Points awarded if flaps are set within the specified range before takeoff.

  • Flap Evaluation Type — "Level" uses simulator-specific numeric positions. "Human" uses consistent flap names like "2", "FULL", "UP", "1+F" that work across simulators.

  • Minimum Flap / Maximum Flap — range bounds (format depends on evaluation type)

  • Points — integer value awarded

Flaps Not Set Before Takeoff

Points deducted if flaps are NOT within the configured range before takeoff. Same parameters as the award variant.

Flaps Set Before Landing

Points awarded if flaps are within the specified range before landing. Same parameters as the takeoff variant.

Flaps Not Set Before Landing

Points deducted if flaps are NOT within range before landing. Same parameters as the takeoff variant.

Flight Length Scoring Rules

Flight Length

Threshold-based scoring on airborne time. Use this to reward or penalise flights of certain durations — for example, awarding more points for longer flights.

  • Thresholds — repeater with the following fields per threshold:

  • Name — threshold label

  • From (inclusive) — minimum airborne time (HH:MM:SS)

  • To (exclusive) — maximum airborne time (HH:MM:SS)

  • Points — points to award

Prep Time

Points awarded if the time between tracking start and pushback falls within a specified range. This rewards pilots who take appropriate time to prepare before departure.

  • From — minimum prep time (HH:MM:SS)

  • To — maximum prep time (HH:MM:SS)

  • Points — integer value awarded

Block Length

Threshold-based scoring on block time (off blocks to on blocks). Uses the same threshold format as Flight Length.

Takeoff Scoring Rules

Pegasus v2 Only

These rules require Pegasus ACARS version 2.

Liftoff Pitch Within Range

Points awarded if the maximum pitch angle at liftoff is within the configured range.

  • Min Degrees / Max Degrees — acceptable pitch range

  • Points — integer value awarded

Liftoff Pitch Outside Range

Points deducted if the maximum pitch angle at liftoff falls outside the configured range. Same parameters as the award variant.

Liftoff Roll Within Range

Points awarded if the roll angle at liftoff is within the acceptable range.

  • Max Degrees — maximum acceptable roll magnitude

  • Points — integer value awarded

Liftoff Roll Outside Range

Points deducted if the roll angle at liftoff exceeds the maximum. Same parameters as the award variant.

Takeoff Weight Within MTOW

Points awarded if the takeoff weight is within the Maximum Takeoff Weight tolerance. The MTOW used is from SimBrief (planned weight), not the aircraft's structural limit.

  • Weight Source — SimBrief (planned) or Structural

  • Bound Check — Both (over and under), Upper Only, or Lower Only

  • Over Tolerance (kg) — allowance above MTOW

  • Under Tolerance (kg) — allowance below MTOW

  • Points — integer value awarded

Takeoff Weight Outside MTOW

Points deducted if the takeoff weight falls outside the MTOW tolerance. Same parameters as the award variant.

Landing Scoring Rules

Graduated Landing (FPM)

Threshold-based scoring on landing rate in feet per minute. Most Virtual Airlines use this as their primary landing scorer. You can define multiple thresholds for different landing qualities (e.g. "Butter", "Good", "Acceptable", "Hard") and optionally enable graduated adjustment to scale points within each range.

  • Thresholds — repeater with the following fields per threshold:

  • Name — threshold label (e.g. "Butter", "Good", "Hard")

  • Heaviest (FPM From) — harder landing limit (more negative value)

  • Lightest (FPM To) — softer landing limit (closer to 0)

  • Points — base points for this range

  • Graduated Adjustment — toggle; when enabled, points are adjusted within the range

  • Direction — "Lighter" (reward softer landings) or "Heavier" (penalise harder landings)

  • Adjust Points — points per FPM difference

FPM values of -9999 or 9999 are treated as infinite bounds.

Graduated Landing (G-Force)

Same concept as the FPM variant but uses G-force values instead (range 0 to 9.99). A G-force of 9.99 is treated as infinite. Uses the same threshold structure with graduated adjustment support.

Diversion Point Reducer

On diverted PIREPs, reduces total points based on the ratio of distance flown to the scheduled distance. For example, if the pilot diverted halfway through the flight, roughly 50% of earned points are kept.

  • Points — the percentage-based reduction to apply

Touchdown Pitch Within Range

Points awarded if the pitch angle at touchdown is within the configured range.

  • Min Degrees / Max Degrees — acceptable pitch range

  • Points — integer value awarded

Touchdown Pitch Outside Range

Points deducted if the pitch angle at touchdown falls outside the range. Same parameters as the award variant.

Touchdown Roll Within Range

Points awarded if the roll angle at touchdown is within the acceptable range.

  • Max Degrees — maximum acceptable roll magnitude

  • Points — integer value awarded

Touchdown Roll Outside Range

Points deducted if the roll angle at touchdown exceeds the maximum. Same parameters as the award variant.

Landing Weight Within MLW

Points awarded if the landing weight is within the Maximum Landing Weight tolerance. Uses SimBrief MLW by default.

  • Weight Source — SimBrief (planned) or Structural

  • Bound Check — Both, Upper Only, or Lower Only

  • Over Tolerance (kg) — allowance above MLW

  • Under Tolerance (kg) — allowance below MLW

  • Points — integer value awarded

Landing Weight Outside MLW

Points deducted if the landing weight falls outside the MLW tolerance. Same parameters as the award variant.

Away From Destination

Triggers when a pilot lands at an airport other than the scheduled destination (diversion detected).

  • Points — integer value (typically negative)

Stabilized Approach (Altitude Gates)

Pegasus v2 Only — Beta Feature

This rule requires Pegasus ACARS version 2. It is currently a beta feature — we recommend setting points to 0/0 during initial testing.

Evaluates approach stability at configurable altitude gates above the touchdown point. This is one of the most complex scoring rules, allowing detailed evaluation of the pilot's approach at multiple altitudes.

  • Points Award — points if all gates are passed

  • Points Deduct — points if any gate is failed

  • Unstable Name — how failures appear in the scorer

  • Show Zero Scores — toggle; whether to show the rule when no points are awarded or deducted

Gates can be configured at the following altitudes above field elevation: 2000, 1500, 1000, 500, 200, 100, 50, 40, 30, 20, 10, and 0 feet. Each gate can evaluate:

  • Min/Max Vertical Speed (FPM)

  • Min/Max Airspeed (groundspeed)

  • Min/Max Flap Position

  • Max Bank Angle

  • Min/Max Pitch

  • Gear Down Required — from this gate onwards, landing gear must be down

  • No Flap Changes — from this gate onwards, flaps must not move

Gates are forward-looking — a 1000ft gate monitors values from 1000ft down to the next configured gate (or touchdown). Subsequent gates override the restrictions set by previous gates.

Fuel Scoring Rules

Landing with Too Much Fuel

Triggers when the pilot lands with more fuel than the configured threshold. An additional penalty can be applied per 1000kg of excess fuel.

  • More Fuel Than (kg) — fuel threshold

  • Fuel Penalty — additional points per 1000kg above threshold

  • Points — base points

Landing with Too Little Fuel

Triggers when the pilot lands with less fuel than the configured threshold.

  • Less Fuel Than (kg) — fuel threshold

  • Points — integer value

Pushback with More Fuel Than

Triggers when the fuel at pushback exceeds the configured threshold.

  • More Fuel Than (kg) — fuel threshold

  • Points — integer value

Pushback with Less Fuel Than

Triggers when the fuel at pushback is below the configured threshold.

  • Less Fuel Than (kg) — fuel threshold

  • Points — integer value

Pushback Fuel Within Planned Range

Points awarded if the fuel at pushback is within the tolerance range of the SimBrief planned ramp fuel.

  • Over Tolerance (kg) — allowance above planned fuel

  • Under Tolerance (kg) — allowance below planned fuel

  • Bound Check — Both, Upper Only, or Lower Only

  • Points — integer value awarded

Pushback Fuel Outside Planned Range

Points deducted if the fuel at pushback falls outside the tolerance range of the SimBrief planned ramp fuel. Same parameters as the award variant.

Landing Fuel Above Reserve

Points awarded if the pilot lands with more fuel than the SimBrief final reserve fuel amount.

  • Points — integer value awarded

Landing Fuel Below Reserve

Points deducted if the pilot lands with less fuel than the SimBrief final reserve fuel amount.

  • Points — integer value (typically negative)

Takeoff Fuel Within Planned Range

Pegasus v2 Only

This rule requires Pegasus ACARS version 2.

Points awarded if takeoff fuel is within the tolerance range of the SimBrief planned takeoff fuel. Same parameters as the pushback fuel planned range variant.

Takeoff Fuel Outside Planned Range

Points deducted if takeoff fuel falls outside the tolerance range. Requires Pegasus ACARS version 2. Same parameters as the pushback fuel planned range variant.

Network Connectivity Scoring Rules

Connected to Network

Points awarded for flying on VATSIM or IVAO with configurable matching requirements. You can require that certain flight details match between the PIREP and the network connection.

  • Require Correct Callsign Prefix — the first 3 characters of the callsign must match

  • Require Correct Callsign — the full callsign must match

  • Require Correct Departure Airport — departure ICAO must match

  • Require Correct Arrival Airport — arrival ICAO must match

  • Required Percentage — minimum percentage of the flight that must be connected to the network

  • Points — integer value awarded

Departure and Arrival Scoring Rules

These rules evaluate whether a pilot departs and arrives on time. Two sets are available: one comparing against booking times, one against route times. All share the same parameters:

  • Tolerance (minutes) — how many minutes early or late is acceptable

  • Tolerance Mode — "Both" (early and late), "Late Only", or "Early Only"

  • Points — integer value

Booking-Based Rules

These compare actual times against the booked departure and arrival times:

  • On-Time Booking Departure — award if off-blocks within tolerance of booked departure

  • Missed Booking Departure Time — deduct if off-blocks outside tolerance of booked departure

  • On-Time Booking Arrival — award if on-blocks within tolerance of booked arrival

  • Missed Booking Arrival Time — deduct if on-blocks outside tolerance of booked arrival

Route-Based Rules

These compare actual times against the route's published departure and arrival times:

  • On-Time Route Departure — award if off-blocks within tolerance of route departure time

  • Missed Route Departure Time — deduct if off-blocks outside tolerance

  • On-Time Route Arrival — award if on-blocks within tolerance of route arrival time

  • Missed Route Arrival Time — deduct if on-blocks outside tolerance

Route Times in UTC

For route time scorers to work properly, routes must have arrival and departure times entered in UTC.

Social Scoring Rules

Group Flight

Points awarded when two or more pilots who are friends on vAMSYS fly between the same airports, on the same online network, with departure and arrival times within an hour of each other.

  • Points — integer value awarded

Shared Cockpit

Points awarded when two pilots who are friends on vAMSYS book a shared cockpit flight on the same route, same online network, and their takeoff and landing times are within 5 seconds of each other.

  • Points — integer value awarded

Taxi Scoring Rules

Taxi Overspeed

Detects overspeed events during taxi phases. Can be configured to reward no overspeeds, penalise overspeeds, or both.

  • Evaluation Type — "Single Event" (any single overspeed triggers the rule) or "All Events" (evaluates all taxi events collectively)

  • Threshold Seconds — duration of overspeed before it triggers

  • Penalise Overspeed — toggle:

  • Name — penalty label

  • Points — penalty points (negative)

  • Reward No Overspeed — toggle:

  • Name — reward label

  • Points — reward points (positive)

Related

  • Scoring Groups — create and manage scoring groups that contain these rules

  • PIREPs — review PIREPs where scoring is applied

  • Fleet — assign fleets to scoring groups

  • AutoReject Rules — automatic PIREP rejection criteria

Was this article helpful?