Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A066C7

ICAO 24-bit transponder address · allocated to United States

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

Hex
A066C7
Octal
50063307
Decimal
10,512,071
Country
US
Tail
N125FE
Type
B763
Broadcasting now · callsign FDX5048 · 34,025 ft
Flights observed
225
Distinct callsigns
20
Country
US
Last broadcast
56m ago

Current position

A066C7 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A066C7 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
FDX55 - 19 2026-07-07
FDX5503 - 17 2026-07-09
FDX5504 FedEx Express 16 2026-07-09
FDX5501 - 14 2026-07-04
FDX5050 - 10 2026-07-02
FDX56 - 9 2026-07-07
FDX5051 - 9 2026-07-01
FDX40 - 8 2026-07-10
FDX115 - 8 2026-07-10
FDX5502 - 7 2026-07-04
FDX41 - 7 2026-06-24
FDX204 - 7 2026-06-17
FDX5048 - 6 2026-07-14
FDX5047 FedEx Express 6 2026-05-21
FDX205 - 6 2026-06-16
FDX43 - 5 2026-07-12
FDX114 - 5 2026-07-09
FDX1272 FedEx Express 4 2026-04-18
FDX9603 FedEx Express 3 2026-04-29
FDX3605 - 3 2026-06-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 FDX5048 - Jul 14, 08:15 UTCJul 14, 13:45 UTC5h 30m
2026-07-13 FDX5048 - Jul 13, 00:05 UTCJul 13, 00:20 UTC15m
2026-07-12 FDX5048 - Jul 12, 22:10 UTCJul 13, 00:01 UTC1h 50m
2026-07-12 FDX43 - Jul 12, 07:31 UTCJul 12, 09:15 UTC1h 45m
2026-07-11 FDX43 - Jul 11, 22:05 UTCJul 12, 04:15 UTC6h 10m
2026-07-10 FDX40 - Jul 10, 08:40 UTCJul 10, 17:50 UTC9h 10m
2026-07-10 FDX115 - Jul 10, 02:45 UTCJul 10, 04:35 UTC1h 50m
2026-07-09 FDX5504 SAP → MIA Jul 9, 23:55 UTCJul 10, 01:25 UTC1h 30m
2026-07-09 FDX5504 SAP → MIA Jul 9, 20:50 UTCJul 9, 21:15 UTC25m
2026-07-09 FDX5503 - Jul 9, 14:00 UTCJul 9, 16:15 UTC2h 15m
2026-07-09 FDX114 - Jul 9, 09:50 UTCJul 9, 11:40 UTC1h 50m
2026-07-09 FDX115 - Jul 9, 02:40 UTCJul 9, 04:40 UTC2h 0m
2026-07-08 FDX5504 SAP → MIA Jul 8, 23:30 UTCJul 9, 01:05 UTC1h 35m
2026-07-08 FDX5504 SAP → MIA Jul 8, 21:05 UTCJul 8, 21:30 UTC25m
2026-07-08 FDX5503 - Jul 8, 15:55 UTCJul 8, 16:05 UTC10m
2026-07-08 FDX5503 - Jul 8, 13:55 UTCJul 8, 15:25 UTC1h 30m
2026-07-08 FDX5503 MIA → GUA Jul 8, 13:53 UTCJul 8, 16:03 UTC2h 10m
2026-07-08 FDX114 - Jul 8, 09:35 UTCJul 8, 11:20 UTC1h 45m
2026-07-07 FDX56 - Jul 7, 15:30 UTCJul 8, 04:25 UTC12h 55m
2026-07-07 FDX55 - Jul 7, 13:30 UTCJul 7, 13:50 UTC20m
2026-07-07 FDX55 - Jul 7, 10:10 UTCJul 7, 11:55 UTC1h 45m
2026-07-07 FDX115 - Jul 7, 02:55 UTCJul 7, 04:40 UTC1h 45m
2026-07-06 FDX5504 SAP → MIA Jul 6, 23:30 UTCJul 7, 01:05 UTC1h 35m
2026-07-06 FDX5504 SAP → MIA Jul 6, 20:40 UTCJul 6, 21:05 UTC25m
2026-07-06 FDX5503 MIA → GUA Jul 6, 14:00 UTCJul 6, 16:10 UTC2h 10m
2026-07-06 FDX5503 MIA → GUA Jul 6, 14:00 UTCJul 6, 16:10 UTC2h 10m
2026-07-04 FDX5502 - Jul 4, 16:10 UTCJul 4, 16:40 UTC30m
2026-07-04 FDX5501 - Jul 4, 02:55 UTCJul 4, 03:25 UTC30m
2026-07-03 FDX5501 - Jul 3, 15:05 UTCJul 3, 23:30 UTC8h 25m
2026-07-03 FDX114 - Jul 3, 09:40 UTCJul 3, 11:25 UTC1h 45m
2026-07-03 FDX1314 - Jul 3, 03:05 UTCJul 3, 05:05 UTC2h 0m
2026-07-03 FDX1314 EWR → MEM Jul 3, 03:05 UTCJul 3, 05:09 UTC2h 4m
2026-07-02 FDX3709 - Jul 2, 20:50 UTCJul 2, 22:20 UTC1h 30m
2026-07-02 FDX5050 DUB → IND Jul 2, 07:50 UTCJul 2, 15:55 UTC8h 5m
2026-07-01 FDX5051 - Jul 1, 20:50 UTCJul 2, 03:35 UTC6h 45m
2026-07-01 FDX5050 DUB → IND Jul 1, 07:25 UTCJul 1, 15:30 UTC8h 5m
2026-06-30 FDX5051 - Jun 30, 20:55 UTCJul 1, 03:35 UTC6h 40m
2026-06-30 FDX3609 - Jun 30, 12:50 UTCJun 30, 13:45 UTC55m
2026-06-30 FDX3609 EWR → IND Jun 30, 12:50 UTCJun 30, 14:14 UTC1h 24m
2026-06-30 FDX1721 - Jun 30, 09:10 UTCJun 30, 10:40 UTC1h 30m
2026-06-27 FDX1574 NQA → IND Jun 27, 08:35 UTCJun 27, 09:29 UTC55m
2026-06-27 FDX1574 MEM → IND Jun 27, 08:30 UTCJun 27, 09:25 UTC55m
2026-06-27 FDX56 - Jun 27, 01:04 UTCJun 27, 04:24 UTC3h 20m
2026-06-27 FDX56 SJO → MEM Jun 27, 00:49 UTCJun 27, 04:25 UTC3h 36m
2026-06-26 FDX55 - Jun 26, 15:15 UTCJun 26, 15:25 UTC10m
2026-06-26 FDX55 - Jun 26, 09:55 UTCJun 26, 13:34 UTC3h 40m
2026-06-26 FDX2283 IND → MEM Jun 26, 04:20 UTCJun 26, 05:19 UTC1h 0m
2026-06-25 FDX3605 - Jun 25, 11:39 UTCJun 25, 13:50 UTC2h 10m
2026-06-25 FDX1444 - Jun 25, 07:54 UTCJun 25, 09:45 UTC1h 50m
2026-06-24 FDX41 - Jun 24, 19:20 UTCJun 25, 05:29 UTC10h 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 N125FE page for operator, model, and routing details .

Mode-S A066C7 frequently asked

What is Mode-S code A066C7?
A066C7 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N125FE.
Where is Mode-S A066C7 registered?
Mode-S code A066C7 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 A066C7 broadcasting right now?
Yes. Mode-S A066C7 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A066C7, octal 50063307, decimal 10,512,071.
What flights does A066C7 operate?
Mode-S A066C7 has broadcast 20 distinct callsigns, including FDX55, FDX5503, FDX5504, FDX5501, FDX5050.