Educational familiarization only. This TechOpsBase resource is an original learning transformation grounded in a privately supplied B737 MAX ATA 36 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 connecting engine/APU/ground sources, regulation and isolation, left/right manifolds and major user systems.
The map is organized by energy flow
Sources are on the left, regulation/protection in the middle, manifold connectivity next, and users on the right.
Cross-ATA links are explicit
ATA 21, 30, 29 and 38 appear as user blocks so a learner can understand why a common pneumatic fault can produce apparently unrelated symptoms.
Use for hypothesis generation
If several user systems on one side are affected, the shared manifold/source path becomes a useful hypothesis. Approved data still controls testing and isolation.
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.
