sensors Mode-S transponder

861B64

ICAO 24-bit transponder address · allocated to Japan

Currently assigned to JA605A · BOEING 767-300

Hex
861B64
Octal
41415544
Decimal
8,788,836
Country
JP
Tail
JA605A
Type
B763
Broadcasting now · callsign ADO87 · 11,750 ft
Flights observed
695
Distinct callsigns
20
Country
JP
Last broadcast
Jul 26, 23:00 UTC

Current position

861B64 is currently broadcasting. Map zoomed to live position.

Country allocation

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 ADO81 HND → AKJ Jul 26, 22:15 UTCJul 26, 23:00 UTC45m
2026-07-26 ADO36 CTS → HND Jul 26, 12:35 UTCJul 26, 13:45 UTC1h 10m
2026-07-26 ADO31 HND → CTS Jul 26, 10:20 UTCJul 26, 11:35 UTC1h 15m
2026-07-26 ADO26 CTS → HND Jul 26, 07:50 UTCJul 26, 09:05 UTC1h 15m
2026-07-26 ADO23 HND → CTS Jul 26, 05:20 UTCJul 26, 06:30 UTC1h 10m
2026-07-26 ADO16 CTS → HND Jul 26, 01:55 UTCJul 26, 03:10 UTC1h 15m
2026-07-25 ADO15 HND → CTS Jul 25, 23:45 UTCJul 26, 01:00 UTC1h 15m
2026-07-25 ADO38 - Jul 25, 13:10 UTCJul 25, 14:45 UTC1h 35m
2026-07-25 ADO35 HND → CTS Jul 25, 11:00 UTCJul 25, 12:15 UTC1h 15m
2026-07-25 ADO60 HKD → HND Jul 25, 08:50 UTCJul 25, 10:00 UTC1h 10m
2026-07-25 ADO59 HND → HKD Jul 25, 06:25 UTCJul 25, 07:25 UTC1h 0m
2026-07-25 ADO20 CTS → HND Jul 25, 03:55 UTCJul 25, 05:10 UTC1h 15m
2026-07-25 ADO19 HND → CTS Jul 25, 01:40 UTCJul 25, 02:50 UTC1h 10m
2026-07-24 ADO12 CTS → HND Jul 24, 23:15 UTCJul 25, 00:20 UTC1h 5m
2026-07-24 ADO39 - Jul 24, 12:45 UTCJul 24, 14:05 UTC1h 20m
2026-07-24 ADO32 - Jul 24, 10:10 UTCJul 24, 11:35 UTC1h 25m
2026-07-24 ADO29 HND → CTS Jul 24, 07:15 UTCJul 24, 08:35 UTC1h 20m
2026-07-24 ADO24 CTS → HND Jul 24, 05:00 UTCJul 24, 06:15 UTC1h 15m
2026-07-24 ADO21 HND → CTS Jul 24, 02:40 UTCJul 24, 04:00 UTC1h 20m
2026-07-24 ADO14 CTS → HND Jul 24, 00:25 UTCJul 24, 01:35 UTC1h 10m
2026-07-23 ADO11 HND → CTS Jul 23, 22:15 UTCJul 23, 23:30 UTC1h 15m
2026-07-23 ADO88 - Jul 23, 11:05 UTCJul 23, 12:25 UTC1h 20m
2026-07-23 ADO87 - Jul 23, 08:55 UTCJul 23, 10:10 UTC1h 15m
2026-07-23 ADO84 AKJ → HND Jul 23, 05:50 UTCJul 23, 07:05 UTC1h 15m
2026-07-23 ADO83 HND → AKJ Jul 23, 03:40 UTCJul 23, 04:55 UTC1h 15m
2026-07-23 ADO82 AKJ → HND Jul 23, 00:35 UTCJul 23, 01:55 UTC1h 20m
2026-07-22 ADO81 HND → AKJ Jul 22, 22:30 UTCJul 22, 23:45 UTC1h 15m
2026-07-22 ADO88 - Jul 22, 10:20 UTCJul 22, 12:20 UTC2h 0m
2026-07-22 ADO83 HND → AKJ Jul 22, 03:35 UTCJul 22, 04:50 UTC1h 15m
2026-07-22 ADO82 - Jul 22, 00:35 UTCJul 22, 01:50 UTC1h 15m
2026-07-21 ADO81 HND → AKJ Jul 21, 22:15 UTCJul 21, 23:30 UTC1h 15m
2026-07-21 ADO88 - Jul 21, 10:55 UTCJul 21, 12:10 UTC1h 15m
2026-07-21 ADO87 - Jul 21, 08:35 UTCJul 21, 09:55 UTC1h 20m
2026-07-21 ADO84 - Jul 21, 05:40 UTCJul 21, 07:05 UTC1h 25m
2026-07-21 ADO83 HND → AKJ Jul 21, 03:35 UTCJul 21, 04:45 UTC1h 10m
2026-07-21 ADO82 AKJ → HND Jul 21, 00:50 UTCJul 21, 02:15 UTC1h 25m
2026-07-20 ADO81 HND → AKJ Jul 20, 22:40 UTCJul 20, 23:50 UTC1h 10m
2026-07-20 ADO38 - Jul 20, 12:45 UTCJul 20, 14:15 UTC1h 30m
2026-07-20 ADO35 - Jul 20, 10:35 UTCJul 20, 11:40 UTC1h 5m
2026-07-20 ADO60 HKD → HND Jul 20, 08:25 UTCJul 20, 09:35 UTC1h 10m
2026-07-20 ADO59 - Jul 20, 06:25 UTCJul 20, 07:25 UTC1h 0m
2026-07-20 ADO20 - Jul 20, 04:05 UTCJul 20, 05:20 UTC1h 15m
2026-07-20 ADO19 HND → CTS Jul 20, 02:05 UTCJul 20, 03:10 UTC1h 5m
2026-07-19 ADO12 CTS → HND Jul 19, 23:20 UTCJul 20, 00:30 UTC1h 10m
2026-07-19 ADO39 - Jul 19, 12:00 UTCJul 19, 13:15 UTC1h 15m
2026-07-19 ADO32 - Jul 19, 09:45 UTCJul 19, 11:00 UTC1h 15m
2026-07-19 ADO29 HND → CTS Jul 19, 07:30 UTCJul 19, 08:50 UTC1h 20m
2026-07-19 ADO24 - Jul 19, 05:15 UTCJul 19, 06:30 UTC1h 15m
2026-07-19 ADO21 - Jul 19, 02:50 UTCJul 19, 04:05 UTC1h 15m
2026-07-19 ADO14 CTS → HND Jul 19, 00:35 UTCJul 19, 01:45 UTC1h 10m

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

Mode-S 861B64 frequently asked

What is Mode-S code 861B64?
861B64 is an ICAO 24-bit transponder address. Allocated to Japan. Assigned to JA605A.
Where is Mode-S 861B64 registered?
Mode-S code 861B64 is allocated to Japan (JP). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 861B64 broadcasting right now?
Yes. Mode-S 861B64 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 861B64, octal 41415544, decimal 8,788,836.
What flights does 861B64 operate?
Mode-S 861B64 has broadcast 20 distinct callsigns, including ADO38, ADO60, ADO59, ADO11, ADO35.