Educational familiarization only. This TechOpsBase resource is an original learning transformation grounded in a privately supplied B737 MAX ATA 22 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 showing MCP/FMC and sensor inputs feeding FCC A/B, then guidance/autopilot/autothrottle outputs and feedback/status.
Inputs are not commands
Air-data/inertial/navigation inputs describe aircraft state; MCP/FMC selections define targets/modes. The FCC combines them.
Outputs split by function
Flight-director guidance, autopilot control and autothrottle actuation are shown as related but separate outputs.
Maintenance layer is separate
BITE/fault history is drawn as an observation layer connected to the computers, not as a direct maintenance instruction generator.
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.
