Filing Your PIREP

How the post-flight summary works, what performance data is included, and how to submit your PIREP.

Filing Your PIREP

When your flight is complete (On Block phase — parking brake set, engines shutting down), the app moves to the Post-Flight Summary screen.

Summary Overview

The summary shows your overall performance at a glance:

  • Flight Score — colour-coded rating (green / yellow / red)
  • Flight Time — block-to-block duration
  • Distance Flown — actual distance in nautical miles
  • Landing Rate — touchdown vertical speed in fpm
  • Events — total events detected during the flight
  • Violations — total violations (if any)

Performance Data

Your PIREP includes detailed performance snapshots captured during the flight:

Departure Data

Gate assignmentFuel on board (lbs)
Aircraft weight (lbs)Weather conditions at departure
QNH (barometric pressure)Departure time (UTC)

Takeoff Data

Takeoff IAS (knots)Pitch angle at rotation (°)
Flap settingWind speed & direction
Headwind component (knots)Crosswind component (knots)
Assigned runway (if available) 

Cruise Statistics

Average cruise altitude (ft)Average IAS (knots)
Average Mach numberAverage fuel flow (lbs/hr)
Average OAT (°C)Total cruise duration

Approach Quality

ILS localizer deviation (dots)ILS glideslope deviation (dots)
Stabilised at 1,000 ft AGL?Gear down, flaps set, VS within limits

Touchdown Data

Vertical speed (fpm)Ground speed (knots)
Pitch angle (°)Flap setting
Spoiler deploymentHeadwind / crosswind (knots)
Bounce detected (yes/no) 

Arrival Data

Fuel remaining (lbs)Fuel used (lbs)
Block timeGate (if available)

Flight Maximums

Maximum altitudeMaximum IAS
Maximum Mach numberMaximum G-force
Maximum climb rateMaximum descent rate
Minimum fuel remaining 

Your Options

Add Notes
Optional free-text pilot notes visible on your PIREP. Add comments about conditions, deviations, or anything noteworthy.
Submit PIREP
Files the PIREP with all telemetry, events, and performance data to the server. It appears in your pilot profile and goes through the normal approval workflow.
New Flight
Discards this PIREP and returns to the flight selection screen.
If your PIREP isn’t filed (app crash, network failure), the prefiled PIREP stays on the server. An admin can review or delete it from the admin panel.

Offline Resilience

The logger handles network interruptions gracefully:

  • Position data is buffered locally and sent in batches every 30 seconds.
  • If the server is unreachable, data is saved to a local SQLite queue.
  • When connectivity returns, queued data is automatically flushed to the server.
  • The queue retries up to 5 times per item, then discards stale data after 24 hours.

You can fly an entire flight offline — the PIREP and all data will be sent when you reconnect.