sensors Mode-S transponder
710DC3
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAL · AIRBUS A-320neo
- Hex
- 710DC3
- Octal
- 34206703
- Decimal
- 7,409,091
- Country
- SA
- Tail
- HZ-FAL
- Type
- A20N
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 710DC3 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD511 | - | 4 | 2026-07-15 |
| FAD304 | Rog-Air | 4 | 2026-06-04 |
| FAD762 | Rog-Air | 2 | 2026-05-23 |
| FAD761 | Rog-Air | 2 | 2026-05-23 |
| FAD614 | - | 2 | 2026-07-10 |
| FAD613 | - | 2 | 2026-07-10 |
| FAD512 | - | 2 | 2026-07-15 |
| FAD506 | Rog-Air | 2 | 2026-05-05 |
| FAD505 | Rog-Air | 2 | 2026-05-05 |
| FAD322 | Rog-Air | 2 | 2026-05-27 |
| FAD318 | Rog-Air | 2 | 2026-06-18 |
| FAD186 | - | 2 | 2026-07-17 |
| FAD966 | - | 1 | 2026-07-04 |
| FAD965 | - | 1 | 2026-07-03 |
| FAD8805 | - | 1 | 2026-06-05 |
| FAD8207 | - | 1 | 2026-07-07 |
| FAD8012 | - | 1 | 2026-06-12 |
| FAD754 | Rog-Air | 1 | 2026-05-21 |
| FAD753 | Rog-Air | 1 | 2026-05-21 |
| FAD742 | Rog-Air | 1 | 2026-05-19 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | FAD186 | - | Jul 17, 18:50 UTC | Jul 17, 19:00 UTC | 10m |
| 2026-07-15 | FAD512 | - | Jul 15, 17:55 UTC | Jul 16, 05:20 UTC | 11h 25m |
| 2026-07-15 | FAD511 | - | Jul 15, 15:30 UTC | Jul 15, 16:55 UTC | 1h 25m |
| 2026-07-10 | FAD614 | - | Jul 10, 09:50 UTC | Jul 10, 10:00 UTC | 10m |
| 2026-07-10 | FAD613 | - | Jul 10, 07:30 UTC | Jul 10, 07:50 UTC | 20m |
| 2026-07-09 | FAD511 | - | Jul 9, 15:20 UTC | Jul 9, 16:45 UTC | 1h 25m |
| 2026-07-08 | FAD511 | - | Jul 8, 18:50 UTC | Jul 9, 16:45 UTC | 21h 55m |
| 2026-07-08 | FAD574 | - | Jul 8, 18:05 UTC | Jul 9, 16:45 UTC | 22h 40m |
| 2026-07-08 | FAD573 | RUH → IST | Jul 8, 14:40 UTC | Jul 8, 16:45 UTC | 2h 5m |
| 2026-07-07 | FAD8207 | - | Jul 7, 19:20 UTC | Jul 7, 19:30 UTC | 10m |
| 2026-07-05 | FAD466 | MED → DMM | Jul 5, 22:05 UTC | Jul 5, 22:20 UTC | 15m |
| 2026-07-05 | FAD465 | - | Jul 5, 18:05 UTC | Jul 5, 18:15 UTC | 10m |
| 2026-07-04 | FAD966 | - | Jul 4, 08:05 UTC | Jul 4, 16:45 UTC | 8h 40m |
| 2026-07-03 | FAD965 | - | Jul 3, 20:10 UTC | Jul 4, 07:00 UTC | 10h 50m |
| 2026-06-26 | FAD512 | - | Jun 26, 17:44 UTC | Jun 26, 18:34 UTC | 50m |
| 2026-06-26 | FAD511 | - | Jun 26, 15:15 UTC | Jun 26, 16:30 UTC | 1h 15m |
| 2026-06-18 | FAD318 | DMM → JED | Jun 18, 18:30 UTC | Jun 19, 13:04 UTC | 18h 34m |
| 2026-06-18 | FAD317 | JED → DMM | Jun 18, 17:05 UTC | Jun 18, 17:21 UTC | 16m |
| 2026-06-16 | FAD318 | DMM → JED | Jun 16, 18:39 UTC | Jun 16, 18:55 UTC | 15m |
| 2026-06-12 | FAD8012 | - | Jun 12, 11:10 UTC | Jun 12, 11:25 UTC | 15m |
| 2026-06-05 | FAD8805 | - | Jun 5, 09:00 UTC | Jun 5, 09:15 UTC | 15m |
| 2026-06-04 | FAD304 | DMM → JED | Jun 4, 08:00 UTC | Jun 4, 08:10 UTC | 10m |
| 2026-06-02 | FAD304 | DMM → JED | Jun 2, 08:00 UTC | Jun 2, 08:15 UTC | 15m |
| 2026-06-01 | FAD304 | DMM → JED | Jun 1, 08:00 UTC | Jun 1, 08:10 UTC | 10m |
| 2026-05-30 | FAD304 | DMM → JED | May 30, 07:55 UTC | May 30, 08:05 UTC | 10m |
| 2026-05-27 | FAD322 | DMM → JED | May 27, 00:04 UTC | May 27, 00:14 UTC | 10m |
| 2026-05-23 | FAD762 | CAI → JED | May 23, 19:05 UTC | May 23, 19:15 UTC | 10m |
| 2026-05-23 | FAD761 | JED → CAI | May 23, 08:05 UTC | May 23, 17:00 UTC | 8h 55m |
| 2026-05-22 | FAD322 | DMM → JED | May 22, 00:15 UTC | May 22, 00:30 UTC | 15m |
| 2026-05-21 | FAD754 | CAI → JED | May 21, 07:20 UTC | May 21, 07:30 UTC | 10m |
| 2026-05-21 | FAD753 | JED → CAI | May 21, 05:15 UTC | May 21, 05:30 UTC | 15m |
| 2026-05-19 | FAD742 | DAM → JED | May 19, 08:20 UTC | May 19, 08:45 UTC | 25m |
| 2026-05-18 | FAD741 | JED → DAM | May 18, 12:55 UTC | May 19, 06:25 UTC | 17h 29m |
| 2026-05-17 | FAD762 | CAI → JED | May 17, 19:10 UTC | May 17, 19:20 UTC | 10m |
| 2026-05-17 | FAD761 | JED → CAI | May 17, 17:01 UTC | May 17, 17:20 UTC | 20m |
| 2026-05-05 | FAD506 | DXB → RUH | May 5, 09:15 UTC | May 5, 09:35 UTC | 20m |
| 2026-05-05 | FAD505 | RUH → DXB | May 5, 07:20 UTC | May 5, 07:40 UTC | 20m |
| 2026-04-28 | FAD506 | DXB → RUH | Apr 28, 09:20 UTC | Apr 28, 10:30 UTC | 1h 10m |
| 2026-04-28 | FAD505 | RUH → DXB | Apr 28, 06:30 UTC | Apr 28, 07:35 UTC | 1h 5m |
| 2026-04-25 | FAD186 | DMM → RUH | Apr 25, 18:40 UTC | Apr 25, 18:55 UTC | 15m |
| 2026-04-15 | FAD614 | CAI → RUH | Apr 15, 09:40 UTC | Apr 15, 09:50 UTC | 10m |
| 2026-04-15 | FAD613 | RUH → CAI | Apr 15, 07:40 UTC | Apr 15, 07:55 UTC | 15m |
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-FAL page for operator, model, and routing details .