Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AA5941

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N766QS · BOMBARDIER BD-100 Challenger 350 · operated by NETJETS SALES INC, BEDFORD TRANSPORTATION LLC, CORNELIUS JAMES M, MAVERICK AIR LLC, MURFEY MARY V

Hex
AA5941
Octal
52454501
Decimal
11,163,969
Country
US
Tail
N766QS
Type
CL35
No current signal · last broadcast 12h ago
Flights observed
108
Distinct callsigns
2
Country
US
Last broadcast
12h ago

Last known position

Most recent position reported by Mode-S AA5941.

Country allocation

The ICAO 24-bit address AA5941 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
EJA766 NetJets 101 2026-05-29
N766QS - 7 2026-05-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 EJA766 CHO → FCA May 29, 21:25 UTCMay 29, 22:15 UTC50m
2026-05-29 EJA766 CHO → FCA May 29, 18:50 UTCMay 29, 20:40 UTC1h 50m
2026-05-29 EJA766 CHO → FCA May 29, 15:20 UTCMay 29, 16:30 UTC1h 10m
2026-05-29 EJA766 CHO → FCA May 29, 13:10 UTCMay 29, 13:30 UTC20m
2026-05-29 EJA766 CHO → FCA May 29, 03:55 UTCMay 29, 07:05 UTC3h 10m
2026-05-28 EJA766 CHO → FCA May 28, 21:05 UTCMay 28, 22:30 UTC1h 25m
2026-05-28 EJA766 CHO → FCA May 28, 02:10 UTCMay 28, 04:15 UTC2h 5m
2026-05-27 EJA766 CHO → FCA May 27, 00:10 UTCMay 27, 00:49 UTC40m
2026-05-26 N766QS - May 26, 16:59 UTCMay 26, 23:10 UTC6h 10m
2026-05-24 EJA766 CHO → FCA May 24, 20:20 UTCMay 24, 21:00 UTC40m
2026-05-24 EJA766 CHO → FCA May 24, 14:30 UTCMay 24, 19:20 UTC4h 50m
2026-05-24 EJA766 CHO → FCA May 24, 12:45 UTCMay 24, 13:40 UTC55m
2026-05-23 EJA766 CHO → FCA May 23, 14:50 UTCMay 23, 16:10 UTC1h 20m
2026-05-23 EJA766 CHO → FCA May 23, 11:15 UTCMay 23, 12:25 UTC1h 10m
2026-05-22 EJA766 CHO → FCA May 22, 21:20 UTCMay 22, 21:50 UTC30m
2026-05-22 EJA766 CHO → FCA May 22, 16:30 UTCMay 22, 20:30 UTC4h 0m
2026-05-22 EJA766 CHO → FCA May 22, 13:50 UTCMay 22, 15:35 UTC1h 45m
2026-05-21 EJA766 CHO → FCA May 21, 20:00 UTCMay 21, 21:45 UTC1h 45m
2026-05-18 EJA766 CHO → FCA May 18, 18:50 UTCMay 18, 22:00 UTC3h 10m
2026-05-18 EJA766 CHO → FCA May 18, 16:45 UTCMay 18, 16:55 UTC10m
2026-05-17 EJA766 CHO → FCA May 17, 19:55 UTCMay 18, 01:35 UTC5h 40m
2026-05-17 EJA766 CHO → FCA May 17, 17:25 UTCMay 17, 18:45 UTC1h 20m
2026-05-17 EJA766 CHO → FCA May 17, 14:20 UTCMay 17, 16:05 UTC1h 45m
2026-05-16 EJA766 CHO → FCA May 16, 22:50 UTCMay 17, 00:40 UTC1h 50m
2026-05-15 EJA766 CHO → FCA May 15, 19:20 UTCMay 15, 22:45 UTC3h 25m
2026-05-15 EJA766 CHO → FCA May 15, 16:20 UTCMay 15, 17:25 UTC1h 5m
2026-05-14 EJA766 CHO → FCA May 14, 23:40 UTCMay 15, 00:30 UTC50m
2026-05-14 EJA766 CHO → FCA May 14, 21:05 UTCMay 14, 21:55 UTC50m
2026-05-14 EJA766 CHO → FCA May 14, 19:35 UTCMay 14, 20:15 UTC40m
2026-05-14 EJA766 CHO → FCA May 14, 17:55 UTCMay 14, 18:15 UTC20m
2026-05-14 EJA766 CHO → FCA May 14, 14:55 UTCMay 14, 16:50 UTC1h 55m
2026-05-13 EJA766 CHO → FCA May 13, 20:35 UTCMay 13, 22:25 UTC1h 50m
2026-05-13 EJA766 CHO → FCA May 13, 18:20 UTCMay 13, 18:45 UTC25m
2026-05-13 EJA766 CHO → FCA May 13, 14:20 UTCMay 13, 15:50 UTC1h 30m
2026-05-13 EJA766 CHO → FCA May 13, 12:35 UTCMay 13, 12:45 UTC10m
2026-05-12 EJA766 CHO → FCA May 12, 21:15 UTCMay 12, 22:01 UTC45m
2026-05-12 EJA766 CHO → FCA May 12, 19:45 UTCMay 12, 20:35 UTC50m
2026-05-12 EJA766 CHO → FCA May 12, 17:15 UTCMay 12, 18:20 UTC1h 5m
2026-05-12 N766QS - May 12, 11:30 UTCMay 12, 16:10 UTC4h 40m
2026-05-11 N766QS - May 11, 15:55 UTCMay 11, 19:35 UTC3h 41m
2026-05-11 EJA766 CHO → FCA May 11, 12:55 UTCMay 11, 13:00 UTC5m
2026-05-11 EJA766 CHO → FCA May 11, 10:10 UTCMay 11, 11:15 UTC1h 5m
2026-05-10 EJA766 CHO → FCA May 10, 00:09 UTCMay 10, 00:20 UTC10m
2026-05-09 EJA766 CHO → FCA May 9, 21:19 UTCMay 9, 22:49 UTC1h 30m
2026-05-09 EJA766 CHO → FCA May 9, 19:05 UTCMay 9, 19:35 UTC30m
2026-05-09 EJA766 CHO → FCA May 9, 00:45 UTCMay 9, 01:40 UTC55m
2026-05-08 EJA766 CHO → FCA May 8, 15:20 UTCMay 8, 23:45 UTC8h 25m
2026-05-08 EJA766 CHO → FCA May 8, 00:14 UTCMay 8, 02:44 UTC2h 30m
2026-05-07 EJA766 CHO → FCA May 7, 21:55 UTCMay 7, 22:54 UTC59m
2026-05-07 EJA766 CHO → FCA May 7, 20:25 UTCMay 7, 21:05 UTC40m

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

Mode-S AA5941 frequently asked

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