sensors Mode-S transponder
AD3CDF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N952JB · AIRBUS A-321 · operated by JET BLUE AIRWAYS CORP
- Hex
- AD3CDF
- Octal
- 53236337
- Decimal
- 11,353,311
- Country
- US
- Tail
- N952JB
- Type
- A321
- Flights observed
- 258
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AD3CDF 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 | - | 11 | 2026-06-15 |
| JBU1161 | JetBlue Airways | 7 | 2026-05-14 |
| JBU1004 | - | 7 | 2026-07-07 |
| JBU1 | JetBlue Airways | 7 | 2026-07-08 |
| JBU862 | JetBlue Airways | 6 | 2026-05-15 |
| JBU503 | - | 6 | 2026-06-24 |
| JBU165 | JetBlue Airways | 6 | 2026-05-13 |
| JBU1347 | JetBlue Airways | 6 | 2026-06-04 |
| JBU92 | JetBlue Airways | 5 | 2026-04-17 |
| JBU373 | JetBlue Airways | 5 | 2026-06-29 |
| JBU2173 | - | 5 | 2026-07-01 |
| JBU821 | JetBlue Airways | 4 | 2026-04-21 |
| JBU771 | JetBlue Airways | 4 | 2026-06-05 |
| JBU757 | JetBlue Airways | 4 | 2026-06-23 |
| JBU474 | - | 4 | 2026-06-29 |
| JBU391 | JetBlue Airways | 4 | 2026-04-17 |
| JBU2924 | - | 4 | 2026-06-28 |
| JBU774 | JetBlue Airways | 3 | 2026-05-30 |
| JBU74 | JetBlue Airways | 3 | 2026-04-18 |
| JBU690 | JetBlue Airways | 3 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2958 | AUA → JFK | Jul 13, 15:46 UTC | Jul 14, 03:45 UTC | 12h 0m |
| 2026-07-13 | JBU1936 | STI → JFK | Jul 13, 03:11 UTC | Jul 14, 01:45 UTC | 22h 35m |
| 2026-07-12 | JBU380 | MBJ → JFK | Jul 12, 15:52 UTC | Jul 13, 14:15 UTC | 22h 24m |
| 2026-07-12 | JBU1179 | - | Jul 12, 10:55 UTC | Jul 12, 13:25 UTC | 2h 30m |
| 2026-07-12 | JBU1179 | JFK → MBJ | Jul 12, 10:53 UTC | Jul 13, 09:45 UTC | 22h 53m |
| 2026-07-11 | JBU105 | EWR → FLL | Jul 11, 12:16 UTC | Jul 12, 11:45 UTC | 23h 30m |
| 2026-07-11 | JBU8301 | JFK → EWR | Jul 11, 09:10 UTC | Jul 11, 09:40 UTC | 30m |
| 2026-07-11 | JBU8301 | JFK → EWR | Jul 11, 09:10 UTC | Jul 12, 06:10 UTC | 21h 1m |
| 2026-07-10 | JBU602 | - | Jul 10, 16:40 UTC | Jul 10, 18:55 UTC | 2h 15m |
| 2026-07-09 | JBU1692 | LIR → JFK | Jul 9, 20:15 UTC | Jul 10, 18:55 UTC | 22h 40m |
| 2026-07-09 | JBU264 | SEA → JFK | Jul 9, 05:59 UTC | Jul 10, 01:55 UTC | 19h 56m |
| 2026-07-08 | JBU1 | JFK → FLL | Jul 8, 11:10 UTC | Jul 8, 13:30 UTC | 2h 20m |
| 2026-07-08 | JBU1 | JFK → FLL | Jul 8, 11:07 UTC | Jul 9, 09:45 UTC | 22h 38m |
| 2026-07-07 | JBU1004 | - | Jul 7, 02:30 UTC | Jul 7, 03:50 UTC | 1h 20m |
| 2026-07-07 | JBU1004 | - | Jul 7, 00:10 UTC | Jul 7, 00:20 UTC | 10m |
| 2026-07-06 | JBU1603 | - | Jul 6, 16:55 UTC | Jul 6, 20:25 UTC | 3h 30m |
| 2026-07-06 | JBU8428 | BOS → SYR | Jul 6, 14:00 UTC | Jul 6, 14:45 UTC | 45m |
| 2026-07-05 | JBU1691 | JFK → LIR | Jul 5, 14:01 UTC | Jul 6, 05:20 UTC | 15h 19m |
| 2026-07-04 | JBU152 | CUN → JFK | Jul 4, 18:38 UTC | Jul 5, 15:45 UTC | 21h 8m |
| 2026-07-03 | JBU280 | MBJ → JFK | Jul 3, 23:02 UTC | Jul 4, 21:45 UTC | 22h 43m |
| 2026-07-03 | JBU279 | - | Jul 3, 16:10 UTC | Jul 3, 18:25 UTC | 2h 15m |
| 2026-07-03 | JBU279 | JFK → MBJ | Jul 3, 16:08 UTC | Jul 4, 15:45 UTC | 23h 37m |
| 2026-07-02 | JBU2023 | BOS → STI | Jul 2, 18:37 UTC | Jul 3, 17:45 UTC | 23h 9m |
| 2026-07-02 | JBU2023 | - | Jul 2, 18:40 UTC | Jul 2, 19:35 UTC | 55m |
| 2026-07-02 | JBU1830 | - | Jul 2, 01:55 UTC | Jul 2, 12:55 UTC | 11h 0m |
| 2026-07-01 | JBU2173 | - | Jul 1, 16:20 UTC | Jul 1, 16:40 UTC | 20m |
| 2026-07-01 | JBU2173 | BOS → AUA | Jul 1, 12:20 UTC | Jul 2, 11:45 UTC | 23h 25m |
| 2026-07-01 | JBU2173 | - | Jul 1, 12:20 UTC | Jul 1, 15:40 UTC | 3h 20m |
| 2026-06-30 | JBU396 | PDX → BOS | Jun 30, 21:25 UTC | Jul 1, 02:15 UTC | 4h 50m |
| 2026-06-30 | JBU395 | BOS → PDX | Jun 30, 14:15 UTC | Jun 30, 19:50 UTC | 5h 35m |
| 2026-06-29 | JBU373 | BOS → AUA | Jun 29, 18:39 UTC | Jun 29, 19:05 UTC | 25m |
| 2026-06-29 | JBU373 | BOS → AUA | Jun 29, 14:39 UTC | Jun 30, 13:45 UTC | 23h 7m |
| 2026-06-29 | JBU373 | BOS → AUA | Jun 29, 14:39 UTC | Jun 29, 17:59 UTC | 3h 20m |
| 2026-06-29 | JBU474 | - | Jun 29, 00:05 UTC | Jun 29, 01:00 UTC | 55m |
| 2026-06-28 | JBU474 | - | Jun 28, 20:45 UTC | Jun 28, 20:54 UTC | 10m |
| 2026-06-28 | JBU2924 | STI → BOS | Jun 28, 01:15 UTC | Jun 28, 20:54 UTC | 19h 40m |
| 2026-06-27 | JBU2924 | JFK → BOS | Jun 27, 20:34 UTC | Jun 28, 04:35 UTC | 8h 0m |
| 2026-06-26 | JBU636 | STI → JFK | Jun 26, 23:45 UTC | Jun 27, 21:15 UTC | 21h 30m |
| 2026-06-26 | JBU2023 | BOS → JFK | Jun 26, 18:24 UTC | Jun 27, 02:55 UTC | 8h 30m |
| 2026-06-25 | JBU1830 | - | Jun 25, 20:34 UTC | Jun 26, 12:59 UTC | 16h 25m |
| 2026-06-25 | JBU209 | JFK → JFK | Jun 25, 09:25 UTC | Jun 25, 17:44 UTC | 8h 20m |
| 2026-06-24 | JBU1004 | - | Jun 24, 22:19 UTC | Jun 24, 23:04 UTC | 45m |
| 2026-06-24 | JBU1004 | - | Jun 24, 19:34 UTC | Jun 24, 19:49 UTC | 15m |
| 2026-06-24 | JBU503 | - | Jun 24, 17:25 UTC | Jun 24, 17:40 UTC | 15m |
| 2026-06-24 | JBU503 | - | Jun 24, 14:20 UTC | Jun 24, 14:50 UTC | 30m |
| 2026-06-24 | JBU2904 | - | Jun 24, 11:50 UTC | Jun 24, 12:25 UTC | 35m |
| 2026-06-24 | JBU2904 | - | Jun 24, 09:09 UTC | Jun 24, 09:24 UTC | 15m |
| 2026-06-23 | JBU757 | JFK → AUA | Jun 23, 11:46 UTC | Jun 24, 09:24 UTC | 21h 39m |
| 2026-06-23 | JBU757 | JFK → AUA | Jun 23, 11:49 UTC | Jun 23, 15:19 UTC | 3h 30m |
| 2026-06-22 | JBU536 | STI → JFK | Jun 22, 10:15 UTC | Jun 23, 01:04 UTC | 14h 50m |
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 N952JB page for operator, model, and routing details .