AirOS App (EFB)

Native iOS and Android Electronic Flight Bag — offline e-techlog, Apple Wallet boarding and crew passes, document scanner, SMS incident fallback, and optional line-worker alarm.

Overview

The AirOS app is the Electronic Flight Bag for the same operational record as the web platform — not a separate logbook. It is available on iOS and Android for entitled users of your organisation (not a separately listed priced module). Crews work offline with PIN authentication, QR provisioning, and auto-sync when connectivity returns. Scheduled sectors land under a daily tech log book per aircraft; regulatory print and the pilot QR flow share that structure.

Once ops confirm a trip on the schedule, owners add boarding passes and crew add duty passes to Apple Wallet (and Apple Watch). When the device has no data, an SMS incident report can still reach OCC and Safety if cellular SMS is available. A native document scanner with page detect feeds ARC-as-a-service and Document Control import. A line-worker session can arm a cancelable pre-alarm before a Safety incident is created.

E-techlog, load sheet, and owner booking use Flight Log, Mass & Balance, Schedule, and Customer Portal as contracted.

AirOS App (EFB)
AirOS App (EFB)

Features

  • Offline-first EFB: Full tech log and schedule workflows without internet — PIN auth, QR setup, and auto-sync when connected
  • Unified e-techlog: Scheduled sectors create sector legs under a daily tech log book per aircraft, shared with web and print
  • Apple Wallet passes: Boarding, crew duty, passenger tickets, and employee ID on iPhone and Apple Watch after ops confirm the trip
  • Native document scanner: Camera page-detect and crop adds PDFs to ARC-as-a-service and other document import flows
  • SMS incident fallback: When the device has no data, a cellular SMS can still enter the same OCC and Safety workflow — it requires a working SMS service
  • Line-worker alarm: Optional armed session with cancelable pre-alarm on stillness, likely fall, or SOS; a Safety incident is created only after escalation, not because the app “knows” someone is down
  • Load sheet on device: Mass and balance workstation, seating manifest, and interactive diagram in mobile-friendly tabs
  • Owner booking on iPhone: Owners request trips, see map confirmation, and add boarding passes from the same app as crew

Electronic Flight Bag, not a second logbook

The AirOS app (iOS and Android) is the Electronic Flight Bag for the aircraft record crews already use on the web. It is not a sidecar logbook that has to be reconciled later. Entitled users of your organisation can install it; e-techlog and load-sheet workflows follow the Flight Log and Mass & Balance modules you licence.

What crews can do without a signal

  • Complete tech log and schedule workflows offline, with PIN authentication and QR provisioning
  • Auto-sync when connectivity returns
  • Send an SMS incident if there is no data and cellular SMS is available — OCC and Safety still get the report
  • Arm an optional line-worker session: a cancelable pre-alarm on stillness or a likely fall; a Safety incident is created only if it is not cancelled (the app does not diagnose injury)
  • Scan documents with page detect for ARC-as-a-service, Document Control, and other AURA import queues

After ops confirm the trip

Owners add boarding passes and crew add duty passes to Apple Wallet (and Apple Watch). Passenger tickets and employee ID use the same PassKit path. Predicted arrivals use type cruise speed and great-circle distance when a live ETA is not available.

Load sheet, seating manifest, and mass and balance stay on the Flight Log workstation — the app is how that workstation travels.

The native app display name is AirOS. EFB is the operational capability.