This notice explains the regulatory position of XOps. It forms part of the Terms of Service. Please read it before relying on the platform in your operation.
1. XOps is decision support, not an approved system
XOps is planning and decision-support software. It is not certified or approved by EASA, the FAA, the UK CAA, or any other national aviation authority ("NAA"), and it is not a substitute for the systems, manuals, and procedures your Air Operator Certificate ("AOC") requires. Nothing in the platform constitutes operational, legal, or airworthiness advice.
2. The operator remains accountable
- Responsibility for compliance with your AOC, operations manual (OM-A/B/C/D), FTL scheme, and every applicable regulation remains with the operator and its accountable manager and nominated post-holders at all times.
- Rosters, schedules, feasibility verdicts, pricing, and disruption-recovery options produced by the platform are proposals. They must be reviewed and approved by appropriately qualified personnel before operational use.
- Publishing a roster to crew, or pushing a schedule to a third-party system, is a decision of the operator, taken through the platform's explicit approval gates.
3. About the built-in rule engines
- The platform ships flight-time-limitation rule sets implemented from published regulatory material: EASA Regulation (EU) 965/2012 Subpart FTL with CS-FTL.1, US 14 CFR Part 117, and UK CAP 371, plus a bio-mathematical fatigue model producing FRMS-style advisories.
- These engines are configurable, and operator-level overrides are restricted to being more conservative than the base rule set — never less.
- Regulations, AMC/GM material, and NAA-approved individual FTL schemes change and vary by operator. It is the operator's responsibility to verify that the configured rule set matches its approved FTL scheme and to validate results against its own compliance processes before use.
- A "0 violations" result means the plan passed the configured checks — it is not a legal determination of compliance.
4. Fatigue model
The fatigue scores are outputs of a published bio-mathematical model (a Three-Process type model). They are advisory inputs to the operator's Fatigue Risk Management System, not medical assessments and not a clearance to extend duties.
5. Data flowing to and from third-party aviation systems
When the operator connects scheduling or crew systems (for example LEON or the XOps crew application), the platform transmits what the operator instructs it to transmit. The operator must verify imported data (fleet, crew, qualifications, duties) before planning against it, and verify exported data in the receiving system before operational use.
6. No dispatch or flight-following function
The platform does not perform flight dispatch, flight following, weight and balance, performance calculation, or NOTAM/weather briefing. Disruption-recovery options are planning aids for the operator's OCC, whose procedures prevail.
7. Incident reporting
If you believe a platform output contributed to an operational error or a regulatory finding, notify us via the contact form so we can investigate, and preserve the relevant run records (the platform keeps audit snapshots of approvals and optimiser runs for this purpose).