sensors Mode-S transponder
A732D9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N563JB · AIRBUS A-320 · operated by BANK OF UTAH TRUSTEE
- Hex
- A732D9
- Octal
- 51631331
- Decimal
- 10,957,529
- Country
- US
- Tail
- N563JB
- Type
- A320
- Flights observed
- 279
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A732D9 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 |
|---|---|---|---|
| JBU1115 | JetBlue Airways | 5 | 2026-06-18 |
| JBU862 | - | 4 | 2026-07-08 |
| JBU241 | - | 4 | 2026-07-12 |
| JBU851 | JetBlue Airways | 3 | 2026-05-09 |
| JBU743 | - | 3 | 2026-07-05 |
| JBU433 | JetBlue Airways | 3 | 2026-07-08 |
| JBU379 | - | 3 | 2026-07-09 |
| JBU2929 | JetBlue Airways | 3 | 2026-04-17 |
| JBU2795 | JetBlue Airways | 3 | 2026-06-05 |
| JBU2549 | JetBlue Airways | 3 | 2026-06-10 |
| JBU2389 | - | 3 | 2026-07-14 |
| JBU2269 | - | 3 | 2026-07-01 |
| JBU1812 | JetBlue Airways | 3 | 2026-05-12 |
| JBU1642 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1501 | JetBlue Airways | 3 | 2026-04-29 |
| JBU1471 | - | 3 | 2026-07-10 |
| JBU1453 | - | 3 | 2026-06-29 |
| JBU143 | JetBlue Airways | 3 | 2026-05-13 |
| JBU1294 | - | 3 | 2026-07-02 |
| JBU1237 | JetBlue Airways | 3 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2389 | EWR → SJU | Jul 14, 03:20 UTC | Jul 14, 12:15 UTC | 8h 56m |
| 2026-07-13 | JBU1390 | SJU → EWR | Jul 13, 22:17 UTC | Jul 14, 12:15 UTC | 13h 59m |
| 2026-07-13 | JBU2851 | TPA → SJU | Jul 13, 18:29 UTC | Jul 14, 12:15 UTC | 17h 47m |
| 2026-07-13 | JBU1979 | DCA → FLL | Jul 13, 01:58 UTC | Jul 13, 22:40 UTC | 20h 43m |
| 2026-07-12 | JBU241 | MCO → NAS | Jul 12, 16:35 UTC | Jul 13, 16:15 UTC | 23h 41m |
| 2026-07-12 | JBU1697 | ATL → FLL | Jul 12, 03:47 UTC | Jul 13, 02:15 UTC | 22h 29m |
| 2026-07-12 | JBU2098 | - | Jul 12, 00:10 UTC | Jul 12, 01:30 UTC | 1h 20m |
| 2026-07-12 | JBU2098 | FLL → ATL | Jul 12, 00:06 UTC | Jul 12, 22:15 UTC | 22h 10m |
| 2026-07-11 | JBU1784 | - | Jul 11, 14:00 UTC | Jul 11, 22:01 UTC | 8h 0m |
| 2026-07-11 | JBU569 | - | Jul 11, 09:35 UTC | Jul 11, 12:20 UTC | 2h 45m |
| 2026-07-10 | JBU1680 | - | Jul 10, 16:30 UTC | Jul 10, 18:25 UTC | 1h 55m |
| 2026-07-10 | JBU1680 | FLL → DCA | Jul 10, 16:27 UTC | Jul 11, 14:30 UTC | 22h 4m |
| 2026-07-10 | JBU1471 | LGA → FLL | Jul 10, 12:20 UTC | Jul 10, 14:50 UTC | 2h 30m |
| 2026-07-09 | JBU172 | FLL → LGA | Jul 9, 17:31 UTC | Jul 10, 14:50 UTC | 21h 20m |
| 2026-07-09 | JBU379 | DCA → FLL | Jul 9, 11:00 UTC | Jul 9, 13:15 UTC | 2h 15m |
| 2026-07-09 | JBU379 | DCA → FLL | Jul 9, 10:58 UTC | Jul 10, 00:45 UTC | 13h 47m |
| 2026-07-08 | JBU862 | - | Jul 8, 14:55 UTC | Jul 8, 17:10 UTC | 2h 15m |
| 2026-07-08 | JBU862 | - | Jul 8, 12:50 UTC | Jul 8, 13:05 UTC | 15m |
| 2026-07-08 | JBU862 | SJU → BOS | Jul 8, 12:49 UTC | Jul 9, 12:15 UTC | 23h 26m |
| 2026-07-08 | JBU433 | BTV → JFK | Jul 8, 01:40 UTC | Jul 8, 02:00 UTC | 20m |
| 2026-07-07 | JBU433 | BTV → JFK | Jul 7, 23:30 UTC | Jul 8, 00:05 UTC | 35m |
| 2026-07-07 | JBU433 | BTV → JFK | Jul 7, 19:55 UTC | Jul 7, 20:45 UTC | 50m |
| 2026-07-07 | JBU241 | - | Jul 7, 17:00 UTC | Jul 7, 17:40 UTC | 40m |
| 2026-07-07 | JBU351 | - | Jul 7, 12:50 UTC | Jul 7, 15:20 UTC | 2h 30m |
| 2026-07-06 | JBU1354 | DCA → BOS | Jul 6, 23:43 UTC | Jul 7, 01:10 UTC | 1h 27m |
| 2026-07-06 | JBU8363 | JFK → LGA | Jul 6, 11:56 UTC | Jul 7, 01:10 UTC | 13h 14m |
| 2026-07-05 | JBU743 | JFK → ANU | Jul 5, 14:31 UTC | Jul 6, 14:15 UTC | 23h 45m |
| 2026-07-05 | JBU1038 | BQN → JFK | Jul 5, 08:47 UTC | Jul 6, 04:10 UTC | 19h 23m |
| 2026-07-04 | JBU906 | ORD → JFK | Jul 4, 15:34 UTC | Jul 5, 12:15 UTC | 20h 41m |
| 2026-07-04 | JBU906 | ORD → JFK | Jul 4, 15:35 UTC | Jul 4, 17:30 UTC | 1h 55m |
| 2026-07-04 | JBU905 | JFK → ORD | Jul 4, 11:10 UTC | Jul 4, 13:05 UTC | 1h 55m |
| 2026-07-03 | JBU743 | JFK → ANU | Jul 3, 14:38 UTC | Jul 3, 18:00 UTC | 3h 22m |
| 2026-07-03 | JBU743 | JFK → JFK | Jul 3, 14:40 UTC | Jul 4, 00:00 UTC | 9h 20m |
| 2026-07-03 | JBU195 | - | Jul 3, 02:35 UTC | Jul 3, 04:50 UTC | 2h 15m |
| 2026-07-03 | JBU195 | HPN → MCO | Jul 3, 02:34 UTC | Jul 4, 00:20 UTC | 21h 46m |
| 2026-07-02 | JBU1294 | - | Jul 2, 22:25 UTC | Jul 3, 00:45 UTC | 2h 20m |
| 2026-07-02 | JBU2251 | BOS → MCO | Jul 2, 18:10 UTC | Jul 2, 20:45 UTC | 2h 35m |
| 2026-07-02 | JBU862 | - | Jul 2, 12:45 UTC | Jul 2, 16:15 UTC | 3h 30m |
| 2026-07-01 | JBU1703 | - | Jul 1, 15:25 UTC | Jul 1, 15:40 UTC | 15m |
| 2026-07-01 | JBU1703 | SJU → MDE | Jul 1, 15:20 UTC | Jul 2, 02:15 UTC | 10h 56m |
| 2026-07-01 | JBU753 | - | Jul 1, 12:55 UTC | Jul 1, 13:05 UTC | 10m |
| 2026-07-01 | JBU753 | - | Jul 1, 11:00 UTC | Jul 1, 11:25 UTC | 25m |
| 2026-07-01 | JBU2269 | BOS → FLL | Jul 1, 00:10 UTC | Jul 1, 02:50 UTC | 2h 40m |
| 2026-06-30 | JBU234 | SJU → MCO | Jun 30, 06:32 UTC | Jul 1, 02:50 UTC | 20h 19m |
| 2026-06-29 | JBU1453 | - | Jun 29, 22:15 UTC | Jun 29, 22:24 UTC | 10m |
| 2026-06-29 | JBU1453 | - | Jun 29, 20:15 UTC | Jun 29, 20:44 UTC | 30m |
| 2026-06-29 | JBU1453 | FLL → SJU | Jun 29, 20:13 UTC | Jun 30, 18:15 UTC | 22h 3m |
| 2026-06-29 | JBU1488 | - | Jun 29, 15:09 UTC | Jun 29, 17:49 UTC | 2h 40m |
| 2026-06-29 | JBU1088 | - | Jun 29, 11:04 UTC | Jun 29, 13:49 UTC | 2h 45m |
| 2026-06-28 | JBU1505 | EWR → FLL | Jun 28, 10:48 UTC | Jun 28, 13:14 UTC | 2h 27m |
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 N563JB page for operator, model, and routing details .