sensors Mode-S transponder
86E430
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA863J · BOEING 787-9 Dreamliner
- Hex
- 86E430
- Octal
- 41562060
- Decimal
- 8,840,240
- Country
- JP
- Tail
- JA863J
- Type
- B789
- Flights observed
- 98
- Distinct callsigns
- 16
- Country
- JP
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 86E430 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAL17 | Japan Airlines | 12 | 2026-05-16 |
| JAL18 | Japan Airlines | 11 | 2026-05-16 |
| JAL68 | Japan Airlines | 10 | 2026-05-26 |
| JAL67 | Japan Airlines | 10 | 2026-05-26 |
| JAL061 | Japan Airlines | 9 | 2026-05-27 |
| JAL062 | Japan Airlines | 8 | 2026-05-27 |
| JAL57 | Japan Airlines | 6 | 2026-05-21 |
| JAL408 | Japan Airlines | 6 | 2026-05-29 |
| JAL407 | Japan Airlines | 6 | 2026-05-29 |
| JAL723 | Japan Airlines | 5 | 2026-04-22 |
| JAL58 | Japan Airlines | 5 | 2026-05-21 |
| JAL66 | Japan Airlines | 3 | 2026-05-20 |
| JAL65 | Japan Airlines | 3 | 2026-05-20 |
| JAL724 | Japan Airlines | 2 | 2026-04-22 |
| JAL8 | Japan Airlines | 1 | 2026-05-24 |
| JAL7 | Japan Airlines | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | JAL408 | FRA → NRT | May 29, 18:55 UTC | May 29, 22:25 UTC | 3h 30m |
| 2026-05-29 | JAL407 | NRT → FRA | May 29, 02:00 UTC | May 29, 15:30 UTC | 13h 30m |
| 2026-05-27 | JAL061 | LAX → NRT | May 27, 20:40 UTC | May 28, 07:40 UTC | 11h 0m |
| 2026-05-27 | JAL062 | NRT → LAX | May 27, 09:05 UTC | May 27, 18:25 UTC | 9h 20m |
| 2026-05-26 | JAL67 | SEA → NRT | May 26, 20:50 UTC | May 27, 06:20 UTC | 9h 30m |
| 2026-05-26 | JAL68 | NRT → SEA | May 26, 09:25 UTC | May 26, 17:50 UTC | 8h 25m |
| 2026-05-25 | JAL7 | BOS → NRT | May 25, 17:35 UTC | May 26, 06:25 UTC | 12h 50m |
| 2026-05-24 | JAL8 | NRT → BOS | May 24, 10:10 UTC | May 24, 21:45 UTC | 11h 35m |
| 2026-05-23 | JAL408 | FRA → NRT | May 23, 18:30 UTC | May 24, 06:50 UTC | 12h 20m |
| 2026-05-23 | JAL407 | NRT → FRA | May 23, 01:55 UTC | May 23, 15:35 UTC | 13h 39m |
| 2026-05-21 | JAL57 | SFO → NRT | May 21, 21:00 UTC | May 22, 07:35 UTC | 10h 35m |
| 2026-05-21 | JAL58 | NRT → SFO | May 21, 09:45 UTC | May 21, 18:20 UTC | 8h 35m |
| 2026-05-20 | JAL65 | SAN → NRT | May 20, 20:25 UTC | May 21, 07:45 UTC | 11h 20m |
| 2026-05-20 | JAL66 | NRT → SAN | May 20, 09:00 UTC | May 20, 18:10 UTC | 9h 10m |
| 2026-05-19 | JAL67 | SEA → NRT | May 19, 20:30 UTC | May 20, 06:25 UTC | 9h 56m |
| 2026-05-19 | JAL68 | NRT → SEA | May 19, 09:25 UTC | May 19, 17:20 UTC | 7h 55m |
| 2026-05-18 | JAL67 | SEA → NRT | May 18, 20:40 UTC | May 19, 06:35 UTC | 9h 55m |
| 2026-05-18 | JAL68 | NRT → SEA | May 18, 09:20 UTC | May 18, 17:30 UTC | 8h 10m |
| 2026-05-17 | JAL67 | SEA → NRT | May 17, 20:30 UTC | May 18, 05:55 UTC | 9h 25m |
| 2026-05-17 | JAL68 | NRT → SEA | May 17, 09:25 UTC | May 17, 17:25 UTC | 8h 0m |
| 2026-05-16 | JAL17 | YVR → NRT | May 16, 21:10 UTC | May 17, 06:45 UTC | 9h 35m |
| 2026-05-16 | JAL18 | NRT → YVR | May 16, 10:25 UTC | May 16, 18:25 UTC | 8h 0m |
| 2026-05-15 | JAL65 | SAN → NRT | May 15, 20:40 UTC | May 16, 08:01 UTC | 11h 21m |
| 2026-05-15 | JAL66 | NRT → SAN | May 15, 08:50 UTC | May 15, 18:25 UTC | 9h 34m |
| 2026-05-14 | JAL67 | SEA → NRT | May 14, 20:35 UTC | May 15, 05:40 UTC | 9h 5m |
| 2026-05-14 | JAL68 | NRT → SEA | May 14, 09:20 UTC | May 14, 17:30 UTC | 8h 10m |
| 2026-05-13 | JAL67 | SEA → NRT | May 13, 20:30 UTC | May 14, 05:40 UTC | 9h 10m |
| 2026-05-13 | JAL68 | NRT → SEA | May 13, 09:30 UTC | May 13, 17:40 UTC | 8h 10m |
| 2026-05-12 | JAL408 | FRA → NRT | May 12, 18:25 UTC | May 13, 07:15 UTC | 12h 50m |
| 2026-05-12 | JAL407 | NRT → FRA | May 12, 07:25 UTC | May 12, 15:50 UTC | 8h 25m |
| 2026-05-10 | JAL061 | LAX → NRT | May 10, 20:30 UTC | May 11, 07:30 UTC | 11h 0m |
| 2026-05-10 | JAL062 | NRT → LAX | May 10, 08:45 UTC | May 10, 17:49 UTC | 9h 5m |
| 2026-05-09 | JAL67 | SEA → NRT | May 9, 20:30 UTC | May 10, 06:04 UTC | 9h 35m |
| 2026-05-09 | JAL68 | NRT → SEA | May 9, 09:15 UTC | May 9, 17:20 UTC | 8h 5m |
| 2026-05-08 | JAL17 | YVR → NRT | May 8, 21:10 UTC | May 9, 06:40 UTC | 9h 30m |
| 2026-05-08 | JAL18 | NRT → YVR | May 8, 10:25 UTC | May 8, 18:30 UTC | 8h 5m |
| 2026-05-07 | JAL061 | LAX → NRT | May 7, 20:35 UTC | May 8, 07:14 UTC | 10h 40m |
| 2026-05-07 | JAL062 | NRT → LAX | May 7, 09:05 UTC | May 7, 18:25 UTC | 9h 20m |
| 2026-05-06 | JAL17 | YVR → NRT | May 6, 21:10 UTC | May 7, 06:55 UTC | 9h 45m |
| 2026-05-06 | JAL18 | NRT → YVR | May 6, 10:25 UTC | May 6, 18:30 UTC | 8h 5m |
| 2026-05-05 | JAL65 | SAN → NRT | May 5, 21:10 UTC | May 6, 08:25 UTC | 11h 15m |
| 2026-05-05 | JAL66 | NRT → SAN | May 5, 09:20 UTC | May 5, 18:55 UTC | 9h 35m |
| 2026-05-04 | JAL408 | FRA → NRT | May 4, 18:30 UTC | May 5, 07:05 UTC | 12h 36m |
| 2026-05-04 | JAL407 | NRT → FRA | May 4, 02:10 UTC | May 4, 15:35 UTC | 13h 25m |
| 2026-05-01 | JAL17 | YVR → NRT | May 1, 21:50 UTC | May 2, 07:30 UTC | 9h 41m |
| 2026-05-01 | JAL18 | NRT → YVR | May 1, 10:50 UTC | May 1, 18:45 UTC | 7h 55m |
| 2026-04-30 | JAL061 | LAX → NRT | Apr 30, 20:50 UTC | May 1, 07:55 UTC | 11h 5m |
| 2026-04-30 | JAL062 | NRT → LAX | Apr 30, 08:50 UTC | Apr 30, 18:05 UTC | 9h 15m |
| 2026-04-29 | JAL67 | SEA → NRT | Apr 29, 21:05 UTC | Apr 30, 06:45 UTC | 9h 39m |
| 2026-04-29 | JAL68 | NRT → SEA | Apr 29, 10:30 UTC | Apr 29, 18:50 UTC | 8h 20m |
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 JA863J page for operator, model, and routing details .