sensors Mode-S transponder

ACADE8

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N916KT · CESSNA 172 Skyhawk · operated by PELICAN FLIGHT TRAINING LLC

Hex
ACADE8
Octal
53126750
Decimal
11,316,712
Country
US
Tail
N916KT
Type
C172
Broadcasting now · callsign N916KT · 2,950 ft
Flights observed
221
Distinct callsigns
1
Country
US
Last broadcast
19h ago

Current position

ACADE8 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address ACADE8 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
N916KT - 221 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 N916KT SQL → SQL Jul 14, 02:35 UTCJul 14, 03:05 UTC30m
2026-07-13 N916KT SQL → SQL Jul 13, 20:35 UTCJul 13, 21:35 UTC1h 0m
2026-07-12 N916KT - Jul 12, 20:55 UTCJul 12, 21:35 UTC40m
2026-07-12 N916KT - Jul 12, 19:25 UTCJul 12, 20:01 UTC35m
2026-07-12 N916KT SQL → SQL Jul 12, 18:25 UTCJul 12, 18:30 UTC5m
2026-07-12 N916KT SQL → SQL Jul 12, 17:05 UTCJul 12, 18:05 UTC1h 0m
2026-07-11 N916KT SQL → SQL Jul 11, 23:10 UTCJul 12, 00:35 UTC1h 25m
2026-07-11 N916KT - Jul 11, 21:30 UTCJul 11, 21:40 UTC10m
2026-07-11 N916KT SQL → SQL Jul 11, 21:15 UTCJul 11, 21:20 UTC5m
2026-07-11 N916KT SQL → SQL Jul 11, 19:35 UTCJul 11, 21:00 UTC1h 25m
2026-07-11 N916KT SQL → SQL Jul 11, 17:25 UTCJul 11, 18:35 UTC1h 10m
2026-07-11 N916KT SQL → SQL Jul 11, 16:50 UTCJul 11, 17:10 UTC20m
2026-07-10 N916KT SQL → SQL Jul 10, 23:25 UTCJul 11, 00:25 UTC1h 0m
2026-07-10 N916KT SQL → SQL Jul 10, 19:35 UTCJul 10, 21:10 UTC1h 35m
2026-07-10 N916KT - Jul 10, 18:20 UTCJul 10, 18:35 UTC15m
2026-07-10 N916KT SQL → SQL Jul 10, 18:05 UTCJul 10, 18:15 UTC10m
2026-07-10 N916KT PAO → SQL Jul 10, 05:00 UTCJul 10, 05:15 UTC15m
2026-07-10 N916KT SQL → PAO Jul 10, 04:30 UTCJul 10, 04:40 UTC10m
2026-07-09 N916KT SQL → SQL Jul 9, 23:55 UTCJul 10, 01:25 UTC1h 30m
2026-07-09 N916KT SQL → SQL Jul 9, 19:55 UTCJul 9, 21:15 UTC1h 20m
2026-07-09 N916KT SQL → SQL Jul 9, 17:40 UTCJul 9, 18:45 UTC1h 5m
2026-07-09 N916KT SQL → SQL Jul 9, 01:35 UTCJul 9, 02:15 UTC40m
2026-07-08 N916KT SQL → SQL Jul 8, 23:20 UTCJul 9, 00:25 UTC1h 5m
2026-07-08 N916KT SQL → SQL Jul 8, 21:50 UTCJul 8, 22:35 UTC45m
2026-07-08 N916KT SQL → SQL Jul 8, 20:10 UTCJul 8, 21:20 UTC1h 10m
2026-07-08 N916KT SQL → SQL Jul 8, 18:10 UTCJul 8, 18:20 UTC10m
2026-07-08 N916KT SQL → SQL Jul 8, 17:50 UTCJul 8, 18:05 UTC15m
2026-07-08 N916KT SQL → SQL Jul 8, 17:30 UTCJul 8, 17:35 UTC5m
2026-07-07 N916KT SQL → SQL Jul 7, 20:45 UTCJul 7, 22:30 UTC1h 45m
2026-07-06 N916KT SQL → SQL Jul 6, 22:55 UTCJul 7, 00:00 UTC1h 5m
2026-07-06 N916KT SQL → SQL Jul 6, 20:15 UTCJul 6, 21:05 UTC50m
2026-07-06 N916KT SQL → SQL Jul 6, 17:35 UTCJul 6, 18:40 UTC1h 5m
2026-07-06 N916KT SQL → SQL Jul 6, 00:25 UTCJul 6, 01:10 UTC45m
2026-07-05 N916KT SQL → SQL Jul 5, 21:25 UTCJul 5, 22:35 UTC1h 10m
2026-07-05 N916KT SQL → SQL Jul 5, 17:45 UTCJul 5, 19:50 UTC2h 5m
2026-07-04 N916KT SQL → SQL Jul 4, 20:35 UTCJul 4, 20:45 UTC10m
2026-07-04 N916KT SQL → SQL Jul 4, 19:20 UTCJul 4, 20:30 UTC1h 10m
2026-07-04 N916KT SQL → SQL Jul 4, 00:00 UTCJul 4, 00:20 UTC20m
2026-07-03 N916KT SQL → SQL Jul 3, 23:35 UTCJul 3, 23:45 UTC10m
2026-07-03 N916KT SQL → SQL Jul 3, 23:25 UTCJul 3, 23:30 UTC5m
2026-07-03 N916KT - Jul 3, 20:20 UTCJul 3, 20:55 UTC35m
2026-07-03 N916KT - Jul 3, 18:20 UTCJul 3, 19:40 UTC1h 20m
2026-07-03 N916KT SQL → SQL Jul 3, 03:45 UTCJul 3, 05:25 UTC1h 40m
2026-07-03 N916KT SQL → SQL Jul 3, 02:05 UTCJul 3, 02:40 UTC35m
2026-07-02 N916KT SQL → SQL Jul 2, 21:10 UTCJul 2, 22:00 UTC50m
2026-07-02 N916KT SQL → SQL Jul 2, 18:25 UTCJul 2, 19:45 UTC1h 20m
2026-07-02 N916KT SQL → SQL Jul 2, 00:10 UTCJul 2, 01:10 UTC1h 0m
2026-07-01 N916KT SQL → SQL Jul 1, 22:15 UTCJul 1, 23:10 UTC55m
2026-07-01 N916KT SQL → SQL Jul 1, 21:05 UTCJul 1, 21:30 UTC25m
2026-07-01 N916KT SQL → SQL Jul 1, 18:10 UTCJul 1, 19:15 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 N916KT page for operator, model, and routing details .

Mode-S ACADE8 frequently asked

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