Flight
TOM38L
Flight history and live tracking for TOM38L, operated by TUI Airways. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | TUI Airways |
| Observed route | EGKK → GCXO |
Flight history 15 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 15:04Z | 18:52Z | 3h 47m | G-TAWG |
Earlier flights (14) - back to 2026-04-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | ? | ? | 14:07Z | 18:16Z | 4h 08m | G-TUKF |
| 2026-07-11estimated | EGKK | GCLA | 16:17 BST | 20:10 WEST | 3h 52m | G-TUKF |
| 2026-07-04 | EGKK | GCTS | 15:02 BST | 20:28 WEST | 5h 25m | G-TUKF |
| 2026-06-27estimated | EGKK | GCXO | 15:43 BST | 19:28 WEST | 3h 45m | G-TUKF |
| 2026-06-20 | EGKK | GCXO | 15:17 BST | 20:50 WEST | 5h 32m | G-TAWG |
| 2026-06-13estimated | EGTD | GCTS | 14:54 BST | 20:19 WEST | 5h 24m | G-TUKO |
| 2026-05-23estimated | EGKK | GCTS | 15:02 BST | 20:42 WEST | 5h 40m | G-TUKF |
| 2026-05-19estimated | EGKK | GCXO | 21:36 BST | 22:36 WEST | 0h 59m | G-TUMG |
| 2026-05-09estimated | EGKK | GCLA | 16:37 BST | 21:02 WEST | 4h 24m | 408027 |
| 2026-05-02estimated | EGKK | GCXO | 15:11 BST | 21:12 WEST | 6h 00m | 407F96 |
| 2026-04-25estimated | EGKK | GCXO | 14:59 BST | 20:43 WEST | 5h 43m | G-TAWW |
| 2026-04-18estimated | ? | ? | 14:01Z | 18:24Z | 4h 22m | 408329 |
| 2026-04-11estimated | ? | ? | 14:00Z | 18:22Z | 4h 21m | G-TUMA |
| 2026-04-04estimated | ? | ? | 14:02Z | 19:46Z | 5h 44m | G-TUMF |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]