sensors Mode-S transponder

0AB044

ICAO 24-bit transponder address · allocated to Belize

Currently assigned to V3-HJA · CESSNA 208 Caravan

Hex
0AB044
Octal
02530104
Decimal
700,484
Country
BZ
Tail
V3-HJA
Type
C208
No current signal · last broadcast 15h ago
Flights observed
68
Distinct callsigns
5
Country
BZ
Last broadcast
15h ago

Last known position

Most recent position reported by Mode-S 0AB044.

Country allocation

The ICAO 24-bit address 0AB044 falls within the block assigned to Belize (BZ) by ICAO Annex 10, Volume III. Every aircraft registered in Belize 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

Callsign Airline Flights Last seen
TOS6610 Tropic Air 33 2026-05-29
TOS6611 Tropic Air 32 2026-05-29
TOT6611 - 1 2026-05-02
TOS6631 - 1 2026-05-17
TOS6630 - 1 2026-05-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 TOS6611 CUN → BZE May 29, 19:05 UTCMay 29, 19:45 UTC40m
2026-05-29 TOS6610 BZE → CUN May 29, 17:30 UTCMay 29, 18:10 UTC40m
2026-05-28 TOS6611 CUN → BZE May 28, 18:45 UTCMay 28, 19:20 UTC35m
2026-05-28 TOS6610 BZE → CUN May 28, 17:30 UTCMay 28, 18:10 UTC40m
2026-05-26 TOS6611 CUN → BZE May 26, 19:20 UTCMay 26, 19:55 UTC35m
2026-05-26 TOS6610 BZE → CUN May 26, 17:30 UTCMay 26, 18:10 UTC40m
2026-05-25 TOS6611 CUN → BZE May 25, 19:25 UTCMay 25, 20:04 UTC40m
2026-05-25 TOS6610 BZE → CUN May 25, 17:30 UTCMay 25, 18:10 UTC40m
2026-05-24 TOS6611 CUN → BZE May 24, 19:20 UTCMay 24, 19:55 UTC35m
2026-05-24 TOS6610 BZE → CUN May 24, 17:35 UTCMay 24, 18:10 UTC35m
2026-05-23 TOS6611 CUN → BZE May 23, 19:15 UTCMay 23, 19:55 UTC40m
2026-05-23 TOS6610 BZE → CUN May 23, 17:15 UTCMay 23, 17:50 UTC35m
2026-05-22 TOS6610 BZE → CUN May 22, 19:15 UTCMay 22, 19:50 UTC35m
2026-05-22 TOS6610 BZE → CUN May 22, 17:35 UTCMay 22, 18:05 UTC30m
2026-05-21 TOS6611 CUN → BZE May 21, 19:15 UTCMay 21, 19:55 UTC40m
2026-05-21 TOS6610 BZE → CUN May 21, 17:25 UTCMay 21, 18:00 UTC35m
2026-05-20 TOS6611 CUN → BZE May 20, 18:45 UTCMay 20, 19:25 UTC40m
2026-05-20 TOS6610 BZE → CUN May 20, 17:20 UTCMay 20, 17:55 UTC35m
2026-05-19 TOS6611 CUN → BZE May 19, 19:05 UTCMay 19, 19:40 UTC35m
2026-05-19 TOS6610 BZE → CUN May 19, 17:25 UTCMay 19, 18:00 UTC35m
2026-05-18 TOS6611 CUN → BZE May 18, 19:00 UTCMay 18, 19:35 UTC35m
2026-05-18 TOS6610 BZE → CUN May 18, 17:25 UTCMay 18, 18:00 UTC35m
2026-05-17 TOS6631 - May 17, 18:05 UTCMay 17, 18:45 UTC40m
2026-05-17 TOS6630 - May 17, 16:45 UTCMay 17, 17:25 UTC40m
2026-05-16 TOS6611 CUN → BZE May 16, 19:20 UTCMay 16, 20:00 UTC40m
2026-05-16 TOS6610 BZE → CUN May 16, 17:20 UTCMay 16, 18:00 UTC40m
2026-05-15 TOS6611 CUN → BZE May 15, 19:10 UTCMay 15, 19:45 UTC35m
2026-05-15 TOS6610 BZE → CUN May 15, 17:20 UTCMay 15, 17:55 UTC35m
2026-05-14 TOS6611 CUN → BZE May 14, 19:00 UTCMay 14, 19:35 UTC35m
2026-05-14 TOS6610 BZE → CUN May 14, 17:30 UTCMay 14, 18:05 UTC35m
2026-05-13 TOS6611 CUN → BZE May 13, 19:20 UTCMay 13, 19:50 UTC30m
2026-05-13 TOS6610 BZE → CUN May 13, 17:40 UTCMay 13, 18:15 UTC35m
2026-05-03 TOS6611 CUN → BZE May 3, 19:20 UTCMay 3, 19:55 UTC35m
2026-05-03 TOS6610 BZE → CUN May 3, 17:29 UTCMay 3, 18:05 UTC35m
2026-05-02 TOT6611 - May 2, 19:40 UTCMay 2, 20:15 UTC35m
2026-05-02 TOS6610 BZE → CUN May 2, 17:35 UTCMay 2, 18:10 UTC35m
2026-05-01 TOS6611 CUN → BZE May 1, 19:05 UTCMay 1, 19:45 UTC40m
2026-05-01 TOS6610 BZE → CUN May 1, 17:25 UTCMay 1, 18:00 UTC35m
2026-04-30 TOS6611 CUN → BZE Apr 30, 19:15 UTCApr 30, 19:50 UTC35m
2026-04-30 TOS6610 BZE → CUN Apr 30, 17:10 UTCApr 30, 17:45 UTC35m
2026-04-29 TOS6611 CUN → BZE Apr 29, 19:00 UTCApr 29, 19:35 UTC35m
2026-04-29 TOS6610 BZE → CUN Apr 29, 17:25 UTCApr 29, 18:00 UTC35m
2026-04-28 TOS6611 CUN → BZE Apr 28, 18:45 UTCApr 28, 19:20 UTC35m
2026-04-28 TOS6610 BZE → CUN Apr 28, 17:20 UTCApr 28, 18:00 UTC40m
2026-04-27 TOS6611 CUN → BZE Apr 27, 19:20 UTCApr 27, 19:50 UTC30m
2026-04-27 TOS6610 BZE → CUN Apr 27, 17:40 UTCApr 27, 18:15 UTC35m
2026-04-26 TOS6611 CUN → BZE Apr 26, 19:20 UTCApr 26, 19:55 UTC35m
2026-04-26 TOS6610 BZE → CUN Apr 26, 17:35 UTCApr 26, 18:05 UTC30m
2026-04-24 TOS6611 CUN → BZE Apr 24, 19:00 UTCApr 24, 19:35 UTC35m
2026-04-24 TOS6610 BZE → CUN Apr 24, 17:30 UTCApr 24, 18:10 UTC40m

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

Mode-S 0AB044 frequently asked

What is Mode-S code 0AB044?
0AB044 is an ICAO 24-bit transponder address. Allocated to Belize. Assigned to V3-HJA.
Where is Mode-S 0AB044 registered?
Mode-S code 0AB044 is allocated to Belize (BZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0AB044 broadcasting right now?
No active broadcast right now. Last signal was 15h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0AB044, octal 02530104, decimal 700,484.
What flights does 0AB044 operate?
Mode-S 0AB044 has broadcast 5 distinct callsigns, including TOS6610, TOS6611, TOT6611, TOS6631, TOS6630.