sensors Mode-S transponder

AD4F2A

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N957FE · CESSNA 208 Caravan · operated by FEDERAL EXPRESS CORPORATION

Hex
AD4F2A
Octal
53247452
Decimal
11,357,994
Country
US
Tail
N957FE
Type
C208
No current signal · last broadcast 18h ago
Flights observed
93
Distinct callsigns
20
Country
US
Last broadcast
18h ago

Last known position

Most recent position reported by Mode-S AD4F2A.

Country allocation

The ICAO 24-bit address AD4F2A 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
CFS8675 - 11 2026-07-11
CFS7697 Empire Airlines 10 2026-05-15
CFS8697 Empire Airlines 9 2026-05-14
CFS8655 - 7 2026-05-28
CFS7686 Empire Airlines 6 2026-06-05
CFS8667 - 5 2026-07-01
CFS7655 Empire Airlines 5 2026-04-21
CFS7692 - 4 2026-06-23
CFS8692 Empire Airlines 3 2026-06-13
CFS8686 Empire Airlines 3 2026-06-05
CFS4697 Empire Airlines 3 2026-05-26
CFS7687 Empire Airlines 2 2026-05-30
CFS7675 - 2 2026-07-03
CFS7662 - 2 2026-06-12
CFS4692 Empire Airlines 2 2026-06-15
CFS4686 - 2 2026-07-13
CFS4662 Empire Airlines 2 2026-06-12
CFS8984 - 1 2026-06-17
CFS8978 - 1 2026-07-10
CFS8976 Empire Airlines 1 2026-05-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 CFS4686 - Jul 13, 19:30 UTCJul 13, 20:25 UTC55m
2026-07-11 CFS8675 - Jul 11, 15:05 UTCJul 11, 16:30 UTC1h 25m
2026-07-10 CFS4978 - Jul 10, 17:35 UTCJul 10, 18:25 UTC50m
2026-07-10 CFS8978 - Jul 10, 15:40 UTCJul 10, 16:50 UTC1h 10m
2026-07-09 CFS8675 - Jul 9, 15:50 UTCJul 9, 17:10 UTC1h 20m
2026-07-08 CFS8675 - Jul 8, 16:25 UTCJul 8, 17:55 UTC1h 30m
2026-07-06 CFS8675 - Jul 6, 12:50 UTCJul 6, 14:10 UTC1h 20m
2026-07-03 CFS7675 - Jul 3, 23:10 UTCJul 4, 00:10 UTC1h 0m
2026-07-03 CFS8675 - Jul 3, 15:10 UTCJul 3, 16:30 UTC1h 20m
2026-07-02 CFS8675 - Jul 2, 15:40 UTCJul 2, 16:55 UTC1h 15m
2026-07-01 CFS8667 PDX → RDM Jul 1, 14:55 UTCJul 1, 15:40 UTC45m
2026-06-30 CFS8675 - Jun 30, 16:10 UTCJun 30, 17:25 UTC1h 15m
2026-06-29 CFS8675 - Jun 29, 12:55 UTCJun 29, 14:09 UTC1h 15m
2026-06-26 CFS8675 - Jun 26, 15:39 UTCJun 26, 17:04 UTC1h 25m
2026-06-25 CFS8675 - Jun 25, 15:34 UTCJun 25, 16:55 UTC1h 20m
2026-06-24 CFS8675 - Jun 24, 15:39 UTCJun 24, 16:54 UTC1h 15m
2026-06-23 CFS7692 - Jun 23, 23:29 UTCJun 24, 00:15 UTC45m
2026-06-23 CFS8667 PDX → RDM Jun 23, 15:24 UTCJun 23, 16:09 UTC45m
2026-06-17 CFS8984 - Jun 17, 15:40 UTCJun 17, 16:25 UTC45m
2026-06-16 CFS7692 RDM → PDX Jun 16, 23:20 UTCJun 17, 00:15 UTC55m
2026-06-16 CFS8667 PDX → RDM Jun 16, 14:50 UTCJun 16, 15:30 UTC40m
2026-06-15 CFS7692 RDM → PDX Jun 15, 23:30 UTCJun 16, 00:24 UTC55m
2026-06-15 CFS4692 PDX → RDM Jun 15, 20:50 UTCJun 15, 21:35 UTC45m
2026-06-13 CFS4692 PDX → RDM Jun 13, 16:40 UTCJun 13, 17:25 UTC45m
2026-06-13 CFS8692 PDX → RDM Jun 13, 15:20 UTCJun 13, 16:00 UTC40m
2026-06-12 CFS7662 - Jun 12, 23:50 UTCJun 13, 00:40 UTC50m
2026-06-12 CFS4662 PDX → EUG Jun 12, 18:05 UTCJun 12, 18:50 UTC45m
2026-06-12 CFS8692 PDX → RDM Jun 12, 15:50 UTCJun 12, 16:30 UTC40m
2026-06-11 CFS7662 EUG → PDX Jun 11, 23:50 UTCJun 12, 00:35 UTC46m
2026-06-11 CFS8692 PDX → RDM Jun 11, 15:45 UTCJun 11, 16:25 UTC40m
2026-06-10 CFS7692 RDM → PDX Jun 10, 23:35 UTCJun 11, 00:30 UTC55m
2026-06-10 CFS8667 PDX → RDM Jun 10, 15:10 UTCJun 10, 15:50 UTC40m
2026-06-09 CFS8667 PDX → RDM Jun 9, 15:00 UTCJun 9, 15:50 UTC50m
2026-06-08 CFS4662 PDX → EUG Jun 8, 20:45 UTCJun 8, 21:35 UTC50m
2026-06-05 CFS8686 PDX → OTH Jun 5, 15:50 UTCJun 5, 16:55 UTC1h 5m
2026-06-05 CFS7686 SLE → PDX Jun 5, 00:10 UTCJun 5, 00:35 UTC25m
2026-06-04 CFS7686 SLE → PDX Jun 4, 22:25 UTCJun 4, 22:50 UTC25m
2026-06-04 CFS8686 PDX → OTH Jun 4, 15:05 UTCJun 4, 15:55 UTC50m
2026-06-04 CFS7686 SLE → PDX Jun 4, 00:20 UTCJun 4, 00:45 UTC25m
2026-06-03 CFS7686 SLE → PDX Jun 3, 22:45 UTCJun 3, 23:25 UTC40m
2026-06-03 CFS8686 PDX → OTH Jun 3, 15:45 UTCJun 3, 16:35 UTC50m
2026-06-02 CFS7686 SLE → PDX Jun 2, 00:05 UTCJun 2, 00:30 UTC25m
2026-06-01 CFS7686 SLE → PDX Jun 1, 22:15 UTCJun 1, 22:45 UTC30m
2026-06-01 CFS4686 PDX → OTH Jun 1, 19:10 UTCJun 1, 20:00 UTC50m
2026-05-30 CFS7687 MFR → PDX May 30, 23:15 UTCMay 31, 00:35 UTC1h 20m
2026-05-30 CFS7687 MFR → PDX May 30, 22:10 UTCMay 30, 22:25 UTC15m
2026-05-30 CFS8690 PDX → RBG May 30, 15:00 UTCMay 30, 15:45 UTC45m
2026-05-28 CFS7675 LMT → PDX May 28, 23:05 UTCMay 29, 00:30 UTC1h 25m
2026-05-28 CFS8655 - May 28, 14:25 UTCMay 28, 15:20 UTC55m
2026-05-27 CFS4976 OTH → PDX May 27, 21:25 UTCMay 27, 22:20 UTC55m

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

Mode-S AD4F2A frequently asked

What is Mode-S code AD4F2A?
AD4F2A is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N957FE.
Where is Mode-S AD4F2A registered?
Mode-S code AD4F2A 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 AD4F2A broadcasting right now?
No active broadcast right now. Last signal was 18h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD4F2A, octal 53247452, decimal 11,357,994.
What flights does AD4F2A operate?
Mode-S AD4F2A has broadcast 20 distinct callsigns, including CFS8675, CFS7697, CFS8697, CFS8655, CFS7686.