sensors Mode-S transponder

AD9D1B

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N9766B · CESSNA 208 Caravan · operated by REDDING AERO ENTERPRISES INC

Hex
AD9D1B
Octal
53316433
Decimal
11,377,947
Country
US
Tail
N9766B
Type
C208
No current signal · last broadcast 7h ago
Flights observed
149
Distinct callsigns
16
Country
US
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S AD9D1B.

Country allocation

The ICAO 24-bit address AD9D1B 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 16 distinct

Callsign Airline Flights Last seen
BXR1981 - 28 2026-05-21
BXR494 - 25 2026-07-14
BXR1984 - 19 2026-05-20
BXR1983 - 14 2026-05-21
BXR800 - 12 2026-06-12
BXR1524 - 12 2026-06-06
BXR8603 - 10 2026-06-23
BXR1523 - 9 2026-06-06
BXR1966 - 5 2026-05-15
BXR1959 - 5 2026-07-18
BXR1960 - 3 2026-07-17
BXR1461 - 2 2026-05-19
BX1981 - 2 2026-04-17
BXR1572 - 1 2026-05-16
BXR1571 - 1 2026-05-16
BXR1462 - 1 2026-05-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 BXR1959 - Jul 18, 00:55 UTCJul 18, 01:25 UTC30m
2026-07-17 BXR1960 - Jul 17, 20:44 UTCJul 17, 21:15 UTC30m
2026-07-17 BXR1959 - Jul 17, 00:55 UTCJul 17, 01:20 UTC25m
2026-07-16 BXR1959 - Jul 16, 16:09 UTCJul 16, 16:30 UTC20m
2026-07-16 BXR1959 - Jul 16, 01:10 UTCJul 16, 01:40 UTC30m
2026-07-15 BXR1960 - Jul 15, 16:05 UTCJul 15, 16:30 UTC25m
2026-07-15 BXR1959 - Jul 15, 01:00 UTCJul 15, 01:30 UTC30m
2026-07-14 BXR1960 - Jul 14, 14:45 UTCJul 14, 15:15 UTC30m
2026-07-14 BXR494 OAK → OAK Jul 14, 14:15 UTCJul 14, 14:20 UTC5m
2026-07-11 BXR494 - Jul 11, 09:35 UTCJul 11, 11:30 UTC1h 55m
2026-07-11 BXR494 OAK → BUR Jul 11, 07:05 UTCJul 11, 08:50 UTC1h 45m
2026-07-10 BXR494 OAK → OAK Jul 10, 07:05 UTCJul 10, 11:00 UTC3h 55m
2026-07-09 BXR494 OAK → OAK Jul 9, 06:50 UTCJul 9, 10:50 UTC4h 0m
2026-07-08 BXR494 OAK → OAK Jul 8, 07:00 UTCJul 8, 10:55 UTC3h 55m
2026-07-07 BXR494 - Jul 7, 09:05 UTCJul 7, 10:45 UTC1h 40m
2026-07-07 BXR494 OAK → BUR Jul 7, 07:00 UTCJul 7, 08:45 UTC1h 45m
2026-07-04 BXR494 BUR → OAK Jul 4, 09:00 UTCJul 4, 10:45 UTC1h 45m
2026-07-04 BXR494 OAK → BUR Jul 4, 07:00 UTCJul 4, 08:45 UTC1h 45m
2026-07-03 BXR494 WHP → OAK Jul 3, 09:10 UTCJul 3, 11:00 UTC1h 50m
2026-07-03 BXR494 OAK → BUR Jul 3, 07:05 UTCJul 3, 08:55 UTC1h 50m
2026-07-02 BXR494 WHP → OAK Jul 2, 08:50 UTCJul 2, 10:40 UTC1h 50m
2026-07-02 BXR494 OAK → BUR Jul 2, 06:45 UTCJul 2, 08:30 UTC1h 45m
2026-07-01 BXR494 - Jul 1, 08:55 UTCJul 1, 10:45 UTC1h 50m
2026-07-01 BXR494 OAK → BUR Jul 1, 06:45 UTCJul 1, 08:25 UTC1h 40m
2026-06-30 BXR494 OAK → OAK Jun 30, 07:20 UTCJun 30, 11:20 UTC4h 0m
2026-06-27 BXR494 OAK → OAK Jun 27, 07:24 UTCJun 27, 11:25 UTC4h 0m
2026-06-26 BXR494 OAK → OAK Jun 26, 07:10 UTCJun 26, 11:05 UTC3h 55m
2026-06-25 BXR494 BUR → OAK Jun 25, 09:05 UTCJun 25, 10:55 UTC1h 50m
2026-06-25 BXR494 OAK → BUR Jun 25, 06:50 UTCJun 25, 08:40 UTC1h 50m
2026-06-24 BXR494 - Jun 24, 09:29 UTCJun 24, 11:09 UTC1h 40m
2026-06-24 BXR494 OAK → BUR Jun 24, 07:20 UTCJun 24, 09:15 UTC1h 55m
2026-06-23 BXR8603 - Jun 23, 01:00 UTCJun 23, 01:20 UTC20m
2026-06-22 BXR8603 OAK → STS Jun 22, 21:40 UTCJun 22, 21:59 UTC20m
2026-06-20 BXR8603 - Jun 20, 00:49 UTCJun 20, 01:09 UTC20m
2026-06-19 BXR8603 - Jun 19, 17:14 UTCJun 19, 17:29 UTC15m
2026-06-19 BXR8603 - Jun 19, 00:59 UTCJun 19, 01:19 UTC20m
2026-06-18 BXR8603 - Jun 18, 14:40 UTCJun 18, 15:00 UTC20m
2026-06-18 BXR8603 - Jun 18, 00:50 UTCJun 18, 01:15 UTC25m
2026-06-17 BXR8603 - Jun 17, 23:20 UTCJun 17, 23:40 UTC20m
2026-06-16 BXR494 BUR → OAK Jun 16, 09:40 UTCJun 16, 11:30 UTC1h 50m
2026-06-16 BXR494 OAK → BUR Jun 16, 07:09 UTCJun 16, 09:10 UTC2h 0m
2026-06-13 BXR8603 - Jun 13, 00:55 UTCJun 13, 01:15 UTC20m
2026-06-12 BXR8603 - Jun 12, 18:40 UTCJun 12, 19:25 UTC45m
2026-06-12 BXR800 - Jun 12, 16:20 UTCJun 12, 17:05 UTC45m
2026-06-08 BXR800 - Jun 8, 20:25 UTCJun 8, 20:40 UTC15m
2026-06-06 BXR1524 MHR → RDD Jun 6, 15:15 UTCJun 6, 15:59 UTC45m
2026-06-06 BXR1523 - Jun 6, 00:05 UTCJun 6, 00:55 UTC50m
2026-06-03 BXR1524 MHR → RDD Jun 3, 15:20 UTCJun 3, 16:10 UTC50m
2026-06-03 BXR1523 - Jun 3, 00:05 UTCJun 3, 00:55 UTC50m
2026-06-02 BXR1524 MHR → RDD Jun 2, 14:10 UTCJun 2, 15:00 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 N9766B page for operator, model, and routing details .

Mode-S AD9D1B frequently asked

What is Mode-S code AD9D1B?
AD9D1B is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N9766B.
Where is Mode-S AD9D1B registered?
Mode-S code AD9D1B 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 AD9D1B broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD9D1B, octal 53316433, decimal 11,377,947.
What flights does AD9D1B operate?
Mode-S AD9D1B has broadcast 16 distinct callsigns, including BXR1981, BXR494, BXR1984, BXR1983, BXR800.