Obsidian Jet Docs

Manage your documents and credential expiry

Track your passport, visa, medical, and qualification expiry with color-coded urgency, on the web portal and in the mobile app.

The international Part 135 pilot lives by document expiry — this page covers where you track it, and what the colors mean.

Web: the Document Wallet

  1. Open Documents (/crew/documents). This is a unified wallet: your type ratings, medical, recurrent training, and travel documents (passport/visa) all in one list, each with a color-coded expiry pill.
  2. Read the pill. EXPIRED (red), EXPIRES SOON (amber, within 30 days), CURRENT (green), or NO EXPIRY (green — the credential simply doesn't carry an expiry date). The date shown next to it is exactly what's on file — never adjusted or assumed.
  3. Attest a qualification. For a qualification, you can self-attest that it's accurate. This is not verification — it lands as self_attested and still reads PENDING_VERIFICATION; only an operator action can move a qualification to verified.
  4. Renew a travel document. For a passport or visa, you can record a renewal (a new expiry date), which replaces the printed expiry going forward.

Mobile: Travel Docs

  1. Open Travel Docs. This mobile screen covers just your travel documents — passport, visa, medical certificate, vaccination — not qualifications/type ratings (those live on the web wallet only, today).
  2. Read the badge. Four tones: Current (green), Expiring (amber, within 30 days), Expired (red), and No expiry date (neutral gray — distinct from "current," because absence of a date is never treated as proof of validity). A document expiring today still reads Expiring, not Expired — only a strictly past date does.
  3. Add or renew a document. Fill in the document type, identifier, issuing country, issue date, and expiry date, and save. Renewing an existing document pre-fills the form from the one that's expiring.
  4. Delete a document. Remove one you no longer need to track.

Reads on this mobile screen are network-first — if the fetch fails you get an honest "not synced" error and an empty list rather than a stale or fabricated one; this screen does not use the offline write-queue the way assignments and duty check-in/out do.

Every tone here is plain date math against the stored expiry — never an operator sign-off. A crew self-attestation or a crew-entered document is your own record, not a verified one; only an operator action reaches verified.

On this page

Manage your documents and credential expiry — Obsidian Jet