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 Operating Modes and Source-Transition Workshop
- 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
Operating-mode knowledge explains why the same valve can be correctly open in one configuration and correctly closed in another.
2. Architecture and system flow
Normal two-engine operation uses separated left and right sources.
APU and ground operation normally require a connected manifold.
One-engine or one-EBAS failure can require crossfeed while respecting remaining source capacity.
Leak isolation can intentionally remove crossfeed or an otherwise healthy source.
Selected control failures move EBAS regulation into a pneumatic backup mode.
3. Major components and functions
Normal two-engine mode
Provides independent source sides. 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 crossbleed closed and each EBAS regulating. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
APU mode
Uses APU priority and connected distribution. 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 engine isolation, APU valve and crossbleed. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Ground-air mode
Uses external supply with ground 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 connector, ground status, crossbleed and users. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Single-source mode
One source supports selected users across the manifold. 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 capacity, crossbleed and load management. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
Leak-isolated mode
Removes pressure from a damaged zone. 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 isolation-valve sequence and remaining supply. A maintenance conclusion is strongest when command, feedback and physical pneumatic effect agree.
4. Normal operating sequence
1. Select configuration
Source and user demands establish the desired mode.
2. Move valves
BAS/BAM and user controls command the required topology.
3. Stabilize pressure/temperature
Regulation adapts to the new total demand.
4. Confirm users
Downstream systems report usable supply.
5. Protect
OHDS or EBAS protection overrides continued supply if needed.
5. Control, monitoring and protection
Rapid source switching can create transient pressure changes that should not be confused with a persistent regulation fault.
A single source may be available but unable to support every simultaneous high-flow user.
Manual selection can force a configuration that automatic logic would avoid; testing must use approved conditions.
6. Failure modes and maintenance reasoning
- Transition causes user trip: Timing, competing valve position, source capacity or regulation.
- Single-source pressure low: Excess demand, crossbleed restriction or source performance.
- Automatic mode incorrect, manual mode works: BAS inputs/logic or command route.
- Pneumatic backup unstable: Mechanical regulator, servo/sense-line or source condition.
- Leak mode removes too much supply: Isolation boundary/valve feedback or persistent overheat.
7. Interfaces with other systems
- Air-generation load management.
- APU and engine controls.
- Landing-gear/flight-phase data.
- OHDS protection.
- Cockpit control and indication.
8. Practical maintenance scenarios
Engine-to-APU transition interrupts both packs
Review coordinated engine isolation, APU valve opening and crossbleed timing.
Ground cart supplies only one side
Check crossbleed command/position and manifold restriction.
One engine source feeds both sides but temperature rises
Evaluate increased demand and cooling-air regulation.
9. Technician takeaways
- Correct valve state depends on operating mode.
- Transitions must be judged by timing and stability.
- Source availability is not the same as source capacity.
- Automatic and manual behavior provide useful comparison.
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?
