Educational familiarization only. This TechOpsBase resource is an original learning transformation grounded in a privately supplied B737 MAX ATA 28 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
Understand pressure sources and flow-path control as separate layers in the B737 MAX fuel system.
Boost pumps are source devices
The source set identifies forward/aft boost-pump functions for the wing tanks and left/right center-tank boost pumps. Learn them as pressure sources associated with specific storage areas.
A pump indication is not the whole system
A pump command or running state should be compared with the expected feed result. Electrical supply, pump condition, inlet fuel availability and downstream path can all affect the outcome.
Crossfeed is a path-control function
The crossfeed valve joins or separates feed manifolds. It does not itself create fuel pressure. This distinction prevents a common mental-model error.
Shutoff valves define safety boundaries
Engine/APU shutoff and related feed valves isolate fuel paths. Their exact commanded states and fire/emergency logic remain approved-data topics; the learning value is recognizing where isolation exists in the flow chain.
Use alternate sources as evidence
When approved troubleshooting allows different feed configurations, whether a symptom follows a pump/source or remains with a consumer/path is useful diagnostic evidence.
Put this topic into the wider system
Fuel safety is functional architecture
Bonding, ignition-source control, venting, configuration control and inerting are not administrative extras. They preserve the assumptions under which the tank was shown to be safe. Maintenance that disturbs those assumptions can affect airworthiness even if the fuel-feed function appears normal.
Cross-system dependencies
ATA 28 depends on ATA 24 electrical power for pumps/control, interfaces with ATA 49 for APU feed, and shares the center-tank safety objective with ATA 47. Treat these interfaces as part of the system map when symptoms appear in more than one chapter.
Deeper system reasoning
Treat storage, pressure and routing as separate layers
The fuel system becomes easier to reason about when tank quantity, pump pressure and routing are kept separate. Main and center tanks store fuel; boost pumps create feed pressure; crossfeed and shutoff/spar valves determine connectivity; engines and the APU are consumers. A pump running does not prove useful fuel reaches a consumer, and an open routing valve does not create pressure. Mapping those layers prevents one indication from being treated as a complete diagnosis.
Pump assignment and crossfeed create comparison opportunities
The supplied chapter identifies forward and aft boost pumps in each main tank plus left and right center-tank pumps, and it includes crossfeed-valve testing. That architecture provides natural comparison points: left versus right, main versus center, local feed versus crossfeed. If a symptom moves when the source/path configuration changes, that change is evidence. If the symptom remains tied to the same consumer or manifold section, the hypothesis should move accordingly.
Technician evidence matrix
Record tank quantity, expected pump/source, valve/manifold connectivity, affected consumer, crossfeed configuration and whether the symptom follows the source or remains with the path/consumer.
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.
