Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AD5622

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N959AM · BOEING 737 MAX 9 · operated by BOEING CO

Hex
AD5622
Octal
53253042
Decimal
11,359,778
Country
US
Tail
N959AM
Type
B39M
No current signal · last broadcast 7h ago
Flights observed
362
Distinct callsigns
20
Country
US
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S AD5622.

Country allocation

The ICAO 24-bit address AD5622 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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
AMX659 Aeroméxico 8 2026-04-18
AMX112 Aeroméxico 8 2026-05-15
AMX905 - 7 2026-06-24
AMX121 Aeroméxico 7 2026-05-15
AMX956 - 6 2026-07-08
AMX953 - 6 2026-07-10
AMX940 - 6 2026-07-09
AMX784 - 6 2026-06-19
AMX658 Aeroméxico 6 2026-04-17
AMX633 - 6 2026-07-09
AMX711 - 5 2026-06-15
AMX704 Aeroméxico 5 2026-06-15
AMX501 Aeroméxico 5 2026-05-01
AMX380 - 5 2026-06-29
AMX201 - 5 2026-06-21
AMX1645 Aeroméxico 5 2026-06-14
AMX957 Aeroméxico 4 2026-06-11
AMX943 Aeroméxico 4 2026-05-19
AMX919 - 4 2026-07-03
AMX785 Aeroméxico 4 2026-06-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 AMX435 - Jul 14, 01:10 UTCJul 14, 03:50 UTC2h 40m
2026-07-13 AMX436 - Jul 13, 20:00 UTCJul 13, 22:50 UTC2h 50m
2026-07-13 AMX116 - Jul 13, 18:05 UTCJul 13, 18:20 UTC15m
2026-07-13 AMX113 - Jul 13, 12:45 UTCJul 13, 17:20 UTC4h 35m
2026-07-13 AMX259 - Jul 13, 03:40 UTCJul 13, 03:55 UTC15m
2026-07-13 AMX248 - Jul 13, 00:40 UTCJul 13, 00:55 UTC15m
2026-07-12 AMX115 - Jul 12, 16:55 UTCJul 12, 21:40 UTC4h 45m
2026-07-12 AMX209 - Jul 12, 14:45 UTCJul 12, 15:05 UTC20m
2026-07-10 AMX264 - Jul 10, 05:10 UTCJul 10, 05:25 UTC15m
2026-07-10 AMX953 MTY → MEX Jul 10, 01:40 UTCJul 10, 02:50 UTC1h 10m
2026-07-09 AMX940 - Jul 9, 23:10 UTCJul 10, 00:20 UTC1h 10m
2026-07-09 AMX633 - Jul 9, 19:10 UTCJul 9, 20:50 UTC1h 40m
2026-07-09 AMX632 - Jul 9, 15:25 UTCJul 9, 17:05 UTC1h 40m
2026-07-09 AMX953 MTY → MEX Jul 9, 01:45 UTCJul 9, 02:55 UTC1h 10m
2026-07-08 AMX940 MEX → MTY Jul 8, 22:40 UTCJul 8, 23:50 UTC1h 10m
2026-07-08 AMX531 CUN → MEX Jul 8, 18:55 UTCJul 8, 20:50 UTC1h 55m
2026-07-08 AMX512 MEX → CUN Jul 8, 15:35 UTCJul 8, 17:30 UTC1h 55m
2026-07-08 AMX901 MTY → MEX Jul 8, 12:05 UTCJul 8, 13:10 UTC1h 5m
2026-07-08 AMX956 - Jul 8, 02:45 UTCJul 8, 04:00 UTC1h 15m
2026-07-07 AMX1689 - Jul 7, 21:25 UTCJul 7, 23:35 UTC2h 10m
2026-07-07 AMX1682 - Jul 7, 16:40 UTCJul 7, 18:50 UTC2h 10m
2026-07-07 AMX477 - Jul 7, 12:10 UTCJul 7, 14:00 UTC1h 50m
2026-07-07 AMX476 - Jul 7, 00:35 UTCJul 7, 02:20 UTC1h 45m
2026-07-06 AMX118 - Jul 6, 22:20 UTCJul 6, 22:30 UTC10m
2026-07-06 AMX115 - Jul 6, 17:00 UTCJul 6, 21:35 UTC4h 35m
2026-07-06 AMX909 MTY → MEX Jul 6, 14:00 UTCJul 6, 15:05 UTC1h 5m
2026-07-05 AMX948 - Jul 5, 00:35 UTCJul 5, 01:45 UTC1h 10m
2026-07-04 AMX935 MTY → MEX Jul 4, 21:00 UTCJul 4, 22:05 UTC1h 5m
2026-07-04 AMX956 - Jul 4, 02:40 UTCJul 4, 03:40 UTC1h 0m
2026-07-03 AMX547 - Jul 3, 22:40 UTCJul 4, 00:35 UTC1h 55m
2026-07-03 AMX528 - Jul 3, 19:35 UTCJul 3, 21:20 UTC1h 45m
2026-07-03 AMX919 - Jul 3, 17:40 UTCJul 3, 17:50 UTC10m
2026-07-03 AMX919 - Jul 3, 16:40 UTCJul 3, 17:05 UTC25m
2026-07-03 AMX908 - Jul 3, 14:05 UTCJul 3, 15:25 UTC1h 20m
2026-07-03 AMX713 HMO → MEX Jul 3, 00:05 UTCJul 3, 02:20 UTC2h 15m
2026-07-02 AMX706 - Jul 2, 22:30 UTCJul 2, 22:45 UTC15m
2026-07-02 AMX706 - Jul 2, 20:35 UTCJul 2, 20:45 UTC10m
2026-07-02 AMX363 - Jul 2, 18:15 UTCJul 2, 18:30 UTC15m
2026-07-02 AMX362 - Jul 2, 13:45 UTCJul 2, 14:00 UTC15m
2026-07-02 AMX147 - Jul 2, 04:15 UTCJul 2, 04:25 UTC10m
2026-07-01 AMX146 - Jul 1, 23:25 UTCJul 2, 03:30 UTC4h 5m
2026-07-01 AMX441 - Jul 1, 18:15 UTCJul 1, 21:10 UTC2h 55m
2026-07-01 AMX440 MEX → MCO Jul 1, 13:25 UTCJul 1, 16:10 UTC2h 45m
2026-07-01 AMX669 - Jul 1, 04:00 UTCJul 1, 04:10 UTC10m
2026-07-01 AMX669 - Jul 1, 00:30 UTCJul 1, 02:20 UTC1h 50m
2026-06-30 AMX668 MEX → SFO Jun 30, 18:05 UTCJun 30, 22:15 UTC4h 10m
2026-06-30 AMX821 - Jun 30, 03:05 UTCJun 30, 13:50 UTC10h 45m
2026-06-29 AMX245 - Jun 29, 20:00 UTCJun 30, 00:55 UTC4h 55m
2026-06-29 AMX381 - Jun 29, 18:10 UTCJun 29, 18:19 UTC10m
2026-06-29 AMX380 - Jun 29, 13:54 UTCJun 29, 14:09 UTC15m

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

Mode-S AD5622 frequently asked

What is Mode-S code AD5622?
AD5622 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N959AM.
Where is Mode-S AD5622 registered?
Mode-S code AD5622 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is AD5622 broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD5622, octal 53253042, decimal 11,359,778.
What flights does AD5622 operate?
Mode-S AD5622 has broadcast 20 distinct callsigns, including AMX659, AMX112, AMX905, AMX121, AMX956.