EASA Part-ORO compliance, stated honestly
Navlyt maps manuals to FAA Part 135 today. EASA Part-ORO support is in development — this page explains what Part-ORO demands, how our approach will apply, and what 'on the roadmap' actually means.
Let's start where a compliance page should: with status. Navlyt's clause-level manual mapping is live for FAA 14 CFR Part 135 and Part 91. EASA Part-ORO is in development and not yet shipped. If a vendor page tells you otherwise about any product — check it the way you'd check a manual against the regulation.
Part-ORO (Organisation Requirements for Air Operations) is the EASA framework governing how a commercial operator is organised and managed: the management system under ORO.GEN, the operations manual structure under ORO.MLR, and flight crew requirements under ORO.FC, among others. Its shape differs from Part 135's — more management-system-led, less prescriptive-checklist — which is exactly why we are building the mapping model for it deliberately rather than forcing the Part 135 shape onto it.
What transfers directly is the method: parse the operator's manuals, map each procedure to the requirement it answers, quote the manual's own words as evidence, and keep a human in the loop before anything counts. That method is regulation-agnostic; the corpus is what takes the engineering time.
What Part-ORO asks of an operator
At the organisational level, Part-ORO requires a defined management system, a compliant operations manual, and demonstrable control of training and checking. The headline areas most operators manage against:
- ORO.GEN — management system, compliance monitoring, and safety management
- ORO.MLR — manuals, logs, and records, including operations manual structure
- ORO.FC — flight crew training, checking, and recency
- ORO.CC — cabin crew requirements where applicable
How Navlyt's approach will apply
The pipeline that runs against Part 135 today — parse, map, cite, human review, corrective action, evidence — is the pipeline Part-ORO support will use. The difference is the corpus: Part-ORO requirements with their references, maintained the same way the Part 135 corpus is, so a finding will cite ORO.MLR.100 the way it cites §135.21 today.
What you can do today
European operators evaluating Navlyt now typically do two things: run their English-language manuals through the existing pipeline to see the finding quality first-hand, and join the early-access conversation — because the sequence of framework delivery is set by the operators who show up with real manuals and real audit dates.
- Trial the pipeline on your manuals to judge citation quality directly
- Tell us your jurisdiction, fleet, and next audit window
- Early-access partners get direct input into the Part-ORO corpus build
Why we won't sell it early
Navlyt's entire value rests on the claim that findings are checkable. A vendor that overclaims its own capability has no standing to catch overclaims in your manuals. So the status stays on the page, the roadmap stays dated by conversation rather than by marketing, and Part-ORO ships when the corpus meets the same verification bar the Part 135 corpus does.
Frequently asked questions
Is EASA Part-ORO support available now?
No. It is in development. FAA Part 135 and Part 91 mapping is what ships today. This page exists because operators search for Part-ORO tooling and deserve a straight answer rather than a maybe.
When will it ship?
We share timelines with customers and early-access partners rather than publishing a quarter we might miss. If Part-ORO matters to your operation, talk to us — real operators with real audit dates set the sequence.
Can I use Navlyt for anything EASA-related today?
The regulation-agnostic parts work now: document lifecycle control, corrective-action tracking with owners and dates, crew medical expiry tracking, and evidence exports. The clause-level mapping against Part-ORO specifically is the part still in development.
Will findings cite Part-ORO references the way they cite §135.21?
That is the design bar: a finding will quote your manual verbatim and cite the ORO reference it maps to, with the same verify-before-display check the Part 135 pipeline enforces.
We operate under both FAA and EASA rules — what then?
Run the Part 135 side through Navlyt today and join the early-access group for the EASA side. Dual-framework operators are precisely who the Part-ORO corpus is being built with.
Related reading
Shape the Part-ORO build
Tell us your jurisdiction and audit window — early-access partners set the sequence and see it first.