Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ACAE33

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N916NT · CESSNA 172 Skyhawk · operated by 9K AIR LLC

Hex
ACAE33
Octal
53127063
Decimal
11,316,787
Country
US
Tail
N916NT
Type
C172
Transponder active on ground
Flights observed
211
Distinct callsigns
1
Country
US
Last broadcast
15h ago

Last known position

Most recent position reported by Mode-S ACAE33.

Country allocation

The ICAO 24-bit address ACAE33 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
N916NT - 211 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 N916NT BFL → BFL Jul 13, 23:35 UTCJul 14, 00:30 UTC55m
2026-07-13 N916NT - Jul 13, 17:35 UTCJul 13, 20:00 UTC2h 25m
2026-07-13 N916NT - Jul 13, 14:15 UTCJul 13, 16:45 UTC2h 30m
2026-07-13 N916NT BFL → BFL Jul 13, 01:05 UTCJul 13, 02:15 UTC1h 10m
2026-07-11 N916NT BFL → BFL Jul 11, 19:45 UTCJul 11, 20:55 UTC1h 10m
2026-07-10 N916NT BFL → BFL Jul 10, 20:35 UTCJul 10, 21:20 UTC45m
2026-07-10 N916NT BFL → BFL Jul 10, 18:15 UTCJul 10, 19:05 UTC50m
2026-07-10 N916NT BFL → BFL Jul 10, 15:50 UTCJul 10, 16:55 UTC1h 5m
2026-07-10 N916NT BFL → BFL Jul 10, 13:45 UTCJul 10, 14:50 UTC1h 5m
2026-07-09 N916NT BFL → BFL Jul 9, 18:35 UTCJul 9, 19:45 UTC1h 10m
2026-07-09 N916NT BFL → BFL Jul 9, 16:00 UTCJul 9, 17:30 UTC1h 30m
2026-07-09 N916NT BFL → BFL Jul 9, 14:15 UTCJul 9, 15:20 UTC1h 5m
2026-07-08 N916NT BFL → BFL Jul 8, 23:10 UTCJul 9, 00:20 UTC1h 10m
2026-07-08 N916NT BFL → BFL Jul 8, 20:40 UTCJul 8, 21:05 UTC25m
2026-07-08 N916NT BFL → BFL Jul 8, 18:15 UTCJul 8, 19:10 UTC55m
2026-07-08 N916NT BFL → BFL Jul 8, 16:10 UTCJul 8, 16:40 UTC30m
2026-07-08 N916NT BFL → BFL Jul 8, 14:00 UTCJul 8, 14:55 UTC55m
2026-07-08 N916NT BFL → BFL Jul 8, 03:55 UTCJul 8, 05:25 UTC1h 30m
2026-07-08 N916NT - Jul 8, 01:30 UTCJul 8, 02:10 UTC40m
2026-07-07 N916NT BFL → BFL Jul 7, 22:25 UTCJul 8, 00:00 UTC1h 35m
2026-07-07 N916NT BFL → BFL Jul 7, 18:35 UTCJul 7, 19:45 UTC1h 10m
2026-07-07 N916NT BFL → BFL Jul 7, 14:15 UTCJul 7, 15:25 UTC1h 10m
2026-07-06 N916NT BFL → BFL Jul 6, 23:15 UTCJul 6, 23:55 UTC40m
2026-07-06 N916NT BFL → BFL Jul 6, 21:00 UTCJul 6, 21:45 UTC45m
2026-07-06 N916NT BFL → BFL Jul 6, 18:35 UTCJul 6, 19:30 UTC55m
2026-07-06 N916NT BFL → BFL Jul 6, 16:15 UTCJul 6, 17:25 UTC1h 10m
2026-07-02 N916NT BFL → BFL Jul 2, 18:55 UTCJul 2, 19:50 UTC55m
2026-07-02 N916NT BFL → BFL Jul 2, 15:55 UTCJul 2, 16:45 UTC50m
2026-07-02 N916NT BFL → BFL Jul 2, 14:00 UTCJul 2, 15:10 UTC1h 10m
2026-07-01 N916NT BFL → BFL Jul 1, 23:45 UTCJul 2, 00:15 UTC30m
2026-07-01 N916NT - Jul 1, 19:40 UTCJul 1, 20:00 UTC20m
2026-07-01 N916NT - Jul 1, 18:05 UTCJul 1, 18:20 UTC15m
2026-07-01 N916NT BFL → BFL Jul 1, 15:50 UTCJul 1, 17:30 UTC1h 40m
2026-07-01 N916NT BFL → BFL Jul 1, 13:30 UTCJul 1, 15:00 UTC1h 30m
2026-07-01 N916NT BFL → BFL Jul 1, 01:10 UTCJul 1, 02:30 UTC1h 20m
2026-06-30 N916NT BFL → BFL Jun 30, 20:50 UTCJun 30, 22:25 UTC1h 35m
2026-06-30 N916NT BFL → BFL Jun 30, 17:40 UTCJun 30, 19:20 UTC1h 40m
2026-06-29 N916NT - Jun 29, 20:30 UTCJun 29, 20:44 UTC15m
2026-06-29 N916NT - Jun 29, 18:25 UTCJun 29, 18:55 UTC30m
2026-06-29 N916NT BFL → BFL Jun 29, 16:25 UTCJun 29, 17:19 UTC55m
2026-06-29 N916NT BFL → BFL Jun 29, 14:29 UTCJun 29, 15:19 UTC50m
2026-06-28 N916NT BFL → BFL Jun 28, 18:44 UTCJun 28, 21:50 UTC3h 5m
2026-06-28 N916NT BFL → BFL Jun 28, 16:05 UTCJun 28, 17:10 UTC1h 5m
2026-06-27 N916NT BFL → BFL Jun 27, 21:04 UTCJun 27, 21:55 UTC50m
2026-06-27 N916NT BFL → BFL Jun 27, 14:14 UTCJun 27, 15:14 UTC1h 0m
2026-06-27 N916NT BFL → BFL Jun 27, 01:35 UTCJun 27, 02:09 UTC35m
2026-06-26 N916NT BFL → BFL Jun 26, 21:20 UTCJun 26, 22:34 UTC1h 15m
2026-06-26 N916NT - Jun 26, 17:44 UTCJun 26, 18:34 UTC50m
2026-06-26 N916NT BFL → BFL Jun 26, 16:09 UTCJun 26, 17:00 UTC50m
2026-06-25 N916NT BFL → BFL Jun 25, 20:59 UTCJun 25, 21:35 UTC35m

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

Mode-S ACAE33 frequently asked

What is Mode-S code ACAE33?
ACAE33 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N916NT.
Where is Mode-S ACAE33 registered?
Mode-S code ACAE33 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 ACAE33 broadcasting right now?
Mode-S ACAE33 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 ACAE33, octal 53127063, decimal 11,316,787.
What flights does ACAE33 operate?
Mode-S ACAE33 has broadcast 1 distinct callsign, including N916NT.