sensors Mode-S transponder
4CC539
ICAO 24-bit transponder address
Currently assigned to TF-MYB · BEECH 200 Super King Air
- Hex
- 4CC539
- Octal
- 23142471
- Decimal
- 5,031,225
- Tail
- TF-MYB
- Type
- BE20
- Flights observed
- 247
- Distinct callsigns
- 20
- Country
- -
- Last broadcast
- 13h ago
Last known position
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FNA570 | - | 53 | 2026-07-13 |
| FNA571 | - | 51 | 2026-07-13 |
| FNA590 | - | 23 | 2026-05-28 |
| FNA591 | - | 15 | 2026-05-28 |
| FNA592 | - | 14 | 2026-05-28 |
| FNA593 | - | 13 | 2026-05-27 |
| FNA575 | - | 12 | 2026-07-10 |
| FNA574 | - | 10 | 2026-07-10 |
| FNA550 | - | 8 | 2026-07-09 |
| FNA514 | - | 4 | 2026-06-04 |
| FNA513 | - | 4 | 2026-06-04 |
| FNA777 | - | 3 | 2026-06-27 |
| FNA541 | - | 3 | 2026-07-01 |
| FNA540 | - | 3 | 2026-07-01 |
| FNA778 | - | 2 | 2026-06-27 |
| FNA597 | - | 2 | 2026-04-22 |
| FNA596 | - | 2 | 2026-04-22 |
| FNA551 | - | 2 | 2026-07-09 |
| FNA516 | - | 2 | 2026-06-11 |
| FNA515 | - | 2 | 2026-06-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FNA573 | - | Jul 13, 14:10 UTC | Jul 13, 14:25 UTC | 15m |
| 2026-07-13 | FNA572 | - | Jul 13, 12:45 UTC | Jul 13, 13:05 UTC | 20m |
| 2026-07-13 | FNA571 | - | Jul 13, 11:40 UTC | Jul 13, 12:00 UTC | 20m |
| 2026-07-13 | FNA570 | - | Jul 13, 10:15 UTC | Jul 13, 10:40 UTC | 25m |
| 2026-07-10 | FNA575 | - | Jul 10, 13:45 UTC | Jul 10, 13:55 UTC | 10m |
| 2026-07-10 | FNA574 | - | Jul 10, 12:35 UTC | Jul 10, 12:50 UTC | 15m |
| 2026-07-10 | FNA571 | - | Jul 10, 11:10 UTC | Jul 10, 11:30 UTC | 20m |
| 2026-07-10 | FNA570 | - | Jul 10, 10:00 UTC | Jul 10, 10:25 UTC | 25m |
| 2026-07-09 | FNA551 | - | Jul 9, 19:15 UTC | Jul 9, 19:35 UTC | 20m |
| 2026-07-09 | FNA550 | - | Jul 9, 17:25 UTC | Jul 9, 17:40 UTC | 15m |
| 2026-07-09 | FNA550 | - | Jul 9, 16:40 UTC | Jul 9, 16:50 UTC | 10m |
| 2026-07-09 | FNA571 | - | Jul 9, 11:20 UTC | Jul 9, 11:45 UTC | 25m |
| 2026-07-09 | FNA570 | - | Jul 9, 10:05 UTC | Jul 9, 10:30 UTC | 25m |
| 2026-07-08 | FNA571 | - | Jul 8, 11:15 UTC | Jul 8, 11:40 UTC | 25m |
| 2026-07-08 | FNA570 | - | Jul 8, 10:00 UTC | Jul 8, 10:20 UTC | 20m |
| 2026-07-07 | FNA571 | - | Jul 7, 11:20 UTC | Jul 7, 11:40 UTC | 20m |
| 2026-07-07 | FNA570 | - | Jul 7, 10:10 UTC | Jul 7, 10:30 UTC | 20m |
| 2026-07-06 | FNA571 | - | Jul 6, 11:10 UTC | Jul 6, 11:35 UTC | 25m |
| 2026-07-06 | FNA570 | - | Jul 6, 10:05 UTC | Jul 6, 10:30 UTC | 25m |
| 2026-07-05 | FNA571 | - | Jul 5, 14:10 UTC | Jul 5, 14:25 UTC | 15m |
| 2026-07-05 | FNA570 | - | Jul 5, 12:55 UTC | Jul 5, 13:20 UTC | 25m |
| 2026-07-03 | FNA575 | - | Jul 3, 14:10 UTC | Jul 3, 14:20 UTC | 10m |
| 2026-07-03 | FNA574 | - | Jul 3, 12:40 UTC | Jul 3, 12:55 UTC | 15m |
| 2026-07-03 | FNA571 | - | Jul 3, 11:20 UTC | Jul 3, 11:40 UTC | 20m |
| 2026-07-03 | FNA570 | - | Jul 3, 10:10 UTC | Jul 3, 10:35 UTC | 25m |
| 2026-07-02 | FNA571 | - | Jul 2, 11:25 UTC | Jul 2, 11:45 UTC | 20m |
| 2026-07-02 | FNA570 | - | Jul 2, 10:10 UTC | Jul 2, 10:40 UTC | 30m |
| 2026-07-01 | FNA541 | - | Jul 1, 15:40 UTC | Jul 1, 16:10 UTC | 30m |
| 2026-07-01 | FNA540 | - | Jul 1, 12:30 UTC | Jul 1, 12:50 UTC | 20m |
| 2026-07-01 | FNA571 | - | Jul 1, 11:20 UTC | Jul 1, 11:45 UTC | 25m |
| 2026-07-01 | FNA570 | - | Jul 1, 10:05 UTC | Jul 1, 10:30 UTC | 25m |
| 2026-06-30 | FNA571 | - | Jun 30, 11:20 UTC | Jun 30, 11:40 UTC | 20m |
| 2026-06-30 | FNA570 | - | Jun 30, 10:05 UTC | Jun 30, 10:30 UTC | 25m |
| 2026-06-29 | FNA571 | - | Jun 29, 11:20 UTC | Jun 29, 11:39 UTC | 20m |
| 2026-06-29 | FNA570 | - | Jun 29, 10:15 UTC | Jun 29, 10:40 UTC | 25m |
| 2026-06-28 | FNA571 | - | Jun 28, 14:14 UTC | Jun 28, 14:30 UTC | 15m |
| 2026-06-28 | FNA570 | - | Jun 28, 12:55 UTC | Jun 28, 13:19 UTC | 25m |
| 2026-06-28 | FNA562 | - | Jun 28, 09:30 UTC | Jun 28, 09:39 UTC | 10m |
| 2026-06-28 | FNA561 | - | Jun 28, 08:44 UTC | Jun 28, 09:10 UTC | 25m |
| 2026-06-27 | FNA778 | - | Jun 27, 13:04 UTC | Jun 27, 15:05 UTC | 2h 0m |
| 2026-06-27 | FNA777 | - | Jun 27, 10:50 UTC | Jun 27, 11:50 UTC | 1h 0m |
| 2026-06-27 | FNA777 | - | Jun 27, 07:55 UTC | Jun 27, 09:44 UTC | 1h 50m |
| 2026-06-23 | FNA550 | - | Jun 23, 08:04 UTC | Jun 23, 08:30 UTC | 25m |
| 2026-06-22 | FNA571 | - | Jun 22, 11:19 UTC | Jun 22, 11:35 UTC | 15m |
| 2026-06-22 | FNA570 | - | Jun 22, 10:10 UTC | Jun 22, 10:34 UTC | 25m |
| 2026-06-21 | FNA571 | - | Jun 21, 13:59 UTC | Jun 21, 14:24 UTC | 25m |
| 2026-06-21 | FNA570 | - | Jun 21, 12:49 UTC | Jun 21, 13:09 UTC | 20m |
| 2026-06-19 | FNA551 | - | Jun 19, 12:25 UTC | Jun 19, 12:34 UTC | 10m |
| 2026-06-19 | FNA550 | - | Jun 19, 09:09 UTC | Jun 19, 09:24 UTC | 15m |
| 2026-06-18 | FNA509 | RKV → RKV | Jun 18, 10:50 UTC | Jun 18, 16:55 UTC | 6h 5m |
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 TF-MYB page for operator, model, and routing details .