4.3 Instructions for Continued Airworthiness and Systematic Troubleshooting

4.3 Instructions for Continued Airworthiness and Systematic Troubleshooting

Core Aviation Standard: Installing advanced avionics is only the first step in a system's lifecycle; maintaining continued airworthiness requires comprehensive technical instructions and disciplined diagnostic methodologies. Under 14 CFR 21.50(b), holders of a type certificate or STC must furnish Instructions for Continued Airworthiness (ICA) so that the product or alteration can be kept airworthy. When complex integrated avionics fail, technicians must reject uncoordinated trial-and-error box swapping in favor of deductive, systematic troubleshooting anchored by verified technical data.

Modern aircraft integrate digital databuses, software-configurable sensors, and multi-display flight decks. Isolating intermittent faults within these interconnected architectures demands a firm grasp of regulatory technical data classifications and rigorous deductive diagnostic techniques.

---

Instructions for Continued Airworthiness (ICA)

Under the airworthiness standards (§ 23.1529 with Part 23 Appendix A, § 25.1529 with Part 25 Appendix H, and §§ 27.1529 and 29.1529 for rotorcraft), an applicant for a type certificate must prepare Instructions for Continued Airworthiness (ICA) acceptable to the Administrator, and 14 CFR 21.50(b) requires TC and STC holders to furnish them to owners. The ICA document provides all maintenance instructions necessary to keep the alteration or appliance in an airworthy condition throughout its operational life.

               INSTRUCTIONS FOR CONTINUED AIRWORTHINESS (ICA) STRUCTURE:

 +-------------------------------------------------------------------------+
 | SECTION 1: SYSTEM INTRODUCTION & SERVICING                              |
 | System description, physical layout, power requirements, cleaning      |
 +-------------------------------------------------------------------------+
 | SECTION 2: MAINTENANCE MANUAL & WIRING DIAGRAMS                         |
 | Removal/installation procedures, pinouts, interconnect schematics       |
 +-------------------------------------------------------------------------+
 | SECTION 3: SCHEDULED INSPECTIONS & CALIBRATIONS                         |
 | Recommended inspection intervals, functional ramp checks, BIT procedures|
 +-------------------------------------------------------------------------+
 | SECTION 4: AIRWORTHINESS LIMITATIONS SECTION (ALS)                      |
 | *** MANDATORY COMPLIANCE BY LAW (14 CFR § 43.16 & § 91.403(c)) ***      |
 | Mandatory component retirement lives, mandatory structural checks.      |
 | Must be explicitly approved by the FAA Aircraft Certification Office.   |
 +-------------------------------------------------------------------------+

The Four Primary ICA Sections

1. System Description & Servicing: Physical locations of LRUs, weight and balance data, access panel locations, lubrication specifications, and operational limitations.
2. Maintenance Manual & Electrical Interconnects: Step-by-step removal and replacement procedures, wiring schematics, connector pin assignment tables, and antenna sealing instructions.
3. Scheduled Inspections & Troubleshooting: Recommended inspection frequencies (e.g., inspecting remote magnetometer mounts every annual inspection), built-in test (BIT) error code catalogs, and ramp testing procedures.
4. Airworthiness Limitations Section (ALS): Contains mandatory replacement intervals, structural fatigue life limits, and mandatory inspection requirements.

---

Approved Technical Data vs. Acceptable Technical Data

In aviation maintenance, technical data is divided into two distinct legal tiers. Using the incorrect tier of data to substantiate a maintenance action can invalidate an aircraft's Certificate of Airworthiness.

The Common Pitfall: AC 43.13-1B Misuse

A common misconception among technicians is that FAA Advisory Circular AC 43.13-1B (Acceptable Methods, Techniques, and Practices) constitutes approved data for any modification. AC 43.13-1B is strictly acceptable data.

For example, an avionics shop installing a new weather radar radome cannot cite AC 43.13-1B alone on Form 337 Block 8 as the sole engineering substantiation for cutting an aircraft pressure bulkhead. Cutting a pressure bulkhead is a major alteration that requires approved data—such as a manufacturer STC or an FAA Form 8110-3 signed by an authorized Designated Engineering Representative (DER).

---

Systematic Avionics Troubleshooting Methodologies

When modern avionics malfunction, inexperienced technicians often resort to "shotgun troubleshooting"—swapping expensive LRUs into the rack one by one in the hope of resolving the squawk. This practice wastes shop hours, risks damaging sensitive donor boxes, and fails to identify harness or power flaws.

Disciplined technicians employ a structured six-step deductive diagnostic methodology:

                  THE SIX-STEP SYSTEMATIC TROUBLESHOOTING CYCLE:

  +-------------------------+
  | 1. VERIFY THE SYMPTOM   |  --> Replicate squawk on ground / verify flight conditions
  +------------+------------+
               |
               v
  +-------------------------+
  | 2. SCHEMATIC ANALYSIS   |  --> Trace power distribution, ground loops, databuses
  +------------+------------+
               |
               v
  +-------------------------+
  | 3. HALF-SPLIT ISOLATION |  --> Test midpoint of linear circuit; eliminate 50% domain
  +------------+------------+
               |
               v
  +-------------------------+
  | 4. POWER & GROUND TEST  |  --> Measure bus V under load; verify ground bond <= 0.003 Ohm
  +------------+------------+
               |
               v
  +-------------------------+
  | 5. INPUT VS OUTPUT TEST |  --> Check sensor input excitation before condemning LRU
  +------------+------------+
               |
               v
  +-------------------------+
  | 6. CORRECT & VALIDATE   |  --> Repair wiring/pin; perform ramp test & return-to-service
  +-------------------------+

1. Verify the Symptom / Squawk

Begin by interviewing the flight crew or reading the exact squawk description. Do not assume the pilot's technical diagnosis is correct—focus on the observable symptom (e.g., "Autopilot pitch trim ran down uncommanded during flap extension"). Verify the fault using aircraft power or an external Ground Power Unit (GPU).

2. Isolate Input vs. Output vs. Internal LRU Fault

An avionics component requires three basic elements to function: clean electrical power, valid sensor inputs, and an uncompromised output path:

• If an engine display shows an erroneous cylinder head temperature (CHT) of 999°F, test the input thermocouple millivolt signal directly at the display rear connector.
• If the thermocouple input voltage corresponds correctly to ambient engine temperature, but the display continues to show 999°F, the fault is internal to the display processor.
• If the thermocouple input voltage is open-circuit ($0.0\ \text{mV}$ or infinite resistance), the fault lies externally in the probe or airframe wiring.

3. The Half-Split (Split-Half) Isolation Technique

In complex multi-stage circuits, long harness runs, or multi-junction data lines, checking every terminal connection sequentially from start to finish is highly inefficient. The half-split technique is a binary search algorithm applied to physical electronics:

• Select a test point at the physical or electrical midpoint of the system.
• Measure signal presence and quality.
• If the signal is normal at the midpoint: The upstream half of the system (transmitter and upstream harness) is proven functional. The fault domain is reduced by 50%, and subsequent tests focus strictly on the downstream half.
• If the signal is missing or abnormal at the midpoint: The fault is located in the upstream half. The technician immediately tests the midpoint of the upstream segment.
• Mathematically, testing by half-split resolves a fault in a system with $N$ stages in only $\log_2(N)$ test steps, compared to an average of $N/2$ tests using sequential tracing.

4. Power and Ground Verification: The Golden Rule

A large share of LRUs removed as "failed" test No Fault Found (NFF) at the repair depot. Many of these phantom failures trace back to degraded power connections or high-resistance ground returns in the aircraft.

• Voltage Under Load: Measuring 28.0 VDC with the connector disconnected (open-circuit) is meaningless. A high-resistance corroded crimp pin can show full supply voltage when unloaded, but will drop to 12 VDC the moment the LRU attempts to draw operational current. Back-probe the connector while the system is energized.
• Ground Bond Verification: AC 43.13-1B paragraph 12-9 describes proper avionics bonding as on the order of $0.003\ \Omega$ and says the equipment manufacturer specifies the bonding requirement; paragraph 11-189 limits each bonding-jumper connection to 0.003 Ω. A floating ground creates ground offset voltages, injects 400 Hz AC alternator whine into audio panels, and corrupts digital serial communication.

---

Post-Maintenance Testing, Ground/Ramp Validation, and Flight Checks

Following any avionics repair or installation, the technician must execute a formal validation hierarchy before signing the return-to-service entry.

                    POST-MAINTENANCE VERIFICATION HIERARCHY:

 [STAGE 1] UNPOWERED WIRE CHECKS:
           - Continuity, insulation resistance (manufacturer's limit)
           - Coax checks; bonding resistance (~0.003 Ohm)
                                |
                                v
 [STAGE 2] INITIAL POWER-UP & BITE VALIDATION:
           - Bus voltage under load; verify Built-In Test (BIT) clear
           - Check software part numbers and configuration checksums
                                |
                                v
 [STAGE 3] RAMP & FLIGHT-LINE TEST SET VERIFICATION:
           - Simulated RF interrogation using IFR/Aeroflex test sets
           - Transponder frequency (+-3 MHz), power, Mode S, ADS-B Out payload
           - Pitot-static simulated altitude leak check per Part 43 App E
                                |
                                v
 [STAGE 4] OPERATIONAL FLIGHT CHECK (14 CFR § 91.407):
           - Mandatory if flight characteristics appreciably affected
           - Flown by pilot; logged in aircraft maintenance records

14 CFR § 91.407 Operational Flight Checks

Under 14 CFR § 91.407(b), no person may carry any person (other than crewmembers) in an aircraft that has been maintained, rebuilt, or altered in a manner that may have appreciably changed its flight characteristics or substantially affected its operation in flight, until:

1. An appropriately rated pilot with at least a private pilot certificate flies the aircraft.
2. The pilot makes an operational check of the maintenance performed or alteration made.
3. The pilot logs the flight in the aircraft records.

Under § 91.407(c), the flight is not required if ground tests, inspection, or both show conclusively that the work has not appreciably changed the flight characteristics or substantially affected flight operation. Separately, § 91.407(a) requires the approval for return to service (§ 43.7) and the § 43.9 or § 43.11 record entry before any operation.

Avionics alterations that typically mandate an operational flight check include: installing an integrated autopilot system interfaced to flight controls, retrofitting a primary flight display (PFD) that replaces primary mechanical attitude instruments, or major alterations to stability augmentation systems.

---

Avionics Shop Worked Scenario: Systematic Diagnosis of an MFD "TRAFFIC FAIL"

Scenario: A multi-engine aircraft arrives with a recurring squawk: the center Multi-Function Display (MFD) displays an amber "TRAFFIC FAIL" annunciation intermittently during climb-out, disabling the onboard TCAS/ADS-B In traffic display.

Step 1: Symptom Verification & BITE Interrogation

• Connect external 28 VDC GPU and power up avionics.
• Access MFD maintenance diagnostic menu. BITE log displays fault code: ERR 2340: LOSS OF ARINC 429 CH 2 DATA FROM GTS-800 TRAFFIC PROCESSOR.

Step 2: Half-Split Isolation on Data Line

• The GTS-800 traffic processor is located in the aft avionics bay at Station 240. The MFD is in the cockpit instrument panel at Station 50. The total wiring run is 30 feet, passing through an intermediate production disconnect terminal block (TB102) located under the mid-cabin floorboard at Station 145.
• Technician Action: Split the system at TB102. Connect an ARINC 429 portable bus analyzer (e.g., Datatracker) to pins 3 and 4 of TB102 (input side from GTS-800).
• Result: Normal ARINC 429 high-speed traffic labels are actively received with valid parity and normal +10V / -10V BPRZ pulse amplitudes.
• Deduction: The GTS-800 processor and the entire 16-foot aft harness segment are operating flawlessly. The intermittent fault domain is isolated to the 14-foot forward harness between TB102 and the cockpit MFD.

Step 3: Power, Ground, and Physical Harness Inspection

• Technician inspects the forward harness from TB102 toward the cockpit.
• Under an Adel cushion clamp adjacent to the main cabin heat duct, the technician discovers mechanical harness pinching. The outer ETFE insulation of the shielded twisted pair had cold-flowed against the clamp edge.
• Multimeter continuity check under harness flex reveals an intermittent short between the ARINC 429 Channel 2 'A' conductor and its shield, which is grounded to structure.

Step 4: Repair, Environmental Splice, and Return to Service

• Cut out the damaged 2-inch segment of shielded twisted pair.
• Splice the shielded data cable only by a method the aircraft or equipment manufacturer's data allows (AC 43.13-1B paragraph 11-167 requires approved data to splice multiplex bus wiring), staggering the individual conductor splices.
• Restore the outer braided shield using a solder sleeve terminator tied to ground.
• Re-clamp the harness with a correctly sized MS21919 cushion clamp, routed away from the heat duct (AC 43.13-1B paragraph 11-124).
• Re-test ARINC 429 bus integrity with analyzer; confirm zero frame errors during harness wiggle testing.
• Make the 14 CFR § 43.9 maintenance record entry, referencing the aircraft maintenance manual's standard-practices chapter and AC 43.13-1B.