PIREPs

PIREPs (Pilot Reports) are how pilots earn hours and points towards rank progression and activity completion. The PIREP Management page is where staff review, accept, reject, or adjust PIREPs. A badge on the navigation item shows the count of PIREPs awaiting review.

Accessing PIREPs

In Orwell, go to Flight Centre → PIREPs. You need the Can Manage PIREPs & Claims permission.

PIREP Sources

PIREPs are created through several channels:

• Pegasus ACARS — automatically filed when a pilot completes a tracked flight

• Claims — manually filed by pilots for flights not tracked by Pegasus (must be enabled in Settings → vAMSYS Modules)

• Transfer PIREPs — created via Pilot Invite or Rank Transfer to credit previous hours

PIREP Statuses

Status	Colour	Meaning
Processing	Blue	PIREP is being processed or scored by the system
Accepted	Green	PIREP passed all checks or was accepted by staff. Hours and points awarded.
Awaiting Review	Yellow	PIREP failed one or more AutoReject rules and needs staff review.
Rejected	Red	PIREP was rejected by staff. Pilot receives credited time but no points.
Invalidated	Red	PIREP was invalidated by staff. Pilot receives no time and no points.

Predefined Views

View	Description
Pending Review	PIREPs awaiting staff review that are not waiting for a pilot reply. Default view when pending PIREPs exist. Badge shows count.
Awaiting Pilot	PIREPs flagged as Reply Needed — waiting for the pilot to comment before further action. Badge shows count.
All	All PIREPs regardless of status. Default view when no pending PIREPs exist.

Review Actions

When reviewing a PIREP, staff have the following actions available:

Action	Effect
Accept PIREP	PIREP passes review. Hours and points are awarded as listed.
Reject PIREP	PIREP is marked as rejected. Pilot only receives credited time, no points.
Invalidate PIREP	PIREP is marked as invalidated. Pilot receives no time and no points.
Reprocess PIREP	Sends the PIREP back through the processing pipeline. The landing rate is cleared so it can be re-evaluated.
Mark Reply Needed	Flags the PIREP so the pilot must leave a comment before they can book and fly additional flights. Can only be set when the PIREP is in the Awaiting Review state.
Next Pending PIREP	Navigates to the next PIREP awaiting review.

Review Page Layout

Clicking a PIREP opens the review page with a two-column layout. The left column (two-thirds width) shows flight data and visualizations. The right column (one-third width) shows review tools, communication, and metadata. All panels load lazily for performance.

Left Column — Flight Data

Status Panel

Always shown at the top of the review page. Displays:

• Status badge — colour-coded PIREP status (see PIREP Statuses table above). Claims show an additional "Claim" badge.

• Pilot information — username, full name, and rank. A "View Pilot" link opens their profile in a new tab.

• Reply Needed flag — displayed when the PIREP has been marked as requiring a pilot reply before further action.

• AutoReject violations — for ACARS PIREPs only. Lists which AutoReject rules were triggered, displayed in a red warning box.

• Claim message — for claims only. Shows the message the pilot submitted when filing their claim.

• Touchdown selection warning — shown when multiple touchdowns were detected and none has been selected yet. Staff must select a landing before accepting or rejecting.

Landing Rate Selection

Shown only when Pegasus detected multiple touchdowns during landing and no touchdown has been selected yet. Each detected touchdown is displayed as a selectable card showing:

• Rate — vertical speed in feet per minute (FPM)

• G-force — impact force at touchdown

• Time — when the touchdown occurred

• Gear status — whether landing gear was down

• Pitch and Roll — aircraft attitude in degrees

• Speed — groundspeed at touchdown in knots

• Runway — detected runway identifier

• LDA — Landing Distance Available in feet

Staff select a touchdown and click Save Selection. Once selected, the PIREP's landing rate and G-force are updated and the pilot's statistics are recalculated.

Proof of Flight

Shown for claims only. Displays the evidence the pilot provided when filing their claim:

• Uploaded images — displayed as thumbnails with links to full-resolution versions

• External links — URLs provided by the pilot, shown with their domain name

Visualisations

Shown for ACARS PIREPs only (not available for claims). A multi-tab panel where each tab can be toggled independently — Map, Departure, Flight, and Approach. Tab state is remembered in your browser.

Map — displays the flight path colour-graded by altitude with a planned route path overlay.

Flight Chart — plots altitude (ft) and groundspeed (kts) over time. Supports zoom (scroll), pan (drag), and area select (shift+drag). Colour-coded event annotations can be toggled by category:

• Pushback events (indigo)

• Engine starts/stops (amber)

• Flap changes (cyan)

• Touchdowns (green)

• Gear changes (orange)

• Stability gates (purple)

Clicking an event in the legend scrolls the chart to that event and highlights it.

Departure Analysis — detailed departure performance data. Requires position reports, a detected liftoff event, and a matchable runway. Shows:

• Detected runway — identifier, bearing, and coordinates of the departure runway

• Liftoff metrics — pitch, max pitch, roll, speed, rejected takeoff count, altitude AGL, distance from threshold

• Climb profile — altitude plotted against distance and time for the first 5 minutes after liftoff

• Performance metrics — runway utilisation (feet used, percentage, remaining distance), climb gradient (ft/NM), climb rate (FPM), centreline tracking (max and average cross-track deviation)

• Departure events — gear retraction and flap changes during climb-out

Approach Analysis — detailed approach and landing performance data. Requires position reports, a runway identifier in the touchdown data, and that runway being found in the vAMSYS database. Shows:

• Approach profile — data for the final 15 NM: altitude MSL and AGL, distance from threshold, ideal glideslope (3 degrees with threshold crossing height), glideslope deviation in feet and dots, cross-track error, groundspeed, and heading

• Landing report — data at altitude gates (2000ft, 1000ft, 500ft, 200ft, 100ft, 50ft, touchdown): airspeed, vertical speed, pitch, roll, and gear status

• Flare analysis — sink rate at 50ft vs touchdown, sink arrest percentage, pitch increase, and quality assessment (Excellent, Good, Fair, or Poor)

• Touchdown data — rate, G-force, distance from threshold (feet and percentage), runway remaining, pitch, roll, speed, rollout distance, and assessment (Short, Early, Good, or Long)

• Runway path visualisation — overhead view of the approach path relative to the runway centreline

Flight Details

Always shown, but the available fields differ significantly between ACARS PIREPs and claims. For ACARS PIREPs, the panel displays comprehensive flight data grouped into the following sections:

Identity and Aircraft — callsign, flight number, flight type, network (if applicable), aircraft registration with link to aircraft management, fleet name with link to fleet management, and livery details (name, approval status with link to livery management).

Event Timeline — a comparison table showing times for each flight phase. Columns adapt based on available data:

• Actual — off blocks, takeoff, landing, on blocks (always shown)

• Route — scheduled departure and arrival times from the route definition, with derived takeoff/landing using average taxi times from airport analytics

• Estimated — SimBrief Out, Off, On, In times (only when dispatched via SimBrief)

• Booked — departure and arrival times from the booking, with derived takeoff/landing

Each column includes a delta showing early, on-time, or late against actuals. Duration rows between events show taxi out, airborne time, taxi in, and total block time with their own deltas. Night flight indicators (sun/moon icons) appear next to takeoff and landing times.

Tracking and Time Summary — tracking start and end times, awarded (credited) time, paused air time, paused ground time, and total paused time. A warning is shown if the paused percentage exceeds 5%.

Performance (ACARS only) — shown below the timeline. When dispatched via SimBrief, displays a comparison grid with Actual, Estimated, and Delta rows for:

• Distance — flight distance vs SimBrief air distance (NM)

• Average Groundspeed — calculated vs SimBrief estimated (kts)

• Weights — ZFW, TOW, and LDW vs SimBrief estimates (shown in the pilot's preferred unit: kg or lbs)

Without SimBrief, these values are shown in a simple grid without comparison rows.

Fuel (ACARS only) — shown in the pilot's preferred unit (kg or lbs). With SimBrief: a comparison grid showing Actual, Estimated, and Delta for ramp fuel, takeoff fuel, fuel used, landing fuel, and fuel flow per hour. Without SimBrief: a simple grid of the same values without comparison.

Touchdown (ACARS only, when touchdown data exists) — rate (FPM), G-force, runway, touchdown point (distance from threshold in feet and percentage), LDA, rollout distance, speed, pitch, and roll.

For claims, only basic information is shown: callsign, flight number, aircraft, fleet, and livery. All operational flight metrics (timeline, performance, fuel, touchdown) are hidden since no tracking data is available.

Dispatch Panel

Always shown. Displays the dispatch configuration for the flight:

• Cost index — the cost index used for flight planning

• FL / Altitude — planned cruise altitude, formatted as a flight level (e.g. FL350) when applicable

• Passengers — number of passengers on board

• Freight — cargo weight in kg or lbs based on pilot preference

• Luggage — luggage weight in kg or lbs

• Containers — if applicable, an expandable section showing each container with its name, type, notes, unit size, unit weight, quantity loaded, and total weight. Links to container management.

When the flight was dispatched via SimBrief, a SimBrief OFP button appears in the panel header, linking to the Operational Flight Plan PDF download.

Flight Data Logs

Shown for ACARS PIREPs only. A filterable log of all events recorded by Pegasus during the flight. Each log entry shows:

• Timestamp — when the event occurred

• Message — description of the event

• Type label — category of the event

• Departure offset — time relative to departure (+/- HH:MM)

• Arrival offset — time relative to arrival (+/- HH:MM)

• Flight phase — Init, Ground (Departure), Departure, Enroute, Arrival, Landing, Ground (Arrival), or Other

Events can be filtered by flight phase using the grouped filter buttons.

Right Column — Review Tools

Internal Notes

Always shown. Staff-only notes attached to this specific PIREP — not visible to pilots. Useful for recording exceptions, observations, or internal decisions about a flight. Notes can be edited at any time.

Pilot Notes

Always shown. Staff-only notes attached to the pilot rather than the PIREP — they appear on every PIREP from this pilot. Useful for tracking warnings, special circumstances, or ongoing issues. Staff can add and delete individual notes.

Comments

Always shown. Two-way communication channel between staff and the pilot.

• Staff can use comment presets to quickly insert standard responses

• The Hide Name option lets staff post comments without revealing their identity to the pilot

• Reply Needed toggle blocks the pilot from booking new flights until they reply

• When either party adds a comment, the PIREP returns to the review queue

• Comments are disabled on rejected or invalidated PIREPs when the corresponding appeal setting is enabled in PIREP Settings

Time

Always shown, but content differs between ACARS and claims. For ACARS PIREPs, displays:

• Awarded (credited time) — prominently displayed in the centre, this is the time that will be awarded to the pilot

• Airborne — time from takeoff to landing

• Block — time from off-blocks to on-blocks

• Scheduled — expected time from the route definition

• Estimated — expected time from the booking

• Paused times — air paused, ground paused, and total paused. A warning highlight appears if paused time exceeds 5%.

Staff can click Edit to adjust airborne time, block time, paused air, and paused block. Changes are saved and credited time is recalculated based on the airline's include_taxi_time setting. For claims, only the awarded time is shown (set when the claim was accepted).

Points

Always shown. Displays the point breakdown for the PIREP with two sections:

• Flight Scores — individual scoring rule results (each showing name and +/- points) with a flight score total

• Bonus Points — additional points from activity completions, manual adjustments, awards, or penalties with a bonus total

Staff can click Edit to open a modal where both flight scores and bonus points can be modified. Presets can be applied to quickly add standard point adjustments to both sections. Individual score entries can be added, removed, or renamed.

Previous Claims

Shown for claims only, when the pilot has previous claim history. Displays recent claims from the same pilot showing each claim's PIREP ID, date, and status. Useful for spotting patterns in claim frequency or legitimacy.

Route

Always shown. Displays route information for the flight:

• Airports — departure and arrival airports with links to airport management

• Flight identification — callsign and flight number

• Company route vs pilot route — if the pilot's filed route differs from the company route, both are shown

• Route remarks — any notes attached to the route

• Scheduled times — departure and arrival times with duration

METAR

Always shown. Displays historic weather data:

• Departure METAR — weather at the departure airport at the time of departure

• Arrival METAR — weather at the arrival airport at the time of landing

Activity Logbooks

Shown when the PIREP contributes to one or more activities. Displays which activities (tours, events, challenges) this PIREP counts towards, including tour leg information where applicable.

Staff Actions

Always shown. A complete, immutable audit trail of every staff action taken on this PIREP. Shows who performed each action, what they did, and when. This log cannot be edited or deleted.

ACARS vs Claims Comparison

The review page adapts based on whether the PIREP was filed via Pegasus ACARS or as a manual claim. Claims lack flight tracking data, so staff review based on the pilot's submitted proof and historical averages.

• ACARS only — Visualisations (Map, Flight Chart, Departure Analysis, Approach Analysis), Flight Data Logs

• Claims only — Proof of Flight, Previous Claims

• Both but different content — Status Panel (ACARS shows AutoReject violations; claims show claim message), Flight Details (ACARS shows full metrics with timeline, performance, fuel, and touchdown; claims show only basic identity and aircraft info), Time (ACARS shows full breakdown with edit; claims show only awarded time)

• Both with same content — Dispatch, Internal Notes, Pilot Notes, Comments, Points, Route, METAR, Activity Logbooks, Staff Actions

Reviewing Claims

Claims are a special type of PIREP filed manually by pilots for flights not tracked by Pegasus. All claims require manual review — they cannot be auto-accepted.

Accepting a Claim

When you click Accept on a claim, a modal displays computed reference data to help you set fair time and point values:

• Claimed Time — the duration between the pilot's submitted departure and arrival times

• Average Route Time — average credited time for completed PIREPs on this specific route. Helps determine if the claimed time is reasonable.

• Average Route Points — average points awarded on this route

• Average Pair Time — average credited time for all PIREPs between this departure and arrival airport pair, across all routes. Useful when the route is new or has limited history.

• Average Pair Points — average points for the same airport pair

You must enter the following values:

• Hours — 0 to 24

• Minutes — 0 to 60

• Points — optional, defaults to 0

When a claim is accepted, the status changes to accepted, credited time is set to the entered hours and minutes, points are set to the entered value, activity progress is recalculated for any tours, events, or challenges, and the pilot's total hours and points are updated.

Accepted claims can still be rejected later, and rejected claims can be accepted. Claims do not trigger automated scoring rules since they lack flight data — all time and point values are set manually by staff.

Rejecting a Claim

Rejecting a claim awards no points and no hours. Rejected claims may still count towards activity requirements depending on your VA settings.

Bulk Actions

Select multiple PIREPs using the checkboxes to perform bulk actions. All bulk actions require confirmation.

Action	Description
Bulk Accept PIREPs	Accept all selected PIREPs (excludes claims and already accepted PIREPs)
Bulk Reject PIREPs	Reject all selected PIREPs (excludes claims and already rejected PIREPs)
Bulk Reject Claims	Reject all selected claims (excludes non-claims and already rejected claims)
Bulk Invalidate PIREPs	Invalidate all selected PIREPs (excludes claims and already invalidated PIREPs)
Bulk Reprocess PIREPs	Reprocess all selected ACARS-filed PIREPs (skips claims, transfers, and non-ACARS PIREPs)

Comments System

The comments panel enables two-way communication between staff and pilots on a PIREP.

• Staff can use comment presets to quickly insert standard responses

• The Hide Name option lets staff post without showing their name

• When either party adds a comment, the PIREP returns to the review queue

• Comments are disabled on rejected PIREPs if Rejected PIREP Appeal is enabled in PIREP Settings, and likewise for invalidated PIREPs

Notes: Internal vs Pilot

Type	Scope	Visible To	Best For
Internal Notes	Per PIREP	Staff only	Recording exceptions, observations about a specific flight
Pilot Notes	Per Pilot	Staff only	Warnings, special circumstances, or ongoing issues with a pilot

Staff Actions Audit Trail

Every action taken on a PIREP is logged in the Staff Actions panel. This includes who performed the action, what they did, and when. Tracked actions include: accepting, rejecting, invalidating, reprocessing, landing rate selection, comment creation/deletion, point and time edits, internal note changes, and reply needed toggles.

Table Columns

Default columns: PIREP ID, Pilot Name, Username, Callsign, Departure, Arrival, Landing Rate, Points, Bonus Points, Status.

Additional columns: Flight Number, Aircraft Registration, Fleet Name/Code, Livery, Booking Type, Route Tag, G-Force, Credited Time, Network, Simulator, Reply Needed, Created.

Filtering

The table supports advanced filtering by:

• Created date — filter by when the PIREP was filed

• Status — complete, accepted, failed, rejected, or invalidated

• Departure / Arrival airport — filter by airport codes

Related

• Bookings — view the bookings that generated PIREPs

• Liveries — approve or reject aircraft liveries that may affect PIREP status

• Presets — create reusable comment and point macros for PIREP review