Use Case Aerospace Engines · MTU Allach · EASA Part-145 Engine

EASA Part-145 for engine maintenance - MTU Aero Engines Allach with engine MSN mapping and FADEC diagnostics

MTU Aero Engines Allach - engine maintenance for GE/CFM/Pratt/Rolls. Engine MSN mapping vs. Aircraft MSN. EASA Part-145 engine specifics + Form 1 for engine modules. UK CAA post-Brexit parallel.

Workshop at Grindelberg All 7 use cases ←

Chapter 1 - Engine MRO vs. Airframe MRO

Engine MSN mapping is not Aircraft MSN mapping. Different audit reality, different data volumes.

MTU Aero Engines AG (Dachauer Straße 665, 80995 Munich-Allach-Untermenzing) is an independent engine MRO + RSP (Risk-Sharing Partner). Ca. 3,500 mechanics in the Allach plant, ca. 800 Certifying Staff with engine Type Rating, ca. 12,000 engine modules in process annually, ca. 480 complete engines per year. Operational reality: Engine Health Monitoring (EHM) generates 10,000-50,000 data points per flight cycle - one engine intake typically brings 200-400 million data points for the maintenance decision.

Engine MRO differs structurally from Hamburg airframe MRO: Engine Serial Number (ESN) instead of tail number, Engine Module Form 1 per module (Fan, LPC, HPC, Combustor, HPT, LPT) instead of Aircraft Form 1, FADEC (Full Authority Digital Engine Control) software diagnostics instead of avionics diagnostics, engine test cell reality (acoustic + thermal engine tests). Plus Service Bulletins per engine type from the OEM (GE Aviation, CFM, Pratt & Whitney, Rolls-Royce) with ESN range mapping. UK parallel: Rolls-Royce Derby operates identical structure for Trent engines - CAA equivalence with EASA is fully recognised.

Decision-Layer split typically for engine MRO decisions: 55% RULES (EASA Part-145 engine validation, LLP cycle-count check, disk replacement records, mechanic Type Rating match, OEM Bulletin mapping), 30% AI AUTONOMOUS (EHM anomaly classification against the failure-mode database, FADEC diagnostic patterns, language versions of Bulletin EN/FR/DE), 15% HUMAN (Severity-A findings, engine removal decision, Module Form 1 sign-off, OEM RSP escalation).

Audit trail per engine maintenance: ESN + engine type + FADEC version + EHM anomaly classification + LLP cycle counts + Bulletin compliance status + mechanic licence verification + Module Form 1 sign-off + Type Rating audit trail. At EASA audit + FAA audit + OEM audit (GE, P&W, Rolls annually): 1-click export per audit format. UK clients selling engines into the US market: MTU is also FAA Part-145 certified - same export covers FAA Repair Station audit.

Chapter 2 - Decision Record for a FADEC Anomaly Assessment

How an engine intake with FADEC anomaly is triaged in the Decision-Layer.

Anonymised decision record for an engine intake at MTU Allach. CFM LEAP-1A engine for A320neo. EHM data shows vibration anomaly. FADEC diagnostics trigger Bulletin check. Decision: routine maintenance or engine removal recommendation?

ENG-MRO-2026-05-17-LEAP1A-ESN-784

CFM LEAP-1A engine · ESN 784xxxx · intake 17.05.2026 · A320neo · 12,400 flight cycles · EHM shows vibration anomaly Stage 2 LPT

Result Routine inspection recommended · engine removal not required · OEM Bulletin status updated
  1. 01 REGEL

    Engine intake validation

    Engine ESN 784xxxx registered in the MTU engine tracking system. Type CFM LEAP-1A for A320neo. Last maintenance 4,800 flight cycles ago. Current cycle count 12,400. Rule engine_intake_v3.2.

    ✓ Intake validated
  2. 02 REGEL

    OEM Bulletin mapping (CFM Service Bulletins)

    Current CFM Bulletins for LEAP-1A: 12 open SBs. Of those 3 with ESN range match (ESN range 700000-800000). 1 Mandatory AD (engine mount inspection), 2 recommended SBs. Compliance date of Mandatory AD: 14.07.2026. Rule cfm_sb_match_v2.4.

    ✓ 1 Mandatory AD + 2 SBs
  3. 03 REGEL

    LLP cycle-count check (Life Limited Parts)

    LLP cycle counts for 7 critical disk modules: HPC-Disk1 (8,400/15,000), HPC-Disk2 (8,400/15,000), HPT-Disk1 (8,400/12,000), HPT-Disk2 (8,400/12,000), LPT-Disk1 (12,400/16,500), LPT-Disk2 (12,400/16,500), Fan-Disk (12,400/20,000). All within limits, no disk replacement required. Rule llp_check_v1.7.

    ✓ All LLPs OK
  4. 04 KI

    FADEC database analysis (model <code>fadec-analyzer-v3.4</code>)

    FADEC software version P12.4 verified (current). Last 50,000 flight cycles loaded (ca. 2 billion data points). EHM anomaly classification: vibration pattern Stage-2-LPT (mid-frequency, cycle 11,200-12,400 steadily increasing). Model classification: bearing-wear pattern (probability 0.87 against disk-crack 0.04 against false-positive 0.09).

    Confidence 0.87 · threshold 0.85

    ✓ Bearing-wear pattern
  5. 05 KI

    Failure-mode database match

    Bearing-wear pattern Stage-2-LPT mapped against the MTU / CFM failure-mode database. 47 similar cases in the last 24 months. Repair pattern: bearing replacement at next Major Maintenance Cycle (typically after 16,500 cycles on LEAP-1A). At 12,400 cycles: no removal required. Model failure-mode-classifier-v2.4.

    Confidence 0.91 · threshold 0.85

    ✓ Routine inspection recommended
  6. 06 REGEL

    Mechanic Type Rating match

    LEAP-1A engine inspection requires EASA Part-66 B1.1 licence + LEAP-1A Type Rating (CFM training). 14 mechanics in the Allach plant with active LEAP-1A Type Rating available. Routing to the mechanic pool. Rule mechanic_type_rating_v3.3.

    ✓ 14 mechanics available
  7. 07 MENSCH

    Senior Inspector sign-off + Mandatory AD compliance path

    Mandatory stop on Mandatory AD compliance. Senior Inspector Ms B. (LEAP-1A Type Rating + 18 years MTU) receives the decision record with bearing-wear classification, LLP status, Mandatory AD status, mechanic availability. Confirms: routine inspection + Mandatory AD compliance path in parallel. Engine removal not required.

    ✓ Routine + Mandatory AD path confirmed
  8. 08 REGEL

    Module Form 1 preparation

    After inspection: Engine Module Form 1 pre-fill with updated LLP counts (LLP counts rise by 200 cycles for test-cell run), Bulletin compliance status (Mandatory AD satisfied), FADEC software update if Bulletin requires. Certifying Staff sign-off path with Type Rating verification. Rule module_form1_v3.4.

    ✓ Form 1 prepared
  9. 09 REGEL

    Audit trail persist (EASA + FAA + CFM OEM)

    Complete decision record persisted with ESN, FADEC version, EHM anomaly classification, LLP counts, Mandatory AD compliance, mechanic Type Rating, Senior Inspector sign-off. 1-click export for EASA audit (LBA format), FAA audit (US customer engine format), CFM OEM auditor view (CFM RSP reporting). Rule audit_v1.4.

    ✓ Audit trail persisted

Chapter 3 - Workshop at Allach or Munich Urban Colab

Engineering from Hamburg, workshop at the MTU plant Allach-Untermenzing.

Engineering head office Hallerstraße 8 Hamburg. Munich workshop on-site. MTU plant Allach (Dachauer Straße 665) or Munich Urban Colab as neutral ground. Separate rooms for Continuing Airworthiness Manager session, engineering workshop with FADEC specialists, compliance / EASA auditor briefing, works-council session. Workshop under EUR 10,000. For UK / FAA customer engagements: workshop in English with remote bridge to UK head office (Rolls-Royce Derby) or US OEM (GE Cincinnati, Pratt East Hartford).

MTU engine MRO workshop pattern: Day 1 = stakeholder mapping (Continuing Airworthiness Manager + Senior Inspectors + IT/OT team + Compliance). Day 2 = Decision-Layer demo with engine-specific use cases (FADEC anomaly classification, LLP tracking, Bulletin mapping, Module Form 1 workflow). Day 3 = integration workshop with engine tooling (MTU engine tracking system, CFM / GE / P&W / Rolls OEM portals, EASA NEXUS interfaces).

Integration with engine MRO IT: the Decision-Layer integrates with engine tracking systems: MTU's own Engine Lifecycle Management software, AMOS (Swiss Aviation Software) for customer engines, CFM Service Bulletins portal, GE Aviation Service Bulletins portal, Pratt & Whitney Engine Health Monitoring, Rolls-Royce Trent Engine Health Care. FADEC data streaming via OEM-specific protocols. Source code of the adapters goes with the repository handover to MTU - no vendor lock-in of the interfaces.

OEM RSP compliance: MTU as Risk-Sharing Partner for GEnx (4%), PW1100G (18%), GE9X (4%) has elevated OEM compliance demands. Engine tracking + performance reporting + defect reporting to OEM in OEM-specific formats. Decision-Layer audit trail must be OEM reporting-capable. Plus: on RSP shares MTU is co-responsible for engine performance guarantees - AI-supported maintenance decisions must be traceable for OEM audit. UK parallel: Rolls-Royce RSP relationships with airlines (TotalCare) demand the same audit-trail depth.

Related use cases

Frequently asked questions

What distinguishes engine MRO from airframe MRO?
The level of work. Airframe MRO (Hamburg cluster: Lufthansa Technik Fuhlsbüttel with A320 maintenance) works at aircraft level - tail-number mapping for the whole aircraft including structures, avionics and hydraulics. Engine MRO (Munich cluster: MTU Aero Engines Allach) works at engine level, keyed on the Engine Serial Number (ESN) with FADEC and performance diagnostics. EASA Part-145 applies to both, but the engine specifics differ: an engine test cell, a Form 1 per engine module rather than an Aircraft Form 1, and Engine Health Monitoring (EHM) data. The same airframe-vs-engine split holds in the UK (BA Engineering Heathrow vs. Rolls-Royce Derby) under CAA with post-Brexit EASA equivalence.
Which engine OEMs are relevant for MTU?
MTU Aero Engines operates as an independent MRO + RSP (Risk-Sharing Partner) with all major OEMs: GE Aviation (GE90, GEnx, GE9X for Boeing 777/787), CFM International (CFM56 for A320ceo + 737, LEAP for A320neo + 737MAX), Pratt & Whitney (PW1100G GTF for A320neo, PW4000 for 747/767), Rolls-Royce (Trent 700/900/1000/XWB for A330/A380/A350). Plus MTU RSP shares in GEnx (4%), PW1100G (18%), GE9X (4%). Service Bulletins come per engine type from the OEM with ESN range and must be mapped per MTU plant (Munich, Hannover, Berlin, Poland, China). UK angle: Rolls-Royce Derby is both MTU's RSP partner and direct competitor on Trent maintenance - architectural standard is identical.
How is FADEC diagnostics covered in the Decision-Layer?
FADEC (Full Authority Digital Engine Control) is the control software on engine modules. On MRO intake it generates roughly 10,000-50,000 Engine Health Monitoring (EHM) data points per flight cycle. The Decision-Layer splits the work by decider type: RULES validate the FADEC software version against the engine-type Bulletin status, AI classifies EHM anomalies (vibration, temperature, pressure patterns) against the failure-mode database, and a human is mandatory on Severity-A findings such as an engine-removal recommendation. Each engine maintenance carries an audit trail keyed on ESN, FADEC version, EHM anomaly classification and mechanic sign-off. UK clients operate the same data scale via CAA and Rolls-Royce Trent Engine Health Care.
How does Engine Module Form 1 work differently from Aircraft Form 1?
EASA Form 1 (Authorised Release Certificate) is mandatory documentation on every maintenance release. In engine MRO: separate Form 1 per engine module (Fan, LPC, HPC, Combustor, HPT, LPT, Bypass) when the module is independently swapped. Plus engine module hardware trackings (Life-Limited Parts LLP with cycle counts, disk replacement records). Certifying Staff must hold an EASA Part-66 licence with engine-specific Type Rating. Decision-Layer integration: RULES validate LLP cycle counts + disk replacement records per module. AI AUTONOMOUS classifies maintenance descriptions against the standard-phrase library. HUMAN mandatory on Module Form 1 sign-off. UK CAA recognises EASA Form 1 via post-Brexit equivalence agreement - dual sign-off only for US customers (FAA Form 8130-3).
What LBA / EASA audit reality applies to MTU?
EASA Part-145 audit every 24 months by LBA (Luftfahrt-Bundesamt) with 18 months of lead time. For the MTU Allach plant: ca. 3,500 mechanics, ca. 800 Certifying Staff with Type Rating, ca. 12,000 engine modules in process annually, ca. 480 complete engines per year. Plus EASA plant audit for RSP-share plants (e.g. PW1100G module production at MTU). Plus FAA Part-145 Repair Station Approval for US customer engines. Plus OEM auditor surveillance (GE, P&W, Rolls annually). Decision-Layer audit-trail view for all three audit formats (EASA, FAA, OEM) per 1-click export. UK parallel: UK MRO faces CAA Part-145 + FAA + OEM surveillance - same triple-audit architecture.

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)