sensors Mode-S transponder

AA91F5

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N780QS · BOMBARDIER BD-100 Challenger 350 · operated by NETJETS SALES INC, NETJETS AVIATION INC

Hex
AA91F5
Octal
52510765
Decimal
11,178,485
Country
US
Tail
N780QS
Type
CL35
No current signal · last broadcast 7d ago
Flights observed
69
Distinct callsigns
2
Country
US
Last broadcast
7d ago

Last known position

Most recent position reported by Mode-S AA91F5.

Country allocation

The ICAO 24-bit address AA91F5 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 2 distinct

Callsign Airline Flights Last seen
EJA780 NetJets 64 2026-05-22
N780QS - 5 2026-05-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-22 EJA780 CHO → HPN May 22, 00:25 UTCMay 22, 02:10 UTC1h 45m
2026-05-21 EJA780 CHO → HPN May 21, 20:50 UTCMay 21, 23:25 UTC2h 35m
2026-05-21 EJA780 CHO → HPN May 21, 17:00 UTCMay 21, 20:05 UTC3h 5m
2026-05-21 EJA780 CHO → HPN May 21, 03:30 UTCMay 21, 04:30 UTC1h 0m
2026-05-21 EJA780 CHO → HPN May 21, 00:55 UTCMay 21, 01:55 UTC1h 0m
2026-05-20 EJA780 CHO → HPN May 20, 22:10 UTCMay 21, 00:00 UTC1h 50m
2026-05-20 EJA780 CHO → HPN May 20, 19:00 UTCMay 20, 20:05 UTC1h 5m
2026-05-20 EJA780 CHO → HPN May 20, 17:00 UTCMay 20, 18:10 UTC1h 10m
2026-05-19 EJA780 CHO → HPN May 19, 21:20 UTCMay 20, 18:10 UTC20h 51m
2026-05-19 EJA780 CHO → HPN May 19, 19:20 UTCMay 20, 18:10 UTC22h 51m
2026-05-19 EJA780 CHO → HPN May 19, 17:00 UTCMay 19, 17:30 UTC30m
2026-05-19 EJA780 CHO → HPN May 19, 13:20 UTCMay 19, 15:30 UTC2h 10m
2026-05-18 EJA780 CHO → HPN May 18, 21:45 UTCMay 18, 22:10 UTC25m
2026-05-18 N780QS - May 18, 13:20 UTCMay 18, 20:40 UTC7h 19m
2026-05-18 EJA780 CHO → HPN May 18, 00:35 UTCMay 18, 00:55 UTC20m
2026-05-17 EJA780 CHO → HPN May 17, 21:05 UTCMay 17, 23:45 UTC2h 40m
2026-05-14 EJA780 CHO → HPN May 14, 22:40 UTCMay 14, 23:10 UTC30m
2026-05-14 EJA780 CHO → HPN May 14, 18:55 UTCMay 14, 20:55 UTC2h 0m
2026-05-14 EJA780 CHO → HPN May 14, 16:20 UTCMay 14, 17:15 UTC55m
2026-05-14 EJA780 CHO → HPN May 14, 00:40 UTCMay 14, 01:55 UTC1h 15m
2026-05-13 EJA780 CHO → HPN May 13, 18:55 UTCMay 13, 20:55 UTC2h 0m
2026-05-13 EJA780 CHO → HPN May 13, 15:25 UTCMay 13, 18:00 UTC2h 35m
2026-05-12 EJA780 CHO → HPN May 12, 23:55 UTCMay 13, 00:35 UTC40m
2026-05-12 EJA780 CHO → HPN May 12, 21:35 UTCMay 12, 22:15 UTC40m
2026-05-12 EJA780 CHO → HPN May 12, 14:30 UTCMay 12, 19:50 UTC5h 20m
2026-05-11 EJA780 CHO → HPN May 11, 17:55 UTCMay 11, 21:50 UTC3h 55m
2026-05-11 EJA780 CHO → HPN May 11, 13:10 UTCMay 11, 15:00 UTC1h 50m
2026-05-11 EJA780 CHO → HPN May 11, 11:15 UTCMay 11, 12:00 UTC45m
2026-05-11 EJA780 CHO → HPN May 11, 01:05 UTCMay 11, 01:34 UTC30m
2026-05-10 EJA780 CHO → HPN May 10, 22:20 UTCMay 11, 00:34 UTC2h 15m
2026-05-10 EJA780 CHO → HPN May 10, 19:30 UTCMay 10, 19:45 UTC15m
2026-05-10 EJA780 CHO → HPN May 10, 15:35 UTCMay 10, 17:15 UTC1h 40m
2026-05-10 EJA780 CHO → HPN May 10, 13:55 UTCMay 10, 14:34 UTC40m
2026-05-09 EJA780 CHO → HPN May 9, 21:45 UTCMay 9, 22:20 UTC35m
2026-05-09 EJA780 CHO → HPN May 9, 15:00 UTCMay 9, 15:40 UTC40m
2026-05-09 EJA780 CHO → HPN May 9, 12:15 UTCMay 9, 13:20 UTC1h 5m
2026-05-08 EJA780 CHO → HPN May 8, 17:40 UTCMay 8, 19:30 UTC1h 50m
2026-05-08 EJA780 CHO → HPN May 8, 16:35 UTCMay 8, 16:50 UTC15m
2026-05-08 EJA780 CHO → HPN May 8, 15:05 UTCMay 8, 15:50 UTC45m
2026-05-03 EJA780 CHO → HPN May 3, 11:50 UTCMay 3, 12:25 UTC35m
2026-05-02 EJA780 CHO → HPN May 2, 23:00 UTCMay 2, 23:45 UTC45m
2026-04-26 EJA780 CHO → HPN Apr 26, 21:30 UTCApr 26, 23:05 UTC1h 35m
2026-04-26 EJA780 CHO → HPN Apr 26, 16:15 UTCApr 26, 20:00 UTC3h 46m
2026-04-25 EJA780 CHO → HPN Apr 25, 22:10 UTCApr 25, 22:25 UTC15m
2026-04-25 EJA780 CHO → HPN Apr 25, 03:20 UTCApr 25, 04:00 UTC40m
2026-04-24 EJA780 CHO → HPN Apr 24, 22:05 UTCApr 24, 23:00 UTC55m
2026-04-24 EJA780 CHO → HPN Apr 24, 20:30 UTCApr 24, 21:10 UTC40m
2026-04-24 EJA780 CHO → HPN Apr 24, 19:00 UTCApr 24, 19:15 UTC15m
2026-04-24 EJA780 CHO → HPN Apr 24, 16:40 UTCApr 24, 17:25 UTC45m
2026-04-24 EJA780 CHO → HPN Apr 24, 01:15 UTCApr 24, 02:05 UTC50m

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

Mode-S AA91F5 frequently asked

What is Mode-S code AA91F5?
AA91F5 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N780QS.
Where is Mode-S AA91F5 registered?
Mode-S code AA91F5 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 AA91F5 broadcasting right now?
No active broadcast right now. Last signal was 7d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AA91F5, octal 52510765, decimal 11,178,485.
What flights does AA91F5 operate?
Mode-S AA91F5 has broadcast 2 distinct callsigns, including EJA780, N780QS.