Educational familiarization only. This original TechOpsBase lesson was developed from privately supplied legacy A350 training and MSG-3 material. It does not reproduce manufacturer pages, proprietary diagrams, maintenance task steps, numerical maintenance limits, dispatch criteria or controlled maintenance data. Current approved aircraft data, correct effectivity, operator procedures and authorization govern all aircraft work.
Resource profile
- Aircraft: Airbus A350 family
- ATA chapter: 36 - Pneumatic
- Resource: A350 ATA 36 Pneumatic - Complete Expanded Overview
- Audience: Enthusiasts, students, junior technicians and professionals
- Level: Intermediate-to-advanced
- Status: Draft pending technical review
Learning objectives
- Map every pneumatic source and major user.
- Explain left/right manifold separation and crossfeed.
- Describe engine-bleed pressure and temperature regulation.
- Explain dual-loop leak detection and automatic isolation.
- Apply source-side-user troubleshooting logic.
1. Purpose and operational value
The pneumatic system selects and regulates compressed-air sources, distributes that air to aircraft users and isolates unsafe sections when pressure, temperature or leak conditions become abnormal.
2. Architecture and system flow
The two engines are the normal in-flight sources. The APU supplies starting and backup demand within its approved operating envelope, while a ground cart can pressurize the system during ground operation.
Each engine normally supplies its own manifold side. A central crossbleed valve can join or separate the two sides according to source configuration, failure logic or manual selection.
Engine bleed air is regulated before it enters the main distribution ducts. Pressure control selects the appropriate compressor source and modulates regulating valves. Temperature control meters fan air through a precooler.
The Overheat Detection System monitors zones adjacent to hot-air ducting with two independent loops and can request staged isolation of a leaking section.
3. Major components and functions
PADS
Routes air from engines, APU or ground supply to the required users. It must receive the correct pneumatic or electronic input, perform the expected function and return a believable output or status. A fault can result from electrical power, data communication, a blocked or leaking pressure/sense line, pneumatic contamination, mechanical friction, incorrect configuration, a failed sensor or an upstream/downstream system request. Useful evidence includes source availability, crossbleed state, duct pressure, check-valve behavior and user demand. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
EBAS
Regulates pressure and temperature for each engine bleed source. It must receive the correct pneumatic or electronic input, perform the expected function and return a believable output or status. A fault can result from electrical power, data communication, a blocked or leaking pressure/sense line, pneumatic contamination, mechanical friction, incorrect configuration, a failed sensor or an upstream/downstream system request. Useful evidence includes HP/IP selection, regulating-valve behavior, pressure/temperature feedback and protective closure. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
OHDS
Detects hot-air leakage, requests isolation and reports location. It must receive the correct pneumatic or electronic input, perform the expected function and return a believable output or status. A fault can result from electrical power, data communication, a blocked or leaking pressure/sense line, pneumatic contamination, mechanical friction, incorrect configuration, a failed sensor or an upstream/downstream system request. Useful evidence includes loop health, zone identification, isolation sequence and stored maintenance data. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
BAS/BAM control
Provides normal electronic control plus independent monitoring and backup functions. It must receive the correct pneumatic or electronic input, perform the expected function and return a believable output or status. A fault can result from electrical power, data communication, a blocked or leaking pressure/sense line, pneumatic contamination, mechanical friction, incorrect configuration, a failed sensor or an upstream/downstream system request. Useful evidence includes CPIOM, BOMU, CRDC, AFDX/CAN status and command-feedback agreement. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Cockpit controls and displays
Allow source selection and show pneumatic configuration. It must receive the correct pneumatic or electronic input, perform the expected function and return a believable output or status. A fault can result from electrical power, data communication, a blocked or leaking pressure/sense line, pneumatic contamination, mechanical friction, incorrect configuration, a failed sensor or an upstream/downstream system request. Useful evidence includes pushbutton/selector state, BLEED page, warnings, valve symbols and sensor availability. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
4. Normal operating sequence
1. System initialization
Controllers, monitors, sensors and valves establish a safe source configuration.
2. Source selection
Available engine, APU or ground air is chosen according to flight phase, user demand and priority.
3. Regulation
Pressure and temperature are controlled before air reaches the main manifold.
4. Distribution
Air flows through the left/right ducts and crossbleed as required.
5. Protection
Abnormal pressure, temperature or leak conditions cause warnings and isolation requests.
5. Control, monitoring and protection
The visible valve symbol is only one layer of evidence. Physical pressure and downstream user response must support the displayed position.
A user-system fault can command a pneumatic valve closed even when the valve and source are mechanically healthy.
A common electronic-control fault can affect more than one displayed parameter, while independent BAM/BOMU functions can still preserve protection.
6. Failure modes and maintenance reasoning
- One side unavailable: Engine source, EBAS regulating chain, manifold isolation or leak response.
- Both sides low: Common source configuration, multiple demands, crossbleed or shared indication issue.
- High temperature: Fan-air valve, precooler airflow, temperature sensor or control path.
- High/unstable pressure: Pressure regulation, sense line, transducer or protective valve.
- Leak warning: Actual hot-air escape, sensing-loop issue or unsuccessful isolation.
7. Interfaces with other systems
- ATA 21 air generation, service-air and temperature-control users.
- ATA 24 electrical power.
- ATA 30 wing ice protection.
- ATA 38 water-tank pressurization.
- ATA 42 IMA/AFDX and CRDC.
- ATA 45 maintenance and condition monitoring.
- ATA 49 APU pneumatic control.
- ATA 80 engine starting.
8. Practical maintenance scenarios
Several users on one side fail together
Start with the common source and manifold path before replacing individual user equipment.
Pressure is displayed but a pack receives no air
Compare valve position, downstream pressure and the pack inlet/control path.
A leak warning remains after reset
Use stored leak-location and isolation evidence; do not treat reset recovery as repair.
9. Technician takeaways
- Always identify source, side, user and operating phase.
- Separate physical air flow from electronic command and indication.
- Pressure regulation and temperature regulation are different chains.
- Leak protection has priority over continued pneumatic supply.
Maintenance boundary
This resource explains system architecture, normal operation, indication and maintenance reasoning. It intentionally excludes removal/installation procedures, wiring-pin checks, valve rigging, leak-test limits, servicing limits, maintenance intervals, software part numbers, dispatch decisions and release-to-service criteria.
Review prompts
- Which pneumatic source should be available in this configuration?
- Which valve or controller establishes the expected flow path?
- Which pressure, temperature or position feedback proves the command was achieved?
- Is the symptom local to one side, one source, one user or the complete manifold?
- Could a user-system demand or isolation command explain the observed state?
- Is the fault in the physical air path, the pneumatic control path or the electronic command path?
- What evidence must be preserved before reset, source change or manual override?
- What hot-air, pressure, moving-equipment and structural-protection boundary applies?
