Not currently tracked · last seen 3h ago
- Flights observed
- 270 showing last 50
- Avg flight time
- 1h 12m
- Typical route
- MUC → BER
- Last seen
- 3h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | VIE → MUC | Jun 2, 19:30 UTC | Jun 2, 20:40 UTC | 1h 10m |
| 2026-06-02 | FRA → GRZ | Jun 2, 17:10 UTC | Jun 2, 18:40 UTC | 1h 30m |
| 2026-06-02 | MXP → MUC | Jun 2, 14:55 UTC | Jun 2, 15:30 UTC | 35m |
| 2026-06-02 | FRA → AMS | Jun 2, 13:35 UTC | Jun 2, 14:10 UTC | 35m |
| 2026-06-02 | FRA → LHR | Jun 2, 11:35 UTC | Jun 2, 12:15 UTC | 40m |
| 2026-06-02 | FRA → HAJ | Jun 2, 10:15 UTC | Jun 2, 10:45 UTC | 30m |
| 2026-06-02 | FRA → LHR | Jun 2, 08:00 UTC | Jun 2, 08:40 UTC | 40m |
| 2026-06-02 | STR → FRA | Jun 2, 06:25 UTC | Jun 2, 07:05 UTC | 40m |
| 2026-06-02 | LEJ → FRA | Jun 2, 04:15 UTC | Jun 2, 05:20 UTC | 1h 5m |
| 2026-06-01 | HAM → FRA | Jun 1, 20:05 UTC | Jun 1, 21:05 UTC | 1h 0m |
| 2026-06-01 | VCE → FRA | Jun 1, 16:40 UTC | Jun 1, 18:30 UTC | 1h 50m |
| 2026-06-01 | MUC → BGO | Jun 1, 13:50 UTC | Jun 1, 15:50 UTC | 2h 0m |
| 2026-06-01 | CPH → FRA | Jun 1, 09:55 UTC | Jun 1, 11:40 UTC | 1h 45m |
| 2026-06-01 | MUC → OTP | Jun 1, 07:10 UTC | Jun 1, 08:40 UTC | 1h 30m |
| 2026-06-01 | STR → MUC | Jun 1, 05:20 UTC | Jun 1, 06:05 UTC | 45m |
| 2026-05-31 | MUC → DUS | May 31, 19:35 UTC | May 31, 20:25 UTC | 50m |
| 2026-05-31 | AMS → MUC | May 31, 17:10 UTC | May 31, 18:30 UTC | 1h 20m |
| 2026-05-31 | FRA → BER | May 31, 14:10 UTC | May 31, 15:25 UTC | 1h 15m |
| 2026-05-31 | HEL → FRA | May 31, 10:05 UTC | May 31, 11:35 UTC | 1h 30m |
| 2026-05-31 | FRA → HAM | May 31, 08:25 UTC | May 31, 09:05 UTC | 40m |
| 2026-05-30 | MUC → BER | May 30, 20:15 UTC | May 30, 21:05 UTC | 50m |
| 2026-05-30 | MUC → LJU | May 30, 12:25 UTC | May 30, 13:25 UTC | 1h 0m |
| 2026-05-30 | FRA → SOF | May 30, 10:35 UTC | May 30, 11:30 UTC | 55m |
| 2026-05-30 | BER → FRA | May 30, 08:45 UTC | May 30, 09:30 UTC | 45m |
| 2026-05-30 | MUC → BER | May 30, 06:20 UTC | May 30, 07:15 UTC | 55m |
| 2026-05-30 | MUC → SUF | May 30, 04:05 UTC | May 30, 05:10 UTC | 1h 5m |
| 2026-05-29 | NAP → FRA | May 29, 20:20 UTC | May 29, 21:20 UTC | 1h 0m |
| 2026-05-29 | OVD → MUC | May 29, 17:00 UTC | May 29, 19:10 UTC | 2h 10m |
| 2026-05-29 | MUC → MAD | May 29, 13:40 UTC | May 29, 15:40 UTC | 2h 0m |
| 2026-05-29 | ZRH → MUC | May 29, 09:00 UTC | May 29, 09:45 UTC | 45m |
| 2026-05-29 | MUC → BER | May 29, 07:15 UTC | May 29, 08:05 UTC | 50m |
| 2026-05-29 | CPH → MUC | May 29, 04:15 UTC | May 29, 05:25 UTC | 1h 10m |
| 2026-05-28 | MUC → CPH | May 28, 20:15 UTC | May 28, 21:30 UTC | 1h 15m |
| 2026-05-28 | BUD → FRA | May 28, 18:10 UTC | May 28, 19:00 UTC | 50m |
| 2026-05-28 | FRA → MAN | May 28, 16:20 UTC | May 28, 17:10 UTC | 50m |
| 2026-05-28 | LCY → FRA | May 28, 13:30 UTC | May 28, 15:15 UTC | 1h 45m |
| 2026-05-28 | MUC → ARN | May 28, 10:15 UTC | May 28, 12:15 UTC | 2h 0m |
| 2026-05-28 | FRA → BER | May 28, 08:20 UTC | May 28, 09:05 UTC | 45m |
| 2026-05-28 | FRA → SUF | May 28, 06:30 UTC | May 28, 07:25 UTC | 55m |
| 2026-05-28 | ATH → FRA | May 28, 04:15 UTC | May 28, 05:20 UTC | 1h 5m |
| 2026-05-27 | FRA → FCO | May 27, 20:30 UTC | May 27, 21:25 UTC | 55m |
| 2026-05-27 | ATH → FRA | May 27, 16:30 UTC | May 27, 18:45 UTC | 2h 15m |
| 2026-05-27 | TRS → FRA | May 27, 13:30 UTC | May 27, 15:30 UTC | 2h 0m |
| 2026-05-27 | FRA → DUB | May 27, 09:55 UTC | May 27, 11:45 UTC | 1h 50m |
| 2026-05-27 | FRA → HAM | May 27, 07:00 UTC | May 27, 08:55 UTC | 1h 55m |
| 2026-05-27 | STR → MUC | May 27, 04:30 UTC | May 27, 05:29 UTC | 1h 0m |
| 2026-05-26 | FRA → HEL | May 26, 19:25 UTC | May 26, 20:15 UTC | 50m |
| 2026-05-26 | FRA → HAJ | May 26, 16:00 UTC | May 26, 17:59 UTC | 2h 0m |
| 2026-05-26 | FRA → CPH | May 26, 13:04 UTC | May 26, 15:05 UTC | 2h 0m |
| 2026-05-26 | ZRH → MUC | May 26, 09:09 UTC | May 26, 09:49 UTC | 40m |
Specifications
| Registration | D-AIZP |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 3C6750 · 17063520 (octal) |
Looking for transponder-level data? View the Mode-S 3C6750 page for country allocation, callsign history, and ADS-B signal details.
D-AIZP frequently asked
What type of aircraft is D-AIZP?
D-AIZP is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for D-AIZP?
D-AIZP broadcasts on Mode-S (ICAO 24-bit) address 3C6750 (octal 17063520). View the transponder page.
What route does D-AIZP typically fly?
D-AIZP most frequently flies between MUC and BER based on observed flights.
Where is D-AIZP right now?
D-AIZP is not currently being tracked; last seen 3h ago.