Some airports require a pilot to have been there recently. Airport recency
records that: a certificate for the airport, and how current it is.
Where: a user's record → Personal endorsements → Airport recency tab
· Permission: admin + adminUsers (EDIT)
Each row is one airport, with these columns in this order:
| Column | Who fills it |
|---|---|
| Airport | You, when adding the row |
| Number | You — the certificate number |
| Country of issue | You |
| Date of issue | You |
| Expiry date | You |
| Remaining | Calculated |
| Last visit | Automatic — never typed |
| Notes | You |
This entered-versus-automatic split is the whole point of the screen, so it is
worth stating plainly:
You enter the issue and expiry dates. Joya fills in the last visit. Remaining
is the gap between them.
Set by the system. Whenever a flight lands at that airport with the crew member
on board in a cockpit seat, their last visit for that airport is updated to that
flight's arrival time. The field is read-only — there is nothing to type, and
nothing to keep in step by hand.
The distance between the expiry date you entered and the last visit
Joya recorded — that is, how much validity was left as of their most recent
visit. It turns red once negative.
If a row has no last visit yet (no flight has taken them there since the record
was created), Remaining shows —, because there is nothing to measure against.
Last visit stays empty until a flight actually lands there.
Update the Expiry date (and the issue date if a fresh certificate was
issued) and save. Do not touch last visit — it is not editable, and it is not
what expires.
| Symptom | Cause | Fix |
|---|---|---|
| Values disappear after saving | Fixed in the current release | Update; if it persists, report it |
Remaining shows — |
No last visit recorded yet | Expected until a flight lands there |
| Last visit never updates | The crew member was not in a cockpit seat on that leg, or the leg has no recorded arrival | Check the crew assignment and the journey log |
| Country of issue not saved | Fixed in the current release | Update |