Original research · Aerospace & Defense

MTU Aero Engines.

Last measured · 13 Jun 2026 Wave · Q2-2026-W8-AEROSPACE-DEFENSE Tier · proprietary Confidence · C
Brand
MTU Aero Engines AG
Agent success

The full locked chain resolves on brand-owned pages over plain HTTP: PW1100G-JM, the A320neo application, Hannover MRO and a reachable B2B contact.

Bottleneck Multi-axis
Weak on more than one axis at once.
4.8 /10
Agent Success Score
AI Visibility 53 / 100

Found & recommended by AI agents

AI Usability 45 / 100

Search-class agents touched the close in some runs; the full agent-fleet access profile lands in a later wave.

Coverage · 1 of 6 lanes measured Commerce lane · Catalog-only · Wave Q2-2026-W8-AEROSPACE-DEFENSE
Commerce 4.8
Talent
After-sales
Procurement
Investor
Press

This page measures the commerce lane: can an agent find MTU Aero Engines, and once it arrives, transact. Talent, after-sales, procurement, investor and press lanes run on different surfaces and are not yet measured.

Your brand isn't measured yet

What does an AI agent do with your website?

The same measurement as MTU Aero Engines, free for your domain. Five agent classes, one real task, your score in 48 hours.

Free · no card · 48h

The test

The locked spec chain resolves end to end on mtu.de over plain HTTP. For the two measured agent classes, this surface simply works; the open question is who finds it.

The Gate-1 audit ran the standard 18 datapoints in German: an unbranded PW1100G-MRO provider probe, the MTU / Lufthansa Technik / Pratt & Whitney comparative shortlist, and the MTU Maintenance Hannover transactional RFQ query, across openai, perplexity and anthropic. The fleet ran phase 1 ceiling extraction on the mtu.de Commercial Maintenance surface and phase 2 HTTP plus coding agents against the PW1100G-JM partnership page. Both measured classes returned success: the GTF family page names PW1100G-JM for the A320neo, raw HTML confirms the full locked chain on brand-owned pages, and the quote pathway is reachable. Phases 3 and 4 (browser, autonomous close) did not run in this wave: the fleet browser runtime was infrastructure-blocked. They follow in the re-run.

One label, many breeds. From a plain reader to an autonomous operator, the kinds behind ChatGPT, Perplexity, and Claude Code:

Plain reader reads your raw page text, no browser Succeeded
Search assistant finds you through search Not yet run
Coding agent a script hitting your site Succeeded
Computer-use agent clicks and types like a person Not yet run
Autonomous operator runs the whole task unattended Not yet run
Commerce lane

Found, and able to transact?

Two questions, measured separately. A brand can be recommended and still un-buyable, or perfectly buyable and never found.

AI Visibility

When someone asks an agent to find a supplier, does it route to MTU Aero Engines?

53 / 100

MTU Aero Engines comes up just over half the time. The rest of the time, an agent recommends an alternative first.

Discoverability · 18-datapoint audit
AI Usability

Once an agent is on MTU Aero Engines's site, can it reach an RFQ pathway for the PW1100G-JM MRO service?

45 / 100

Search-class agents surface a quote in some runs; the full agent-fleet access profile lands in a later wave.

Evidence · 65 / 100 A measure of how provable and consistent the result is, grounded in cross-method ground-truth agreement (the methods that ran returned the same price), not a separate measured run. A confidence layer on the two scores above, not a third sales axis.

What's next

What this means for MTU Aero Engines.

Diagnosis

MTU is not lacking surface quality; it lacks discovery share. The PW1100G-JM chain reads cleanly for agents, and the spec-fidelity question resolved in MTU's favour: both measured classes disambiguate the GTF program from V2500, GP7200 and GE9X on brand-owned pages. But the unbranded engine-MRO question reaches MTU only about half the time, and the RFQ pathway still routes through a cross-program Maintenance contact form rather than a per-program entry point.

What changes the outcome

Answer surfaces that own the unbranded MRO questions (shop-visit decisions, GTF on-wing support, A320neo engine service) and cite the Hannover capability as evidence, so the agent arrives at mtu.de before it settles a shortlist. At the close: a PW1100G-JM-specific RFQ entry that identifies the engine and airframe combination directly, instead of the cross-program contact form.

What proof looks like

The proof isn't more content. It's a repeatable lift in whether agents find, verify, cite, recommend, and complete the brand journey directly — re-measured each wave.

Audit · €1,900

Commission an audit.

Where the BrandScore opens the question, an audit closes it. An interpretive engagement on your full surface, scored under the same methodology.

Get the audit
Founding · €4,500

Found with us.

Strategic partnership for brands building agent success as a long-term capability, not a one-off engagement.

Apply
Snapshot

Audit an adjacent property.

The BrandScore covers the primary domain. Get the same methodology applied to an adjacent property: a country site, a sub-brand, a category beyond the DAX-40 slate.

Get a Snapshot

This is MTU Aero Engines. What about your brand?

You just saw how an AI agent treats a DAX 40 brand.

The same measurement runs free against your domain: five agent classes, one real buying task, your Agent Success Score in 48 hours, in the exact format of this page.

Measured, not guessed. Real agents against your real site, no questionnaire.
Publicly comparable. Your score in the same grid as the measured DAX 40 brands.
Next wave closing. Start now to be in the next index round.

Free · no card · 48h

Channel position

MTU Aero Engines owns its channel. Agents arrive directly.

Commercial aero-engine MRO closes via direct B2B sales; Lufthansa Technik, Pratt & Whitney EngineWise and AFI KLM compete the same way, without a marketplace platform. No intermediary captures the close. The close stays on mtu.de.

0% direct
0% via intermediary
Frozen task slate

Hyperize-selected tasks.

One task from the public sector grid. Task list is frozen before each wave runs.

MTU Maintenance Hannover · PW1100G-JM (GTF) engine MRO service for A320neo

Close state
a quote
Bottleneck
Discovery, not the surface: the unbranded MRO question reaches MTU about half the time, while the locked chain resolves fully once an agent is on mtu.de.

Fairness note

Wave 8 Q2 2026 partial measurement on a single task (MTU Maintenance Hannover · PW1100G-JM MRO service, quote_ready close, GTF engine for A320neo locked SKU). AI Visibility from Cody Gate-1 (52.50, 18/18 valid datapoints across openai/perplexity/anthropic, DE language). AI Usability from a fleet wave Phase 2 only (HTTP + coding agents, both success; Phase 3 browser + Phase 4 ACT infrastructure-blocked in this wave: fleet browser runtime unavailable, not a brand result; re-run scheduled). The browser and full_automation rows of the agent_matrix are marked pending. Fairness Review pending the sector fairness grid.

Methodology

How the score was produced.

Discoverability is audit-pipeline-derived. 3-provider sample (openai, perplexity, anthropic), 3 query variants per task, 2 runs per variant · 18 valid datapoints scored against a five-state handoff cascade. [S1]

AI Usability is derived from the access-profile above (usability-derivation/v1): how far the best agent reached (close state) modulated by how many agent classes succeeded. The per-class profile is the truth; the score is a reproducible summary of it, not a separate rating. Fleet phases (HTTP / Coding / Browser / ACT) produce the profile. [S2]

Formula

Agent Success Score = (AI Visibility × 0.20) + (AI Usability × 0.70) + (Evidence × 0.10)

On a 0–100 scale, displayed 0–10. AI Usability bundles the agent's reach + completion; AI Visibility is audit-derived discoverability. Weighting is public; the per-prompt derivation is not.

Measurement scope

Confidence C · one measured task on a 3-provider track (openai, perplexity, anthropic). Confidence promotes to B with a second task plus a fourth provider on the next wave.

History

Measurement timeline.

Each wave appends; nothing overwrites. Frozen Wave Rule.

  1. Entry · 01

    26 May 2026

    Wave · Protocol

    WAVE-Q2-2026-W8-AEROSPACE-DEFENSE

    ars-methodology/v1.1

    Wave 8 dispatch. Cody Gate-1 audit and Giorgio a fleet wave ceiling pulls launched 2026-05-26. Pre-measurement state: yaml seeded with frozen task (MTU Maintenance Hannover · PW1100G-JM MRO for A320neo), close-state quote_ready, locked spec markers per spec-fidelity rule (PW1100G-JM vs V2500/GE9X, A320neo vs A330/787, MTU 18% stake).

  2. Entry · 02

    13 Jun 2026

    Wave · Protocol

    WAVE-Q2-2026-W8-AEROSPACE-DEFENSE

    ars-methodology/v1.1

    Wave 8 partial measurement landed. Cody Gate-1 complete (D 52.50, 18/18 valid). a fleet wave Phase 1 ceiling + Phase 2 HTTP+coding complete, both classes success: the full locked chain (PW1100G-JM, A320neo application, Hannover MRO, quote pathway) resolves on brand-owned pages over plain HTTP. Phase 3 browser + Phase 4 ACT not executed in this wave (fleet browser runtime infrastructure-blocked, not a brand result; marked pending in agent_matrix, re-run scheduled). Brand flipped to scored at partial-FLEET.

Sources

Evidence and provenance.

Public methodology references and internal evidence pointers behind every claim above.

  1. [S1]

    Gate-1 audit run · MTU Aero Engines Wave Q2 2026 (Cody, dispatched 2026-05-26)

    Accessed · 26 May 2026

    Internal · Hyperize evidence

    • · AI Visibility score
    • · the close state reached (quote_ready)
  2. [S2]

    a fleet wave aerospace + defence wave · MTU phase 1-4 (Giorgio repo, dispatched 2026-05-26)

    Accessed · 26 May 2026

    Internal · Hyperize evidence

    • · the per-breed access profile (Phase 1-4 pending)
  3. Accessed · 26 May 2026

    Public · hyperize.ai

    • · fairness declaration
    • · Third-Party Interception framing
Last updated · 13 Jun 2026 Next review · 30 Sept 2026 Wave · Q2-2026-W8-AEROSPACE-DEFENSE Tier · proprietary Confidence · C Index score · 4.8/10 Machine-readable record

Editorial coverage

The DAX 40 Agent Success Index is a point-in-time snapshot of the agent-success of public digital touchpoints. Results are not statements about product quality, company performance, service quality, or the legal obligations of the brands named. Brand names and logos remain the property of their respective owners and are used solely for identification and reporting purposes in the context of editorial coverage (§ 23 MarkenG, Art. 5 GG).

Brands wishing to respond, engage, or correct a factual error may contact hello@hyperize.ai. Responses received are published in full alongside the findings. Full methodology and editorial-coverage notice: coverage statement.