Flight
TOM584
Flight history and live tracking for TOM584, 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 |
| Typical origin | EGCC MANCHESTER |
| Typical destination | LTAI ANTALYA |
| Distance | 1,690 nm |
Flight history 15 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 14:37Z | 20:42Z | 6h 04m | G-TUML |
Earlier flights (14) - back to 2026-04-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | EGCC | LTAI | 15:36 BST | 23:08 +03 | 5h 32m | 408314 |
| 2026-07-11 | EGCC | LTAI | 17:01 BST | 23:16 +03 | 4h 14m | G-FDZZ |
| 2026-07-04 | EGCC | LTAI | 15:36 BST | 21:28 +03 | 3h 52m | G-TUML |
| 2026-06-27estimated | EGCC | LTAI | 15:31 BST | 21:34 +03 | 4h 02m | 40832A |
| 2026-06-20 | EGCC | LTAI | 15:19 BST | 23:23 +03 | 6h 03m | G-TUML |
| 2026-06-13estimated | EGCC | LTAY | 15:19 BST | 21:02 +03 | 3h 42m | 407F96 |
| 2026-05-23 | EGCC | LTAH | 16:20 BST | 00:06 +03 | 5h 46m | G-TUMT |
| 2026-05-19 | EGCC | LTAH | 21:50 BST | 01:15 +03 | 1h 25m | 408314 |
| 2026-05-09estimated | EGCC | LTAY | 15:11 BST | 21:00 +03 | 3h 48m | G-TAWM |
| 2026-05-02 | EGCC | LTAH | 15:18 BST | 23:26 +03 | 6h 07m | G-TAWU |
| 2026-04-25estimated | EGCC | LTAI | 10:18 BST | 18:14 +03 | 5h 55m | G-TUIB |
| 2026-04-18estimated | ? | ? | 09:26Z | 13:00Z | 3h 33m | G-TUIF |
| 2026-04-11estimated | ? | ? | 09:13Z | 12:40Z | 3h 26m | G-TUIA |
| 2026-04-04estimated | ? | ? | 09:32Z | 13:04Z | 3h 32m | G-TUII |
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]