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