Not currently tracked · last seen 2h ago
- Flights observed
- 116 showing last 50
- Avg flight time
- 3h 19m
- Typical route
- DMM → CAI
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | CAI → TIF | Jun 2, 18:05 UTC | Jun 2, 18:20 UTC | 15m |
| 2026-06-02 | JED → CAI | Jun 2, 15:45 UTC | Jun 2, 16:05 UTC | 20m |
| 2026-06-02 | CAI → RUH | Jun 2, 03:10 UTC | Jun 2, 08:55 UTC | 5h 45m |
| 2026-06-01 | DMM → CAI | Jun 1, 23:20 UTC | Jun 1, 23:45 UTC | 25m |
| 2026-06-01 | CAI → DMM | Jun 1, 17:55 UTC | Jun 1, 18:20 UTC | 25m |
| 2026-06-01 | JED → CAI | Jun 1, 14:50 UTC | Jun 1, 15:05 UTC | 15m |
| 2026-06-01 | RUH → CAI | Jun 1, 02:25 UTC | Jun 1, 08:05 UTC | 5h 40m |
| 2026-05-31 | DMM → CAI | May 31, 22:00 UTC | May 31, 22:35 UTC | 35m |
| 2026-05-31 | DMM → CAI | May 31, 19:45 UTC | May 31, 19:55 UTC | 10m |
| 2026-05-31 | RUH → CAI | May 31, 08:25 UTC | May 31, 14:05 UTC | 5h 40m |
| 2026-05-30 | CAI → RUH | May 30, 22:10 UTC | May 30, 22:40 UTC | 30m |
| 2026-05-30 | DMM → CAI | May 30, 19:45 UTC | May 30, 20:20 UTC | 35m |
| 2026-05-30 | - | May 30, 17:50 UTC | May 30, 18:00 UTC | 10m |
| 2026-05-30 | CAI → DMM | May 30, 16:10 UTC | May 30, 16:25 UTC | 15m |
| 2026-05-30 | CAI → DMM | May 30, 14:15 UTC | May 30, 14:35 UTC | 20m |
| 2026-05-30 | CAI → RUH | May 30, 06:15 UTC | May 30, 12:05 UTC | 5h 50m |
| 2026-05-29 | TUU → CAI | May 29, 16:25 UTC | May 29, 19:40 UTC | 3h 15m |
| 2026-05-29 | CAI → RUH | May 29, 03:10 UTC | May 29, 08:55 UTC | 5h 45m |
| 2026-05-28 | CAI → DMM | May 28, 17:30 UTC | May 28, 23:40 UTC | 6h 10m |
| 2026-05-28 | RUH → CAI | May 28, 09:45 UTC | May 28, 15:30 UTC | 5h 45m |
| 2026-05-28 | CAI → RUH | May 28, 02:10 UTC | May 28, 07:40 UTC | 5h 30m |
| 2026-05-27 | TUU → CAI | May 27, 17:05 UTC | May 27, 20:00 UTC | 2h 55m |
| 2026-05-27 | JED → CAI | May 27, 10:30 UTC | May 27, 15:00 UTC | 4h 30m |
| 2026-05-27 | CAI → RUH | May 27, 02:49 UTC | May 27, 08:25 UTC | 5h 36m |
| 2026-05-27 | - | May 27, 00:39 UTC | May 27, 01:05 UTC | 25m |
| 2026-05-26 | - | May 26, 20:24 UTC | May 26, 20:54 UTC | 30m |
| 2026-05-26 | RUH → CAI | May 26, 12:14 UTC | May 26, 17:44 UTC | 5h 30m |
| 2026-05-26 | DMM → CAI | May 26, 04:00 UTC | May 26, 09:55 UTC | 5h 55m |
| 2026-05-26 | DMM → CAI | May 26, 01:49 UTC | May 26, 02:10 UTC | 20m |
| 2026-05-25 | CAI → DMM | May 25, 19:59 UTC | May 25, 22:05 UTC | 2h 5m |
| 2026-05-25 | - | May 25, 12:50 UTC | May 25, 17:10 UTC | 4h 20m |
| 2026-05-25 | CAI → DMM | May 25, 04:10 UTC | May 25, 10:20 UTC | 6h 10m |
| 2026-05-24 | CAI → RUH | May 24, 20:35 UTC | May 25, 02:25 UTC | 5h 50m |
| 2026-05-24 | DMM → CAI | May 24, 12:30 UTC | May 24, 18:55 UTC | 6h 25m |
| 2026-05-24 | DMM → CAI | May 24, 09:10 UTC | May 24, 09:35 UTC | 25m |
| 2026-05-24 | CAI → DMM | May 24, 03:20 UTC | May 24, 03:40 UTC | 20m |
| 2026-05-23 | TIF → CAI | May 23, 22:50 UTC | May 23, 23:15 UTC | 25m |
| 2026-05-23 | - | May 23, 11:55 UTC | May 23, 16:00 UTC | 4h 5m |
| 2026-05-23 | DMM → CAI | May 23, 03:30 UTC | May 23, 09:30 UTC | 6h 0m |
| 2026-05-22 | CAI → RUH | May 22, 19:35 UTC | May 23, 02:00 UTC | 6h 25m |
| 2026-05-22 | RUH → CAI | May 22, 11:40 UTC | May 22, 17:35 UTC | 5h 55m |
| 2026-05-22 | CAI → DMM | May 22, 03:35 UTC | May 22, 09:40 UTC | 6h 5m |
| 2026-05-21 | CAI → RUH | May 21, 20:15 UTC | May 22, 01:50 UTC | 5h 35m |
| 2026-05-21 | DMM → CAI | May 21, 18:10 UTC | May 21, 18:30 UTC | 20m |
| 2026-05-21 | DMM → CAI | May 21, 04:15 UTC | May 21, 10:15 UTC | 6h 0m |
| 2026-05-20 | RUH → CAI | May 20, 20:10 UTC | May 21, 02:10 UTC | 6h 0m |
| 2026-05-20 | DMM → CAI | May 20, 13:45 UTC | May 20, 18:25 UTC | 4h 40m |
| 2026-05-20 | CAI → DMM | May 20, 03:55 UTC | May 20, 04:15 UTC | 20m |
| 2026-05-19 | TIF → CAI | May 19, 17:40 UTC | May 19, 22:30 UTC | 4h 50m |
| 2026-05-19 | - | May 19, 11:00 UTC | May 19, 15:35 UTC | 4h 35m |
Specifications
| Registration | SU-BQL |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 0101B2 · 00200662 (octal) |
Looking for transponder-level data? View the Mode-S 0101B2 page for country allocation, callsign history, and ADS-B signal details.
SU-BQL frequently asked
What type of aircraft is SU-BQL?
SU-BQL is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for SU-BQL?
SU-BQL broadcasts on Mode-S (ICAO 24-bit) address 0101B2 (octal 00200662). View the transponder page.
What route does SU-BQL typically fly?
SU-BQL most frequently flies between DMM and CAI based on observed flights.
Where is SU-BQL right now?
SU-BQL is not currently being tracked; last seen 2h ago.