Every fleet has chronic offenders — the ATA chapters that keep showing up in th tech log, the LRUs that come back to the workshop with No Fault Found stamped on them again and again, the tail with a snag pattern no one has stitched together yet. The line crew works each event as a one-off; reliability engineering never gets ahead of the noise. Recurring aircraft defect analysis is the discipline that turns that noise into ranked, closable engineering campaigns — MTBUR curves per LRU, Pareto ordering per ATA chapter, and a closed root-cause loop back into the maintenance program. This guide walks the practice inside OxMaint AI-powered CMMS / Maintenance Management Software — the platform that holds the WO history, MTBUR math, Pareto view and campaign tracker on one record — or book an aviation walkthrough.
Aviation Reliability · Recurring Defect Analysis · MTBUR & Pareto
Turn Repeat Snags Into Ranked Engineering Campaigns.
Repeat defects hide inside the daily flow of squawks — same ATA chapter, different write-up, no one linking them. OxMaint AI-powered CMMS auto-links repeat entries, rolls up MTBUR from WO close data, ranks the worst offenders by Pareto, and gives reliability engineering a live queue of campaigns to close.
Repeat Auto-Link
MTBUR & MTBF Trends
Pareto Ranking
Campaign Closure Loop
The Four Reliability Metrics OxMaint Runs Per LRU
Reliability isn't one number. Four related metrics tell you different things about a component, and the gap between them is often where the real problem sits — high NFF rate means the shop is receiving parts that weren't broken, and time-on-wing is where cost hides.
MTBUR
Mean Time Between Unscheduled Removals
Total fleet FH ÷ Unscheduled removals
Counts every removal — justified or not. Includes NFF. The metric line maintenance actually sees.
MTBF
Mean Time Between Failures
Total fleet FH ÷ Confirmed failures
Counts justified removals only — a real failure at the shop. Diverges from MTBUR when NFF climbs.
NFF %
No Fault Found Rate
(MTBF − MTBUR) ÷ MTBUR × 100
The wedge between MTBUR and MTBF. High NFF means the diagnostic loop is broken, not the LRU.
TOW
Time on Wing
Time Since New (TSN) or Installation (TSI)
Longer TOW = lower lifecycle cost per FH. The metric that drives fleet-level replace-vs-repair calls.
The Pareto Board — Which 20% of ATA Chapters Own 80% of the Pain
Most fleet defect data looks flat until you rank it. Sort by count and the Pareto shape appears — a small set of ATA chapters carries most of the write-ups, and that's where reliability engineering earns its keep. OxMaint renders the fleet's rolling Pareto live so the campaign backlog reflects what's actually costing the operator, not what shouted loudest last week.
OxMaint · ATA Chapter Pareto · Last 12 Months · Fleet View
ATA 27 — Flight Controls
28% · 28% cum
ATA 21 — Air Conditioning
22% · 50% cum
ATA 32 — Landing Gear
14% · 64% cum
ATA 34 — Navigation
11% · 75% cum
ATA 36 — Pneumatic
6% · 81% cum
ATA 24 — Electrical Power
5% · 86% cum
All other ATA chapters
14% · 100% cum
The 5-Stage Reliability Loop OxMaint Enforces
Recurring defect analysis is a loop, not a report. Each stage below feeds the next, and OxMaint runs the sequence so engineering time is spent on the campaign, not on data assembly.
01
Collect
Every squawk, defer entry and WO close carries a short code, ATA chapter, tail and LRU serial. OxMaint aggregates it all into the reliability dataset without engineering re-keying.
›
02
Detect
MTBUR / MTBF trends per LRU, repeat-snag auto-linking per tail + ATA, NFF wedge widening — the software flags what has crossed a control limit before it reaches the monthly review.
›
03
Rank
Live Pareto by count and by cost weight (labour + parts + AOG minutes). The engineering backlog reorders itself as new data arrives — no manual re-sort.
›
04
Root-Cause
RCA workspace attached to each campaign — 5-Whys, fishbone, evidence photos, prior WO history and OEM service bulletins in one place, closed with an action.
›
05
Close
Action pushed back into the maintenance program — task-card revision, PM interval change, LRU repair-standard update — and MTBUR re-checked in the next window to confirm the fix held.
Same Snag, Sixth Time, Different Write-Up — That's a Campaign, Not a Squawk.
Move the reliability loop into OxMaint and let the software surface the campaigns hiding inside your line data.
Chronic Offender Watchlist — Live in OxMaint
Every campaign gets a watchlist row — MTBUR trend, NFF, RCA status, action owner. The watchlist is where the monthly reliability meeting starts and where the closure evidence gets attached.
OxMaint · Chronic Offender Watchlist · Live
| LRU / Part No. | ATA | MTBUR (FH) | Trend | NFF % | Campaign | Owner |
|---|
| Aileron Actuator · 27-42-01 | 27 | 1,840 | ↓ 22% | 38% | RCA Open | Rel. Eng. |
| Pack Controller · 21-58-04 | 21 | 2,610 | ↓ 14% | 24% | SB Trial | Powerplant |
| NLG Steering Valve · 32-51-02 | 32 | 3,120 | → Flat | 19% | PM Rev. | Systems |
| IRU · 34-21-11 | 34 | 5,780 | ↓ 9% | 52% | NFF Focus | Avionics |
| Bleed Valve · 36-11-08 | 36 | 4,240 | ↑ 6% | 16% | Closed · Monitor | Rel. Eng. |
| TR Unit · 24-31-05 | 24 | 6,900 | ↑ 11% | 21% | Closed · Monitor | Electrical |
Root-Cause Techniques Attached to Each Campaign
The RCA workspace on each campaign supports the techniques reliability engineering already uses — no separate tool. Evidence, prior WOs and OEM references stay with the campaign so the closeout is defensible.
5-WHYS
Fast Chain-of-Cause
Five iterative "why" prompts drive the shop-floor cause below the symptom. Best for single-LRU repeat events with a clear owner.
FISHBONE
Ishikawa 6M Diagram
Machine, Method, Material, Man, Measurement, Environment — the categorised map for cross-system failures where cause could sit anywhere.
FMEA
Failure Mode & Effects
Structured RPN scoring (Severity × Occurrence × Detection). Best when the campaign feeds a task-card or PM interval change.
FTA
Fault Tree Analysis
Top-down Boolean logic for safety-critical or Cat III implication events. The heavier tool, reserved for the campaigns that warrant it.
What OxMaint Gives a Reliability Engineering Team
Auto Short-Coding
Every squawk and defer entry tagged with ATA chapter, LRU serial, tail and short code so the reliability dataset is clean at source.
MTBUR Rolling Windows
Trend calculated on 3-, 6- and 12-month rolling windows so a real change is visible before a monthly meeting can catch it.
Live Pareto
Ranked by count and cost weight — the engineering backlog reorders itself as new WOs close, no re-sort by hand.
Campaign Workspace
RCA templates, evidence, prior WO history and OEM SB refs attached to each campaign — one page for the whole investigation.
Closure Verification
MTBUR re-checked in the next window after a fix ships so engineering knows the campaign held before it closes for good.
Fleet Report Export
Monthly reliability report auto-built from live data — no analyst evening spent stitching spreadsheets together.
FAQs
Q. How does OxMaint auto-link repeat defects?
Every entry carries a short code and ATA chapter. Repeats on the same tail and same chapter within a rolling window auto-link on the reliability dashboard.
See repeat auto-link live.
Q. Which reliability metric should we watch first — MTBUR or MTBF?
Q. Can the Pareto be weighted by cost, not just count?
Q. Does OxMaint close the loop back into the maintenance program?
Yes — campaign closure links the action (task-card revision, PM interval change, repair-standard update) to the affected WO template.
See closure loop in a demo.
Repeat Snags In. Ranked Campaigns Out. One Loop.
Move your reliability program onto OxMaint — auto-linked repeats, live MTBUR, live Pareto, closed RCA loop.
