Not currently tracked · last seen 1h ago
- Flights observed
- 85 showing last 50
- Avg flight time
- 9h 10m
- Typical route
- MUC → PVG
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-03 | YUL → MUC | Jun 3, 01:10 UTC | Jun 3, 02:15 UTC | 1h 5m |
| 2026-06-02 | MUC → YUL | Jun 2, 15:25 UTC | Jun 2, 22:25 UTC | 7h 0m |
| 2026-06-02 | EWR → MUC | Jun 2, 01:05 UTC | Jun 2, 07:55 UTC | 6h 50m |
| 2026-06-01 | MUC → EWR | Jun 1, 14:35 UTC | Jun 1, 22:25 UTC | 7h 50m |
| 2026-06-01 | FRA → PMI | Jun 1, 03:30 UTC | Jun 1, 11:35 UTC | 8h 5m |
| 2026-05-31 | MUC → ORD | May 31, 15:35 UTC | Jun 1, 00:05 UTC | 8h 30m |
| 2026-05-31 | FRA → PMI | May 31, 09:15 UTC | May 31, 11:30 UTC | 2h 15m |
| 2026-05-30 | MUC → ORD | May 30, 14:25 UTC | May 30, 23:00 UTC | 8h 35m |
| 2026-05-30 | EWR → MUC | May 30, 10:20 UTC | May 30, 10:55 UTC | 35m |
| 2026-05-30 | EWR → MUC | May 30, 00:45 UTC | May 30, 08:25 UTC | 7h 40m |
| 2026-05-29 | MUC → EWR | May 29, 14:35 UTC | May 29, 22:25 UTC | 7h 50m |
| 2026-05-29 | SAN → MUC | May 29, 00:55 UTC | May 29, 11:50 UTC | 10h 55m |
| 2026-05-28 | MUC → SAN | May 28, 18:30 UTC | May 28, 22:15 UTC | 3h 45m |
| 2026-05-28 | MUC → SAN | May 28, 10:55 UTC | May 28, 13:00 UTC | 2h 5m |
| 2026-05-27 | ORD → MUC | May 27, 21:05 UTC | May 28, 05:20 UTC | 8h 15m |
| 2026-05-27 | MUC → ORD | May 27, 08:25 UTC | May 27, 17:15 UTC | 8h 50m |
| 2026-05-24 | PVG → MUC | May 24, 21:10 UTC | May 25, 03:55 UTC | 6h 45m |
| 2026-05-23 | MUC → PVG | May 23, 22:20 UTC | May 24, 21:15 UTC | 22h 55m |
| 2026-05-23 | MUC → PVG | May 23, 21:50 UTC | May 24, 00:00 UTC | 2h 10m |
| 2026-05-23 | MUC → PVG | May 23, 20:30 UTC | May 23, 21:45 UTC | 1h 15m |
| 2026-05-23 | HND → MUC | May 23, 01:00 UTC | May 23, 14:45 UTC | 13h 44m |
| 2026-05-22 | MUC → HND | May 22, 10:50 UTC | May 22, 22:30 UTC | 11h 40m |
| 2026-05-21 | PVG → MUC | May 21, 16:50 UTC | May 22, 04:00 UTC | 11h 10m |
| 2026-05-21 | PVG → MUC | May 21, 05:50 UTC | May 22, 04:00 UTC | 22h 10m |
| 2026-05-20 | MUC → PVG | May 20, 22:20 UTC | May 21, 17:10 UTC | 18h 50m |
| 2026-05-20 | MUC → PVG | May 20, 20:35 UTC | May 21, 17:10 UTC | 20h 35m |
| 2026-05-20 | HND → MUC | May 20, 01:00 UTC | May 20, 14:50 UTC | 13h 51m |
| 2026-05-19 | MUC → HND | May 19, 10:45 UTC | May 19, 22:45 UTC | 12h 0m |
| 2026-05-18 | SAN → MUC | May 18, 00:40 UTC | May 18, 11:10 UTC | 10h 30m |
| 2026-05-17 | MUC → SAN | May 17, 11:20 UTC | May 17, 22:25 UTC | 11h 5m |
| 2026-05-17 | PVG → MUC | May 17, 00:10 UTC | May 17, 04:05 UTC | 3h 55m |
| 2026-05-16 | MUC → PVG | May 16, 00:25 UTC | May 17, 00:15 UTC | 23h 51m |
| 2026-05-15 | MUC → PVG | May 15, 21:15 UTC | May 16, 01:10 UTC | 3h 55m |
| 2026-05-15 | HND → MUC | May 15, 01:35 UTC | May 15, 15:10 UTC | 13h 34m |
| 2026-05-14 | MUC → HND | May 14, 11:15 UTC | May 14, 23:20 UTC | 12h 5m |
| 2026-05-13 | HND → MUC | May 13, 00:45 UTC | May 13, 14:25 UTC | 13h 40m |
| 2026-05-12 | MUC → HND | May 12, 10:50 UTC | May 12, 22:45 UTC | 11h 55m |
| 2026-05-12 | PVG → MUC | May 12, 02:45 UTC | May 12, 03:50 UTC | 1h 5m |
| 2026-05-10 | MUC → PVG | May 10, 20:54 UTC | May 11, 00:49 UTC | 3h 55m |
| 2026-05-10 | SAN → MUC | May 10, 00:24 UTC | May 10, 11:10 UTC | 10h 45m |
| 2026-05-09 | MUC → SAN | May 9, 11:05 UTC | May 9, 22:25 UTC | 11h 20m |
| 2026-05-09 | EWR → MUC | May 9, 01:00 UTC | May 9, 08:15 UTC | 7h 15m |
| 2026-05-08 | MUC → EWR | May 8, 14:35 UTC | May 8, 22:45 UTC | 8h 10m |
| 2026-05-08 | SAN → MUC | May 8, 00:34 UTC | May 8, 11:30 UTC | 10h 55m |
| 2026-05-07 | MUC → SAN | May 7, 11:00 UTC | May 7, 21:45 UTC | 10h 45m |
| 2026-05-07 | MUC → SAN | May 7, 10:45 UTC | May 7, 10:55 UTC | 10m |
| 2026-05-07 | EWR → MUC | May 7, 00:50 UTC | May 7, 08:10 UTC | 7h 20m |
| 2026-05-06 | MUC → EWR | May 6, 14:30 UTC | May 6, 22:45 UTC | 8h 14m |
| 2026-05-06 | FRA → PMI | May 6, 03:00 UTC | May 6, 10:55 UTC | 7h 55m |
| 2026-05-05 | MUC → ORD | May 5, 13:55 UTC | May 5, 22:50 UTC | 8h 55m |
Specifications
| Registration | D-AIXY |
| Aircraft type | AIRBUS A-350-900 (A359) |
| Mode-S code | 3C6719 · 17063431 (octal) |
Looking for transponder-level data? View the Mode-S 3C6719 page for country allocation, callsign history, and ADS-B signal details.
D-AIXY frequently asked
What type of aircraft is D-AIXY?
D-AIXY is a AIRBUS A-350-900 (ICAO type code A359).
What is the Mode-S transponder code for D-AIXY?
D-AIXY broadcasts on Mode-S (ICAO 24-bit) address 3C6719 (octal 17063431). View the transponder page.
What route does D-AIXY typically fly?
D-AIXY most frequently flies between MUC and PVG based on observed flights.
Where is D-AIXY right now?
D-AIXY is not currently being tracked; last seen 1h ago.