sensors Mode-S transponder

A04A6D

ICAO 24-bit transponder address · allocated to United States

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

Hex
A04A6D
Octal
50045155
Decimal
10,504,813
Country
US
Tail
N118FE
Type
B763
No current signal · last broadcast 3d ago
Flights observed
167
Distinct callsigns
20
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S A04A6D.

Country allocation

The ICAO 24-bit address A04A6D 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
FDX6068 - 12 2026-07-01
FDX6067 - 11 2026-07-01
FDX6127 - 8 2026-07-10
FDX6091 - 8 2026-06-19
FDX6126 - 7 2026-07-10
FDX6159 - 6 2026-06-20
FDX6002 - 6 2026-06-30
FDX6001 - 6 2026-06-29
FDX9172 - 5 2026-06-28
FDX9073 - 5 2026-06-15
FDX6020 - 5 2026-06-23
FDX5926 - 5 2026-07-09
FDX5284 - 5 2026-07-02
FDX5199 - 5 2026-07-03
FDX6019 - 4 2026-06-22
FDX5960 FedEx Express 4 2026-06-10
FDX5775 - 4 2026-07-01
FDX5311 - 4 2026-07-02
FDX6231 - 3 2026-07-07
FDX5231 - 3 2026-07-10

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDX6076 - Jul 14, 17:20 UTCJul 14, 18:20 UTC1h 0m
2026-07-14 FDX5262 - Jul 14, 08:35 UTCJul 14, 15:25 UTC6h 50m
2026-07-13 FDX6074 KIX → KIX Jul 13, 14:30 UTCJul 14, 01:05 UTC10h 35m
2026-07-11 FDX6028 - Jul 11, 19:10 UTCJul 11, 22:35 UTC3h 25m
2026-07-10 - - Jul 10, 16:35 UTCJul 10, 16:45 UTC10m
2026-07-10 FDX5231 - Jul 10, 14:00 UTCJul 10, 14:40 UTC40m
2026-07-10 FDX6127 TPE → ICN Jul 10, 06:00 UTCJul 10, 08:05 UTC2h 5m
2026-07-10 FDX6126 ICN → TPE Jul 10, 01:20 UTCJul 10, 03:30 UTC2h 10m
2026-07-09 FDX5926 - Jul 9, 22:15 UTCJul 9, 22:55 UTC40m
2026-07-08 FDX5231 - Jul 8, 14:00 UTCJul 8, 14:40 UTC40m
2026-07-08 FDX6127 TPE → ICN Jul 8, 06:20 UTCJul 8, 08:25 UTC2h 5m
2026-07-08 FDX6126 ICN → TPE Jul 8, 01:55 UTCJul 8, 04:00 UTC2h 5m
2026-07-07 FDX6231 ICN → ICN Jul 7, 14:00 UTCJul 7, 22:55 UTC8h 55m
2026-07-07 FDX6127 TPE → ICN Jul 7, 05:05 UTCJul 7, 07:10 UTC2h 5m
2026-07-07 FDX6126 ICN → TPE Jul 7, 01:10 UTCJul 7, 03:15 UTC2h 5m
2026-07-06 FDX5926 - Jul 6, 22:20 UTCJul 6, 23:00 UTC40m
2026-07-06 FDX5231 - Jul 6, 13:45 UTCJul 6, 14:25 UTC40m
2026-07-06 FDX6127 TPE → ICN Jul 6, 06:45 UTCJul 6, 08:55 UTC2h 10m
2026-07-06 FDX6126 ICN → TPE Jul 6, 02:05 UTCJul 6, 04:10 UTC2h 5m
2026-07-04 FDX9126 - Jul 4, 07:35 UTCJul 4, 09:25 UTC1h 50m
2026-07-03 FDX9156 - Jul 3, 22:55 UTCJul 4, 00:35 UTC1h 40m
2026-07-03 FDX5199 - Jul 3, 13:35 UTCJul 3, 14:30 UTC55m
2026-07-02 FDX6075 KIX → KIX Jul 2, 17:25 UTCJul 3, 02:35 UTC9h 10m
2026-07-02 FDX5284 KIX → KIX Jul 2, 08:35 UTCJul 2, 15:30 UTC6h 55m
2026-07-02 FDX5311 - Jul 2, 04:00 UTCJul 2, 05:10 UTC1h 10m
2026-07-01 FDX5775 - Jul 1, 23:15 UTCJul 2, 00:50 UTC1h 35m
2026-07-01 FDX6067 - Jul 1, 18:05 UTCJul 1, 18:35 UTC30m
2026-07-01 FDX6067 - Jul 1, 11:05 UTCJul 1, 11:30 UTC25m
2026-07-01 FDX6068 - Jul 1, 04:05 UTCJul 1, 05:25 UTC1h 20m
2026-07-01 FDX6068 - Jul 1, 01:25 UTCJul 1, 01:45 UTC20m
2026-06-30 FDX6002 - Jun 30, 16:40 UTCJun 30, 22:20 UTC5h 40m
2026-06-30 FDX6002 - Jun 30, 13:00 UTCJun 30, 14:20 UTC1h 20m
2026-06-29 FDX6001 - Jun 29, 23:49 UTCJun 30, 01:14 UTC1h 25m
2026-06-29 FDX6001 - Jun 29, 21:44 UTCJun 29, 22:10 UTC25m
2026-06-28 FDX9125 MEM → SJU Jun 28, 19:14 UTCJun 28, 19:40 UTC25m
2026-06-28 FDX9172 - Jun 28, 14:34 UTCJun 28, 17:19 UTC2h 45m
2026-06-27 FDX6073 - Jun 27, 14:25 UTCJun 28, 01:40 UTC11h 15m
2026-06-27 FDX6074 - Jun 27, 00:25 UTCJun 27, 01:15 UTC50m
2026-06-25 FDX5199 - Jun 25, 13:40 UTCJun 25, 14:39 UTC1h 0m
2026-06-24 FDX5284 - Jun 24, 08:30 UTCJun 24, 15:00 UTC6h 30m
2026-06-24 FDX5311 - Jun 24, 03:55 UTCJun 24, 04:50 UTC55m
2026-06-23 FDX5775 - Jun 23, 23:10 UTCJun 24, 00:44 UTC1h 35m
2026-06-23 FDX6020 - Jun 23, 13:45 UTCJun 23, 16:39 UTC2h 55m
2026-06-22 FDX6019 - Jun 22, 20:19 UTCJun 22, 23:45 UTC3h 25m
2026-06-21 FDX6024 - Jun 21, 18:39 UTCJun 21, 21:49 UTC3h 10m
2026-06-21 FDX18 - Jun 21, 13:24 UTCJun 21, 16:39 UTC3h 15m
2026-06-20 FDX169 - Jun 20, 22:30 UTCJun 20, 22:54 UTC25m
2026-06-20 FDX169 - Jun 20, 19:19 UTCJun 20, 19:44 UTC25m
2026-06-20 FDX5148 - Jun 20, 06:49 UTCJun 20, 07:49 UTC1h 0m
2026-06-20 FDX6159 - Jun 20, 01:24 UTCJun 20, 01:39 UTC15m

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

Mode-S A04A6D frequently asked

What is Mode-S code A04A6D?
A04A6D is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N118FE.
Where is Mode-S A04A6D registered?
Mode-S code A04A6D 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 A04A6D broadcasting right now?
No active broadcast right now. Last signal was 3d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A04A6D, octal 50045155, decimal 10,504,813.
What flights does A04A6D operate?
Mode-S A04A6D has broadcast 20 distinct callsigns, including FDX6068, FDX6067, FDX6127, FDX6091, FDX6126.