sensors Mode-S transponder

8404F3

ICAO 24-bit transponder address · allocated to Japan

Currently assigned to JA01AM · ATR-42-600

Hex
8404F3
Octal
41002363
Decimal
8,652,019
Country
JP
Tail
JA01AM
Type
AT46
No current signal · last broadcast 1d ago
Flights observed
244
Distinct callsigns
11
Country
JP
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 8404F3.

Country allocation

The ICAO 24-bit address 8404F3 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 11 distinct

Callsign Airline Flights Last seen
AHX802 Amakusa Airlines 49 2026-06-01
AHX801 Amakusa Airlines 43 2026-06-01
AHX106 Amakusa Airlines 31 2026-06-01
AHX102 Amakusa Airlines 29 2026-05-31
AHX108 Amakusa Airlines 26 2026-06-01
AHX105 Amakusa Airlines 26 2026-06-01
AHX107 Amakusa Airlines 13 2026-06-01
AHX101 Amakusa Airlines 11 2026-05-31
AHX201 Amakusa Airlines 8 2026-06-01
AHX202 Amakusa Airlines 6 2026-06-01
AHX01AM Amakusa Airlines 2 2026-05-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-01 AHX108 FUK → AXJ Jun 1, 10:45 UTCJun 1, 11:00 UTC15m
2026-06-01 AHX107 AXJ → FUK Jun 1, 09:45 UTCJun 1, 09:55 UTC10m
2026-06-01 AHX106 FUK → AXJ Jun 1, 08:15 UTCJun 1, 08:25 UTC10m
2026-06-01 AHX105 AXJ → FUK Jun 1, 06:55 UTCJun 1, 07:10 UTC15m
2026-06-01 AHX202 KMJ → AXJ Jun 1, 05:50 UTCJun 1, 06:10 UTC20m
2026-06-01 AHX802 ITM → KMJ Jun 1, 03:55 UTCJun 1, 04:50 UTC55m
2026-06-01 AHX801 KMJ → ITM Jun 1, 02:15 UTCJun 1, 03:00 UTC45m
2026-06-01 AHX201 AXJ → KMJ Jun 1, 01:00 UTCJun 1, 01:10 UTC10m
2026-05-31 AHX102 FUK → AXJ May 31, 23:55 UTCJun 1, 00:10 UTC15m
2026-05-31 AHX101 AXJ → FUK May 31, 22:45 UTCMay 31, 23:00 UTC15m
2026-05-31 AHX108 FUK → AXJ May 31, 10:10 UTCMay 31, 10:30 UTC20m
2026-05-31 AHX107 AXJ → FUK May 31, 09:00 UTCMay 31, 09:20 UTC20m
2026-05-31 AHX102 FUK → AXJ May 31, 00:15 UTCMay 31, 00:35 UTC20m
2026-05-30 AHX101 AXJ → FUK May 30, 23:00 UTCMay 30, 23:15 UTC15m
2026-05-30 AHX108 FUK → AXJ May 30, 10:35 UTCMay 30, 10:45 UTC10m
2026-05-30 AHX107 AXJ → FUK May 30, 09:20 UTCMay 30, 09:40 UTC20m
2026-05-30 AHX106 FUK → AXJ May 30, 08:35 UTCMay 30, 08:50 UTC15m
2026-05-30 AHX105 AXJ → FUK May 30, 07:00 UTCMay 30, 07:15 UTC15m
2026-05-30 AHX202 KMJ → AXJ May 30, 06:15 UTCMay 30, 06:25 UTC10m
2026-05-30 AHX802 ITM → KMJ May 30, 04:10 UTCMay 30, 05:20 UTC1h 10m
2026-05-30 AHX801 KMJ → ITM May 30, 02:20 UTCMay 30, 03:05 UTC45m
2026-05-30 AHX102 FUK → AXJ May 30, 00:05 UTCMay 30, 00:25 UTC20m
2026-05-29 AHX101 AXJ → FUK May 29, 22:50 UTCMay 29, 23:05 UTC15m
2026-05-29 AHX108 FUK → AXJ May 29, 10:45 UTCMay 29, 11:00 UTC15m
2026-05-29 AHX107 AXJ → FUK May 29, 09:25 UTCMay 29, 09:45 UTC20m
2026-05-29 AHX106 FUK → AXJ May 29, 08:20 UTCMay 29, 08:35 UTC15m
2026-05-29 AHX105 AXJ → FUK May 29, 06:55 UTCMay 29, 07:15 UTC20m
2026-05-29 AHX802 ITM → KMJ May 29, 04:10 UTCMay 29, 05:05 UTC55m
2026-05-29 AHX801 KMJ → ITM May 29, 02:25 UTCMay 29, 03:05 UTC40m
2026-05-29 AHX201 AXJ → KMJ May 29, 01:00 UTCMay 29, 01:15 UTC15m
2026-05-29 AHX102 FUK → AXJ May 29, 00:10 UTCMay 29, 00:25 UTC15m
2026-05-28 AHX101 AXJ → FUK May 28, 22:45 UTCMay 28, 23:05 UTC20m
2026-05-28 AHX108 FUK → AXJ May 28, 10:15 UTCMay 28, 10:25 UTC10m
2026-05-28 AHX802 ITM → KMJ May 28, 04:05 UTCMay 28, 05:20 UTC1h 15m
2026-05-28 AHX801 KMJ → ITM May 28, 02:25 UTCMay 28, 03:10 UTC45m
2026-05-27 AHX108 FUK → AXJ May 27, 10:25 UTCMay 27, 10:35 UTC10m
2026-05-27 AHX106 FUK → AXJ May 27, 08:15 UTCMay 27, 08:30 UTC15m
2026-05-27 AHX802 ITM → KMJ May 27, 04:09 UTCMay 27, 05:24 UTC1h 15m
2026-05-27 AHX801 KMJ → ITM May 27, 02:24 UTCMay 27, 03:14 UTC50m
2026-05-27 AHX102 FUK → AXJ May 27, 00:04 UTCMay 27, 00:30 UTC25m
2026-05-26 AHX106 FUK → AXJ May 26, 07:59 UTCMay 26, 08:10 UTC10m
2026-05-26 AHX105 AXJ → FUK May 26, 06:59 UTCMay 26, 07:10 UTC10m
2026-05-26 AHX802 ITM → KMJ May 26, 04:00 UTCMay 26, 05:10 UTC1h 10m
2026-05-26 AHX801 KMJ → ITM May 26, 02:15 UTCMay 26, 03:05 UTC50m
2026-05-25 AHX108 FUK → AXJ May 25, 10:15 UTCMay 25, 10:30 UTC15m
2026-05-25 AHX106 FUK → AXJ May 25, 08:15 UTCMay 25, 08:25 UTC10m
2026-05-25 AHX105 AXJ → FUK May 25, 06:55 UTCMay 25, 07:15 UTC20m
2026-05-25 AHX202 KMJ → AXJ May 25, 05:55 UTCMay 25, 06:10 UTC15m
2026-05-25 AHX802 ITM → KMJ May 25, 04:00 UTCMay 25, 04:50 UTC50m
2026-05-25 AHX801 KMJ → ITM May 25, 02:15 UTCMay 25, 03:00 UTC45m

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

Mode-S 8404F3 frequently asked

What is Mode-S code 8404F3?
8404F3 is an ICAO 24-bit transponder address. Allocated to Japan. Assigned to JA01AM.
Where is Mode-S 8404F3 registered?
Mode-S code 8404F3 is allocated to Japan (JP). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8404F3 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 8404F3, octal 41002363, decimal 8,652,019.
What flights does 8404F3 operate?
Mode-S 8404F3 has broadcast 11 distinct callsigns, including AHX802, AHX801, AHX106, AHX102, AHX108.