Help centre · For pilots

The evidence badge on a PIREP

Watch the video: Reviewing PIREPs

Every flight filed by ACARS shows an evidence badge next to its status, at the top of the PIREP page. It tells you, staff and the other pilots how well the flight's figures are backed by what Vaeroly itself saw on the flight track, not only by what the app said.

What the badge says

  • Checked by the track: everything Vaeroly could check agrees with the recorded track.
  • Confirmed: 2 of 4: some facts are confirmed, the others had nothing to check them with (an older ACARS, or a gap in the track).
  • To check: 1: one fact doesn't agree with the track. Staff look at it before anything moves or counts.
  • Little data to check: the flight recorded too little to confirm anything.

Flights filed by hand, from a claim or imported from old records say Not recorded by ACARS.

The lines under Evidence

Press the badge, or scroll to the Evidence card below the tiles, to see each fact:

  1. Take-off point: where the aircraft left the ground, against the departure airport. More than 10 nm away (the simulator reloaded at another airport) shows as Took off 42 nm from LHBP.
  2. Landing: the touchdown the app reported, against the track on the ground after it. When no track confirms it, pilot and aircraft stay at the planned arrival until staff accept the flight (see After a diversion).
  3. Flight track: how many positions were recorded, and whether the position jumped.
  4. Aircraft: whether the aircraft in the simulator matches the booked one, when ACARS could read its name.

Below them, grey lines say what the flight was recorded with: the ACARS version and simulator, the aircraft's title in the simulator, and where the flap lever was read from (the add-on's own variable or the simulator's reading). They are information, not checks.

Good to know

  • When the track contradicts what the app said, the flight waits for staff and is never accepted by itself. That covers a take-off far from the departure, a track that starts in the air (so the take-off point can't be checked), a diversion the track doesn't confirm, and a touchdown the track doesn't match. Landing at the planned arrival needs no track: the booking confirms it.
  • Staff also see the badge next to each flight in the review queue and the PIREP list, as it was when the flight was filed.
  • On the PIREP page it is worked out each time the page opens, so older PIREPs have one too.
  • To get the most lines confirmed, keep ACARS running from the gate to the gate and use the newest version. See How flights are measured.

Was this helpful?