MRO software connects work orders, serialized part histories, inventory, tool calibration records, and release certificates into one operational record. For a component shop under EASA Part 145 or FAA 14 CFR Part 145, that record is not optional — it is the audit. This guide covers what the software needs to do and what to look for when buying.
What MRO software actually is (and what it is not)
The term gets used loosely. At one end, generic computerized maintenance management system (CMMS) tools manage assets and schedule preventive maintenance — useful in a factory, but with no concept of a certificate of release to service (CRS) or a life-limited component. At the other end, airline maintenance and engineering (M&E) platforms handle fleet-scale work at a price and complexity that has no business in a 12-person wheel and brake shop.
Aviation MRO software, defined for a component shop, maps the regulatory workflow: receiving → preliminary inspection → work order → bench tasks → EASA Form 1 or FAA Form 8130-3 release → shipping. Every step has a timestamp, an assigned person, and a record that survives an unannounced audit. A CMMS does not do that. Neither does an airline M&E system at any price that makes sense for a small approval.
The scope of this guide is component and accessory shops operating under EASA Part 145 or FAA 14 CFR Part 145 — bench-level overhaul and repair, not airline line maintenance or base-maintenance docks. The compliance requirements and the data model are different at that scale, and most of the software reviews you will find online are written for the wrong audience.
Why spreadsheets and generic tools break down in a Part 145 shop
The failure modes are predictable. The first is document control: a technician starts work against a component maintenance manual (CMM) revision that was superseded three months ago because the shared drive was not updated. The second is calibration: a torque wrench is signed off as serviceable but its calibration certificate expired two weeks earlier and nobody caught it. The third is the incomplete traveler — at the moment of release, the work order is missing sign-offs and someone is reconstructing it from memory.
EASA AMC 145.A.55 (ED Decision 2022/011/R) sets specific requirements for computer-based maintenance records: at least one backup updated within 24 hours of any maintenance entry, and program safeguards at every terminal against unauthorized database alteration. A shared Excel workbook on a network drive cannot meet either requirement as written. That is not a preference — it is a structural gap that an auditor will find.
There is also the double-entry problem. Technicians write on paper; someone re-enters the data to a spreadsheet. Industry figures for manual re-entry error rates run around 6–8%. The errors themselves matter less than the reconciliation: when records do not match, someone has to investigate before the certificate of release to service goes out.
Shops usually feel the scheduling pain first. The record-reconstruction cost at audit is the expensive one — measured in time, in production disruption, and sometimes in a temporary suspension of activities.
Core modules a component MRO shop needs
Not every shop needs the same configuration, but these modules earn their place in any Part 145 component operation. You can follow the Part 145 workflow to see how they connect in sequence from receiving to release.
- Work order management — from customer receipt through preliminary inspection, bench work, final check, and release. The system should not allow a release step to open before the inspection record is signed and dated.
- Serialized part and component history tracking — each unit’s life-limited status, last overhaul date, and next-due interval, linked to its serial number. For wheel and brake components, you need to know exactly what was replaced, by whom, and when.
- Inventory and shelf-life control — part numbers, batch and lot traceability, expiry dates, and quarantine status. A part in quarantine needs to be unreachable in the system, not just flagged with a sticky note.
- Tool and equipment calibration management — due-date alerts, out-of-tolerance lock-out, and traceability to the calibrating entity per EASA 145.A.40(b). The alert should fire before the calibration lapses, not after a sign-off has already happened.
- Release documentation — Part 145 requires a certificate of release to service for every component worked: EASA Form 1 (Blocks 11 and 12) for EASA-approved work, FAA Form 8130-3 for FAA-approved work. A compliant system generates the correct document and surfaces dual-release obligations under BASA.
- Quality and audit trail — immutable sign-off log, document revision control, and the ability to produce a complete maintenance record package on demand. Five minutes or less is achievable; two hours is a problem.
You can see how those capabilities map to daily shop operations in the AirOne shop management features.
The Part 145 compliance backbone: records, releases, and tools
The requirements are not ambiguous. The table below covers the rules a component shop needs documented before a software decision makes sense.
| Requirement | Rule | What it requires |
|---|---|---|
| Maintenance record retention | EASA 145.A.55 | 3 years from the date of CRS |
| Digital backup frequency | EASA AMC 145.A.55 | At least one backup within 24 hours of any entry; access-control safeguards at each terminal |
| Tool calibration records | EASA 145.A.40(b) | Calibrated to an officially recognised standard; calibration entity and traceability records kept |
| Maintenance records language and format | FAA 14 CFR §145.219(a) | English; format acceptable to the FAA; demonstrates Part 43 compliance |
| Employee training records | FAA 14 CFR Part 145, Subpart E | Minimum 2-year retention |
The EASA Form 1 is where most documentation pressure lands in a component shop. Block 11 states the component status — overhauled, repaired, or inspected. Block 12 is what the auditor actually reads: it must include the maintenance data reference and revision (CMM number and revision), compliance with any applicable airworthiness directives (ADs) or service bulletins (SBs), and a clear description of the work performed. Vague Block 12 entries are a finding every time. The EASA FAQ on Form 1 certification sets out what clearly describes means in practice.
On the FAA side, the 8130-3 and EASA Form 1 operate under BASA. For used components from a U.S. repair station being accepted onto EU-registered aircraft, a dual release on Form 8130-3 is required. For rebuilt components, a dual release is not permitted — EASA treats rebuilt as a manufacturing status, not a maintenance release, and applies the same import requirements as for new parts.
Calibration failures compound quickly. When a tool’s calibration record is found to have lapsed, the finding does not stop at the tool — it calls into question every unit signed off using that tool during the lapse period. Software’s job is to surface the due date before the technician picks the wrench up, not after the certificate has gone out.
How MRO software actually reduces turnaround time
Turnaround time (TAT) is lost at waiting points, not on the bench. The technician working a wheel overhaul is rarely the bottleneck. The bottleneck is waiting for the correct CMM revision to be confirmed in use, waiting for a part to clear quarantine, waiting for a certifying staff signature from someone who left the building at 4 p.m.
Digital work-order routing gives every step an owner and a timestamp. There is no paper traveler to disappear under a bench or be destroyed by brake fluid. When a finding mid-job adds scope, the customer and the planner see it immediately — not at the moment the unit was supposed to ship.
Pre-induction kitting recovers the most time per event. Checking part availability and confirming CMM currency before the unit reaches the bench means the technician starts with everything needed to finish. A unit that arrives at the bench without the right parts will sit there until someone solves the supply problem, and that wait is invisible to the customer until the delivery promise fails.
One caveat worth stating plainly: software does not fix a shortage of licensed certifying staff. It removes the information delays that surround skilled labor. The bench work takes as long as it takes.
KPIs a component MRO shop should track
Most shops already know what is going wrong. What they lack is the data to prove it or fix it systematically.
- Turnaround time (TAT) — promised vs. actual, broken out by work scope category. An overhaul and a repair have different expected TATs and should be tracked separately.
- On-time delivery (OTD) — percentage of units shipped on or before the promised date. This is the number customers track even when they do not tell you they are tracking it.
- First-time quality / rework rate — units requiring re-inspection or re-work after initial release. Consistent rework is both a quality and a resource problem.
- Tool calibration compliance rate — percentage of calibration-due events resolved before expiry. Anything below 100% is an open Part 145 exposure.
- Record retrieval time — how long it takes to produce a complete maintenance record package on demand. This is the most direct proxy for audit readiness.
- Quote-to-actual variance — how accurately the shop estimated labor hours and parts at quotation stage. Consistent variance in one direction means the estimating model needs work.
- Work-in-progress (WIP) aging — units on the floor beyond the target TAT window. This catches scheduling problems before they become customer relationship problems.
Buying guide: what small and independent component shops should evaluate
The first question is whether the tool was built for aviation or adapted to it. A generic CMMS may handle scheduled maintenance competently and have no concept of what a CRS is. Aviation-specific tools understand the workflow natively — release certificates, life-limited components, serialized part history. That is not a feature-list comparison; it is a fundamentally different data model.
Match the software to your regulatory scope. EASA only, FAA only, or dual — the system needs to support the release documents and records your competent authority expects. A tool that generates 8130-3s but cannot produce a compliant EASA Form 1 Block 12 narrative is the wrong tool for a dual-regulated shop.
Cloud vs. on-premise comes down partly to who manages backup compliance. EASA AMC 145.A.55 requires a backup updated within 24 hours. A well-run cloud system handles this by design. An on-premise installation puts that responsibility on whatever your IT arrangement looks like — which in most small shops means whoever is most comfortable with a computer.
Pricing is real. Entry-level cloud-based aviation MRO tools start at approximately $100–$300 per user per month, or $5,000–$15,000 annually for small teams, according to SoftwareConnect’s 2025 aviation MRO software roundup. That sits next to the compliance risk of paper-based systems: one audit suspension or record-reconstruction event typically costs more — in management time alone — than a year’s subscription.
Vendor provenance matters more than the feature checklist. Ask whether the people who built the software have stood a Part 145 audit. Before signing anything, put these three questions to every vendor:
- Can it produce a complete 145.A.55-compliant record package for a single work order, on demand, in under five minutes?
- How does it handle calibration expiry lock-out — does it prevent sign-off, or just send an email that someone might ignore?
- Can it generate Block 12 narrative from work order data, or does a certifying staff member still type it by hand every time?
AirOne MRO is developed inside a working EASA Part 145 wheel and brake shop. The EASA Form 1 data fields, the work order, and the calibration log are one connected record — not three separate files someone has to reconcile after the fact.
Built on a real shop floor
AirOne MRO is developed inside a working EASA Part 145 wheel and brake shop. The first 10 Founding Shops get a full year free in exchange for honest feedback.
Frequently asked questions
Under EASA 145.A.55, an approved maintenance organisation must retain all detailed maintenance records for 3 years from the date of the certificate of release to service. Under FAA 14 CFR Part 145, employee training records must be kept for a minimum of 2 years. Maintenance records under 14 CFR §145.219 must be in English and demonstrate compliance with Part 43 in a format acceptable to the FAA.
EASA AMC 145.A.55 (ED Decision 2022/011/R) requires any computer system used for maintenance records to have at least one backup updated within 24 hours of any maintenance entry. Each terminal must also carry program safeguards against unauthorized database alteration. A shared spreadsheet on a network drive cannot meet either requirement as written — the gap is structural, not a configuration problem.
Under BASA Technical Implementation Procedures, a dual release is required when a used engine or component from a U.S. repair station is accepted onto an EU-registered aircraft. This does not apply to rebuilt components: EASA recognizes rebuilt as a manufacturing certification status, not a maintenance release, and applies the same import requirements as for new parts.
Block 12 must include: the maintenance data reference and revision (typically a CMM number and revision), compliance with any applicable airworthiness directives (ADs) or service bulletins (SBs), and a clear description of the maintenance actions performed. Listing only a CMM number without a revision reference, or omitting AD compliance status, are the most common Block 12 audit findings.
A computerized maintenance management system (CMMS) manages assets and preventive maintenance schedules — it is designed for facilities or manufacturing, not for regulated aviation maintenance. Aviation MRO software adds the regulatory layer: certificate of release to service workflow, serialized component history, EASA Form 1 and FAA 8130-3 generation, and record-keeping that satisfies Part 145 requirements. A CMMS has no concept of a CRS.
Entry-level cloud-based aviation MRO tools start at approximately $5,000–$15,000 per year for small teams (SoftwareConnect, 2025). That cost should sit next to the compliance risk of paper-based systems: one audit suspension or record-reconstruction event typically costs more in management time alone than a year’s subscription. Cloud pricing also avoids a large up-front capital commitment, which matters for independent shops.
Each unit needs its own work order tied to its serial number. Every inspection step, part consumed (with part number, batch, and traceability), and technician sign-off must be recorded and time-stamped against the traveler. The completed record package — work order, release certificate, and parts documentation — becomes the unit’s permanent overhaul history and is what the next shop or operator will rely on at induction.