sensors Mode-S transponder
A87898
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N645JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A87898
- Octal
- 52074230
- Decimal
- 11,040,920
- Country
- US
- Tail
- N645JB
- Type
- A320
- Flights observed
- 285
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 51m ago
Current position
Country allocation
The ICAO 24-bit address A87898 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 |
|---|---|---|---|
| JBU2920 | - | 6 | 2026-07-05 |
| JBU2548 | - | 4 | 2026-07-10 |
| JBU1797 | - | 4 | 2026-06-24 |
| JBU1793 | JetBlue Airways | 4 | 2026-05-29 |
| JBU814 | JetBlue Airways | 3 | 2026-05-10 |
| JBU65 | - | 3 | 2026-04-15 |
| JBU635 | - | 3 | 2026-04-13 |
| JBU365 | JetBlue Airways | 3 | 2026-04-16 |
| JBU2919 | - | 3 | 2026-07-05 |
| JBU240 | - | 3 | 2026-07-10 |
| JBU2166 | JetBlue Airways | 3 | 2026-05-08 |
| JBU2153 | - | 3 | 2026-07-01 |
| JBU213 | JetBlue Airways | 3 | 2026-05-10 |
| JBU2097 | JetBlue Airways | 3 | 2026-04-30 |
| JBU2066 | JetBlue Airways | 3 | 2026-04-14 |
| JBU2065 | - | 3 | 2026-04-14 |
| JBU2032 | - | 3 | 2026-06-30 |
| JBU1990 | - | 3 | 2026-06-21 |
| JBU1778 | JetBlue Airways | 3 | 2026-05-12 |
| JBU1754 | JetBlue Airways | 3 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2118 | FLL → JAX | Jul 14, 17:35 UTC | Jul 15, 01:50 UTC | 8h 15m |
| 2026-07-13 | JBU472 | FLL → LGA | Jul 13, 21:15 UTC | Jul 14, 20:00 UTC | 22h 46m |
| 2026-07-13 | JBU126 | TPA → JFK | Jul 13, 10:22 UTC | Jul 14, 03:40 UTC | 17h 19m |
| 2026-07-13 | JBU2932 | PUJ → SJU | Jul 13, 01:05 UTC | Jul 13, 23:45 UTC | 22h 41m |
| 2026-07-12 | JBU2931 | SJU → PUJ | Jul 12, 23:31 UTC | Jul 13, 22:00 UTC | 22h 30m |
| 2026-07-12 | JBU1608 | STI → SJU | Jul 12, 21:03 UTC | Jul 13, 19:35 UTC | 22h 33m |
| 2026-07-12 | JBU127 | EWR → MCO | Jul 12, 10:35 UTC | Jul 12, 12:40 UTC | 2h 5m |
| 2026-07-12 | JBU127 | EWR → MCO | Jul 12, 10:35 UTC | Jul 13, 05:55 UTC | 19h 21m |
| 2026-07-11 | JBU1233 | MCO → SJU | Jul 11, 09:18 UTC | Jul 12, 01:50 UTC | 16h 33m |
| 2026-07-11 | JBU1727 | EWR → MCO | Jul 11, 05:15 UTC | Jul 12, 01:50 UTC | 20h 36m |
| 2026-07-10 | JBU240 | - | Jul 10, 20:00 UTC | Jul 10, 20:55 UTC | 55m |
| 2026-07-10 | JBU240 | NAS → MCO | Jul 10, 19:48 UTC | Jul 11, 16:10 UTC | 20h 23m |
| 2026-07-10 | JBU241 | - | Jul 10, 17:35 UTC | Jul 10, 18:10 UTC | 35m |
| 2026-07-10 | JBU2548 | - | Jul 10, 15:20 UTC | Jul 10, 16:00 UTC | 40m |
| 2026-07-10 | JBU569 | BOS → FLL | Jul 10, 11:10 UTC | Jul 10, 13:55 UTC | 2h 45m |
| 2026-07-09 | JBU1493 | FLL → NAS | Jul 9, 12:40 UTC | Jul 10, 12:00 UTC | 23h 20m |
| 2026-07-09 | JBU2269 | BOS → FLL | Jul 9, 00:23 UTC | Jul 9, 23:25 UTC | 23h 2m |
| 2026-07-09 | JBU2269 | BOS → FLL | Jul 9, 00:25 UTC | Jul 9, 03:05 UTC | 2h 40m |
| 2026-07-08 | JBU70 | - | Jul 8, 20:20 UTC | Jul 8, 22:55 UTC | 2h 35m |
| 2026-07-08 | JBU579 | DCA → FLL | Jul 8, 16:50 UTC | Jul 8, 18:55 UTC | 2h 5m |
| 2026-07-08 | JBU1480 | - | Jul 8, 11:50 UTC | Jul 8, 13:45 UTC | 1h 55m |
| 2026-07-07 | JBU569 | BOS → FLL | Jul 7, 10:45 UTC | Jul 7, 13:30 UTC | 2h 46m |
| 2026-07-06 | JBU1194 | MBJ → BOS | Jul 6, 20:57 UTC | Jul 7, 13:30 UTC | 16h 34m |
| 2026-07-06 | JBU1193 | BOS → MBJ | Jul 6, 15:30 UTC | Jul 7, 13:30 UTC | 22h 1m |
| 2026-07-05 | JBU1136 | DTW → BOS | Jul 5, 23:50 UTC | Jul 6, 22:00 UTC | 22h 10m |
| 2026-07-05 | JBU1237 | BOS → DTW | Jul 5, 20:34 UTC | Jul 6, 18:20 UTC | 21h 46m |
| 2026-07-05 | JBU384 | - | Jul 5, 13:50 UTC | Jul 5, 14:00 UTC | 10m |
| 2026-07-05 | JBU384 | MCO → JFK | Jul 5, 13:49 UTC | Jul 6, 01:55 UTC | 12h 6m |
| 2026-07-05 | JBU2920 | - | Jul 5, 09:55 UTC | Jul 5, 12:30 UTC | 2h 35m |
| 2026-07-05 | JBU2920 | ALB → MCO | Jul 5, 09:50 UTC | Jul 6, 01:55 UTC | 16h 5m |
| 2026-07-05 | JBU2919 | MCO → ALB | Jul 5, 01:00 UTC | Jul 5, 03:30 UTC | 2h 30m |
| 2026-07-04 | JBU1696 | - | Jul 4, 19:20 UTC | Jul 4, 22:00 UTC | 2h 40m |
| 2026-07-03 | JBU725 | RDU → FLL | Jul 3, 23:02 UTC | Jul 4, 20:00 UTC | 20h 58m |
| 2026-07-03 | JBU1246 | - | Jul 3, 13:40 UTC | Jul 3, 14:00 UTC | 20m |
| 2026-07-03 | JBU1 | JFK → FLL | Jul 3, 09:50 UTC | Jul 3, 12:10 UTC | 2h 20m |
| 2026-07-03 | JBU1 | JFK → FLL | Jul 3, 09:49 UTC | Jul 4, 05:00 UTC | 19h 11m |
| 2026-07-02 | JBU310 | SDQ → JFK | Jul 2, 10:56 UTC | Jul 3, 10:00 UTC | 23h 4m |
| 2026-07-02 | JBU1203 | EWR → SDQ | Jul 2, 03:38 UTC | Jul 3, 02:00 UTC | 22h 22m |
| 2026-07-01 | JBU1475 | BDL → SJU | Jul 1, 15:57 UTC | Jul 2, 14:00 UTC | 22h 3m |
| 2026-07-01 | JBU1476 | SJU → BDL | Jul 1, 11:12 UTC | Jul 2, 04:20 UTC | 17h 9m |
| 2026-07-01 | JBU1476 | SJU → BDL | Jul 1, 11:12 UTC | Jul 2, 04:20 UTC | 17h 9m |
| 2026-07-01 | JBU2153 | - | Jul 1, 04:40 UTC | Jul 1, 04:55 UTC | 15m |
| 2026-07-01 | JBU2153 | - | Jul 1, 02:45 UTC | Jul 1, 03:10 UTC | 25m |
| 2026-07-01 | JBU2153 | FLL → SJU | Jul 1, 02:41 UTC | Jul 2, 00:55 UTC | 22h 15m |
| 2026-06-30 | JBU1501 | - | Jun 30, 22:25 UTC | Jul 1, 00:45 UTC | 2h 20m |
| 2026-06-30 | JBU2032 | JFK → JFK | Jun 30, 15:05 UTC | Jun 30, 20:15 UTC | 5h 10m |
| 2026-06-30 | JBU310 | - | Jun 30, 03:45 UTC | Jun 30, 12:50 UTC | 9h 5m |
| 2026-06-29 | JBU1016 | EWR → EWR | Jun 29, 14:14 UTC | Jun 29, 22:44 UTC | 8h 30m |
| 2026-06-29 | JBU709 | JFK → SDQ | Jun 29, 02:39 UTC | Jun 29, 23:49 UTC | 21h 11m |
| 2026-06-28 | JBU944 | BZN → JFK | Jun 28, 17:47 UTC | Jun 29, 14:50 UTC | 21h 3m |
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 N645JB page for operator, model, and routing details .