Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A81365

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N6196P · CESSNA 172 Skyhawk · operated by CHRISTIANSEN AVIATION LLC

Hex
A81365
Octal
52011545
Decimal
11,015,013
Country
US
Tail
N6196P
Type
C172
No current signal · last broadcast 19d ago
Flights observed
143
Distinct callsigns
1
Country
US
Last broadcast
19d ago

Last known position

Most recent position reported by Mode-S A81365.

Country allocation

The ICAO 24-bit address A81365 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
N6196P - 143 2026-06-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-24 N6196P BFL → BFL Jun 24, 21:19 UTCJun 24, 21:40 UTC20m
2026-06-12 N6196P BFL → BFL Jun 12, 05:45 UTCJun 12, 06:30 UTC45m
2026-06-11 N6196P BFL → BFL Jun 11, 17:10 UTCJun 11, 17:30 UTC20m
2026-06-11 N6196P BFL → BFL Jun 11, 16:35 UTCJun 11, 17:05 UTC30m
2026-06-10 N6196P BFL → BFL Jun 10, 23:20 UTCJun 11, 00:20 UTC1h 0m
2026-06-10 N6196P BFL → BFL Jun 10, 18:35 UTCJun 10, 19:20 UTC45m
2026-06-10 N6196P BFL → BFL Jun 10, 16:40 UTCJun 10, 17:05 UTC25m
2026-06-10 N6196P BFL → BFL Jun 10, 13:55 UTCJun 10, 14:45 UTC50m
2026-06-09 N6196P BFL → BFL Jun 9, 23:00 UTCJun 10, 01:25 UTC2h 25m
2026-06-09 N6196P BFL → BFL Jun 9, 20:55 UTCJun 9, 22:00 UTC1h 5m
2026-06-09 N6196P BFL → BFL Jun 9, 18:50 UTCJun 9, 19:55 UTC1h 5m
2026-06-08 N6196P BFL → BFL Jun 8, 23:10 UTCJun 9, 00:30 UTC1h 20m
2026-06-07 N6196P - Jun 7, 17:25 UTCJun 7, 17:35 UTC10m
2026-06-07 N6196P - Jun 7, 15:50 UTCJun 7, 16:10 UTC20m
2026-06-07 N6196P - Jun 7, 14:50 UTCJun 7, 15:10 UTC20m
2026-06-07 N6196P - Jun 7, 13:40 UTCJun 7, 14:00 UTC20m
2026-06-06 N6196P BFL → BFL Jun 6, 03:40 UTCJun 6, 04:40 UTC1h 0m
2026-06-05 N6196P BFL → BFL Jun 5, 20:35 UTCJun 5, 21:55 UTC1h 20m
2026-06-05 N6196P BFL → BFL Jun 5, 18:40 UTCJun 5, 19:40 UTC1h 0m
2026-06-05 N6196P BFL → BFL Jun 5, 16:25 UTCJun 5, 17:40 UTC1h 15m
2026-06-05 N6196P BFL → BFL Jun 5, 01:45 UTCJun 5, 02:40 UTC55m
2026-06-02 N6196P BFL → BFL Jun 2, 20:45 UTCJun 2, 21:40 UTC55m
2026-06-02 N6196P BFL → BFL Jun 2, 18:20 UTCJun 2, 19:20 UTC1h 0m
2026-06-02 N6196P BFL → BFL Jun 2, 16:15 UTCJun 2, 17:00 UTC45m
2026-06-02 N6196P BFL → BFL Jun 2, 14:10 UTCJun 2, 15:15 UTC1h 5m
2026-06-01 N6196P BFL → BFL Jun 1, 18:30 UTCJun 1, 19:50 UTC1h 20m
2026-05-31 N6196P BFL → BFL May 31, 20:55 UTCMay 31, 22:30 UTC1h 35m
2026-05-31 N6196P BFL → BFL May 31, 18:15 UTCMay 31, 19:10 UTC55m
2026-05-31 N6196P BFL → BFL May 31, 15:50 UTCMay 31, 17:25 UTC1h 35m
2026-05-30 N6196P BFL → BFL May 30, 18:50 UTCMay 30, 19:45 UTC55m
2026-05-30 N6196P BFL → BFL May 30, 16:35 UTCMay 30, 17:35 UTC1h 0m
2026-05-30 N6196P BFL → BFL May 30, 14:15 UTCMay 30, 15:30 UTC1h 15m
2026-05-28 N6196P BFL → BFL May 28, 23:15 UTCMay 29, 00:30 UTC1h 15m
2026-05-28 N6196P BFL → BFL May 28, 18:45 UTCMay 28, 19:40 UTC55m
2026-05-28 N6196P BFL → BFL May 28, 14:15 UTCMay 28, 15:30 UTC1h 15m
2026-05-27 N6196P BFL → BFL May 27, 20:25 UTCMay 27, 21:45 UTC1h 20m
2026-05-27 N6196P BFL → BFL May 27, 16:30 UTCMay 27, 17:30 UTC1h 0m
2026-05-27 N6196P BFL → BFL May 27, 14:05 UTCMay 27, 15:00 UTC55m
2026-05-24 N6196P BFL → BFL May 24, 16:25 UTCMay 24, 18:10 UTC1h 45m
2026-05-24 N6196P BFL → BFL May 24, 01:05 UTCMay 24, 02:20 UTC1h 15m
2026-05-23 N6196P BFL → BFL May 23, 14:25 UTCMay 23, 16:05 UTC1h 40m
2026-05-22 N6196P BFL → BFL May 22, 23:20 UTCMay 23, 00:25 UTC1h 5m
2026-05-22 N6196P BFL → BFL May 22, 18:50 UTCMay 22, 19:45 UTC55m
2026-05-22 N6196P BFL → BFL May 22, 14:15 UTCMay 22, 15:55 UTC1h 40m
2026-05-22 N6196P BFL → BFL May 22, 01:05 UTCMay 22, 01:35 UTC30m
2026-05-21 N6196P BFL → BFL May 21, 18:40 UTCMay 21, 19:55 UTC1h 15m
2026-05-21 N6196P BFL → BFL May 21, 16:15 UTCMay 21, 17:40 UTC1h 25m
2026-05-21 N6196P BFL → BFL May 21, 14:00 UTCMay 21, 15:20 UTC1h 20m
2026-05-21 N6196P BFL → BFL May 21, 01:05 UTCMay 21, 02:15 UTC1h 10m
2026-05-20 N6196P BFL → BFL May 20, 16:45 UTCMay 20, 18:00 UTC1h 15m

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

Mode-S A81365 frequently asked

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