sensors Mode-S transponder
A360B7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3169J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A360B7
- Octal
- 50660267
- Decimal
- 10,707,127
- Country
- US
- Tail
- N3169J
- Type
- BCS3
- Flights observed
- 288
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A360B7 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 |
|---|---|---|---|
| JBU2321 | JetBlue Airways | 6 | 2026-04-18 |
| JBU203 | JetBlue Airways | 5 | 2026-06-01 |
| JBU793 | - | 4 | 2026-07-09 |
| JBU638 | - | 4 | 2026-07-06 |
| JBU2665 | - | 4 | 2026-07-08 |
| JBU2230 | - | 4 | 2026-07-05 |
| JBU1352 | - | 4 | 2026-06-24 |
| JBU1048 | - | 4 | 2026-06-20 |
| JBU822 | JetBlue Airways | 3 | 2026-04-18 |
| JBU641 | - | 3 | 2026-07-06 |
| JBU640 | - | 3 | 2026-07-06 |
| JBU394 | - | 3 | 2026-07-09 |
| JBU2722 | JetBlue Airways | 3 | 2026-04-29 |
| JBU2601 | - | 3 | 2026-06-21 |
| JBU249 | - | 3 | 2026-07-10 |
| JBU2184 | JetBlue Airways | 3 | 2026-07-07 |
| JBU2121 | JetBlue Airways | 3 | 2026-06-16 |
| JBU1822 | JetBlue Airways | 3 | 2026-05-07 |
| JBU1044 | - | 3 | 2026-04-13 |
| JBU970 | JetBlue Airways | 2 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1174 | BNA → JFK | Jul 13, 23:04 UTC | Jul 14, 03:45 UTC | 4h 42m |
| 2026-07-13 | JBU1173 | JFK → BNA | Jul 13, 19:51 UTC | Jul 14, 03:45 UTC | 7h 55m |
| 2026-07-13 | JBU254 | DCA → JFK | Jul 13, 10:27 UTC | Jul 14, 03:45 UTC | 17h 19m |
| 2026-07-12 | JBU1054 | - | Jul 12, 17:52 UTC | Jul 13, 17:45 UTC | 23h 54m |
| 2026-07-12 | JBU845 | BOS → SYR | Jul 12, 02:11 UTC | Jul 13, 00:55 UTC | 22h 45m |
| 2026-07-11 | JBU1324 | BOS → MVY | Jul 11, 13:36 UTC | Jul 12, 11:45 UTC | 22h 10m |
| 2026-07-10 | JBU2785 | JFK → RDU | Jul 10, 19:50 UTC | Jul 11, 19:45 UTC | 23h 56m |
| 2026-07-10 | JBU2785 | JFK → RDU | Jul 10, 19:50 UTC | Jul 10, 21:05 UTC | 1h 15m |
| 2026-07-10 | JBU142 | SAV → JFK | Jul 10, 15:15 UTC | Jul 10, 16:50 UTC | 1h 35m |
| 2026-07-10 | JBU249 | BOS → SAV | Jul 10, 11:40 UTC | Jul 10, 13:45 UTC | 2h 5m |
| 2026-07-09 | JBU394 | DEN → BOS | Jul 9, 22:25 UTC | Jul 10, 02:05 UTC | 3h 40m |
| 2026-07-09 | JBU793 | - | Jul 9, 15:40 UTC | Jul 9, 19:55 UTC | 4h 15m |
| 2026-07-08 | JBU1351 | ACK → BOS | Jul 8, 22:02 UTC | Jul 9, 21:45 UTC | 23h 43m |
| 2026-07-08 | JBU2665 | ACK → HPN | Jul 8, 18:04 UTC | Jul 9, 17:45 UTC | 23h 41m |
| 2026-07-08 | JBU484 | RDU → BOS | Jul 8, 13:24 UTC | Jul 9, 02:35 UTC | 13h 12m |
| 2026-07-08 | JBU2186 | PIT → BOS | Jul 8, 01:03 UTC | Jul 8, 23:30 UTC | 22h 28m |
| 2026-07-07 | JBU2184 | RDU → BOS | Jul 7, 18:54 UTC | Jul 8, 16:40 UTC | 21h 47m |
| 2026-07-07 | JBU2255 | BOS → DCA | Jul 7, 10:48 UTC | Jul 8, 08:25 UTC | 21h 38m |
| 2026-07-06 | JBU640 | CLE → BOS | Jul 6, 21:53 UTC | Jul 7, 20:45 UTC | 22h 53m |
| 2026-07-06 | JBU641 | BOS → CLE | Jul 6, 18:55 UTC | Jul 7, 17:20 UTC | 22h 26m |
| 2026-07-06 | JBU641 | BOS → CLE | Jul 6, 18:55 UTC | Jul 6, 20:25 UTC | 1h 30m |
| 2026-07-06 | JBU2040 | - | Jul 6, 16:20 UTC | Jul 6, 17:40 UTC | 1h 20m |
| 2026-07-06 | JBU2041 | - | Jul 6, 11:25 UTC | Jul 6, 13:00 UTC | 1h 35m |
| 2026-07-06 | JBU638 | BOS → BOS | Jul 6, 10:25 UTC | Jul 6, 10:30 UTC | 5m |
| 2026-07-06 | JBU638 | BOS → BOS | Jul 6, 08:35 UTC | Jul 6, 08:40 UTC | 5m |
| 2026-07-06 | JBU638 | BOS → BOS | Jul 6, 07:30 UTC | Jul 6, 07:35 UTC | 5m |
| 2026-07-05 | JBU638 | - | Jul 5, 23:25 UTC | Jul 6, 02:55 UTC | 3h 30m |
| 2026-07-05 | JBU639 | - | Jul 5, 18:20 UTC | Jul 5, 22:10 UTC | 3h 50m |
| 2026-07-05 | JBU2230 | - | Jul 5, 15:05 UTC | Jul 5, 17:00 UTC | 1h 55m |
| 2026-07-04 | JBU1336 | DTW → BOS | Jul 4, 21:07 UTC | Jul 5, 19:45 UTC | 22h 39m |
| 2026-07-04 | JBU837 | BOS → DTW | Jul 4, 18:10 UTC | Jul 5, 15:45 UTC | 21h 36m |
| 2026-07-03 | JBU22 | PBI → BOS | Jul 3, 22:02 UTC | Jul 4, 21:45 UTC | 23h 43m |
| 2026-07-03 | JBU2786 | RDU → JFK | Jul 3, 15:13 UTC | Jul 4, 13:45 UTC | 22h 33m |
| 2026-07-02 | JBU678 | JAX → JFK | Jul 2, 22:50 UTC | Jul 3, 20:30 UTC | 21h 40m |
| 2026-07-02 | JBU1273 | JFK → CHS | Jul 2, 12:11 UTC | Jul 3, 11:10 UTC | 23h 0m |
| 2026-07-01 | JBU36 | STI → JFK | Jul 1, 19:53 UTC | Jul 2, 19:45 UTC | 23h 52m |
| 2026-07-01 | JBU237 | JFK → STI | Jul 1, 14:20 UTC | Jul 2, 13:45 UTC | 23h 26m |
| 2026-07-01 | JBU2769 | - | Jul 1, 10:30 UTC | Jul 1, 11:45 UTC | 1h 15m |
| 2026-07-01 | JBU2768 | JFK → CLE | Jul 1, 03:00 UTC | Jul 1, 04:10 UTC | 1h 10m |
| 2026-07-01 | JBU520 | ATL → JFK | Jul 1, 00:00 UTC | Jul 1, 01:50 UTC | 1h 50m |
| 2026-06-30 | JBU897 | BOS → ATL | Jun 30, 18:55 UTC | Jun 30, 21:00 UTC | 2h 5m |
| 2026-06-30 | JBU2230 | - | Jun 30, 14:35 UTC | Jun 30, 16:25 UTC | 1h 50m |
| 2026-06-30 | JBU2229 | - | Jun 30, 11:25 UTC | Jun 30, 13:25 UTC | 2h 0m |
| 2026-06-30 | JBU1854 | ADW → BOS | Jun 30, 01:14 UTC | Jun 30, 02:15 UTC | 1h 1m |
| 2026-06-29 | JBU1955 | - | Jun 29, 22:59 UTC | Jun 30, 00:09 UTC | 1h 10m |
| 2026-06-29 | JBU494 | - | Jun 29, 17:59 UTC | Jun 29, 21:30 UTC | 3h 30m |
| 2026-06-29 | JBU493 | BOS → DEN | Jun 29, 11:14 UTC | Jun 29, 15:14 UTC | 4h 0m |
| 2026-06-28 | JBU1595 | - | Jun 28, 18:59 UTC | Jun 28, 22:49 UTC | 3h 50m |
| 2026-06-28 | JBU1595 | BOS → PUJ | Jun 28, 18:57 UTC | Jun 29, 17:45 UTC | 22h 48m |
| 2026-06-28 | JBU2454 | DCA → BOS | Jun 28, 15:34 UTC | Jun 28, 16:49 UTC | 1h 15m |
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 N3169J page for operator, model, and routing details .