sensors Mode-S transponder
AD2BAA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N948JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD2BAA
- Octal
- 53225652
- Decimal
- 11,348,906
- Country
- US
- Tail
- N948JB
- Type
- A321
- Flights observed
- 228
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address AD2BAA 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 |
|---|---|---|---|
| JBU1348 | - | 10 | 2026-06-25 |
| JBU1347 | - | 10 | 2026-06-25 |
| JBU474 | - | 7 | 2026-07-06 |
| JBU724 | JetBlue Airways | 6 | 2026-07-02 |
| JBU2904 | - | 6 | 2026-07-11 |
| JBU851 | - | 5 | 2026-07-10 |
| JBU1057 | JetBlue Airways | 5 | 2026-06-10 |
| JBU395 | - | 4 | 2026-07-04 |
| JBU373 | JetBlue Airways | 4 | 2026-07-06 |
| JBU2173 | JetBlue Airways | 4 | 2026-05-24 |
| JBU1604 | - | 4 | 2026-07-11 |
| JBU1192 | JetBlue Airways | 4 | 2026-06-05 |
| JBU1058 | JetBlue Airways | 4 | 2026-05-26 |
| JBU852 | - | 3 | 2026-07-10 |
| JBU762 | JetBlue Airways | 3 | 2026-05-22 |
| JBU651 | JetBlue Airways | 3 | 2026-06-01 |
| JBU622 | JetBlue Airways | 3 | 2026-04-14 |
| JBU510 | - | 3 | 2026-07-01 |
| JBU491 | JetBlue Airways | 3 | 2026-04-26 |
| JBU274 | JetBlue Airways | 3 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1936 | STI → JFK | Jul 14, 03:00 UTC | Jul 14, 18:30 UTC | 15h 31m |
| 2026-07-13 | JBU710 | SDQ → JFK | Jul 13, 16:29 UTC | Jul 14, 14:30 UTC | 22h 2m |
| 2026-07-13 | JBU2709 | - | Jul 13, 11:35 UTC | Jul 13, 12:20 UTC | 45m |
| 2026-07-13 | JBU2709 | JFK → SDQ | Jul 13, 11:35 UTC | Jul 14, 06:15 UTC | 18h 41m |
| 2026-07-12 | JBU627 | - | Jul 12, 16:40 UTC | Jul 13, 00:25 UTC | 7h 45m |
| 2026-07-11 | JBU1604 | SJU → JFK | Jul 11, 19:22 UTC | Jul 12, 17:50 UTC | 22h 29m |
| 2026-07-11 | JBU2904 | SJU → JFK | Jul 11, 09:11 UTC | Jul 12, 08:15 UTC | 23h 5m |
| 2026-07-10 | JBU852 | CUN → JFK | Jul 10, 16:47 UTC | Jul 11, 15:10 UTC | 22h 24m |
| 2026-07-10 | JBU851 | JFK → CUN | Jul 10, 11:40 UTC | Jul 10, 14:55 UTC | 3h 15m |
| 2026-07-10 | JBU851 | JFK → CUN | Jul 10, 11:36 UTC | Jul 11, 09:25 UTC | 21h 50m |
| 2026-07-09 | JBU1159 | BOS → PHL | Jul 9, 10:33 UTC | Jul 10, 02:05 UTC | 15h 32m |
| 2026-07-08 | JBU1829 | BOS → SDQ | Jul 8, 18:06 UTC | Jul 9, 16:30 UTC | 22h 25m |
| 2026-07-08 | JBU1323 | - | Jul 8, 06:15 UTC | Jul 8, 06:45 UTC | 30m |
| 2026-07-08 | JBU1323 | BOS → STI | Jul 8, 06:13 UTC | Jul 9, 04:00 UTC | 21h 48m |
| 2026-07-08 | JBU1323 | BOS → BOS | Jul 8, 04:55 UTC | Jul 8, 05:00 UTC | 5m |
| 2026-07-07 | JBU398 | SEA → BOS | Jul 7, 22:45 UTC | Jul 8, 03:50 UTC | 5h 5m |
| 2026-07-07 | JBU397 | - | Jul 7, 11:45 UTC | Jul 7, 17:20 UTC | 5h 35m |
| 2026-07-06 | JBU474 | AUA → BOS | Jul 6, 20:42 UTC | Jul 7, 17:35 UTC | 20h 54m |
| 2026-07-06 | JBU373 | BOS → AUA | Jul 6, 14:25 UTC | Jul 7, 12:30 UTC | 22h 6m |
| 2026-07-05 | JBU474 | - | Jul 5, 23:45 UTC | Jul 6, 00:45 UTC | 1h 0m |
| 2026-07-05 | JBU474 | - | Jul 5, 20:30 UTC | Jul 5, 20:45 UTC | 15m |
| 2026-07-05 | JBU474 | AUA → BOS | Jul 5, 20:28 UTC | Jul 6, 18:05 UTC | 21h 37m |
| 2026-07-05 | JBU373 | BOS → AUA | Jul 5, 14:55 UTC | Jul 5, 19:05 UTC | 4h 10m |
| 2026-07-05 | JBU396 | PDX → BOS | Jul 5, 06:45 UTC | Jul 5, 11:30 UTC | 4h 45m |
| 2026-07-04 | JBU395 | - | Jul 4, 23:20 UTC | Jul 5, 05:00 UTC | 5h 40m |
| 2026-07-04 | JBU774 | - | Jul 4, 17:20 UTC | Jul 4, 20:55 UTC | 3h 35m |
| 2026-07-04 | JBU774 | - | Jul 4, 16:30 UTC | Jul 4, 16:45 UTC | 15m |
| 2026-07-04 | JBU1073 | JFK → BNA | Jul 4, 10:20 UTC | Jul 4, 14:30 UTC | 4h 10m |
| 2026-07-03 | JBU395 | BOS → PDX | Jul 3, 14:27 UTC | Jul 4, 11:25 UTC | 20h 58m |
| 2026-07-03 | JBU395 | - | Jul 3, 14:30 UTC | Jul 3, 17:45 UTC | 3h 15m |
| 2026-07-02 | JBU724 | STI → BOS | Jul 2, 12:45 UTC | Jul 2, 12:50 UTC | 5m |
| 2026-07-02 | JBU724 | STI → BOS | Jul 2, 09:03 UTC | Jul 3, 02:40 UTC | 17h 37m |
| 2026-07-01 | JBU724 | STI → BOS | Jul 1, 21:10 UTC | Jul 2, 12:35 UTC | 15h 25m |
| 2026-07-01 | JBU510 | SDQ → JFK | Jul 1, 14:04 UTC | Jul 2, 12:30 UTC | 22h 26m |
| 2026-07-01 | JBU510 | JFK → JFK | Jul 1, 09:15 UTC | Jul 1, 17:45 UTC | 8h 30m |
| 2026-06-30 | JBU922 | - | Jun 30, 21:50 UTC | Jun 30, 23:55 UTC | 2h 5m |
| 2026-06-30 | JBU921 | - | Jun 30, 17:00 UTC | Jun 30, 19:05 UTC | 2h 5m |
| 2026-06-29 | JBU9 | - | Jun 29, 20:35 UTC | Jun 30, 15:05 UTC | 18h 31m |
| 2026-06-29 | JBU510 | JFK → JFK | Jun 29, 09:20 UTC | Jun 29, 18:05 UTC | 8h 45m |
| 2026-06-28 | JBU454 | ONT → JFK | Jun 28, 07:44 UTC | Jun 29, 00:39 UTC | 16h 56m |
| 2026-06-27 | JBU151 | JFK → CUN | Jun 27, 13:25 UTC | Jun 28, 12:29 UTC | 23h 5m |
| 2026-06-27 | JBU151 | - | Jun 27, 13:30 UTC | Jun 27, 16:30 UTC | 3h 0m |
| 2026-06-26 | JBU279 | JFK → JFK | Jun 26, 14:29 UTC | Jun 26, 22:44 UTC | 8h 15m |
| 2026-06-25 | JBU1604 | - | Jun 25, 20:09 UTC | Jun 25, 20:45 UTC | 35m |
| 2026-06-25 | JBU1604 | - | Jun 25, 17:14 UTC | Jun 25, 17:30 UTC | 15m |
| 2026-06-25 | JBU1604 | SJU → JFK | Jun 25, 17:12 UTC | Jun 26, 16:30 UTC | 23h 18m |
| 2026-06-25 | JBU1347 | - | Jun 25, 15:15 UTC | Jun 25, 15:34 UTC | 20m |
| 2026-06-25 | JBU1347 | - | Jun 25, 12:19 UTC | Jun 25, 13:00 UTC | 40m |
| 2026-06-25 | JBU1348 | - | Jun 25, 00:24 UTC | Jun 25, 01:24 UTC | 1h 0m |
| 2026-06-24 | JBU1348 | - | Jun 24, 22:04 UTC | Jun 24, 22:14 UTC | 10m |
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 N948JB page for operator, model, and routing details .