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