Add ATA 22 Auto Flight documentation and directory structure for BWB-Q100

[Copilot]

Title

Add ATA 22 Auto Flight documentation and directory structure for BWB-Q100

Summary

Implements ATA iSpec 2200 / ATA Standard Numbering System breakdown for ATA 22 Auto Flight, scoped to flight guidance/automatic flight functions (autopilot, auto-throttle, monitoring, load alleviation) for BWB-Q100 H₂ fuel cell / electric aircraft.

Documentation Updates

• Root README.md: Added ATA 22 section with six-section breakdown (22-00 through 22-50), BWB-Q100 H₂ propulsion context, and boundary clarifications
• ata/22/README.md: Complete ATA iSpec 2200 documentation with scope definitions, BWB deltas per section, and cross-references to ATA 23/24/26/27/31/34/42

Directory Structure Created

PRODUCTS/AMPEL360/AMPEL360_AIR_TRANSPORT/BWB-Q100/domains/IIS/ata/ATA-22-auto-flight/

Six sections with SYS–SEC–SBJ pattern:

• 22-00: Auto Flight General — architecture, modes, redundancy, integration boundaries
• 22-10: Autopilot — control laws, engagement logic, fail-operational behavior
• 22-20: Speed–Attitude Correction — capture/correction functions, energy state coupling
• 22-30: Auto Throttle — fuel cell dynamics integration, thrust command shaping
• 22-40: System Monitor — BITE, fault detection, graceful degradation
• 22-50: Load Alleviating — gust/load functions for large lifting surfaces

Each section includes:

• SSOT/: 8 lifecycle phases (LC01_Requirements → LC08_Certification)
• PUB/AMM/: S1000D CSDB structure (DM, PM, DML, ICN, BREX, COMMON, APPLICABILITY, EXPORT)
• PUB/IPC/: Same structure as AMM
• Configuration: bindings.csv, csdb.profile.yaml (BWB1 model, S1000D 5.0)

BWB-Q100 Specifics

• Distributed control effectors coordination (elevons/spoilers/drag devices)
• Fuel cell dynamics with battery buffering and inverter limits
• Enhanced load alleviation for large surfaces and bending sensitivities
• Power quality assumptions (ride-through, brownout)
• Explicit constraints for aeroelastic excitation avoidance

Canon checks

• Bridge QS→FWD→UE→FE→CB→QB unchanged
• UTCS phrasing intact
• QOx = Quantum Optimizations
• PAx orientation markers: ONB/OUT only
• AMPEL360 remains commons (no app code)

CXP (Context eXchange Points)

• Update UTCS/context.manifest.json if applicable
• Update sbom/spdx.sbom.json if dependencies changed
• cxp-publish passes in CI ✅

Evidence

• All CI checks pass
• Documentation updated (README.md, ata/22/README.md, ATA-22-auto-flight/README.md, 00_INDEX.md)
• Tests added/updated (documentation-only change, no tests required)

Original prompt

On README.md, PRODUCTS/AMPEL360/AMPEL360_AIR_TRANSPORT/BWB-Q100/domains/IIS/ata/22/README.md add ATA iSpec 2200 / ATA Standard Numbering System* breakdown, ATA 22 = Auto Flight and it should be scoped to flight guidance/automatic flight functions (autopilot/auto-throttle/monitoring/load alleviation), not primary flight controls, comms, or power generation. The ATA Standard Numbering System is published as an extract of ATA iSpec 2200 by Airlines for America (A4A). (A4A Publications)

ATA 22 Auto Flight (SNS breakdown)

The commonly used SNS section breakdown for ATA 22 is: (itlims-zsis.meil.pw.edu.pl)

• 22-00 — Auto Flight, General
• 22-10 — Autopilot
• 22-20 — Speed–Attitude Correction
• 22-30 — Auto Throttle
• 22-40 — System Monitor
• 22-50 — Aerodynamic Load Alleviating

What belongs in each ATA 22 section (BWB + H₂ fuel cell / electric context)

22-00 Auto Flight, General

Scope: architecture, modes philosophy, redundancy concept, integration boundaries, dispatch criteria, maintenance overview.
BWB deltas: mode logic and limitations tied to BWB envelope (e.g., pitch-moment management, trim strategy, high-lift interactions), electrical power quality assumptions (ride-through, brownout behavior), DAL allocation rationale for AF functions.

22-10 Autopilot

Scope: automatic control laws (AP), engagement/disengagement logic, fail-operational/fail-passive behavior, servo/command outputs to the Flight Control System (but not the flight controls themselves).
BWB deltas: distributed control effectors (elevons/spoilers/drag devices) coordination and reconfiguration handling; integration with FBW laws and gust response.

22-20 Speed–Attitude Correction

Scope: speed/attitude capture and correction functions that sit “between” guidance and control (depending on OEM, this may include speed stability augmentation behaviors).
BWB deltas: tighter coupling to energy state management (electric propulsion responsiveness, thrust limits, fuel cell transient constraints) and to load alleviation constraints.

22-30 Auto Throttle

Scope: autothrottle/autothrust computation and mode logic; commands to propulsion control.
BWB H₂-electric deltas: thrust command shaping to respect fuel cell dynamics, battery buffering strategy, inverter limits, thermal derates, and any distributed propulsion allocation logic (if propulsors are multiple).

22-40 System Monitor

Scope: monitoring, built-in tests, fault detection/isolation, mode inhibition, annunciations specific to Auto Flight.
BWB deltas: expanded monitoring of cross-domain dependencies (power availability, network health, flight control reconfiguration state), and robust “graceful degradation” mode tables.

22-50 Aerodynamic Load Alleviating

Scope: gust/load alleviation functions (structural load reduction via control law scheduling).
BWB deltas: typically more prominent due to large lifting surfaces and structural bending sensitivities; close integration with FBW and structural monitoring; explicit constraints to avoid adverse aeroelastic excitation.

Boundary map (what you listed that is not ATA 22)

Your sections like “Flight Control System (FCS)”, “Navigation”, “Communication”, “Power System”, “Cockpit Displays”, “Fire detection”, “IMA” are real, but they live in other ATA chapters, typically: (Wikipedia)

• Flight controls / actuators / FCC for surfaces: ATA 27 (Flight Controls)
• Navigation sensors / GNSS / INS / RNAV: ATA 34 (Navigation)
• Comms (VHF/HF/SATCOM): ATA 23 (Communications)
• Electrical generation/distribution: ATA 24 (Electrical Power)
• Displays / indicating / warnings: largely ATA 31 (Indicating/Recording)
• Fire detection/suppression: ATA 26 (Fire Protection)
• IMA / avionics computing platform: often ATA 42 (Integrated Modular Avionics) in many schemes

Important note (OEM variance): some manufacturers place FMS content under ATA 34-60 (Flight Management Computing) rather than ATA 22; treat FMS as a cross-reference, and decide one home chapter in your SSOT to avoid duplication. (Wikipedia)

---

If you want this to drop directly into your repo scaffolding (SYS–SEC–SBJ with SBJ = 5th/6th digits), tell me whether you want SBJ=00 only for each section at first (e.g., 22-10-00), or whether you already have subject granularity defined for your program; I will generate the 22-xx-yy subject skeleton plus the AMM/IPC SUB_ID publishing partitions exactly as you did for ATA 21.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.