sensors Mode-S transponder
AB4F5D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N828JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AB4F5D
- Octal
- 52647535
- Decimal
- 11,226,973
- Country
- US
- Tail
- N828JB
- Type
- A320
- Flights observed
- 274
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address AB4F5D 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 |
|---|---|---|---|
| JBU225 | - | 4 | 2026-07-06 |
| JBU2097 | - | 4 | 2026-06-18 |
| JBU1698 | - | 4 | 2026-06-21 |
| JBU1241 | JetBlue Airways | 4 | 2026-05-03 |
| JBU761 | - | 3 | 2026-06-25 |
| JBU598 | - | 3 | 2026-06-20 |
| JBU569 | - | 3 | 2026-07-14 |
| JBU322 | - | 3 | 2026-07-12 |
| JBU306 | - | 3 | 2026-06-28 |
| JBU2584 | JetBlue Airways | 3 | 2026-06-12 |
| JBU2334 | JetBlue Airways | 3 | 2026-05-03 |
| JBU1752 | JetBlue Airways | 3 | 2026-04-24 |
| JBU1288 | JetBlue Airways | 3 | 2026-05-13 |
| JBU1142 | - | 3 | 2026-07-01 |
| JBU1141 | JetBlue Airways | 3 | 2026-05-03 |
| JBU110 | - | 3 | 2026-04-13 |
| JBU105 | - | 3 | 2026-06-29 |
| JBU929 | JetBlue Airways | 2 | 2026-04-15 |
| JBU894 | - | 2 | 2026-07-04 |
| JBU883 | JetBlue Airways | 2 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2761 | - | Jul 14, 13:45 UTC | Jul 14, 14:10 UTC | 25m |
| 2026-07-14 | JBU569 | BOS → FLL | Jul 14, 09:15 UTC | Jul 14, 11:55 UTC | 2h 40m |
| 2026-07-13 | JBU257 | BOS → BOS | Jul 13, 13:00 UTC | Jul 13, 23:05 UTC | 10h 5m |
| 2026-07-12 | JBU1193 | BOS → BOS | Jul 12, 15:20 UTC | Jul 13, 00:20 UTC | 9h 0m |
| 2026-07-12 | JBU322 | - | Jul 12, 10:55 UTC | Jul 12, 13:30 UTC | 2h 35m |
| 2026-07-11 | JBU23 | DCA → PBI | Jul 11, 22:05 UTC | Jul 12, 00:05 UTC | 2h 0m |
| 2026-07-11 | JBU24 | - | Jul 11, 18:40 UTC | Jul 11, 20:30 UTC | 1h 50m |
| 2026-07-11 | JBU1167 | - | Jul 11, 14:30 UTC | Jul 11, 16:50 UTC | 2h 20m |
| 2026-07-10 | JBU1594 | NAS → FLL | Jul 10, 17:27 UTC | Jul 11, 16:50 UTC | 23h 24m |
| 2026-07-10 | JBU1 | JFK → FLL | Jul 10, 11:40 UTC | Jul 10, 14:00 UTC | 2h 20m |
| 2026-07-10 | JBU1 | JFK → FLL | Jul 10, 11:35 UTC | Jul 11, 11:15 UTC | 23h 41m |
| 2026-07-09 | JBU939 | JFK → SJD | Jul 9, 13:51 UTC | Jul 10, 13:15 UTC | 23h 24m |
| 2026-07-09 | JBU676 | BDL → JFK | Jul 9, 10:53 UTC | Jul 10, 02:15 UTC | 15h 22m |
| 2026-07-08 | JBU1695 | MCO → SJO | Jul 8, 14:55 UTC | Jul 9, 11:25 UTC | 20h 31m |
| 2026-07-08 | JBU1334 | - | Jul 8, 04:55 UTC | Jul 8, 05:10 UTC | 15m |
| 2026-07-08 | JBU1608 | - | Jul 8, 03:05 UTC | Jul 8, 03:20 UTC | 15m |
| 2026-07-08 | JBU1608 | STI → SJU | Jul 8, 02:27 UTC | Jul 9, 01:15 UTC | 22h 48m |
| 2026-07-07 | JBU593 | - | Jul 7, 19:30 UTC | Jul 7, 22:05 UTC | 2h 35m |
| 2026-07-06 | JBU225 | JFK → TPA | Jul 6, 10:46 UTC | Jul 6, 17:15 UTC | 6h 30m |
| 2026-07-06 | JBU225 | JFK → TPA | Jul 6, 10:50 UTC | Jul 6, 13:10 UTC | 2h 20m |
| 2026-07-05 | JBU2662 | - | Jul 5, 23:00 UTC | Jul 6, 02:30 UTC | 3h 30m |
| 2026-07-05 | JBU1203 | EWR → SDQ | Jul 5, 05:50 UTC | Jul 6, 02:45 UTC | 20h 55m |
| 2026-07-05 | JBU1728 | - | Jul 5, 00:55 UTC | Jul 5, 01:15 UTC | 20m |
| 2026-07-04 | JBU399 | LGA → MCO | Jul 4, 20:20 UTC | Jul 5, 17:35 UTC | 21h 16m |
| 2026-07-04 | JBU399 | LGA → MCO | Jul 4, 20:20 UTC | Jul 4, 23:15 UTC | 2h 55m |
| 2026-07-04 | JBU894 | - | Jul 4, 02:00 UTC | Jul 4, 03:30 UTC | 1h 30m |
| 2026-07-04 | JBU894 | STI → EWR | Jul 4, 00:01 UTC | Jul 4, 23:15 UTC | 23h 14m |
| 2026-07-03 | JBU1607 | SJU → STI | Jul 3, 21:45 UTC | Jul 3, 22:00 UTC | 15m |
| 2026-07-03 | JBU703 | JFK → SJU | Jul 3, 17:00 UTC | Jul 3, 20:05 UTC | 3h 5m |
| 2026-07-02 | JBU1794 | - | Jul 2, 20:00 UTC | Jul 3, 00:30 UTC | 4h 30m |
| 2026-07-02 | JBU1793 | - | Jul 2, 13:45 UTC | Jul 2, 18:00 UTC | 4h 15m |
| 2026-07-02 | JBU676 | BDL → JFK | Jul 2, 10:50 UTC | Jul 2, 11:20 UTC | 30m |
| 2026-07-02 | JBU675 | JFK → BDL | Jul 2, 03:15 UTC | Jul 2, 03:45 UTC | 30m |
| 2026-07-01 | JBU1284 | - | Jul 1, 23:15 UTC | Jul 2, 01:30 UTC | 2h 15m |
| 2026-07-01 | JBU2937 | - | Jul 1, 19:30 UTC | Jul 1, 21:50 UTC | 2h 20m |
| 2026-07-01 | JBU1142 | - | Jul 1, 15:50 UTC | Jul 1, 18:25 UTC | 2h 35m |
| 2026-07-01 | JBU1067 | - | Jul 1, 11:05 UTC | Jul 1, 13:20 UTC | 2h 15m |
| 2026-06-30 | JBU1168 | - | Jun 30, 18:55 UTC | Jun 30, 21:25 UTC | 2h 30m |
| 2026-06-30 | JBU1167 | - | Jun 30, 15:05 UTC | Jun 30, 17:20 UTC | 2h 15m |
| 2026-06-29 | JBU1975 | FLL → KIN | Jun 29, 20:55 UTC | Jun 30, 19:15 UTC | 22h 21m |
| 2026-06-29 | JBU105 | EWR → FLL | Jun 29, 16:25 UTC | Jun 29, 18:39 UTC | 2h 15m |
| 2026-06-29 | JBU105 | EWR → FLL | Jun 29, 16:21 UTC | Jun 30, 15:15 UTC | 22h 55m |
| 2026-06-29 | JBU2144 | - | Jun 29, 11:50 UTC | Jun 29, 14:19 UTC | 2h 30m |
| 2026-06-28 | JBU23 | - | Jun 28, 22:39 UTC | Jun 29, 00:39 UTC | 2h 0m |
| 2026-06-28 | JBU24 | - | Jun 28, 18:40 UTC | Jun 28, 20:39 UTC | 2h 0m |
| 2026-06-28 | JBU2143 | - | Jun 28, 14:59 UTC | Jun 28, 17:10 UTC | 2h 10m |
| 2026-06-28 | JBU306 | - | Jun 28, 10:55 UTC | Jun 28, 13:19 UTC | 2h 25m |
| 2026-06-25 | JBU761 | - | Jun 25, 13:29 UTC | Jun 25, 13:59 UTC | 30m |
| 2026-06-25 | JBU761 | BOS → SJU | Jun 25, 10:22 UTC | Jun 26, 01:39 UTC | 15h 18m |
| 2026-06-25 | JBU761 | - | Jun 25, 10:25 UTC | Jun 25, 10:59 UTC | 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 N828JB page for operator, model, and routing details .