sensors Mode-S transponder
4B9C61
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-GCA · AIRBUS A-321
- Hex
- 4B9C61
- Octal
- 22716141
- Decimal
- 4,955,233
- Country
- TR
- Tail
- TC-GCA
- Type
- A321
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 4B9C61 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 |
|---|---|---|---|
| BBT412 | - | 4 | 2026-05-23 |
| BBT416 | - | 3 | 2026-05-25 |
| BBT759 | - | 2 | 2026-04-17 |
| BBT414 | - | 2 | 2026-05-24 |
| BBT213 | - | 2 | 2026-05-25 |
| BBT917 | - | 1 | 2026-05-10 |
| BBT916 | - | 1 | 2026-05-10 |
| BBT915 | - | 1 | 2026-05-09 |
| BBT795 | - | 1 | 2026-06-02 |
| BBT794 | - | 1 | 2026-06-02 |
| BBT793 | - | 1 | 2026-06-01 |
| BBT792 | - | 1 | 2026-06-01 |
| BBT791 | - | 1 | 2026-05-31 |
| BBT760 | - | 1 | 2026-04-17 |
| BBT713 | - | 1 | 2026-05-17 |
| BBT711 | - | 1 | 2026-05-17 |
| BBT612 | - | 1 | 2026-05-22 |
| BBT611 | - | 1 | 2026-05-16 |
| BBT450 | - | 1 | 2026-06-07 |
| BBT449 | - | 1 | 2026-06-07 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | BBT450 | - | Jun 7, 05:45 UTC | Jun 7, 08:55 UTC | 3h 10m |
| 2026-06-07 | BBT449 | - | Jun 7, 01:09 UTC | Jun 7, 04:20 UTC | 3h 10m |
| 2026-06-06 | BBT448 | - | Jun 6, 05:20 UTC | Jun 6, 08:55 UTC | 3h 35m |
| 2026-06-06 | BBT447 | - | Jun 6, 01:00 UTC | Jun 6, 04:10 UTC | 3h 10m |
| 2026-06-05 | BBT446 | - | Jun 5, 10:20 UTC | Jun 5, 13:30 UTC | 3h 10m |
| 2026-06-05 | BBT445 | - | Jun 5, 04:15 UTC | Jun 5, 07:35 UTC | 3h 20m |
| 2026-06-04 | BBT444 | - | Jun 4, 16:50 UTC | Jun 4, 21:30 UTC | 4h 40m |
| 2026-06-02 | BBT795 | - | Jun 2, 18:15 UTC | Jun 2, 20:35 UTC | 2h 20m |
| 2026-06-02 | BBT794 | - | Jun 2, 13:40 UTC | Jun 2, 16:45 UTC | 3h 5m |
| 2026-06-01 | BBT793 | - | Jun 1, 18:45 UTC | Jun 1, 22:05 UTC | 3h 20m |
| 2026-06-01 | BBT792 | - | Jun 1, 14:20 UTC | Jun 1, 17:20 UTC | 3h 0m |
| 2026-05-31 | BBT791 | - | May 31, 21:25 UTC | Jun 1, 01:25 UTC | 4h 0m |
| 2026-05-25 | BBT213 | - | May 25, 20:19 UTC | May 26, 15:14 UTC | 18h 55m |
| 2026-05-25 | BBT213 | - | May 25, 19:44 UTC | May 26, 15:14 UTC | 19h 30m |
| 2026-05-25 | BBT416 | - | May 25, 14:25 UTC | May 25, 17:15 UTC | 2h 50m |
| 2026-05-24 | BBT416 | - | May 24, 20:20 UTC | May 25, 17:15 UTC | 20h 55m |
| 2026-05-24 | BBT416 | BEG → BEG | May 24, 20:00 UTC | May 25, 17:15 UTC | 21h 15m |
| 2026-05-24 | BBT415 | BEG → BEG | May 24, 18:00 UTC | May 24, 19:45 UTC | 1h 45m |
| 2026-05-24 | BBT414 | BEG → BEG | May 24, 02:10 UTC | May 24, 17:50 UTC | 15h 40m |
| 2026-05-23 | BBT412 | - | May 23, 22:10 UTC | May 24, 00:15 UTC | 2h 5m |
| 2026-05-23 | BBT412 | - | May 23, 02:20 UTC | May 24, 00:15 UTC | 21h 55m |
| 2026-05-23 | BBT412 | BEG → BEG | May 23, 01:20 UTC | May 24, 00:15 UTC | 22h 55m |
| 2026-05-22 | BBT612 | - | May 22, 09:50 UTC | May 22, 23:10 UTC | 13h 20m |
| 2026-05-21 | BBT414 | - | May 21, 09:30 UTC | May 21, 18:15 UTC | 8h 45m |
| 2026-05-20 | BBT412 | - | May 20, 22:00 UTC | May 21, 06:35 UTC | 8h 35m |
| 2026-05-20 | BBT312 | - | May 20, 02:55 UTC | May 20, 19:15 UTC | 16h 21m |
| 2026-05-19 | BBT214 | - | May 19, 08:10 UTC | May 20, 00:00 UTC | 15h 50m |
| 2026-05-19 | BBT212 | - | May 19, 02:35 UTC | May 19, 04:35 UTC | 2h 0m |
| 2026-05-18 | BBT211 | - | May 18, 20:20 UTC | May 18, 22:10 UTC | 1h 50m |
| 2026-05-18 | BBT111 | - | May 18, 09:45 UTC | May 18, 18:15 UTC | 8h 30m |
| 2026-05-17 | BBT713 | - | May 17, 22:55 UTC | May 18, 07:55 UTC | 9h 0m |
| 2026-05-17 | BBT711 | - | May 17, 12:30 UTC | May 17, 21:10 UTC | 8h 40m |
| 2026-05-16 | BBT611 | - | May 16, 23:40 UTC | May 17, 10:55 UTC | 11h 15m |
| 2026-05-16 | BBT410 | - | May 16, 01:10 UTC | May 16, 03:00 UTC | 1h 50m |
| 2026-05-10 | BBT917 | - | May 10, 16:44 UTC | May 10, 19:05 UTC | 2h 20m |
| 2026-05-10 | BBT916 | - | May 10, 10:30 UTC | May 10, 13:05 UTC | 2h 35m |
| 2026-05-09 | BBT915 | - | May 9, 15:35 UTC | May 9, 20:15 UTC | 4h 40m |
| 2026-05-05 | BBT127 | - | May 5, 11:35 UTC | May 5, 13:25 UTC | 1h 50m |
| 2026-05-05 | BBT126 | - | May 5, 06:45 UTC | May 5, 08:50 UTC | 2h 5m |
| 2026-05-04 | BBT125 | - | May 4, 15:05 UTC | May 4, 18:40 UTC | 3h 36m |
| 2026-04-23 | BBT396 | - | Apr 23, 15:25 UTC | Apr 23, 19:20 UTC | 3h 54m |
| 2026-04-22 | BBT395 | - | Apr 22, 22:10 UTC | Apr 23, 02:25 UTC | 4h 15m |
| 2026-04-17 | BBT760 | - | Apr 17, 09:45 UTC | Apr 17, 10:40 UTC | 55m |
| 2026-04-17 | BBT759 | - | Apr 17, 07:20 UTC | Apr 17, 07:30 UTC | 10m |
| 2026-04-17 | BBT759 | - | Apr 17, 05:50 UTC | Apr 17, 07:15 UTC | 1h 25m |
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-GCA page for operator, model, and routing details .