sensors Mode-S transponder
717CB8
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBA · AIRBUS A-320neo
- Hex
- 717CB8
- Octal
- 34276270
- Decimal
- 7,437,496
- Country
- SA
- Tail
- HZ-FBA
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 16
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 717CB8 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD762 | - | 5 | 2026-07-02 |
| FAD763 | - | 4 | 2026-07-08 |
| FAD761 | - | 4 | 2026-07-02 |
| FAD741 | Rog-Air | 4 | 2026-06-05 |
| FAD764 | - | 3 | 2026-07-03 |
| FAD742 | Rog-Air | 3 | 2026-06-05 |
| FAD754 | - | 2 | 2026-07-11 |
| FAD753 | - | 2 | 2026-07-11 |
| FAD318 | Rog-Air | 2 | 2026-06-24 |
| FAD8721 | - | 1 | 2026-05-21 |
| FAD774 | - | 1 | 2026-07-06 |
| FAD773 | - | 1 | 2026-07-05 |
| FAD514 | - | 1 | 2026-07-13 |
| FAD513 | - | 1 | 2026-07-13 |
| FAD429 | - | 1 | 2026-07-08 |
| FAD304 | - | 1 | 2026-06-23 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FAD514 | - | Jul 13, 19:15 UTC | Jul 13, 20:25 UTC | 1h 10m |
| 2026-07-13 | FAD513 | - | Jul 13, 16:35 UTC | Jul 13, 18:00 UTC | 1h 25m |
| 2026-07-11 | FAD754 | - | Jul 11, 07:10 UTC | Jul 11, 07:20 UTC | 10m |
| 2026-07-11 | FAD753 | - | Jul 11, 05:01 UTC | Jul 11, 05:40 UTC | 40m |
| 2026-07-08 | FAD763 | - | Jul 8, 20:15 UTC | Jul 8, 20:40 UTC | 25m |
| 2026-07-08 | FAD429 | - | Jul 8, 08:50 UTC | Jul 8, 09:00 UTC | 10m |
| 2026-07-06 | FAD774 | - | Jul 6, 06:00 UTC | Jul 6, 06:35 UTC | 35m |
| 2026-07-05 | FAD773 | - | Jul 5, 21:50 UTC | Jul 6, 04:45 UTC | 6h 55m |
| 2026-07-05 | FAD763 | - | Jul 5, 19:40 UTC | Jul 5, 20:00 UTC | 20m |
| 2026-07-03 | FAD764 | - | Jul 3, 21:55 UTC | Jul 3, 22:20 UTC | 25m |
| 2026-07-02 | FAD762 | - | Jul 2, 19:25 UTC | Jul 2, 19:50 UTC | 25m |
| 2026-07-02 | FAD761 | - | Jul 2, 16:45 UTC | Jul 2, 17:05 UTC | 20m |
| 2026-06-30 | FAD762 | - | Jun 30, 18:55 UTC | Jun 30, 19:15 UTC | 20m |
| 2026-06-29 | FAD761 | - | Jun 29, 22:05 UTC | Jun 30, 17:10 UTC | 19h 5m |
| 2026-06-29 | FAD764 | CAI → JED | Jun 29, 21:54 UTC | Jun 30, 17:10 UTC | 19h 15m |
| 2026-06-29 | FAD763 | JED → CAI | Jun 29, 19:29 UTC | Jun 29, 19:44 UTC | 15m |
| 2026-06-26 | FAD762 | CAI → JED | Jun 26, 19:00 UTC | Jun 26, 19:24 UTC | 25m |
| 2026-06-26 | FAD761 | JED → CAI | Jun 26, 00:15 UTC | Jun 26, 17:00 UTC | 16h 45m |
| 2026-06-24 | FAD318 | DMM → JED | Jun 24, 18:34 UTC | Jun 24, 18:44 UTC | 10m |
| 2026-06-23 | FAD304 | - | Jun 23, 08:04 UTC | Jun 23, 08:15 UTC | 10m |
| 2026-06-15 | - | - | Jun 15, 18:40 UTC | Jun 15, 18:50 UTC | 10m |
| 2026-06-13 | FAD754 | CAI → JED | Jun 13, 06:55 UTC | Jun 13, 07:05 UTC | 10m |
| 2026-06-13 | FAD753 | JED → CAI | Jun 13, 05:00 UTC | Jun 13, 05:15 UTC | 15m |
| 2026-06-05 | FAD764 | CAI → JED | Jun 5, 21:40 UTC | Jun 5, 21:50 UTC | 10m |
| 2026-06-05 | FAD742 | DAM → JED | Jun 5, 08:10 UTC | Jun 5, 19:55 UTC | 11h 45m |
| 2026-06-05 | FAD741 | JED → DAM | Jun 5, 06:10 UTC | Jun 5, 06:30 UTC | 20m |
| 2026-06-04 | FAD741 | JED → DAM | Jun 4, 11:05 UTC | Jun 5, 06:30 UTC | 19h 25m |
| 2026-06-03 | FAD742 | DAM → JED | Jun 3, 08:10 UTC | Jun 3, 08:35 UTC | 25m |
| 2026-06-02 | FAD741 | JED → DAM | Jun 2, 21:25 UTC | Jun 3, 06:05 UTC | 8h 40m |
| 2026-06-02 | FAD763 | JED → CAI | Jun 2, 19:35 UTC | Jun 2, 19:50 UTC | 15m |
| 2026-05-31 | FAD762 | CAI → JED | May 31, 19:10 UTC | May 31, 19:30 UTC | 20m |
| 2026-05-30 | FAD761 | JED → CAI | May 30, 23:30 UTC | May 31, 17:20 UTC | 17h 50m |
| 2026-05-29 | FAD318 | DMM → JED | May 29, 18:35 UTC | May 29, 18:45 UTC | 10m |
| 2026-05-25 | FAD762 | CAI → JED | May 25, 19:00 UTC | May 25, 19:10 UTC | 10m |
| 2026-05-25 | FAD742 | DAM → JED | May 25, 07:45 UTC | May 25, 16:55 UTC | 9h 10m |
| 2026-05-25 | FAD741 | JED → DAM | May 25, 06:00 UTC | May 25, 06:25 UTC | 25m |
| 2026-05-21 | FAD8721 | - | May 21, 11:35 UTC | May 21, 11:45 UTC | 10m |
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-FBA page for operator, model, and routing details .