Flight training records software, signed, versioned and inspection-ready
FlyerOS holds training records the way the CAA expects: each lesson signed by an identified person, corrections appended rather than overwritten, and retained after a course completes, aligned with CAP 1298 for DTOs and ORA.GEN.220 for ATOs.
What it does
Signed and bound to the record
A lesson is signed by an identified person, and the signature binds to the record, not to a printout that can be swapped later.
Corrections never overwrite
An amendment carries who made it, when and why; the original stands beside it, so the history is intact and any alteration is visible.
Retained and produced on demand
Records are kept for the period a training organisation is subject to, and a named student’s full history is produced as an evidence pack, not rebuilt.
A by-product of the day
The record is created as the lesson is flown and signed, maintained by nobody, rather than a folder someone keeps up after the fact.
Questions schools ask
- What makes a training record inspection-ready?
- It is traceable to the instructor who signed it, protected from silent alteration, and retained for the required period, so an inspection is a query rather than a reconstruction. FlyerOS holds records this way by default.
- Which regulations apply?
- CAP 1298 for a DTO’s training records, and ORA.GEN.220 with ORA.ATO.120 for an ATO. FlyerOS helps you operate them; it does not confer approval.
- Can a signed grade be changed?
- Only by appending a correction that records who changed it, when and why. The original is never overwritten.