HELP SHAPE TECHOPSBASE

Test the platform with us. Explore real features and report anything confusing, broken or missing. Your feedback will help prepare TechOpsBase for public release.

SYSTEM GUIDE Write an online resource Intermediate Focused read Technically reviewed

A350 Avionics, IFEC and Connectivity-Rack Smoke Detection

A detailed guide to duct smoke sampling, piccolo tubes, detector pairs, CIDS logic, ventilation/power isolation and contamination-related faults.

Airbus A350 English 26 min Version 2.0
By TechOpsBase Editorial ◆ Silver Contributor
Original TechOpsBase resource

Learn here. Maintain with approved data.

This resource is educational. Confirm current effectivity and approved manufacturer or operator data before aircraft work.

Technically reviewedReview state
Not applicableSource link
Review not scheduledFreshness
Start reading
26Views
0Saves
0Useful
0Downloads
KEY TAKEAWAYS

What you should leave with

  • Explain duct-type smoke detection.
  • Describe airflow sampling through piccolo tubes.
  • Trace detector pairs to CIDS warning logic.
  • Connect smoke warning to ventilation and electrical isolation.
  • Diagnose contamination and airflow-related faults.
Educational familiarization only. This is original TechOpsBase learning content. It does not reproduce Airbus pages, diagrams, procedures, maintenance-task instructions, numerical limits or controlled data. Actual aircraft work requires current approved data, correct aircraft effectivity, operator procedures, authorization, safety precautions and supervision.

Resource profile

  • Aircraft: Airbus A350 family
  • ATA chapter: 26 - Fire Protection
  • Audience: Aviation enthusiasts, students, junior technicians and experienced maintainers
  • Level: Intermediate system familiarization with maintenance reasoning
  • Source basis: Privately supplied legacy manufacturer training and MSG-3 analysis
  • Publication status: Draft pending technical review

Learning objectives

  • Explain duct-type smoke detection.
  • Describe airflow sampling through piccolo tubes.
  • Trace detector pairs to CIDS warning logic.
  • Connect smoke warning to ventilation and electrical isolation.
  • Diagnose contamination and airflow-related faults.

1. Duct detector operating concept

Avionics, in-flight-entertainment and connectivity equipment are cooled by forced ventilation. Smoke generated inside a rack is carried into the extraction duct. Sampling the extraction flow allows the system to monitor a large equipment volume without placing one detector beside every electronic unit.

Duct-type detectors use a sealed sensing housing connected to the extraction duct through sample and return tubes. A piccolo tube collects representative airflow from the duct.

Detection performance depends on both detector health and ventilation airflow. A failed fan, blocked duct or disconnected sample tube can delay smoke transport even when the detector is electrically serviceable.

Original TechOpsBase diagram: 1. Duct detector operating concept
Original TechOpsBase diagram: 1. Duct detector operating concept

2. Detector pairs and CIDS logic

Pairs of smoke detectors provide redundant monitoring. The CIDS Smoke Detection Function evaluates detector state and generates a warning when both detect smoke, or when one detector is already inoperative and the remaining detector detects smoke.

The protected areas are identified separately: main avionics compartment, IFEC and connectivity rack. Warning and controlled-response functions depend on the affected area.

A common CIDS or power fault can affect several detector pairs. A blocked piccolo tube usually produces a local sampling problem.

Original TechOpsBase diagram: 2. Detector pairs and CIDS logic
Original TechOpsBase diagram: 2. Detector pairs and CIDS logic
Original TechOpsBase diagram: 2. Detector pairs and CIDS logic
Original TechOpsBase diagram: 2. Detector pairs and CIDS logic

3. Ventilation and electrical response

Smoke detection can command the Ventilation Control System to stop affected airflow. Cockpit controls allow the crew to isolate IFEC or connectivity ventilation and remove power from selected equipment.

Stopping ventilation reduces smoke movement and can remove the electrical source of the event, but it also changes airflow through the detector. Maintenance analysis must account for the commanded configuration.

A smoke warning can remain while equipment is isolated because particles remain in the duct or compartment.

Original TechOpsBase diagram: 3. Ventilation and electrical response
Original TechOpsBase diagram: 3. Ventilation and electrical response
Original TechOpsBase diagram: 3. Ventilation and electrical response
Original TechOpsBase diagram: 3. Ventilation and electrical response

4. Contamination and troubleshooting

Piccolo tubes and sample passages can collect dust and dirt. A blockage reduces representative air reaching the detector. Contamination inside the detector can produce sensitivity loss or nuisance warnings.

If both detectors in one extraction duct are reported failed, investigate shared power, airflow path, local wiring and CIDS interface. If one detector alone is failed, compare its sample tube, connector and internal status with its pair.

If an avionics smoke warning occurs with a cooling-fan fault, preserve the sequence. Reduced airflow may overheat equipment, while a genuine electrical event may have caused both smoke and fan shutdown.

Original TechOpsBase diagram: 4. Contamination and troubleshooting
Original TechOpsBase diagram: 4. Contamination and troubleshooting
Original TechOpsBase diagram: 4. Contamination and troubleshooting
Original TechOpsBase diagram: 4. Contamination and troubleshooting

Maintenance boundary

This resource teaches system architecture and fault reasoning. It deliberately excludes cartridge handling, squib isolation steps, bottle removal procedures, discharge tests, detector acceptance limits, resistance values, agent quantities, warning-reset procedures and dispatch decisions. Fire bottles, cartridges, squibs, hot-battery circuits and pressurized agent are hazardous. Use the current approved AMM, TSM, wiring data, safety procedures and aircraft effectivity before performing aircraft work.

Review prompts

  1. Which zone is being protected, and is the hazard fire, overheat or smoke?
  2. What sensing technology is used in that zone?
  3. Which independent channels must agree before a warning is confirmed?
  4. Which computing function converts, validates and distributes the signal?
  5. What automatic isolation or shutdown follows the warning?
  6. Is extinguishing automatic, manual, or not installed for that zone?
  7. Which test proves the detector path, warning path and firing-circuit monitoring?
  8. What hazardous stored energy remains during maintenance?
APPLICABILITY

Check effectivity before applying information.

A350-family familiarization. Detector, bottle, agent, cabin-layout and option differences may apply by effectivity.

Operational reminder

Confirm aircraft registration, model, serial effectivity, modification status, software standard and operator procedures using current approved maintenance data.

RELATED LEARNING

More resources in this context

SYS
System guideWrite an online resource
ATA 29Intermediate

Airbus A350 ATA 29 Hydraulic Power - System Study Guide

An original, system-level familiarization guide to the A350 Green and Yellow hydraulic systems, covering architecture, power generation, reservoirs, ground operation, thermal control, monitoring and maintenanc…

1 useful1 saved
Open resource
BUILD YOUR TECHNICAL LIBRARY

Save the references you actually use.

Keep useful resources, saved searches and followed aircraft/ATA topics together without changing public access to the material.

✓ Saved resources✓ Saved searches✓ Follow aircraft + ATA