sensors Mode-S transponder

AD78CF

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N9672K · PIPER PA-28-140/150/160/180 · operated by EVERGLADES AVIATION ACADEMY LLC

Hex
AD78CF
Octal
53274317
Decimal
11,368,655
Country
US
Tail
N9672K
Type
P28A
No current signal · last broadcast 4h ago
Flights observed
61
Distinct callsigns
1
Country
US
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S AD78CF.

Country allocation

The ICAO 24-bit address AD78CF 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
N9672K - 61 2026-05-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 N9672K HWO → HWO May 30, 12:40 UTCMay 30, 13:35 UTC55m
2026-05-29 N9672K - May 29, 14:55 UTCMay 29, 15:25 UTC30m
2026-05-29 N9672K - May 29, 13:55 UTCMay 29, 14:20 UTC25m
2026-05-29 N9672K - May 29, 12:45 UTCMay 29, 13:20 UTC35m
2026-05-26 N9672K HWO → HWO May 26, 12:35 UTCMay 26, 14:05 UTC1h 30m
2026-05-25 N9672K - May 25, 13:35 UTCMay 25, 16:20 UTC2h 45m
2026-05-22 N9672K HWO → HWO May 22, 13:05 UTCMay 22, 14:15 UTC1h 10m
2026-05-21 N9672K HWO → HWO May 21, 16:45 UTCMay 21, 17:55 UTC1h 10m
2026-05-21 N9672K - May 21, 14:45 UTCMay 21, 16:01 UTC1h 15m
2026-05-21 N9672K HWO → HWO May 21, 12:35 UTCMay 21, 13:50 UTC1h 15m
2026-05-20 N9672K - May 20, 17:45 UTCMay 20, 19:20 UTC1h 35m
2026-05-20 N9672K - May 20, 15:55 UTCMay 20, 16:55 UTC1h 0m
2026-05-19 N9672K - May 19, 12:40 UTCMay 19, 13:55 UTC1h 15m
2026-05-16 N9672K - May 16, 18:45 UTCMay 16, 20:50 UTC2h 5m
2026-05-14 N9672K - May 14, 14:50 UTCMay 14, 16:00 UTC1h 10m
2026-05-14 N9672K HWO → HWO May 14, 12:35 UTCMay 14, 13:50 UTC1h 15m
2026-05-13 N9672K HWO → HWO May 13, 16:10 UTCMay 13, 16:55 UTC45m
2026-05-13 N9672K - May 13, 12:50 UTCMay 13, 14:00 UTC1h 10m
2026-05-12 N9672K - May 12, 12:40 UTCMay 12, 13:55 UTC1h 15m
2026-05-10 N9672K - May 10, 15:55 UTCMay 10, 18:25 UTC2h 30m
2026-05-08 N9672K HWO → HWO May 8, 20:00 UTCMay 8, 21:05 UTC1h 5m
2026-05-08 N9672K HWO → HWO May 8, 12:25 UTCMay 8, 13:50 UTC1h 25m
2026-05-07 N9672K HWO → HWO May 7, 13:10 UTCMay 7, 14:00 UTC50m
2026-05-06 N9672K HWO → HWO May 6, 19:05 UTCMay 6, 20:05 UTC1h 0m
2026-05-06 N9672K - May 6, 16:55 UTCMay 6, 18:05 UTC1h 9m
2026-05-06 N9672K - May 6, 15:00 UTCMay 6, 16:00 UTC1h 0m
2026-05-06 N9672K - May 6, 12:40 UTCMay 6, 13:50 UTC1h 10m
2026-05-05 N9672K - May 5, 18:05 UTCMay 5, 19:15 UTC1h 10m
2026-05-05 N9672K - May 5, 15:30 UTCMay 5, 16:50 UTC1h 20m
2026-05-02 N9672K HWO → HWO May 2, 12:55 UTCMay 2, 15:25 UTC2h 30m
2026-05-01 N9672K HWO → HWO May 1, 16:10 UTCMay 1, 17:15 UTC1h 5m
2026-04-30 N9672K - Apr 30, 16:50 UTCApr 30, 18:05 UTC1h 15m
2026-04-30 N9672K HWO → HWO Apr 30, 12:45 UTCApr 30, 14:00 UTC1h 15m
2026-04-29 N9672K HWO → HWO Apr 29, 17:45 UTCApr 29, 18:55 UTC1h 10m
2026-04-29 N9672K - Apr 29, 15:10 UTCApr 29, 16:45 UTC1h 35m
2026-04-28 N9672K HWO → HWO Apr 28, 15:45 UTCApr 28, 17:00 UTC1h 15m
2026-04-28 N9672K HWO → HWO Apr 28, 12:20 UTCApr 28, 13:40 UTC1h 20m
2026-04-27 N9672K - Apr 27, 19:35 UTCApr 27, 20:50 UTC1h 15m
2026-04-26 N9672K - Apr 26, 22:45 UTCApr 26, 23:25 UTC40m
2026-04-26 N9672K - Apr 26, 18:50 UTCApr 26, 19:15 UTC25m
2026-04-26 N9672K - Apr 26, 17:50 UTCApr 26, 18:20 UTC30m
2026-04-25 N9672K - Apr 25, 13:35 UTCApr 25, 14:50 UTC1h 15m
2026-04-25 N9672K - Apr 25, 12:35 UTCApr 25, 13:00 UTC25m
2026-04-24 N9672K - Apr 24, 15:10 UTCApr 24, 15:55 UTC45m
2026-04-23 N9672K - Apr 23, 21:20 UTCApr 23, 22:20 UTC1h 0m
2026-04-23 N9672K - Apr 23, 19:25 UTCApr 23, 19:55 UTC30m
2026-04-23 N9672K - Apr 23, 16:50 UTCApr 23, 18:00 UTC1h 9m
2026-04-23 N9672K HWO → HWO Apr 23, 14:55 UTCApr 23, 15:55 UTC1h 0m
2026-04-23 N9672K - Apr 23, 12:50 UTCApr 23, 13:35 UTC45m
2026-04-22 N9672K - Apr 22, 16:40 UTCApr 22, 17:45 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 N9672K page for operator, model, and routing details .

Mode-S AD78CF frequently asked

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