Educational familiarization only. This TechOpsBase resource is an original learning transformation grounded in a privately supplied B737 MAX ATA 34 source. It does not reproduce manufacturer task steps, limits, figures or controlled maintenance instructions. Current approved data and aircraft effectivity control real work.
What this resource teaches
See how surveillance and navigation-computation functions depend on air-data, inertial, GPS and display systems.
TCAS is an integrated consumer and producer of traffic information
The chapter includes TCAS computer/antenna functions and tests that depend on air-data, ATC, common display and radio-altimeter serviceability. That dependency list is a powerful systems-engineering lesson.
ATC/ADS-B combines identity, altitude and position-related data
ATC/transponder testing references air-data sources, GPS visibility and flight-management inputs. A surveillance complaint can therefore originate in several upstream data providers.
FMCS is the navigation-computation layer
The chapter includes FMC computers and CDUs. The FMC uses navigation source data and route/performance inputs to create guidance consumed by displays and autoflight.
Cross-ATA interfaces are the rule
ATA 22 DFCS, ATA 31 MDS and ATA 34 ADIRS/ATC/FMCS appear together in system tests. Avoid diagnosing an integrated avionics symptom by ATA number alone.
Evidence strategy
Identify which data item is wrong, list every producer and consumer of that data, compare independent sources, then use approved test/fault-isolation data to narrow the interface.
Put this topic into the wider system
Independent sources are valuable comparators
Left/right ADIRUs, radio sources and GPS-supported functions create opportunities to compare independent information. Agreement between independent sources strengthens confidence; disagreement helps identify which data chain deserves approved testing.
Validity matters as much as availability
A navigation computer or sensor can be powered and communicating yet provide data that is invalid for the current state. Alignment, source selection and built-in tests are ways the aircraft establishes or checks validity—not merely whether a box is switched on.
Deeper system reasoning
Navigation integration makes cross-ATA reasoning mandatory
ATC/ADS-B tests depend on DFCS, ADIRS, ILS, ATC and FMCS; TCAS tests depend on air data, ATC, display and radio-altimeter serviceability. ADIRS tests also reference equipment cooling and MDS. These relationships demonstrate why integrated-avionics symptoms do not respect one ATA boundary. Map producers, processing, buses and consumers, compare independent sources, then hand off to the approved IFIM/WDM/test procedure.
Technician evidence matrix
Record the specific data item that is wrong, left/right source comparison, ADIRS/alignment/source validity, GPS/radio availability and which consumers show the same symptom.
Before using a maintenance message as a conclusion, note what independent evidence agrees with it and what evidence does not. If an alternate source, channel or display changes the symptom, record that explicitly because it can separate a common path from a source-specific path. Preserve configuration and event conditions in the handover so the next technician does not have to rebuild the diagnostic context from memory.
Evidence-first study method
For any system complaint, separate source/input, control logic, physical response, sensing/indication and consumer/result. When two layers disagree, that disagreement is useful evidence. Do not turn that evidence into a maintenance action until the applicable approved fault-isolation or maintenance data is open.
Approved-data boundary
Educational system explanation only. Do not use this page to perform maintenance, operate aircraft systems, isolate components or determine dispatch status. Current approved maintenance data, aircraft effectivity and operator procedures control real aircraft work.
