Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ADDADB

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N992JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP

Hex
ADDADB
Octal
53355333
Decimal
11,393,755
Country
US
Tail
N992JB
Type
A321
Broadcasting now · callsign JBU923 · 34,000 ft
Flights observed
273
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Current position

ADDADB is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address ADDADB 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 20 distinct

Callsign Airline Flights Last seen
JBU416 - 10 2026-07-11
JBU1997 JetBlue Airways 9 2026-04-18
JBU778 - 6 2026-07-16
JBU1756 JetBlue Airways 6 2026-05-16
JBU957 JetBlue Airways 5 2026-05-16
JBU833 - 5 2026-07-17
JBU733 - 5 2026-07-16
JBU607 JetBlue Airways 5 2026-05-15
JBU423 - 5 2026-06-24
JBU373 JetBlue Airways 5 2026-05-30
JBU15 JetBlue Airways 5 2026-06-14
JBU1388 - 5 2026-06-28
JBU134 - 5 2026-07-17
JBU919 JetBlue Airways 4 2026-05-06
JBU615 JetBlue Airways 4 2026-06-26
JBU578 JetBlue Airways 4 2026-05-15
JBU424 - 4 2026-06-18
JBU223 - 4 2026-07-14
JBU2178 JetBlue Airways 4 2026-04-17
JBU2077 JetBlue Airways 4 2026-05-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 JBU216 SFO → JFK Jul 17, 20:27 UTCJul 18, 04:45 UTC8h 19m
2026-07-17 JBU833 BOS → SFO Jul 17, 12:35 UTCJul 17, 18:15 UTC5h 40m
2026-07-17 JBU833 BOS → SFO Jul 17, 12:34 UTCJul 18, 04:45 UTC16h 12m
2026-07-17 JBU833 BOS → BOS Jul 17, 11:55 UTCJul 17, 12:00 UTC5m
2026-07-17 JBU134 BOS → BOS Jul 17, 11:15 UTCJul 17, 11:20 UTC5m
2026-07-17 JBU134 - Jul 17, 05:04 UTCJul 17, 10:10 UTC5h 5m
2026-07-16 JBU733 BOS → SFO Jul 16, 21:19 UTCJul 17, 02:59 UTC5h 40m
2026-07-16 JBU778 LAS → BOS Jul 16, 04:35 UTCJul 17, 02:45 UTC22h 10m
2026-07-16 JBU778 LAS → BOS Jul 16, 04:35 UTCJul 16, 09:20 UTC4h 45m
2026-07-15 JBU1211 JFK → LAS Jul 15, 21:05 UTCJul 16, 01:35 UTC4h 30m
2026-07-15 JBU1511 JFK → LAS Jul 15, 02:47 UTCJul 15, 22:45 UTC19h 58m
2026-07-14 JBU324 LAX → JFK Jul 14, 18:43 UTCJul 15, 16:45 UTC22h 2m
2026-07-14 JBU223 JFK → LAX Jul 14, 11:40 UTCJul 14, 16:30 UTC4h 50m
2026-07-14 JBU223 JFK → LAX Jul 14, 11:40 UTCJul 15, 07:20 UTC19h 40m
2026-07-13 JBU924 - Jul 13, 22:30 UTCJul 14, 03:45 UTC5h 15m
2026-07-13 JBU1487 BOS → LAX Jul 13, 15:40 UTCJul 13, 20:45 UTC5h 5m
2026-07-13 JBU1034 - Jul 13, 08:05 UTCJul 13, 13:20 UTC5h 15m
2026-07-13 JBU1633 - Jul 13, 00:45 UTCJul 13, 06:30 UTC5h 45m
2026-07-12 JBU988 - Jul 12, 17:01 UTCJul 12, 22:20 UTC5h 20m
2026-07-12 JBU123 JFK → LAX Jul 12, 10:10 UTCJul 12, 15:10 UTC5h 0m
2026-07-11 JBU416 - Jul 11, 22:55 UTCJul 12, 04:01 UTC5h 5m
2026-07-11 JBU1633 BOS → SFO Jul 11, 00:58 UTCJul 12, 00:40 UTC23h 43m
2026-07-10 JBU1734 - Jul 10, 17:55 UTCJul 10, 23:10 UTC5h 15m
2026-07-10 JBU1734 SFO → BOS Jul 10, 17:54 UTCJul 11, 16:45 UTC22h 52m
2026-07-10 JBU115 JFK → SFO Jul 10, 10:15 UTCJul 10, 16:10 UTC5h 55m
2026-07-09 JBU1487 BOS → LAX Jul 9, 15:16 UTCJul 10, 14:45 UTC23h 29m
2026-07-09 JBU1487 BOS → LAX Jul 9, 15:20 UTCJul 9, 21:00 UTC5h 40m
2026-07-09 JBU1034 - Jul 9, 07:05 UTCJul 9, 12:05 UTC5h 0m
2026-07-08 JBU1633 - Jul 8, 23:15 UTCJul 9, 05:10 UTC5h 55m
2026-07-08 JBU923 JFK → LAX Jul 8, 02:21 UTCJul 9, 00:45 UTC22h 25m
2026-07-07 JBU189 JFK → SAN Jul 7, 12:31 UTCJul 8, 07:30 UTC19h 0m
2026-07-07 JBU189 - Jul 7, 12:35 UTCJul 7, 17:30 UTC4h 55m
2026-07-07 JBU16 SFO → JFK Jul 7, 05:50 UTCJul 7, 10:50 UTC5h 0m
2026-07-06 JBU415 JFK → SFO Jul 6, 21:55 UTCJul 7, 04:10 UTC6h 15m
2026-07-05 JBU324 - Jul 5, 18:50 UTCJul 6, 00:00 UTC5h 10m
2026-07-04 JBU608 LAS → FLL Jul 4, 07:40 UTCJul 4, 11:50 UTC4h 10m
2026-07-04 JBU608 LAS → FLL Jul 4, 07:39 UTCJul 4, 19:00 UTC11h 21m
2026-07-04 JBU777 BOS → LAS Jul 4, 00:45 UTCJul 4, 06:10 UTC5h 25m
2026-07-03 JBU123 JFK → LAX Jul 3, 10:20 UTCJul 3, 15:50 UTC5h 30m
2026-07-03 JBU123 JFK → LAX Jul 3, 10:27 UTCJul 4, 08:45 UTC22h 18m
2026-07-02 JBU416 SFO → JFK Jul 2, 22:40 UTCJul 3, 04:00 UTC5h 20m
2026-07-02 JBU1833 BOS → SFO Jul 2, 15:20 UTCJul 2, 21:00 UTC5h 40m
2026-07-02 JBU134 SFO → BOS Jul 2, 05:20 UTCJul 2, 10:30 UTC5h 10m
2026-07-01 JBU733 - Jul 1, 21:45 UTCJul 2, 03:40 UTC5h 55m
2026-07-01 JBU288 LAX → BOS Jul 1, 15:05 UTCJul 1, 20:05 UTC5h 0m
2026-07-01 JBU387 BOS → LAX Jul 1, 01:55 UTCJul 1, 07:35 UTC5h 40m
2026-06-30 JBU1333 - Jun 30, 10:40 UTCJun 30, 16:45 UTC6h 5m
2026-06-30 JBU1333 BOS → SFO Jun 30, 10:37 UTCJul 1, 07:35 UTC20h 58m
2026-06-30 JBU2120 - Jun 30, 04:05 UTCJun 30, 08:55 UTC4h 50m
2026-06-29 JBU319 - Jun 29, 20:35 UTCJun 30, 02:10 UTC5h 35m

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

Mode-S ADDADB frequently asked

What is Mode-S code ADDADB?
ADDADB is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N992JB.
Where is Mode-S ADDADB registered?
Mode-S code ADDADB 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 ADDADB broadcasting right now?
Yes. Mode-S ADDADB is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex ADDADB, octal 53355333, decimal 11,393,755.
What flights does ADDADB operate?
Mode-S ADDADB has broadcast 20 distinct callsigns, including JBU416, JBU1997, JBU778, JBU1756, JBU957.