Not currently tracked · last seen 2h ago
- Flights observed
- 297 showing last 50
- Avg flight time
- 3h 47m
- Typical route
- MAN → AYT
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 21:50 UTC | Jul 14, 02:15 UTC | 4h 25m |
| 2026-07-13 | MAN → AYT | Jul 13, 16:35 UTC | Jul 13, 20:25 UTC | 3h 50m |
| 2026-07-13 | - | Jul 13, 11:15 UTC | Jul 13, 14:40 UTC | 3h 25m |
| 2026-07-13 | - | Jul 13, 06:20 UTC | Jul 13, 09:20 UTC | 3h 0m |
| 2026-07-12 | LCA → MAN | Jul 12, 21:55 UTC | Jul 13, 02:35 UTC | 4h 40m |
| 2026-07-12 | - | Jul 12, 16:10 UTC | Jul 12, 20:15 UTC | 4h 5m |
| 2026-07-12 | - | Jul 12, 11:05 UTC | Jul 12, 14:25 UTC | 3h 20m |
| 2026-07-12 | - | Jul 12, 06:15 UTC | Jul 12, 09:20 UTC | 3h 5m |
| 2026-07-11 | - | Jul 11, 21:40 UTC | Jul 12, 01:10 UTC | 3h 30m |
| 2026-07-11 | - | Jul 11, 16:00 UTC | Jul 11, 19:55 UTC | 3h 55m |
| 2026-07-11 | - | Jul 11, 10:15 UTC | Jul 11, 12:30 UTC | 2h 15m |
| 2026-07-11 | - | Jul 11, 06:55 UTC | Jul 11, 08:50 UTC | 1h 55m |
| 2026-07-10 | MAN → MAN | Jul 10, 09:10 UTC | Jul 10, 21:45 UTC | 12h 35m |
| 2026-07-10 | - | Jul 10, 00:55 UTC | Jul 10, 04:35 UTC | 3h 40m |
| 2026-07-09 | - | Jul 9, 20:30 UTC | Jul 9, 23:25 UTC | 2h 55m |
| 2026-07-09 | MLA → MAN | Jul 9, 10:00 UTC | Jul 9, 13:15 UTC | 3h 15m |
| 2026-07-09 | MAN → MLA | Jul 9, 05:40 UTC | Jul 9, 08:45 UTC | 3h 5m |
| 2026-07-08 | - | Jul 8, 14:35 UTC | Jul 8, 19:25 UTC | 4h 50m |
| 2026-07-08 | - | Jul 8, 08:20 UTC | Jul 8, 12:30 UTC | 4h 10m |
| 2026-07-08 | - | Jul 8, 03:15 UTC | Jul 8, 06:50 UTC | 3h 35m |
| 2026-07-07 | - | Jul 7, 22:45 UTC | Jul 8, 02:05 UTC | 3h 20m |
| 2026-07-07 | - | Jul 7, 11:20 UTC | Jul 7, 14:45 UTC | 3h 25m |
| 2026-07-07 | MAN → EFL | Jul 7, 06:55 UTC | Jul 7, 10:00 UTC | 3h 5m |
| 2026-07-06 | - | Jul 6, 22:10 UTC | Jul 7, 02:30 UTC | 4h 20m |
| 2026-07-06 | MAN → AYT | Jul 6, 16:40 UTC | Jul 6, 20:30 UTC | 3h 50m |
| 2026-07-06 | - | Jul 6, 11:05 UTC | Jul 6, 14:40 UTC | 3h 35m |
| 2026-07-06 | MAN → JSI | Jul 6, 06:30 UTC | Jul 6, 09:30 UTC | 3h 0m |
| 2026-07-05 | MAN → SID | Jul 5, 21:10 UTC | Jul 6, 01:15 UTC | 4h 5m |
| 2026-07-05 | MAN → KGS | Jul 5, 16:05 UTC | Jul 5, 19:40 UTC | 3h 35m |
| 2026-07-05 | CWL → REU | Jul 5, 10:55 UTC | Jul 5, 14:35 UTC | 3h 40m |
| 2026-07-05 | MAN → ZTH | Jul 5, 06:20 UTC | Jul 5, 09:25 UTC | 3h 5m |
| 2026-07-04 | - | Jul 4, 21:10 UTC | Jul 5, 01:05 UTC | 3h 55m |
| 2026-07-04 | - | Jul 4, 15:20 UTC | Jul 4, 19:20 UTC | 4h 0m |
| 2026-07-04 | - | Jul 4, 11:30 UTC | Jul 4, 13:55 UTC | 2h 25m |
| 2026-07-04 | - | Jul 4, 07:00 UTC | Jul 4, 09:25 UTC | 2h 25m |
| 2026-07-03 | BOH → ACE | Jul 3, 21:50 UTC | Jul 4, 00:25 UTC | 2h 35m |
| 2026-07-03 | BRS → AGP | Jul 3, 17:35 UTC | Jul 3, 20:05 UTC | 2h 30m |
| 2026-07-03 | - | Jul 3, 12:00 UTC | Jul 3, 15:40 UTC | 3h 40m |
| 2026-07-03 | - | Jul 3, 06:50 UTC | Jul 3, 09:55 UTC | 3h 5m |
| 2026-07-02 | KGS → NCL | Jul 2, 18:55 UTC | Jul 2, 23:05 UTC | 4h 10m |
| 2026-07-02 | NCL → KGS | Jul 2, 13:55 UTC | Jul 2, 17:45 UTC | 3h 50m |
| 2026-07-02 | - | Jul 2, 09:35 UTC | Jul 2, 12:25 UTC | 2h 50m |
| 2026-07-02 | - | Jul 2, 05:20 UTC | Jul 2, 08:00 UTC | 2h 40m |
| 2026-07-01 | NCL → NCL | Jul 1, 13:45 UTC | Jul 2, 02:25 UTC | 12h 40m |
| 2026-07-01 | - | Jul 1, 09:45 UTC | Jul 1, 12:25 UTC | 2h 40m |
| 2026-07-01 | - | Jul 1, 05:15 UTC | Jul 1, 07:25 UTC | 2h 10m |
| 2026-06-30 | - | Jun 30, 22:05 UTC | Jul 1, 02:20 UTC | 4h 15m |
| 2026-06-30 | - | Jun 30, 16:00 UTC | Jun 30, 19:50 UTC | 3h 50m |
| 2026-06-30 | - | Jun 30, 10:45 UTC | Jun 30, 14:05 UTC | 3h 20m |
| 2026-06-30 | - | Jun 30, 05:10 UTC | Jun 30, 08:30 UTC | 3h 20m |
Specifications
| Registration | G-TUMY |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 407FAF · 20077657 (octal) |
Looking for transponder-level data? View the Mode-S 407FAF page for country allocation, callsign history, and ADS-B signal details.
G-TUMY frequently asked
What type of aircraft is G-TUMY?
G-TUMY is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for G-TUMY?
G-TUMY broadcasts on Mode-S (ICAO 24-bit) address 407FAF (octal 20077657). View the transponder page.
What route does G-TUMY typically fly?
G-TUMY most frequently flies between MAN and AYT based on observed flights.
Where is G-TUMY right now?
G-TUMY is not currently being tracked; last seen 2h ago.