Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AD5A50

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N96FF · operated by PEREGRINE HOWARD AVIATION LLC

Hex
AD5A50
Octal
53255120
Decimal
11,360,848
Country
US
Tail
N96FF
Type
C172
No current signal · last broadcast 8h ago
Flights observed
119
Distinct callsigns
1
Country
US
Last broadcast
8h ago

Last known position

Most recent position reported by Mode-S AD5A50.

Country allocation

The ICAO 24-bit address AD5A50 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
N96FF - 119 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 N96FF BJC → BJC May 29, 19:50 UTCMay 29, 21:15 UTC1h 25m
2026-05-29 N96FF BJC → BJC May 29, 17:40 UTCMay 29, 18:55 UTC1h 15m
2026-05-29 N96FF BJC → BJC May 29, 15:25 UTCMay 29, 16:20 UTC56m
2026-05-28 N96FF BJC → BJC May 28, 16:50 UTCMay 28, 17:30 UTC40m
2026-05-28 N96FF BJC → BJC May 28, 12:40 UTCMay 28, 13:45 UTC1h 5m
2026-05-27 N96FF BJC → BJC May 27, 22:10 UTCMay 27, 23:45 UTC1h 35m
2026-05-27 N96FF BJC → BJC May 27, 20:15 UTCMay 27, 21:20 UTC1h 5m
2026-05-27 N96FF BJC → BJC May 27, 17:00 UTCMay 27, 18:05 UTC1h 5m
2026-05-27 N96FF BJC → BJC May 27, 13:30 UTCMay 27, 15:10 UTC1h 40m
2026-05-26 N96FF BJC → BJC May 26, 17:59 UTCMay 26, 19:20 UTC1h 20m
2026-05-26 N96FF BJC → BJC May 26, 15:24 UTCMay 26, 16:45 UTC1h 20m
2026-05-25 N96FF BJC → BJC May 25, 13:15 UTCMay 25, 15:05 UTC1h 50m
2026-05-24 N96FF BJC → BJC May 24, 17:40 UTCMay 24, 19:20 UTC1h 40m
2026-05-24 N96FF BJC → BJC May 24, 15:40 UTCMay 24, 16:40 UTC1h 0m
2026-05-23 N96FF BJC → BJC May 23, 20:20 UTCMay 23, 22:00 UTC1h 40m
2026-05-23 N96FF BJC → BJC May 23, 18:00 UTCMay 23, 19:30 UTC1h 30m
2026-05-23 N96FF BJC → BJC May 23, 15:15 UTCMay 23, 16:45 UTC1h 30m
2026-05-23 N96FF BJC → BJC May 23, 12:55 UTCMay 23, 14:20 UTC1h 25m
2026-05-22 N96FF BJC → BJC May 22, 22:05 UTCMay 22, 23:10 UTC1h 5m
2026-05-22 N96FF - May 22, 19:45 UTCMay 22, 20:00 UTC15m
2026-05-22 N96FF - May 22, 19:15 UTCMay 22, 19:35 UTC20m
2026-05-22 N96FF BJC → BJC May 22, 16:40 UTCMay 22, 17:40 UTC1h 0m
2026-05-22 N96FF BJC → BJC May 22, 14:20 UTCMay 22, 15:20 UTC1h 0m
2026-05-21 N96FF BJC → BJC May 21, 19:25 UTCMay 21, 21:05 UTC1h 40m
2026-05-20 N96FF BJC → BJC May 20, 13:40 UTCMay 20, 15:05 UTC1h 25m
2026-05-17 N96FF BJC → BJC May 17, 12:15 UTCMay 17, 13:55 UTC1h 40m
2026-05-16 N96FF BJC → BJC May 16, 17:25 UTCMay 16, 18:25 UTC1h 0m
2026-05-16 N96FF BJC → BJC May 16, 13:41 UTCMay 16, 14:46 UTC1h 5m
2026-05-15 N96FF BJC → BJC May 15, 21:30 UTCMay 15, 23:00 UTC1h 30m
2026-05-15 N96FF - May 15, 17:20 UTCMay 15, 17:50 UTC30m
2026-05-15 N96FF - May 15, 17:05 UTCMay 15, 17:15 UTC10m
2026-05-15 N96FF BJC → FNL May 15, 16:25 UTCMay 15, 17:00 UTC35m
2026-05-15 N96FF BJC → BJC May 15, 12:20 UTCMay 15, 13:50 UTC1h 30m
2026-05-14 N96FF BJC → BJC May 14, 21:45 UTCMay 14, 22:35 UTC50m
2026-05-14 N96FF BJC → BJC May 14, 13:01 UTCMay 14, 14:20 UTC1h 20m
2026-05-13 N96FF BJC → BJC May 13, 22:10 UTCMay 13, 22:55 UTC45m
2026-05-13 N96FF - May 13, 19:25 UTCMay 13, 20:45 UTC1h 20m
2026-05-13 N96FF BJC → BJC May 13, 17:05 UTCMay 13, 18:25 UTC1h 20m
2026-05-13 N96FF BJC → BJC May 13, 14:05 UTCMay 13, 15:05 UTC1h 0m
2026-05-12 N96FF BJC → BJC May 12, 19:55 UTCMay 12, 20:45 UTC50m
2026-05-12 N96FF BJC → BJC May 12, 17:05 UTCMay 12, 18:35 UTC1h 30m
2026-05-12 N96FF - May 12, 14:15 UTCMay 12, 14:20 UTC5m
2026-05-12 N96FF BJC → BJC May 12, 13:51 UTCMay 12, 14:00 UTC10m
2026-05-11 N96FF BJC → BJC May 11, 21:00 UTCMay 11, 21:25 UTC25m
2026-05-11 N96FF - May 11, 15:10 UTCMay 11, 15:25 UTC15m
2026-05-11 N96FF - May 11, 14:20 UTCMay 11, 14:35 UTC15m
2026-05-11 N96FF - May 11, 13:50 UTCMay 11, 13:55 UTC5m
2026-05-11 N96FF BJC → BJC May 11, 13:40 UTCMay 11, 13:45 UTC5m
2026-05-09 N96FF BJC → BJC May 9, 18:10 UTCMay 9, 18:15 UTC5m
2026-05-09 N96FF - May 9, 17:55 UTCMay 9, 18:00 UTC5m

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

Mode-S AD5A50 frequently asked

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