Key Troubleshooting Principle: When a TCAS BIT fails for the transponder interface, the most likely cause is a faulty Mode S transponder or the transponder being in standby mode. The TCAS computer itself may be serviceable.
Built-In Test (BIT) Considerations
The TCAS BIT checks multiple interfaces separately:
Transponder interface BIT: Checks communication between TCAS computer and Mode S transponder
Antenna BIT: Checks TCAS antenna performance
Computer BIT: Checks TCAS processor integrity
2. Weather Radar System
System Components
The weather radar system consists of:
Receiver/Transmitter (R/T) Unit: Generates and receives RF energy
Antenna: Steerable parabolic dish with sweep and stabilization
Antenna Drive Motor: Provides azimuth sweep
Control Panel: Mode selection, gain, tilt, range
Display Interface: Data bus connection to EFIS
Operational Modes
WX (Weather): Standard weather detection mode
WX/TURB (Weather/Turbulence): Detects both precipitation and turbulence
MAP (Mapping): Ground mapping mode
TEST: Built-in test pattern verification
Antenna Tilt and Beam Position
The antenna tilt angle is critical for proper weather detection:
Tilt too high (+15°): Beam points above horizon; no ground returns on ground testing
Tilt too low: Excessive ground clutter
Proper tilt: Optimized for weather detection at cruise altitude
Weather Radar Troubleshooting Scenarios
Important Relationship: The weather radar overlay on the EFIS map requires a dedicated data bus connection between the weather radar receiver/transmitter and the EFIS symbol generator. A fault in this bus will prevent overlay display even when the radar is functioning normally.
3. Flight Management System (FMS)
System Functions
The FMS integrates navigation sensors (GPS, IRS, VOR, DME) with a navigation database to provide:
VNAV (Vertical Navigation): Vertical profile guidance including climb, cruise, and descent
Performance Management: Speed and altitude optimization
Navigation Database: Waypoints, airways, procedures, and airspace data
Navigation Database Management
The FMS navigation database is organized by cycles (typically 28-day updates). Loading an incorrect database cycle means:
The FMS will still operate normally
Waypoints, procedures, and airspace data may be incorrect or outdated
A "DB MISMATCH" message occurs only if the database is incompatible with the FMS software version
Waypoint Sequencing Logic
The FMS sequences to the next waypoint only when the aircraft has passed the current waypoint's abeam point or a defined distance from it. This is normal operation and not a failure condition.
Direct-To (DIR) Function Requirements
For a DIR function to execute successfully:
49.The waypoint must exist in the FMS navigation database
50.The waypoint must be suitable for direct-to navigation (some waypoints like holds or procedure turns are excluded)
51.GPS or other position sensors must be available for navigation
VNAV Computation Requirements
VNAV requires specific pilot-entered data:
Cruise altitude
Top of descent (TOD) point
Speed constraints at waypoints
Altitude constraints at waypoints
If these parameters are not entered or are incorrect, the FMS cannot compute a VNAV profile even though LNAV functions correctly.
FMS Troubleshooting Scenarios
4. Autopilot System
System Architecture
The autopilot system consists of:
Autopilot Computer: Processes commands and generates servo signals
Flight Director: Provides visual guidance commands on the PFD
Servo Actuators: Physically move control surfaces (pitch, roll, yaw)
Servo Clutches: Engage/disengage servo to control surface
Engage Switches: Pilot controls for autopilot activation
Mode Selectors: Altitude hold, heading select, approach, etc.
Control Loop Fundamentals
The autopilot operates as a closed-loop control system:
Error Signal: Difference between desired and actual state
Servo Command: Corrective signal to eliminate error
Gain Settings: Determine responsiveness and stability
Autopilot Failure Modes
Flight Director vs. Autopilot Relationship
The flight director and autopilot share sensor inputs but have separate output paths:
Flight Director: Generates visual commands (no physical control movement)
Autopilot: Generates physical control movement via servos
When the flight director displays correct commands but the autopilot won't engage, the fault is in the servo system, not the autopilot computer or sensors.
Approach Mode Considerations
During an autopilot approach:
Localizer capture: Requires functioning localizer receiver and antenna
Glideslope capture: Requires functioning glideslope receiver and antenna
Mode arming: Both localizer and glideslope must be armed; if approach mode isn't armed, neither will capture
5. Electronic Flight Instrument System (EFIS)
System Components
Symbol Generator (SG): Primary processor generating display symbology
Display Units (DU): Cathode ray tube or LCD screens
Display Backlight Inverter: Provides illumination for CRT displays
Data Buses: ARINC 429 or similar for data transfer
Primary Flight Display (PFD) Information Sources
Attitude: Attitude and Heading Reference System (AHRS) or Inertial Reference System (IRS)
Heading: AHRS flux valve/magnetometer
Airspeed: Air Data Computer (ADC)
Altitude: Air Data Computer (ADC)
Vertical Speed: Air Data Computer (ADC)
Failure Mode Analysis
Key Relationship: When both PFDs show the same failure (e.g., ATT FAIL), the fault is in the common source (AHRS/IRS). When only one PFD shows a failure, the fault is in the display-specific component (symbol generator or display unit).
Symbol Generator Power-Up
The symbol generator requires electrical power to operate. If it fails to power up:
108.Check the circuit breaker (most likely cause)
109.Check the power supply
110.Verify other aircraft systems are normal (to rule out general power failure)
6. Engine Indication and Crew Alerting System (EICAS)
161.Localized failures affect only one display (e.g., symbol generator failure)
162.Normal operations must be distinguished from failures (e.g., TA-ONLY mode)
163.Data bus faults can prevent system integration (e.g., radar overlay)
164.Pilot-entered data is required for some FMS functions (e.g., VNAV)
This comprehensive understanding of advanced avionics systems, their interrelationships, and troubleshooting approaches will prepare the AME to diagnose and resolve the most common system failures encountered in modern aircraft maintenance.