sensors Mode-S transponder
4BB0FA
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LGZ · AIRBUS A-350-900 · operated by Turkish Airlines
- Hex
- 4BB0FA
- Octal
- 22730372
- Decimal
- 4,960,506
- Country
- TR
- Tail
- TC-LGZ
- Type
- A359
- Flights observed
- 218
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB0FA 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 |
|---|---|---|---|
| THY216 | Turkish Airlines | 20 | 2026-06-26 |
| THY215 | Turkish Airlines | 11 | 2026-06-26 |
| THY800 | Turkish Airlines | 10 | 2026-06-11 |
| THY10J | Turkish Airlines | 8 | 2026-06-15 |
| THY45T | Turkish Airlines | 7 | 2026-06-23 |
| THY164 | Turkish Airlines | 7 | 2026-05-09 |
| THY92W | - | 6 | 2026-06-28 |
| THY175 | Turkish Airlines | 6 | 2026-04-27 |
| THY165 | Turkish Airlines | 6 | 2026-05-09 |
| THY056 | - | 6 | 2026-07-09 |
| THY904 | Turkish Airlines | 5 | 2026-04-28 |
| THY69 | Turkish Airlines | 5 | 2026-06-06 |
| THY209 | - | 5 | 2026-06-21 |
| THY174 | Turkish Airlines | 5 | 2026-04-26 |
| THY9ZP | - | 4 | 2026-07-12 |
| THY903 | Turkish Airlines | 4 | 2026-04-27 |
| THY8JK | - | 4 | 2026-06-18 |
| THY8DE | Turkish Airlines | 4 | 2026-06-17 |
| THY68 | Turkish Airlines | 4 | 2026-06-05 |
| THY3UN | Turkish Airlines | 4 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY7JV | - | Jul 14, 05:05 UTC | Jul 14, 06:30 UTC | 1h 25m |
| 2026-07-13 | THY173 | - | Jul 13, 17:20 UTC | Jul 14, 01:30 UTC | 8h 10m |
| 2026-07-13 | THY173 | - | Jul 13, 05:25 UTC | Jul 14, 01:30 UTC | 20h 5m |
| 2026-07-13 | THY173 | - | Jul 13, 03:55 UTC | Jul 14, 01:30 UTC | 21h 35m |
| 2026-07-13 | THY173 | - | Jul 13, 00:35 UTC | Jul 14, 00:25 UTC | 23h 50m |
| 2026-07-12 | THY172 | - | Jul 12, 23:10 UTC | Jul 13, 19:50 UTC | 20h 40m |
| 2026-07-12 | THY9ZP | - | Jul 12, 18:50 UTC | Jul 12, 19:25 UTC | 35m |
| 2026-07-12 | THY7UW | - | Jul 12, 16:30 UTC | Jul 12, 16:55 UTC | 25m |
| 2026-07-11 | THY801 | - | Jul 11, 22:15 UTC | Jul 12, 13:35 UTC | 15h 20m |
| 2026-07-11 | THY801 | - | Jul 11, 19:40 UTC | Jul 11, 20:00 UTC | 20m |
| 2026-07-11 | THY801 | - | Jul 11, 07:00 UTC | Jul 11, 17:45 UTC | 10h 45m |
| 2026-07-10 | THY057 | - | Jul 10, 14:10 UTC | Jul 11, 01:30 UTC | 11h 20m |
| 2026-07-09 | THY056 | - | Jul 9, 23:10 UTC | Jul 10, 10:15 UTC | 11h 5m |
| 2026-07-09 | THY9ZP | - | Jul 9, 16:30 UTC | Jul 9, 19:30 UTC | 3h 0m |
| 2026-07-09 | THY3MJ | - | Jul 9, 11:00 UTC | Jul 9, 14:05 UTC | 3h 5m |
| 2026-07-09 | THY30S | - | Jul 9, 05:45 UTC | Jul 9, 09:05 UTC | 3h 20m |
| 2026-07-08 | THY057 | - | Jul 8, 14:20 UTC | Jul 8, 20:20 UTC | 6h 0m |
| 2026-07-08 | THY056 | - | Jul 8, 10:05 UTC | Jul 8, 10:20 UTC | 15m |
| 2026-07-08 | THY056 | - | Jul 8, 03:40 UTC | Jul 8, 09:30 UTC | 5h 50m |
| 2026-07-07 | THY4YT | EWR → IST | Jul 7, 05:00 UTC | Jul 7, 13:35 UTC | 8h 35m |
| 2026-07-06 | THY29M | IST → EWR | Jul 6, 16:25 UTC | Jul 7, 02:35 UTC | 10h 10m |
| 2026-07-06 | THY1RT | - | Jul 6, 04:55 UTC | Jul 6, 13:10 UTC | 8h 15m |
| 2026-07-05 | THY81D | IST → BOS | Jul 5, 14:25 UTC | Jul 6, 00:20 UTC | 9h 55m |
| 2026-07-05 | THY4WU | - | Jul 5, 09:30 UTC | Jul 5, 11:40 UTC | 2h 10m |
| 2026-07-05 | THY6VM | - | Jul 5, 05:05 UTC | Jul 5, 07:35 UTC | 2h 30m |
| 2026-07-04 | THY81K | - | Jul 4, 23:55 UTC | Jul 5, 01:45 UTC | 1h 50m |
| 2026-07-03 | THY38H | - | Jul 3, 23:40 UTC | Jul 4, 01:20 UTC | 1h 40m |
| 2026-07-03 | THY4SD | - | Jul 3, 18:20 UTC | Jul 3, 21:15 UTC | 2h 55m |
| 2026-07-03 | THY2LD | - | Jul 3, 12:50 UTC | Jul 3, 16:10 UTC | 3h 20m |
| 2026-07-01 | THY163 | SGN → IST | Jul 1, 01:00 UTC | Jul 1, 01:20 UTC | 20m |
| 2026-06-30 | THY162 | - | Jun 30, 00:35 UTC | Jun 30, 20:10 UTC | 19h 36m |
| 2026-06-29 | THY162 | - | Jun 29, 23:14 UTC | Jun 29, 23:39 UTC | 25m |
| 2026-06-29 | THY9ZP | - | Jun 29, 19:24 UTC | Jun 29, 20:00 UTC | 35m |
| 2026-06-29 | THY7UW | IST → BSL | Jun 29, 16:44 UTC | Jun 29, 17:24 UTC | 40m |
| 2026-06-29 | THY8NK | - | Jun 29, 09:40 UTC | Jun 29, 12:05 UTC | 2h 25m |
| 2026-06-29 | THY7JV | - | Jun 29, 04:39 UTC | Jun 29, 06:59 UTC | 2h 20m |
| 2026-06-28 | THY92W | - | Jun 28, 16:05 UTC | Jun 29, 01:05 UTC | 9h 0m |
| 2026-06-28 | THY92W | - | Jun 28, 10:10 UTC | Jun 28, 13:59 UTC | 3h 50m |
| 2026-06-27 | THY21Y | - | Jun 27, 22:55 UTC | Jun 28, 07:54 UTC | 9h 0m |
| 2026-06-27 | THY3PQ | - | Jun 27, 16:20 UTC | Jun 27, 19:24 UTC | 3h 5m |
| 2026-06-27 | THY3UN | IST → LHR | Jun 27, 10:34 UTC | Jun 27, 13:44 UTC | 3h 10m |
| 2026-06-26 | THY216 | GRU → IST | Jun 26, 19:50 UTC | Jun 27, 07:59 UTC | 12h 10m |
| 2026-06-26 | THY216 | GRU → IST | Jun 26, 15:05 UTC | Jun 26, 17:35 UTC | 2h 30m |
| 2026-06-26 | THY216 | GRU → IST | Jun 26, 14:19 UTC | Jun 26, 14:29 UTC | 10m |
| 2026-06-26 | THY215 | GRU → SCL | Jun 26, 08:34 UTC | Jun 26, 11:14 UTC | 2h 40m |
| 2026-06-25 | THY215 | GRU → SCL | Jun 25, 17:49 UTC | Jun 26, 06:15 UTC | 12h 25m |
| 2026-06-25 | THY9WC | - | Jun 25, 02:14 UTC | Jun 25, 14:24 UTC | 12h 10m |
| 2026-06-24 | THY79K | IST → SFO | Jun 24, 10:39 UTC | Jun 24, 23:10 UTC | 12h 30m |
| 2026-06-23 | THY45T | CPT → IST | Jun 23, 14:35 UTC | Jun 24, 00:44 UTC | 10h 10m |
| 2026-06-22 | THY4YT | EWR → IST | Jun 22, 04:49 UTC | Jun 22, 13:39 UTC | 8h 50m |
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-LGZ page for operator, model, and routing details .