Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

502D24

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-AAV · AIRBUS A220-300

Hex
502D24
Octal
24026444
Decimal
5,254,436
Country
LV
Tail
YL-AAV
Type
BCS3
No current signal · last broadcast 7h ago
Flights observed
526
Distinct callsigns
20
Country
LV
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S 502D24.

Country allocation

The ICAO 24-bit address 502D24 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
BTI9YF Air Baltic 6 2026-06-29
BEL9SZ Brussels Airlines 6 2026-06-12
BEL9CK Brussels Airlines 6 2026-06-12
BEL7TC Brussels Airlines 6 2026-06-11
BEL7DD Brussels Airlines 6 2026-06-11
BEL4SF - 6 2026-07-14
BEL3JY - 6 2026-07-14
BTI84F - 5 2026-06-29
BTI4YE - 5 2026-07-07
BTI31J - 5 2026-07-12
BEL7PK - 5 2026-07-14
BEL6HI - 5 2026-07-14
BEL6AK - 5 2026-07-13
BEL5RA Brussels Airlines 5 2026-06-12
BEL4QA Brussels Airlines 5 2026-06-12
BEL4OZ Brussels Airlines 5 2026-06-11
BEL4HU - 5 2026-07-13
BEL3LY - 5 2026-07-14
BEL2JE Brussels Airlines 5 2026-06-09
BEL1ZT Brussels Airlines 5 2026-06-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BEL3LY - Jul 14, 19:55 UTCJul 14, 20:55 UTC1h 0m
2026-07-14 BEL6HI - Jul 14, 17:20 UTCJul 14, 18:50 UTC1h 30m
2026-07-14 BEL7PK BRU → LJU Jul 14, 14:45 UTCJul 14, 16:00 UTC1h 15m
2026-07-14 BEL4SF - Jul 14, 12:10 UTCJul 14, 13:10 UTC1h 0m
2026-07-14 BEL3JY - Jul 14, 09:40 UTCJul 14, 10:40 UTC1h 0m
2026-07-14 BEL2SC MXP → BRU Jul 14, 07:05 UTCJul 14, 08:20 UTC1h 15m
2026-07-14 BEL5BN BRU → MXP Jul 14, 04:45 UTCJul 14, 05:50 UTC1h 5m
2026-07-13 BEL6AK MUC → BRU Jul 13, 20:10 UTCJul 13, 21:20 UTC1h 10m
2026-07-13 BEL4HU - Jul 13, 17:50 UTCJul 13, 18:50 UTC1h 0m
2026-07-13 BTI6C3 - Jul 13, 14:30 UTCJul 13, 16:35 UTC2h 5m
2026-07-13 BTI1B6 - Jul 13, 12:20 UTCJul 13, 13:20 UTC1h 0m
2026-07-13 BTI1A5 - Jul 13, 09:55 UTCJul 13, 11:00 UTC1h 5m
2026-07-13 BTI25K HAM → RIX Jul 13, 07:01 UTCJul 13, 08:20 UTC1h 20m
2026-07-13 BTI8PW - Jul 13, 04:35 UTCJul 13, 06:05 UTC1h 30m
2026-07-12 BTI630 - Jul 12, 17:20 UTCJul 12, 19:55 UTC2h 35m
2026-07-12 BTI629 RIX → MXP Jul 12, 13:10 UTCJul 12, 15:35 UTC2h 25m
2026-07-12 BTI31J TLL → RIX Jul 12, 11:25 UTCJul 12, 12:01 UTC35m
2026-07-12 BTI9UG - Jul 12, 08:35 UTCJul 12, 10:30 UTC1h 55m
2026-07-12 BTI8FH TLL → AMS Jul 12, 04:40 UTCJul 12, 06:45 UTC2h 5m
2026-07-11 BTI8YW - Jul 11, 20:20 UTCJul 11, 23:05 UTC2h 45m
2026-07-11 BTI86L TLL → BOJ Jul 11, 16:20 UTCJul 11, 19:10 UTC2h 50m
2026-07-11 BTI42U - Jul 11, 11:05 UTCJul 11, 15:20 UTC4h 15m
2026-07-11 BTI8ZF - Jul 11, 05:31 UTCJul 11, 09:55 UTC4h 25m
2026-07-11 BTI8FC - Jul 11, 02:00 UTCJul 11, 04:30 UTC2h 30m
2026-07-10 BTI29P - Jul 10, 22:05 UTCJul 11, 00:25 UTC2h 20m
2026-07-10 BTI98R BRU → TLL Jul 10, 18:30 UTCJul 10, 20:45 UTC2h 15m
2026-07-10 BTI2YH TLL → BRU Jul 10, 15:10 UTCJul 10, 17:30 UTC2h 20m
2026-07-10 BTI92L - Jul 10, 09:45 UTCJul 10, 12:15 UTC2h 30m
2026-07-10 BTI7HQ TLL → CDG Jul 10, 05:40 UTCJul 10, 08:15 UTC2h 35m
2026-07-09 BTI4ZK - Jul 9, 20:30 UTCJul 9, 21:00 UTC30m
2026-07-09 BTI2PG HEL → RIX Jul 9, 18:45 UTCJul 9, 19:25 UTC40m
2026-07-09 BTI24X - Jul 9, 17:05 UTCJul 9, 17:45 UTC40m
2026-07-09 BTI26R BCN → RIX Jul 9, 12:50 UTCJul 9, 16:10 UTC3h 20m
2026-07-09 BTI9TZ - Jul 9, 08:15 UTCJul 9, 11:20 UTC3h 5m
2026-07-09 BTI3G2 - Jul 9, 06:20 UTCJul 9, 06:50 UTC30m
2026-07-09 BTI3ZB - Jul 9, 05:00 UTCJul 9, 05:30 UTC30m
2026-07-09 BTI3WX - Jul 9, 02:35 UTCJul 9, 03:15 UTC40m
2026-07-08 BTI3U9 RIX → TKU Jul 8, 21:30 UTCJul 8, 22:10 UTC40m
2026-07-08 BTI8GC ZRH → RIX Jul 8, 18:05 UTCJul 8, 20:25 UTC2h 20m
2026-07-08 BTI9AG - Jul 8, 14:55 UTCJul 8, 16:55 UTC2h 0m
2026-07-08 BTI30E HEL → RIX Jul 8, 13:10 UTCJul 8, 13:55 UTC45m
2026-07-08 BTI30K - Jul 8, 11:20 UTCJul 8, 12:05 UTC45m
2026-07-08 BTI77U - Jul 8, 09:35 UTCJul 8, 10:05 UTC30m
2026-07-08 BTI38C - Jul 8, 07:10 UTCJul 8, 08:50 UTC1h 40m
2026-07-08 BTI7QF PLQ → AMS Jul 8, 04:10 UTCJul 8, 05:50 UTC1h 40m
2026-07-07 BTI7JW - Jul 7, 21:25 UTCJul 7, 21:40 UTC15m
2026-07-07 BTI15L - Jul 7, 18:45 UTCJul 7, 20:00 UTC1h 15m
2026-07-07 BTI15M - Jul 7, 16:25 UTCJul 7, 17:45 UTC1h 20m
2026-07-07 BTI31B - Jul 7, 14:50 UTCJul 7, 15:25 UTC35m
2026-07-07 BTI31C - Jul 7, 13:20 UTCJul 7, 13:55 UTC35m

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

Mode-S 502D24 frequently asked

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