Flight
OMA931
Flight history and live tracking for OMA931, operated by Oman Air. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Oman Air |
| Typical origin | OOMS SEEB INTERNATIONAL |
| Typical destination | OOKB KHASAB |
| Distance | 191 nm |
Flight history 41 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (41) - back to 2025-08-19
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-02-25 | OOMS | OOKB | 07:42 +04 | 08:24 +04 | 0h 41m | A4O-MI |
| 2026-02-24 | OOMS | OOKB | 07:34 +04 | 08:14 +04 | 0h 39m | A4O-MD |
| 2026-02-22 | OOMS | OOKB | 08:21 +04 | 09:08 +04 | 0h 47m | A4O-ME |
| 2026-02-17estimated | OOMS | ? | 07:40 +04 | 04:22Z | 0h 41m | A4O-MD |
| 2026-02-16estimated | OOMS | ? | 10:44 +04 | 07:26Z | 0h 41m | A4O-BAA |
| 2026-02-15 | OOMS | OOKB | 08:33 +04 | 09:26 +04 | 0h 52m | 70C11F |
| 2026-02-11 | OOMS | OOKB | 07:42 +04 | 08:26 +04 | 0h 43m | A4O-MB |
| 2026-02-04 | OOMS | OOKB | 07:38 +04 | 08:32 +04 | 0h 54m | A4O-MD |
| 2026-02-03 | OOMS | OOKB | 07:33 +04 | 08:32 +04 | 0h 58m | A4O-MI |
| 2026-02-02 | OOMS | OOKB | 07:46 +04 | 08:34 +04 | 0h 47m | A4O-MD |
| 2026-02-01 | OOMS | OOKB | 10:16 +04 | 11:10 +04 | 0h 53m | A4O-MM |
| 2026-01-28estimated | OOMS | ? | 07:40 +04 | 04:26Z | 0h 45m | A4O-ME |
| 2026-01-27estimated | OOMS | ? | 07:49 +04 | 04:24Z | 0h 34m | A4O-MA |
| 2026-01-26estimated | OOMS | ? | 07:43 +04 | 04:32Z | 0h 48m | A4O-MG |
| 2026-01-25estimated | OOMS | ? | 08:29 +04 | 05:24Z | 0h 54m | A4O-MJ |
| 2026-01-21estimated | OOMS | ? | 07:48 +04 | 04:38Z | 0h 50m | A4O-MK |
| 2026-01-20 | OOMS | OOKB | 07:38 +04 | 08:28 +04 | 0h 49m | A4O-MB |
| 2026-01-19 | OOMS | OOKB | 07:45 +04 | 08:40 +04 | 0h 54m | A4O-MF |
| 2026-01-07estimated | OOMS | ? | 07:41 +04 | 04:30Z | 0h 48m | A4O-MJ |
| 2026-01-06estimated | OOMS | ? | 07:36 +04 | 04:20Z | 0h 43m | A4O-MB |
| 2026-01-05estimated | OOMS | ? | 07:40 +04 | 04:30Z | 0h 49m | 70C109 |
| 2026-01-04estimated | OOMS | ? | 08:41 +04 | 05:20Z | 0h 38m | 70C11C |
| 2025-12-31estimated | OOMS | ? | 07:43 +04 | 04:28Z | 0h 44m | A4O-BAE |
| 2025-12-29estimated | OOMS | ? | 09:44 +04 | 06:32Z | 0h 47m | A4O-MB |
| 2025-12-28estimated | OOMS | ? | 11:15 +04 | 08:00Z | 0h 44m | A4O-MB |
| 2025-12-24 | OOMS | OOKB | 07:46 +04 | 08:38 +04 | 0h 51m | A4O-BAE |
| 2025-12-23estimated | OOMS | ? | 10:52 +04 | 07:30Z | 0h 37m | A4O-MD |
| 2025-12-22estimated | OOMS | ? | 07:41 +04 | 04:34Z | 0h 52m | A4O-MD |
| 2025-12-21estimated | OOMS | ? | 14:07 +04 | 11:00Z | 0h 53m | 70C11D |
| 2025-12-17partial | OOMS | ? | 07:47 +04 | A4O-BAA | ||
| 2025-12-15estimated | OOMS | ? | 07:41 +04 | 04:26Z | 0h 44m | A4O-BAA |
| 2025-12-10 | OOMS | OOKB | 10:38 +04 | 11:24 +04 | 0h 45m | A4O-MM |
| 2025-10-15 | OOMS | OOKB | 07:46 +04 | 08:40 +04 | 0h 53m | A4O-MC |
| 2025-10-14 | OOMS | OOKB | 07:39 +04 | 08:34 +04 | 0h 54m | A4O-BAB |
| 2025-10-13 | OOMS | OOKB | 07:31 +04 | 08:20 +04 | 0h 48m | A4O-MB |
| 2025-10-08 | OOMS | OOKB | 07:36 +04 | 08:22 +04 | 0h 46m | A4O-MB |
| 2025-10-07 | OOMS | OOKB | 12:17 +04 | 13:10 +04 | 0h 52m | 70C11D |
| 2025-10-06 | OOMS | OOKB | 07:28 +04 | 08:18 +04 | 0h 49m | A4O-BAA |
| 2025-08-26partial | OOKB | ? | 06:44 +04 | A4O-BAB | ||
| 2025-08-20estimated | ? | ? | 06:19Z | 06:54Z | 0h 34m | A4O-MH |
| 2025-08-19estimated | ? | OOKB | 07:55Z | 12:20 +04 | 0h 25m | A4O-BAB |
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 OMA931 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]