Some units never stay fixed. They come off the aircraft, test fine or get a minor repair, go back into service, and return again a few weeks later. The industry calls them rogue units, and they are expensive out of proportion to their numbers: each one cycles through removal, shipping, induction, a full bench test, and recertification on every loop. This guide shows how to catch them early using nothing but the retest count you already generate.
What Makes a Unit Rogue
Airlines and suppliers define rogues contractually. A common definition: the same serial number removed three or more times for similar discrepancies, or four no-fault-found shop visits within twelve months. Airbus documents a comparable policy for its suppliers, and its maintenance briefing notes describe a fuel quantity indicator that returned to the shop fifteen times before finally causing a low-fuel event in service.
The failure behind most rogues is intermittent: a cracked solder joint, a chafed wire, connector fretting. It appears under vibration and thermal cycling on the aircraft and disappears on a warm, still bench. A conventional functional test scans one circuit at a time and can miss a fault lasting microseconds, so the unit passes, ships, and fails again.
You cannot fix an intermittent you have not localized. But you can stop losing track of the units that carry one, and that is a data problem, not a hardware problem.
Identify Every Unit by Serial Number
Rogue tracking collapses if runs are not tied to unit identity. In a TofuPilot procedure, the unit block makes serial and part number a first-class part of every run:
name: LRU Bench Acceptance Testversion: 1.0.0unit: serial_number: default_value: "LRU000042" part_number: default_value: "622-1234-001"On a station, the operator scans or enters the serial number at the start of each run. Every test result, pass or fail, is then attached to that serial forever.
Read the Unit History
With identity in place, TofuPilot builds the per-unit history automatically. The unit page shows every run for a serial number: date, procedure, result, and every measured value. A rogue candidate reads like a story:
- Visit 1: removed for reported fault, tests NFF, returned to stock.
- Visit 2, five weeks later: same reported fault, tests NFF again.
- Visit 3: fails marginally on one measurement, minor repair, released.
- Visit 4: back again.
On paper records spread over months, this pattern is invisible unless someone remembers the serial number. In a per-unit history it is one screen.
The measurements add what the visit count alone cannot: a unit that tests NFF but whose signal margin shrinks on every visit is not fine, it is degrading. That trajectory is the difference between "no fault found" and "fault not yet caught".
Alert on Abnormal Retest Rates
Reviewing histories by hand only works for units someone already suspects. TofuPilot's retest threshold alert watches all of them: it fires when a unit has been tested more often than is normal for that procedure. The threshold self-calibrates, learning each procedure's ordinary retest rate, so a part that routinely needs two runs per visit does not generate noise while a genuine repeat offender does.
The alert resolves manually once the unit's history has been reviewed, which fits how shops actually work: the point is to force a human look at the right serial numbers, early.
From Detection to Action
Once a serial number is flagged, the shop has options that all work better early:
- Deep test instead of another standard cycle. Route the unit to environmental screening (temperature and vibration during test) or intermittence-focused equipment rather than repeating the same bench test that already passed it.
- Quarantine. Hold the unit and monitor the aircraft for a few flights before deciding; if the fault follows the aircraft, the unit was never the problem.
- Supplier claim. Rogue clauses in supply contracts trigger on exactly the pattern the history documents: removals, dates, findings per serial number. A queryable history is the evidence.
What Good Looks Like
A shop with rogue tracking under control knows its repeat offenders by name. Retest alerts surface a handful of serials a month, each of which gets a history review before its next standard test cycle. Units on their third visit go to deep test, not back to stock. And when a supplier conversation happens, the shop brings the serial's full documented trajectory instead of an anecdote.