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