Use case Aerospace · Fuhlsbüttel + Finkenwerder · EASA + UK CAA

Service Bulletins for 800 licensed mechanics - MSN-precise, Form-1 pre-checked, LBA-auditable, UK CAA-bridgeable

Service Bulletins for 800 licensed mechanics distributed MSN-precise. EASA Part-145, Part-66, Part-21. Continuing Airworthiness Records for LBA audit. UK CAA bridge post-Brexit.

Workshop at Grindelberg All 7 use cases ←

Chapter 1 — An MSN gap is an EASA finding

180 Service Bulletins per month. 800 licensed mechanics. Audit every 24 months.

A typical MRO operation at Fuhlsbüttel receives around 180 Service Bulletins per month from Airbus, Pratt & Whitney, Honeywell, Rolls-Royce, GE Aviation. Each must be mapped to specific MSN (Master Serial Number) and ESN (Engine Serial Number) of the fleet. Distributed to licensed-mechanic tablets. Acknowledgement-tracked. One MSN gap = potential EASA finding at next audit.

Current practice: 4 full-time staff occupied with bulletin distribution. 22 open mechanic positions (EASA Part-66 licensed) for 8 months. Recruiting pipeline via LinkedIn and Indeed takes 3-5 months per position - licence verification in 4 EU languages, EASA database reconciliation, background check for Fuhlsbüttel security control area.

Decision-Layer split typical for Service Bulletins: 60 percent RULES (MSN/ESN mapping, deadline calculation by AD compliance date, mandatory field validation), 30 percent AI AUTONOMOUS (language variants EN/FR/DE detection, acknowledgement tracking, classification Mandatory AD vs. Recommended SB), 10 percent HUMAN (critical bulletins with aircraft-grounding consequence, Form 1 pre-check by certifying staff).

Audit trail per bulletin: AD/SB number, MSN match, distribution timestamp, acknowledgement status per mechanic, compliance date, rule version (e.g. easa_part145_2026-q2). At LBA audit every 24 months, audit-trail UI is 1-click export. UK CAA audit on G-registered aircraft: parallel export via uk_caa_part145_2026-q2 rule lane.

Chapter 2 — Decision-Record for a Service Bulletin distribution

How a Service Bulletin runs through the Decision Layer from OEM email to mechanic tablet.

Anonymised decision-record for a Service Bulletin distribution at a Hamburg MRO operation with 800 licensed mechanics and a fleet of 240 tail numbers (A320 family, A330, A350). Includes UK CAA dual-lane handling for 47 G-registered aircraft in the same fleet.

SB-2026-05-15-AB-A320-CFM56-7B

Service Bulletin · Airbus A320 · CFM56-7B engines · Received 14.05.2026 18:42 · Mandatory AD

Result 47 tails identified · 89 mechanics notified · 87 acknowledgements
  1. 01 REGEL

    Bulletin intake + format check

    Service Bulletin from Airbus per EASA standard format (PDF + XML metadata). Mandatory fields complete: SB number, affected MSN range, compliance type (Mandatory AD), compliance date 14.07.2026. Rule sb_format_easa_v3.2.

    ✓ Intake valid
  2. 02 REGEL

    MSN range matching against fleet

    MSN range 5800-7200 (A320 family with CFM56-7B engines). Match against 240-tail fleet: 47 affected aircraft identified. Of these, 12 G-registered (UK CAA dual-lane required). Rule msn_match_v4.1.

    ✓ 47 tails (12 UK CAA)
  3. 03 REGEL

    Regulator lane assignment

    35 EU/EASA tails routed to EASA Part-145 lane. 12 UK CAA tails routed to parallel UK lane with diverging Mandatory SB lithium battery transport rules. Rule regulator_lane_v2.0.

    ✓ 2 lanes active
  4. 04 KI

    Language variants + classification

    Bulletin in EN. Classification: Mandatory AD (Airworthiness Directive), Compliance-Type Engine-Mount-Inspection. Severity high (aircraft grounding possible on non-compliance by compliance date). Model sb-classifier-v2.4.

    Confidence 0.97 · threshold 0.85

    ✓ Mandatory AD
  5. 05 REGEL

    Mechanic assignment by licence profile

    47 aircraft × ~2 affected mechanics (maintenance crew + certifying staff). 89 mechanics with matching EASA Part-66 licence (B1.1 for engine inspections) identified. 14 of those dual-licensed (EASA + UK CAA) for G-registered work. Rule mechanic_match_v3.3.

    ✓ 89 mechanics
  6. 06 REGEL

    Tablet distribution + acknowledgement tracking

    Bulletin PDF + compliance deadline + aircraft list in mechanic tablet inbox. Immediate notification. Acknowledgement deadline 7 days. Rule distribution_v2.1.

    ✓ 89 inboxes filled
  7. 07 KI

    Acknowledgement status after 7 days

    87 of 89 acknowledgements received. 2 outstanding: Mechanic T. (sick leave 5 days), Mechanic R. (vacation 3 days, return 22.05.). Model ack-tracker-v1.2.

    ▲ 2 outstanding
  8. 08 MENSCH

    Escalation to Continuing Airworthiness Manager

    Mandatory stop on acknowledgement gap. CAM receives notification with mechanic status and compliance date 14.07.2026. Decision: assign substitute mechanic or supervisor sign-off? Documented with timestamp.

    ✓ CAM assigns substitute
  9. 09 REGEL

    Continuing Airworthiness Records update (both lanes)

    Bulletin status per 35 EU + 12 UK tails marked as 'In Compliance Process'. Compliance date 14.07.2026 in audit trail. At every maintenance cycle until compliance date, inspection status against bulletin verified. Rule caw_records_v4.0.

    ✓ Records updated
  10. 10 REGEL

    LBA + UK CAA audit-trail persist

    Complete decision-record with AD/SB number, MSN match list, mechanic acknowledgements, escalation path, compliance date persisted. 1-click export for next LBA audit (EU tails) and UK CAA audit (G-registered). Rule audit_trail_v1.4.

    ✓ Audit trail persisted

Chapter 3 — Engineering on-site + AMOS integration + UK CAA bridge

Head office Hallerstraße 8 - 25 min to Fuhlsbüttel MRO, 35 min to Finkenwerder.

Head office Hallerstraße 8 is within 25 min by car of the Fuhlsbüttel MRO cluster, 35 min to Finkenwerder (Final Assembly Line A320 family + A321XLR exclusive). On-site meetings at MRO operations or ZAL TechCenter same-day reachable. Engineering counterpart sits in Hamburg, not Munich. Workshop sessions in training centre at Grindelberg with separate room for licensed-mechanic tablet-inbox demo and certifying-staff sign-off walk-through.

System integration: Decision Layer integrates with established MRO operations platforms: AMOS (Swiss Aviation Software, standard at many Hamburg MROs), CAMP (Continuous Airworthiness Maintenance Program), AMASIS, plus EASA database direct connection via NEXUS interfaces. REST, GraphQL or SOAP adapters depending on customer system. Interface definition part of discovery workshop.

UK CAA bridge post-Brexit: Since 1 January 2021, UK CAA operates as independent regulator. The Decision Layer treats UK CAA as separate rule lane running in parallel to EASA. Cross-recognition under EU-UK TCA Annex covers Form 1 certificates in both directions, but diverging Mandatory Service Bulletin requirements (e.g. on lithium battery transport) require dual-lane handling. For shared operations (Lufthansa Technik MRO with British Airways, easyJet maintenance contracts), the same Decision Layer handles both regulators with one audit trail per regulator export.

Final Assembly Line Finkenwerder: A320 family with ~301 deliveries in 2024 plus A321XLR exclusive with 550+ orders. Decision Layer carries EASA Part-21 (Production Organisation Approval) in addition to Part-145. Configuration documentation per tail with audit trail. AS9100 for Aerospace Quality Management. EU CRA (Cyber Resilience Act) for networked avionics systems. Source code, prompts and rule sets transferred to the MRO operator by repository handover, contractually. After 12-18 months you operate your Aerospace Decision Layer without us.

Related use cases

Frequently asked questions

Which EASA regulations does the Decision Layer cover?
EASA Part-145 (Maintenance Organisation Approval, EU 1321/2014), Part-66 (Aircraft Maintenance Licence), Part-21 (Production Organisation Approval, for Final Assembly Line Finkenwerder), Continuing Airworthiness Records with audit obligation every 24 months. Plus EU CRA (Cyber Resilience Act) for networked maintenance systems. Service Bulletins from Airbus, Pratt & Whitney, Honeywell, Rolls-Royce, GE Aviation mapped MSN/ESN-precise with mandatory acknowledgement tracking.
How does the architecture handle UK CAA divergence post-Brexit?
Since 1 January 2021 the UK CAA operates as an independent regulator with mostly aligned but increasingly diverging requirements from EASA. The Decision Layer treats UK CAA as a separate rule lane (e.g. <code>uk_caa_part145_2026-q2</code>) running in parallel to <code>easa_part145_2026-q2</code>. For UK-registered aircraft (G-prefix) or UK Part-145 organisations, the rule lane switches automatically. Cross-recognition under the EU-UK TCA Annex covers Form 1 certificates in both directions, but diverging Mandatory Service Bulletin requirements (e.g. on lithium battery transport) require dual-lane handling.
How is Form 1 pre-check by certifying staff ensured?
Form 1 (EASA Form 1 / CAA Form 1, Authorised Release Certificate) is mandatory for every maintenance release. Decision Layer pattern: RULES validates mandatory fields (Block 1-22), checks consistency with maintenance records, generates pre-filled output. AI AUTONOMOUS classifies maintenance descriptions against standard-phrase library. HUMAN required at final sign-off by certifying staff (EASA Part-66 or UK CAA equivalent licence). Audit trail documents: which licence number, which timestamp, which intervention point.
How does the architecture react to new Service Bulletins from Airbus or engine OEMs?
A typical MRO operation receives 180+ Service Bulletins per month. Decision Layer pipeline: RULES step maps bulletin against MSN/ESN database (Aircraft Master Serial Number, Engine Serial Number) of the fleet. Result: affected tail numbers identified. AI classifies urgency (Mandatory AD, Recommended SB, Service Information) and language variants (EN, FR, DE for European OEMs). Distribution to licensed-mechanic tablets with mandatory acknowledgement. Escalation to Continuing Airworthiness Manager on AD-compliance gaps.
How are Continuing Airworthiness Records prepared for LBA / CAA audit?
Every 24 months LBA audit (Luftfahrt-Bundesamt) with 18-month lead time. A missing mechanic-logbook entry = audit finding = licence risk. Decision Layer aggregates maintenance records, Form 1 certificates, AD-compliance status per tail number in one audit-trail view. Delta-analysis between expected and actual records per aircraft per maintenance interval. On gaps: escalation to Continuing Airworthiness Manager with concrete reference number. Same export structure works for UK CAA audit on G-registered aircraft.
What about AMOS, CAMP and AMASIS integration?
Decision Layer is system-agnostic. AMOS (Swiss Aviation Software), CAMP (Continuous Airworthiness Maintenance Program) and AMASIS are the established MRO operations platforms. The Decision Layer integrates via REST/GraphQL/SOAP - depending on customer system. Interface definition part of discovery workshop. Adapter source code transferred to customer at repository handover, no vendor lock-in on interfaces.

Schedule workshop at Grindelberg

3-day discovery: Day 1 process analysis, Day 2 Decision-Layer mapping, Day 3 use-case prioritisation. Concrete deliverable.

Schedule meeting

Discovery workshop below EUR 10,000. Pilot fixed price discussed after the workshop.

← Back to overview: AI Agents Hamburg (7 use cases)