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