sensors Mode-S transponder

AC76B2

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N902AZ · CESSNA 172 Skyhawk · operated by SANTIAGO FELIPE

Hex
AC76B2
Octal
53073262
Decimal
11,302,578
Country
US
Tail
N902AZ
Type
C172
No current signal · last broadcast Jul 26, 22:30 UTC
Flights observed
191
Distinct callsigns
1
Country
US
Last broadcast
Jul 26, 22:30 UTC

Last known position

Most recent position reported by Mode-S AC76B2.

Country allocation

The ICAO 24-bit address AC76B2 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
OZN902 - 191 2026-07-26

Recent flights last 50

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

Mode-S AC76B2 frequently asked

What is Mode-S code AC76B2?
AC76B2 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N902AZ.
Where is Mode-S AC76B2 registered?
Mode-S code AC76B2 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 AC76B2 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 22:30 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AC76B2, octal 53073262, decimal 11,302,578.
What flights does AC76B2 operate?
Mode-S AC76B2 has broadcast 1 distinct callsign, including OZN902.