Case study — US Part-145 MRO

Every non-routine task raised, tracked and billed — at the aircraft

A US MRO raising several hundred findings on a typical base visit moved its non-routine tasks off paper and onto OASES — and turned its biggest source of schedule risk into its clearest source of data.

  • ✓Findings raised against the work order at the point of discovery
  • ✓Parts, labour and sign-off attached to the task itself
  • ✓Customer approval thresholds and billing status on the same record

Book a demo of OASES

Pick a time that suits you — 30 minutes on non-routine task handling, using your own check profile.

Results after two years on OASES
100%
of non-routine findings raised digitally at the aircraft
31%
faster closure of open non-routine tasks
1,900
labour hours captured that were previously unbilled
Zero
paper task cards left in the hangar
Built for the people who sign it off
Airlines MROs CAMOs
The case study

From paper task cards to a live view of every open finding

An independent US Part-145 MRO — three line stations and a two-bay heavy check facility in the Southeast — raises several hundred non-routine tasks on a typical base visit.

The challenge

Findings were raised on paper task cards, hand-carried to planning and keyed in hours later. Supervisors could not see how many non-routine tasks were open on an aircraft, and labour booked against them was routinely under-recorded — and under-billed.

Choosing OASES

OASES was chosen for raising non-routine tasks against the work order at the point of discovery, with parts, labour and sign-off attached to the task itself. Approval thresholds and billing status sit on the same record.

Going live

A sixteen-week rollout put non-routine task raising on tablets at the aircraft, mapped approval limits to each customer contract, and trained 60 mechanics and supervisors. The first heavy check afterwards ran fully paperless for non-routine work.

Looking ahead

With two years of structured findings history, the MRO now quotes checks from its own data rather than estimates — and is exploring OASES Insights to flag recurring defects by tail and by zone.

“

We used to find out how bad a check was going at the end of it. Now every non-routine task is on the system the moment it is raised — the customer sees it, and we bill for it.

Director of Maintenance — US MRO
Inside OASES

One record per task — parts, labour, approval and sign-off

Raised on a tablet at the aircraft, visible to planning and the customer the moment it is logged.

An OASES dashboard on a tablet on the parts bench in an MRO stores area, aircraft engine in the background

Non-routine task control

Raise a finding against the work order as it is discovered, with zone, defect type, photos and the labour booked against it.

Customer approvals

Contract-specific approval thresholds route work for sign-off automatically, so nothing stalls and nothing goes unbilled.

Airworthiness management

Airworthiness directive and service bulletin tracking, with compliance status across the fleet in one place.

Maintenance planning

Forecast checks, build work packages and see the labour and parts a visit will actually need.

Components & LLPs

Full life history, position and expiry for every component and life-limited part in a single database.

OASES Insights

Reporting and dashboards built on your own maintenance data — recurring defects by tail, by zone, by check.

Trusted by airlines, MROs and CAMOs worldwide
British Airways
CAERDAV
CMA CGM
Emirates Flight Training Academy
euroAtlantic Airways
European Air Charter
European Aviation Group
FL Technics
Fly Air41
Harrods Aviation
helloJets
Heston Airlines
Hi Fly
Jazeera Airways
Jet Time
Kenya Airways
Loganair
SalamAir
SKY express
SmartLynx
Smartwings
SolitAir
Titan Airways
World2Fly

Common questions

How long does implementation take?

It depends on scope and data volume. The MRO in this case study went live in sixteen weeks, including record migration, configuration and training.

Will it fit our existing Part-145 procedures?

OASES is configured to your approved procedures rather than the other way round — maintenance programmes, approval limits and sign-off rules are all mapped during implementation.

Can we migrate historical records?

Yes. Migration and validation of legacy records is a standard part of the implementation, with a parallel-running period before the old system is retired.

How much training do mechanics need?

Raising a non-routine task is designed to be quicker than filling in a card. Structured training is delivered to mechanics, supervisors and planners before go-live.

Is OASES suitable for a smaller organisation?

Yes. OASES is used by organisations from around a hundred people up to major carriers, with the same service model applied at every size.

Does it work away from the hangar network?

OASES is accessible on any device, and line stations work to the same records as the base facility.

See it against your own check profile

Thirty minutes, no slideware — we walk through how a non-routine task moves from the aircraft to the invoice.

OASES

Airworthiness, maintenance and engineering software for airlines, MROs and CAMOs.

Communications Software (Airline Systems) Ltd, trading as OASES Part of the Valsoft Aviation Software Portfolio
Scroll to Top