Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AC916E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N909JL · PIPER PA-28-140/150/160/180 · operated by AIMS COMMUNITY COLLEGE

Hex
AC916E
Octal
53110556
Decimal
11,309,422
Country
US
Tail
N909JL
Type
P28A
Transponder active on ground
Flights observed
148
Distinct callsigns
1
Country
US
Last broadcast
18h ago

Last known position

Most recent position reported by Mode-S AC916E.

Country allocation

The ICAO 24-bit address AC916E 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
RTY909 - 148 2026-06-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-04 RTY909 FNL → FNL Jun 4, 19:45 UTCJun 4, 20:15 UTC30m
2026-06-04 RTY909 FNL → FNL Jun 4, 17:35 UTCJun 4, 18:35 UTC1h 0m
2026-06-03 RTY909 FNL → FNL Jun 3, 16:55 UTCJun 3, 18:00 UTC1h 5m
2026-06-03 RTY909 FNL → FNL Jun 3, 14:15 UTCJun 3, 15:30 UTC1h 15m
2026-05-31 RTY909 FNL → FNL May 31, 19:05 UTCMay 31, 20:35 UTC1h 30m
2026-05-31 RTY909 FNL → FNL May 31, 16:45 UTCMay 31, 17:40 UTC55m
2026-05-30 RTY909 FNL → FNL May 30, 17:20 UTCMay 30, 18:15 UTC55m
2026-05-28 RTY909 FNL → FNL May 28, 20:20 UTCMay 28, 21:25 UTC1h 5m
2026-05-27 RTY909 FNL → FNL May 27, 17:50 UTCMay 27, 18:05 UTC15m
2026-05-27 RTY909 FNL → FNL May 27, 14:30 UTCMay 27, 15:10 UTC40m
2026-05-24 RTY909 FNL → FNL May 24, 17:55 UTCMay 24, 19:15 UTC1h 20m
2026-05-23 RTY909 FNL → FNL May 23, 21:40 UTCMay 23, 23:05 UTC1h 25m
2026-05-23 RTY909 FNL → FNL May 23, 20:10 UTCMay 23, 20:35 UTC25m
2026-05-23 RTY909 FNL → FNL May 23, 17:55 UTCMay 23, 18:55 UTC1h 0m
2026-05-23 RTY909 FNL → FNL May 23, 15:15 UTCMay 23, 16:25 UTC1h 10m
2026-05-23 RTY909 FNL → FNL May 23, 13:15 UTCMay 23, 14:05 UTC50m
2026-05-22 RTY909 - May 22, 20:40 UTCMay 22, 21:10 UTC30m
2026-05-22 RTY909 - May 22, 19:30 UTCMay 22, 19:45 UTC15m
2026-05-22 RTY909 - May 22, 18:25 UTCMay 22, 18:35 UTC10m
2026-05-22 RTY909 - May 22, 16:45 UTCMay 22, 17:30 UTC45m
2026-05-21 RTY909 FNL → FNL May 21, 17:05 UTCMay 21, 18:05 UTC1h 0m
2026-05-20 RTY909 FNL → FNL May 20, 14:50 UTCMay 20, 15:30 UTC40m
2026-05-19 RTY909 FNL → FNL May 19, 22:35 UTCMay 19, 23:25 UTC50m
2026-05-19 RTY909 FNL → FNL May 19, 17:30 UTCMay 19, 18:35 UTC1h 5m
2026-05-15 RTY909 FNL → FNL May 15, 16:45 UTCMay 15, 17:50 UTC1h 5m
2026-05-15 RTY909 FNL → FNL May 15, 14:35 UTCMay 15, 15:15 UTC39m
2026-05-15 RTY909 FNL → FNL May 15, 12:05 UTCMay 15, 13:15 UTC1h 10m
2026-05-15 RTY909 FNL → FNL May 15, 00:00 UTCMay 15, 01:15 UTC1h 15m
2026-05-14 RTY909 FNL → FNL May 14, 17:30 UTCMay 14, 18:15 UTC45m
2026-05-14 RTY909 FNL → FNL May 14, 00:15 UTCMay 14, 01:50 UTC1h 35m
2026-05-13 RTY909 FNL → FNL May 13, 21:45 UTCMay 13, 22:55 UTC1h 10m
2026-05-13 RTY909 FNL → FNL May 13, 19:20 UTCMay 13, 20:30 UTC1h 10m
2026-05-13 RTY909 FNL → FNL May 13, 17:10 UTCMay 13, 17:45 UTC35m
2026-05-13 RTY909 FNL → FNL May 13, 11:15 UTCMay 13, 12:55 UTC1h 40m
2026-05-13 RTY909 FNL → FNL May 13, 02:50 UTCMay 13, 04:10 UTC1h 20m
2026-05-13 RTY909 FNL → FNL May 13, 00:10 UTCMay 13, 01:35 UTC1h 25m
2026-05-12 RTY909 FNL → FNL May 12, 21:40 UTCMay 12, 22:50 UTC1h 10m
2026-05-12 RTY909 PUB → FNL May 12, 18:15 UTCMay 12, 20:30 UTC2h 15m
2026-05-12 RTY909 FNL → PUB May 12, 15:25 UTCMay 12, 17:15 UTC1h 50m
2026-05-12 RTY909 FNL → FNL May 12, 11:40 UTCMay 12, 13:20 UTC1h 40m
2026-05-12 RTY909 FNL → FNL May 12, 03:15 UTCMay 12, 06:00 UTC2h 45m
2026-05-11 RTY909 FNL → FNL May 11, 20:20 UTCMay 11, 20:55 UTC35m
2026-05-11 RTY909 FNL → FNL May 11, 17:25 UTCMay 11, 18:15 UTC50m
2026-05-11 RTY909 FNL → FNL May 11, 14:15 UTCMay 11, 15:55 UTC1h 40m
2026-05-11 RTY909 FNL → FNL May 11, 11:40 UTCMay 11, 13:05 UTC1h 25m
2026-05-11 RTY909 - May 11, 02:40 UTCMay 11, 04:10 UTC1h 30m
2026-05-11 RTY909 FNL → PUB May 11, 00:19 UTCMay 11, 01:50 UTC1h 30m
2026-05-09 RTY909 FNL → FNL May 9, 15:05 UTCMay 9, 16:40 UTC1h 35m
2026-05-09 RTY909 FNL → FNL May 9, 12:30 UTCMay 9, 13:50 UTC1h 20m
2026-05-09 RTY909 FNL → FNL May 9, 02:45 UTCMay 9, 04:45 UTC2h 0m

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

Mode-S AC916E frequently asked

What is Mode-S code AC916E?
AC916E is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N909JL.
Where is Mode-S AC916E registered?
Mode-S code AC916E 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 AC916E broadcasting right now?
Mode-S AC916E is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AC916E, octal 53110556, decimal 11,309,422.
What flights does AC916E operate?
Mode-S AC916E has broadcast 1 distinct callsign, including RTY909.