Engineers reviewing evidence for a repeat removal investigation beside an air cycle machine at an FAA-certificated repair station

Repeat Removal Investigation: A Program for Finding Why the Same Fault Keeps Coming Back

By the AeroKool Aviation team · Hialeah, Florida

Repeat removal investigation is the structured work of finding out why the same fault keeps returning to an aircraft, and it is a program with an owner and a closing decision, not a longer troubleshooting session. It starts when the pattern is recognized and it ends when someone can say what changed on the aircraft, not what was done to the unit.

The difficulty is that every party already has an explanation. The shop points to a unit that tested clean, the operator points to a unit that failed on the aircraft, and each is describing a different piece of the same problem. An investigation exists to put the pieces on one table.

This guide sets out a four-step program for opening, evidencing, reasoning about, and closing a repeat removal investigation. The steps are program steps, not shop steps: they describe how an operator or a reliability team organizes the work, and they contain no test limit, acceptance criterion, or procedure for a part number. For the pattern that triggers the work, see why aircraft component repeat removals persist.

Prerequisites: What to Settle Before the Investigation Opens

An investigation that starts without these three things settled turns into a series of conversations. Settle them once, in writing, and reuse them.

Confirm who owns the investigation

Under Part 121, the certificate holder is primarily responsible for the airworthiness of its aircraft, and 14 CFR §121.363 provides that arranging for another person to perform maintenance does not relieve it of that responsibility. 14 CFR §121.373 requires continuing analysis and surveillance that reviews the maintenance programs and corrects deficiencies, whether the work is done by the certificate holder or by someone else. A repeat removal investigation therefore belongs to the operator, with the shop as a contributor.

Operators outside Part 121 should confirm how responsibility is allocated in the contract and the maintenance program. The practical exposure is the same.

Agree what triggers an investigation

Write down what pattern opens one. It can be the same unit returning, the same position returning with different units, or the same complaint coded in different ways. FAA Advisory Circular 120-79A lists among its non-routine data ““Chronic” systems that have repeat write-ups in a specified time period”, with 10 to 15 days as an example of its own, not as a rule.

None of the sources cited in this guide sets a trigger. The trigger is the operator’s decision, and the written version is what keeps two people from reading the same pattern differently.

Agree who sees what

An investigation needs the aircraft-side record, the shop-side record, and a person who reads both. Decide in advance how the shop receives the removal history and how the operator receives the shop’s findings. A finding that does not reach the owner of the investigation might as well not have been made.

It also helps to agree on the form of the exchange. A shared folder, a standing request to the shop, or a single named contact on each side is enough, as long as the same route is used for every removal and the route is written down.

Step 1: Open the Investigation and Freeze the Evidence

The first step is to stop the evidence from disappearing. Every day of routine handling changes what can be learned.

Name the owner and write the question

Record one owner and one question, such as why the same complaint has returned on this position. A question that names the unit invites a repair. A question that names the complaint invites an explanation.

Date the entry. Everything that follows is measured from it.

The owner does not have to perform the work. The owner has to make sure that each step happens, that each result is recorded, and that the decision at the end is written by someone who has read the whole file.

Hold the unit and the records before anything is cleaned or discarded

Ask the shop to hold the removed unit, the replaced parts, and the findings as received. Cleaning removes deposits that show where contamination came from, and discarded parts take their wear patterns with them. If the unit has already been repaired, say so in the record, because the evidence available is then different.

What an aircraft component teardown report has to contain covers the document that preserves what was seen before the repair erased it.

Step 2: Assemble the Evidence Package

An investigation is only as good as its package. Collect it before anyone proposes a cause.

Collect the removal history by serial number and by position

Gather every earlier removal of the unit and of the position, with dates, complaints in the operator’s words, and the shop findings. Read the complaints, not the codes. A fault coded three ways looks like three faults until the entries are laid side by side.

FAA Advisory Circular 120-79A lists “Unscheduled parts replacement or unscheduled maintenance” and “Individual component failure rates” among the data an operator’s analysis uses. The history is how those entries become a pattern.

Obtain the shop record

Ask for the teardown report, the test record, and the manufacturer data the tests were run against. 14 CFR §43.9(a)(1) requires a maintenance record entry to describe the work performed or reference data acceptable to the Administrator, and a finding that says only “no fault found” gives the investigation little to work with. How a no fault found finding should be documented explains what a credible one carries.

Note what the shop did not examine. Absence of a finding means something only when the examination was made.

If the record does not say whether a check was performed, ask. A reply that the check was not part of the scope is an answer, and it tells the investigation where the gap is.

Collect the aircraft-side record

Gather the entries the operator holds: the original write-up, related maintenance performed before and after each removal, the conditions reported at the time, and anything changed on the aircraft between removals. The aircraft-side record is the half the shop does not see, and it is often where the pattern is visible.

Look at the interval between removals as well as the content of each one. A fault that returns after a similar period of operation each time suggests something about the installation or the environment, while a fault that returns at irregular intervals suggests something different. Neither reading is a conclusion, but each one narrows the list in the next step.

Step 3: Separate the Hypotheses

With the package assembled, the investigation reasons about causes. This is where it differs from repeating the repair.

List the candidates outside the unit as well as inside it

Write down every explanation the evidence allows. The unit itself, the installation, the control signal, a sensor, an upstream condition such as contamination, and the repair or test process are all candidates. A unit that failed repeatedly in different shops points away from the shop and toward the aircraft.

The reverse also holds. If the same shop handled every removal and the units differ in serial number, the process at that shop is a candidate that deserves the same scrutiny as the installation.

A short list that includes the aircraft is more useful than a long list that is only about the unit. How a damage pattern traces to another component covers the evidence that separates a failed unit from a victim.

Decide what would confirm or exclude each hypothesis

For each candidate, state what evidence would support it and what would rule it out, before any check is made. An investigation that decides what it is looking for after it has seen the result can confirm anything. Write the expectation first.

This also protects the people involved. When the expectation is on record before the check, nobody can later say that the result was bent to fit a preferred explanation.

Keep the checks within the approved procedures for the aircraft and the component. This guide describes how to organize the work and does not describe the work.

Step 4: Test, Decide, and Follow Up

The last step turns reasoning into a decision that someone is accountable for. An investigation without a decision is a report.

Run the checks in the order the evidence supports

Order the checks by what the package already suggests, and run each under the approved procedures. Record the result of each, including the ones that excluded a hypothesis. A check that found nothing still removes a candidate.

Resist closing on the first plausible cause. A plausible cause that does not change the pattern was not the cause.

When a check cannot be made within the approved procedures, record that it was not made and why. An open item stated plainly is more useful to the next reader than a closed one that was not tested.

Record the decision, the corrective action, and the follow-up

Write the decision in plain words: what was concluded, what was changed on the aircraft or in the process, and what will show whether it worked. FAA Advisory Circular 120-79A describes a continuing analysis and surveillance system built on four activities, which are surveillance, analysis, corrective action, and follow-up. Follow-up is the activity that tends to be dropped first, because the ticket looks finished by then.

Set the follow-up date when the decision is written. A review that has a date and a name attached to it happens, and one that is left as an intention usually does not.

Check the pattern against reporting duties as well. When a removal becomes a service difficulty report covers that check, and 14 CFR §121.703 is the rule for the certificate holder.

Common Investigation Problems and How to Trace Them

These problems rarely show in one record. They show when the investigation file is read from start to finish.

Stopping at the first plausible cause

The investigation names a cause, the corrective action is taken, and the same complaint returns. Trace it by checking whether the stated cause would have produced the earlier removals as well. If it would not, the cause explains one event, not the pattern.

Closing the investigation when the unit is replaced

A new serial number on the position closes the ticket and leaves the question open. Trace it by looking at whether the file records a change to the aircraft or the process, or only a change to the unit.

Replacing the unit is an action. It is not a conclusion, and a file that stops there has not answered the question it opened with.

Evidence discarded before anyone read it

Replaced parts, deposits, and as-received findings are lost when units are cleaned and repaired on the normal schedule. Trace it by asking, for each earlier removal, which evidence still exists. Where none does, the investigation has to say so.

A record that states what was lost is still evidence. It tells the next investigation which gaps were already known and which holds should be placed earlier.

Warning Signs of a Minimum-Standard Approach

A minimum-standard approach opens an investigation to satisfy a requirement and closes it when the paperwork is complete. These signs show it.

  • No named owner, or an owner who does not see the shop record.
  • No written trigger, so each pattern is judged on instinct.
  • The question names the unit instead of the complaint.
  • The shop is asked to repeat the test and not to explain the finding.
  • Hypotheses are listed only about the unit.
  • Checks are chosen after the first result is seen.
  • The file ends with a part number change and no follow-up date.
  • The shop is blamed for the pattern before the history has been read.

A file that shows several of these signs documents activity, not understanding. None of them needs new software to fix.

Expected Outcome: A Defensible Repeat Removal Investigation

The outcome is a file that another person can read and follow from trigger to decision. It shows who owned the question, what evidence was gathered and where it came from, which causes were considered, which were excluded and how, and what will be checked later.

The program does not guarantee that the pattern stops. It guarantees that the next removal, if it happens, is an event in a record that can explain it. For general reasoning about cause in maintenance, see root cause analysis in aircraft maintenance, and for how repeat removals affect aircraft downtime, see downtime and its causes on the ground.

Start with the part number. If the unit is an air cycle machine such as the Boeing 747 ACM 774469-4, that number ties the history, the findings, and the checks to one set of manufacturer data. The published capabilities by aircraft and component type show which part numbers sit in the scope AeroKool Aviation publishes, and a part number outside the published list is a question to ask, not an assumption to make.

The published programs page lists repair and overhaul, PMA and DER, manufacturing, engineering, and repair management and logistics. The contact form is where the part number and the removal history go.

Frequently Asked Questions

What is a repeat removal investigation?

It is the structured work of finding out why the same fault keeps returning to an aircraft, with a named owner, an evidence package, a set of hypotheses, and a closing decision. None of the sources cited in this guide defines the term, so an organization using it should say in writing what opens one.

Who should lead a repeat removal investigation?

For a Part 121 certificate holder, the operator, because 14 CFR §121.363 leaves primary responsibility for airworthiness with it even when another person performs the maintenance. The repair station contributes its records and findings. Outside Part 121, confirm the allocation in your contract.

When should an investigation start?

When the pattern meets the trigger the operator wrote down in advance. FAA Advisory Circular 120-79A gives 10 to 15 days only as an example for chronic write-ups, not as a rule, so the threshold is the operator’s own choice.

What evidence does an investigation need from the repair station?

The teardown report, the test record, the manufacturer data the tests were run against, the calibration status of the equipment, and a statement of what was not examined. The shop should also receive the removal history, because it cannot read a pattern it has not been shown.

How is a repeat removal investigation different from troubleshooting?

Troubleshooting looks for the fault on one aircraft on one day, and an investigation looks for the pattern across removals, units, and shops. It has an owner, a written question, and a decision that is checked later. A repair can end troubleshooting, but only a change that stops the pattern can end an investigation.

Does the investigation end when the unit is replaced?

No. Replacing the unit is an action, and the investigation ends when the file shows what was concluded and how the follow-up will confirm it. If the cause stayed on the aircraft, the next unit will inherit it.

A repeat removal investigation is finished when someone can say what changed on the aircraft, not what changed on the tag. If the file cannot show the evidence, the causes excluded, and the follow-up, the investigation has repeated the repair under a different name.

About AeroKool Aviation. AeroKool Aviation is an FAA-certificated repair station in Hialeah, Florida, specializing in the repair and overhaul of environmental control system components — air cycle machines, cooling turbines, heat exchangers, refrigeration packages, valves and environmental control units — for commercial, regional, business jet, rotorcraft and military operators. The company was founded in 1959 and holds AS9110C and AS9100D registrations, with in-house PMA parts manufacturing and FAA DER repair engineering. Read more in the company profile.

This article is general technical information about how investigations of repeat removals of aircraft environmental control system components are organized and documented. It is not approved data, it is not a maintenance procedure, and it does not replace the component maintenance manual, structural repair manual, service bulletin, airworthiness directive or other airworthiness data your organization is approved to use. Regulations, standards and manufacturer data are revised, and the requirements that apply to a specific job depend on the part number, the aircraft, the operator’s approved program and the scope of the repair station’s certificate. Verify the applicable requirements against the current manufacturer data, your own quality system, your operator’s continuing analysis and surveillance system, and your FAA principal inspector or EASA competent authority before performing or accepting any maintenance action.

Talk to AeroKool Aviation

AeroKool Aviation is an FAA-certificated repair station in Hialeah, Florida, overhauling air cycle machines, cooling turbines, heat exchangers, valves and environmental control units for commercial, regional, business and military operators since 1959, with an AS9110C quality system and in-house PMA and DER engineering. If you have a component on the bench, a repeat removal you cannot explain, or a part number you cannot source, we will tell you what falls inside our ratings and what does not.

Address
1495 S.E. 10th Avenue Hialeah, FL 33010-5984

eMail
aerokool@aerokool.com | sales@aerokool.com

Phone
305.887.6912 | 800.458.4255

Scroll to Top

Have Questions Or Need Information?

Please fill out the form below to contact us and we will get back to you as soon as possible.
Request a Quote
Choose one for Sales and Repair Services
We're committed to your privacy. AeroKool Aviation uses the information you provide to us to contact you about our relevant content, products, and services. You may unsubscribe from these communications at any time. For more information, check out our Privacy Policy.

Looking for parts?

You can search by Part Number or Aircraft Model

Search for Parts

Browse our extensive inventory

Note: You can search by part number

Your Aircraft

Browse our extensive inventory

Note: You can search by aircraft name