sensors Mode-S transponder

AC5FD6

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N897FD · BOEING 777-200LR · operated by FEDERAL EXPRESS CORP

Hex
AC5FD6
Octal
53057726
Decimal
11,296,726
Country
US
Tail
N897FD
Type
B77L
No current signal · last broadcast 3h ago
Flights observed
195
Distinct callsigns
20
Country
US
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S AC5FD6.

Country allocation

The ICAO 24-bit address AC5FD6 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
FDX97 - 10 2026-06-18
FDX5174 - 9 2026-07-04
FDX5928 FedEx Express 8 2026-04-30
FDX7 FedEx Express 7 2026-07-01
FDX5217 - 7 2026-06-30
FDX5040 FedEx Express 7 2026-04-28
FDX48 - 7 2026-07-09
FDX92 - 6 2026-06-18
FDX6013 FedEx Express 6 2026-04-29
FDX5030 FedEx Express 6 2026-05-16
FDX2 - 6 2026-07-14
FDX1 - 6 2026-07-08
FDX5155 FedEx Express 5 2026-04-13
FDX10 - 5 2026-07-02
FDX8 - 4 2026-06-30
FDX6174 - 4 2026-07-06
FDX5460 FedEx Express 4 2026-05-10
FDX5384 FedEx Express 4 2026-05-15
FDX5225 - 4 2026-07-07
FDX5024 - 4 2026-06-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDX2 - Jul 14, 09:50 UTCJul 14, 17:55 UTC8h 5m
2026-07-12 FDX5159 - Jul 12, 09:15 UTCJul 12, 15:01 UTC5h 45m
2026-07-11 FDX5159 - Jul 11, 21:55 UTCJul 12, 07:45 UTC9h 50m
2026-07-11 FDX6031 - Jul 11, 07:30 UTCJul 11, 15:15 UTC7h 45m
2026-07-10 FDX9162 - Jul 10, 20:55 UTCJul 11, 03:10 UTC6h 15m
2026-07-10 FDX5025 - Jul 10, 06:45 UTCJul 10, 15:55 UTC9h 10m
2026-07-10 FDX5025 LGG → MEM Jul 10, 06:44 UTCJul 10, 15:55 UTC9h 11m
2026-07-09 FDX48 - Jul 9, 20:25 UTCJul 10, 04:30 UTC8h 5m
2026-07-08 FDX1 - Jul 8, 20:15 UTCJul 9, 04:55 UTC8h 40m
2026-07-08 FDX2 - Jul 8, 09:30 UTCJul 8, 17:40 UTC8h 10m
2026-07-07 FDX5225 - Jul 7, 20:10 UTCJul 8, 05:30 UTC9h 20m
2026-07-07 FDX4 - Jul 7, 09:30 UTCJul 7, 18:05 UTC8h 35m
2026-07-06 FDX6174 - Jul 6, 19:00 UTCJul 7, 04:05 UTC9h 5m
2026-07-06 FDX38 - Jul 6, 01:45 UTCJul 6, 04:55 UTC3h 10m
2026-07-06 FDX38 MEM → CDG Jul 6, 01:40 UTCJul 6, 09:38 UTC7h 58m
2026-07-04 FDX5174 - Jul 4, 20:30 UTCJul 5, 05:35 UTC9h 5m
2026-07-04 FDX5174 - Jul 4, 11:00 UTCJul 4, 14:05 UTC3h 5m
2026-07-03 FDX5174 - Jul 3, 16:45 UTCJul 4, 08:40 UTC15h 55m
2026-07-03 FDX5174 - Jul 3, 09:50 UTCJul 4, 08:40 UTC22h 50m
2026-07-03 FDX5175 - Jul 3, 07:35 UTCJul 4, 07:30 UTC23h 55m
2026-07-03 FDX5175 - Jul 3, 06:40 UTCJul 3, 23:30 UTC16h 50m
2026-07-02 FDX10 - Jul 2, 10:20 UTCJul 2, 18:20 UTC8h 0m
2026-07-01 FDX7 MXP → MEM Jul 1, 19:45 UTCJul 2, 05:35 UTC9h 50m
2026-07-01 FDX7 MXP → MEM Jul 1, 08:35 UTCJul 1, 16:55 UTC8h 20m
2026-06-30 FDX8 - Jun 30, 19:45 UTCJul 1, 05:05 UTC9h 20m
2026-06-30 FDX5217 - Jun 30, 11:15 UTCJun 30, 14:05 UTC2h 50m
2026-06-30 FDX5217 - Jun 30, 07:10 UTCJun 30, 09:30 UTC2h 20m
2026-06-29 FDX5217 - Jun 29, 22:49 UTCJun 29, 23:05 UTC15m
2026-06-29 FDX5217 - Jun 29, 19:20 UTCJun 29, 19:35 UTC15m
2026-06-29 FDX5217 - Jun 29, 16:25 UTCJun 29, 18:44 UTC2h 20m
2026-06-28 FDX10 - Jun 28, 13:59 UTCJun 28, 15:20 UTC1h 20m
2026-06-27 FDX10 - Jun 27, 22:49 UTCJun 28, 12:09 UTC13h 20m
2026-06-27 FDX5174 - Jun 27, 11:14 UTCJun 27, 14:00 UTC2h 45m
2026-06-26 FDX5174 - Jun 26, 16:44 UTCJun 27, 08:44 UTC16h 0m
2026-06-26 FDX5174 - Jun 26, 09:35 UTCJun 27, 08:44 UTC23h 10m
2026-06-26 FDX5175 - Jun 26, 06:35 UTCJun 26, 23:19 UTC16h 45m
2026-06-25 FDX10 - Jun 25, 09:20 UTCJun 25, 17:05 UTC7h 45m
2026-06-24 FDX1 - Jun 24, 20:09 UTCJun 24, 21:19 UTC1h 10m
2026-06-24 FDX1 STN → MEM Jun 24, 20:09 UTCJun 25, 04:51 UTC8h 42m
2026-06-24 FDX2 MEM → STN Jun 24, 09:30 UTCJun 24, 17:00 UTC7h 30m
2026-06-24 FDX2 - Jun 24, 09:34 UTCJun 24, 17:14 UTC7h 40m
2026-06-23 FDX1 - Jun 23, 20:04 UTCJun 24, 04:39 UTC8h 35m
2026-06-23 FDX1 STN → MEM Jun 23, 20:00 UTCJun 24, 04:45 UTC8h 45m
2026-06-23 FDX2 - Jun 23, 09:40 UTCJun 23, 17:09 UTC7h 30m
2026-06-22 FDX32 MEM → CGN Jun 22, 18:49 UTCJun 23, 04:14 UTC9h 25m
2026-06-22 FDX32 MEM → CGN Jun 22, 16:10 UTCJun 22, 16:50 UTC40m
2026-06-21 FDX38 - Jun 21, 23:34 UTCJun 22, 07:34 UTC8h 0m
2026-06-20 FDX5225 - Jun 20, 22:10 UTCJun 21, 07:34 UTC9h 25m
2026-06-20 FDX5024 - Jun 20, 15:09 UTCJun 20, 15:54 UTC45m
2026-06-20 FDX5022 MEM → CDG Jun 20, 00:49 UTCJun 20, 08:39 UTC7h 50m

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

Mode-S AC5FD6 frequently asked

What is Mode-S code AC5FD6?
AC5FD6 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N897FD.
Where is Mode-S AC5FD6 registered?
Mode-S code AC5FD6 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 AC5FD6 broadcasting right now?
No active broadcast right now. Last signal was 3h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AC5FD6, octal 53057726, decimal 11,296,726.
What flights does AC5FD6 operate?
Mode-S AC5FD6 has broadcast 20 distinct callsigns, including FDX97, FDX5174, FDX5928, FDX7, FDX5217.