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