sensors Mode-S transponder
7114CE
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBN · AIRBUS A-320neo
- Hex
- 7114CE
- Octal
- 34212316
- Decimal
- 7,410,894
- Country
- SA
- Tail
- HZ-FBN
- Type
- A20N
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7114CE 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 |
|---|---|---|---|
| FAD451 | Rog-Air | 4 | 2026-05-29 |
| FAD911 | Rog-Air | 2 | 2026-04-16 |
| FAD6047 | - | 2 | 2026-05-14 |
| FAD574 | - | 2 | 2026-04-13 |
| FAD573 | - | 2 | 2026-04-13 |
| FAD481 | Rog-Air | 2 | 2026-05-29 |
| FAD465 | Rog-Air | 2 | 2026-05-31 |
| FAD461 | Rog-Air | 2 | 2026-04-23 |
| FAD829 | Rog-Air | 1 | 2026-04-25 |
| FAD808 | Rog-Air | 1 | 2026-05-04 |
| FAD807 | Rog-Air | 1 | 2026-05-04 |
| FAD774 | Rog-Air | 1 | 2026-05-16 |
| FAD773 | Rog-Air | 1 | 2026-05-16 |
| FAD702 | - | 1 | 2026-04-29 |
| FAD701 | Rog-Air | 1 | 2026-04-28 |
| FAD6836 | - | 1 | 2026-05-17 |
| FAD6781 | - | 1 | 2026-05-18 |
| FAD6780 | - | 1 | 2026-05-17 |
| FAD6213 | - | 1 | 2026-05-05 |
| FAD6046 | - | 1 | 2026-05-13 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FAD432 | AHB → DMM | Jun 1, 16:10 UTC | Jun 1, 16:20 UTC | 10m |
| 2026-05-31 | FAD465 | DMM → MED | May 31, 17:50 UTC | May 31, 18:10 UTC | 20m |
| 2026-05-30 | FAD490 | NUM → DMM | May 30, 10:00 UTC | May 30, 18:20 UTC | 8h 20m |
| 2026-05-29 | FAD481 | DMM → HAS | May 29, 17:40 UTC | May 30, 10:05 UTC | 16h 25m |
| 2026-05-29 | FAD451 | DMM → TIF | May 29, 12:10 UTC | May 29, 16:15 UTC | 4h 5m |
| 2026-05-27 | FAD451 | DMM → TIF | May 27, 12:10 UTC | May 27, 12:20 UTC | 10m |
| 2026-05-25 | FAD431 | DMM → AHB | May 25, 12:20 UTC | May 26, 11:00 UTC | 22h 39m |
| 2026-05-21 | FAD3402 | - | May 21, 08:10 UTC | May 21, 08:20 UTC | 10m |
| 2026-05-18 | FAD6781 | - | May 18, 05:05 UTC | May 18, 05:30 UTC | 25m |
| 2026-05-17 | FAD6780 | - | May 17, 17:05 UTC | May 18, 03:30 UTC | 10h 25m |
| 2026-05-17 | FAD6836 | - | May 17, 01:55 UTC | May 17, 18:40 UTC | 16h 45m |
| 2026-05-16 | FAD774 | ALY → JED | May 16, 06:25 UTC | May 17, 02:05 UTC | 19h 40m |
| 2026-05-16 | FAD773 | JED → ALY | May 16, 04:05 UTC | May 16, 04:35 UTC | 30m |
| 2026-05-14 | FAD6047 | - | May 14, 15:25 UTC | May 14, 15:55 UTC | 30m |
| 2026-05-14 | FAD6047 | - | May 14, 13:10 UTC | May 14, 13:40 UTC | 30m |
| 2026-05-13 | FAD6046 | - | May 13, 19:20 UTC | May 14, 05:35 UTC | 10h 15m |
| 2026-05-05 | FAD6213 | - | May 5, 15:45 UTC | May 5, 16:15 UTC | 30m |
| 2026-05-04 | FAD808 | IST → JED | May 4, 20:50 UTC | May 5, 14:40 UTC | 17h 50m |
| 2026-05-04 | FAD807 | JED → IST | May 4, 16:30 UTC | May 4, 18:35 UTC | 2h 6m |
| 2026-04-29 | FAD702 | - | Apr 29, 11:55 UTC | Apr 29, 13:00 UTC | 1h 5m |
| 2026-04-28 | FAD701 | JED → MCT | Apr 28, 16:50 UTC | Apr 29, 09:20 UTC | 16h 30m |
| 2026-04-25 | FAD829 | JED → KHI | Apr 25, 22:40 UTC | Apr 26, 04:10 UTC | 5h 30m |
| 2026-04-23 | FAD324 | DMM → JED | Apr 23, 23:20 UTC | Apr 23, 23:40 UTC | 20m |
| 2026-04-23 | FAD481 | - | Apr 23, 17:40 UTC | Apr 23, 17:55 UTC | 15m |
| 2026-04-23 | FAD462 | MED → DMM | Apr 23, 09:10 UTC | Apr 23, 09:20 UTC | 10m |
| 2026-04-23 | FAD461 | DMM → MED | Apr 23, 05:10 UTC | Apr 23, 05:25 UTC | 15m |
| 2026-04-22 | FAD451 | DMM → TIF | Apr 22, 12:05 UTC | Apr 22, 12:15 UTC | 10m |
| 2026-04-21 | FAD451 | DMM → TIF | Apr 21, 12:15 UTC | Apr 21, 16:05 UTC | 3h 50m |
| 2026-04-17 | FAD461 | DMM → MED | Apr 17, 05:05 UTC | Apr 17, 05:15 UTC | 10m |
| 2026-04-16 | FAD437 | - | Apr 16, 19:00 UTC | Apr 16, 19:10 UTC | 10m |
| 2026-04-16 | FAD485 | - | Apr 16, 12:24 UTC | Apr 16, 12:39 UTC | 15m |
| 2026-04-16 | FAD911 | DMM → CAI | Apr 16, 06:34 UTC | Apr 16, 06:49 UTC | 15m |
| 2026-04-16 | FAD911 | DMM → CAI | Apr 16, 04:24 UTC | Apr 16, 04:40 UTC | 15m |
| 2026-04-15 | FAD465 | DMM → MED | Apr 15, 18:25 UTC | Apr 15, 18:35 UTC | 10m |
| 2026-04-13 | FAD574 | - | Apr 13, 19:50 UTC | Apr 13, 20:45 UTC | 55m |
| 2026-04-13 | FAD574 | - | Apr 13, 19:00 UTC | Apr 13, 20:10 UTC | 1h 10m |
| 2026-04-13 | FAD573 | - | Apr 13, 15:50 UTC | Apr 13, 16:25 UTC | 35m |
| 2026-04-13 | FAD573 | - | Apr 13, 14:20 UTC | Apr 13, 16:00 UTC | 1h 40m |
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-FBN page for operator, model, and routing details .