bitelog.ukAll articlesHome

No Fault Found in Avionics: Using Fault Logs to Cut Unnecessary LRU Removals

Updated 16 November 2026

Few things frustrate a maintenance team more than this. A unit is pulled from the aircraft, shipped to the shop and bench-tested, then comes back with the same verdict: no fault found. Meanwhile, the original defect returns on the aircraft a few days later.

No fault found (NFF) is one of the most persistent problems in avionics maintenance. It goes by other names too: no trouble found, could not duplicate, retest OK. This article looks at why it happens and how the evidence already sitting in a unit's BITE or event log can help you avoid unnecessary removals.

What 'no fault found' really means

An NFF result doesn't mean nothing was wrong. It means the shop couldn't reproduce a failure under its test conditions. The crew saw a real symptom and the unit may well have logged real faults. Something just didn't line up between what happened in service and what the bench test checked.

That gap is the key to the problem. Closing it means getting better information from the aircraft, and making sure it travels with the unit.

Why units come back clean

The fault was never in the unit

An LRU often reports problems it didn't cause. A failing connector, a chafed wire, an unstable power supply or a misbehaving peer system can all make a healthy box log faults. Replace the box and the symptom may disappear for a while, simply because the connector was disturbed, before coming back.

Intermittent conditions the bench can't recreate

Some faults only appear at altitude, at low temperature, under vibration or during a particular flight phase. A shop bench at room temperature may never trigger them. The unit passes every test, yet fails again once it's back in the air.

Start-up faults mistaken for real failures

Many units log a burst of entries each time they power up, while interfaces and peer systems come online. These are usually normal. Read quickly under time pressure, they can look like evidence of a failed unit.

Chasing the loudest code

One genuine failure can set off a cascade of secondary faults. If the decision to remove is based on whichever code appears most often, the root cause can easily be missed.

Poor information sent with the unit

A removal tag that just says "inop" or "faulty" gives the shop very little to go on. Without the reported symptom, flight phase and relevant log entries, the shop can only run its standard tests and hope they catch it.

Why it matters

Every unnecessary removal has a cost, even when no money changes hands at the shop. Aircraft can be delayed or held on the ground. Spares get tied up in transit and testing. Engineers lose time on repeat defects. And units that keep cycling through removals without a confirmed fault are hard to manage, because nobody quite trusts them.

Using the fault log before you remove

The best time to prevent an NFF is before the unit leaves the aircraft. A short, structured look at the log can tell you a lot.

  1. Anchor on the reported symptom. Note exactly what was reported, when, and in which flight phase.
  2. Find the entries around that moment. Faults logged at the time of the event matter far more than older ones.
  3. Filter out power-up entries. Mark the normal start-up chatter so it doesn't steer the decision.
  4. Look for the first fault in any cascade. Ask whether later entries could just be consequences of it.
  5. Ask whether the unit is the cause or the messenger. Faults pointing at an external interface, bus or power input suggest checking wiring, connectors or the peer system first.
  6. Check for patterns across flights. Repeats tied to altitude, cold starts or specific sectors point towards intermittent or environmental causes.
  7. Verify against approved troubleshooting data. The log suggests a direction. Approved data decides the action.

Situations worth a second look

What the log suggestsConsider before removing
Faults on an interface to another systemCheck the peer system, wiring and connectors on that interface
Power or voltage monitor faults alongside many othersInvestigate the power supply and its connections first
Faults only at certain altitudes or temperaturesLook for environmental causes and record the conditions for the shop
Faults only in the power-up sequenceConfirm whether they are normal start-up behaviour for that unit
The same defect after a previous replacementTreat the installation, not just the box, as a suspect

If the unit does come off: send the evidence with it

Sometimes removal is the right call. When it is, give the shop the best chance of finding the fault. A useful removal package includes:

A clear, readable record also helps the next shift if the defect comes back. A short note on what was ruled out, and why, can save hours of repeated work.

Where BiteLog helps

Much of the work above is mechanical: decoding hex fault words, separating boot-up noise from real faults and lining up entries against the reported event. That's what BiteLog is built to take on.

You upload the BITE or event log from the unit, whether it's an SDU, modem, antenna controller, datalink radio or any other LRU. You tell BiteLog which unit it came from, add the aircraft and what was reported, and it reads the whole log against that unit's technical documentation. The result includes decoded fault words, start-up noise filtered out, the likely cause, a suggested fix and cited sources you can trace and check.

For NFF problems in particular, a few features are handy:

To be clear, BiteLog is a diagnostic aid only. Its output is not approved maintenance data and not a release to service. Always verify every finding against approved data before acting on it.

Pricing is usage-based, with no subscription and no setup fee. There's a 30-day free trial from first login, and many analyses are free. A typical fault analysis is about £1–£2, and even a long, detailed investigation usually comes to just a few pounds, excluding VAT. Charges are totalled into one itemised invoice at the end of each month. See the pricing page for details.

Get started

If NFF removals and repeat defects are costing your team time, try running your next suspect log through BiteLog before the unit comes off. You can request an account on the BiteLog analyser page, using your own name or a team name so everyone can share one login. New accounts are checked before they're activated.