Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A366A1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N318XL · CESSNA 560XL Citation XLS · operated by CARRIAGE DPB LLC

Hex
A366A1
Octal
50663241
Decimal
10,708,641
Country
US
Tail
N318XL
Type
C56X
No current signal · last broadcast 55m ago
Flights observed
135
Distinct callsigns
1
Country
US
Last broadcast
55m ago

Last known position

Most recent position reported by Mode-S A366A1.

Country allocation

The ICAO 24-bit address A366A1 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
JTL318 - 135 2026-07-14

Recent flights last 50

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

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

Mode-S A366A1 frequently asked

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