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 Interfaces and User-System Demand
- Audience: Enthusiasts, students, junior technicians and professionals
- Level: Intermediate-to-advanced
- Status: Draft pending technical review
Learning objectives
- Explain the subsystem architecture and purpose.
- Identify the major components and interfaces.
- Trace command, pneumatic flow and feedback.
- Recognize protection and failure patterns.
- Apply evidence-based maintenance reasoning.
1. Purpose and operational value
Pneumatic behavior cannot be understood from ATA 36 alone because user-system demands and isolation requests continuously shape source and valve configuration.
2. Architecture and system flow
Air-generation packs create major continuous demand and can compensate or isolate according to their own control logic.
Wing ice protection and engine starting create high-priority or high-flow demands that alter source regulation.
Service-air users include equipment cooling/ventilation and water-tank pressurization.
Aircraft state, warning, maintenance and recording systems provide control inputs and receive pneumatic status.
3. Major components and functions
Air-generation system
Consumes regulated bleed air for environmental control. 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 pack demand, flow-valve state and isolation requests. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Wing ice protection
Uses hot bleed air at wing leading edges. 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 WIPS demand, valves, leak zones and source capacity. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Main engine start
Uses pneumatic energy to drive the starter. 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 start-valve demand, source pressure and crossbleed configuration. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Service-air manifold users
Use air for ventilation, cooled service air and tank pressurization. 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 branch demand, isolation and downstream pressure. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Aircraft data interfaces
Supply ground/flight state and record/display conditions. 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 LGERS, FWS, CDS, CMS, ACMS and recorded parameters. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
4. Normal operating sequence
1. Demand created
A user requests pneumatic air.
2. Capacity evaluated
BAS considers source condition and other users.
3. Valves configured
Source, crossbleed and user valves establish the route.
4. Performance monitored
Pressure and temperature response confirm supply.
5. Protection/isolation
User or OHDS request can remove a source or branch.
5. Control, monitoring and protection
A pack or WIPS command can legitimately change bleed pressure, valve position or source availability.
A pneumatic fault message may be secondary to incorrect aircraft-state data or a user-system isolation request.
Source capacity should be evaluated with the total active-demand picture, not one user in isolation.
6. Failure modes and maintenance reasoning
- Low pressure under high demand: Source regulation, excessive total demand or user leakage.
- One user unavailable: Local user valve/control or branch path.
- Source closes when user selected: Protection, excessive demand or interface command.
- Incorrect ground/flight logic: Landing-gear/air-data input.
- Recorded data differs from cockpit: Sensor route, recording interface or time correlation.
7. Interfaces with other systems
- ATA 21, 30, 38, 42, 45, 49 and 80.
- Landing-gear and air-data systems.
- Flight warning, display and recording.
- Electrical power and load management.
8. Practical maintenance scenarios
Bleed pressure drops only when WIPS is selected
Evaluate source capacity, WIPS flow and leakage.
Pack reports no bleed while manifold pressure exists
Trace the pack inlet and isolation interface.
Unexpected crossbleed command during ground operation
Check source availability and aircraft ground-state inputs.
9. Technician takeaways
- User demand is part of source diagnosis.
- Cross-ATA isolation requests can close healthy ATA 36 hardware.
- Use total-demand context.
- Correlate cockpit, CMS and recorded data by time.
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?
