sensors Mode-S transponder
4BBB21
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-NYA · AIRBUS A-330-300
- Hex
- 4BBB21
- Octal
- 22735441
- Decimal
- 4,963,105
- Country
- TR
- Tail
- TC-NYA
- Type
- A333
- Flights observed
- 53
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 4BBB21 falls within the block assigned to Turkey (TR) by ICAO Annex 10, Volume III. Every aircraft registered in Turkey 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 |
|---|---|---|---|
| FAD7301 | - | 3 | 2026-06-01 |
| FAD6342 | - | 3 | 2026-05-03 |
| FAD6762 | - | 2 | 2026-05-18 |
| FAD6345 | Rog-Air | 2 | 2026-05-05 |
| FAD6315 | Rog-Air | 2 | 2026-04-23 |
| FAD6314 | - | 2 | 2026-04-23 |
| FAD6308 | - | 2 | 2026-04-20 |
| FAD6303 | Rog-Air | 2 | 2026-04-19 |
| FAD6020 | - | 2 | 2026-05-15 |
| FAD8508 | - | 1 | 2026-04-18 |
| FAD8002 | Rog-Air | 1 | 2026-05-29 |
| FAD8001 | - | 1 | 2026-05-22 |
| FAD7466 | Rog-Air | 1 | 2026-05-30 |
| FAD7411 | - | 1 | 2026-06-01 |
| FAD7410 | Rog-Air | 1 | 2026-05-31 |
| FAD6763 | - | 1 | 2026-05-19 |
| FAD6700 | - | 1 | 2026-05-09 |
| FAD6451 | Rog-Air | 1 | 2026-05-01 |
| FAD6444 | - | 1 | 2026-04-30 |
| FAD6439 | - | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FAD7301 | - | Jun 1, 22:20 UTC | Jun 2, 17:40 UTC | 19h 20m |
| 2026-06-01 | FAD7301 | - | Jun 1, 21:30 UTC | Jun 2, 17:40 UTC | 20h 10m |
| 2026-06-01 | FAD7301 | - | Jun 1, 18:20 UTC | Jun 2, 17:40 UTC | 23h 20m |
| 2026-06-01 | FAD7411 | - | Jun 1, 17:10 UTC | Jun 2, 15:45 UTC | 22h 35m |
| 2026-05-31 | FAD7410 | JED → ESB | May 31, 18:35 UTC | Jun 1, 18:15 UTC | 23h 40m |
| 2026-05-30 | FAD7466 | JED → MCT | May 30, 21:05 UTC | May 31, 18:40 UTC | 21h 35m |
| 2026-05-29 | FAD8002 | JED → JED | May 29, 10:25 UTC | May 29, 11:30 UTC | 1h 5m |
| 2026-05-22 | FAD8001 | - | May 22, 02:45 UTC | May 22, 16:15 UTC | 13h 30m |
| 2026-05-19 | FAD6763 | - | May 19, 04:35 UTC | May 19, 04:55 UTC | 20m |
| 2026-05-18 | FAD6762 | - | May 18, 08:25 UTC | May 19, 02:15 UTC | 17h 49m |
| 2026-05-18 | FAD6762 | - | May 18, 05:50 UTC | May 19, 02:15 UTC | 20h 24m |
| 2026-05-17 | FAD6244 | - | May 17, 14:20 UTC | May 18, 08:25 UTC | 18h 5m |
| 2026-05-17 | FAD5735 | - | May 17, 05:10 UTC | May 17, 21:05 UTC | 15h 55m |
| 2026-05-17 | FAD5734 | - | May 17, 02:15 UTC | May 17, 02:40 UTC | 25m |
| 2026-05-15 | FAD6020 | - | May 15, 03:00 UTC | May 15, 15:35 UTC | 12h 34m |
| 2026-05-14 | FAD6020 | - | May 14, 11:40 UTC | May 15, 05:35 UTC | 17h 55m |
| 2026-05-14 | FAD5732 | - | May 14, 08:35 UTC | May 14, 08:55 UTC | 20m |
| 2026-05-10 | FAD6362 | - | May 10, 16:10 UTC | May 11, 04:35 UTC | 12h 25m |
| 2026-05-10 | FAD5736 | - | May 10, 12:05 UTC | May 10, 12:30 UTC | 25m |
| 2026-05-09 | FAD6700 | AMM → AMM | May 9, 06:15 UTC | May 9, 12:55 UTC | 6h 40m |
| 2026-05-05 | FAD6345 | CCU → MED | May 5, 06:40 UTC | May 5, 07:40 UTC | 1h 0m |
| 2026-05-05 | FAD6345 | CCU → MED | May 5, 02:35 UTC | May 5, 03:20 UTC | 45m |
| 2026-05-04 | FAD6343 | CCU → MED | May 4, 06:25 UTC | May 4, 23:35 UTC | 17h 11m |
| 2026-05-03 | FAD6342 | - | May 3, 21:35 UTC | May 4, 02:10 UTC | 4h 35m |
| 2026-05-03 | FAD6342 | - | May 3, 04:50 UTC | May 4, 02:10 UTC | 21h 20m |
| 2026-05-03 | FAD6342 | - | May 3, 02:50 UTC | May 4, 02:10 UTC | 23h 19m |
| 2026-05-02 | FAD6119 | - | May 2, 17:15 UTC | May 3, 05:55 UTC | 12h 39m |
| 2026-05-01 | FAD6451 | ESB → MED | May 1, 18:20 UTC | May 2, 18:10 UTC | 23h 50m |
| 2026-05-01 | FAD6335 | CCU → MED | May 1, 02:00 UTC | May 1, 19:15 UTC | 17h 15m |
| 2026-04-30 | FAD6334 | - | Apr 30, 10:45 UTC | Apr 30, 21:40 UTC | 10h 55m |
| 2026-04-30 | FAD6444 | - | Apr 30, 05:50 UTC | Apr 30, 06:55 UTC | 1h 5m |
| 2026-04-28 | FAD6329 | - | Apr 28, 21:05 UTC | Apr 29, 02:05 UTC | 5h 0m |
| 2026-04-28 | FAD6328 | CCU → CCU | Apr 28, 03:35 UTC | Apr 28, 17:55 UTC | 14h 20m |
| 2026-04-27 | FAD6326 | - | Apr 27, 08:50 UTC | Apr 27, 22:50 UTC | 14h 0m |
| 2026-04-26 | FAD6439 | - | Apr 26, 18:45 UTC | Apr 27, 14:15 UTC | 19h 30m |
| 2026-04-26 | FAD6323 | CCU → MED | Apr 26, 14:45 UTC | Apr 27, 14:15 UTC | 23h 30m |
| 2026-04-26 | FAD6322 | - | Apr 26, 05:45 UTC | Apr 26, 10:20 UTC | 4h 35m |
| 2026-04-24 | FAD6319 | CCU → MED | Apr 24, 21:05 UTC | Apr 25, 02:10 UTC | 5h 5m |
| 2026-04-24 | FAD6318 | - | Apr 24, 13:35 UTC | Apr 24, 18:10 UTC | 4h 35m |
| 2026-04-23 | FAD6315 | CCU → MED | Apr 23, 14:30 UTC | Apr 24, 14:05 UTC | 23h 35m |
| 2026-04-23 | FAD6315 | CCU → MED | Apr 23, 09:45 UTC | Apr 23, 14:55 UTC | 5h 10m |
| 2026-04-23 | FAD6314 | - | Apr 23, 00:35 UTC | Apr 23, 05:25 UTC | 4h 51m |
| 2026-04-22 | FAD6314 | - | Apr 22, 02:30 UTC | Apr 23, 01:30 UTC | 23h 0m |
| 2026-04-21 | FAD6311 | - | Apr 21, 22:25 UTC | Apr 22, 03:30 UTC | 5h 5m |
| 2026-04-21 | FAD6310 | - | Apr 21, 18:20 UTC | Apr 21, 19:05 UTC | 45m |
| 2026-04-21 | FAD6309 | - | Apr 21, 01:35 UTC | Apr 21, 15:05 UTC | 13h 30m |
| 2026-04-20 | FAD6308 | - | Apr 20, 02:20 UTC | Apr 20, 21:35 UTC | 19h 16m |
| 2026-04-20 | FAD6308 | - | Apr 20, 01:35 UTC | Apr 20, 21:35 UTC | 20h 0m |
| 2026-04-19 | FAD6305 | - | Apr 19, 21:30 UTC | Apr 20, 17:45 UTC | 20h 15m |
| 2026-04-19 | FAD6303 | GZT → MED | Apr 19, 03:15 UTC | Apr 19, 18:55 UTC | 15h 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 TC-NYA page for operator, model, and routing details .