sensors Mode-S transponder
A7A1E8
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N591JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORPORATION
- Hex
- A7A1E8
- Octal
- 51720750
- Decimal
- 10,985,960
- Country
- US
- Tail
- N591JB
- Type
- A320
- Flights observed
- 266
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address A7A1E8 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 |
|---|---|---|---|
| JBU1962 | - | 5 | 2026-06-28 |
| JBU868 | JetBlue Airways | 4 | 2026-04-20 |
| JBU1903 | JetBlue Airways | 4 | 2026-05-07 |
| JBU98 | - | 3 | 2026-04-14 |
| JBU969 | - | 3 | 2026-07-10 |
| JBU961 | JetBlue Airways | 3 | 2026-04-22 |
| JBU676 | - | 3 | 2026-07-08 |
| JBU503 | JetBlue Airways | 3 | 2026-06-08 |
| JBU38 | - | 3 | 2026-07-13 |
| JBU304 | - | 3 | 2026-07-06 |
| JBU257 | - | 3 | 2026-07-06 |
| JBU2476 | JetBlue Airways | 3 | 2026-05-18 |
| JBU2390 | JetBlue Airways | 3 | 2026-04-16 |
| JBU1868 | JetBlue Airways | 3 | 2026-05-17 |
| JBU1761 | - | 3 | 2026-06-27 |
| JBU1367 | JetBlue Airways | 3 | 2026-05-03 |
| JBU1242 | JetBlue Airways | 3 | 2026-04-27 |
| JBU1229 | JetBlue Airways | 3 | 2026-06-30 |
| JBU1142 | - | 3 | 2026-06-22 |
| JBU1048 | JetBlue Airways | 3 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU38 | SJO → FLL | Jul 13, 21:45 UTC | Jul 14, 00:10 UTC | 2h 25m |
| 2026-07-13 | JBU2919 | MCO → ALB | Jul 13, 00:35 UTC | Jul 14, 00:00 UTC | 23h 26m |
| 2026-07-12 | JBU595 | - | Jul 12, 20:25 UTC | Jul 12, 22:45 UTC | 2h 20m |
| 2026-07-12 | JBU595 | HPN → MCO | Jul 12, 20:23 UTC | Jul 13, 20:00 UTC | 23h 38m |
| 2026-07-12 | JBU194 | - | Jul 12, 16:01 UTC | Jul 12, 18:25 UTC | 2h 25m |
| 2026-07-11 | JBU137 | BDL → MCO | Jul 11, 21:16 UTC | Jul 12, 18:25 UTC | 21h 10m |
| 2026-07-11 | JBU2938 | MCO → BDL | Jul 11, 17:39 UTC | Jul 12, 16:01 UTC | 22h 22m |
| 2026-07-11 | JBU195 | HPN → MCO | Jul 11, 04:31 UTC | Jul 11, 23:55 UTC | 19h 25m |
| 2026-07-11 | JBU1694 | MCO → HPN | Jul 11, 01:00 UTC | Jul 11, 23:55 UTC | 22h 56m |
| 2026-07-10 | JBU969 | RIC → MCO | Jul 10, 21:09 UTC | Jul 11, 20:00 UTC | 22h 52m |
| 2026-07-10 | JBU670 | MCO → RIC | Jul 10, 18:21 UTC | Jul 11, 18:00 UTC | 23h 40m |
| 2026-07-10 | JBU8367 | BOS → JFK | Jul 10, 14:55 UTC | Jul 10, 17:05 UTC | 2h 10m |
| 2026-07-10 | JBU8367 | BOS → JFK | Jul 10, 14:55 UTC | Jul 11, 09:55 UTC | 19h 1m |
| 2026-07-09 | JBU383 | JFK → MCO | Jul 9, 15:40 UTC | Jul 9, 17:50 UTC | 2h 10m |
| 2026-07-09 | JBU383 | JFK → MCO | Jul 9, 15:38 UTC | Jul 10, 02:35 UTC | 10h 57m |
| 2026-07-09 | JBU1901 | - | Jul 9, 12:55 UTC | Jul 9, 13:55 UTC | 1h 0m |
| 2026-07-09 | JBU1602 | JFK → BUF | Jul 9, 10:50 UTC | Jul 9, 11:45 UTC | 55m |
| 2026-07-08 | JBU676 | BDL → JFK | Jul 8, 10:56 UTC | Jul 9, 01:15 UTC | 14h 19m |
| 2026-07-08 | JBU1117 | BOS → JFK | Jul 8, 04:55 UTC | Jul 8, 05:45 UTC | 50m |
| 2026-07-08 | JBU1117 | BOS → JFK | Jul 8, 04:55 UTC | Jul 9, 01:15 UTC | 20h 20m |
| 2026-07-07 | JBU256 | BZN → BOS | Jul 7, 21:50 UTC | Jul 8, 01:35 UTC | 3h 45m |
| 2026-07-06 | JBU257 | - | Jul 6, 17:10 UTC | Jul 6, 21:05 UTC | 3h 55m |
| 2026-07-06 | JBU304 | - | Jul 6, 02:20 UTC | Jul 6, 03:20 UTC | 1h 0m |
| 2026-07-05 | JBU304 | - | Jul 5, 23:50 UTC | Jul 6, 00:10 UTC | 20m |
| 2026-07-05 | JBU304 | SJU → JFK | Jul 5, 23:48 UTC | Jul 6, 21:05 UTC | 21h 18m |
| 2026-07-05 | JBU1133 | SYR → JFK | Jul 5, 18:40 UTC | Jul 5, 21:10 UTC | 2h 30m |
| 2026-07-05 | JBU2695 | - | Jul 5, 14:40 UTC | Jul 5, 17:15 UTC | 2h 35m |
| 2026-07-05 | JBU1368 | - | Jul 5, 10:40 UTC | Jul 5, 13:10 UTC | 2h 30m |
| 2026-07-04 | JBU257 | BOS → BZN | Jul 4, 13:34 UTC | Jul 5, 12:00 UTC | 22h 27m |
| 2026-07-04 | JBU257 | - | Jul 4, 13:35 UTC | Jul 4, 19:30 UTC | 5h 55m |
| 2026-07-04 | JBU50 | - | Jul 4, 04:55 UTC | Jul 4, 09:45 UTC | 4h 50m |
| 2026-07-03 | JBU1473 | FLL → PUJ | Jul 3, 11:15 UTC | Jul 4, 09:45 UTC | 22h 30m |
| 2026-07-03 | JBU2269 | - | Jul 3, 01:10 UTC | Jul 3, 02:00 UTC | 50m |
| 2026-07-03 | JBU2269 | BOS → FLL | Jul 3, 01:09 UTC | Jul 4, 00:00 UTC | 22h 52m |
| 2026-07-02 | JBU70 | - | Jul 2, 20:35 UTC | Jul 2, 23:30 UTC | 2h 55m |
| 2026-07-02 | JBU579 | - | Jul 2, 18:55 UTC | Jul 2, 19:15 UTC | 20m |
| 2026-07-02 | JBU579 | - | Jul 2, 15:10 UTC | Jul 2, 17:25 UTC | 2h 15m |
| 2026-07-02 | JBU1480 | - | Jul 2, 11:45 UTC | Jul 2, 13:40 UTC | 1h 55m |
| 2026-07-02 | JBU571 | - | Jul 2, 01:25 UTC | Jul 2, 03:40 UTC | 2h 15m |
| 2026-07-01 | JBU472 | - | Jul 1, 21:25 UTC | Jul 1, 23:45 UTC | 2h 20m |
| 2026-07-01 | JBU1979 | DCA → FLL | Jul 1, 00:43 UTC | Jul 2, 00:00 UTC | 23h 18m |
| 2026-06-30 | JBU1229 | EWR → CUN | Jun 30, 13:00 UTC | Jul 1, 02:40 UTC | 13h 41m |
| 2026-06-30 | JBU1229 | EWR → CUN | Jun 30, 13:00 UTC | Jun 30, 16:00 UTC | 3h 0m |
| 2026-06-29 | JBU144 | - | Jun 29, 23:39 UTC | Jun 30, 02:10 UTC | 2h 30m |
| 2026-06-29 | JBU2087 | - | Jun 29, 19:15 UTC | Jun 29, 21:50 UTC | 2h 35m |
| 2026-06-28 | JBU1962 | PBI → LGA | Jun 28, 22:28 UTC | Jun 29, 21:50 UTC | 23h 22m |
| 2026-06-28 | JBU1552 | RSW → HPN | Jun 28, 14:40 UTC | Jun 29, 13:59 UTC | 23h 20m |
| 2026-06-28 | JBU1551 | HPN → RSW | Jun 28, 10:50 UTC | Jun 29, 01:34 UTC | 14h 45m |
| 2026-06-27 | JBU1761 | LGA → PBI | Jun 27, 20:59 UTC | Jun 28, 19:59 UTC | 23h 1m |
| 2026-06-27 | JBU1761 | LGA → PBI | Jun 27, 20:59 UTC | Jun 27, 23:34 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 N591JB page for operator, model, and routing details .