sensors Mode-S transponder
49D53E
ICAO 24-bit transponder address · allocated to Czech Republic
Currently assigned to OK-MSM · PILATUS PC-12
- Hex
- 49D53E
- Octal
- 22352476
- Decimal
- 4,838,718
- Country
- CZ
- Tail
- OK-MSM
- Type
- PC12
- Flights observed
- 38
- Distinct callsigns
- 19
- Country
- CZ
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 49D53E falls within the block assigned to Czech Republic (CZ) by ICAO Annex 10, Volume III. Every aircraft registered in Czech Republic 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| NTF209M | - | 5 | 2026-04-13 |
| NTF203M | - | 4 | 2026-04-15 |
| NTF208M | - | 3 | 2026-04-19 |
| NTF318M | - | 2 | 2026-05-27 |
| NTF303M | - | 2 | 2026-05-21 |
| NTF279M | - | 2 | 2026-05-13 |
| NTF277M | - | 2 | 2026-05-19 |
| NTF268M | - | 2 | 2026-05-09 |
| NTF258M | - | 2 | 2026-05-04 |
| NTF251M | - | 2 | 2026-04-30 |
| NTF236M | - | 2 | 2026-04-25 |
| NTF225M | - | 2 | 2026-04-22 |
| NTF162M | - | 2 | 2026-05-10 |
| NTF334M | - | 1 | 2026-05-30 |
| NTF319M | - | 1 | 2026-05-27 |
| NTF306M | - | 1 | 2026-05-21 |
| NTF302M | - | 1 | 2026-05-21 |
| NTF280M | - | 1 | 2026-05-13 |
| NTF278M | - | 1 | 2026-05-13 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | NTF334M | - | May 30, 06:15 UTC | May 30, 07:05 UTC | 50m |
| 2026-05-27 | NTF319M | BTS → PRG | May 27, 13:35 UTC | May 27, 14:40 UTC | 1h 5m |
| 2026-05-27 | NTF318M | - | May 27, 11:10 UTC | May 27, 12:25 UTC | 1h 15m |
| 2026-05-27 | NTF318M | - | May 27, 08:55 UTC | May 27, 10:10 UTC | 1h 15m |
| 2026-05-21 | NTF306M | BTS → PRG | May 21, 18:35 UTC | May 21, 19:25 UTC | 50m |
| 2026-05-21 | NTF303M | - | May 21, 16:40 UTC | May 21, 17:45 UTC | 1h 5m |
| 2026-05-21 | NTF303M | - | May 21, 14:35 UTC | May 21, 15:35 UTC | 1h 0m |
| 2026-05-21 | NTF302M | PRG → BTS | May 21, 12:40 UTC | May 21, 13:30 UTC | 50m |
| 2026-05-19 | NTF277M | VIE → PRG | May 19, 14:10 UTC | May 19, 14:50 UTC | 40m |
| 2026-05-19 | NTF277M | PRG → VIE | May 19, 07:15 UTC | May 19, 08:05 UTC | 50m |
| 2026-05-13 | NTF280M | - | May 13, 20:05 UTC | May 13, 20:55 UTC | 50m |
| 2026-05-13 | NTF279M | - | May 13, 19:00 UTC | May 13, 19:40 UTC | 40m |
| 2026-05-13 | NTF279M | - | May 13, 10:45 UTC | May 13, 11:20 UTC | 35m |
| 2026-05-13 | NTF278M | PRG → BTS | May 13, 08:50 UTC | May 13, 09:35 UTC | 45m |
| 2026-05-10 | NTF162M | - | May 10, 13:40 UTC | May 10, 14:59 UTC | 1h 20m |
| 2026-05-10 | NTF162M | - | May 10, 11:40 UTC | May 10, 12:59 UTC | 1h 20m |
| 2026-05-09 | NTF268M | - | May 9, 16:55 UTC | May 9, 19:10 UTC | 2h 15m |
| 2026-05-07 | NTF268M | - | May 7, 08:15 UTC | May 7, 11:05 UTC | 2h 50m |
| 2026-05-04 | NTF258M | - | May 4, 15:40 UTC | May 4, 18:20 UTC | 2h 40m |
| 2026-05-04 | NTF258M | - | May 4, 06:40 UTC | May 4, 09:20 UTC | 2h 40m |
| 2026-04-30 | NTF251M | NCE → PRG | Apr 30, 18:30 UTC | Apr 30, 20:50 UTC | 2h 20m |
| 2026-04-30 | NTF251M | PRG → NCE | Apr 30, 15:20 UTC | Apr 30, 17:10 UTC | 1h 50m |
| 2026-04-25 | NTF236M | - | Apr 25, 14:15 UTC | Apr 25, 15:40 UTC | 1h 25m |
| 2026-04-23 | NTF236M | PRG → WAW | Apr 23, 10:50 UTC | Apr 23, 12:15 UTC | 1h 25m |
| 2026-04-22 | NTF225M | HAM → PRG | Apr 22, 12:25 UTC | Apr 22, 13:50 UTC | 1h 25m |
| 2026-04-21 | NTF225M | PRG → HAM | Apr 21, 06:45 UTC | Apr 21, 08:00 UTC | 1h 15m |
| 2026-04-19 | NTF208M | - | Apr 19, 12:35 UTC | Apr 19, 14:55 UTC | 2h 20m |
| 2026-04-17 | NTF208M | - | Apr 17, 09:20 UTC | Apr 17, 10:40 UTC | 1h 20m |
| 2026-04-17 | NTF208M | - | Apr 17, 08:30 UTC | Apr 17, 09:15 UTC | 45m |
| 2026-04-15 | NTF203M | - | Apr 15, 13:01 UTC | Apr 15, 13:25 UTC | 25m |
| 2026-04-15 | NTF203M | - | Apr 15, 11:20 UTC | Apr 15, 12:55 UTC | 1h 35m |
| 2026-04-15 | NTF203M | - | Apr 15, 09:00 UTC | Apr 15, 10:10 UTC | 1h 10m |
| 2026-04-15 | NTF203M | - | Apr 15, 08:10 UTC | Apr 15, 08:55 UTC | 45m |
| 2026-04-13 | NTF209M | - | Apr 13, 12:20 UTC | Apr 13, 13:05 UTC | 45m |
| 2026-04-13 | NTF209M | - | Apr 13, 11:55 UTC | Apr 13, 12:15 UTC | 20m |
| 2026-04-13 | NTF209M | - | Apr 13, 09:45 UTC | Apr 13, 11:10 UTC | 1h 25m |
| 2026-04-13 | NTF209M | LNZ → POW | Apr 13, 08:20 UTC | Apr 13, 09:05 UTC | 45m |
| 2026-04-13 | NTF209M | - | Apr 13, 07:50 UTC | Apr 13, 08:15 UTC | 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 OK-MSM page for operator, model, and routing details .