sensors Mode-S transponder

AD56E0

ICAO 24-bit transponder address · allocated to United States

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

Hex
AD56E0
Octal
53253340
Decimal
11,359,968
Country
US
Tail
N959JB
Type
A321
Broadcasting now · callsign JBU396 · 10,500 ft
Flights observed
261
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Current position

AD56E0 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address AD56E0 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
JBU1829 - 9 2026-07-09
JBU373 - 8 2026-07-13
JBU771 JetBlue Airways 6 2026-05-19
JBU398 - 6 2026-07-11
JBU397 - 6 2026-07-11
JBU369 JetBlue Airways 6 2026-05-11
JBU772 JetBlue Airways 5 2026-05-17
JBU395 - 5 2026-07-14
JBU303 JetBlue Airways 5 2026-06-09
JBU2829 - 5 2026-06-27
JBU2173 JetBlue Airways 5 2026-06-27
JBU2151 JetBlue Airways 5 2026-04-29
JBU774 JetBlue Airways 4 2026-05-16
JBU494 JetBlue Airways 4 2026-04-30
JBU474 - 4 2026-07-13
JBU2129 JetBlue Airways 4 2026-06-15
JBU1347 - 4 2026-06-19
JBU870 JetBlue Airways 3 2026-04-27
JBU761 JetBlue Airways 3 2026-05-26
JBU662 JetBlue Airways 3 2026-05-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 JBU395 BOS → PDX Jul 14, 14:05 UTCJul 14, 19:25 UTC5h 20m
2026-07-13 JBU474 - Jul 13, 23:40 UTCJul 14, 00:50 UTC1h 10m
2026-07-13 JBU474 - Jul 13, 20:35 UTCJul 13, 20:45 UTC10m
2026-07-13 JBU373 - Jul 13, 18:35 UTCJul 13, 18:50 UTC15m
2026-07-13 JBU373 - Jul 13, 14:25 UTCJul 13, 17:40 UTC3h 15m
2026-07-12 JBU373 - Jul 12, 18:45 UTCJul 12, 18:55 UTC10m
2026-07-12 JBU373 - Jul 12, 14:35 UTCJul 12, 18:01 UTC3h 25m
2026-07-12 JBU373 BOS → AUA Jul 12, 14:34 UTCJul 13, 14:00 UTC23h 27m
2026-07-11 JBU398 SEA → BOS Jul 11, 21:25 UTCJul 12, 02:01 UTC4h 35m
2026-07-11 JBU397 BOS → SEA Jul 11, 13:30 UTCJul 11, 19:05 UTC5h 35m
2026-07-10 JBU396 - Jul 10, 21:20 UTCJul 11, 02:15 UTC4h 55m
2026-07-10 JBU395 BOS → PDX Jul 10, 14:10 UTCJul 10, 19:30 UTC5h 20m
2026-07-09 JBU330 SDQ → BOS Jul 9, 22:23 UTCJul 10, 22:00 UTC23h 38m
2026-07-09 JBU1829 BOS → SDQ Jul 9, 16:31 UTCJul 10, 16:00 UTC23h 29m
2026-07-09 JBU1829 - Jul 9, 16:35 UTCJul 9, 18:15 UTC1h 40m
2026-07-09 JBU1323 BOS → BOS Jul 9, 02:55 UTCJul 9, 12:45 UTC9h 50m
2026-07-08 JBU397 BOS → SEA Jul 8, 11:21 UTCJul 9, 03:25 UTC16h 5m
2026-07-08 JBU397 - Jul 8, 11:25 UTCJul 8, 16:55 UTC5h 30m
2026-07-07 JBU8366 STI → JFK Jul 7, 13:52 UTCJul 8, 12:00 UTC22h 9m
2026-07-07 JBU637 JFK → JFK Jul 7, 05:25 UTCJul 7, 17:10 UTC11h 45m
2026-07-06 JBU152 CUN → JFK Jul 6, 20:30 UTCJul 7, 00:05 UTC3h 35m
2026-07-05 JBU151 JFK → CUN Jul 5, 13:10 UTCJul 5, 16:35 UTC3h 25m
2026-07-05 JBU151 JFK → CUN Jul 5, 13:05 UTCJul 5, 16:45 UTC3h 41m
2026-07-04 JBU710 - Jul 4, 18:35 UTCJul 4, 19:30 UTC55m
2026-07-03 JBU1759 JFK → KIN Jul 3, 22:24 UTCJul 4, 19:45 UTC21h 22m
2026-07-03 JBU869 - Jul 3, 11:00 UTCJul 3, 11:55 UTC55m
2026-07-03 JBU869 JFK → PUJ Jul 3, 10:57 UTCJul 4, 08:25 UTC21h 29m
2026-07-02 JBU1936 JFK → JFK Jul 2, 20:45 UTCJul 3, 08:15 UTC11h 30m
2026-07-02 JBU510 JFK → JFK Jul 2, 09:25 UTCJul 2, 18:00 UTC8h 35m
2026-07-01 JBU1457 JFK → AUA Jul 1, 16:11 UTCJul 2, 10:05 UTC17h 54m
2026-07-01 JBU536 STI → JFK Jul 1, 10:03 UTCJul 2, 02:20 UTC16h 18m
2026-07-01 JBU1323 BOS → STI Jul 1, 03:28 UTCJul 2, 02:00 UTC22h 33m
2026-06-30 JBU398 SEA → BOS Jun 30, 19:43 UTCJul 1, 16:50 UTC21h 8m
2026-06-30 JBU398 SEA → BOS Jun 30, 19:45 UTCJul 1, 00:35 UTC4h 50m
2026-06-30 JBU397 BOS → SEA Jun 30, 11:40 UTCJun 30, 17:25 UTC5h 45m
2026-06-29 JBU395 BOS → PDX Jun 29, 14:09 UTCJun 30, 14:00 UTC23h 52m
2026-06-28 JBU330 SDQ → BOS Jun 28, 21:23 UTCJun 29, 19:39 UTC22h 17m
2026-06-28 JBU1829 - Jun 28, 16:19 UTCJun 28, 17:34 UTC1h 15m
2026-06-28 JBU1829 BOS → SDQ Jun 28, 16:15 UTCJun 29, 16:00 UTC23h 45m
2026-06-28 JBU1829 BOS → BOS Jun 28, 15:09 UTCJun 28, 15:14 UTC5m
2026-06-28 JBU1830 - Jun 28, 02:29 UTCJun 28, 13:10 UTC10h 40m
2026-06-27 JBU2829 - Jun 27, 22:15 UTCJun 27, 23:04 UTC50m
2026-06-27 JBU574 - Jun 27, 18:49 UTCJun 27, 19:00 UTC10m
2026-06-27 JBU2173 BOS → AUA Jun 27, 12:55 UTCJun 27, 17:14 UTC4h 20m
2026-06-26 JBU396 PDX → BOS Jun 26, 21:24 UTCJun 27, 02:20 UTC4h 55m
2026-06-26 JBU395 BOS → PDX Jun 26, 14:25 UTCJun 26, 20:10 UTC5h 45m
2026-06-25 JBU1829 BOS → BOS Jun 25, 16:45 UTCJun 26, 01:10 UTC8h 25m
2026-06-25 JBU2829 BOS → BOS Jun 25, 01:50 UTCJun 25, 12:40 UTC10h 50m
2026-06-24 JBU2173 BOS → AUA Jun 24, 13:00 UTCJun 24, 17:29 UTC4h 30m
2026-06-24 JBU2173 BOS → AUA Jun 24, 12:58 UTCJun 25, 11:59 UTC23h 2m

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

Mode-S AD56E0 frequently asked

What is Mode-S code AD56E0?
AD56E0 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N959JB.
Where is Mode-S AD56E0 registered?
Mode-S code AD56E0 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 AD56E0 broadcasting right now?
Yes. Mode-S AD56E0 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD56E0, octal 53253340, decimal 11,359,968.
What flights does AD56E0 operate?
Mode-S AD56E0 has broadcast 20 distinct callsigns, including JBU1829, JBU373, JBU771, JBU398, JBU397.