Flight
QTR1B
Flight history and live tracking for QTR1B, operated by Qatar Airways. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Qatar Airways |
| Observed route | LTAZ → EKCH |
Flight history 15 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (15) - back to 2026-01-18
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-05-28estimated | OSPR | EKCH | 05:34 +03 | 10:57 CEST | 6h 23m | 6A2F8 |
| 2026-05-26estimated | LTAZ | EKCH | 06:19 +03 | 10:55 CEST | 5h 36m | 6A2F4 |
| 2026-05-23estimated | LTAZ | EKCH | 06:05 +03 | 10:55 CEST | 5h 49m | 6A2E9 |
| 2026-05-21estimated | LTAZ | EKCH | 06:32 +03 | 10:53 CEST | 5h 20m | 6A2F3 |
| 2026-05-20partial | EKCH | ? | 07:08 CEST | 6A2F2 | ||
| 2026-05-19estimated | LTAZ | EKCH | 09:20 +03 | 21:24 CEST | 13h 03m | 6A2EC |
| 2026-05-12 | LTAZ | EKCH | 06:19 +03 | 10:52 CEST | 5h 32m | 6A2F2 |
| 2026-02-28 | ? | OTBD | 00:58Z | 05:25 +03 | 1h 26m | 06A0FC |
| 2026-02-24 | ? | OTBD | 01:10Z | 05:31 +03 | 1h 21m | 06A106 |
| 2026-02-16 | VOHY | ? | 04:08 IST | 23:56Z | 1h 17m | 6A101 |
| 2026-02-12 | VOHY | ? | 03:51 IST | 23:49Z | 1h 27m | 6A0BC |
| 2026-02-04 | ? | OTBD | 01:21Z | 05:41 +03 | 1h 20m | 06A0A8 |
| 2026-01-27 | VOHY | ? | 03:52 IST | 23:30Z | 1h 08m | 06A0AA |
| 2026-01-20 | VOHY | ? | 03:53 IST | 23:29Z | 1h 06m | 06A0B5 |
| 2026-01-18 | VOHY | ? | 03:49 IST | 23:22Z | 1h 02m | 06A0B3 |
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.
Follow this flight
Get an email when QTR1B flies + if it runs late.
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]