sensors Mode-S transponder

A01B80

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N106FE · BOEING 767-300 · operated by FEDERAL EXPRESS CORP

Hex
A01B80
Octal
50015600
Decimal
10,492,800
Country
US
Tail
N106FE
Type
B763
Broadcasting now · callsign FDX1385 · 15,775 ft
Flights observed
141
Distinct callsigns
20
Country
US
Last broadcast
16h ago

Current position

A01B80 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A01B80 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
FDX5501 FedEx Express 33 2026-05-26
FDX205 FedEx Express 22 2026-05-26
FDX204 FedEx Express 22 2026-05-27
FDX5502 FedEx Express 21 2026-05-26
FDX114 FedEx Express 6 2026-05-15
FDX5504 FedEx Express 5 2026-05-14
FDX115 FedEx Express 4 2026-05-15
FDX619 FedEx Express 2 2026-05-07
FDX5503 FedEx Express 2 2026-05-14
FDX55 FedEx Express 2 2026-05-07
FDX442 FedEx Express 2 2026-04-17
FDX431 FedEx Express 2 2026-05-22
FDX219 FedEx Express 2 2026-05-03
FDX208 FedEx Express 2 2026-05-28
FDX1461 FedEx Express 2 2026-05-23
FDX1431 FedEx Express 2 2026-04-17
FDX56 FedEx Express 1 2026-05-07
FDX416 FedEx Express 1 2026-05-28
FDX232 FedEx Express 1 2026-05-05
FDX218 FedEx Express 1 2026-05-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 FDX1418 MEM → DTW May 29, 08:35 UTCMay 29, 09:55 UTC1h 20m
2026-05-29 FDX147 YYZ → MEM May 29, 02:10 UTCMay 29, 04:00 UTC1h 50m
2026-05-28 FDX208 MEM → YYZ May 28, 21:10 UTCMay 28, 23:00 UTC1h 50m
2026-05-28 FDX208 MEM → YYZ May 28, 21:05 UTCMay 28, 22:55 UTC1h 50m
2026-05-28 FDX416 BOS → MEM May 28, 12:45 UTCMay 28, 15:20 UTC2h 35m
2026-05-28 FDX1406 MEM → BOS May 28, 08:15 UTCMay 28, 10:30 UTC2h 15m
2026-05-28 FDX1261 MIA → MEM May 28, 00:50 UTCMay 28, 02:40 UTC1h 50m
2026-05-27 FDX204 MDE → MIA May 27, 15:00 UTCMay 27, 15:30 UTC30m
2026-05-26 FDX205 MIA → BOG May 26, 17:59 UTCMay 26, 18:19 UTC20m
2026-05-26 FDX5502 UIO → MIA May 26, 08:15 UTCMay 26, 15:20 UTC7h 5m
2026-05-26 FDX5501 MIA → EZE May 26, 01:55 UTCMay 26, 02:19 UTC25m
2026-05-25 FDX5501 MIA → EZE May 25, 14:45 UTCMay 25, 23:04 UTC8h 20m
2026-05-24 FDX204 MDE → MIA May 24, 14:55 UTCMay 24, 15:35 UTC40m
2026-05-23 FDX205 MIA → BOG May 23, 23:45 UTCMay 24, 00:05 UTC20m
2026-05-23 FDX205 MIA → BOG May 23, 21:05 UTCMay 23, 21:25 UTC20m
2026-05-23 FDX1461 MEM → MIA May 23, 08:40 UTCMay 23, 10:25 UTC1h 45m
2026-05-23 FDX1461 MEM → MIA May 23, 08:36 UTCMay 23, 10:24 UTC1h 48m
2026-05-22 FDX431 LAX → MEM May 22, 12:50 UTCMay 22, 14:40 UTC1h 50m
2026-05-22 FDX431 LAX → MEM May 22, 12:47 UTCMay 22, 14:41 UTC1h 54m
2026-05-21 FDX5502 UIO → MIA May 21, 11:00 UTCMay 21, 18:00 UTC7h 0m
2026-05-21 FDX5501 MIA → EZE May 21, 04:20 UTCMay 21, 04:50 UTC30m
2026-05-20 FDX5501 MIA → EZE May 20, 17:55 UTCMay 21, 02:05 UTC8h 10m
2026-05-20 FDX204 MDE → MIA May 20, 15:25 UTCMay 20, 16:00 UTC35m
2026-05-20 FDX204 MDE → MIA May 20, 10:55 UTCMay 20, 11:05 UTC10m
2026-05-19 FDX205 MIA → BOG May 19, 20:50 UTCMay 19, 21:05 UTC15m
2026-05-19 FDX205 MIA → BOG May 19, 18:10 UTCMay 19, 18:25 UTC15m
2026-05-19 FDX5502 UIO → MIA May 19, 09:05 UTCMay 19, 16:00 UTC6h 55m
2026-05-19 FDX5501 MIA → EZE May 19, 01:50 UTCMay 19, 03:40 UTC1h 50m
2026-05-18 FDX5501 MIA → EZE May 18, 14:55 UTCMay 18, 23:10 UTC8h 14m
2026-05-16 FDX5502 UIO → MIA May 16, 21:02 UTCMay 17, 00:51 UTC3h 49m
2026-05-16 FDX5502 UIO → MIA May 16, 17:25 UTCMay 17, 00:55 UTC7h 30m
2026-05-16 FDX5501 MIA → EZE May 16, 02:15 UTCMay 16, 02:45 UTC30m
2026-05-15 FDX5501 MIA → EZE May 15, 15:20 UTCMay 15, 23:45 UTC8h 25m
2026-05-15 FDX114 MEM → MIA May 15, 09:45 UTCMay 15, 11:35 UTC1h 50m
2026-05-15 FDX115 MIA → MEM May 15, 03:10 UTCMay 15, 05:00 UTC1h 50m
2026-05-14 FDX5504 SAP → MIA May 14, 23:45 UTCMay 15, 01:15 UTC1h 30m
2026-05-14 FDX5504 SAP → MIA May 14, 23:23 UTCMay 15, 01:15 UTC1h 52m
2026-05-14 FDX5504 SAP → MIA May 14, 21:00 UTCMay 14, 21:20 UTC20m
2026-05-14 FDX5503 MIA → GUA May 14, 14:15 UTCMay 14, 16:30 UTC2h 15m
2026-05-14 FDX114 MEM → MIA May 14, 09:50 UTCMay 14, 11:35 UTC1h 45m
2026-05-14 FDX114 MEM → MIA May 14, 09:48 UTCMay 14, 11:35 UTC1h 47m
2026-05-14 FDX115 MIA → MEM May 14, 03:05 UTCMay 14, 04:55 UTC1h 50m
2026-05-14 FDX115 MIA → MEM May 14, 03:04 UTCMay 14, 05:01 UTC1h 57m
2026-05-13 FDX5504 SAP → MIA May 13, 23:35 UTCMay 14, 01:05 UTC1h 30m
2026-05-13 FDX5504 SAP → MIA May 13, 20:55 UTCMay 13, 21:20 UTC25m
2026-05-13 FDX5503 MIA → GUA May 13, 13:55 UTCMay 13, 16:10 UTC2h 15m
2026-05-13 FDX204 MDE → MIA May 13, 10:35 UTCMay 13, 11:10 UTC35m
2026-05-12 FDX205 MIA → BOG May 12, 17:50 UTCMay 12, 18:00 UTC10m
2026-05-12 FDX205 MIA → BOG May 12, 17:46 UTCMay 12, 20:46 UTC3h 0m
2026-05-12 FDX5502 UIO → MIA May 12, 12:06 UTCMay 12, 15:31 UTC3h 25m

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

Mode-S A01B80 frequently asked

What is Mode-S code A01B80?
A01B80 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N106FE.
Where is Mode-S A01B80 registered?
Mode-S code A01B80 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 A01B80 broadcasting right now?
Yes. Mode-S A01B80 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A01B80, octal 50015600, decimal 10,492,800.
What flights does A01B80 operate?
Mode-S A01B80 has broadcast 20 distinct callsigns, including FDX5501, FDX205, FDX204, FDX5502, FDX114.