sensors Mode-S transponder

A0FD55

ICAO 24-bit transponder address · allocated to United States

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

Hex
A0FD55
Octal
50176525
Decimal
10,550,613
Country
US
Tail
N163FE
Type
B763
Broadcasting now · callsign FDX1583 · 22,750 ft
Flights observed
91
Distinct callsigns
20
Country
US
Last broadcast
4h ago

Current position

A0FD55 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A0FD55 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
FDX1627 FedEx Express 3 2026-06-09
FDX1226 FedEx Express 3 2026-05-28
FDX9129 - 2 2026-05-01
FDX82 - 2 2026-06-16
FDX68 FedEx Express 2 2026-06-03
FDX653 FedEx Express 2 2026-06-07
FDX3700 FedEx Express 2 2026-06-09
FDX2200 FedEx Express 2 2026-06-12
FDX1835 FedEx Express 2 2026-05-19
FDX154 FedEx Express 2 2026-05-16
FDX1483 FedEx Express 2 2026-05-28
FDX1467 - 2 2026-06-17
FDX1455 FedEx Express 2 2026-05-27
FDX1443 FedEx Express 2 2026-06-09
FDX1432 FedEx Express 2 2026-05-13
FDX1417 FedEx Express 2 2026-06-04
FDX1386 FedEx Express 2 2026-05-16
FDX130 FedEx Express 2 2026-05-29
FDX1248 FedEx Express 2 2026-05-15
FDX1223 FedEx Express 2 2026-06-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-18 FDX2361 SDF → MEM Jun 18, 04:30 UTCJun 18, 05:20 UTC50m
2026-06-17 FDX1467 - Jun 17, 09:20 UTCJun 17, 10:05 UTC45m
2026-06-17 FDX1467 MEM → SDF Jun 17, 09:16 UTCJun 17, 10:14 UTC58m
2026-06-16 FDX82 - Jun 16, 09:34 UTCJun 17, 03:45 UTC18h 11m
2026-06-16 FDX1251 - Jun 16, 03:10 UTCJun 16, 04:20 UTC1h 10m
2026-06-13 FDX1475 MEM → OMA Jun 13, 09:50 UTCJun 13, 11:20 UTC1h 30m
2026-06-13 FDX141 YYC → MEM Jun 13, 02:30 UTCJun 13, 05:35 UTC3h 4m
2026-06-12 FDX140 MEM → YYC Jun 12, 09:30 UTCJun 12, 13:05 UTC3h 35m
2026-06-12 FDX2200 FLL → MEM Jun 12, 02:45 UTCJun 12, 04:45 UTC2h 0m
2026-06-12 FDX2200 FLL → MEM Jun 12, 02:43 UTCJun 12, 04:45 UTC2h 2m
2026-06-11 FDX398 MEM → ORD Jun 11, 22:25 UTCJun 12, 00:15 UTC1h 50m
2026-06-11 FDX1223 SEA → MEM Jun 11, 02:02 UTCJun 11, 05:20 UTC3h 18m
2026-06-11 FDX1223 SEA → MEM Jun 11, 02:05 UTCJun 11, 05:35 UTC3h 30m
2026-06-10 FDX1717 IND → SEA Jun 10, 08:25 UTCJun 10, 12:25 UTC4h 0m
2026-06-10 FDX1604 PHL → IND Jun 10, 02:20 UTCJun 10, 03:40 UTC1h 20m
2026-06-09 FDX3700 IND → PHL Jun 9, 21:45 UTCJun 9, 23:00 UTC1h 15m
2026-06-09 FDX3700 IND → PHL Jun 9, 21:40 UTCJun 9, 23:07 UTC1h 27m
2026-06-09 FDX3617 SEA → IND Jun 9, 13:35 UTCJun 9, 19:35 UTC6h 0m
2026-06-09 FDX1750 IND → LAX Jun 9, 08:00 UTCJun 9, 11:55 UTC3h 55m
2026-06-09 FDX1627 ORD → IND Jun 9, 04:30 UTCJun 9, 05:10 UTC40m
2026-06-09 FDX1627 ORD → IND Jun 9, 04:29 UTCJun 9, 05:06 UTC37m
2026-06-09 FDX1443 MEM → RIC Jun 9, 00:15 UTCJun 9, 01:45 UTC1h 30m
2026-06-07 FDX653 DTW → MEM Jun 7, 13:55 UTCJun 7, 15:30 UTC1h 35m
2026-06-07 FDX653 DTW → MEM Jun 7, 11:15 UTCJun 7, 12:35 UTC1h 20m
2026-06-05 FDX1418 MEM → DTW Jun 5, 08:35 UTCJun 5, 09:55 UTC1h 20m
2026-06-05 FDX1213 BUR → MEM Jun 5, 02:00 UTCJun 5, 05:15 UTC3h 15m
2026-06-04 FDX1417 MEM → BUR Jun 4, 08:30 UTCJun 4, 11:45 UTC3h 15m
2026-06-04 FDX1417 MEM → BUR Jun 4, 08:26 UTCJun 4, 11:43 UTC3h 17m
2026-06-03 FDX82 NRT → ANC Jun 3, 09:40 UTCJun 4, 04:20 UTC18h 40m
2026-06-03 FDX68 MTY → MEM Jun 3, 02:38 UTCJun 3, 04:31 UTC1h 53m
2026-06-03 FDX68 MTY → MEM Jun 3, 02:40 UTCJun 3, 04:30 UTC1h 50m
2026-06-02 FDX67 MEM → MTY Jun 2, 10:25 UTCJun 2, 12:20 UTC1h 55m
2026-06-02 FDX1290 RNO → MEM Jun 2, 02:15 UTCJun 2, 05:35 UTC3h 20m
2026-05-30 FDX1490 MEM → RNO May 30, 09:20 UTCMay 30, 12:15 UTC2h 55m
2026-05-30 FDX131 YMX → MEM May 30, 01:35 UTCMay 30, 04:00 UTC2h 25m
2026-05-29 FDX130 MEM → YMX May 29, 08:55 UTCMay 29, 11:15 UTC2h 20m
2026-05-29 FDX130 MEM → YMX May 29, 08:54 UTCMay 29, 11:11 UTC2h 17m
2026-05-29 FDX1292 JFK → MEM May 29, 03:20 UTCMay 29, 05:20 UTC2h 0m
2026-05-28 FDX1483 MEM → JFK May 28, 08:45 UTCMay 28, 10:40 UTC1h 55m
2026-05-28 FDX1483 MEM → JFK May 28, 08:42 UTCMay 28, 10:35 UTC1h 53m
2026-05-28 FDX1226 JAX → MEM May 28, 02:00 UTCMay 28, 03:15 UTC1h 15m
2026-05-27 FDX1455 MEM → JAX May 27, 09:20 UTCMay 27, 10:35 UTC1h 15m
2026-05-27 FDX1213 BUR → MEM May 27, 02:04 UTCMay 27, 05:14 UTC3h 10m
2026-05-26 FDX1808 LAX → BUR May 26, 22:59 UTCMay 26, 23:14 UTC15m
2026-05-24 FDX781 MEM → PDX May 24, 23:00 UTCMay 24, 23:46 UTC46m
2026-05-23 FDX1224 RIC → MEM May 23, 01:50 UTCMay 23, 03:25 UTC1h 35m
2026-05-22 FDX1542 MEM → RIC May 22, 09:05 UTCMay 22, 10:30 UTC1h 25m
2026-05-22 FDX1205 ORD → MEM May 22, 02:40 UTCMay 22, 03:50 UTC1h 10m
2026-05-21 FDX1447 MEM → ORD May 21, 08:00 UTCMay 21, 09:05 UTC1h 5m
2026-05-21 FDX1226 JAX → MEM May 21, 01:40 UTCMay 21, 02:50 UTC1h 10m

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

Mode-S A0FD55 frequently asked

What is Mode-S code A0FD55?
A0FD55 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N163FE.
Where is Mode-S A0FD55 registered?
Mode-S code A0FD55 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 A0FD55 broadcasting right now?
Yes. Mode-S A0FD55 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A0FD55, octal 50176525, decimal 10,550,613.
What flights does A0FD55 operate?
Mode-S A0FD55 has broadcast 20 distinct callsigns, including FDX1627, FDX1226, FDX9129, FDX82, FDX68.