Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AC9F65

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N912PG · HUGHES 500 · operated by PRINCE GEORGES COUNTY POLICE DEPARTMENT

Hex
AC9F65
Octal
53117545
Decimal
11,312,997
Country
US
Tail
N912PG
Type
H500
No current signal · last broadcast 5h ago
Flights observed
49
Distinct callsigns
1
Country
US
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S AC9F65.

Country allocation

The ICAO 24-bit address AC9F65 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
GARDN2 - 49 2026-07-14

Recent flights last 49

DateFlightRouteTakeoffLandingDuration
2026-07-14 GARDN2 CGS → CGS Jul 14, 15:45 UTCJul 14, 16:00 UTC15m
2026-07-14 GARDN2 CGS → CGS Jul 14, 15:10 UTCJul 14, 15:35 UTC25m
2026-07-14 GARDN2 CGS → CGS Jul 14, 14:40 UTCJul 14, 15:05 UTC25m
2026-07-14 GARDN2 - Jul 14, 04:00 UTCJul 14, 05:15 UTC1h 15m
2026-07-14 GARDN2 - Jul 14, 02:40 UTCJul 14, 03:10 UTC30m
2026-07-13 GARDN2 - Jul 13, 22:05 UTCJul 13, 23:20 UTC1h 15m
2026-07-12 GARDN2 CGS → CGS Jul 12, 03:35 UTCJul 12, 05:01 UTC1h 25m
2026-07-12 GARDN2 - Jul 12, 00:25 UTCJul 12, 00:40 UTC15m
2026-07-11 GARDN2 CGS → CGS Jul 11, 21:55 UTCJul 11, 23:20 UTC1h 25m
2026-07-11 GARDN2 CGS → CGS Jul 11, 20:45 UTCJul 11, 21:10 UTC25m
2026-07-11 GARDN2 - Jul 11, 03:25 UTCJul 11, 04:50 UTC1h 25m
2026-07-10 GARDN2 CGS → CGS Jul 10, 21:55 UTCJul 10, 23:00 UTC1h 5m
2026-07-10 GARDN2 CGS → CGS Jul 10, 20:50 UTCJul 10, 21:10 UTC20m
2026-07-10 GARDN2 CGS → CGS Jul 10, 17:55 UTCJul 10, 18:25 UTC30m
2026-07-10 GARDN2 CGS → CGS Jul 10, 05:40 UTCJul 10, 06:00 UTC20m
2026-07-10 GARDN2 CGS → CGS Jul 10, 02:45 UTCJul 10, 04:40 UTC1h 55m
2026-07-09 GARDN2 CGS → CGS Jul 9, 03:10 UTCJul 9, 03:40 UTC30m
2026-07-09 GARDN2 CGS → CGS Jul 9, 01:05 UTCJul 9, 02:00 UTC55m
2026-07-08 GARDN2 CGS → CGS Jul 8, 03:00 UTCJul 8, 03:30 UTC30m
2026-07-07 GARDN2 CGS → CGS Jul 7, 22:40 UTCJul 7, 23:20 UTC40m
2026-07-03 GARDN2 CGS → CGS Jul 3, 02:50 UTCJul 3, 03:10 UTC20m
2026-07-02 GARDN2 CGS → CGS Jul 2, 23:10 UTCJul 3, 00:00 UTC50m
2026-07-02 GARDN2 CGS → CGS Jul 2, 15:25 UTCJul 2, 15:30 UTC5m
2026-07-01 GARDN2 CGS → CGS Jul 1, 22:25 UTCJul 1, 23:15 UTC50m
2026-07-01 GARDN2 - Jul 1, 01:10 UTCJul 1, 01:50 UTC40m
2026-06-30 GARDN2 CGS → CGS Jun 30, 19:50 UTCJun 30, 20:00 UTC10m
2026-06-29 GARDN2 ADW → CGS Jun 29, 22:49 UTCJun 29, 23:09 UTC20m
2026-06-29 GARDN2 - Jun 29, 21:54 UTCJun 29, 22:19 UTC25m
2026-06-24 GARDN2 CGS → CGS Jun 24, 15:35 UTCJun 24, 16:24 UTC50m
2026-06-24 GARDN2 CGS → CGS Jun 24, 00:59 UTCJun 24, 02:00 UTC1h 0m
2026-06-23 GARDN2 CGS → CGS Jun 23, 20:19 UTCJun 23, 20:24 UTC5m
2026-06-23 GARDN2 - Jun 23, 03:54 UTCJun 23, 04:19 UTC25m
2026-06-23 GARDN2 CGS → CGS Jun 23, 02:40 UTCJun 23, 03:49 UTC1h 10m
2026-06-22 GARDN2 CGS → CGS Jun 22, 19:09 UTCJun 22, 19:40 UTC30m
2026-06-22 GARDN2 CGS → CGS Jun 22, 15:59 UTCJun 22, 16:10 UTC10m
2026-06-22 GARDN2 CGS → CGS Jun 22, 15:35 UTCJun 22, 15:45 UTC10m
2026-06-08 GARDN2 CGS → CGS Jun 8, 18:35 UTCJun 8, 18:40 UTC5m
2026-06-08 GARDN2 CGS → CGS Jun 8, 18:10 UTCJun 8, 18:15 UTC5m
2026-06-08 GARDN2 CGS → CGS Jun 8, 17:45 UTCJun 8, 18:00 UTC15m
2026-06-08 GARDN2 CGS → CGS Jun 8, 17:25 UTCJun 8, 17:30 UTC5m
2026-06-01 GARDN2 CGS → CGS Jun 1, 19:20 UTCJun 1, 19:25 UTC5m
2026-06-01 GARDN2 CGS → CGS Jun 1, 19:00 UTCJun 1, 19:05 UTC5m
2026-06-01 GARDN2 CGS → CGS Jun 1, 17:40 UTCJun 1, 17:45 UTC5m
2026-06-01 GARDN2 CGS → CGS Jun 1, 16:35 UTCJun 1, 16:40 UTC5m
2026-05-29 GARDN2 CGS → CGS May 29, 21:20 UTCMay 29, 21:25 UTC5m
2026-04-21 GARDN2 CGS → CGS Apr 21, 14:55 UTCApr 21, 15:01 UTC5m
2026-04-21 GARDN2 CGS → CGS Apr 21, 14:35 UTCApr 21, 14:40 UTC5m
2026-04-16 GARDN2 CGS → CGS Apr 16, 18:35 UTCApr 16, 18:40 UTC5m
2026-04-16 GARDN2 CGS → CGS Apr 16, 18:10 UTCApr 16, 18:30 UTC20m

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

Mode-S AC9F65 frequently asked

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