Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A1624E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N189CA · EMBRAER EMB-120 Brasilia · operated by UAS TRANSERVICES INC

Hex
A1624E
Octal
50261116
Decimal
10,576,462
Country
US
Tail
N189CA
Type
E120
No current signal · last broadcast 1h ago
Flights observed
128
Distinct callsigns
10
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A1624E.

Country allocation

The ICAO 24-bit address A1624E 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 10 distinct

Callsign Airline Flights Last seen
AMF1932 - 58 2026-07-17
AMF1931 - 57 2026-07-18
AMF1978 - 3 2026-07-20
AMF1977 - 3 2026-07-21
AMF8046 - 2 2026-06-04
AMF8017 - 1 2026-06-30
AMF2694 - 1 2026-07-20
AMF2129 - 1 2026-06-01
AMF2121 - 1 2026-04-20
AMF2104 - 1 2026-06-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-21 AMF1977 MFR → PDX Jul 21, 00:10 UTCJul 21, 00:55 UTC45m
2026-07-20 AMF2694 MFR → MFR Jul 20, 21:40 UTCJul 20, 21:45 UTC5m
2026-07-20 AMF1978 - Jul 20, 20:10 UTCJul 20, 21:00 UTC50m
2026-07-18 AMF1931 MFR → PDX Jul 18, 00:00 UTCJul 18, 00:50 UTC50m
2026-07-17 AMF1932 PDX → MFR Jul 17, 12:50 UTCJul 17, 13:45 UTC55m
2026-07-17 AMF1931 MFR → PDX Jul 17, 00:10 UTCJul 17, 00:55 UTC45m
2026-07-16 AMF1932 - Jul 16, 14:20 UTCJul 16, 15:00 UTC40m
2026-07-16 AMF1931 MFR → PDX Jul 16, 00:05 UTCJul 16, 00:50 UTC45m
2026-07-15 AMF1932 PDX → MFR Jul 15, 12:50 UTCJul 15, 13:50 UTC1h 0m
2026-07-15 AMF1931 MFR → PDX Jul 15, 00:05 UTCJul 15, 00:50 UTC45m
2026-07-14 AMF1932 PDX → MFR Jul 14, 12:40 UTCJul 14, 13:35 UTC55m
2026-07-14 AMF1931 MFR → PDX Jul 14, 00:05 UTCJul 14, 00:50 UTC45m
2026-07-13 AMF1932 - Jul 13, 21:25 UTCJul 13, 22:20 UTC55m
2026-07-11 AMF1931 MFR → PDX Jul 11, 00:00 UTCJul 11, 00:50 UTC50m
2026-07-10 AMF1932 PDX → MFR Jul 10, 12:50 UTCJul 10, 13:40 UTC50m
2026-07-09 AMF1931 MFR → PDX Jul 9, 23:55 UTCJul 10, 00:45 UTC50m
2026-07-09 AMF1932 PDX → MFR Jul 9, 12:50 UTCJul 9, 13:40 UTC50m
2026-07-09 AMF1931 MFR → PDX Jul 9, 00:00 UTCJul 9, 00:50 UTC50m
2026-07-08 AMF1932 PDX → MFR Jul 8, 12:45 UTCJul 8, 13:35 UTC50m
2026-07-08 AMF1931 MFR → PDX Jul 8, 00:00 UTCJul 8, 00:45 UTC45m
2026-07-07 AMF1932 PDX → MFR Jul 7, 12:45 UTCJul 7, 13:35 UTC50m
2026-07-06 AMF1931 MFR → PDX Jul 6, 23:55 UTCJul 7, 00:40 UTC45m
2026-07-06 AMF1932 PDX → MFR Jul 6, 21:45 UTCJul 6, 22:35 UTC50m
2026-07-03 AMF1931 MFR → PDX Jul 3, 23:45 UTCJul 4, 00:35 UTC50m
2026-07-03 AMF1932 PDX → MFR Jul 3, 12:45 UTCJul 3, 13:40 UTC55m
2026-07-03 AMF1931 MFR → PDX Jul 3, 00:00 UTCJul 3, 00:45 UTC45m
2026-07-02 AMF1932 PDX → MFR Jul 2, 12:55 UTCJul 2, 13:45 UTC50m
2026-07-02 AMF1931 MFR → PDX Jul 2, 00:00 UTCJul 2, 00:55 UTC55m
2026-07-01 AMF1932 PDX → MFR Jul 1, 13:10 UTCJul 1, 14:00 UTC50m
2026-07-01 AMF1931 MFR → PDX Jul 1, 00:00 UTCJul 1, 00:50 UTC50m
2026-06-30 AMF8017 MFR → MFR Jun 30, 21:50 UTCJun 30, 22:30 UTC40m
2026-06-30 AMF1932 - Jun 30, 12:45 UTCJun 30, 13:40 UTC55m
2026-06-30 AMF1931 MFR → PDX Jun 30, 00:00 UTCJun 30, 00:55 UTC55m
2026-06-29 AMF2104 - Jun 29, 21:50 UTCJun 29, 22:00 UTC10m
2026-06-29 AMF1932 - Jun 29, 19:49 UTCJun 29, 20:35 UTC45m
2026-06-26 AMF1931 MFR → PDX Jun 26, 23:55 UTCJun 27, 00:44 UTC50m
2026-06-26 AMF1932 PDX → MFR Jun 26, 13:49 UTCJun 26, 14:39 UTC50m
2026-06-25 AMF1931 MFR → PDX Jun 25, 23:55 UTCJun 26, 00:45 UTC50m
2026-06-25 AMF1932 PDX → MFR Jun 25, 12:54 UTCJun 25, 13:45 UTC50m
2026-06-24 AMF1931 MFR → PDX Jun 24, 23:59 UTCJun 25, 00:49 UTC50m
2026-06-24 AMF1932 PDX → MFR Jun 24, 12:50 UTCJun 24, 13:40 UTC50m
2026-06-24 AMF1931 MFR → PDX Jun 24, 00:05 UTCJun 24, 00:49 UTC45m
2026-06-23 AMF1932 PDX → MFR Jun 23, 12:45 UTCJun 23, 13:34 UTC50m
2026-06-22 AMF1931 MFR → PDX Jun 22, 23:55 UTCJun 23, 00:45 UTC50m
2026-06-22 AMF1932 - Jun 22, 21:30 UTCJun 22, 22:24 UTC55m
2026-06-19 AMF1931 MFR → PDX Jun 19, 23:54 UTCJun 20, 00:44 UTC50m
2026-06-19 AMF1932 - Jun 19, 12:49 UTCJun 19, 13:39 UTC50m
2026-06-19 AMF1931 - Jun 19, 00:00 UTCJun 19, 00:49 UTC49m
2026-06-18 AMF1932 - Jun 18, 12:45 UTCJun 18, 13:35 UTC50m
2026-06-17 AMF1931 - Jun 17, 23:55 UTCJun 18, 00:45 UTC50m

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

Mode-S A1624E frequently asked

What is Mode-S code A1624E?
A1624E is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N189CA.
Where is Mode-S A1624E registered?
Mode-S code A1624E 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 A1624E broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A1624E, octal 50261116, decimal 10,576,462.
What flights does A1624E operate?
Mode-S A1624E has broadcast 10 distinct callsigns, including AMF1932, AMF1931, AMF1978, AMF1977, AMF8046.