On the ground · transponder active
- Flights observed
- 186 showing last 50
- Avg flight time
- 7h 58m
- Typical route
- BKK → MUC
- Last seen
- Jul 26, 20:20 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | BKK → MUC | Jul 26, 16:25 UTC | Jul 26, 20:20 UTC | 3h 55m |
| 2026-07-25 | MUC → BKK | Jul 25, 20:40 UTC | Jul 26, 06:55 UTC | 10h 16m |
| 2026-07-25 | JNB → MUC | Jul 25, 07:05 UTC | Jul 25, 17:00 UTC | 9h 55m |
| 2026-07-24 | MUC → JNB | Jul 24, 18:40 UTC | Jul 25, 04:20 UTC | 9h 40m |
| 2026-07-24 | KIX → MUC | Jul 24, 01:45 UTC | Jul 24, 14:50 UTC | 13h 5m |
| 2026-07-23 | MUC → KIX | Jul 23, 11:00 UTC | Jul 23, 22:10 UTC | 11h 10m |
| 2026-07-22 | SFO → MUC | Jul 22, 04:55 UTC | Jul 22, 15:05 UTC | 10h 10m |
| 2026-07-21 | MUC → SFO | Jul 21, 15:00 UTC | Jul 22, 02:45 UTC | 11h 45m |
| 2026-07-20 | ICN → MUC | Jul 20, 13:40 UTC | Jul 20, 17:40 UTC | 4h 0m |
| 2026-07-20 | ICN → MUC | Jul 20, 05:00 UTC | Jul 20, 05:20 UTC | 20m |
| 2026-07-20 | MUC → ICN | Jul 20, 02:10 UTC | Jul 20, 02:35 UTC | 25m |
| 2026-07-19 | MUC → ICN | Jul 19, 16:25 UTC | Jul 20, 01:25 UTC | 9h 0m |
| 2026-07-18 | BKK → MUC | Jul 18, 17:00 UTC | Jul 19, 03:25 UTC | 10h 25m |
| 2026-07-17 | MUC → BKK | Jul 17, 20:44 UTC | Jul 18, 07:00 UTC | 10h 16m |
| 2026-07-17 | - | Jul 17, 13:10 UTC | Jul 17, 17:09 UTC | 4h 0m |
| 2026-07-17 | - | Jul 17, 06:00 UTC | Jul 17, 06:15 UTC | 15m |
| 2026-07-17 | - | Jul 17, 02:50 UTC | Jul 17, 03:10 UTC | 20m |
| 2026-07-16 | - | Jul 16, 18:10 UTC | Jul 16, 21:25 UTC | 3h 15m |
| 2026-07-16 | - | Jul 16, 04:20 UTC | Jul 16, 15:25 UTC | 11h 5m |
| 2026-07-16 | - | Jul 16, 03:00 UTC | Jul 16, 03:30 UTC | 30m |
| 2026-07-15 | - | Jul 15, 14:45 UTC | Jul 16, 00:50 UTC | 10h 5m |
| 2026-07-15 | - | Jul 15, 02:20 UTC | Jul 15, 11:45 UTC | 9h 25m |
| 2026-07-14 | - | Jul 14, 13:55 UTC | Jul 15, 00:05 UTC | 10h 9m |
| 2026-07-14 | - | Jul 14, 00:35 UTC | Jul 14, 11:05 UTC | 10h 30m |
| 2026-07-13 | - | Jul 13, 10:50 UTC | Jul 13, 22:10 UTC | 11h 20m |
| 2026-07-12 | DEN → MUC | Jul 12, 22:10 UTC | Jul 13, 07:35 UTC | 9h 25m |
| 2026-07-12 | MUC → DEN | Jul 12, 10:10 UTC | Jul 12, 20:01 UTC | 9h 50m |
| 2026-07-11 | - | Jul 11, 20:40 UTC | Jul 12, 04:40 UTC | 8h 0m |
| 2026-07-11 | MUC → BOM | Jul 11, 10:40 UTC | Jul 11, 17:55 UTC | 7h 15m |
| 2026-07-10 | - | Jul 10, 20:25 UTC | Jul 11, 04:25 UTC | 8h 0m |
| 2026-07-10 | MUC → BOM | Jul 10, 10:45 UTC | Jul 10, 17:50 UTC | 7h 5m |
| 2026-07-09 | - | Jul 9, 15:05 UTC | Jul 10, 03:05 UTC | 12h 0m |
| 2026-07-08 | - | Jul 8, 20:35 UTC | Jul 9, 08:10 UTC | 11h 35m |
| 2026-07-08 | - | Jul 8, 07:00 UTC | Jul 8, 17:15 UTC | 10h 15m |
| 2026-07-07 | - | Jul 7, 18:40 UTC | Jul 8, 04:10 UTC | 9h 30m |
| 2026-07-07 | - | Jul 7, 11:30 UTC | Jul 7, 15:35 UTC | 4h 5m |
| 2026-07-07 | - | Jul 7, 03:15 UTC | Jul 7, 03:30 UTC | 15m |
| 2026-07-07 | - | Jul 7, 00:10 UTC | Jul 7, 00:30 UTC | 20m |
| 2026-07-06 | - | Jul 6, 14:15 UTC | Jul 6, 23:25 UTC | 9h 10m |
| 2026-07-05 | - | Jul 5, 20:50 UTC | Jul 6, 05:10 UTC | 8h 20m |
| 2026-07-05 | - | Jul 5, 10:55 UTC | Jul 5, 18:35 UTC | 7h 40m |
| 2026-07-04 | - | Jul 4, 20:45 UTC | Jul 5, 05:00 UTC | 8h 15m |
| 2026-07-04 | - | Jul 4, 10:45 UTC | Jul 4, 18:05 UTC | 7h 20m |
| 2026-07-03 | - | Jul 3, 15:10 UTC | Jul 4, 03:30 UTC | 12h 20m |
| 2026-07-02 | - | Jul 2, 20:45 UTC | Jul 3, 07:45 UTC | 11h 0m |
| 2026-07-02 | - | Jul 2, 05:55 UTC | Jul 2, 16:25 UTC | 10h 30m |
| 2026-07-01 | MUC → MEX | Jul 1, 15:00 UTC | Jul 2, 03:00 UTC | 12h 0m |
| 2026-07-01 | - | Jul 1, 02:40 UTC | Jul 1, 12:25 UTC | 9h 45m |
| 2026-06-30 | MUC → SEA | Jun 30, 14:15 UTC | Jun 30, 23:55 UTC | 9h 40m |
| 2026-06-29 | - | Jun 29, 21:05 UTC | Jun 30, 06:15 UTC | 9h 11m |
Specifications
| Registration | D-AIXO |
| Aircraft type | AIRBUS A-350-900 (A359) |
| Mode-S code | 3C670F · 17063417 (octal) |
Looking for transponder-level data? View the Mode-S 3C670F page for country allocation, callsign history, and ADS-B signal details.
D-AIXO frequently asked
What type of aircraft is D-AIXO?
D-AIXO is a AIRBUS A-350-900 (ICAO type code A359).
What is the Mode-S transponder code for D-AIXO?
D-AIXO broadcasts on Mode-S (ICAO 24-bit) address 3C670F (octal 17063417). View the transponder page.
What route does D-AIXO typically fly?
D-AIXO most frequently flies between BKK and MUC based on observed flights.
Where is D-AIXO right now?
D-AIXO is currently on the ground with its transponder active.