Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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 2d ago
Flights observed
88
Distinct callsigns
1
Country
US
Last broadcast
2d 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 - 88 2026-06-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-06 N501SC - Jun 6, 22:30 UTCJun 6, 22:44 UTC15m
2026-06-06 N501SC - Jun 6, 20:35 UTCJun 6, 21:40 UTC1h 5m
2026-06-06 N501SC PAO → PAO Jun 6, 18:00 UTCJun 6, 18:59 UTC1h 0m
2026-06-06 N501SC PAO → PAO Jun 6, 15:54 UTCJun 6, 16:45 UTC50m
2026-05-31 N501SC PAO → PAO May 31, 21:30 UTCMay 31, 22:25 UTC55m
2026-05-31 N501SC CCR → PAO May 31, 19:30 UTCMay 31, 20:05 UTC35m
2026-05-31 N501SC PAO → CCR May 31, 18:45 UTCMay 31, 19:25 UTC40m
2026-05-30 N501SC HWD → PAO May 30, 21:50 UTCMay 30, 22:20 UTC30m
2026-05-30 N501SC PAO → HWD May 30, 21:30 UTCMay 30, 21:40 UTC10m
2026-05-30 N501SC PAO → PAO May 30, 18:40 UTCMay 30, 20:50 UTC2h 10m
2026-05-30 N501SC PAO → PAO May 30, 16:30 UTCMay 30, 16:55 UTC25m
2026-05-30 N501SC PAO → PAO May 30, 16:15 UTCMay 30, 16:25 UTC10m
2026-05-30 N501SC PAO → PAO May 30, 16:00 UTCMay 30, 16:10 UTC10m
2026-05-30 N501SC PAO → PAO May 30, 15:50 UTCMay 30, 15:55 UTC5m
2026-05-29 N501SC PAO → PAO May 29, 22:50 UTCMay 29, 23:35 UTC45m
2026-05-29 N501SC - May 29, 21:30 UTCMay 29, 21:55 UTC25m
2026-05-29 N501SC PAO → HWD May 29, 20:45 UTCMay 29, 21:20 UTC35m
2026-05-29 N501SC PAO → PAO May 29, 18:00 UTCMay 29, 18:15 UTC15m
2026-05-29 N501SC PAO → PAO May 29, 17:25 UTCMay 29, 17:55 UTC30m
2026-05-27 N501SC HWD → PAO May 27, 18:55 UTCMay 27, 19:25 UTC30m
2026-05-27 N501SC PAO → HWD May 27, 18:00 UTCMay 27, 18:50 UTC50m
2026-05-25 N501SC - May 25, 20:40 UTCMay 25, 20:55 UTC15m
2026-05-25 N501SC - May 25, 19:05 UTCMay 25, 19:25 UTC20m
2026-05-25 N501SC PAO → PAO May 25, 17:15 UTCMay 25, 17:55 UTC40m
2026-05-24 N501SC PAO → PAO May 24, 16:45 UTCMay 24, 17:35 UTC50m
2026-05-23 N501SC PAO → PAO May 23, 16:50 UTCMay 23, 16:55 UTC5m
2026-05-23 N501SC PAO → PAO May 23, 16:00 UTCMay 23, 16:45 UTC45m
2026-05-21 N501SC HWD → PAO May 21, 17:40 UTCMay 21, 18:10 UTC30m
2026-05-21 N501SC HWD → HWD May 21, 16:55 UTCMay 21, 17:30 UTC35m
2026-05-21 N501SC PAO → HWD May 21, 16:40 UTCMay 21, 16:50 UTC10m
2026-05-20 N501SC PAO → PAO May 20, 19:50 UTCMay 20, 20:45 UTC55m
2026-05-20 N501SC PAO → PAO May 20, 16:50 UTCMay 20, 18:10 UTC1h 20m
2026-05-19 N501SC PAO → PAO May 19, 17:00 UTCMay 19, 17:05 UTC5m
2026-05-19 N501SC PAO → PAO May 19, 16:45 UTCMay 19, 16:55 UTC10m
2026-05-19 N501SC PAO → PAO May 19, 16:30 UTCMay 19, 16:40 UTC10m
2026-05-19 N501SC PAO → PAO May 19, 16:20 UTCMay 19, 16:25 UTC5m
2026-05-16 N501SC PAO → PAO May 16, 17:20 UTCMay 16, 18:25 UTC1h 5m
2026-05-15 N501SC PAO → PAO May 15, 21:15 UTCMay 15, 22:05 UTC50m
2026-05-15 N501SC PAO → PAO May 15, 19:10 UTCMay 15, 20:00 UTC50m
2026-05-15 N501SC PAO → PAO May 15, 15:45 UTCMay 15, 16:35 UTC50m
2026-05-14 N501SC PAO → PAO May 14, 23:10 UTCMay 15, 00:05 UTC55m
2026-05-14 N501SC PAO → PAO May 14, 19:10 UTCMay 14, 19:55 UTC45m
2026-05-14 N501SC SQL → PAO May 14, 17:55 UTCMay 14, 18:10 UTC15m
2026-05-14 N501SC PAO → SQL May 14, 17:15 UTCMay 14, 17:50 UTC35m
2026-05-01 N501SC PAO → PAO May 1, 19:00 UTCMay 1, 19:55 UTC55m
2026-04-30 N501SC - Apr 30, 23:10 UTCMay 1, 00:25 UTC1h 15m
2026-04-30 N501SC - Apr 30, 21:15 UTCApr 30, 22:30 UTC1h 15m
2026-04-30 N501SC - Apr 30, 17:10 UTCApr 30, 18:25 UTC1h 15m
2026-04-30 N501SC PAO → PAO Apr 30, 16:55 UTCApr 30, 17:05 UTC10m
2026-04-29 N501SC PAO → PAO Apr 29, 22:55 UTCApr 29, 23:35 UTC39m

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 2d 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.