Flight
TLM616
Flight history and live tracking for TLM616, operated by Thai Lion Air. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Thai Lion Air |
| Observed route | VTBD → VTBL |
Flight history 54 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21partial | VTBD | ? | 19:05 +07 | HS-LGI | ||
| 2026-08-20partial | VTBD | ? | 18:08 +07 | 8832DA | ||
| 2026-08-18partial | VTBD | ? | 18:58 +07 | 8830ED | ||
| 2026-08-12partial | VTBD | ? | 12:36 +07 | 8830F3 |
Earlier flights (50) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23partial | VTBD | ? | 18:55 +07 | HS-LUU | ||
| 2026-07-22partial | VTBD | ? | 19:05 +07 | HS-LUV | ||
| 2026-07-21partial | VTBD | ? | 19:00 +07 | 8830F7 | ||
| 2026-07-15partial | VTBD | ? | 18:53 +07 | HS-LUU | ||
| 2026-07-10partial | VTBD | ? | 19:03 +07 | HS-LUV | ||
| 2026-07-08partial | VTBD | ? | 18:55 +07 | 8830EF | ||
| 2026-07-07partial | VTBD | ? | 18:57 +07 | HS-LUU | ||
| 2026-07-05partial | VTBD | ? | 19:04 +07 | 8830F7 | ||
| 2026-07-03partial | VTBD | ? | 18:59 +07 | HS-LUJ | ||
| 2026-07-02partial | VTBD | ? | 10:11 +07 | HS-LUV | ||
| 2026-06-30partial | VTBD | ? | 18:52 +07 | 8830F7 | ||
| 2026-06-29partial | VTBD | ? | 18:48 +07 | HS-LUP | ||
| 2026-06-28estimated | VTBD | VTPN | 18:57 +07 | 19:24 +07 | 0h 26m | 8830ED |
| 2026-06-27partial | VTBD | ? | 18:50 +07 | 8830F6 | ||
| 2026-06-26partial | VTBD | ? | 18:50 +07 | 8830F7 | ||
| 2026-06-25estimated | VTBD | VTPI | 19:10 +07 | 21:11 +07 | 2h 01m | 8830EF |
| 2026-06-22partial | VTBD | ? | 07:25 +07 | 8830EF | ||
| 2026-06-21partial | VTBD | ? | 18:54 +07 | 8830EF | ||
| 2026-06-16partial | VTBD | ? | 18:59 +07 | 8830F3 | ||
| 2026-06-14partial | VTBD | ? | 18:57 +07 | 8832D0 | ||
| 2026-06-12partial | VTBD | ? | 19:01 +07 | 8830EB | ||
| 2026-05-29partial | VTBD | ? | 19:23 +07 | HS-LUP | ||
| 2026-05-24partial | VTBD | ? | 18:56 +07 | 8830F7 | ||
| 2026-05-22partial | VTBD | ? | 19:04 +07 | HS-LUV | ||
| 2026-05-19partial | VTBD | ? | 09:52 +07 | HS-LUP | ||
| 2026-05-11partial | VTBD | ? | 19:03 +07 | 8830EB | ||
| 2026-05-10partial | VTBD | ? | 18:59 +07 | 8830F3 | ||
| 2026-05-09partial | VTBD | ? | 19:36 +07 | 8832E8 | ||
| 2026-05-08partial | VTBD | ? | 19:17 +07 | 8832D2 | ||
| 2026-05-07partial | VTBD | ? | 18:54 +07 | HS-LUU | ||
| 2026-05-06 | VTBD | VTBL | 18:50 +07 | 21:01 +07 | 2h 10m | 8830F4 |
| 2026-05-04partial | VTBD | ? | 19:24 +07 | 8832CF | ||
| 2026-05-03estimated | VTBD | VTBL | 19:02 +07 | 21:14 +07 | 2h 11m | 8830F3 |
| 2026-05-02partial | VTBD | ? | 19:00 +07 | 8830F1 | ||
| 2026-05-01partial | VTBD | ? | 18:56 +07 | 8830EA | ||
| 2026-04-28partial | VTBD | ? | 19:05 +07 | 8830EF | ||
| 2026-04-26partial | VTBD | ? | 19:42 +07 | 8830F6 | ||
| 2026-04-25partial | VTBD | ? | 19:00 +07 | 8830EC | ||
| 2026-04-23partial | VTBD | ? | 18:58 +07 | HS-LUV | ||
| 2026-04-22partial | VTBD | ? | 19:20 +07 | HS-LVK | ||
| 2026-04-21partial | VTBD | ? | 19:03 +07 | 8832CC | ||
| 2026-04-19partial | VTBD | ? | 19:36 +07 | HS-LUQ | ||
| 2026-04-18partial | VTBD | ? | 18:58 +07 | 8832CC | ||
| 2026-04-16partial | VTBD | ? | 19:25 +07 | 8832E8 | ||
| 2026-04-11partial | VTBD | ? | 19:22 +07 | 8832D4 | ||
| 2026-03-29partial | VTBD | ? | 19:31 +07 | 8830EC | ||
| 2026-03-16partial | VTBD | ? | 19:50 +07 | 8830EC | ||
| 2026-03-15partial | VTBD | ? | 19:58 +07 | HS-LTT | ||
| 2026-03-14partial | VTBD | ? | 18:52 +07 | 8830EA | ||
| 2026-03-13partial | VTBD | ? | 19:01 +07 | 8830F1 |
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]