sensors Mode-S transponder
503D17
ICAO 24-bit transponder address · allocated to Lithuania
Currently assigned to LY-LTA · HAWKER BEECHCRAFT Hawker 750/850
- Hex
- 503D17
- Octal
- 24036427
- Decimal
- 5,258,519
- Country
- LT
- Tail
- LY-LTA
- Type
- H25B
- Flights observed
- 101
- Distinct callsigns
- 5
- Country
- LT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 503D17 falls within the block assigned to Lithuania (LT) by ICAO Annex 10, Volume III. Every aircraft registered in Lithuania 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | LTC601 | - | Jul 21, 08:55 UTC | Jul 21, 12:10 UTC | 3h 15m |
| 2026-07-20 | SZN209 | DSS → CKY | Jul 20, 15:35 UTC | Jul 20, 15:50 UTC | 15m |
| 2026-07-20 | LTC601 | - | Jul 20, 13:50 UTC | Jul 20, 14:25 UTC | 35m |
| 2026-07-20 | LTC601 | - | Jul 20, 09:10 UTC | Jul 20, 12:35 UTC | 3h 25m |
| 2026-07-19 | LTC601 | - | Jul 19, 12:50 UTC | Jul 19, 13:40 UTC | 50m |
| 2026-07-19 | LTC601 | LCA → WMI | Jul 19, 08:25 UTC | Jul 19, 11:45 UTC | 3h 20m |
| 2026-07-18 | LTC601 | - | Jul 18, 10:30 UTC | Jul 18, 13:35 UTC | 3h 5m |
| 2026-07-17 | LTC601 | TBS → WMI | Jul 17, 08:04 UTC | Jul 17, 11:55 UTC | 3h 50m |
| 2026-07-16 | LTC601 | - | Jul 16, 14:29 UTC | Jul 16, 14:40 UTC | 10m |
| 2026-07-16 | LTC601 | - | Jul 16, 10:40 UTC | Jul 16, 13:25 UTC | 2h 45m |
| 2026-07-14 | LTC601 | - | Jul 14, 14:10 UTC | Jul 14, 18:55 UTC | 4h 45m |
| 2026-07-12 | LTC601 | - | Jul 12, 09:30 UTC | Jul 12, 13:25 UTC | 3h 55m |
| 2026-07-11 | LTC601 | - | Jul 11, 13:40 UTC | Jul 11, 14:25 UTC | 45m |
| 2026-07-11 | LTC601 | - | Jul 11, 10:25 UTC | Jul 11, 12:55 UTC | 2h 30m |
| 2026-07-10 | SZN216 | - | Jul 10, 00:25 UTC | Jul 10, 00:35 UTC | 10m |
| 2026-07-09 | LTC601 | - | Jul 9, 13:15 UTC | Jul 9, 14:05 UTC | 50m |
| 2026-07-09 | SZN332 | - | Jul 9, 12:15 UTC | Jul 9, 12:35 UTC | 20m |
| 2026-07-08 | SZN332 | - | Jul 8, 04:40 UTC | Jul 8, 12:10 UTC | 7h 30m |
| 2026-07-07 | LTC601 | - | Jul 7, 12:20 UTC | Jul 7, 16:10 UTC | 3h 50m |
| 2026-07-07 | LTC601 | - | Jul 7, 05:05 UTC | Jul 7, 09:05 UTC | 4h 0m |
| 2026-07-06 | LTC601 | - | Jul 6, 18:50 UTC | Jul 7, 05:00 UTC | 10h 10m |
| 2026-07-06 | LTC601 | IBZ → NCE | Jul 6, 09:25 UTC | Jul 6, 10:45 UTC | 1h 20m |
| 2026-07-05 | - | - | Jul 5, 18:45 UTC | Jul 5, 18:55 UTC | 10m |
| 2026-07-04 | LTC601 | - | Jul 4, 07:55 UTC | Jul 4, 11:05 UTC | 3h 10m |
| 2026-07-04 | LTC601 | - | Jul 4, 06:30 UTC | Jul 4, 07:10 UTC | 40m |
| 2026-07-03 | LTC601 | - | Jul 3, 07:25 UTC | Jul 3, 09:40 UTC | 2h 15m |
| 2026-07-02 | LTC601 | - | Jul 2, 11:50 UTC | Jul 2, 12:50 UTC | 1h 0m |
| 2026-07-01 | LTC601 | - | Jul 1, 10:50 UTC | Jul 1, 13:45 UTC | 2h 55m |
| 2026-07-01 | LTC601 | - | Jul 1, 06:35 UTC | Jul 1, 07:30 UTC | 55m |
| 2026-06-29 | SZN306 | - | Jun 29, 19:05 UTC | Jun 29, 19:24 UTC | 20m |
| 2026-06-29 | LTC601 | - | Jun 29, 12:00 UTC | Jun 29, 14:25 UTC | 2h 25m |
| 2026-06-29 | LTC601 | - | Jun 29, 08:39 UTC | Jun 29, 10:55 UTC | 2h 15m |
| 2026-06-28 | LTC601 | - | Jun 28, 10:39 UTC | Jun 28, 13:00 UTC | 2h 20m |
| 2026-06-27 | LTC601 | - | Jun 27, 05:39 UTC | Jun 27, 09:00 UTC | 3h 20m |
| 2026-06-27 | LTC601 | VNO → RIX | Jun 27, 03:30 UTC | Jun 27, 04:09 UTC | 40m |
| 2026-06-25 | LTC601 | - | Jun 25, 14:09 UTC | Jun 25, 18:10 UTC | 4h 0m |
| 2026-06-23 | LTC601 | - | Jun 23, 15:55 UTC | Jun 23, 18:29 UTC | 2h 35m |
| 2026-06-21 | LTC601 | - | Jun 21, 11:55 UTC | Jun 21, 14:30 UTC | 2h 35m |
| 2026-06-20 | LTC601 | - | Jun 20, 09:39 UTC | Jun 20, 16:29 UTC | 6h 50m |
| 2026-06-19 | LTC601 | CGN → RIX | Jun 19, 12:25 UTC | Jun 19, 14:09 UTC | 1h 45m |
| 2026-06-19 | SZN216 | - | Jun 19, 01:45 UTC | Jun 19, 01:54 UTC | 10m |
| 2026-06-18 | LTC601 | - | Jun 18, 17:21 UTC | Jun 18, 18:15 UTC | 54m |
| 2026-06-17 | LTC601 | - | Jun 17, 06:20 UTC | Jun 17, 11:25 UTC | 5h 5m |
| 2026-06-16 | LTC601 | BRU → LCA | Jun 16, 09:45 UTC | Jun 16, 13:34 UTC | 3h 50m |
| 2026-06-15 | - | - | Jun 15, 12:39 UTC | Jun 15, 12:49 UTC | 10m |
| 2026-06-15 | LTC601 | - | Jun 15, 02:04 UTC | Jun 15, 06:35 UTC | 4h 30m |
| 2026-06-13 | LTC601 | - | Jun 13, 09:00 UTC | Jun 13, 13:05 UTC | 4h 5m |
| 2026-06-13 | LTC601 | VNO → TLL | Jun 13, 05:45 UTC | Jun 13, 06:35 UTC | 50m |
| 2026-06-11 | LTC601 | - | Jun 11, 15:15 UTC | Jun 11, 15:55 UTC | 40m |
| 2026-06-11 | LTC601 | LIN → WMI | Jun 11, 12:30 UTC | Jun 11, 14:10 UTC | 1h 40m |
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 LY-LTA page for operator, model, and routing details .