Defect Investigation (DI) on a Military Aero Engine

Defect Investigation (DI) on a Military Aero Engine: How It Is Carried Out on the Adour Mk 811 of the Jaguar

Introduction: When the Aircraft Tells You Something Is Wrong

A pilot walks in after a sortie and says, quietly, "The left engine felt a bit lazy on the throttle push." There is no warning light, no exceedance, and nothing on the gauges. Many people would shrug. An experienced engineer does not, because that sentence is the start of a Defect Investigation.

Early in my career, my senior used to say, "A scheduled inspection finds what you expect. A defect investigation finds what you didn't." After decades around military engines, I still think that is the best one-line description of the work.

In this article, I will explain how a Defect Investigation (DI) is approached on the Rolls-Royce/Turbomeca Adour Mk 811, the turbofan that powers the upgraded SEPECAT Jaguar in Indian Air Force service, with engines manufactured and overhauled under licence by HAL. I will cover the logic, methods, common defects, documentation, human factors, and how technology is changing the work. Students, technicians, enthusiasts, and young engineers should all be able to follow it.

What Is a Defect Investigation?

A Defect Investigation is a structured, evidence-based process to find the root cause of a reported or observed abnormality in an aircraft or engine, rectify it as per approved data, and prove that the fault is gone before the aircraft flies again.

It is different from routine servicing in several ways:

Aspect	Scheduled inspection	Defect Investigation
Trigger	Time, flying hours, or calendar	A symptom, report, or observation
Scope	Fixed task list	Defined by the problem
Outcome	Serviceable or defects found	Root cause identified, rectified and cleared
Skill emphasis	Thoroughness and discipline	Diagnostic reasoning and judgment
Risk	Missing something	Treating the symptom instead of the cause

What triggers a DI?

Pilot-reported snags (abnormal sound, vibration, slow acceleration, throttle response, warning lights)
Cockpit indication discrepancies (temperature, RPM, fuel flow, oil pressure)
Findings during servicing (leaks, chafing, damage)
Chip detector or oil analysis alerts
Events such as bird strike, suspected FOD ingestion, hot start, surge, flame-out or over-temperature
Trend data showing gradual degradation
Fleet-wide alerts or service bulletins

A Brief History: From Instinct to Evidence

Early jet-engine troubleshooting was mostly instinct. Experienced fitters listened to the spool-up, read the colour of exhaust staining, felt the vibration through the airframe, and relied on a handful of gauges. Many problems were found only after hardware had failed.

The Adour came out of the Anglo-French Jaguar program in the late 1960s and 1970s. Its modular design was an important step: a team could isolate a fault to a module or accessory and replace it without sending the whole engine to depot. The Jaguar, a low-level strike aircraft, also subjected its engines to heavy thermal and ingestion loads, which taught the industry a great deal about reheat durability, compressor erosion and FOD.

Since then, practice has changed in several ways:

Borescopes progressed from dim rigid scopes to high-resolution video probes.
Spectrometric oil analysis and chip detection became standard tools.
Recorded engine parameters let engineers look back at what the engine did, not just what the pilot remembered.
Reliability programmes connect individual defects across the fleet.
The Mk 811 and DARIN upgrade era brought modernised systems and updated maintenance practices to the Indian Jaguar fleet.

Each step in a modern DI procedure tends to exist because some earlier failure taught a lesson, often a painful one.

Know the Engine You Are Investigating

You cannot investigate a defect on an engine you do not understand. The Adour is a twin-spool, low-bypass turbofan with reheat (afterburner). The Jaguar has two of them, and each must be treated as an individual.

Engine section	Function	Typical defect symptoms
Intake and ducting	Delivers airflow	FOD evidence, distortion, loose items
LP compressor (fan)	Initial compression and bypass	Blade damage, vibration, performance loss
HP compressor	Main compression	Surge or stall, slow acceleration, high temperatures
Combustion section	Burns fuel	Hot spots, uneven temperatures, hot starts
HP and LP turbines	Drive the compressors	High jet pipe temperature, vibration, performance loss
Reheat section	Adds thrust	Failure to light, rough light-up, flame-out, liner damage
Accessory gearbox and drives	Power pumps and generators	Leaks, noise, chip detector indications
Fuel and control system	Meters fuel, schedules the engine	Throttle response issues, hunting, trimming problems
Oil system	Lubricates and cools	Pressure fluctuation, consumption, contamination
Bleed and air systems	Services and cabin systems	Leaks, pressure issues

The cause of a symptom is often not where the symptom appears. A high temperature indication might come from a compressor problem, a control problem, a sensor problem or a real thermal issue. This is why disciplined diagnosis matters.

The DI Process: A Step-by-Step Approach

The actual sequence in your organisation is governed by approved manuals and orders. What follows is the logic that underlies them.

Step 1: Receive and Understand the Defect

Everything depends on the quality of the initial report.

Read the exact wording of the snag as recorded.
Debrief the pilot directly where possible. Ask open questions: When did it occur? At what power setting, altitude, speed or phase of flight? Was it steady or intermittent? What did the instruments show? Was there a sound, smell or vibration? Did it affect both engines?
Note whether the report is engine-specific, system-related or an indication-only issue.

A vague report like "engine problem" is useless. The first job is to sharpen it. In my experience, a good five-minute conversation with the pilot has saved hours of unnecessary work.

Step 2: Review History and Records

Before touching anything, study the paper trail:

Previous similar defects on this aircraft and engine
Recent component replacements, repairs or modifications
Engine operating hours and cycles, and the module or component life status
Previous oil analysis, chip detector findings and borescope results
Outstanding service bulletins or fleet alerts
Recent events such as bird strike, hot start or over-temperature

Recurring defects are a warning. If the same snag has been "fixed" three times, the cause has not been found.

Step 3: Safety Precautions and Initial Assessment

Ensure the aircraft is safe: ground safety devices, fire protection, no personnel near intakes or exhaust, and ground power arrangements as required.
Decide whether the defect is flight-safety critical, which means the aircraft is grounded and quarantined until cleared.
Carry out a visual assessment before anything is disturbed. Do not wipe away evidence. A fresh leak trail, a scorch mark, or a film of oil is a clue.

Step 4: Preliminary Checks

Many defects have simple causes, and a good investigator rules out the simple causes first, systematically rather than hopefully.

Visual inspection of the engine bay, pipes, connectors and fasteners.
Intake and compressor inspection for FOD or damage.
Exhaust and reheat inspection for liner damage, discolouration or cracking.
Fluid levels and condition: oil and fuel.
Electrical connectors and harness security, especially for indication faults.
Filters and chip detectors: inspect and record.

Step 5: Fault Isolation

This is the real intellectual work of the DI. The fault-finding procedures in the manual guide you, but your reasoning has to fill the gaps. The approach is:

List possible causes based on the symptom.
Rank them by likelihood and ease of checking.
Test one thing at a time, so that changes can be attributed.
Record each result, including negative findings.
Narrow down to a component, module or system.

Typical tools and methods include:

Ground run under controlled conditions, to reproduce the defect and observe parameters.
Instrument and sensor checks to separate a real engine problem from an indication problem.
Fuel system and control checks, including throttle linkage and trimming checks as per the manual.
Borescope inspection to examine internal components without teardown.
Oil sampling and analysis and chip detector examination.
Vibration checks where a vibration complaint is involved.
Leak checks on pressurised systems, including bleed air.
Comparison with the other engine, a surprisingly effective technique on a twin-engine aircraft.

Step 6: Identify the Root Cause

A symptom is not a cause. "Replaced the fuel control unit" is an action. "Fuel control unit output erratic due to internal wear confirmed on test" is a finding.

Ask three questions:

Does the identified cause explain every symptom?
Does it explain why the defect appeared when it did?
If I fix it, what evidence will prove it is fixed?

If the answers are not clear, you may have found a contributing factor and not the root cause.

Step 7: Rectification

Rectify strictly per approved data: manuals, approved repair schemes, or authorised technical instructions.
Use the correct parts, tools and consumables, with full traceability.
Where a module or major component is replaced, follow the associated procedures for installation, rigging, adjustment and any required checks.
Apply independent inspection to critical tasks.
Quarantine and tag the removed unit, along with all relevant data, so that the depot or manufacturer can carry out a proper teardown.

Step 8: Verification and Clearance

A defect is not cleared because a part was changed. It is cleared when the fault is proven absent.

Carry out the required post-rectification checks and ground run, observing all parameters.
Compare behaviour with the healthy engine and with the baseline.
Where the manual requires, arrange a flight test or check flight.
Only authorised personnel may certify clearance.

Step 9: Documentation and Reporting

Record the defect, investigation steps, findings, rectification, parts used and tests carried out.
Report to higher-level authorities where a defect is significant, recurring or potentially fleet-wide.
Ensure data is available to reliability and trend monitoring teams.

Common Engine Defects and What They Usually Point To

These are general patterns seen in turbofan engines of this class. They are not definitive diagnostic rules, so always follow the manual.

Reported symptom	Possible areas to investigate	Why it matters
Slow acceleration or throttle response	Fuel control, linkage and trimming, compressor condition, bleed system	Safety in critical flight phases
Compressor surge or stall indications	Compressor damage or erosion, FOD, airflow distortion, fuel scheduling	Can lead to loss of thrust and damage
High temperature indication	Sensor or harness fault, combustion issues, turbine deterioration, performance loss	Thermal damage to hot-section parts
Reheat failure to light or rough light	Ignition, fuel supply to reheat, controls, liner or flame holder condition	Mission capability and possible flame-out
Oil pressure fluctuation	Oil pump, filters, scavenge system, sensors, leaks	Risk of bearing damage
Chip detector indication	Bearing or gear wear, accessory gearbox	Possible impending component failure
Abnormal vibration	Blade damage, imbalance, bearing wear, loose components	Mechanical failure risk
Fuel or oil leak	Seals, unions, chafed lines, housings	Fire hazard and system degradation
Engine does not reach expected performance	Compressor erosion, control scheduling, turbine wear, air leaks	Operational capability
Hot start or over-temperature event	Starting system, fuel scheduling, ignition, conditions at start	Possible hot-section damage requiring assessment

The QA/QC Engineer's Perspective

After many years across manufacturing and inspection, I see the DI as a test of whether a quality system really works under pressure.

Process control

Defects tempt people to improvise. A quality system keeps the investigation inside a controlled framework: approved procedures, calibrated tools, qualified people, recorded results.

Documentation and traceability

A good DI record answers these questions without anyone needing to ask:

What was the reported symptom, and who reported it?
What was checked, in what order, and with what result?
What was found, and what was the confirmed root cause?
What was done, with which parts (part and serial numbers), by whom, under what authority?
How was the fix verified?

Auditors often say: "If it isn't documented, it wasn't done." I would add that if it is documented badly, it might as well not have been done. "Found loose, tightened" is not an investigation record.

Non-conformance and root cause

A repeated defect is a systemic signal, not an individual failure. Quality practice requires root-cause analysis and corrective and preventive action, not just replacing the part again.

Calibration and tool control

Test equipment, gauges, torque tools and borescopes must be in calibration. An out-of-calibration instrument can create a false defect or hide a real one.

Independent inspection

Critical rectification, such as control linkages, engine mounting and anything involving flight safety, needs a second set of eyes. That is not distrust. It reflects the fact that people make mistakes.

Audit considerations

Expect auditors to examine:

Authorisation and training records of investigators
Use of current, controlled manuals
Handling and closure of repetitive defects
Part quarantine, tagging and traceability
Whether the clearance evidence supports the clearance given
Whether defect trends were analysed or just closed one by one

Lessons from production

A defect found at component inspection is cheap, one found at assembly is costly, and one found in flight can be catastrophic. A DI is the last line before the flight, and it works best when earlier lines (production quality, overhaul quality, servicing discipline) did their jobs.

The Maintenance Engineer's Perspective

Line vs base level

Line level investigators work close to the aircraft, under time pressure, and are often the first to see the symptom. They carry out initial checks, simple rectification and decide what needs escalation.
Base or depot level has specialised test facilities, deeper teardown capability and manufacturer-supported analysis.

The best organisations keep communication open in both directions. Line crews supply the observations and depot teams supply the findings. I have seen an engine problem solved faster because someone on the flightline had written one clear line in the defect record.

Troubleshooting in practice

A scenario I have seen in different forms: a pilot reports a delayed reheat light on one engine. Everything looks normal on the ground. A less experienced technician might replace the igniter, find the engine lights, and close the defect. A more careful investigator will:

Check the history for similar reports.
Examine the ignition components and wiring.
Inspect the reheat fuel system, filters and connections.
Check control settings per the manual.
Compare with the other engine.
Run the engine and watch parameters carefully.

The fault may well be the igniter. But the method makes sure you know that, instead of hoping.

The "no fault found" problem

The most frustrating defect is the one that cannot be reproduced on the ground. Intermittent faults often come from vibration-sensitive connectors, chafed wiring, or conditions found only in flight. The temptation is to write "NFF, released." A good engineer instead:

Looks for patterns in time, conditions and flight phase.
Checks recorded data for evidence.
Applies targeted monitoring on the next flights.
Escalates if the defect recurs.

Human factors

Confirmation bias: deciding on the cause early, and then seeing only what supports it.
Time pressure: the aircraft is needed, so the investigation gets shortened.
Fatigue: especially during night work or long recovery operations.
Poor handover: half-finished investigations passed between shifts with incomplete information.
Normalisation of deviance: gradually accepting small anomalies as normal.

A disciplined DI process pushes back on all of these.

Operational realities

Military aircraft operate in dust, heat, humidity and salt air, and at forward bases with limited facilities. Each environment shows up in different defects: dust and erosion, corrosion, seal ageing, fuel contamination. An investigator who knows the operating environment starts with better hypotheses.

Case Study: The Defect That Looked Like an Instrument Problem

This is a composite scenario representing the kind of case engineers encounter.

A Jaguar returned with a report of a slightly high temperature indication on one engine at cruise power, within limits but noticeably different from the other engine. The ground run showed nothing unusual. The first suspicion was the temperature sensing system, and a thermocouple harness check found a connector with signs of heat discolouration.

A technician might have replaced the harness and signed it off. Instead, the investigator asked whether the connector was the cause or the victim. Further checks, including a borescope inspection, showed early signs of uneven combustion patterns that explained a localised hot area near the connector. The harness was a casualty. The real problem was upstream, and replacing the harness alone would have left the engine to continue running hot in that region.

The lesson: always ask whether the thing you found explains the whole story. A fix that treats only the symptom is a delay, not a solution.

Comparison: Older and Modern Investigation Approaches

Aspect	Traditional	Modern
Information source	Pilot memory, gauges	Recorded data, trend analysis
Internal inspection	Often teardown	Video borescope, image records
Oil monitoring	Limited	Routine spectrometric analysis and trending
Fault finding	Experience-based	Experience plus structured fault trees and data
Records	Paper-based	Digital with traceability
Learning	Local knowledge	Fleet-wide reliability and shared defect data
Maintenance decisions	Fixed intervals	Increasingly condition-informed

Manual vs automated: Automation provides consistency and volume of data. People provide judgment, context and creativity. Data points to where to look. A competent human decides what it means.

Military vs civil: Civil operators like Boeing and Airbus customers emphasise dispatch reliability, with defect handling guided by regulator-approved programmes and minimum equipment lists. Military operations emphasise mission readiness and may operate with more varied conditions and flight profiles, and defects can come from higher thermal and mechanical stresses. Both rely on the same principle: find the cause, fix it properly, and prove it.

Safety and Reliability: Why DI Matters

Failure modes a good DI helps prevent

Progressive compressor damage from unnoticed FOD
Bearing failure from ignored chip detector or oil trends
Fuel and oil leaks leading to fire
Control faults causing unexpected thrust behaviour
Reheat malfunctions causing overheating
Hot-section damage from unassessed over-temperature events

Preventive measures

Quality pilot debriefs and clear snag reporting
Rigorous FOD control
Oil analysis and chip detector programmes
Controlled use of approved data
Repeat-defect analysis
Training and competence assessment
A culture where reporting a doubt is rewarded and not punished

On a twin-engine aircraft like the Jaguar, the second engine provides redundancy, but it should never be treated as a reason to accept a doubtful first engine.

Future Trends

Predictive maintenance and health monitoring

Engines now record large volumes of data. Analysing trends in temperature, vibration, pressure and fuel flow can show degradation weeks before it produces a symptom. Modern civil engines on the Boeing 787 and Airbus A350 lean heavily on this, and military fleets are adopting similar principles.

Digital tools

Tablet-based fault-finding guidance and digital task cards
Image-based borescope records that can be shared with specialists remotely
Digital twins that simulate engine behaviour and ageing

AI and data analytics

Machine learning can assist in reviewing borescope images and spotting patterns across fleet data. These are decision-support tools. Accountability for airworthiness stays with qualified people.

Modern quality practices

Risk-based maintenance planning
Stronger safety management systems
Human factors training
Structured root-cause methods for repeat defects

None of this removes the need for a competent person standing at the engine, with a torch and a questioning mind.

Advice for Young Engineers

Listen first. The pilot's words are your first diagnostic tool.
Don't jump to the part. Replacing parts is not troubleshooting.
Change one thing at a time, so you know what worked.
Write down negative results. What you ruled out matters.
Never clear what you haven't proved.
Report your own errors immediately.
Keep learning. Study defect histories and talk to senior colleagues.
Respect the other engine as a reference, not a reason to relax.

Frequently Asked Questions (FAQ)

1. What does DI mean in this context?
In this context DI stands for Defect Investigation: the structured process of diagnosing, rectifying and verifying a reported or observed fault. In some organisations DI can also be used for other terms, so always check local usage.

2. How is a DI different from a scheduled inspection?
A scheduled inspection follows a fixed task list at set intervals. A DI starts from a specific symptom or finding and follows the evidence wherever it leads.

3. What engine powers the Jaguar?
Two Rolls-Royce/Turbomeca Adour turbofans. Indian Air Force upgraded Jaguars use the Adour Mk 811, with HAL involved in licence manufacture and overhaul.

4. Why is the pilot debrief so important?
Pilots experience conditions that cannot always be reproduced on the ground. Their description of when, how and under what conditions a defect occurred can cut diagnosis time significantly.

5. What is a "no fault found" (NFF) defect, and how is it handled?
It is a reported defect that cannot be reproduced during investigation. It should not be treated as closed without further effort. Investigators look at recorded data, check likely intermittent causes, and monitor the aircraft on subsequent flights.

6. Why is a ground run often part of a DI?
It allows investigators to reproduce symptoms under controlled, safe conditions and to verify that rectification has worked.

7. What role does a borescope play?
It allows internal inspection of the compressor, combustion and turbine sections without major disassembly, which is valuable after suspected FOD, bird strike or abnormal parameters.

8. What are chip detectors and oil analysis used for?
Both are early warning tools for wear in bearings and gearboxes. Metal particles and trends in oil contamination can reveal problems before they produce cockpit symptoms.

9. Who can clear an aircraft after a DI?
Only personnel who are trained, assessed and formally authorised under the applicable regulations and orders.

10. Can this article be used as an official procedure?
No. It is educational. Official procedures, limits and criteria come from the approved maintenance manuals and orders for the aircraft and engine.

Conclusion: The Cause Is Always Somewhere

After a lifetime around engines, I trust one idea above any other: a defect always has a cause, and the cause is always findable if you are patient, honest and systematic.

A Defect Investigation on an engine like the Adour Mk 811 combines technical knowledge, careful listening, disciplined troubleshooting, strong documentation and sound judgment. It also tests character. The temptation to shortcut, to guess, or to sign off a doubtful fix is always present, and it is resisted by professionals who understand that someone else will fly on their signature.

Technology will bring better data and sharper tools. But the foundation will not change: a competent, curious and honest engineer who asks one more question, runs one more check, and clears only what they have proved.

Respect the engine, respect the procedure, and respect the person who will fly it.

Disclaimer: This article is for educational and informational purposes only. It does not replace the approved Maintenance Manual, fault-finding procedures, airworthiness directives or operator and regulatory requirements.