The records the CAA asks for, kept as a by-product of the day

Every lesson is recorded with what was covered, the grade, and who signed it, and, crucially, who can prove they signed it. A record is signed by an identified person, and that signature is bound to the record rather than to a printout that can be swapped later.

A correction never overwrites. An amendment is appended, carrying who made it, when and why, so the original stands beside the correction and the history is intact. That is what reliable traceability and protection from alteration mean in practice, and it is retained for the period a training organisation is expected to keep records after a course completes.

The transparency a Head of Training actually cares about is internal: who signed that lesson, who changed a grade after the fact, who deferred that defect, who moved a booking the morning of a skill test. Every record carries its own history in place, created by whom, every amendment, who made it, when and why, append-only, so the original is never lost and a correction sits visibly beside what it corrected.

It is scoped by role: an instructor sees their assigned students, an accountable manager sees everything. In most schools this lives in a paper folder, a shared drive and somebody’s memory. Here it is a by-product of running the day, maintained by nobody.

FlyerOS records the recommendation validity clock, the eighteen-month window that runs from the end of the calendar month of first attempt, along with attempts per subject, the number of sittings, and the pass mark, so a student’s theoretical-knowledge position is a fact rather than a reconstruction.

It records examination paper custody and the reporting a school owes, so the SRG2155 return is assembled from records you are already keeping. It does not sit the exam or guarantee an outcome; it keeps the record straight.

Licences, ratings, medicals and instructor privileges are structured data with expiry dates, not a wall of certificate scans. The schedule reads them: it refuses to book an instructor for something they are not currently authorised or current to do, and it says why.

Duty and flight-hour limits are modelled as rolling windows and checked when a booking is made, not discovered afterwards. A booking that would breach a limit is refused with the reason, so the limitation shapes the roster rather than being reconciled after the month closes.

An open defect, a directive or an expiring ARC makes an aircraft unbookable in the calendar the moment it is recorded. A scheduled check coming due is forecast forward and flagged against each booking with the tolerance in the programme applied: an aircraft that would be flown beyond its limits on the fourteenth is refused for the fourteenth, and one still inside tolerance is flagged as a decision, because eligibility is evaluated for the time the flight is scheduled for, not the moment it was booked.

On the roadmap, not built yet: confidential occurrence reporting, a hazard and risk register, and corrective actions tracked to closure, with the tighter access controls safety data deserves, and an ECCAIRS-ready export. Until it ships, keep running your SMS in your current tools. Telling us how you run it shapes what we build.

At a standardisation visit or a continuation audit an inspector asks for specific evidence about specific people, aircraft and dates. FlyerOS assembles it as an evidence pack, scoped to what was asked, date-filtered, read-only and expiring, from the records the day already produced, rather than a fortnight of reconstruction.

This section is meant to be useful to your school whether or not you ever buy FlyerOS: it is a plain description of what a UK inspection actually asks for.

The annual internal review and the annual activity report are assembled from records a declared training organisation is already keeping day to day, not written from memory once a year against a deadline.