sensors Mode-S transponder
8966B0
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-AQQ · AIRBUS A-320
- Hex
- 8966B0
- Octal
- 42263260
- Decimal
- 9,004,720
- Country
- AE
- Tail
- A6-AQQ
- Type
- A320
- Flights observed
- 226
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8966B0 falls within the block assigned to United Arab Emirates (AE) by ICAO Annex 10, Volume III. Every aircraft registered in United Arab Emirates receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJL849 | Fly Jinnah | 31 | 2026-07-26 |
| FJL678 | Fly Jinnah | 22 | 2026-07-25 |
| FJL870 | - | 21 | 2026-07-16 |
| FJL674 | - | 21 | 2026-07-10 |
| FJL871 | - | 20 | 2026-07-15 |
| FJL675 | Fly Jinnah | 17 | 2026-07-24 |
| FJL679 | Fly Jinnah | 15 | 2026-07-21 |
| FJL673 | - | 13 | 2026-07-05 |
| FJL866 | Fly Jinnah | 12 | 2026-07-22 |
| FJL865 | - | 11 | 2026-07-20 |
| FJL821 | - | 6 | 2026-07-13 |
| FJL672 | - | 6 | 2026-07-07 |
| FJL811 | Fly Jinnah | 5 | 2026-07-04 |
| FJL670 | Fly Jinnah | 5 | 2026-06-02 |
| FJL676 | Fly Jinnah | 4 | 2026-05-05 |
| FJL845 | Fly Jinnah | 3 | 2026-05-28 |
| FJL810 | Fly Jinnah | 2 | 2026-07-24 |
| FJL744 | Fly Jinnah | 2 | 2026-04-27 |
| FJL741 | Fly Jinnah | 2 | 2026-04-27 |
| FJL847 | Fly Jinnah | 1 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJL849 | LHE → KHI | Jul 26, 05:55 UTC | Jul 26, 17:25 UTC | 11h 31m |
| 2026-07-25 | FJL678 | KHI → ISB | Jul 25, 17:05 UTC | Jul 26, 04:25 UTC | 11h 20m |
| 2026-07-24 | FJL810 | KHI → LYP | Jul 24, 16:55 UTC | Jul 25, 11:15 UTC | 18h 20m |
| 2026-07-24 | FJL810 | KHI → LYP | Jul 24, 14:50 UTC | Jul 25, 11:15 UTC | 20h 25m |
| 2026-07-24 | FJL675 | ISB → KHI | Jul 24, 11:45 UTC | Jul 25, 07:45 UTC | 20h 0m |
| 2026-07-24 | FJL675 | ISB → KHI | Jul 24, 09:45 UTC | Jul 25, 07:45 UTC | 22h 0m |
| 2026-07-24 | FJL849 | LHE → KHI | Jul 24, 06:05 UTC | Jul 25, 05:40 UTC | 23h 35m |
| 2026-07-23 | FJL678 | KHI → ISB | Jul 23, 17:10 UTC | Jul 23, 19:35 UTC | 2h 25m |
| 2026-07-22 | FJL675 | ISB → KHI | Jul 22, 20:15 UTC | Jul 22, 20:25 UTC | 10m |
| 2026-07-22 | FJL866 | PEW → KHI | Jul 22, 12:10 UTC | Jul 22, 15:25 UTC | 3h 15m |
| 2026-07-21 | FJL679 | ISB → KHI | Jul 21, 19:20 UTC | Jul 22, 15:25 UTC | 20h 5m |
| 2026-07-21 | FJL678 | KHI → ISB | Jul 21, 17:25 UTC | Jul 22, 15:25 UTC | 22h 0m |
| 2026-07-21 | FJL820 | KHI → SKT | Jul 21, 05:35 UTC | Jul 21, 19:30 UTC | 13h 55m |
| 2026-07-20 | FJL675 | - | Jul 20, 17:35 UTC | Jul 21, 13:30 UTC | 19h 55m |
| 2026-07-20 | FJL675 | - | Jul 20, 15:25 UTC | Jul 21, 13:30 UTC | 22h 4m |
| 2026-07-20 | FJL675 | - | Jul 20, 10:05 UTC | Jul 21, 07:50 UTC | 21h 45m |
| 2026-07-20 | FJL865 | - | Jul 20, 09:55 UTC | Jul 21, 07:50 UTC | 21h 55m |
| 2026-07-20 | FJL849 | LHE → KHI | Jul 20, 06:05 UTC | Jul 21, 05:45 UTC | 23h 39m |
| 2026-07-19 | FJL743 | SHJ → ISB | Jul 19, 16:45 UTC | Jul 20, 04:40 UTC | 11h 55m |
| 2026-07-17 | FJL849 | - | Jul 17, 06:20 UTC | Jul 17, 18:10 UTC | 11h 50m |
| 2026-07-16 | FJL679 | - | Jul 16, 17:10 UTC | Jul 17, 04:49 UTC | 11h 40m |
| 2026-07-16 | FJL870 | - | Jul 16, 11:40 UTC | Jul 16, 12:00 UTC | 20m |
| 2026-07-15 | FJL678 | - | Jul 15, 17:35 UTC | Jul 15, 20:00 UTC | 2h 25m |
| 2026-07-15 | FJL871 | - | Jul 15, 12:45 UTC | Jul 15, 12:55 UTC | 10m |
| 2026-07-15 | FJL870 | - | Jul 15, 11:20 UTC | Jul 15, 11:35 UTC | 15m |
| 2026-07-15 | FJL849 | - | Jul 15, 07:45 UTC | Jul 15, 08:15 UTC | 30m |
| 2026-07-14 | FJL675 | - | Jul 14, 10:05 UTC | Jul 15, 04:50 UTC | 18h 44m |
| 2026-07-14 | FJL849 | - | Jul 14, 06:15 UTC | Jul 15, 04:50 UTC | 22h 34m |
| 2026-07-13 | FJL821 | - | Jul 13, 07:15 UTC | Jul 14, 04:50 UTC | 21h 35m |
| 2026-07-12 | FJL866 | - | Jul 12, 11:20 UTC | Jul 13, 06:01 UTC | 18h 40m |
| 2026-07-12 | FJL865 | - | Jul 12, 09:25 UTC | Jul 13, 06:01 UTC | 20h 35m |
| 2026-07-12 | FJL865 | - | Jul 12, 06:15 UTC | Jul 13, 06:01 UTC | 23h 45m |
| 2026-07-12 | FJL849 | - | Jul 12, 05:50 UTC | Jul 12, 16:55 UTC | 11h 5m |
| 2026-07-11 | FJL678 | - | Jul 11, 12:45 UTC | Jul 12, 04:25 UTC | 15h 40m |
| 2026-07-11 | FJL821 | - | Jul 11, 07:35 UTC | Jul 11, 11:10 UTC | 3h 35m |
| 2026-07-10 | FJL674 | - | Jul 10, 11:40 UTC | Jul 11, 05:50 UTC | 18h 10m |
| 2026-07-10 | FJL674 | - | Jul 10, 09:40 UTC | Jul 11, 05:50 UTC | 20h 10m |
| 2026-07-10 | FJL849 | - | Jul 10, 06:05 UTC | Jul 11, 05:50 UTC | 23h 45m |
| 2026-07-09 | FJL866 | - | Jul 9, 11:40 UTC | Jul 10, 04:25 UTC | 16h 45m |
| 2026-07-09 | FJL865 | - | Jul 9, 09:40 UTC | Jul 10, 04:25 UTC | 18h 45m |
| 2026-07-08 | FJL849 | - | Jul 8, 06:25 UTC | Jul 8, 17:55 UTC | 11h 30m |
| 2026-07-07 | FJL672 | - | Jul 7, 10:45 UTC | Jul 8, 04:30 UTC | 17h 45m |
| 2026-07-07 | FJL821 | - | Jul 7, 07:30 UTC | Jul 8, 04:30 UTC | 21h 0m |
| 2026-07-06 | FJL675 | - | Jul 6, 11:30 UTC | Jul 7, 05:50 UTC | 18h 20m |
| 2026-07-06 | FJL675 | - | Jul 6, 09:35 UTC | Jul 7, 05:50 UTC | 20h 15m |
| 2026-07-06 | FJL675 | - | Jul 6, 06:05 UTC | Jul 7, 05:50 UTC | 23h 45m |
| 2026-07-05 | FJL673 | - | Jul 5, 10:40 UTC | Jul 6, 04:20 UTC | 17h 40m |
| 2026-07-05 | FJL821 | - | Jul 5, 07:25 UTC | Jul 5, 19:55 UTC | 12h 30m |
| 2026-07-04 | FJL811 | LYP → KHI | Jul 4, 12:40 UTC | Jul 5, 05:55 UTC | 17h 15m |
| 2026-07-03 | FJL678 | - | Jul 3, 17:10 UTC | Jul 4, 07:35 UTC | 14h 25m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the A6-AQQ page for operator, model, and routing details .