Helicopter MRO with AI — the aircraft does not fly again until the Form 1 adds up.

The problem

The helicopter comes into the hangar in hours — the dossier comes out in weeks.

Returning a tail number to service under Part-145 is not just removing the transmission, inspecting the blades and reassembling. It means closing out, all at once, several traceability threads that live in different places:

1. Applicable ADs and SBs — Airworthiness Directives from EASA or the FAA, Service Bulletins from the OEM. A tail number comes into the hangar and nobody knows for sure whether the latest AD affecting its rotor model is already verified in its file, or whether SB-2024-XX from the transmission manufacturer is still open.
2. Rotable component traceability — every rotor, transmission, engine and accessory carries a P/N, an S/N, cycles and hours. The dataplate is marked on the part, but the cycles live in the hangar manager's Excel sheet and in a manufacturer file, and the two do not always match.
3. Work cards and NDT — every task performed by the technician is signed on paper or in a vertical system. NDT results (dye penetrant, ultrasonics, eddy current) leave the lab as a PDF, travel by email and end up in a folder.
4. Form 1 and release-to-service — the Certifying Staff signs the EASA Form 1 on the way out. Before signing, they have to be sure that everything above adds up. When something does not, the helicopter is AOG (Aircraft on Ground) — and that is thousands of euros a day.

The technical director knows this. But the bottleneck is not doing the work well — it is proving it was done well, fast. Every hour a Certifying Staff member spends hunting for a signed work card is an hour the helicopter is not flying.

How it fits the IRIS system

iLEAN does not add another MRO management system — it seals the joints between the ones you already have.

The problem in MRO is not a lack of information: it is information living in islands — the hangar management system, the OEM manuals in PDF, the AD/SB notices arriving by email, the paper work cards, the NDT reports in yet another system. iLEAN acts as the putty that fills those gaps, without replacing your CAMP/MRO software or the manufacturer's manuals.

Edge reads dataplates in the hangar. Connect captures new ADs/SBs at second zero. The agent cross-references them with the tail number and closes the dossier for release. The person — the Certifying Staff — signs the Form 1.

The three iLEAN pieces applied to helicopter MRO:

• Edge — a portable terminal with vision + OCR at the inspection station. It reads the dataplates of rotable components (P/N, S/N) and captures an image of the visual inspection (blades, transmission, airframe) linked to the work card and the technician. It works with no network — large hangars have areas with patchy WiFi and the welding equipment nearby causes interference.
• Connect — captures new EASA and FAA ADs at second zero, indexes OEM SBs when they arrive by email, digitizes handwritten work cards if you still have any, and captures the NDT report in PDF the moment it is generated in the lab. Two-way conversation: the technician asks by voice "what torque does this rotor bolt take?" and the agent gives back the figure from the CMM on the spot.
• Agent — for every tail number that enters the hangar, it cross-references the scheduled maintenance plan with the open ADs/SBs, identifies the additional tasks that need to be folded in, tracks work progress through the signatures on the cards, and returns the release-to-service dossier to the Certifying Staff. If a signature, an NDT result or a verified AD is missing, it says so before the release appointment.

See the full IRIS architecture →

Before and after

MRO by hand vs. cross-referenced MRO with iLEAN

Aspect	Today (Excel + email + work cards)	With iLEAN Edge + Connect + Agent
Reading dataplates at removal	Manual, exposed to transcription errors	Edge OCR, linked to the tail number's file
Detecting new applicable ADs/SBs	Quarterly review, risk of delay	Captured at second zero, cross-referenced automatically
Work cards	Paper, scanned later, some lost	Photo + signature indexed to the tail number and the order
NDT reports	PDF in a shared folder	Indexed to the rotable component by S/N
Closing the Form 1	Certifying Staff rebuilds it and signs	Coherent dossier, minutes to validate and sign
AOG caused by an incomplete dossier	It happens; enormous cost per day	The system warns before the release appointment

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the specific data of your hangar. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• A Part-145 helicopter organization (civil types such as AS350/H125, EC135, AW109/AW139, Bell 407…), a volume of several dozen to several hundred tail numbers a year, a mix of scheduled work and AOG.
• Focused pilot: Edge OCR of dataplates at removal + automatic closing of the release-to-service dossier with an Agent. First value expected within a few weeks.
• Indicative payback between 4 and 9 months. Hard levers: a reduction in AOG hours caused by an incomplete dossier (≥30%), Certifying Staff time saved rebuilding traceability, and reduced regulatory risk in Part-145 audits.
• On reliability: hallucinations are a problem of free generation, not of anchored tasks. In anchored tasks (reading a dataplate, linking an S/N to a file, cross-referencing an AD with a model), the best models brought error below 1.5%^[1]. And even so, release-to-service is never decided alone — the Certifying Staff signs.

^[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.