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