GO or NO-GO before every release
Today’s and tomorrow’s flights by aircraft, with a GO or NO-GO for every crew member before release. Delays, sickness and swaps are checked again before they save, including their effect on the days after.

A NO-GO lists its reasons
The check uses actual times where they exist. A NO-GO lists every reason, from a rest shortfall to a missing breath-analyser record, so the controller knows what to change.
Flights and GO / NO-GO16-Nov-2026, LT, CAR 7-J-III
Demo aircraft 01Twin turboprop, starts at VOBL
- DM 21106:1007:05VOBL to VOMM, off blocks 06:12
- AOKA. Okafor, PICGO
- MHDM. Haddad, Co-pilotGO
- DM 30508:4009:55VOBL to VOCI
- LFEL. Fernandes, PICGO
- KTAK. Tanaka, Co-pilot
- Rest before duty 11:20, short of 12:00 by 0:40 (para 10.1).
- No breath-analyser record on file for today.
Legality checked at 05:58 LT, from planned times until the actuals are verified.
What it does
- GO or NO-GO
- For every crew member on every flight before release, using actual data where available.
- Delays re-checked
- A delay recalculates FDP and rest for the crew affected and warns before any limit is crossed.
- Same-day changes
- Sickness, swaps and standby call-outs are checked before they save.
- Actual times
- Chocks off, take-off, landing, chocks on, engines off and landing surface, runway or water, per sector.
- Source on every entry
- Entered from the journey log or by crew in the app, with the user, device, document reference and a photo of the journey log.
- Verify, then lock
- The person who entered the actual times cannot verify them. Verified records lock; later corrections are amendments that keep the original.
- Breath-analyser record
- Time and result per crew member per day, with the receipt or video; the GO or NO-GO shows whether it is on file.
- Fleet board
- Aircraft on a timeline with delays and reason codes, cancellations, diversions, AOG and MEL items.
See it working on a demo operator
We show you the screens with demo data, then talk through your own Scheme, fleet and bases.