Flight
QTR1G
Flight history and live tracking for QTR1G, 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 | OMDB → OTHH |
Flight history 51 flights since Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-05 | OMDB | OTHH | 23:31 +04 | 23:08 +03 | 0h 36m | A7-BHA |
| 2026-10-04estimated | ? | ? | 19:47Z | 20:10Z | 0h 22m | 6A12C |
| 2026-10-03estimated | ? | ? | 19:03Z | 20:22Z | 1h 18m | 6A372 |
| 2026-10-02partial | OMDB | ? | 23:28 +04 | A7-BOA | ||
| 2026-10-01 | OMDB | OTHH | 23:42 +04 | 23:31 +03 | 0h 49m | A7-ANQ |
| 2026-09-30estimated | OMDB | OTHH | 16:37 +04 | 23:26 +03 | 7h 48m | 6A11E |
| 2026-09-29partial | ? | ? | 01:15Z | 6A079 | ||
| 2026-09-28partial | ? | ? | 01:24Z | 6A0F7 | ||
| 2026-09-27 | OMDB | OTHH | 23:31 +04 | 23:18 +03 | 0h 47m | A7-ALC |
| 2026-09-26partial | OMDB | ? | 05:13 +04 | 6A11D | ||
| 2026-09-25estimated | ? | ? | 06:16Z | 20:02Z | 13h 45m | 6A373 |
| 2026-09-24 | OMDB | OTHH | 00:11 +04 | 23:50 +03 | 0h 38m | A7-BOB |
| 2026-09-23partial | OMDB | ? | 11:13 +04 | 6A125 | ||
| 2026-09-22partial | OMDB | ? | 23:39 +04 | A7-ANI | ||
| 2026-09-21partial | OMDB | ? | 23:35 +04 | A7-ANK | ||
| 2026-09-17partial | OMDB | ? | 23:55 +04 | 6A2FB | ||
| 2026-09-16partial | OMDB | ? | 23:30 +04 | 6A07E | ||
| 2026-09-15partial | OMDB | ? | 23:36 +04 | 6A0E9 | ||
| 2026-09-14partial | OMDB | ? | 23:46 +04 | 6A07E | ||
| 2026-09-09partial | OMDB | ? | 23:49 +04 | 6A122 | ||
| 2026-09-08partial | OMDB | ? | 23:38 +04 | 6A102 | ||
| 2026-09-06partial | OMDB | ? | 23:47 +04 | 6A07D |
Earlier flights (29) - back to 2026-06-21
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-04partial | ? | ? | 00:28Z | 6A38C | ||
| 2026-09-03partial | ? | ? | 00:38Z | 6A122 | ||
| 2026-08-31estimated | ? | ? | 07:10Z | 20:06Z | 12h 55m | 6A12B |
| 2026-08-30partial | OMDB | ? | 23:38 +04 | 6A12B | ||
| 2026-08-29partial | OMDB | ? | 23:41 +04 | 6A0BA | ||
| 2026-08-28partial | OMDB | ? | 23:52 +04 | 6A0F5 | ||
| 2026-08-27partial | OMDB | ? | 23:29 +04 | 6A12B | ||
| 2026-08-25estimated | ? | ? | 08:40Z | 20:02Z | 11h 22m | 6A0E9 |
| 2026-08-23partial | OMDB | ? | 00:02 +04 | 6A0E9 | ||
| 2026-08-22partial | OMDB | ? | 23:31 +04 | 6A073 | ||
| 2026-08-20partial | OMDB | ? | 23:31 +04 | 6A12E | ||
| 2026-08-14partial | ? | ? | 00:30Z | 6A2FA | ||
| 2026-08-13estimated | ? | ? | 06:38Z | 19:58Z | 13h 19m | 6A12D |
| 2026-08-12partial | ? | ? | 01:25Z | 6A128 | ||
| 2026-08-11partial | OMDB | ? | 23:33 +04 | 6A128 | ||
| 2026-07-23partial | OMDB | ? | 23:29 +04 | 6A0A9 | ||
| 2026-07-15partial | OMDB | ? | 23:32 +04 | 6A12B | ||
| 2026-07-14partial | OMDB | ? | 23:55 +04 | 6A11F | ||
| 2026-07-13estimated | OMDB | ? | 12:32 +04 | 19:58Z | 11h 25m | 6A0F4 |
| 2026-07-12estimated | SBGR | ? | 09:52 -03 | 19:46Z | 6h 53m | 6A11E |
| 2026-07-03partial | OMDB | ? | 23:33 +04 | 6A0B3 | ||
| 2026-06-29partial | OMDB | ? | 23:34 +04 | 6A068 | ||
| 2026-06-28estimated | OMDB | ? | 10:10 +04 | 20:04Z | 13h 54m | 6A10B |
| 2026-06-27estimated | OMDB | ? | 12:18 +04 | 19:44Z | 11h 25m | 6A128 |
| 2026-06-26partial | OMDB | ? | 23:42 +04 | 6A128 | ||
| 2026-06-25estimated | OMDB | ? | 06:59 +04 | 19:56Z | 16h 56m | 6A073 |
| 2026-06-23partial | OMDB | ? | 23:36 +04 | 6A2B6 | ||
| 2026-06-22partial | OMDB | ? | 23:38 +04 | 6A066 | ||
| 2026-06-21partial | OMDB | ? | 23:37 +04 | 6A12E |
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 QTR1G 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 archive (from $9.99, with a free one-day sample). Questions: [email protected]