For Airlines + ATOs
A logbook your pilots can trust, with your data handled properly.
Your pilots already keep a logbook by law, and many of them now forward your flight emails to fill it. The OALO Project reads those emails for one purpose only: the logbook entry. Everything else is thrown away as the email is read.
What we keep, and what we never keep
Kept: only what the logbook requires
- Date and flight number
- Departure and arrival airports
- Off-blocks, take-off, landing and on-blocks times (UTC)
- Aircraft type and registration
- The commander’s name and the pilot’s own role
Never kept
- Fuel figures, uplift and burn
- Passenger numbers, loads, freight and weights
- Delay codes, delay reasons and captain’s remarks
- Other crew members’ names and contact details
- The email itself: it’s read once and never stored
These are the fields required by Part-FCL (FCL.050) for EASA and UK CAA licences, and nothing more.
How we handle it
- Each format is built carefully. A reader for your email format is written and tested against real examples, with the operational lines blanked before anyone looks at them, and checked by a pilot before it goes live. Flight emails from many airlines worldwide are already read.
- The pilot stays in control. Every entry waits for the pilot to confirm it, and is checked against their authority’s rules.
- Never sold, never shared. A pilot’s logbook is visible only to them. OALO never sells or passes on logbook or operational data.
- Secure by design. Encrypted personal data, an append-only change history on every entry, and access to the operations side limited and logged.
- Your brand stays yours. OALO is for every pilot and never uses airline names or logos to promote itself.
For training organisations
Students can start their OALO logbook from their first lesson, in the format of the authority that will issue their licence, and carry it with them into their career. Digital countersigning already lets a commander sign a PICUS entry with a finger, with their name and licence number recorded. Instructor sign-off for students’ entries is being built with training organisations: tell us what your school needs.
Partner with OALO to share logbook data
Pilots may only send OALO flight emails from their own personal email accounts. If your organisation would like to send logbook data for your pilots or students directly, for example after each training flight, it needs a partnership agreed with OALO first. We’ll agree with you in writing exactly what is sent, with each pilot’s consent.
- Less admin, fewer mistakes. Times, aircraft and roles go straight into each pilot’s logbook, so nobody re-types them and instructors answer fewer logbook queries.
- Ready for checks and licence applications. Entries are checked against the pilot’s authority’s rules (FCL.050 for EASA and UK CAA licences) and printed like the paper logbook.
- Digital signatures. Commanders countersign PICUS entries with a finger, recorded and locked to the entry; instructor sign-off is being built with training organisations.
- Data handled properly. Only logbook fields are kept, emails are deleted once read, operational and company-sensitive details are discarded, and a pilot’s logbook is never sold or shared, including with you.
- An offer for your pilots and students. We can set up a partner offer, such as a longer free trial of OALO Pro.
Talk to us about a partnership
Working together
- Confirm your flight-email format with us, so your pilots’ entries are right from day one.
- Point your pilots and students to a logbook that meets their authority’s format.
- Agree the data handling in writing: what we read, what we discard, and how quickly.