Not currently tracked · last seen 1h ago
- Flights observed
- 520 showing last 50
- Avg flight time
- 2h 14m
- Typical route
- MAN → CDG
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 21:15 UTC | Jul 14, 00:40 UTC | 3h 25m |
| 2026-07-13 | - | Jul 13, 15:30 UTC | Jul 13, 19:45 UTC | 4h 15m |
| 2026-07-13 | MLA → MAN | Jul 13, 10:10 UTC | Jul 13, 13:40 UTC | 3h 30m |
| 2026-07-13 | MAN → MLA | Jul 13, 06:05 UTC | Jul 13, 09:00 UTC | 2h 55m |
| 2026-07-12 | CPH → MAN | Jul 12, 20:25 UTC | Jul 12, 21:55 UTC | 1h 30m |
| 2026-07-12 | MAN → CPH | Jul 12, 18:15 UTC | Jul 12, 19:35 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 16:20 UTC | Jul 12, 16:55 UTC | 35m |
| 2026-07-12 | MAN → BFS | Jul 12, 14:50 UTC | Jul 12, 15:30 UTC | 40m |
| 2026-07-12 | - | Jul 12, 10:45 UTC | Jul 12, 13:20 UTC | 2h 35m |
| 2026-07-12 | - | Jul 12, 06:35 UTC | Jul 12, 08:55 UTC | 2h 20m |
| 2026-07-11 | - | Jul 11, 18:30 UTC | Jul 11, 22:20 UTC | 3h 50m |
| 2026-07-11 | - | Jul 11, 13:30 UTC | Jul 11, 17:15 UTC | 3h 45m |
| 2026-07-11 | - | Jul 11, 09:40 UTC | Jul 11, 11:35 UTC | 1h 55m |
| 2026-07-11 | - | Jul 11, 06:01 UTC | Jul 11, 07:50 UTC | 1h 50m |
| 2026-07-10 | RHO → MAN | Jul 10, 22:00 UTC | Jul 11, 02:05 UTC | 4h 5m |
| 2026-07-10 | MAN → RHO | Jul 10, 17:05 UTC | Jul 10, 20:55 UTC | 3h 50m |
| 2026-07-10 | LIS → MAN | Jul 10, 13:25 UTC | Jul 10, 15:40 UTC | 2h 15m |
| 2026-07-10 | MAN → LIS | Jul 10, 09:45 UTC | Jul 10, 12:05 UTC | 2h 20m |
| 2026-07-09 | - | Jul 9, 20:40 UTC | Jul 9, 21:35 UTC | 55m |
| 2026-07-09 | - | Jul 9, 18:25 UTC | Jul 9, 19:20 UTC | 55m |
| 2026-07-09 | CDG → MAN | Jul 9, 16:15 UTC | Jul 9, 17:15 UTC | 1h 0m |
| 2026-07-09 | MAN → CDG | Jul 9, 14:05 UTC | Jul 9, 15:05 UTC | 1h 0m |
| 2026-07-09 | - | Jul 9, 10:00 UTC | Jul 9, 12:30 UTC | 2h 30m |
| 2026-07-09 | - | Jul 9, 05:55 UTC | Jul 9, 08:20 UTC | 2h 25m |
| 2026-07-08 | OPO → MAN | Jul 8, 23:20 UTC | Jul 9, 01:20 UTC | 2h 0m |
| 2026-07-08 | MAN → OPO | Jul 8, 19:00 UTC | Jul 8, 21:05 UTC | 2h 5m |
| 2026-07-08 | IBZ → MAN | Jul 8, 15:30 UTC | Jul 8, 17:40 UTC | 2h 10m |
| 2026-07-08 | MAN → IBZ | Jul 8, 11:55 UTC | Jul 8, 14:15 UTC | 2h 20m |
| 2026-07-08 | - | Jul 8, 09:35 UTC | Jul 8, 10:35 UTC | 1h 0m |
| 2026-07-08 | - | Jul 8, 07:10 UTC | Jul 8, 08:20 UTC | 1h 10m |
| 2026-07-07 | - | Jul 7, 22:05 UTC | Jul 7, 23:50 UTC | 1h 45m |
| 2026-07-07 | MAN → CPH | Jul 7, 19:15 UTC | Jul 7, 20:50 UTC | 1h 35m |
| 2026-07-07 | BHD → MAN | Jul 7, 17:35 UTC | Jul 7, 18:10 UTC | 35m |
| 2026-07-07 | - | Jul 7, 16:10 UTC | Jul 7, 16:45 UTC | 35m |
| 2026-07-07 | MAN → MAN | Jul 7, 06:30 UTC | Jul 7, 15:10 UTC | 8h 40m |
| 2026-07-06 | - | Jul 6, 20:40 UTC | Jul 6, 21:45 UTC | 1h 5m |
| 2026-07-06 | MAN → CDG | Jul 6, 18:30 UTC | Jul 6, 19:35 UTC | 1h 5m |
| 2026-07-06 | - | Jul 6, 14:45 UTC | Jul 6, 17:15 UTC | 2h 30m |
| 2026-07-06 | - | Jul 6, 11:30 UTC | Jul 6, 13:50 UTC | 2h 20m |
| 2026-07-06 | - | Jul 6, 08:35 UTC | Jul 6, 10:25 UTC | 1h 50m |
| 2026-07-06 | MAN → BER | Jul 6, 06:00 UTC | Jul 6, 07:30 UTC | 1h 30m |
| 2026-07-05 | - | Jul 5, 21:00 UTC | Jul 5, 22:40 UTC | 1h 40m |
| 2026-07-05 | MAN → BER | Jul 5, 18:15 UTC | Jul 5, 19:50 UTC | 1h 35m |
| 2026-07-05 | - | Jul 5, 15:40 UTC | Jul 5, 16:50 UTC | 1h 10m |
| 2026-07-05 | MAN → CDG | Jul 5, 13:25 UTC | Jul 5, 14:30 UTC | 1h 5m |
| 2026-07-05 | GIB → MAN | Jul 5, 09:15 UTC | Jul 5, 12:15 UTC | 3h 0m |
| 2026-07-05 | MAN → GIB | Jul 5, 05:40 UTC | Jul 5, 08:15 UTC | 2h 35m |
| 2026-07-04 | - | Jul 4, 18:35 UTC | Jul 4, 22:35 UTC | 4h 0m |
| 2026-07-04 | - | Jul 4, 13:25 UTC | Jul 4, 17:25 UTC | 4h 0m |
| 2026-07-04 | FAO → MAN | Jul 4, 09:10 UTC | Jul 4, 12:00 UTC | 2h 50m |
Specifications
| Registration | G-EZUN |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 406668 · 20063150 (octal) |
Looking for transponder-level data? View the Mode-S 406668 page for country allocation, callsign history, and ADS-B signal details.
G-EZUN frequently asked
What type of aircraft is G-EZUN?
G-EZUN is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for G-EZUN?
G-EZUN broadcasts on Mode-S (ICAO 24-bit) address 406668 (octal 20063150). View the transponder page.
What route does G-EZUN typically fly?
G-EZUN most frequently flies between MAN and CDG based on observed flights.
Where is G-EZUN right now?
G-EZUN is not currently being tracked; last seen 1h ago.