sensors Mode-S transponder

A63F3A

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N501SC · CESSNA 172 Skyhawk · operated by SAZ DYNAMICS LLC

Hex
A63F3A
Octal
51437472
Decimal
10,895,162
Country
US
Tail
N501SC
Type
C172
No current signal · last broadcast 7h ago
Flights observed
182
Distinct callsigns
1
Country
US
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S A63F3A.

Country allocation

The ICAO 24-bit address A63F3A 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
N501SC - 182 2026-07-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-24 N501SC PAO → PAO Jul 24, 01:25 UTCJul 24, 02:15 UTC50m
2026-07-23 N501SC PAO → PAO Jul 23, 19:35 UTCJul 23, 20:30 UTC55m
2026-07-23 N501SC PAO → PAO Jul 23, 15:30 UTCJul 23, 16:40 UTC1h 10m
2026-07-22 N501SC PAO → PAO Jul 22, 20:45 UTCJul 22, 21:30 UTC45m
2026-07-22 N501SC PAO → PAO Jul 22, 17:45 UTCJul 22, 17:50 UTC5m
2026-07-22 N501SC PAO → PAO Jul 22, 17:30 UTCJul 22, 17:40 UTC10m
2026-07-22 N501SC PAO → PAO Jul 22, 17:10 UTCJul 22, 17:25 UTC15m
2026-07-21 N501SC PAO → PAO Jul 21, 20:35 UTCJul 21, 21:20 UTC45m
2026-07-21 N501SC PAO → PAO Jul 21, 01:20 UTCJul 21, 01:55 UTC35m
2026-07-20 N501SC PAO → PAO Jul 20, 18:35 UTCJul 20, 20:30 UTC1h 55m
2026-07-19 N501SC PAO → PAO Jul 19, 18:35 UTCJul 19, 21:05 UTC2h 30m
2026-07-18 N501SC PAO → PAO Jul 18, 20:05 UTCJul 18, 21:00 UTC55m
2026-07-18 N501SC HWD → PAO Jul 18, 17:45 UTCJul 18, 18:10 UTC25m
2026-07-18 N501SC PAO → HWD Jul 18, 17:05 UTCJul 18, 17:40 UTC35m
2026-07-17 N501SC PAO → PAO Jul 17, 18:44 UTCJul 17, 20:40 UTC1h 55m
2026-07-16 N501SC PAO → PAO Jul 16, 22:05 UTCJul 16, 23:49 UTC1h 45m
2026-07-16 N501SC PAO → PAO Jul 16, 18:19 UTCJul 16, 19:30 UTC1h 10m
2026-07-14 N501SC - Jul 14, 21:30 UTCJul 14, 22:45 UTC1h 14m
2026-07-14 N501SC - Jul 14, 18:20 UTCJul 14, 19:25 UTC1h 5m
2026-07-13 N501SC PAO → PAO Jul 13, 21:10 UTCJul 13, 23:25 UTC2h 15m
2026-07-13 N501SC - Jul 13, 18:15 UTCJul 13, 18:55 UTC40m
2026-07-13 N501SC - Jul 13, 17:55 UTCJul 13, 18:05 UTC10m
2026-07-13 N501SC PAO → PAO Jul 13, 00:40 UTCJul 13, 01:05 UTC25m
2026-07-12 N501SC - Jul 12, 22:10 UTCJul 12, 22:35 UTC25m
2026-07-12 N501SC - Jul 12, 21:20 UTCJul 12, 21:55 UTC35m
2026-07-12 N501SC PAO → PAO Jul 12, 16:20 UTCJul 12, 17:50 UTC1h 30m
2026-07-11 N501SC PAO → PAO Jul 11, 19:50 UTCJul 11, 20:55 UTC1h 5m
2026-07-11 N501SC PAO → PAO Jul 11, 01:55 UTCJul 11, 02:50 UTC55m
2026-07-10 N501SC PAO → PAO Jul 10, 22:30 UTCJul 10, 23:05 UTC35m
2026-07-10 N501SC PAO → PAO Jul 10, 21:40 UTCJul 10, 22:25 UTC45m
2026-07-10 N501SC PAO → PAO Jul 10, 17:35 UTCJul 10, 18:15 UTC40m
2026-07-10 N501SC PAO → PAO Jul 10, 14:40 UTCJul 10, 15:35 UTC55m
2026-07-09 N501SC PAO → PAO Jul 9, 22:15 UTCJul 9, 23:00 UTC45m
2026-07-09 N501SC PAO → PAO Jul 9, 18:15 UTCJul 9, 20:10 UTC1h 55m
2026-07-08 N501SC PAO → PAO Jul 8, 19:40 UTCJul 8, 20:35 UTC55m
2026-07-08 N501SC PAO → PAO Jul 8, 17:05 UTCJul 8, 17:55 UTC50m
2026-07-07 N501SC PAO → PAO Jul 7, 16:05 UTCJul 7, 16:55 UTC50m
2026-07-06 N501SC PAO → PAO Jul 6, 14:35 UTCJul 6, 15:35 UTC1h 0m
2026-07-05 N501SC PAO → PAO Jul 5, 19:25 UTCJul 5, 20:45 UTC1h 20m
2026-07-04 N501SC PAO → PAO Jul 4, 18:10 UTCJul 4, 19:05 UTC55m
2026-07-03 N501SC PAO → PAO Jul 3, 20:15 UTCJul 3, 20:35 UTC20m
2026-07-03 N501SC - Jul 3, 20:00 UTCJul 3, 20:10 UTC10m
2026-07-03 N501SC PAO → PAO Jul 3, 19:40 UTCJul 3, 19:50 UTC10m
2026-07-03 N501SC PAO → PAO Jul 3, 01:15 UTCJul 3, 02:20 UTC1h 5m
2026-07-02 N501SC PAO → PAO Jul 2, 18:30 UTCJul 2, 20:30 UTC2h 0m
2026-07-02 N501SC PAO → PAO Jul 2, 14:40 UTCJul 2, 15:45 UTC1h 5m
2026-07-01 N501SC PAO → PAO Jul 1, 16:45 UTCJul 1, 16:50 UTC5m
2026-07-01 N501SC PAO → PAO Jul 1, 16:30 UTCJul 1, 16:40 UTC10m
2026-06-30 N501SC PAO → PAO Jun 30, 19:55 UTCJun 30, 21:00 UTC1h 5m
2026-06-30 N501SC PAO → PAO Jun 30, 17:05 UTCJun 30, 18:10 UTC1h 5m

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

Mode-S A63F3A frequently asked

What is Mode-S code A63F3A?
A63F3A is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N501SC.
Where is Mode-S A63F3A registered?
Mode-S code A63F3A 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 A63F3A broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A63F3A, octal 51437472, decimal 10,895,162.
What flights does A63F3A operate?
Mode-S A63F3A has broadcast 1 distinct callsign, including N501SC.