Read the currency card

What this does

Turns every number, word and colour on the Currency Status card into something you can act on.

Before you start

• The acknowledgement is given and at least one authority is on, or the card has nothing to show you (→ G6).
• You’ve read How currency is worked out here. The key point: each row is fed either by a document you filed or by flights you logged, and the card doesn’t tell you which. G5 also explains why a rule can be missing from the card altogether — for example because of its operation, the part of the regulations a flight was flown under (→ G7).
• If any medical row matters to you, set your date of birth first (→ A9). Without it, a row can read Expired on a certificate that still has months to run — see A medical row is only as good as your date of birth, below.

Steps

1. On the dashboard, find the card headed Currency Status. The green badge beside the title lists your active authorities, joined by •.

   Expand

2. Find a document row: a name over Valid, Expires in N days or Expired. It’s fed by the Document Store, and you change it by filing a record (→ G2, G3).
3. Find a counting row: a name over something like 2 / 3 landings day, with (Needed) added when it isn’t met. It’s fed by your logged flights, and you change it by flying.
4. Tap the chevron on a row that reads Valid · via …, Expires in N days · via … or No leg current to see its legs. The row is green if any one of its legs is current, and the text after via names the leg that’s doing it.

   

5. Tap anywhere on the card to open Compliance Settings, where the rules behind these rows are switched on and off (→ G7).

How to tell it worked

You can point at any row and say what it wants, how close you are, and whether the fix is a document or a flight.

If something goes wrong

Reading a status line

There are five shapes, and the shape tells you what kind of requirement it is:

On a document row, any count you see is 1 / 1 and means nothing. The date is all the information there is.

Red and grey mean different things: red is an answer, grey is the absence of one. Only red is telling you to go and do something about it.

The colours, exactly

Green with a tick: met. Amber with a warning triangle: met, but expiring within thirty days. Red with an outlined circle round an exclamation mark: not met. Grey with a question mark: not checked, with the reason in the row’s own text. The thirty days is fixed, not a setting.

Not every rule goes amber first. A counting rule only has an expiry date while it’s currently met, so a rule you’re failing shows red with no amber stage before it. Between two looks at the dashboard, a landing-currency row can go from green straight to red. A document row always has a date, so it always passes through amber — though that date is only as good as what the app had to work it out from (→ G5).

A landing row can read zero on a day you flew. Some rules count only the landings you flew — FAA 61.57(a) is one, because the regulation asks for the sole manipulator of the controls. On a flight with more than one pilot on the crew, the app credits a landing to you only when PF Landing is ticked on that flight’s Times step. If the box is left unticked, the landing goes to nobody: the app can’t tell that you landed.

So a row can read 0 / 3 landings day in the same week a type-recency rule beside it reads 14 / 3 — they’re asking different questions. Tap the rule to see how many landings were held back, and why. A single-pilot flight is never affected: the box only matters when someone else could have been flying.

A medical row is only as good as your date of birth. If you left Valid Until (Optional) blank on the record, the expiry on this card was worked out from the rule’s validity period for your age on the day of the exam. With no date of birth on file the app can’t pick an age tier, so it uses the shortest one the rule has. For a TCCA Category 1, that’s three months against a possible twelve. The row is early rather than late, and the card won’t tell you that’s why.

Set the date (→ A9) or type the certificate’s own expiry into the record (→ G2). To see what the app would have used if it knew your age, open the rule: its Window chip shows the range and its Age tiers chip lists the tiers (→ G9).

Rows whose name is not a rule

Any document you gave a Valid Until date to, and that no active rule reads, gets its own row at the bottom of the card. You can tell by the label: instead of a rule’s name, it’s the event type exactly as stored, with the subcategory after a dash if the record has one — DG_Training, Medical — BasicMed, or whatever you typed into Custom event type. It reads Valid / Expires in N days / Expired straight from the date you typed. That’s how a passport, a company ID, a BasicMed or a custom event type can turn up on a compliance card. These rows come after every rule row, sorted by expiry, soonest first.

The app decides which documents land here the same way the rules decide what they read — event type, subcategory, and authority where the rule has one. So a medical in a category no rule reads, or from an authority you haven’t switched on, shows up here instead of vanishing. What it can’t do is invent a date: a record with Valid Until blank and no rule to work one out appears on no row at all (→ G2).

What the card will never do

It won’t warn you, notify you or badge anything — there are no reminders anywhere in the app. It won’t tell a document rule from a flight rule. It won’t say which age tier a medical’s window came from, or that it fell back to the strictest one. And it says nothing at all about a requirement whose rule is switched off.

Nor does a colour on this card mean you’re legal. Each row is the shipped text of one rule read against your own logbook, as of the date that rule set was last reviewed — which is the limit the acknowledgement you gave is about (→ G7). The regulation you fly under decides whether you may fly; this card is a reading of your records against it.