Flight
TOM236
Flight history and live tracking for TOM236, 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 | LTBS DALAMAN |
| Distance | 1,633 nm |
Flight history 15 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-19estimated | ? | ? | 17:43Z | 20:40Z | 2h 56m | G-TUMG |
| 2026-08-12estimated | ? | ? | 16:44Z | 22:38Z | 5h 53m | G-TUML |
Earlier flights (13) - back to 2026-04-15
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22estimated | ? | ? | 16:41Z | 22:24Z | 5h 43m | 408314 |
| 2026-07-15estimated | ? | ? | 17:15Z | 22:36Z | 5h 21m | 407F96 |
| 2026-07-08 | EGCC | LTBS | 17:42 BST | 01:13 +03 | 5h 31m | G-TUMB |
| 2026-07-01estimated | EGCC | LTBS | 17:56 BST | 23:50 +03 | 3h 53m | G-TUMT |
| 2026-06-24estimated | EGCC | ? | 17:19 BST | 22:08Z | 5h 49m | 40832A |
| 2026-06-17 | EGCC | LTBS | 17:28 BST | 23:08 +03 | 3h 40m | G-TUMT |
| 2026-05-27 | EGCD | LTBS | 17:32 BST | 01:01 +03 | 5h 28m | G-TUML |
| 2026-05-20 | EGCC | LTBS | 17:38 BST | 23:20 +03 | 3h 41m | 408040 |
| 2026-05-19estimated | EGCC | LTBS | 04:41 BST | 07:30 +03 | 0h 48m | 408314 |
| 2026-05-06estimated | EGCC | LTBS | 17:25 BST | 23:14 +03 | 3h 48m | G-TUMB |
| 2026-04-29estimated | LOWS | LTBS | 17:29 CEST | 22:16 +03 | 3h 47m | 4082E6 |
| 2026-04-22estimated | ? | ? | 13:53Z | 19:16Z | 5h 22m | G-TAWY |
| 2026-04-15estimated | EGCC | LTBS | 14:48 BST | 20:50 +03 | 4h 01m | G-TAWM |
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]