Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A29A6D

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N267QS · BOMBARDIER CL-600 Challenger · operated by AIRKAY LLC, AWC 2018 AVIATION HOLDINGS LLC, AXON ENTERPRISE INC, BANK OF UTAH TRUSTEE, BOARDMAN PARTNERS AVIATION LLC, GFO ASSET MANAGEMENT LLC

Hex
A29A6D
Octal
50515155
Decimal
10,656,365
Country
US
Tail
N267QS
Type
CL60
No current signal · last broadcast 3d ago
Flights observed
90
Distinct callsigns
2
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S A29A6D.

Country allocation

The ICAO 24-bit address A29A6D 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
EJA267 NetJets 75 2026-05-30
N267QS - 15 2026-05-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 EJA267 MVY → BED May 30, 05:35 UTCMay 30, 10:25 UTC4h 50m
2026-05-30 EJA267 MVY → BED May 30, 01:10 UTCMay 30, 03:00 UTC1h 50m
2026-05-29 EJA267 MVY → BED May 29, 06:25 UTCMay 29, 07:15 UTC50m
2026-05-28 EJA267 MVY → BED May 28, 22:50 UTCMay 28, 23:55 UTC1h 5m
2026-05-26 EJA267 MVY → BED May 26, 23:29 UTCMay 27, 00:14 UTC45m
2026-05-26 EJA267 MVY → BED May 26, 21:09 UTCMay 26, 21:25 UTC15m
2026-05-26 EJA267 MVY → BED May 26, 19:15 UTCMay 26, 19:34 UTC20m
2026-05-26 EJA267 MVY → BED May 26, 16:50 UTCMay 26, 17:35 UTC45m
2026-05-26 EJA267 MVY → BED May 26, 15:00 UTCMay 26, 15:24 UTC25m
2026-05-25 EJA267 MVY → BED May 25, 19:20 UTCMay 25, 22:55 UTC3h 35m
2026-05-25 EJA267 MVY → BED May 25, 13:05 UTCMay 25, 16:50 UTC3h 45m
2026-05-24 EJA267 MVY → BED May 24, 21:10 UTCMay 24, 21:45 UTC35m
2026-05-22 EJA267 MVY → BED May 22, 20:55 UTCMay 22, 23:25 UTC2h 30m
2026-05-22 N267QS - May 22, 17:15 UTCMay 22, 18:00 UTC45m
2026-05-22 N267QS - May 22, 12:40 UTCMay 22, 13:15 UTC35m
2026-05-21 N267QS - May 21, 22:00 UTCMay 21, 22:10 UTC10m
2026-05-21 N267QS - May 21, 20:25 UTCMay 21, 20:55 UTC30m
2026-05-21 N267QS - May 21, 16:55 UTCMay 21, 18:20 UTC1h 25m
2026-05-21 N267QS - May 21, 14:30 UTCMay 21, 14:40 UTC10m
2026-05-20 N267QS - May 20, 19:20 UTCMay 20, 19:30 UTC10m
2026-05-20 N267QS - May 20, 14:10 UTCMay 20, 15:30 UTC1h 20m
2026-05-19 EJA267 MVY → BED May 19, 20:40 UTCMay 19, 21:10 UTC30m
2026-05-19 EJA267 MVY → BED May 19, 15:15 UTCMay 19, 19:25 UTC4h 10m
2026-05-18 EJA267 MVY → BED May 18, 20:15 UTCMay 18, 20:40 UTC25m
2026-05-18 EJA267 MVY → BED May 18, 17:05 UTCMay 18, 19:00 UTC1h 54m
2026-05-18 EJA267 MVY → BED May 18, 12:15 UTCMay 18, 14:45 UTC2h 30m
2026-05-17 EJA267 MVY → BED May 17, 21:35 UTCMay 17, 22:20 UTC45m
2026-05-17 EJA267 MVY → BED May 17, 19:05 UTCMay 17, 19:55 UTC50m
2026-05-17 EJA267 MVY → BED May 17, 14:55 UTCMay 17, 15:35 UTC40m
2026-05-16 EJA267 MVY → BED May 16, 17:15 UTCMay 16, 18:05 UTC50m
2026-05-15 EJA267 MVY → BED May 15, 16:20 UTCMay 15, 18:05 UTC1h 45m
2026-05-14 EJA267 MVY → BED May 14, 17:15 UTCMay 14, 20:30 UTC3h 15m
2026-05-13 EJA267 MVY → BED May 13, 22:30 UTCMay 14, 01:55 UTC3h 25m
2026-05-13 EJA267 MVY → BED May 13, 02:05 UTCMay 13, 03:10 UTC1h 5m
2026-05-12 EJA267 MVY → BED May 12, 17:15 UTCMay 12, 21:50 UTC4h 35m
2026-05-11 EJA267 MVY → BED May 11, 17:45 UTCMay 11, 20:25 UTC2h 40m
2026-05-11 EJA267 MVY → BED May 11, 10:20 UTCMay 11, 14:45 UTC4h 25m
2026-05-10 EJA267 MVY → BED May 10, 15:49 UTCMay 10, 16:25 UTC35m
2026-05-08 EJA267 MVY → BED May 8, 22:50 UTCMay 9, 03:40 UTC4h 50m
2026-05-08 EJA267 MVY → BED May 8, 04:09 UTCMay 8, 05:39 UTC1h 30m
2026-05-08 EJA267 MVY → BED May 8, 01:29 UTCMay 8, 02:24 UTC55m
2026-05-06 EJA267 MVY → BED May 6, 21:15 UTCMay 7, 00:25 UTC3h 10m
2026-05-06 EJA267 MVY → BED May 6, 18:35 UTCMay 6, 18:50 UTC15m
2026-05-05 EJA267 MVY → BED May 5, 23:15 UTCMay 6, 01:30 UTC2h 15m
2026-05-05 EJA267 MVY → BED May 5, 20:05 UTCMay 5, 20:30 UTC25m
2026-05-05 EJA267 MVY → BED May 5, 18:20 UTCMay 5, 19:00 UTC40m
2026-05-05 EJA267 MVY → BED May 5, 02:25 UTCMay 5, 02:35 UTC10m
2026-05-02 EJA267 MVY → BED May 2, 21:25 UTCMay 2, 23:50 UTC2h 25m
2026-05-02 EJA267 MVY → BED May 2, 19:55 UTCMay 2, 20:40 UTC45m
2026-05-01 EJA267 MVY → BED May 1, 17:40 UTCMay 1, 21:20 UTC3h 40m

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

Mode-S A29A6D frequently asked

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