sensors Mode-S transponder

502D3E

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-AAZ · AIRBUS A220-300

Hex
502D3E
Octal
24026476
Decimal
5,254,462
Country
LV
Tail
YL-AAZ
Type
BCS3
No current signal · last broadcast 4h ago
Flights observed
603
Distinct callsigns
20
Country
LV
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S 502D3E.

Country allocation

The ICAO 24-bit address 502D3E falls within the block assigned to Latvia (LV) by ICAO Annex 10, Volume III. Every aircraft registered in Latvia 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
BTI2YQ - 10 2026-07-10
BTI2VE - 10 2026-07-11
BTI7JW - 9 2026-07-06
BTI30Y - 8 2026-07-05
BTI30W - 8 2026-07-05
AUA312U - 8 2026-04-28
BTI79E - 7 2026-07-14
BTI6RZ - 7 2026-07-12
BTI6RV - 7 2026-07-12
BTI60L - 7 2026-07-03
BTI60K - 7 2026-07-03
BTI43N - 7 2026-07-14
BTI30K - 7 2026-07-10
BTI30E - 7 2026-07-10
BTI9BN - 6 2026-07-12
BTI7BU - 6 2026-07-10
BTI6GN - 6 2026-07-12
BTI4LF - 6 2026-07-10
AUA71V Austrian Airlines 6 2026-04-29
AUA31J Austrian Airlines 6 2026-04-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BTI6UQ - Jul 14, 18:35 UTCJul 14, 20:25 UTC1h 50m
2026-07-14 BTI8BX - Jul 14, 15:25 UTCJul 14, 17:15 UTC1h 50m
2026-07-14 BTI79E - Jul 14, 12:25 UTCJul 14, 14:20 UTC1h 55m
2026-07-14 BTI43N - Jul 14, 08:55 UTCJul 14, 10:50 UTC1h 55m
2026-07-14 BTI1R2 - Jul 14, 06:20 UTCJul 14, 07:40 UTC1h 20m
2026-07-14 BTI15P - Jul 14, 04:20 UTCJul 14, 05:30 UTC1h 10m
2026-07-14 BTI3WX - Jul 14, 02:40 UTCJul 14, 03:25 UTC45m
2026-07-13 BTI3U9 - Jul 13, 21:50 UTCJul 13, 22:30 UTC40m
2026-07-13 BTI4UJ - Jul 13, 18:55 UTCJul 13, 20:10 UTC1h 15m
2026-07-13 BTI6UN - Jul 13, 16:20 UTCJul 13, 17:40 UTC1h 20m
2026-07-13 BTI8MT PRG → RIX Jul 13, 13:00 UTCJul 13, 14:30 UTC1h 30m
2026-07-13 BTI3VL - Jul 13, 10:25 UTCJul 13, 12:05 UTC1h 40m
2026-07-13 BTI8ED - Jul 13, 07:35 UTCJul 13, 09:25 UTC1h 50m
2026-07-13 BTI89G - Jul 13, 04:30 UTCJul 13, 06:20 UTC1h 50m
2026-07-13 BTI32M - Jul 13, 02:40 UTCJul 13, 03:20 UTC40m
2026-07-12 BTI32B - Jul 12, 22:00 UTCJul 12, 22:35 UTC35m
2026-07-12 BTI11X - Jul 12, 19:01 UTCJul 12, 19:50 UTC50m
2026-07-12 BTI1X9 - Jul 12, 17:20 UTCJul 12, 18:10 UTC50m
2026-07-12 BTI6GN - Jul 12, 14:25 UTCJul 12, 16:30 UTC2h 5m
2026-07-12 BTI9BN - Jul 12, 11:30 UTCJul 12, 13:25 UTC1h 55m
2026-07-12 BTI6RZ - Jul 12, 08:40 UTCJul 12, 10:35 UTC1h 55m
2026-07-12 BTI6RV - Jul 12, 04:55 UTCJul 12, 06:50 UTC1h 55m
2026-07-11 BTI62D - Jul 11, 17:30 UTCJul 11, 19:30 UTC2h 0m
2026-07-11 BTI6D9 - Jul 11, 14:15 UTCJul 11, 16:05 UTC1h 50m
2026-07-11 BTI34G VNO → RIX Jul 11, 12:55 UTCJul 11, 13:25 UTC30m
2026-07-11 BTI34K - Jul 11, 11:25 UTCJul 11, 12:00 UTC35m
2026-07-11 BTI7EG FRA → RIX Jul 11, 08:35 UTCJul 11, 10:30 UTC1h 55m
2026-07-11 BTI83L - Jul 11, 05:01 UTCJul 11, 06:55 UTC1h 55m
2026-07-11 BTI2VE - Jul 11, 02:00 UTCJul 11, 03:25 UTC1h 25m
2026-07-10 BTI2YQ - Jul 10, 21:05 UTCJul 10, 22:20 UTC1h 15m
2026-07-10 BTI4LF - Jul 10, 18:00 UTCJul 10, 19:25 UTC1h 25m
2026-07-10 BTI7BU RIX → BLL Jul 10, 15:30 UTCJul 10, 16:50 UTC1h 20m
2026-07-10 BTI30E HEL → RIX Jul 10, 13:15 UTCJul 10, 14:00 UTC45m
2026-07-10 BTI30K - Jul 10, 11:30 UTCJul 10, 12:20 UTC50m
2026-07-10 BTI6RZ - Jul 10, 08:35 UTCJul 10, 10:30 UTC1h 55m
2026-07-10 BTI6RV - Jul 10, 05:00 UTCJul 10, 06:50 UTC1h 50m
2026-07-10 BTI3WX - Jul 10, 02:30 UTCJul 10, 03:10 UTC40m
2026-07-09 BTI3U9 - Jul 9, 21:15 UTCJul 9, 21:50 UTC35m
2026-07-09 BTI2J4 - Jul 9, 18:20 UTCJul 9, 19:45 UTC1h 25m
2026-07-09 BTI84W - Jul 9, 15:45 UTCJul 9, 17:05 UTC1h 20m
2026-07-09 BTI3MD TMP → RIX Jul 9, 12:35 UTCJul 9, 13:25 UTC50m
2026-07-09 BTI9FY - Jul 9, 10:50 UTCJul 9, 11:40 UTC50m
2026-07-09 BTI7EG - Jul 9, 08:00 UTCJul 9, 09:55 UTC1h 55m
2026-07-09 BTI83L - Jul 9, 04:55 UTCJul 9, 06:40 UTC1h 45m
2026-07-09 BTI35T - Jul 9, 02:30 UTCJul 9, 03:20 UTC50m
2026-07-08 BTI35Z - Jul 8, 21:20 UTCJul 8, 22:10 UTC50m
2026-07-08 BTI14B CPH → RIX Jul 8, 18:45 UTCJul 8, 19:50 UTC1h 5m
2026-07-08 BTI1P9 - Jul 8, 16:25 UTCJul 8, 17:30 UTC1h 5m
2026-07-08 BTI31B - Jul 8, 14:45 UTCJul 8, 15:15 UTC30m
2026-07-08 BTI31C - Jul 8, 13:25 UTCJul 8, 13:55 UTC30m

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 YL-AAZ page for operator, model, and routing details .

Mode-S 502D3E frequently asked

What is Mode-S code 502D3E?
502D3E is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-AAZ.
Where is Mode-S 502D3E registered?
Mode-S code 502D3E is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D3E broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D3E, octal 24026476, decimal 5,254,462.
What flights does 502D3E operate?
Mode-S 502D3E has broadcast 20 distinct callsigns, including BTI2YQ, BTI2VE, BTI7JW, BTI30Y, BTI30W.