sensors Mode-S transponder

AC0D22

ICAO 24-bit transponder address · allocated to United States

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

Hex
AC0D22
Octal
53006442
Decimal
11,275,554
Country
US
Tail
N876FE
Type
C208
No current signal · last broadcast 6d ago
Flights observed
54
Distinct callsigns
15
Country
US
Last broadcast
6d ago

Last known position

Most recent position reported by Mode-S AC0D22.

Country allocation

The ICAO 24-bit address AC0D22 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 15 distinct

Callsign Airline Flights Last seen
CFS7805 - 10 2026-06-20
CFS8812 Empire Airlines 8 2026-06-19
CFS201 Empire Airlines 7 2026-06-06
CFS8801 - 6 2026-06-27
CFS7801 - 5 2026-06-26
CFS4805 Empire Airlines 5 2026-06-19
CFS4801 - 3 2026-06-27
CFS7775 - 2 2026-07-08
CFS7726 Empire Airlines 2 2026-05-18
CFS8802 - 1 2026-07-03
CFS8775 - 1 2026-07-07
CFS8744 Empire Airlines 1 2026-05-14
CFS4802 - 1 2026-07-03
CFS4775 - 1 2026-07-06
CFS4726 Empire Airlines 1 2026-05-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-08 CFS7775 - Jul 8, 00:20 UTCJul 8, 00:50 UTC30m
2026-07-07 CFS8775 - Jul 7, 15:45 UTCJul 7, 16:20 UTC35m
2026-07-07 CFS7775 - Jul 7, 00:40 UTCJul 7, 01:10 UTC30m
2026-07-06 CFS4775 - Jul 6, 21:25 UTCJul 6, 21:55 UTC30m
2026-07-03 CFS4802 - Jul 3, 16:10 UTCJul 3, 16:55 UTC45m
2026-07-03 CFS8802 - Jul 3, 14:35 UTCJul 3, 15:20 UTC45m
2026-06-27 CFS4801 HII → PHX Jun 27, 19:39 UTCJun 27, 20:44 UTC1h 5m
2026-06-27 CFS8801 - Jun 27, 15:10 UTCJun 27, 16:14 UTC1h 5m
2026-06-26 CFS7801 HII → PHX Jun 26, 23:55 UTCJun 27, 00:55 UTC1h 0m
2026-06-26 CFS8801 - Jun 26, 14:35 UTCJun 26, 15:34 UTC1h 0m
2026-06-26 CFS7801 - Jun 26, 00:10 UTCJun 26, 01:15 UTC1h 5m
2026-06-25 CFS8801 - Jun 25, 15:04 UTCJun 25, 16:09 UTC1h 5m
2026-06-25 CFS7801 HII → PHX Jun 25, 00:05 UTCJun 25, 01:14 UTC1h 10m
2026-06-24 CFS8801 PHX → HII Jun 24, 14:50 UTCJun 24, 15:49 UTC1h 0m
2026-06-23 CFS7801 - Jun 23, 23:55 UTCJun 24, 00:55 UTC1h 0m
2026-06-23 CFS8801 - Jun 23, 14:49 UTCJun 23, 15:40 UTC50m
2026-06-23 CFS7801 HII → PHX Jun 23, 00:04 UTCJun 23, 01:10 UTC1h 5m
2026-06-22 CFS4801 PHX → HII Jun 22, 20:24 UTCJun 22, 21:25 UTC1h 0m
2026-06-20 CFS4801 - Jun 20, 16:49 UTCJun 20, 17:44 UTC55m
2026-06-20 CFS8801 - Jun 20, 14:44 UTCJun 20, 15:49 UTC1h 5m
2026-06-20 CFS7805 - Jun 20, 00:14 UTCJun 20, 00:59 UTC45m
2026-06-19 CFS4805 PHX → YUM Jun 19, 16:29 UTCJun 19, 17:04 UTC35m
2026-06-19 CFS8812 PHX → YUM Jun 19, 14:49 UTCJun 19, 15:54 UTC1h 5m
2026-06-19 CFS7805 - Jun 19, 00:24 UTCJun 19, 01:10 UTC45m
2026-06-18 CFS8812 PHX → YUM Jun 18, 15:00 UTCJun 18, 15:50 UTC50m
2026-06-18 CFS7805 - Jun 18, 00:50 UTCJun 18, 01:35 UTC45m
2026-06-17 CFS8812 PHX → YUM Jun 17, 15:05 UTCJun 17, 15:50 UTC45m
2026-06-17 CFS7805 - Jun 17, 00:25 UTCJun 17, 01:20 UTC55m
2026-06-16 CFS8812 PHX → YUM Jun 16, 15:00 UTCJun 16, 15:45 UTC45m
2026-06-16 CFS7805 - Jun 16, 00:15 UTCJun 16, 01:04 UTC50m
2026-06-15 CFS4805 PHX → YUM Jun 15, 20:59 UTCJun 15, 21:45 UTC45m
2026-06-13 CFS7805 YUM → PHX Jun 13, 00:20 UTCJun 13, 01:10 UTC50m
2026-06-12 CFS8812 PHX → YUM Jun 12, 15:05 UTCJun 12, 15:50 UTC45m
2026-06-12 CFS7805 YUM → PHX Jun 12, 00:25 UTCJun 12, 01:15 UTC51m
2026-06-11 CFS4805 PHX → YUM Jun 11, 16:40 UTCJun 11, 17:35 UTC55m
2026-06-11 CFS8812 PHX → YUM Jun 11, 14:55 UTCJun 11, 15:25 UTC30m
2026-06-11 CFS7805 YUM → PHX Jun 11, 00:30 UTCJun 11, 01:20 UTC50m
2026-06-10 CFS8812 PHX → YUM Jun 10, 14:40 UTCJun 10, 15:30 UTC50m
2026-06-10 CFS7805 YUM → PHX Jun 10, 00:20 UTCJun 10, 01:10 UTC50m
2026-06-09 CFS4805 PHX → YUM Jun 9, 17:40 UTCJun 9, 19:00 UTC1h 20m
2026-06-09 CFS8812 PHX → YUM Jun 9, 15:30 UTCJun 9, 15:50 UTC20m
2026-06-09 CFS7805 YUM → PHX Jun 9, 00:20 UTCJun 9, 01:20 UTC1h 0m
2026-06-08 CFS4805 PHX → YUM Jun 8, 20:35 UTCJun 8, 21:20 UTC45m
2026-06-06 CFS201 PDX → YKM Jun 6, 17:24 UTCJun 6, 17:49 UTC25m
2026-06-06 CFS201 PDX → YKM Jun 6, 15:50 UTCJun 6, 16:20 UTC30m
2026-06-06 CFS201 PDX → YKM Jun 6, 13:05 UTCJun 6, 13:34 UTC30m
2026-05-21 CFS201 PDX → YKM May 21, 18:00 UTCMay 21, 18:50 UTC50m
2026-05-21 CFS201 PDX → YKM May 21, 15:25 UTCMay 21, 15:40 UTC15m
2026-05-20 CFS201 PDX → YKM May 20, 00:00 UTCMay 20, 00:15 UTC15m
2026-05-19 CFS201 PDX → YKM May 19, 20:30 UTCMay 19, 21:00 UTC30m

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

Mode-S AC0D22 frequently asked

What is Mode-S code AC0D22?
AC0D22 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N876FE.
Where is Mode-S AC0D22 registered?
Mode-S code AC0D22 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 AC0D22 broadcasting right now?
No active broadcast right now. Last signal was 6d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AC0D22, octal 53006442, decimal 11,275,554.
What flights does AC0D22 operate?
Mode-S AC0D22 has broadcast 15 distinct callsigns, including CFS7805, CFS8812, CFS201, CFS8801, CFS7801.