Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ACD4B6

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N926CR · CESSNA 172 Skyhawk · operated by AERO TECH SERVICES INC

Hex
ACD4B6
Octal
53152266
Decimal
11,326,646
Country
US
Tail
N926CR
Type
C172
No current signal · last broadcast 11h ago
Flights observed
190
Distinct callsigns
1
Country
US
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S ACD4B6.

Country allocation

The ICAO 24-bit address ACD4B6 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
N926CR - 190 2026-07-13

Recent flights last 50

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

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

Mode-S ACD4B6 frequently asked

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