Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AC9BAE

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N911PG · HUGHES 500 · operated by PRINCE GEORGES COUNTY

Hex
AC9BAE
Octal
53115656
Decimal
11,312,046
Country
US
Tail
N911PG
Type
H500
No current signal · last broadcast 2d ago
Flights observed
79
Distinct callsigns
1
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S AC9BAE.

Country allocation

The ICAO 24-bit address AC9BAE 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
GARDN1 - 79 2026-05-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-27 GARDN1 CGS → CGS May 27, 19:15 UTCMay 27, 19:20 UTC5m
2026-05-27 GARDN1 CGS → CGS May 27, 19:00 UTCMay 27, 19:10 UTC10m
2026-05-27 GARDN1 CGS → CGS May 27, 18:20 UTCMay 27, 18:45 UTC25m
2026-05-27 GARDN1 CGS → CGS May 27, 18:05 UTCMay 27, 18:15 UTC10m
2026-05-27 GARDN1 - May 27, 01:49 UTCMay 27, 02:19 UTC30m
2026-05-26 GARDN1 CGS → CGS May 26, 17:09 UTCMay 26, 17:39 UTC30m
2026-05-25 GARDN1 CGS → CGS May 25, 21:35 UTCMay 25, 21:54 UTC20m
2026-05-25 GARDN1 - May 25, 19:50 UTCMay 25, 20:40 UTC50m
2026-05-21 GARDN1 - May 21, 23:05 UTCMay 21, 23:30 UTC25m
2026-05-20 GARDN1 CGS → CGS May 20, 17:50 UTCMay 20, 18:25 UTC35m
2026-05-18 GARDN1 - May 18, 23:05 UTCMay 18, 23:20 UTC15m
2026-05-18 GARDN1 - May 18, 22:05 UTCMay 18, 23:00 UTC55m
2026-05-18 GARDN1 CGS → CGS May 18, 20:20 UTCMay 18, 21:35 UTC1h 15m
2026-05-18 GARDN1 CGS → CGS May 18, 18:05 UTCMay 18, 18:20 UTC15m
2026-05-17 GARDN1 CGS → CGS May 17, 21:50 UTCMay 17, 22:45 UTC55m
2026-05-16 GARDN1 - May 16, 23:25 UTCMay 16, 23:40 UTC15m
2026-05-16 GARDN1 CGS → CGS May 16, 22:15 UTCMay 16, 22:40 UTC25m
2026-05-16 GARDN1 CGS → CGS May 16, 02:20 UTCMay 16, 02:50 UTC30m
2026-05-15 GARDN1 CGS → CGS May 15, 23:25 UTCMay 16, 00:00 UTC35m
2026-05-15 GARDN1 CGS → CGS May 15, 19:50 UTCMay 15, 20:15 UTC25m
2026-05-13 GARDN1 CGS → CGS May 13, 21:30 UTCMay 13, 22:00 UTC30m
2026-05-13 GARDN1 CGS → CGS May 13, 20:40 UTCMay 13, 20:50 UTC10m
2026-05-13 GARDN1 - May 13, 19:40 UTCMay 13, 19:50 UTC10m
2026-05-12 GARDN1 CGS → CGS May 12, 14:15 UTCMay 12, 15:01 UTC45m
2026-05-12 GARDN1 CGS → CGS May 12, 02:50 UTCMay 12, 03:05 UTC15m
2026-05-09 GARDN1 CGS → CGS May 9, 02:40 UTCMay 9, 03:25 UTC45m
2026-05-07 GARDN1 CGS → CGS May 7, 22:54 UTCMay 7, 23:05 UTC10m
2026-05-07 GARDN1 CGS → CGS May 7, 03:25 UTCMay 7, 04:25 UTC1h 0m
2026-05-07 GARDN1 - May 7, 00:25 UTCMay 7, 00:45 UTC20m
2026-05-06 GARDN1 - May 6, 01:55 UTCMay 6, 03:25 UTC1h 30m
2026-05-05 GARDN1 CGS → CGS May 5, 18:35 UTCMay 5, 19:20 UTC45m
2026-05-05 GARDN1 CGS → CGS May 5, 15:01 UTCMay 5, 15:50 UTC50m
2026-05-04 GARDN1 CGS → CGS May 4, 20:35 UTCMay 4, 21:10 UTC35m
2026-05-04 GARDN1 CGS → CGS May 4, 03:54 UTCMay 4, 04:15 UTC20m
2026-05-03 GARDN1 CGS → CGS May 3, 03:10 UTCMay 3, 04:00 UTC49m
2026-05-01 GARDN1 CGS → CGS May 1, 22:50 UTCMay 1, 23:25 UTC35m
2026-04-30 GARDN1 CGS → CGS Apr 30, 21:45 UTCApr 30, 22:35 UTC50m
2026-04-30 GARDN1 CGS → CGS Apr 30, 14:45 UTCApr 30, 15:00 UTC15m
2026-04-29 GARDN1 CGS → CGS Apr 29, 14:35 UTCApr 29, 14:50 UTC15m
2026-04-29 GARDN1 CGS → CGS Apr 29, 13:45 UTCApr 29, 14:30 UTC45m
2026-04-29 GARDN1 CGS → CGS Apr 29, 13:25 UTCApr 29, 13:40 UTC15m
2026-04-28 GARDN1 CGS → CGS Apr 28, 15:50 UTCApr 28, 16:25 UTC35m
2026-04-28 GARDN1 CGS → CGS Apr 28, 03:25 UTCApr 28, 04:50 UTC1h 25m
2026-04-27 GARDN1 CGS → CGS Apr 27, 23:05 UTCApr 27, 23:55 UTC50m
2026-04-27 GARDN1 CGS → CGS Apr 27, 00:40 UTCApr 27, 01:10 UTC30m
2026-04-24 GARDN1 - Apr 24, 18:15 UTCApr 24, 18:25 UTC10m
2026-04-24 GARDN1 - Apr 24, 16:35 UTCApr 24, 17:05 UTC30m
2026-04-24 GARDN1 CGS → CGS Apr 24, 13:25 UTCApr 24, 14:40 UTC1h 15m
2026-04-24 GARDN1 CGS → CGS Apr 24, 13:10 UTCApr 24, 13:15 UTC5m
2026-04-24 GARDN1 CGS → CGS Apr 24, 02:15 UTCApr 24, 03:20 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 N911PG page for operator, model, and routing details .

Mode-S AC9BAE frequently asked

What is Mode-S code AC9BAE?
AC9BAE is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N911PG.
Where is Mode-S AC9BAE registered?
Mode-S code AC9BAE 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 AC9BAE 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 AC9BAE, octal 53115656, decimal 11,312,046.
What flights does AC9BAE operate?
Mode-S AC9BAE has broadcast 1 distinct callsign, including GARDN1.