sensors Mode-S transponder
A7946A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N588JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7946A
- Octal
- 51712152
- Decimal
- 10,982,506
- Country
- US
- Tail
- N588JB
- Type
- A320
- Flights observed
- 291
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address A7946A 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 |
|---|---|---|---|
| JBU88 | JetBlue Airways | 4 | 2026-05-02 |
| JBU281 | - | 4 | 2026-07-07 |
| JBU252 | JetBlue Airways | 4 | 2026-05-15 |
| JBU2269 | - | 4 | 2026-07-04 |
| JBU87 | JetBlue Airways | 3 | 2026-05-01 |
| JBU452 | - | 3 | 2026-06-29 |
| JBU433 | - | 3 | 2026-07-13 |
| JBU368 | JetBlue Airways | 3 | 2026-05-24 |
| JBU315 | JetBlue Airways | 3 | 2026-05-19 |
| JBU2761 | JetBlue Airways | 3 | 2026-06-03 |
| JBU2334 | - | 3 | 2026-06-25 |
| JBU2276 | - | 3 | 2026-06-26 |
| JBU2129 | - | 3 | 2026-07-10 |
| JBU2097 | - | 3 | 2026-07-14 |
| JBU2024 | - | 3 | 2026-04-13 |
| JBU1730 | JetBlue Airways | 3 | 2026-05-08 |
| JBU1715 | - | 3 | 2026-04-20 |
| JBU1529 | JetBlue Airways | 3 | 2026-05-06 |
| JBU1267 | JetBlue Airways | 3 | 2026-05-09 |
| JBU1104 | JetBlue Airways | 3 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU1905 | FLL → TPA | Jul 15, 00:16 UTC | Jul 15, 01:00 UTC | 44m |
| 2026-07-14 | JBU2097 | - | Jul 14, 19:25 UTC | Jul 14, 20:55 UTC | 1h 30m |
| 2026-07-14 | JBU2097 | ATL → FLL | Jul 14, 19:25 UTC | Jul 15, 01:00 UTC | 5h 35m |
| 2026-07-14 | JBU1698 | - | Jul 14, 16:15 UTC | Jul 14, 17:40 UTC | 1h 25m |
| 2026-07-14 | JBU1795 | - | Jul 14, 12:45 UTC | Jul 14, 15:00 UTC | 2h 15m |
| 2026-07-13 | JBU2594 | - | Jul 13, 23:30 UTC | Jul 14, 01:35 UTC | 2h 5m |
| 2026-07-13 | JBU433 | MCO → SJU | Jul 13, 03:44 UTC | Jul 14, 01:35 UTC | 21h 52m |
| 2026-07-12 | JBU1042 | MCO → ROC | Jul 12, 20:25 UTC | Jul 13, 16:30 UTC | 20h 6m |
| 2026-07-12 | JBU1531 | BOS → MCO | Jul 12, 14:50 UTC | Jul 13, 13:20 UTC | 22h 31m |
| 2026-07-11 | JBU740 | ANU → JFK | Jul 11, 19:56 UTC | Jul 12, 17:35 UTC | 21h 40m |
| 2026-07-11 | JBU743 | JFK → ANU | Jul 11, 14:35 UTC | Jul 12, 13:05 UTC | 22h 31m |
| 2026-07-11 | JBU18 | POS → JFK | Jul 11, 00:47 UTC | Jul 11, 23:55 UTC | 23h 9m |
| 2026-07-10 | JBU130 | RSW → JFK | Jul 10, 10:13 UTC | Jul 11, 05:40 UTC | 19h 28m |
| 2026-07-10 | JBU2129 | JFK → RSW | Jul 10, 03:11 UTC | Jul 11, 02:30 UTC | 23h 20m |
| 2026-07-09 | JBU237 | JFK → STI | Jul 9, 16:55 UTC | Jul 10, 12:30 UTC | 19h 35m |
| 2026-07-09 | JBU406 | ORD → JFK | Jul 9, 00:08 UTC | Jul 9, 18:15 UTC | 18h 7m |
| 2026-07-09 | JBU406 | ORD → JFK | Jul 9, 00:10 UTC | Jul 9, 01:50 UTC | 1h 40m |
| 2026-07-08 | JBU405 | - | Jul 8, 20:15 UTC | Jul 8, 22:05 UTC | 1h 50m |
| 2026-07-08 | JBU282 | - | Jul 8, 15:30 UTC | Jul 8, 18:40 UTC | 3h 10m |
| 2026-07-07 | JBU281 | - | Jul 7, 20:15 UTC | Jul 7, 20:30 UTC | 15m |
| 2026-07-07 | JBU281 | JFK → IAH | Jul 7, 20:14 UTC | Jul 8, 18:30 UTC | 22h 17m |
| 2026-07-07 | JBU164 | - | Jul 7, 16:05 UTC | Jul 7, 18:40 UTC | 2h 35m |
| 2026-07-07 | JBU164 | SRQ → JFK | Jul 7, 16:02 UTC | Jul 8, 00:00 UTC | 7h 59m |
| 2026-07-07 | JBU163 | JFK → SRQ | Jul 7, 12:30 UTC | Jul 7, 14:55 UTC | 2h 25m |
| 2026-07-06 | JBU2510 | JFK → JFK | Jul 6, 15:45 UTC | Jul 7, 00:00 UTC | 8h 15m |
| 2026-07-05 | JBU1039 | JFK → BQN | Jul 5, 22:26 UTC | Jul 6, 16:25 UTC | 18h 0m |
| 2026-07-05 | JBU1039 | - | Jul 5, 22:30 UTC | Jul 5, 23:20 UTC | 50m |
| 2026-07-05 | JBU2032 | JFK → JFK | Jul 5, 15:05 UTC | Jul 5, 20:10 UTC | 5h 5m |
| 2026-07-05 | JBU302 | PPM → JFK | Jul 5, 10:55 UTC | Jul 5, 13:15 UTC | 2h 20m |
| 2026-07-04 | JBU2269 | - | Jul 4, 23:30 UTC | Jul 5, 02:15 UTC | 2h 45m |
| 2026-07-04 | JBU2269 | BOS → BOS | Jul 4, 23:05 UTC | Jul 4, 23:10 UTC | 5m |
| 2026-07-04 | JBU2269 | BOS → BOS | Jul 4, 22:35 UTC | Jul 4, 22:40 UTC | 5m |
| 2026-07-04 | JBU70 | - | Jul 4, 18:55 UTC | Jul 4, 21:35 UTC | 2h 40m |
| 2026-07-04 | JBU579 | DCA → FLL | Jul 4, 15:15 UTC | Jul 4, 17:20 UTC | 2h 5m |
| 2026-07-03 | JBU598 | MCO → LGA | Jul 3, 18:50 UTC | Jul 4, 17:20 UTC | 22h 31m |
| 2026-07-03 | JBU2129 | JFK → RSW | Jul 3, 02:30 UTC | Jul 4, 00:30 UTC | 22h 1m |
| 2026-07-03 | JBU2129 | JFK → RSW | Jul 3, 02:35 UTC | Jul 3, 05:00 UTC | 2h 25m |
| 2026-07-02 | JBU2984 | - | Jul 2, 22:10 UTC | Jul 3, 00:20 UTC | 2h 10m |
| 2026-07-02 | JBU1778 | MCO → MCO | Jul 2, 12:55 UTC | Jul 2, 19:05 UTC | 6h 10m |
| 2026-07-01 | JBU1137 | BOS → DTW | Jul 1, 23:45 UTC | Jul 2, 22:30 UTC | 22h 46m |
| 2026-07-01 | JBU238 | SDQ → SJU | Jul 1, 21:04 UTC | Jul 2, 19:15 UTC | 22h 11m |
| 2026-07-01 | JBU1937 | SJU → SDQ | Jul 1, 19:00 UTC | Jul 2, 18:30 UTC | 23h 30m |
| 2026-07-01 | JBU1638 | SDQ → SJU | Jul 1, 16:26 UTC | Jul 2, 13:35 UTC | 21h 10m |
| 2026-07-01 | JBU2537 | SJU → SDQ | Jul 1, 14:25 UTC | Jul 1, 14:30 UTC | 5m |
| 2026-07-01 | JBU403 | JFK → SJU | Jul 1, 09:20 UTC | Jul 1, 12:35 UTC | 3h 15m |
| 2026-07-01 | JBU403 | JFK → SJU | Jul 1, 09:20 UTC | Jul 2, 08:30 UTC | 23h 10m |
| 2026-06-30 | JBU938 | JFK → JFK | Jun 30, 13:15 UTC | Jul 1, 01:00 UTC | 11h 45m |
| 2026-06-30 | JBU675 | JFK → BDL | Jun 30, 03:05 UTC | Jul 1, 01:15 UTC | 22h 11m |
| 2026-06-30 | JBU1117 | BOS → JFK | Jun 30, 00:25 UTC | Jun 30, 22:30 UTC | 22h 6m |
| 2026-06-29 | JBU892 | TPA → BOS | Jun 29, 13:59 UTC | Jun 29, 16:25 UTC | 2h 25m |
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 N588JB page for operator, model, and routing details .