Electronic Tech LogVersion 1.0.0 · 05/07/2026Loading…
The Recovery page works even when the application itself is down — nominated Ops staff can check status and restart the application out of hours with the recovery PIN. Every use is logged.
The logo used on the login screen, Tech Log prints, CRS, HIL, Cabin Defects Log, reports and all pages. Upload a replacement or revert to the default Fly2Sky logo.
PNG or SVG recommended, max 500 KB. Using default Fly2Sky logo.
The master trial switch. While ON the trial banners show and the controls below apply (test code, Switch aircraft, message texts — each adjustable individually). Turn OFF at go-live: banners, the test code and Switch-aircraft all stop at once. Enrol every user's MFA first, or they'll be locked out.
Stale-bundle pop-up — when an iPad detects a newer published app version, show a one-time pop-up on the Main Menu telling the crew how to update (the red star on ⇩ Update stays as the passive cue).
Trial messages — the banner on the iPad Main Menu and the note on the login screen. Leave blank for the automatic default (which reflects the 123456 toggle).
Minimum hours between iPad OTA publishes — repeated same-day publishes make every crew login download a fresh bundle and feel slow. The deploy tooling reads this limit before publishing; an emergency fix can still override it explicitly. 0 disables the guard.
Crew must fill these before a defect can be raised on the iPad.
Which roles appear in the Users → Add user dropdown. Only an admin can create admin/CAMO accounts.
Tick the roles for which each field is required in Users → Add user. Username & password are always required. By default the licence / auth no. is required for mechanics only.
| Captain | First Officer | Cabin Crew | Mechanic | CAMO | Administrator | Temp User | |
|---|---|---|---|---|---|---|---|
| Licence / auth no. | |||||||
| Full name | |||||||
Control which fields are visible, required, and their label on each iPad page. Hidden fields are removed from the screen. Required fields must be filled before signing.
No field configuration available for this page.
Flight Sign Off — filter categories — the category drop-down on the iPad Flight Sign Off screen. All (top) and Others (catch-all) are automatic. A sign-off falls in a category when its source (pirep/marep/cabin) or its kind (preflight/postflight/crs/release) matches one of the comma-separated tokens.
Advance reminder before a check is due — a Notice (and CAMO email) is raised this far ahead of each 2/10-day check.
Which conditions make an aircraft unserviceable. A mechanic’s AOG declaration is always enforced and cannot be switched off; the other conditions are configurable.
Recipient for skipped-TL-number and signed-defect-deletion notices.
Where crew feedback from the iPad is emailed. Add any number of named recipients (e.g. OCC, MCC, Duty Manager); crew choose one — or All — on the Feedback page. If none is enabled, feedback falls back to the CAMO Manager email above.
Outbound email (password resets, MFA fallback, CAMO notices) via the M365 IP‑restricted relay — no login; authenticated by the server’s source IP, so IT must whitelist this server’s public IP on the connector. Port 25 (the M365 IP-relay port that works from this server).
The ETL logs in here to read baseline TSN/CSN and post per‑sector utilisation. CAMO replaces OASES. Leave blank to keep sectors "pending".
OAuth (Keycloak client_credentials). The tenant governs uploads & connection tests only: Test (F2_OASESTEST) or Live (F2_AMALGAMATE). Reads (TSN/CSN & defects) always come from the Live read tenant below. Uploads to OASES are never automatic — you confirm each one from the back office.
Upload endpoint (per docs): POST /camo/techLogs/sectors → returns reportId; defects → defectId. Times HHMM (GMT); sectorType F/M/C and life-code oil uplifts are wired. The two tenant-specific codes below are the last items before go-live.
Both are Key=Value comma lists, pre-filled from a validated F2_OASESTEST upload. Flight-type is a 1-char code — actual set S, P, X, M (unlisted natures fall back to first letter). Report classification is a 2-char LE21 code — validated: PI=PIREP, MA=MAREP, FB=FBV.
TSN/CSN auto-syncs from the Live read tenant daily at 00:01 GMT, pulling the last 7 day(s) of tech-log pages (interim, until go-live). Active defects reconcile on their own loop — interval below. Defect import adds new open/HIL items and closes ones OASES has rectified; ETL-raised defects are never duplicated.
Trigger an immediate OASES sync. Each button runs independently — no save required.
Because OASES lags the live Tech Log, ETL never blindly overwrites its figures. Set how each tail reconciles. In Reconcile: ETL is kept whenever it is ahead (OASES catching up) and the missing legs are flagged; ETL adopts OASES only when they match within tolerance. In ETL only: ETL figures continue from the chosen date — OASES never overwrites that tail.
| Aircraft | MSN | Mode | ETL authoritative from | Current status |
|---|---|---|---|---|
| No aircraft. | ||||
Applied on the daily OASES sync and every "Sync TSN/CSN". Save settings to apply changes.
When a tech log is closed (post-flight signed), push the flight actuals it captured — OOOI times, block/flight time and landing fuel — back into the Leon Journey Log. Off by default. Leon is otherwise read-only.
Currently OFF — nothing is written to Leon.
Read-only Jamf API client (Read Mobile Devices privilege only) — aircraft-iPad labels follow the Jamf device names (nightly + “⟳ Sync Jamf names” on Devices). Personal device names are never copied. A blank secret keeps the stored one; saving verifies the credentials against Jamf. The box .env acts as fallback when these fields are blank.
When a new iPad signs in it picks a kind (Aircraft / Personal) and self-registers as pending. It works during the grace window below until an admin approves it in Devices → Awaiting approval. Beyond the grace window an unapproved iPad is blocked (admin/CAMO always exempt).
The in-app Flight Folder is opt-in per user OR per iPad — never blanket by role, and everything starts unchecked, so the live fleet and line pilots see nothing until you deliberately tick them. A ticked user gets EFF on every device they sign in on (web, personal and aircraft iPads); a ticked iPad shows EFF to whoever signs in on it. Aircraft iPads appear last and are tagged ✈ aircraft — tick one to give that tail's whole crew EFF. Turning the module off hides EFF everywhere instantly.
OM-A requires fuel checks at intervals not exceeding this value from TOC to TOD (or one check per flight if total flight time ≤ 1 h). The Nav Log highlights waypoints where a fuel entry is due.
TOD skip: if the last fuel check is within this many minutes of TOD, the TOD check flag is suppressed. Set 0 to always flag TOD.
The iPad signs the user out after this many minutes without use. Offline Leon schedule window = how many hours of upcoming flights each iPad keeps cached for an outage (default 72 h = next three days; re-fetched whenever online; max 72 h server ceiling). Picker flights shown = how many of those the Flight Details list shows at once; later flights slide in as the nearer ones are flown.