Airborne now · flying as OCN3TG at 36,000 ft
- Flights observed
- 295 showing last 50
- Avg flight time
- 2h 29m
- Typical route
- IBZ → MUC
- Last seen
- 1h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 16:10 UTC | Jul 14, 16:30 UTC | 20m |
| 2026-07-14 | - | Jul 14, 12:35 UTC | Jul 14, 14:40 UTC | 2h 5m |
| 2026-07-14 | MIR → MUC | Jul 14, 07:10 UTC | Jul 14, 09:10 UTC | 2h 0m |
| 2026-07-14 | MUC → MIR | Jul 14, 04:20 UTC | Jul 14, 06:05 UTC | 1h 45m |
| 2026-07-13 | - | Jul 13, 17:05 UTC | Jul 13, 19:30 UTC | 2h 25m |
| 2026-07-13 | MUC → JMK | Jul 13, 13:55 UTC | Jul 13, 16:05 UTC | 2h 10m |
| 2026-07-13 | - | Jul 13, 10:10 UTC | Jul 13, 12:40 UTC | 2h 30m |
| 2026-07-13 | - | Jul 13, 06:35 UTC | Jul 13, 08:35 UTC | 2h 0m |
| 2026-07-12 | LCA → MUC | Jul 12, 17:40 UTC | Jul 12, 20:55 UTC | 3h 15m |
| 2026-07-12 | - | Jul 12, 13:20 UTC | Jul 12, 16:15 UTC | 2h 55m |
| 2026-07-12 | - | Jul 12, 08:40 UTC | Jul 12, 12:01 UTC | 3h 20m |
| 2026-07-12 | - | Jul 12, 04:20 UTC | Jul 12, 07:15 UTC | 2h 55m |
| 2026-07-11 | FNC → MUC | Jul 11, 16:55 UTC | Jul 11, 20:25 UTC | 3h 30m |
| 2026-07-11 | MUC → FNC | Jul 11, 11:55 UTC | Jul 11, 15:55 UTC | 4h 0m |
| 2026-07-11 | - | Jul 11, 07:20 UTC | Jul 11, 09:05 UTC | 1h 45m |
| 2026-07-11 | - | Jul 11, 04:25 UTC | Jul 11, 06:15 UTC | 1h 50m |
| 2026-07-10 | ZTH → MUC | Jul 10, 16:30 UTC | Jul 10, 18:35 UTC | 2h 5m |
| 2026-07-10 | MUC → ZTH | Jul 10, 13:30 UTC | Jul 10, 15:20 UTC | 1h 50m |
| 2026-07-10 | IBZ → MUC | Jul 10, 10:20 UTC | Jul 10, 12:15 UTC | 1h 55m |
| 2026-07-10 | MUC → IBZ | Jul 10, 07:05 UTC | Jul 10, 09:10 UTC | 2h 5m |
| 2026-07-09 | - | Jul 9, 16:05 UTC | Jul 9, 20:00 UTC | 3h 55m |
| 2026-07-09 | - | Jul 9, 10:10 UTC | Jul 9, 14:25 UTC | 4h 15m |
| 2026-07-08 | - | Jul 8, 11:45 UTC | Jul 8, 14:15 UTC | 2h 30m |
| 2026-07-08 | - | Jul 8, 07:30 UTC | Jul 8, 10:30 UTC | 3h 0m |
| 2026-07-06 | IBZ → MUC | Jul 6, 17:05 UTC | Jul 6, 19:15 UTC | 2h 10m |
| 2026-07-06 | MUC → IBZ | Jul 6, 14:05 UTC | Jul 6, 15:55 UTC | 1h 50m |
| 2026-07-06 | - | Jul 6, 10:20 UTC | Jul 6, 12:45 UTC | 2h 25m |
| 2026-07-06 | - | Jul 6, 06:30 UTC | Jul 6, 08:35 UTC | 2h 5m |
| 2026-07-05 | - | Jul 5, 17:35 UTC | Jul 5, 21:00 UTC | 3h 25m |
| 2026-07-05 | - | Jul 5, 13:20 UTC | Jul 5, 16:15 UTC | 2h 55m |
| 2026-07-05 | - | Jul 5, 08:25 UTC | Jul 5, 11:40 UTC | 3h 15m |
| 2026-07-05 | - | Jul 5, 04:15 UTC | Jul 5, 07:05 UTC | 2h 50m |
| 2026-07-04 | KGS → MUC | Jul 4, 17:55 UTC | Jul 4, 20:25 UTC | 2h 30m |
| 2026-07-04 | HER → FRA | Jul 4, 14:40 UTC | Jul 4, 16:50 UTC | 2h 10m |
| 2026-07-04 | - | Jul 4, 10:55 UTC | Jul 4, 13:20 UTC | 2h 25m |
| 2026-07-04 | - | Jul 4, 07:20 UTC | Jul 4, 09:30 UTC | 2h 10m |
| 2026-07-03 | LPA → MUC | Jul 3, 17:10 UTC | Jul 3, 21:15 UTC | 4h 5m |
| 2026-07-03 | MUC → LPA | Jul 3, 11:25 UTC | Jul 3, 15:35 UTC | 4h 10m |
| 2026-07-03 | - | Jul 3, 08:10 UTC | Jul 3, 10:05 UTC | 1h 55m |
| 2026-07-03 | - | Jul 3, 04:45 UTC | Jul 3, 06:15 UTC | 1h 30m |
| 2026-07-02 | - | Jul 2, 16:45 UTC | Jul 2, 19:00 UTC | 2h 15m |
| 2026-07-02 | - | Jul 2, 13:05 UTC | Jul 2, 15:20 UTC | 2h 15m |
| 2026-07-02 | - | Jul 2, 10:00 UTC | Jul 2, 11:55 UTC | 1h 55m |
| 2026-07-02 | - | Jul 2, 07:00 UTC | Jul 2, 08:40 UTC | 1h 40m |
| 2026-07-01 | - | Jul 1, 16:40 UTC | Jul 1, 19:55 UTC | 3h 15m |
| 2026-07-01 | - | Jul 1, 11:25 UTC | Jul 1, 14:30 UTC | 3h 5m |
| 2026-07-01 | - | Jul 1, 08:15 UTC | Jul 1, 10:00 UTC | 1h 45m |
| 2026-07-01 | - | Jul 1, 04:05 UTC | Jul 1, 05:50 UTC | 1h 45m |
| 2026-06-30 | IBZ → MUC | Jun 30, 17:15 UTC | Jun 30, 19:15 UTC | 2h 0m |
| 2026-06-30 | MUC → IBZ | Jun 30, 13:50 UTC | Jun 30, 15:45 UTC | 1h 55m |
Specifications
| Registration | D-AIWB |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 3C66E2 · 17063342 (octal) |
Looking for transponder-level data? View the Mode-S 3C66E2 page for country allocation, callsign history, and ADS-B signal details.
D-AIWB frequently asked
What type of aircraft is D-AIWB?
D-AIWB is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for D-AIWB?
D-AIWB broadcasts on Mode-S (ICAO 24-bit) address 3C66E2 (octal 17063342). View the transponder page.
What route does D-AIWB typically fly?
D-AIWB most frequently flies between IBZ and MUC based on observed flights.
Where is D-AIWB right now?
D-AIWB is currently airborne flying as OCN3TG. Live position is shown on the map above.