sensors Mode-S transponder
4B9C63
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-GCC · AIRBUS A-321
- Hex
- 4B9C63
- Octal
- 22716143
- Decimal
- 4,955,235
- Country
- TR
- Tail
- TC-GCC
- Type
- A321
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 4B9C63 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 |
|---|---|---|---|
| BBT609 | - | 3 | 2026-05-22 |
| BBT411 | - | 3 | 2026-05-29 |
| THY6602 | - | 2 | 2026-04-15 |
| THY6474 | - | 2 | 2026-04-17 |
| THY6473 | - | 2 | 2026-04-17 |
| THY6432 | - | 2 | 2026-05-27 |
| THY6431 | Turkish Airlines | 2 | 2026-05-27 |
| BBT726 | - | 2 | 2026-04-24 |
| BBT621 | - | 2 | 2026-05-21 |
| BBT405 | - | 2 | 2026-05-24 |
| THY6638 | - | 1 | 2026-04-22 |
| THY6637 | Turkish Airlines | 1 | 2026-04-22 |
| THY6631 | Turkish Airlines | 1 | 2026-04-18 |
| THY6630 | - | 1 | 2026-04-18 |
| THY6402 | Turkish Airlines | 1 | 2026-05-16 |
| THY6401 | Turkish Airlines | 1 | 2026-05-16 |
| BBT725 | - | 1 | 2026-04-24 |
| BBT613 | - | 1 | 2026-05-06 |
| BBT612 | - | 1 | 2026-05-06 |
| BBT610 | - | 1 | 2026-05-22 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | BBT412 | - | May 30, 06:05 UTC | May 30, 08:55 UTC | 2h 50m |
| 2026-05-29 | BBT411 | - | May 29, 06:35 UTC | May 29, 16:05 UTC | 9h 30m |
| 2026-05-28 | BBT409 | - | May 28, 13:15 UTC | May 28, 15:50 UTC | 2h 35m |
| 2026-05-27 | THY6432 | - | May 27, 19:05 UTC | May 27, 21:55 UTC | 2h 50m |
| 2026-05-27 | THY6431 | MAA → IST | May 27, 13:35 UTC | May 27, 16:30 UTC | 2h 55m |
| 2026-05-26 | BBT411 | - | May 26, 14:14 UTC | May 26, 17:20 UTC | 3h 5m |
| 2026-05-25 | BBT411 | - | May 25, 16:50 UTC | May 26, 16:45 UTC | 23h 54m |
| 2026-05-25 | BBT406 | - | May 25, 15:25 UTC | May 26, 14:45 UTC | 23h 19m |
| 2026-05-24 | BBT405 | - | May 24, 16:50 UTC | May 25, 12:20 UTC | 19h 30m |
| 2026-05-24 | BBT405 | BEG → BEG | May 24, 14:50 UTC | May 25, 12:20 UTC | 21h 30m |
| 2026-05-23 | BBT403 | - | May 23, 16:50 UTC | May 24, 12:30 UTC | 19h 40m |
| 2026-05-22 | BBT610 | BEG → BEG | May 22, 20:35 UTC | May 23, 13:40 UTC | 17h 4m |
| 2026-05-22 | BBT609 | - | May 22, 14:15 UTC | May 22, 17:15 UTC | 3h 0m |
| 2026-05-21 | BBT609 | - | May 21, 18:50 UTC | May 22, 17:15 UTC | 22h 25m |
| 2026-05-21 | BBT609 | - | May 21, 18:35 UTC | May 22, 16:45 UTC | 22h 10m |
| 2026-05-21 | BBT621 | - | May 21, 12:50 UTC | May 21, 15:25 UTC | 2h 35m |
| 2026-05-20 | BBT621 | - | May 20, 14:50 UTC | May 21, 14:45 UTC | 23h 55m |
| 2026-05-20 | BBT608 | - | May 20, 13:15 UTC | May 20, 15:10 UTC | 1h 55m |
| 2026-05-20 | BBT607 | - | May 20, 07:45 UTC | May 20, 09:30 UTC | 1h 45m |
| 2026-05-19 | BBT606 | - | May 19, 05:00 UTC | May 19, 06:40 UTC | 1h 40m |
| 2026-05-18 | BBT605 | - | May 18, 18:00 UTC | May 19, 03:20 UTC | 9h 19m |
| 2026-05-17 | BBT603 | - | May 17, 17:55 UTC | May 18, 03:40 UTC | 9h 45m |
| 2026-05-17 | BBT601 | - | May 17, 14:35 UTC | May 17, 16:05 UTC | 1h 30m |
| 2026-05-16 | THY6402 | BCN → IST | May 16, 20:05 UTC | May 16, 22:40 UTC | 2h 35m |
| 2026-05-16 | THY6401 | IST → BCN | May 16, 14:46 UTC | May 16, 17:55 UTC | 3h 10m |
| 2026-05-06 | BBT613 | - | May 6, 18:45 UTC | May 6, 22:20 UTC | 3h 35m |
| 2026-05-06 | BBT612 | - | May 6, 12:35 UTC | May 6, 16:50 UTC | 4h 15m |
| 2026-05-01 | THY6432 | VIE → ISL | May 1, 19:35 UTC | May 1, 22:20 UTC | 2h 45m |
| 2026-05-01 | THY6431 | ISL → ISL | May 1, 13:50 UTC | May 1, 16:40 UTC | 2h 50m |
| 2026-04-24 | BBT726 | - | Apr 24, 23:45 UTC | Apr 25, 01:10 UTC | 1h 25m |
| 2026-04-24 | BBT726 | - | Apr 24, 02:50 UTC | Apr 25, 01:10 UTC | 22h 20m |
| 2026-04-24 | BBT725 | - | Apr 24, 01:55 UTC | Apr 25, 00:45 UTC | 22h 50m |
| 2026-04-22 | THY6638 | - | Apr 22, 10:40 UTC | Apr 22, 12:30 UTC | 1h 50m |
| 2026-04-22 | THY6637 | AMM → AMM | Apr 22, 06:40 UTC | Apr 22, 08:40 UTC | 2h 0m |
| 2026-04-18 | THY6631 | ALA → IST | Apr 18, 20:45 UTC | Apr 19, 00:10 UTC | 3h 25m |
| 2026-04-18 | THY6630 | - | Apr 18, 15:00 UTC | Apr 18, 19:00 UTC | 4h 0m |
| 2026-04-17 | THY6474 | - | Apr 17, 15:20 UTC | Apr 17, 16:15 UTC | 55m |
| 2026-04-17 | THY6474 | - | Apr 17, 14:05 UTC | Apr 17, 15:15 UTC | 1h 9m |
| 2026-04-17 | THY6473 | - | Apr 17, 11:20 UTC | Apr 17, 11:50 UTC | 30m |
| 2026-04-17 | THY6473 | - | Apr 17, 09:25 UTC | Apr 17, 11:15 UTC | 1h 50m |
| 2026-04-15 | THY6602 | - | Apr 15, 19:05 UTC | Apr 15, 19:25 UTC | 20m |
| 2026-04-15 | THY6602 | - | Apr 15, 18:00 UTC | Apr 15, 19:00 UTC | 1h 0m |
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-GCC page for operator, model, and routing details .