sensors Mode-S transponder
717C99
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBC · AIRBUS A-320neo
- Hex
- 717C99
- Octal
- 34276231
- Decimal
- 7,437,465
- Country
- SA
- Tail
- HZ-FBC
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 13
- Country
- SA
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 717C99 falls within the block assigned to Saudi Arabia (SA) by ICAO Annex 10, Volume III. Every aircraft registered in Saudi Arabia 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD775 | Rog-Air | 10 | 2026-05-24 |
| FAD771 | Rog-Air | 8 | 2026-05-21 |
| FAD776 | Rog-Air | 6 | 2026-05-24 |
| FAD772 | Rog-Air | 2 | 2026-05-13 |
| FAD608 | Rog-Air | 2 | 2026-05-27 |
| FAD607 | Rog-Air | 2 | 2026-05-26 |
| FAD764 | - | 1 | 2026-04-13 |
| FAD763 | Rog-Air | 1 | 2026-04-13 |
| FAD756 | Rog-Air | 1 | 2026-04-17 |
| FAD6798 | - | 1 | 2026-05-15 |
| FAD6518 | - | 1 | 2026-05-16 |
| FAD615 | Rog-Air | 1 | 2026-05-26 |
| FAD467 | Rog-Air | 1 | 2026-05-01 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | FAD608 | CAI → RUH | May 27, 12:50 UTC | May 27, 13:00 UTC | 10m |
| 2026-05-26 | FAD607 | RUH → CAI | May 26, 23:54 UTC | May 27, 11:10 UTC | 11h 16m |
| 2026-05-26 | FAD615 | RUH → CAI | May 26, 21:55 UTC | May 26, 22:15 UTC | 20m |
| 2026-05-24 | FAD776 | CAI → MED | May 24, 20:05 UTC | May 24, 20:20 UTC | 15m |
| 2026-05-24 | FAD775 | MED → CAI | May 24, 17:55 UTC | May 24, 18:20 UTC | 25m |
| 2026-05-23 | FAD775 | MED → CAI | May 23, 18:20 UTC | May 24, 18:15 UTC | 23h 55m |
| 2026-05-21 | FAD771 | MED → CAI | May 21, 05:10 UTC | May 21, 05:30 UTC | 20m |
| 2026-05-20 | FAD771 | MED → CAI | May 20, 07:40 UTC | May 21, 05:30 UTC | 21h 50m |
| 2026-05-20 | FAD771 | MED → CAI | May 20, 05:05 UTC | May 20, 05:30 UTC | 25m |
| 2026-05-18 | FAD776 | CAI → MED | May 18, 20:55 UTC | May 18, 21:10 UTC | 15m |
| 2026-05-18 | FAD775 | MED → CAI | May 18, 07:15 UTC | May 18, 18:25 UTC | 11h 10m |
| 2026-05-18 | FAD771 | MED → CAI | May 18, 05:00 UTC | May 18, 05:20 UTC | 20m |
| 2026-05-16 | FAD771 | MED → CAI | May 16, 14:11 UTC | May 17, 05:20 UTC | 15h 10m |
| 2026-05-16 | FAD6518 | - | May 16, 11:21 UTC | May 16, 11:51 UTC | 30m |
| 2026-05-15 | FAD6798 | - | May 15, 09:20 UTC | May 16, 02:35 UTC | 17h 14m |
| 2026-05-14 | FAD776 | CAI → MED | May 14, 20:05 UTC | May 15, 12:15 UTC | 16h 10m |
| 2026-05-14 | FAD775 | MED → CAI | May 14, 17:50 UTC | May 14, 18:05 UTC | 15m |
| 2026-05-13 | FAD772 | CAI → MED | May 13, 07:10 UTC | May 13, 07:25 UTC | 15m |
| 2026-05-13 | FAD771 | MED → CAI | May 13, 05:15 UTC | May 13, 05:45 UTC | 30m |
| 2026-05-12 | FAD771 | MED → CAI | May 12, 05:10 UTC | May 12, 05:30 UTC | 20m |
| 2026-05-09 | FAD776 | CAI → MED | May 9, 20:15 UTC | May 9, 20:25 UTC | 10m |
| 2026-05-09 | FAD775 | MED → CAI | May 9, 17:55 UTC | May 9, 18:25 UTC | 30m |
| 2026-05-08 | FAD772 | CAI → MED | May 8, 07:20 UTC | May 8, 07:29 UTC | 10m |
| 2026-05-08 | FAD771 | MED → CAI | May 8, 05:20 UTC | May 8, 05:44 UTC | 25m |
| 2026-05-07 | FAD775 | MED → CAI | May 7, 18:05 UTC | May 7, 18:25 UTC | 20m |
| 2026-05-05 | FAD776 | CAI → MED | May 5, 19:55 UTC | May 5, 20:10 UTC | 15m |
| 2026-05-05 | FAD775 | MED → CAI | May 5, 17:50 UTC | May 5, 18:10 UTC | 20m |
| 2026-05-04 | FAD775 | MED → CAI | May 4, 19:50 UTC | May 5, 18:10 UTC | 22h 20m |
| 2026-05-04 | FAD775 | MED → CAI | May 4, 17:50 UTC | May 4, 18:05 UTC | 15m |
| 2026-05-01 | FAD467 | DMM → MED | May 1, 16:50 UTC | May 1, 17:05 UTC | 15m |
| 2026-04-29 | FAD776 | CAI → MED | Apr 29, 19:55 UTC | Apr 29, 20:05 UTC | 10m |
| 2026-04-29 | FAD775 | MED → CAI | Apr 29, 18:00 UTC | Apr 29, 18:15 UTC | 15m |
| 2026-04-23 | FAD608 | CAI → RUH | Apr 23, 13:25 UTC | Apr 23, 13:35 UTC | 10m |
| 2026-04-23 | FAD607 | RUH → CAI | Apr 23, 10:55 UTC | Apr 23, 11:15 UTC | 20m |
| 2026-04-17 | FAD756 | CAI → JED | Apr 17, 09:00 UTC | Apr 17, 09:10 UTC | 10m |
| 2026-04-13 | FAD764 | - | Apr 13, 21:35 UTC | Apr 13, 21:45 UTC | 10m |
| 2026-04-13 | FAD763 | JED → CAI | Apr 13, 19:50 UTC | Apr 13, 20:10 UTC | 20m |
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 HZ-FBC page for operator, model, and routing details .