Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AD5FF1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N961AV · AIRBUS A-320 · operated by WILMINGTON TRUST CO TRUSTEE

Hex
AD5FF1
Octal
53257761
Decimal
11,362,289
Country
US
Tail
N961AV
Type
A320
No current signal · last broadcast 46m ago
Flights observed
269
Distinct callsigns
20
Country
US
Last broadcast
46m ago

Last known position

Most recent position reported by Mode-S AD5FF1.

Country allocation

The ICAO 24-bit address AD5FF1 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 20 distinct

Callsign Airline Flights Last seen
TAI522 - 12 2026-07-12
TAI523 - 11 2026-07-12
TAI311 - 9 2026-06-24
LRC600 - 9 2026-06-25
TAI396 - 8 2026-06-24
TAI310 Avianca El Salvador 8 2026-06-21
TAI590 - 7 2026-07-08
TAI520 Avianca El Salvador 7 2026-05-26
TAI424 - 7 2026-07-06
TAI582 - 6 2026-07-09
TAI521 Avianca El Salvador 6 2026-05-26
LRC671 LACSA 6 2026-05-17
LRC670 LACSA 6 2026-05-17
LRC601 - 6 2026-06-25
TAI591 Avianca El Salvador 5 2026-06-14
TAI583 - 5 2026-07-09
TAI569 - 5 2026-07-10
TAI568 - 5 2026-07-10
TAI425 - 5 2026-07-06
TAI397 - 5 2026-06-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAI367 - Jul 14, 19:15 UTCJul 14, 19:45 UTC30m
2026-07-14 TAI368 - Jul 14, 14:15 UTCJul 14, 16:45 UTC2h 30m
2026-07-14 TAI317 - Jul 14, 05:35 UTCJul 14, 11:25 UTC5h 50m
2026-07-14 TAI585 - Jul 14, 00:05 UTCJul 14, 03:40 UTC3h 35m
2026-07-13 TAI584 SJO → IAD Jul 13, 16:05 UTCJul 13, 22:30 UTC6h 25m
2026-07-13 LRC626 SJO → SJO Jul 13, 11:10 UTCJul 13, 15:00 UTC3h 50m
2026-07-13 LRC627 - Jul 13, 05:05 UTCJul 13, 05:35 UTC30m
2026-07-12 TAI523 - Jul 12, 21:05 UTCJul 13, 01:40 UTC4h 35m
2026-07-12 TAI522 - Jul 12, 14:30 UTCJul 12, 18:55 UTC4h 25m
2026-07-12 LRC661 - Jul 12, 07:50 UTCJul 12, 11:45 UTC3h 55m
2026-07-12 LRC660 - Jul 12, 01:50 UTCJul 12, 05:45 UTC3h 55m
2026-07-11 TAI581 - Jul 11, 11:40 UTCJul 11, 15:10 UTC3h 30m
2026-07-11 TAI580 - Jul 11, 05:35 UTCJul 11, 09:10 UTC3h 35m
2026-07-11 TAI535 - Jul 11, 02:35 UTCJul 11, 03:15 UTC40m
2026-07-10 TAI569 - Jul 10, 11:05 UTCJul 10, 15:00 UTC3h 55m
2026-07-10 TAI568 - Jul 10, 05:05 UTCJul 10, 09:00 UTC3h 55m
2026-07-09 TAI583 - Jul 9, 22:25 UTCJul 10, 02:20 UTC3h 55m
2026-07-09 TAI582 - Jul 9, 16:00 UTCJul 9, 19:30 UTC3h 30m
2026-07-09 TAI321 - Jul 9, 13:30 UTCJul 9, 13:50 UTC20m
2026-07-09 TAI321 GUA → GUA Jul 9, 13:15 UTCJul 9, 13:20 UTC5m
2026-07-09 LRC645 IAD → GUA Jul 9, 08:15 UTCJul 9, 12:10 UTC3h 55m
2026-07-09 LRC644 GUA → IAD Jul 9, 02:35 UTCJul 9, 06:30 UTC3h 55m
2026-07-09 LRC631 - Jul 9, 01:00 UTCJul 9, 01:10 UTC10m
2026-07-08 LRC631 - Jul 8, 21:10 UTCJul 9, 00:05 UTC2h 55m
2026-07-08 LRC630 CCS → SJO Jul 8, 14:45 UTCJul 8, 18:40 UTC3h 55m
2026-07-08 LRC655 IAD → GUA Jul 8, 08:10 UTCJul 8, 12:05 UTC3h 55m
2026-07-08 TAI590 - Jul 8, 03:10 UTCJul 8, 06:20 UTC3h 10m
2026-07-08 TAI590 - Jul 8, 02:45 UTCJul 8, 03:05 UTC20m
2026-07-07 TAI431 - Jul 7, 23:05 UTCJul 8, 00:40 UTC1h 35m
2026-07-07 LRC632 SJO → MEX Jul 7, 19:15 UTCJul 7, 21:10 UTC1h 55m
2026-07-06 TAI425 - Jul 6, 22:50 UTCJul 7, 01:10 UTC2h 20m
2026-07-06 TAI424 - Jul 6, 18:25 UTCJul 6, 20:50 UTC2h 25m
2026-07-06 TAI384 - Jul 6, 16:00 UTCJul 6, 16:20 UTC20m
2026-06-27 AVA127 - Jun 27, 18:20 UTCJun 27, 18:45 UTC25m
2026-06-27 AVA126 - Jun 27, 15:39 UTCJun 27, 16:14 UTC35m
2026-06-26 TAI581 - Jun 26, 12:24 UTCJun 26, 15:54 UTC3h 30m
2026-06-26 TAI580 - Jun 26, 07:05 UTCJun 26, 10:55 UTC3h 50m
2026-06-25 TAI583 - Jun 25, 21:44 UTCJun 26, 01:29 UTC3h 45m
2026-06-25 TAI582 - Jun 25, 15:59 UTCJun 25, 19:29 UTC3h 30m
2026-06-25 LRC601 - Jun 25, 09:59 UTCJun 25, 13:35 UTC3h 35m
2026-06-25 LRC600 - Jun 25, 04:20 UTCJun 25, 07:59 UTC3h 40m
2026-06-24 TAI311 - Jun 24, 20:24 UTCJun 24, 22:25 UTC2h 0m
2026-06-24 TAI396 - Jun 24, 17:05 UTCJun 24, 17:34 UTC30m
2026-06-24 LRC661 - Jun 24, 07:10 UTCJun 24, 11:14 UTC4h 5m
2026-06-24 LRC660 - Jun 24, 00:55 UTCJun 24, 04:55 UTC4h 0m
2026-06-23 TAI433 MEX → SAL Jun 23, 10:19 UTCJun 23, 11:54 UTC1h 35m
2026-06-23 TAI432 SAL → MEX Jun 23, 05:00 UTCJun 23, 06:39 UTC1h 40m
2026-06-22 TAI523 LAX → SAL Jun 22, 21:14 UTCJun 23, 01:50 UTC4h 35m
2026-06-22 TAI522 - Jun 22, 14:14 UTCJun 22, 18:49 UTC4h 35m
2026-06-22 TAI535 - Jun 22, 02:30 UTCJun 22, 02:50 UTC20m

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

Mode-S AD5FF1 frequently asked

What is Mode-S code AD5FF1?
AD5FF1 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N961AV.
Where is Mode-S AD5FF1 registered?
Mode-S code AD5FF1 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 AD5FF1 broadcasting right now?
No active broadcast right now. Last signal was 46m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD5FF1, octal 53257761, decimal 11,362,289.
What flights does AD5FF1 operate?
Mode-S AD5FF1 has broadcast 20 distinct callsigns, including TAI522, TAI523, TAI311, LRC600, TAI396.