sensors Mode-S transponder
AD846F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N970JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD846F
- Octal
- 53302157
- Decimal
- 11,371,631
- Country
- US
- Tail
- N970JB
- Type
- A321
- Flights observed
- 270
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address AD846F 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 |
|---|---|---|---|
| JBU2173 | - | 9 | 2026-07-08 |
| JBU904 | - | 7 | 2026-07-06 |
| JBU574 | - | 6 | 2026-06-21 |
| JBU2829 | - | 6 | 2026-06-20 |
| JBU58 | JetBlue Airways | 5 | 2026-06-24 |
| JBU552 | JetBlue Airways | 5 | 2026-05-18 |
| JBU2903 | - | 5 | 2026-07-06 |
| JBU1192 | JetBlue Airways | 5 | 2026-06-03 |
| JBU661 | JetBlue Airways | 4 | 2026-05-19 |
| JBU651 | JetBlue Airways | 4 | 2026-05-17 |
| JBU452 | JetBlue Airways | 4 | 2026-06-10 |
| JBU151 | JetBlue Airways | 4 | 2026-06-07 |
| JBU1348 | - | 4 | 2026-07-12 |
| JBU1 | JetBlue Airways | 4 | 2026-05-31 |
| JBU869 | - | 3 | 2026-06-25 |
| JBU855 | - | 3 | 2026-04-13 |
| JBU803 | JetBlue Airways | 3 | 2026-06-02 |
| JBU602 | - | 3 | 2026-06-30 |
| JBU57 | JetBlue Airways | 3 | 2026-06-24 |
| JBU451 | JetBlue Airways | 3 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1837 | JFK → STI | Jul 13, 23:43 UTC | Jul 14, 00:30 UTC | 48m |
| 2026-07-13 | JBU1837 | - | Jul 13, 23:45 UTC | Jul 14, 00:30 UTC | 45m |
| 2026-07-13 | JBU1604 | - | Jul 13, 19:55 UTC | Jul 13, 20:45 UTC | 50m |
| 2026-07-13 | JBU1604 | - | Jul 13, 17:30 UTC | Jul 13, 17:40 UTC | 10m |
| 2026-07-12 | JBU1348 | - | Jul 12, 23:45 UTC | Jul 13, 01:15 UTC | 1h 30m |
| 2026-07-12 | JBU1348 | - | Jul 12, 21:50 UTC | Jul 12, 22:00 UTC | 10m |
| 2026-07-12 | JBU1348 | SJU → DCA | Jul 12, 21:46 UTC | Jul 13, 17:40 UTC | 19h 55m |
| 2026-07-12 | JBU1603 | - | Jul 12, 19:45 UTC | Jul 12, 20:05 UTC | 20m |
| 2026-07-11 | JBU903 | JFK → SJU | Jul 11, 23:19 UTC | Jul 12, 20:05 UTC | 20h 47m |
| 2026-07-11 | JBU903 | JFK → SJU | Jul 11, 23:20 UTC | Jul 12, 02:40 UTC | 3h 20m |
| 2026-07-11 | JBU2709 | JFK → JFK | Jul 11, 10:55 UTC | Jul 11, 19:40 UTC | 8h 45m |
| 2026-07-10 | JBU1692 | JFK → JFK | Jul 10, 13:20 UTC | Jul 11, 01:55 UTC | 12h 35m |
| 2026-07-09 | JBU921 | JFK → NAS | Jul 9, 17:20 UTC | Jul 10, 15:45 UTC | 22h 25m |
| 2026-07-09 | JBU2110 | SDQ → JFK | Jul 9, 11:38 UTC | Jul 10, 09:35 UTC | 21h 57m |
| 2026-07-09 | JBU2110 | BOS → JFK | Jul 9, 02:25 UTC | Jul 9, 14:55 UTC | 12h 30m |
| 2026-07-08 | JBU2173 | BOS → AUA | Jul 8, 12:26 UTC | Jul 9, 03:15 UTC | 14h 49m |
| 2026-07-08 | JBU2173 | - | Jul 8, 12:30 UTC | Jul 8, 14:50 UTC | 2h 20m |
| 2026-07-07 | JBU395 | BOS → PDX | Jul 7, 14:06 UTC | Jul 8, 13:45 UTC | 23h 40m |
| 2026-07-07 | JBU395 | - | Jul 7, 14:10 UTC | Jul 7, 19:35 UTC | 5h 25m |
| 2026-07-07 | JBU2924 | BOS → BOS | Jul 7, 03:05 UTC | Jul 7, 03:10 UTC | 5m |
| 2026-07-07 | JBU2924 | - | Jul 7, 02:15 UTC | Jul 7, 03:00 UTC | 45m |
| 2026-07-06 | JBU337 | - | Jul 6, 18:20 UTC | Jul 7, 02:10 UTC | 7h 50m |
| 2026-07-06 | JBU904 | - | Jul 6, 12:05 UTC | Jul 6, 15:35 UTC | 3h 30m |
| 2026-07-06 | JBU2903 | - | Jul 6, 01:50 UTC | Jul 6, 02:10 UTC | 20m |
| 2026-07-05 | JBU2903 | - | Jul 5, 22:55 UTC | Jul 5, 23:35 UTC | 40m |
| 2026-07-05 | JBU169 | JFK → JFK | Jul 5, 12:10 UTC | Jul 5, 20:40 UTC | 8h 30m |
| 2026-07-04 | JBU60 | JFK → JFK | Jul 4, 22:00 UTC | Jul 5, 08:25 UTC | 10h 25m |
| 2026-07-04 | JBU268 | PUJ → JFK | Jul 4, 10:35 UTC | Jul 4, 19:15 UTC | 8h 40m |
| 2026-07-03 | JBU922 | NAS → JFK | Jul 3, 21:26 UTC | Jul 4, 19:25 UTC | 21h 59m |
| 2026-07-03 | JBU922 | JFK → JFK | Jul 3, 17:15 UTC | Jul 3, 23:55 UTC | 6h 40m |
| 2026-07-03 | JBU904 | - | Jul 3, 14:30 UTC | Jul 3, 15:25 UTC | 55m |
| 2026-07-03 | JBU904 | - | Jul 3, 12:00 UTC | Jul 3, 12:15 UTC | 15m |
| 2026-07-03 | JBU2903 | - | Jul 3, 01:50 UTC | Jul 3, 02:10 UTC | 20m |
| 2026-07-02 | JBU2903 | - | Jul 2, 22:55 UTC | Jul 2, 23:35 UTC | 40m |
| 2026-07-02 | JBU168 | JFK → JFK | Jul 2, 12:05 UTC | Jul 2, 20:25 UTC | 8h 20m |
| 2026-07-01 | JBU1936 | JFK → JFK | Jul 1, 23:35 UTC | Jul 2, 08:35 UTC | 9h 0m |
| 2026-07-01 | JBU168 | JFK → JFK | Jul 1, 11:55 UTC | Jul 1, 20:35 UTC | 8h 40m |
| 2026-06-30 | JBU2637 | JFK → STI | Jun 30, 20:35 UTC | Jul 1, 19:45 UTC | 23h 11m |
| 2026-06-30 | JBU2637 | - | Jun 30, 20:35 UTC | Jun 30, 21:30 UTC | 55m |
| 2026-06-30 | JBU602 | - | Jun 30, 15:10 UTC | Jun 30, 17:35 UTC | 2h 25m |
| 2026-06-30 | JBU1601 | JFK → FLL | Jun 30, 11:10 UTC | Jun 30, 13:35 UTC | 2h 25m |
| 2026-06-29 | JBU627 | JFK → POP | Jun 29, 14:54 UTC | Jun 29, 22:44 UTC | 7h 50m |
| 2026-06-29 | JBU2129 | JFK → RSW | Jun 29, 03:18 UTC | Jun 29, 22:49 UTC | 19h 32m |
| 2026-06-29 | JBU2129 | - | Jun 29, 03:20 UTC | Jun 29, 05:40 UTC | 2h 20m |
| 2026-06-28 | JBU1692 | JFK → JFK | Jun 28, 13:34 UTC | Jun 29, 00:39 UTC | 11h 5m |
| 2026-06-28 | JBU1059 | JFK → KIN | Jun 28, 02:21 UTC | Jun 29, 00:44 UTC | 22h 24m |
| 2026-06-27 | JBU503 | JFK → SJU | Jun 27, 14:25 UTC | Jun 28, 13:45 UTC | 23h 20m |
| 2026-06-27 | JBU303 | JFK → SJU | Jun 27, 01:20 UTC | Jun 27, 23:04 UTC | 21h 45m |
| 2026-06-26 | JBU662 | BGI → JFK | Jun 26, 18:28 UTC | Jun 27, 17:44 UTC | 23h 17m |
| 2026-06-26 | JBU361 | JFK → JFK | Jun 26, 12:24 UTC | Jun 26, 23:04 UTC | 10h 40m |
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 N970JB page for operator, model, and routing details .