sensors Mode-S transponder
A38B84
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3276J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS
- Hex
- A38B84
- Octal
- 50705604
- Decimal
- 10,718,084
- Country
- US
- Tail
- N3276J
- Type
- BCS3
- Flights observed
- 285
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A38B84 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 |
|---|---|---|---|
| JBU2152 | - | 5 | 2026-07-10 |
| JBU80 | - | 4 | 2026-07-05 |
| JBU379 | JetBlue Airways | 4 | 2026-05-09 |
| JBU2854 | JetBlue Airways | 4 | 2026-05-11 |
| JBU1880 | JetBlue Airways | 4 | 2026-05-10 |
| JBU109 | - | 4 | 2026-06-25 |
| JBU907 | JetBlue Airways | 3 | 2026-06-04 |
| JBU806 | JetBlue Airways | 3 | 2026-06-18 |
| JBU776 | JetBlue Airways | 3 | 2026-04-15 |
| JBU775 | JetBlue Airways | 3 | 2026-04-15 |
| JBU625 | - | 3 | 2026-07-07 |
| JBU618 | JetBlue Airways | 3 | 2026-05-12 |
| JBU519 | - | 3 | 2026-06-30 |
| JBU359 | - | 3 | 2026-07-04 |
| JBU266 | JetBlue Airways | 3 | 2026-05-16 |
| JBU2601 | - | 3 | 2026-07-10 |
| JBU2454 | JetBlue Airways | 3 | 2026-06-17 |
| JBU2272 | JetBlue Airways | 3 | 2026-06-09 |
| JBU1888 | JetBlue Airways | 3 | 2026-05-20 |
| JBU1497 | - | 3 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2769 | CLE → JFK | Jul 13, 10:30 UTC | Jul 14, 02:50 UTC | 16h 21m |
| 2026-07-13 | JBU2768 | JFK → CLE | Jul 13, 03:15 UTC | Jul 14, 02:50 UTC | 23h 36m |
| 2026-07-13 | JBU2768 | - | Jul 13, 03:15 UTC | Jul 13, 04:30 UTC | 1h 15m |
| 2026-07-12 | JBU2510 | - | Jul 12, 15:50 UTC | Jul 13, 00:35 UTC | 8h 45m |
| 2026-07-11 | JBU609 | JFK → SDQ | Jul 11, 19:12 UTC | Jul 12, 17:10 UTC | 21h 59m |
| 2026-07-11 | JBU92 | ACK → JFK | Jul 11, 16:29 UTC | Jul 12, 04:01 UTC | 11h 32m |
| 2026-07-11 | JBU2783 | BOS → RDU | Jul 11, 01:33 UTC | Jul 11, 20:05 UTC | 18h 33m |
| 2026-07-10 | JBU2152 | SJU → TPA | Jul 10, 17:06 UTC | Jul 11, 17:00 UTC | 23h 55m |
| 2026-07-10 | JBU2601 | - | Jul 10, 12:15 UTC | Jul 10, 15:40 UTC | 3h 25m |
| 2026-07-10 | JBU2601 | HPN → SJU | Jul 10, 12:12 UTC | Jul 11, 03:01 UTC | 14h 49m |
| 2026-07-09 | JBU1047 | PHL → SJU | Jul 9, 16:59 UTC | Jul 10, 13:00 UTC | 20h 2m |
| 2026-07-08 | JBU533 | BDL → TPA | Jul 8, 21:41 UTC | Jul 9, 20:50 UTC | 23h 9m |
| 2026-07-08 | JBU534 | TPA → BDL | Jul 8, 17:50 UTC | Jul 9, 17:00 UTC | 23h 11m |
| 2026-07-08 | JBU1516 | - | Jul 8, 04:30 UTC | Jul 8, 05:00 UTC | 30m |
| 2026-07-08 | JBU1516 | JFK → SYR | Jul 8, 04:29 UTC | Jul 9, 03:00 UTC | 22h 31m |
| 2026-07-08 | JBU26 | TPA → JFK | Jul 8, 00:55 UTC | Jul 8, 03:15 UTC | 2h 20m |
| 2026-07-08 | JBU26 | TPA → JFK | Jul 8, 00:53 UTC | Jul 8, 23:00 UTC | 22h 8m |
| 2026-07-07 | JBU625 | JFK → TPA | Jul 7, 21:25 UTC | Jul 7, 23:45 UTC | 2h 20m |
| 2026-07-07 | JBU142 | - | Jul 7, 15:55 UTC | Jul 7, 17:30 UTC | 1h 35m |
| 2026-07-06 | JBU1529 | JFK → RSW | Jul 6, 12:48 UTC | Jul 7, 00:50 UTC | 12h 2m |
| 2026-07-06 | JBU1529 | JFK → RSW | Jul 6, 12:50 UTC | Jul 6, 15:15 UTC | 2h 25m |
| 2026-07-05 | JBU80 | - | Jul 5, 21:05 UTC | Jul 5, 21:45 UTC | 40m |
| 2026-07-05 | JBU80 | - | Jul 5, 16:50 UTC | Jul 5, 21:00 UTC | 4h 10m |
| 2026-07-05 | JBU80 | RNO → JFK | Jul 5, 16:47 UTC | Jul 6, 15:00 UTC | 22h 14m |
| 2026-07-04 | JBU81 | - | Jul 4, 22:20 UTC | Jul 5, 03:10 UTC | 4h 50m |
| 2026-07-04 | JBU359 | BUR → JFK | Jul 4, 05:35 UTC | Jul 4, 10:35 UTC | 5h 0m |
| 2026-07-04 | JBU359 | BUR → JFK | Jul 4, 05:34 UTC | Jul 5, 03:10 UTC | 21h 37m |
| 2026-07-03 | JBU358 | JFK → BUR | Jul 3, 21:45 UTC | Jul 4, 03:15 UTC | 5h 30m |
| 2026-07-03 | JBU80 | - | Jul 3, 14:45 UTC | Jul 3, 19:45 UTC | 5h 0m |
| 2026-07-03 | JBU81 | - | Jul 3, 01:55 UTC | Jul 3, 06:30 UTC | 4h 35m |
| 2026-07-02 | JBU2901 | JFK → FLL | Jul 2, 22:25 UTC | Jul 2, 23:30 UTC | 1h 5m |
| 2026-07-02 | JBU2725 | JFK → TPA | Jul 2, 02:06 UTC | Jul 2, 23:35 UTC | 21h 29m |
| 2026-07-01 | JBU226 | TPA → JFK | Jul 1, 21:48 UTC | Jul 2, 18:55 UTC | 21h 8m |
| 2026-07-01 | JBU125 | JFK → TPA | Jul 1, 18:00 UTC | Jul 1, 20:25 UTC | 2h 25m |
| 2026-07-01 | JBU125 | JFK → TPA | Jul 1, 17:58 UTC | Jul 2, 15:35 UTC | 21h 37m |
| 2026-06-30 | JBU1963 | HYA → JFK | Jun 30, 19:44 UTC | Jul 1, 19:00 UTC | 23h 17m |
| 2026-06-30 | JBU1964 | JFK → HYA | Jun 30, 17:50 UTC | Jul 1, 14:55 UTC | 21h 6m |
| 2026-06-30 | JBU1520 | ATL → JFK | Jun 30, 14:10 UTC | Jun 30, 16:00 UTC | 1h 50m |
| 2026-06-30 | JBU519 | JFK → ATL | Jun 30, 10:50 UTC | Jun 30, 12:30 UTC | 1h 40m |
| 2026-06-29 | JBU210 | JFK → JFK | Jun 29, 19:00 UTC | Jun 30, 03:45 UTC | 8h 46m |
| 2026-06-29 | JBU2786 | - | Jun 29, 15:14 UTC | Jun 29, 16:25 UTC | 1h 10m |
| 2026-06-29 | JBU2285 | - | Jun 29, 12:49 UTC | Jun 29, 13:59 UTC | 1h 10m |
| 2026-06-29 | JBU1198 | - | Jun 29, 10:04 UTC | Jun 29, 11:04 UTC | 1h 0m |
| 2026-06-29 | JBU1195 | - | Jun 29, 02:30 UTC | Jun 29, 03:39 UTC | 1h 10m |
| 2026-06-28 | JBU1498 | - | Jun 28, 20:25 UTC | Jun 28, 23:54 UTC | 3h 30m |
| 2026-06-28 | JBU1497 | JFK → DEN | Jun 28, 15:05 UTC | Jun 28, 18:44 UTC | 3h 40m |
| 2026-06-28 | JBU854 | PBI → JFK | Jun 28, 10:55 UTC | Jun 28, 13:19 UTC | 2h 25m |
| 2026-06-27 | JBU444 | PBI → ISP | Jun 27, 17:20 UTC | Jun 28, 17:00 UTC | 23h 40m |
| 2026-06-26 | JBU818 | JFK → BOS | Jun 26, 23:02 UTC | Jun 27, 19:55 UTC | 20h 53m |
| 2026-06-26 | JBU176 | MSY → JFK | Jun 26, 18:29 UTC | Jun 26, 21:04 UTC | 2h 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 N3276J page for operator, model, and routing details .