Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A0FD13

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N163CP · operated by TEXTRON AVIATION INC

Hex
A0FD13
Octal
50176423
Decimal
10,550,547
Country
US
Tail
N163CP
Transponder active on ground
Flights observed
74
Distinct callsigns
1
Country
US
Last broadcast
6d ago

Last known position

Most recent position reported by Mode-S A0FD13.

Country allocation

The ICAO 24-bit address A0FD13 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 1 distinct

Callsign Airline Flights Last seen
CAP563 - 74 2026-07-12

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 CAP563 - Jul 12, 16:30 UTCJul 12, 17:05 UTC35m
2026-07-12 CAP563 FNL → GXY Jul 12, 14:55 UTCJul 12, 15:35 UTC40m
2026-07-10 CAP563 FNL → FNL Jul 10, 14:35 UTCJul 10, 15:35 UTC1h 0m
2026-07-01 CAP563 BJC → FNL Jul 1, 16:30 UTCJul 1, 16:55 UTC25m
2026-07-01 CAP563 FNL → BJC Jul 1, 14:40 UTCJul 1, 15:10 UTC30m
2026-06-30 CAP563 FNL → FNL Jun 30, 14:50 UTCJun 30, 15:50 UTC1h 0m
2026-06-29 CAP563 FNL → FNL Jun 29, 14:34 UTCJun 29, 15:24 UTC50m
2026-06-24 CAP563 FNL → FNL Jun 24, 18:39 UTCJun 24, 19:20 UTC40m
2026-06-22 CAP563 COS → FNL Jun 22, 14:24 UTCJun 22, 15:20 UTC55m
2026-06-21 CAP563 - Jun 21, 18:29 UTCJun 21, 19:05 UTC35m
2026-06-21 CAP563 - Jun 21, 13:24 UTCJun 21, 15:09 UTC1h 45m
2026-06-19 CAP563 - Jun 19, 14:34 UTCJun 19, 15:34 UTC1h 0m
2026-06-18 CAP563 - Jun 18, 15:45 UTCJun 18, 16:55 UTC1h 10m
2026-06-18 CAP563 - Jun 18, 14:30 UTCJun 18, 14:55 UTC25m
2026-06-16 CAP563 - Jun 16, 14:39 UTCJun 16, 15:00 UTC20m
2026-06-15 CAP563 - Jun 15, 23:25 UTCJun 16, 00:10 UTC45m
2026-06-15 CAP563 - Jun 15, 15:59 UTCJun 15, 16:35 UTC35m
2026-06-15 CAP563 - Jun 15, 14:45 UTCJun 15, 15:10 UTC25m
2026-06-13 CAP563 - Jun 13, 23:30 UTCJun 14, 00:00 UTC30m
2026-06-13 CAP563 - Jun 13, 16:20 UTCJun 13, 16:45 UTC25m
2026-06-13 CAP563 - Jun 13, 15:20 UTCJun 13, 15:40 UTC20m
2026-06-12 CAP563 - Jun 12, 23:30 UTCJun 13, 00:45 UTC1h 15m
2026-06-11 CAP563 - Jun 11, 18:40 UTCJun 11, 20:00 UTC1h 20m
2026-06-11 CAP563 - Jun 11, 16:20 UTCJun 11, 17:20 UTC1h 0m
2026-06-08 CAP563 FNL → COS Jun 8, 18:25 UTCJun 8, 19:25 UTC1h 0m
2026-06-07 CAP563 FNL → FNL Jun 7, 22:30 UTCJun 7, 23:15 UTC45m
2026-06-07 CAP563 - Jun 7, 21:05 UTCJun 7, 21:40 UTC35m
2026-06-07 CAP563 - Jun 7, 16:45 UTCJun 7, 17:35 UTC50m
2026-06-07 CAP563 FNL → GXY Jun 7, 15:05 UTCJun 7, 15:45 UTC40m
2026-06-06 CAP563 FNL → FNL Jun 6, 18:50 UTCJun 6, 19:34 UTC45m
2026-06-06 CAP563 GXY → FNL Jun 6, 16:45 UTCJun 6, 17:24 UTC40m
2026-06-06 CAP563 FNL → GXY Jun 6, 15:25 UTCJun 6, 15:59 UTC35m
2026-06-05 CAP563 - Jun 5, 19:20 UTCJun 5, 20:20 UTC1h 0m
2026-05-23 CAP563 GXY → FNL May 23, 19:35 UTCMay 23, 20:05 UTC30m
2026-05-23 CAP563 FNL → GXY May 23, 16:35 UTCMay 23, 17:35 UTC1h 0m
2026-05-19 CAP563 - May 19, 21:20 UTCMay 19, 22:10 UTC50m
2026-05-19 CAP563 FNL → GXY May 19, 18:50 UTCMay 19, 19:50 UTC1h 0m
2026-05-16 CAP563 - May 16, 21:25 UTCMay 16, 22:05 UTC40m
2026-05-16 CAP563 FNL → GXY May 16, 19:30 UTCMay 16, 20:05 UTC35m
2026-05-11 CAP563 FNL → FNL May 11, 17:20 UTCMay 11, 18:45 UTC1h 25m
2026-05-09 CAP563 - May 9, 22:30 UTCMay 9, 22:49 UTC20m
2026-05-09 CAP563 - May 9, 20:44 UTCMay 9, 21:40 UTC55m
2026-05-09 CAP563 - May 9, 19:14 UTCMay 9, 19:55 UTC40m
2026-05-09 CAP563 - May 9, 17:10 UTCMay 9, 18:05 UTC55m
2026-05-09 CAP563 - May 9, 15:30 UTCMay 9, 16:15 UTC45m
2026-05-09 CAP563 - May 9, 14:20 UTCMay 9, 14:35 UTC15m
2026-05-04 CAP563 GXY → FNL May 4, 19:00 UTCMay 4, 20:00 UTC1h 0m
2026-05-04 CAP563 FNL → GXY May 4, 17:00 UTCMay 4, 17:45 UTC45m
2026-05-03 CAP563 FNL → FNL May 3, 20:25 UTCMay 3, 22:25 UTC2h 0m
2026-05-03 CAP563 - May 3, 17:05 UTCMay 3, 17:35 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 N163CP page for operator, model, and routing details .

Mode-S A0FD13 frequently asked

What is Mode-S code A0FD13?
A0FD13 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N163CP.
Where is Mode-S A0FD13 registered?
Mode-S code A0FD13 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 A0FD13 broadcasting right now?
Mode-S A0FD13 is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A0FD13, octal 50176423, decimal 10,550,547.
What flights does A0FD13 operate?
Mode-S A0FD13 has broadcast 1 distinct callsign, including CAP563.