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