Not currently tracked · last seen 4h ago
- Flights observed
- 211 showing last 50
- Avg flight time
- 6h 49m
- Typical route
- ATL → MAN
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 17:30 UTC | Jul 14, 00:25 UTC | 6h 55m |
| 2026-07-13 | - | Jul 13, 03:10 UTC | Jul 13, 11:20 UTC | 8h 10m |
| 2026-07-12 | LHR → MIA | Jul 12, 15:25 UTC | Jul 13, 00:25 UTC | 9h 0m |
| 2026-07-12 | - | Jul 12, 03:01 UTC | Jul 12, 11:01 UTC | 8h 0m |
| 2026-07-11 | LHR → MIA | Jul 11, 15:55 UTC | Jul 12, 00:45 UTC | 8h 50m |
| 2026-07-11 | YYZ → LHR | Jul 11, 06:55 UTC | Jul 11, 13:35 UTC | 6h 40m |
| 2026-07-10 | - | Jul 10, 21:20 UTC | Jul 11, 04:40 UTC | 7h 20m |
| 2026-07-10 | IAD → LHR | Jul 10, 03:25 UTC | Jul 10, 10:05 UTC | 6h 40m |
| 2026-07-09 | - | Jul 9, 17:15 UTC | Jul 10, 01:00 UTC | 7h 45m |
| 2026-07-09 | IAD → LHR | Jul 9, 03:10 UTC | Jul 9, 10:20 UTC | 7h 10m |
| 2026-07-08 | - | Jul 8, 17:20 UTC | Jul 9, 00:45 UTC | 7h 25m |
| 2026-07-08 | IAD → LHR | Jul 8, 03:20 UTC | Jul 8, 10:25 UTC | 7h 5m |
| 2026-07-07 | - | Jul 7, 17:20 UTC | Jul 8, 00:40 UTC | 7h 20m |
| 2026-07-07 | - | Jul 7, 03:25 UTC | Jul 7, 10:05 UTC | 6h 40m |
| 2026-07-06 | LHR → YYZ | Jul 6, 17:20 UTC | Jul 7, 00:30 UTC | 7h 10m |
| 2026-07-06 | IAD → LHR | Jul 6, 04:25 UTC | Jul 6, 11:10 UTC | 6h 45m |
| 2026-07-05 | - | Jul 5, 17:35 UTC | Jul 6, 01:55 UTC | 8h 20m |
| 2026-07-05 | SEA → LHR | Jul 5, 02:00 UTC | Jul 5, 10:45 UTC | 8h 45m |
| 2026-07-04 | - | Jul 4, 12:10 UTC | Jul 4, 21:50 UTC | 9h 40m |
| 2026-07-04 | - | Jul 4, 08:40 UTC | Jul 4, 10:00 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 23:55 UTC | Jul 4, 00:15 UTC | 20m |
| 2026-07-03 | - | Jul 3, 21:35 UTC | Jul 3, 21:55 UTC | 20m |
| 2026-07-03 | - | Jul 3, 19:30 UTC | Jul 3, 19:50 UTC | 20m |
| 2026-07-03 | - | Jul 3, 11:30 UTC | Jul 3, 12:30 UTC | 1h 0m |
| 2026-07-02 | - | Jul 2, 23:20 UTC | Jul 3, 07:30 UTC | 8h 10m |
| 2026-07-02 | - | Jul 2, 11:10 UTC | Jul 2, 20:00 UTC | 8h 50m |
| 2026-07-02 | - | Jul 2, 00:40 UTC | Jul 2, 08:45 UTC | 8h 5m |
| 2026-07-01 | - | Jul 1, 12:20 UTC | Jul 1, 21:05 UTC | 8h 45m |
| 2026-07-01 | - | Jul 1, 08:25 UTC | Jul 1, 09:40 UTC | 1h 15m |
| 2026-06-30 | - | Jun 30, 09:05 UTC | Jul 1, 09:00 UTC | 23h 55m |
| 2026-06-30 | - | Jun 30, 08:55 UTC | Jun 30, 10:00 UTC | 1h 5m |
| 2026-06-29 | - | Jun 29, 22:39 UTC | Jun 30, 05:10 UTC | 6h 30m |
| 2026-06-29 | - | Jun 29, 10:50 UTC | Jun 29, 17:49 UTC | 7h 0m |
| 2026-06-29 | LHR → MAN | Jun 29, 08:09 UTC | Jun 29, 08:50 UTC | 40m |
| 2026-06-28 | ATL → MAN | Jun 28, 22:24 UTC | Jun 29, 05:40 UTC | 7h 15m |
| 2026-06-28 | MAN → ATL | Jun 28, 10:30 UTC | Jun 28, 18:49 UTC | 8h 20m |
| 2026-06-28 | JFK → MAN | Jun 28, 00:35 UTC | Jun 28, 06:30 UTC | 5h 55m |
| 2026-06-27 | MAN → JFK | Jun 27, 14:14 UTC | Jun 27, 21:04 UTC | 6h 50m |
| 2026-06-26 | ATL → MAN | Jun 26, 23:55 UTC | Jun 27, 07:19 UTC | 7h 25m |
| 2026-06-26 | MAN → ATL | Jun 26, 12:29 UTC | Jun 26, 20:55 UTC | 8h 25m |
| 2026-06-25 | ATL → MAN | Jun 25, 23:55 UTC | Jun 26, 07:00 UTC | 7h 5m |
| 2026-06-25 | MAN → ATL | Jun 25, 12:19 UTC | Jun 25, 20:59 UTC | 8h 40m |
| 2026-06-25 | JFK → MAN | Jun 25, 00:40 UTC | Jun 25, 06:25 UTC | 5h 45m |
| 2026-06-24 | MAN → JFK | Jun 24, 14:39 UTC | Jun 24, 21:50 UTC | 7h 10m |
| 2026-06-23 | ATL → MAN | Jun 23, 23:55 UTC | Jun 24, 07:10 UTC | 7h 15m |
| 2026-06-23 | MAN → ATL | Jun 23, 12:20 UTC | Jun 23, 20:59 UTC | 8h 40m |
| 2026-06-23 | ATL → MAN | Jun 23, 00:09 UTC | Jun 23, 07:40 UTC | 7h 30m |
| 2026-06-22 | MAN → ATL | Jun 22, 12:15 UTC | Jun 22, 20:44 UTC | 8h 30m |
| 2026-06-22 | - | Jun 22, 00:44 UTC | Jun 22, 06:39 UTC | 5h 55m |
| 2026-06-21 | MAN → JFK | Jun 21, 14:19 UTC | Jun 21, 21:05 UTC | 6h 45m |
Specifications
| Registration | G-VGEM |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 406814 · 20064024 (octal) |
Looking for transponder-level data? View the Mode-S 406814 page for country allocation, callsign history, and ADS-B signal details.
G-VGEM frequently asked
What type of aircraft is G-VGEM?
G-VGEM is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for G-VGEM?
G-VGEM broadcasts on Mode-S (ICAO 24-bit) address 406814 (octal 20064024). View the transponder page.
What route does G-VGEM typically fly?
G-VGEM most frequently flies between ATL and MAN based on observed flights.
Where is G-VGEM right now?
G-VGEM is not currently being tracked; last seen 4h ago.