sensors Mode-S transponder
8405CB
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA01KM · DIAMOND DA-42 Guardian
- Hex
- 8405CB
- Octal
- 41002713
- Decimal
- 8,652,235
- Country
- JP
- Tail
- JA01KM
- Type
- DA42
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- JP
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 8405CB 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JA01KM | - | 49 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | JA01KM | - | Jul 23, 04:30 UTC | Jul 23, 06:30 UTC | 2h 0m |
| 2026-07-23 | JA01KM | - | Jul 23, 01:55 UTC | Jul 23, 02:10 UTC | 15m |
| 2026-07-22 | JA01KM | - | Jul 22, 00:10 UTC | Jul 22, 00:55 UTC | 45m |
| 2026-07-21 | JA01KM | - | Jul 21, 04:40 UTC | Jul 21, 06:30 UTC | 1h 50m |
| 2026-07-21 | JA01KM | - | Jul 21, 00:15 UTC | Jul 21, 02:55 UTC | 2h 40m |
| 2026-07-16 | JA01KM | - | Jul 16, 06:45 UTC | Jul 16, 07:00 UTC | 15m |
| 2026-07-16 | - | - | Jul 16, 04:05 UTC | Jul 16, 04:15 UTC | 10m |
| 2026-07-15 | JA01KM | - | Jul 15, 05:10 UTC | Jul 15, 06:10 UTC | 1h 0m |
| 2026-07-15 | JA01KM | - | Jul 15, 00:55 UTC | Jul 15, 01:35 UTC | 40m |
| 2026-07-14 | JA01KM | - | Jul 14, 00:10 UTC | Jul 14, 02:20 UTC | 2h 10m |
| 2026-07-13 | JA01KM | - | Jul 13, 06:01 UTC | Jul 13, 06:15 UTC | 15m |
| 2026-07-13 | JA01KM | - | Jul 13, 00:40 UTC | Jul 13, 02:40 UTC | 2h 0m |
| 2026-07-10 | JA01KM | - | Jul 10, 05:40 UTC | Jul 10, 06:30 UTC | 50m |
| 2026-07-10 | JA01KM | - | Jul 10, 04:05 UTC | Jul 10, 05:05 UTC | 1h 0m |
| 2026-07-10 | JA01KM | - | Jul 10, 02:15 UTC | Jul 10, 02:30 UTC | 15m |
| 2026-07-10 | JA01KM | - | Jul 10, 00:10 UTC | Jul 10, 01:40 UTC | 1h 30m |
| 2026-07-09 | JA01KM | - | Jul 9, 04:10 UTC | Jul 9, 04:55 UTC | 45m |
| 2026-07-09 | JA01KM | - | Jul 9, 02:15 UTC | Jul 9, 02:35 UTC | 20m |
| 2026-07-09 | JA01KM | - | Jul 9, 00:15 UTC | Jul 9, 01:35 UTC | 1h 20m |
| 2026-06-17 | JA01KM | - | Jun 17, 04:05 UTC | Jun 17, 04:45 UTC | 40m |
| 2026-06-16 | JA01KM | - | Jun 16, 04:10 UTC | Jun 16, 04:30 UTC | 20m |
| 2026-06-15 | JA01KM | - | Jun 15, 04:40 UTC | Jun 15, 05:35 UTC | 55m |
| 2026-06-15 | JA01KM | - | Jun 15, 00:10 UTC | Jun 15, 00:49 UTC | 40m |
| 2026-06-12 | JA01KM | - | Jun 12, 05:50 UTC | Jun 12, 06:05 UTC | 15m |
| 2026-06-11 | JA01KM | - | Jun 11, 04:05 UTC | Jun 11, 04:25 UTC | 20m |
| 2026-06-10 | JA01KM | - | Jun 10, 04:10 UTC | Jun 10, 04:35 UTC | 25m |
| 2026-06-08 | JA01KM | - | Jun 8, 03:40 UTC | Jun 8, 03:50 UTC | 10m |
| 2026-06-05 | JA01KM | - | Jun 5, 04:40 UTC | Jun 5, 05:20 UTC | 40m |
| 2026-06-03 | JA01KM | - | Jun 3, 06:10 UTC | Jun 3, 06:20 UTC | 10m |
| 2026-06-03 | JA01KM | - | Jun 3, 04:45 UTC | Jun 3, 05:20 UTC | 35m |
| 2026-06-01 | JA01KM | - | Jun 1, 02:50 UTC | Jun 1, 03:00 UTC | 10m |
| 2026-06-01 | JA01KM | - | Jun 1, 00:20 UTC | Jun 1, 00:55 UTC | 35m |
| 2026-05-29 | JA01KM | - | May 29, 06:15 UTC | May 29, 06:25 UTC | 10m |
| 2026-05-25 | JA01KM | - | May 25, 05:20 UTC | May 25, 05:55 UTC | 35m |
| 2026-05-25 | JA01KM | - | May 25, 04:25 UTC | May 25, 04:35 UTC | 10m |
| 2026-05-25 | JA01KM | - | May 25, 02:40 UTC | May 25, 02:50 UTC | 10m |
| 2026-05-22 | JA01KM | - | May 22, 05:15 UTC | May 22, 05:40 UTC | 25m |
| 2026-05-22 | JA01KM | - | May 22, 01:30 UTC | May 22, 02:00 UTC | 30m |
| 2026-05-19 | JA01KM | - | May 19, 07:00 UTC | May 19, 07:20 UTC | 20m |
| 2026-05-18 | JA01KM | - | May 18, 06:45 UTC | May 18, 07:05 UTC | 20m |
| 2026-05-14 | JA01KM | - | May 14, 02:15 UTC | May 14, 02:30 UTC | 15m |
| 2026-05-11 | JA01KM | - | May 11, 02:00 UTC | May 11, 02:30 UTC | 30m |
| 2026-05-11 | JA01KM | - | May 11, 00:10 UTC | May 11, 00:54 UTC | 45m |
| 2026-05-01 | JA01KM | - | May 1, 00:55 UTC | May 1, 01:20 UTC | 25m |
| 2026-04-30 | JA01KM | - | Apr 30, 00:50 UTC | Apr 30, 01:20 UTC | 30m |
| 2026-04-28 | JA01KM | - | Apr 28, 06:25 UTC | Apr 28, 06:35 UTC | 10m |
| 2026-04-27 | JA01KM | - | Apr 27, 00:35 UTC | Apr 27, 01:00 UTC | 25m |
| 2026-04-24 | JA01KM | - | Apr 24, 06:50 UTC | Apr 24, 07:00 UTC | 10m |
| 2026-04-24 | JA01KM | - | Apr 24, 04:15 UTC | Apr 24, 04:55 UTC | 40m |
| 2026-04-24 | JA01KM | - | Apr 24, 00:05 UTC | Apr 24, 00:50 UTC | 45m |
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 JA01KM page for operator, model, and routing details .