sensors Mode-S transponder

A02CB5

ICAO 24-bit transponder address · allocated to United States

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

Hex
A02CB5
Octal
50026265
Decimal
10,497,205
Country
US
Tail
N110FE
Type
B763
No current signal · last broadcast 10h ago
Flights observed
189
Distinct callsigns
20
Country
US
Last broadcast
10h ago

Last known position

Most recent position reported by Mode-S A02CB5.

Country allocation

The ICAO 24-bit address A02CB5 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
FDX5046 - 15 2026-07-10
FDX5501 FedEx Express 14 2026-06-11
FDX5201 - 14 2026-07-13
FDX205 FedEx Express 11 2026-06-13
FDX204 - 11 2026-06-14
FDX5202 - 10 2026-07-08
FDX5047 - 9 2026-07-09
FDX55 - 8 2026-06-16
FDX6238 - 6 2026-07-14
FDX5502 FedEx Express 6 2026-06-11
FDX114 FedEx Express 6 2026-06-03
FDX5034 - 5 2026-07-02
FDX36 - 5 2026-07-02
FDX5504 FedEx Express 4 2026-06-16
FDX5220 - 4 2026-07-12
FDX6927 FedEx Express 3 2026-06-30
FDX56 - 3 2026-06-17
FDX5503 FedEx Express 3 2026-06-15
FDX5048 FedEx Express 3 2026-05-19
FDX115 FedEx Express 3 2026-06-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDX6238 - Jul 14, 01:45 UTCJul 14, 04:25 UTC2h 40m
2026-07-13 FDX5201 - Jul 13, 21:40 UTCJul 13, 22:25 UTC45m
2026-07-13 FDX5201 DUB → STN Jul 13, 17:50 UTCJul 13, 18:45 UTC55m
2026-07-12 FDX5220 - Jul 12, 00:40 UTCJul 12, 01:30 UTC50m
2026-07-11 FDX5220 - Jul 11, 22:30 UTCJul 11, 23:15 UTC45m
2026-07-11 FDX5812 - Jul 11, 17:40 UTCJul 11, 18:25 UTC45m
2026-07-11 FDX5811 - Jul 11, 13:05 UTCJul 11, 13:50 UTC45m
2026-07-10 FDX5046 - Jul 10, 07:55 UTCJul 10, 14:40 UTC6h 45m
2026-07-09 FDX5046 - Jul 9, 23:20 UTCJul 10, 01:40 UTC2h 20m
2026-07-09 FDX5047 - Jul 9, 14:55 UTCJul 9, 17:10 UTC2h 15m
2026-07-09 FDX5047 - Jul 9, 02:00 UTCJul 9, 09:30 UTC7h 30m
2026-07-08 FDX5201 - Jul 8, 21:45 UTCJul 8, 22:20 UTC35m
2026-07-08 FDX5201 DUB → STN Jul 8, 17:40 UTCJul 8, 18:30 UTC50m
2026-07-08 FDX5201 - Jul 8, 14:10 UTCJul 8, 15:25 UTC1h 15m
2026-07-08 FDX5202 - Jul 8, 08:40 UTCJul 8, 10:00 UTC1h 20m
2026-07-08 FDX5202 - Jul 8, 04:00 UTCJul 8, 04:45 UTC45m
2026-07-08 FDX5202 - Jul 8, 02:15 UTCJul 8, 02:55 UTC40m
2026-07-07 FDX5201 - Jul 7, 21:55 UTCJul 7, 22:40 UTC45m
2026-07-07 FDX5201 DUB → STN Jul 7, 17:45 UTCJul 7, 18:35 UTC50m
2026-07-07 FDX5201 - Jul 7, 14:15 UTCJul 7, 15:35 UTC1h 20m
2026-07-07 FDX5202 - Jul 7, 09:15 UTCJul 7, 10:30 UTC1h 15m
2026-07-07 FDX5202 - Jul 7, 04:55 UTCJul 7, 05:40 UTC45m
2026-07-07 FDX5202 CDG → STN Jul 7, 03:00 UTCJul 7, 03:40 UTC40m
2026-07-06 FDX6917 - Jul 6, 19:40 UTCJul 6, 22:40 UTC3h 0m
2026-07-04 FDX6226 - Jul 4, 23:45 UTCJul 5, 02:35 UTC2h 50m
2026-07-03 FDX6335 AMS → CDG Jul 3, 19:40 UTCJul 3, 22:40 UTC3h 0m
2026-07-03 FDX6238 - Jul 3, 02:00 UTCJul 3, 04:45 UTC2h 45m
2026-07-02 FDX36 - Jul 2, 20:35 UTCJul 2, 21:25 UTC50m
2026-07-02 FDX5034 - Jul 2, 17:50 UTCJul 2, 18:35 UTC45m
2026-07-02 FDX5046 - Jul 2, 08:35 UTCJul 2, 15:15 UTC6h 40m
2026-07-01 FDX5046 - Jul 1, 22:30 UTCJul 2, 00:40 UTC2h 10m
2026-07-01 FDX5046 MEM → EWR Jul 1, 22:28 UTCJul 2, 00:34 UTC2h 6m
2026-07-01 FDX5047 - Jul 1, 14:40 UTCJul 1, 16:35 UTC1h 55m
2026-07-01 FDX5047 CDG → EWR Jul 1, 02:00 UTCJul 1, 09:45 UTC7h 45m
2026-06-30 FDX6927 CDG → CDG Jun 30, 19:45 UTCJun 30, 22:45 UTC3h 0m
2026-06-30 FDX6238 - Jun 30, 01:45 UTCJun 30, 04:40 UTC2h 55m
2026-06-29 FDX6917 - Jun 29, 19:39 UTCJun 29, 22:30 UTC2h 50m
2026-06-28 FDX6226 - Jun 28, 00:00 UTCJun 28, 03:00 UTC3h 0m
2026-06-27 FDX5201 - Jun 27, 17:04 UTCJun 27, 18:04 UTC1h 0m
2026-06-27 FDX5201 - Jun 27, 14:14 UTCJun 27, 15:05 UTC50m
2026-06-26 FDX5202 - Jun 26, 04:00 UTCJun 26, 04:45 UTC45m
2026-06-26 FDX5202 - Jun 26, 02:05 UTCJun 26, 02:40 UTC35m
2026-06-25 FDX5187 HAJ → CDG Jun 25, 21:25 UTCJun 25, 22:29 UTC1h 5m
2026-06-25 FDX5187 - Jun 25, 19:24 UTCJun 25, 19:59 UTC35m
2026-06-25 FDX5084 - Jun 25, 03:40 UTCJun 25, 04:35 UTC55m
2026-06-25 FDX5084 - Jun 25, 01:44 UTCJun 25, 02:25 UTC40m
2026-06-24 FDX36 FRA → CDG Jun 24, 20:35 UTCJun 24, 21:24 UTC50m
2026-06-24 FDX5034 - Jun 24, 17:59 UTCJun 24, 18:44 UTC45m
2026-06-24 FDX5046 EWR → CDG Jun 24, 07:54 UTCJun 24, 14:34 UTC6h 40m
2026-06-23 FDX5046 - Jun 23, 23:19 UTCJun 24, 01:14 UTC1h 55m

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

Mode-S A02CB5 frequently asked

What is Mode-S code A02CB5?
A02CB5 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N110FE.
Where is Mode-S A02CB5 registered?
Mode-S code A02CB5 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 A02CB5 broadcasting right now?
No active broadcast right now. Last signal was 10h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A02CB5, octal 50026265, decimal 10,497,205.
What flights does A02CB5 operate?
Mode-S A02CB5 has broadcast 20 distinct callsigns, including FDX5046, FDX5501, FDX5201, FDX205, FDX204.