sensors Mode-S transponder
4BB062
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LCB · BOEING 737 MAX 8
- Hex
- 4BB062
- Octal
- 22730142
- Decimal
- 4,960,354
- Country
- TR
- Tail
- TC-LCB
- Type
- B38M
- Flights observed
- 214
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 51m ago
Last known position
Country allocation
The ICAO 24-bit address 4BB062 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 |
|---|---|---|---|
| THY7KC | Turkish Airlines | 12 | 2026-06-18 |
| THY647 | - | 8 | 2026-07-10 |
| THY505 | - | 7 | 2026-07-14 |
| THY506 | - | 6 | 2026-07-12 |
| THY2YM | - | 5 | 2026-06-21 |
| THY88K | - | 4 | 2026-07-04 |
| THY5UW | Turkish Airlines | 4 | 2026-06-13 |
| THY5LR | - | 4 | 2026-06-09 |
| THY538 | Turkish Airlines | 4 | 2026-05-22 |
| THY537 | Turkish Airlines | 4 | 2026-05-15 |
| THY4HU | Turkish Airlines | 4 | 2026-06-13 |
| THY38D | - | 4 | 2026-06-17 |
| THY9GV | - | 3 | 2026-07-01 |
| THY94E | - | 3 | 2026-06-28 |
| THY8TY | - | 3 | 2026-07-07 |
| THY7BH | - | 3 | 2026-07-02 |
| THY646 | - | 3 | 2026-07-13 |
| THY597 | Turkish Airlines | 3 | 2026-05-29 |
| THY4LE | Turkish Airlines | 3 | 2026-05-30 |
| THY4ES | Turkish Airlines | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY505 | - | Jul 14, 16:45 UTC | Jul 14, 18:30 UTC | 1h 45m |
| 2026-07-13 | THY646 | - | Jul 13, 23:30 UTC | Jul 14, 13:40 UTC | 14h 10m |
| 2026-07-13 | THY54D | - | Jul 13, 16:50 UTC | Jul 13, 19:20 UTC | 2h 30m |
| 2026-07-13 | THY9QR | - | Jul 13, 12:40 UTC | Jul 13, 15:30 UTC | 2h 50m |
| 2026-07-13 | THY7MP | - | Jul 13, 08:05 UTC | Jul 13, 10:45 UTC | 2h 40m |
| 2026-07-13 | THY3RK | - | Jul 13, 04:15 UTC | Jul 13, 06:45 UTC | 2h 30m |
| 2026-07-12 | THY7HE | - | Jul 12, 14:35 UTC | Jul 12, 17:15 UTC | 2h 40m |
| 2026-07-12 | THY1ZL | - | Jul 12, 10:05 UTC | Jul 12, 13:10 UTC | 3h 5m |
| 2026-07-12 | THY506 | - | Jul 12, 01:45 UTC | Jul 12, 08:10 UTC | 6h 25m |
| 2026-07-11 | THY505 | - | Jul 11, 17:20 UTC | Jul 12, 00:15 UTC | 6h 55m |
| 2026-07-10 | THY647 | - | Jul 10, 23:15 UTC | Jul 11, 13:20 UTC | 14h 5m |
| 2026-07-10 | THY126 | - | Jul 10, 11:45 UTC | Jul 10, 19:35 UTC | 7h 50m |
| 2026-07-09 | THY84W | - | Jul 9, 15:50 UTC | Jul 10, 08:40 UTC | 16h 50m |
| 2026-07-08 | THY647 | - | Jul 8, 23:10 UTC | Jul 9, 13:25 UTC | 14h 15m |
| 2026-07-08 | THY647 | - | Jul 8, 02:35 UTC | Jul 8, 16:15 UTC | 13h 40m |
| 2026-07-07 | THY646 | - | Jul 7, 23:15 UTC | Jul 8, 01:00 UTC | 1h 45m |
| 2026-07-07 | THY8TY | - | Jul 7, 09:45 UTC | Jul 7, 20:20 UTC | 10h 35m |
| 2026-07-06 | THY560 | IST → JRO | Jul 6, 13:25 UTC | Jul 7, 06:25 UTC | 17h 0m |
| 2026-07-06 | THY1448 | - | Jul 6, 06:10 UTC | Jul 6, 10:10 UTC | 4h 0m |
| 2026-07-05 | THY9SA | - | Jul 5, 18:00 UTC | Jul 5, 22:05 UTC | 4h 5m |
| 2026-07-05 | THY8AD | - | Jul 5, 14:35 UTC | Jul 5, 16:05 UTC | 1h 30m |
| 2026-07-05 | THY6NG | - | Jul 5, 11:00 UTC | Jul 5, 12:50 UTC | 1h 50m |
| 2026-07-04 | THY88K | - | Jul 4, 16:05 UTC | Jul 5, 08:45 UTC | 16h 40m |
| 2026-07-03 | THY647 | - | Jul 3, 23:35 UTC | Jul 4, 13:20 UTC | 13h 45m |
| 2026-07-03 | THY2RE | - | Jul 3, 19:15 UTC | Jul 3, 20:35 UTC | 1h 20m |
| 2026-07-03 | THY8DT | - | Jul 3, 16:55 UTC | Jul 3, 18:10 UTC | 1h 15m |
| 2026-07-02 | THY647 | - | Jul 2, 23:45 UTC | Jul 3, 13:40 UTC | 13h 55m |
| 2026-07-02 | THY1LX | - | Jul 2, 18:35 UTC | Jul 2, 20:25 UTC | 1h 50m |
| 2026-07-02 | THY6LH | - | Jul 2, 15:30 UTC | Jul 2, 17:15 UTC | 1h 45m |
| 2026-07-02 | THY4BY | - | Jul 2, 09:40 UTC | Jul 2, 11:50 UTC | 2h 10m |
| 2026-07-02 | THY7BH | - | Jul 2, 03:50 UTC | Jul 2, 06:35 UTC | 2h 45m |
| 2026-07-01 | THY7QN | - | Jul 1, 22:45 UTC | Jul 2, 02:10 UTC | 3h 25m |
| 2026-07-01 | THY9GV | - | Jul 1, 19:20 UTC | Jul 1, 21:05 UTC | 1h 45m |
| 2026-07-01 | THY9GV | - | Jul 1, 17:10 UTC | Jul 1, 19:15 UTC | 2h 5m |
| 2026-07-01 | THY1BC | - | Jul 1, 08:50 UTC | Jul 1, 11:30 UTC | 2h 40m |
| 2026-07-01 | THY8VN | - | Jul 1, 04:50 UTC | Jul 1, 07:20 UTC | 2h 30m |
| 2026-06-30 | THY2HY | - | Jun 30, 11:40 UTC | Jul 1, 02:10 UTC | 14h 30m |
| 2026-06-29 | THY3LG | - | Jun 29, 15:49 UTC | Jun 30, 08:30 UTC | 16h 41m |
| 2026-06-29 | THY1RL | - | Jun 29, 09:50 UTC | Jun 29, 13:44 UTC | 3h 55m |
| 2026-06-29 | THY1297 | - | Jun 29, 04:14 UTC | Jun 29, 08:04 UTC | 3h 50m |
| 2026-06-28 | THY1HE | - | Jun 28, 17:19 UTC | Jun 28, 21:10 UTC | 3h 50m |
| 2026-06-28 | THY6TU | - | Jun 28, 11:29 UTC | Jun 28, 15:24 UTC | 3h 55m |
| 2026-06-28 | THY94E | - | Jun 28, 09:45 UTC | Jun 28, 10:04 UTC | 20m |
| 2026-06-27 | THY50K | IST → KGL | Jun 27, 16:39 UTC | Jun 28, 08:50 UTC | 16h 10m |
| 2026-06-27 | THY4BY | - | Jun 27, 09:24 UTC | Jun 27, 11:59 UTC | 2h 35m |
| 2026-06-27 | THY7BH | - | Jun 27, 03:49 UTC | Jun 27, 06:40 UTC | 2h 50m |
| 2026-06-26 | THY1HE | - | Jun 26, 17:15 UTC | Jun 26, 21:10 UTC | 3h 55m |
| 2026-06-26 | THY6TU | - | Jun 26, 11:20 UTC | Jun 26, 15:20 UTC | 4h 0m |
| 2026-06-25 | THY88K | - | Jun 25, 15:44 UTC | Jun 26, 08:54 UTC | 17h 10m |
| 2026-06-25 | THY4BY | - | Jun 25, 09:50 UTC | Jun 25, 12:04 UTC | 2h 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 TC-LCB page for operator, model, and routing details .