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
An original diagram from air-data/inertial/GPS/radio sensors to ADIRU/FMC processing and consumers such as MDS, DFCS, ATC/ADS-B and TCAS.
Source data is drawn separately from consumers
The visual keeps sensors/ADIRUs/FMC on the left and the systems that consume their outputs on the right.
One bad source can create many messages
Because several consumers share air-data/inertial/navigation outputs, common-mode symptoms should trigger an upstream-data hypothesis.
Use the map with ATA 22 and 31
Autoflight and display-system resources are linked because those chapters consume and present ATA 34 data.
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.
