Flight
TLM532
Flight history and live tracking for TLM532, 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 → VTPP |
Flight history 50 flights since Feb 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-18partial | VTBD | ? | 08:23 +07 | HS-LTT |
Earlier flights (49) - back to 2026-02-15
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22partial | VTBD | ? | 08:37 +07 | 8832D2 | ||
| 2026-07-11partial | VTBD | ? | 08:16 +07 | 8832D6 | ||
| 2026-07-10partial | VTBD | ? | 08:18 +07 | 8832DA | ||
| 2026-07-09partial | VTBD | ? | 08:16 +07 | 8832EA | ||
| 2026-07-08partial | VTBD | ? | 08:08 +07 | 8832CC | ||
| 2026-07-07partial | VTBD | ? | 08:11 +07 | 8832DA | ||
| 2026-07-06 | VTBD | VTPP | 08:17 +07 | 10:48 +07 | 2h 30m | 8832D5 |
| 2026-07-05estimated | VTBD | VTPP | 08:21 +07 | 10:46 +07 | 2h 25m | 8832EA |
| 2026-07-04estimated | VTBD | VTBL | 08:03 +07 | 11:06 +07 | 3h 02m | 8832D2 |
| 2026-07-03partial | VTBD | ? | 08:08 +07 | 8832CC | ||
| 2026-07-01estimated | VTBD | VTBL | 08:29 +07 | 11:08 +07 | 2h 38m | 8832CC |
| 2026-06-27partial | VTBD | ? | 08:13 +07 | HS-LGI | ||
| 2026-06-26partial | VTBD | ? | 08:10 +07 | 8830F1 | ||
| 2026-06-20partial | VTBD | ? | 08:09 +07 | 8830F3 | ||
| 2026-05-29partial | VTBD | ? | 08:13 +07 | 8830F4 | ||
| 2026-05-25partial | VTBD | ? | 08:18 +07 | 8830F6 | ||
| 2026-05-22partial | VTBD | ? | 08:08 +07 | HS-LUP | ||
| 2026-05-21estimated | VTBD | VTBL | 08:14 +07 | 10:50 +07 | 2h 35m | HS-LUJ |
| 2026-05-19partial | VTBD | ? | 08:35 +07 | 8830F6 | ||
| 2026-05-12 | VTBD | VTPN | 08:15 +07 | 10:39 +07 | 2h 24m | HS-LUP |
| 2026-05-11partial | VTBD | ? | 08:22 +07 | 8830F6 | ||
| 2026-05-10estimated | VTBD | VTPN | 08:17 +07 | 10:46 +07 | 2h 28m | HS-LUQ |
| 2026-05-09partial | VTBD | ? | 08:25 +07 | 8830EC | ||
| 2026-05-08partial | VTBD | ? | 08:48 +07 | 8832CF | ||
| 2026-05-07 | VTBD | VTPP | 08:23 +07 | 10:45 +07 | 2h 22m | HS-LVK |
| 2026-05-06 | VTBD | VTPP | 08:22 +07 | 10:50 +07 | 2h 27m | HS-LVK |
| 2026-05-05estimated | VTBD | VTPP | 08:24 +07 | 08:50 +07 | 0h 26m | 8832EA |
| 2026-05-03partial | VTBD | ? | 08:15 +07 | 8832D2 | ||
| 2026-05-02estimated | VTBD | VTBL | 08:29 +07 | 11:06 +07 | 2h 36m | 8832DA |
| 2026-05-01estimated | VTBD | VTPI | 08:31 +07 | 11:14 +07 | 2h 42m | 8832D3 |
| 2026-04-30partial | VTBD | ? | 08:35 +07 | 8832CC | ||
| 2026-04-28 | VTBD | VTPP | 08:19 +07 | 10:50 +07 | 2h 30m | 8832EA |
| 2026-04-25estimated | VTBD | VTPP | 08:23 +07 | 10:46 +07 | 2h 22m | HS-LUQ |
| 2026-04-24partial | VTBD | ? | 08:23 +07 | HS-LTT | ||
| 2026-04-22partial | VTBD | ? | 08:21 +07 | 8832D2 | ||
| 2026-04-21partial | VTBD | ? | 08:25 +07 | 8832D0 | ||
| 2026-04-17partial | VTBD | ? | 08:48 +07 | 8832D4 | ||
| 2026-04-16partial | VTBD | ? | 08:29 +07 | 8832D0 | ||
| 2026-04-11partial | VTBD | ? | 08:23 +07 | 8832CC | ||
| 2026-04-04partial | VTBD | ? | 08:33 +07 | 8830EC | ||
| 2026-04-03partial | VTBD | ? | 08:51 +07 | HS-LTT | ||
| 2026-04-02partial | VTBD | ? | 08:29 +07 | 8832D2 | ||
| 2026-03-29partial | VTBD | ? | 08:32 +07 | 8830F7 | ||
| 2026-03-16partial | VTBD | ? | 08:58 +07 | 8832CF | ||
| 2026-03-15partial | VTBD | ? | 08:20 +07 | HS-LVK | ||
| 2026-03-13partial | VTBD | ? | 08:32 +07 | 8832CF | ||
| 2026-03-12partial | VTBD | ? | 08:52 +07 | 8832CF | ||
| 2026-02-16partial | VTBD | ? | 08:47 +07 | 8832D0 | ||
| 2026-02-15 | VTBD | VTBL | 08:19 +07 | 11:03 +07 | 2h 44m | 8832BA |
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]