Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A6D158

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N5386J · CESSNA 172 Skyhawk · operated by NAYLOR-ADAMS AVIATION LLC

Hex
A6D158
Octal
51550530
Decimal
10,932,568
Country
US
Tail
N5386J
Type
C172
No current signal · last broadcast 4d ago
Flights observed
87
Distinct callsigns
1
Country
US
Last broadcast
4d ago

Last known position

Most recent position reported by Mode-S A6D158.

Country allocation

The ICAO 24-bit address A6D158 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
N5386J - 87 2026-07-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 N5386J HAR → HAR Jul 16, 13:00 UTCJul 16, 13:30 UTC30m
2026-07-14 N5386J HAR → HAR Jul 14, 13:20 UTCJul 14, 14:25 UTC1h 5m
2026-07-14 N5386J HAR → HAR Jul 14, 00:00 UTCJul 14, 00:10 UTC10m
2026-07-13 N5386J HAR → HAR Jul 13, 22:35 UTCJul 13, 23:40 UTC1h 5m
2026-07-08 N5386J HAR → HAR Jul 8, 23:40 UTCJul 9, 00:30 UTC50m
2026-07-08 N5386J HAR → HAR Jul 8, 23:25 UTCJul 8, 23:30 UTC5m
2026-07-05 N5386J - Jul 5, 17:15 UTCJul 5, 17:55 UTC40m
2026-07-05 N5386J - Jul 5, 16:15 UTCJul 5, 16:25 UTC10m
2026-07-05 N5386J - Jul 5, 15:25 UTCJul 5, 15:35 UTC10m
2026-06-30 N5386J HAR → HAR Jun 30, 20:05 UTCJun 30, 20:30 UTC25m
2026-06-30 N5386J - Jun 30, 16:50 UTCJun 30, 18:00 UTC1h 10m
2026-06-30 N5386J HAR → HAR Jun 30, 14:15 UTCJun 30, 14:45 UTC30m
2026-06-30 N5386J - Jun 30, 00:30 UTCJun 30, 01:35 UTC1h 6m
2026-06-29 N5386J - Jun 29, 20:35 UTCJun 29, 21:34 UTC1h 0m
2026-06-29 N5386J - Jun 29, 17:49 UTCJun 29, 19:00 UTC1h 10m
2026-06-29 N5386J - Jun 29, 16:00 UTCJun 29, 16:50 UTC50m
2026-06-28 N5386J HAR → HAR Jun 28, 18:00 UTCJun 28, 18:55 UTC55m
2026-06-27 N5386J HAR → HAR Jun 27, 23:39 UTCJun 28, 00:35 UTC55m
2026-06-26 N5386J - Jun 26, 19:55 UTCJun 26, 20:59 UTC1h 5m
2026-06-26 N5386J - Jun 26, 14:09 UTCJun 26, 14:19 UTC10m
2026-06-25 N5386J - Jun 25, 23:05 UTCJun 26, 00:20 UTC1h 15m
2026-06-24 N5386J HAR → HAR Jun 24, 16:05 UTCJun 24, 17:40 UTC1h 35m
2026-06-23 N5386J HAR → HAR Jun 23, 22:34 UTCJun 24, 00:15 UTC1h 40m
2026-06-16 N5386J - Jun 16, 20:05 UTCJun 16, 20:45 UTC40m
2026-06-16 N5386J - Jun 16, 15:45 UTCJun 16, 16:35 UTC50m
2026-06-12 N5386J HAR → HAR Jun 12, 11:30 UTCJun 12, 11:50 UTC20m
2026-06-11 N5386J - Jun 11, 18:00 UTCJun 11, 18:40 UTC40m
2026-06-08 N5386J - Jun 8, 18:35 UTCJun 8, 18:45 UTC10m
2026-06-08 N5386J - Jun 8, 17:45 UTCJun 8, 17:55 UTC10m
2026-06-05 N5386J - Jun 5, 15:25 UTCJun 5, 16:15 UTC50m
2026-06-05 N5386J HAR → HAR Jun 5, 13:55 UTCJun 5, 14:30 UTC35m
2026-06-04 N5386J - Jun 4, 15:35 UTCJun 4, 16:50 UTC1h 15m
2026-06-03 N5386J HAR → HAR Jun 3, 20:15 UTCJun 3, 21:00 UTC45m
2026-06-03 N5386J HAR → HAR Jun 3, 18:15 UTCJun 3, 18:50 UTC35m
2026-06-02 N5386J HAR → HAR Jun 2, 22:25 UTCJun 2, 23:15 UTC50m
2026-05-31 N5386J HAR → HAR May 31, 23:40 UTCJun 1, 01:10 UTC1h 30m
2026-05-31 N5386J HAR → HAR May 31, 17:40 UTCMay 31, 18:15 UTC35m
2026-05-29 N5386J - May 29, 14:50 UTCMay 29, 15:40 UTC50m
2026-05-26 N5386J - May 26, 22:44 UTCMay 26, 23:10 UTC25m
2026-05-26 N5386J - May 26, 20:29 UTCMay 26, 20:54 UTC25m
2026-05-26 N5386J - May 26, 20:00 UTCMay 26, 20:24 UTC25m
2026-05-26 N5386J - May 26, 14:24 UTCMay 26, 14:40 UTC15m
2026-05-26 N5386J HAR → HAR May 26, 14:09 UTCMay 26, 14:14 UTC5m
2026-05-25 N5386J HAR → HAR May 25, 21:40 UTCMay 25, 22:15 UTC35m
2026-05-22 N5386J HAR → HAR May 22, 13:50 UTCMay 22, 14:15 UTC25m
2026-05-20 N5386J - May 20, 15:10 UTCMay 20, 16:15 UTC1h 5m
2026-05-17 N5386J HAR → HAR May 17, 23:00 UTCMay 17, 23:55 UTC55m
2026-05-17 N5386J - May 17, 19:25 UTCMay 17, 21:45 UTC2h 20m
2026-05-17 N5386J - May 17, 14:40 UTCMay 17, 15:05 UTC25m
2026-05-17 N5386J HAR → RDG May 17, 12:45 UTCMay 17, 14:30 UTC1h 45m

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

Mode-S A6D158 frequently asked

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