Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A4AC6E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N40Y · BEECH 200 Super King Air · operated by DYNAMIC AVLEASE INC

Hex
A4AC6E
Octal
51126156
Decimal
10,792,046
Country
US
Tail
N40Y
Type
BE20
No current signal · last broadcast 11d ago
Flights observed
76
Distinct callsigns
1
Country
US
Last broadcast
11d ago

Last known position

Most recent position reported by Mode-S A4AC6E.

Country allocation

The ICAO 24-bit address A4AC6E 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
INTEL12 - 76 2026-07-24

Recent flights last 50

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

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

Mode-S A4AC6E frequently asked

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