Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A5A764

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N4632F · PIPER PA-28-140/150/160/180 · operated by G & M AIRCRAFT INC

Hex
A5A764
Octal
51323544
Decimal
10,856,292
Country
US
Tail
N4632F
Type
P28A
Broadcasting now · callsign N4632F · 9,200 ft
Flights observed
229
Distinct callsigns
1
Country
US
Last broadcast
Jul 26, 19:20 UTC

Current position

A5A764 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A5A764 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
N4632F - 229 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 N4632F BJC → BJC Jul 26, 18:15 UTCJul 26, 19:20 UTC1h 5m
2026-07-26 N4632F - Jul 26, 04:55 UTCJul 26, 06:00 UTC1h 5m
2026-07-26 N4632F - Jul 26, 00:35 UTCJul 26, 01:20 UTC45m
2026-07-25 N4632F - Jul 25, 17:25 UTCJul 25, 18:55 UTC1h 30m
2026-07-25 N4632F BJC → BJC Jul 25, 14:00 UTCJul 25, 16:05 UTC2h 5m
2026-07-24 N4632F BJC → BJC Jul 24, 19:55 UTCJul 24, 20:45 UTC50m
2026-07-24 N4632F BJC → BJC Jul 24, 17:55 UTCJul 24, 18:20 UTC25m
2026-07-24 N4632F BJC → BJC Jul 24, 14:20 UTCJul 24, 17:00 UTC2h 40m
2026-07-22 N4632F BJC → BJC Jul 22, 15:10 UTCJul 22, 16:30 UTC1h 20m
2026-07-22 N4632F - Jul 22, 12:45 UTCJul 22, 13:50 UTC1h 5m
2026-07-21 N4632F - Jul 21, 14:40 UTCJul 21, 16:30 UTC1h 50m
2026-07-21 N4632F BJC → BJC Jul 21, 12:10 UTCJul 21, 13:35 UTC1h 25m
2026-07-20 N4632F BJC → BJC Jul 20, 13:55 UTCJul 20, 14:40 UTC45m
2026-07-19 N4632F - Jul 19, 18:00 UTCJul 19, 18:45 UTC45m
2026-07-18 N4632F - Jul 18, 14:55 UTCJul 18, 16:10 UTC1h 15m
2026-07-17 N4632F - Jul 17, 19:35 UTCJul 17, 20:04 UTC30m
2026-07-17 N4632F GXY → GXY Jul 17, 18:25 UTCJul 17, 18:44 UTC20m
2026-07-17 N4632F - Jul 17, 17:25 UTCJul 17, 17:44 UTC20m
2026-07-17 N4632F - Jul 17, 15:44 UTCJul 17, 16:49 UTC1h 5m
2026-07-17 N4632F GXY → GXY Jul 17, 14:04 UTCJul 17, 14:24 UTC20m
2026-07-17 N4632F BJC → GXY Jul 17, 12:50 UTCJul 17, 13:15 UTC25m
2026-07-16 N4632F BJC → BJC Jul 16, 14:50 UTCJul 16, 16:44 UTC1h 55m
2026-07-16 N4632F BJC → BJC Jul 16, 12:05 UTCJul 16, 13:54 UTC1h 50m
2026-07-15 N4632F - Jul 15, 15:45 UTCJul 15, 16:30 UTC45m
2026-07-15 N4632F BJC → BJC Jul 15, 12:45 UTCJul 15, 13:40 UTC55m
2026-07-15 N4632F BJC → BJC Jul 15, 01:45 UTCJul 15, 03:45 UTC2h 0m
2026-07-14 N4632F BJC → BJC Jul 14, 18:00 UTCJul 14, 19:20 UTC1h 20m
2026-07-14 N4632F - Jul 14, 15:15 UTCJul 14, 16:45 UTC1h 30m
2026-07-14 N4632F BJC → BJC Jul 14, 12:05 UTCJul 14, 13:40 UTC1h 35m
2026-07-13 N4632F - Jul 13, 19:15 UTCJul 13, 20:45 UTC1h 30m
2026-07-13 N4632F - Jul 13, 16:55 UTCJul 13, 17:40 UTC45m
2026-07-13 N4632F BJC → BJC Jul 13, 14:55 UTCJul 13, 15:45 UTC50m
2026-07-13 N4632F BJC → BJC Jul 13, 12:00 UTCJul 13, 13:40 UTC1h 40m
2026-07-13 N4632F - Jul 13, 04:00 UTCJul 13, 05:10 UTC1h 10m
2026-07-13 N4632F - Jul 13, 01:45 UTCJul 13, 02:40 UTC55m
2026-07-12 N4632F GXY → BJC Jul 12, 17:20 UTCJul 12, 18:01 UTC40m
2026-07-12 N4632F BJC → GXY Jul 12, 16:05 UTCJul 12, 16:40 UTC35m
2026-07-12 N4632F BJC → BJC Jul 12, 13:45 UTCJul 12, 15:05 UTC1h 20m
2026-07-11 N4632F - Jul 11, 20:40 UTCJul 11, 21:40 UTC1h 0m
2026-07-11 N4632F BJC → PUB Jul 11, 17:30 UTCJul 11, 18:35 UTC1h 5m
2026-07-11 N4632F BJC → BJC Jul 11, 12:00 UTCJul 11, 13:35 UTC1h 35m
2026-07-10 N4632F BJC → BJC Jul 10, 17:45 UTCJul 10, 19:25 UTC1h 40m
2026-07-10 N4632F BJC → BJC Jul 10, 12:40 UTCJul 10, 14:00 UTC1h 20m
2026-07-09 N4632F BJC → BJC Jul 9, 15:25 UTCJul 9, 16:40 UTC1h 15m
2026-07-09 N4632F BJC → BJC Jul 9, 11:55 UTCJul 9, 13:40 UTC1h 45m
2026-07-08 N4632F - Jul 8, 17:05 UTCJul 8, 17:30 UTC25m
2026-07-08 N4632F - Jul 8, 13:55 UTCJul 8, 14:30 UTC35m
2026-07-08 N4632F BJC → BJC Jul 8, 11:30 UTCJul 8, 12:40 UTC1h 10m
2026-07-07 N4632F BJC → BJC Jul 7, 18:45 UTCJul 7, 19:35 UTC50m
2026-07-07 N4632F - Jul 7, 15:00 UTCJul 7, 16:40 UTC1h 40m

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

Mode-S A5A764 frequently asked

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