Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AC9A70

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N911AP · BELL 407 · operated by ANNE ARUNDEL COUNTY MARYLAND

Hex
AC9A70
Octal
53115160
Decimal
11,311,728
Country
US
Tail
N911AP
Type
B407
No current signal · last broadcast 12d ago
Flights observed
99
Distinct callsigns
1
Country
US
Last broadcast
12d ago

Last known position

Most recent position reported by Mode-S AC9A70.

Country allocation

The ICAO 24-bit address AC9A70 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
N911AP - 99 2026-07-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-11 N911AP FME → FME Jul 11, 19:35 UTCJul 11, 20:10 UTC35m
2026-07-10 N911AP - Jul 10, 16:40 UTCJul 10, 17:40 UTC1h 0m
2026-07-10 N911AP - Jul 10, 13:55 UTCJul 10, 14:05 UTC10m
2026-07-09 N911AP FME → FME Jul 9, 01:00 UTCJul 9, 03:05 UTC2h 5m
2026-07-08 N911AP - Jul 8, 20:25 UTCJul 8, 21:25 UTC1h 0m
2026-07-06 N911AP FME → FME Jul 6, 23:10 UTCJul 7, 00:00 UTC50m
2026-07-02 N911AP FME → FME Jul 2, 23:45 UTCJul 3, 01:10 UTC1h 25m
2026-07-02 N911AP - Jul 2, 21:40 UTCJul 2, 22:45 UTC1h 5m
2026-07-01 N911AP - Jul 1, 21:40 UTCJul 1, 22:55 UTC1h 15m
2026-06-30 N911AP - Jun 30, 15:25 UTCJun 30, 16:50 UTC1h 25m
2026-06-29 N911AP - Jun 29, 02:54 UTCJun 29, 03:20 UTC25m
2026-06-27 N911AP - Jun 27, 23:34 UTCJun 27, 23:45 UTC10m
2026-06-27 N911AP FME → FME Jun 27, 19:00 UTCJun 27, 20:59 UTC2h 0m
2026-06-26 N911AP - Jun 26, 00:05 UTCJun 26, 00:59 UTC55m
2026-06-25 N911AP - Jun 25, 19:15 UTCJun 25, 22:24 UTC3h 10m
2026-06-24 N911AP - Jun 24, 21:14 UTCJun 24, 23:14 UTC2h 0m
2026-06-24 N911AP - Jun 24, 20:24 UTCJun 24, 20:35 UTC10m
2026-06-21 N911AP - Jun 21, 03:00 UTCJun 21, 07:55 UTC4h 55m
2026-06-20 N911AP - Jun 20, 15:49 UTCJun 20, 17:59 UTC2h 10m
2026-06-20 N911AP - Jun 20, 01:39 UTCJun 20, 03:04 UTC1h 25m
2026-06-19 N911AP - Jun 19, 22:24 UTCJun 19, 23:19 UTC55m
2026-06-19 N911AP - Jun 19, 18:39 UTCJun 19, 19:25 UTC45m
2026-06-19 N911AP - Jun 19, 04:54 UTCJun 19, 05:05 UTC10m
2026-06-18 N911AP FME → FME Jun 18, 19:00 UTCJun 18, 19:30 UTC30m
2026-06-18 N911AP - Jun 18, 01:35 UTCJun 18, 01:55 UTC20m
2026-06-17 N911AP - Jun 17, 01:00 UTCJun 17, 02:25 UTC1h 25m
2026-06-16 N911AP - Jun 16, 22:40 UTCJun 16, 23:15 UTC35m
2026-06-16 N911AP - Jun 16, 21:00 UTCJun 16, 22:10 UTC1h 10m
2026-06-16 N911AP - Jun 16, 03:04 UTCJun 16, 04:35 UTC1h 30m
2026-06-15 N911AP - Jun 15, 23:45 UTCJun 16, 00:40 UTC55m
2026-06-15 N911AP - Jun 15, 20:34 UTCJun 15, 21:55 UTC1h 20m
2026-06-14 N911AP - Jun 14, 11:30 UTCJun 14, 13:55 UTC2h 25m
2026-06-13 N911AP - Jun 13, 19:25 UTCJun 13, 21:00 UTC1h 35m
2026-06-12 N911AP - Jun 12, 17:50 UTCJun 12, 20:00 UTC2h 10m
2026-06-11 N911AP FME → FME Jun 11, 19:10 UTCJun 11, 21:45 UTC2h 35m
2026-06-10 N911AP FME → FME Jun 10, 23:00 UTCJun 11, 00:55 UTC1h 55m
2026-06-09 N911AP - Jun 9, 22:20 UTCJun 9, 23:05 UTC45m
2026-06-09 N911AP - Jun 9, 20:30 UTCJun 9, 21:40 UTC1h 10m
2026-06-08 N911AP - Jun 8, 20:20 UTCJun 8, 22:00 UTC1h 40m
2026-06-07 N911AP FME → FME Jun 7, 23:05 UTCJun 8, 00:40 UTC1h 35m
2026-06-06 N911AP FME → FME Jun 6, 20:25 UTCJun 6, 21:50 UTC1h 25m
2026-06-06 N911AP - Jun 6, 02:30 UTCJun 6, 04:25 UTC1h 55m
2026-06-05 N911AP FME → FME Jun 5, 20:30 UTCJun 5, 22:25 UTC1h 55m
2026-06-04 N911AP - Jun 4, 18:35 UTCJun 4, 19:35 UTC1h 0m
2026-06-04 N911AP - Jun 4, 01:55 UTCJun 4, 02:15 UTC20m
2026-06-03 N911AP - Jun 3, 22:35 UTCJun 3, 23:40 UTC1h 5m
2026-06-03 N911AP - Jun 3, 20:40 UTCJun 3, 21:00 UTC20m
2026-06-03 N911AP - Jun 3, 01:10 UTCJun 3, 02:50 UTC1h 40m
2026-06-02 N911AP FME → FME Jun 2, 20:10 UTCJun 2, 21:20 UTC1h 10m
2026-06-01 N911AP - Jun 1, 20:45 UTCJun 1, 22:40 UTC1h 55m

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

Mode-S AC9A70 frequently asked

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