sensors Mode-S transponder
A87C4F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N646JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A87C4F
- Octal
- 52076117
- Decimal
- 11,041,871
- Country
- US
- Tail
- N646JB
- Type
- A320
- Flights observed
- 265
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 21m ago
Current position
Country allocation
The ICAO 24-bit address A87C4F 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 | - | 4 | 2026-04-15 |
| JBU87 | JetBlue Airways | 4 | 2026-04-15 |
| JBU2153 | JetBlue Airways | 4 | 2026-06-14 |
| JBU1471 | JetBlue Airways | 4 | 2026-06-05 |
| JBU934 | JetBlue Airways | 3 | 2026-06-03 |
| JBU869 | JetBlue Airways | 3 | 2026-05-06 |
| JBU572 | JetBlue Airways | 3 | 2026-04-17 |
| JBU503 | JetBlue Airways | 3 | 2026-04-30 |
| JBU2374 | JetBlue Airways | 3 | 2026-06-07 |
| JBU2054 | JetBlue Airways | 3 | 2026-05-10 |
| JBU1903 | - | 3 | 2026-06-16 |
| JBU1743 | - | 3 | 2026-07-10 |
| JBU1696 | - | 3 | 2026-07-01 |
| JBU133 | JetBlue Airways | 3 | 2026-06-03 |
| JBU1230 | JetBlue Airways | 3 | 2026-05-16 |
| JBU1197 | - | 3 | 2026-07-03 |
| JBU1196 | - | 3 | 2026-07-02 |
| JBU861 | JetBlue Airways | 2 | 2026-05-01 |
| JBU8507 | - | 2 | 2026-06-22 |
| JBU846 | - | 2 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2371 | FLL → AUS | Jul 14, 13:53 UTC | Jul 14, 19:45 UTC | 5h 53m |
| 2026-07-14 | JBU513 | ISP → FLL | Jul 14, 10:06 UTC | Jul 14, 19:45 UTC | 9h 40m |
| 2026-07-14 | JBU846 | MCO → ISP | Jul 14, 01:41 UTC | Jul 14, 19:45 UTC | 18h 5m |
| 2026-07-14 | JBU846 | MCO → ISP | Jul 14, 01:45 UTC | Jul 14, 03:50 UTC | 2h 5m |
| 2026-07-13 | JBU1043 | - | Jul 13, 23:10 UTC | Jul 13, 23:40 UTC | 30m |
| 2026-07-13 | JBU1043 | - | Jul 13, 18:45 UTC | Jul 13, 22:25 UTC | 3h 40m |
| 2026-07-13 | JBU1042 | MCO → ROC | Jul 13, 15:05 UTC | Jul 13, 17:25 UTC | 2h 20m |
| 2026-07-13 | JBU283 | JFK → MCO | Jul 13, 00:45 UTC | Jul 13, 02:55 UTC | 2h 10m |
| 2026-07-12 | JBU1084 | MCO → JFK | Jul 12, 20:35 UTC | Jul 12, 22:55 UTC | 2h 20m |
| 2026-07-11 | JBU1976 | KIN → FLL | Jul 11, 23:58 UTC | Jul 12, 22:55 UTC | 22h 58m |
| 2026-07-11 | JBU1976 | - | Jul 11, 20:50 UTC | Jul 12, 01:30 UTC | 4h 40m |
| 2026-07-11 | JBU1676 | - | Jul 11, 14:25 UTC | Jul 11, 18:45 UTC | 4h 20m |
| 2026-07-10 | JBU1743 | - | Jul 10, 23:25 UTC | Jul 10, 23:40 UTC | 15m |
| 2026-07-10 | JBU1743 | - | Jul 10, 20:55 UTC | Jul 10, 21:45 UTC | 50m |
| 2026-07-10 | JBU1743 | JAX → SJU | Jul 10, 20:53 UTC | Jul 11, 18:45 UTC | 21h 53m |
| 2026-07-10 | JBU1742 | - | Jul 10, 18:35 UTC | Jul 10, 19:45 UTC | 1h 10m |
| 2026-07-10 | JBU1742 | - | Jul 10, 17:00 UTC | Jul 10, 17:10 UTC | 10m |
| 2026-07-10 | JBU635 | - | Jul 10, 15:20 UTC | Jul 10, 15:40 UTC | 20m |
| 2026-07-09 | JBU1950 | RSW → BUF | Jul 9, 19:25 UTC | Jul 9, 21:45 UTC | 2h 20m |
| 2026-07-09 | JBU1950 | RSW → BUF | Jul 9, 19:21 UTC | Jul 10, 17:10 UTC | 21h 49m |
| 2026-07-09 | JBU2049 | BUF → RSW | Jul 9, 15:40 UTC | Jul 9, 18:15 UTC | 2h 35m |
| 2026-07-08 | JBU2466 | - | Jul 8, 23:45 UTC | Jul 9, 02:15 UTC | 2h 30m |
| 2026-07-08 | JBU1775 | FLL → KIN | Jul 8, 02:48 UTC | Jul 9, 01:45 UTC | 22h 58m |
| 2026-07-07 | JBU2275 | PHL → FLL | Jul 7, 22:24 UTC | Jul 8, 21:25 UTC | 23h 2m |
| 2026-07-07 | JBU1468 | PBI → HPN | Jul 7, 04:31 UTC | Jul 8, 03:25 UTC | 22h 55m |
| 2026-07-06 | JBU545 | ISP → PBI | Jul 6, 20:36 UTC | Jul 7, 06:55 UTC | 10h 19m |
| 2026-07-06 | JBU444 | - | Jul 6, 14:35 UTC | Jul 6, 17:35 UTC | 3h 0m |
| 2026-07-06 | JBU444 | PBI → ISP | Jul 6, 14:30 UTC | Jul 7, 06:55 UTC | 16h 25m |
| 2026-07-06 | JBU445 | - | Jul 6, 10:30 UTC | Jul 6, 12:40 UTC | 2h 10m |
| 2026-07-05 | JBU40 | MDE → FLL | Jul 5, 17:34 UTC | Jul 6, 15:45 UTC | 22h 12m |
| 2026-07-05 | JBU1703 | SJU → MDE | Jul 5, 13:36 UTC | Jul 6, 11:45 UTC | 22h 10m |
| 2026-07-05 | JBU1697 | ATL → FLL | Jul 5, 04:35 UTC | Jul 6, 03:00 UTC | 22h 26m |
| 2026-07-04 | JBU1799 | ORF → FLL | Jul 4, 18:00 UTC | Jul 4, 19:40 UTC | 1h 40m |
| 2026-07-04 | JBU1799 | ORF → FLL | Jul 4, 17:57 UTC | Jul 5, 14:45 UTC | 20h 48m |
| 2026-07-04 | JBU1800 | - | Jul 4, 15:25 UTC | Jul 4, 17:10 UTC | 1h 45m |
| 2026-07-04 | JBU1906 | TPA → FLL | Jul 4, 13:40 UTC | Jul 4, 14:15 UTC | 35m |
| 2026-07-04 | JBU1905 | - | Jul 4, 01:40 UTC | Jul 4, 02:15 UTC | 35m |
| 2026-07-03 | JBU1579 | DCA → FLL | Jul 3, 22:40 UTC | Jul 4, 00:35 UTC | 1h 55m |
| 2026-07-03 | JBU1680 | - | Jul 3, 18:25 UTC | Jul 3, 20:20 UTC | 1h 55m |
| 2026-07-03 | JBU1197 | - | Jul 3, 16:35 UTC | Jul 3, 16:55 UTC | 20m |
| 2026-07-03 | JBU1197 | - | Jul 3, 12:15 UTC | Jul 3, 15:15 UTC | 3h 0m |
| 2026-07-02 | JBU1196 | - | Jul 2, 23:15 UTC | Jul 3, 01:55 UTC | 2h 40m |
| 2026-07-02 | JBU38 | - | Jul 2, 21:05 UTC | Jul 2, 21:40 UTC | 35m |
| 2026-07-02 | JBU38 | - | Jul 2, 19:20 UTC | Jul 2, 20:10 UTC | 50m |
| 2026-07-02 | JBU1695 | - | Jul 2, 14:25 UTC | Jul 2, 16:50 UTC | 2h 25m |
| 2026-07-01 | JBU1696 | - | Jul 1, 19:25 UTC | Jul 1, 19:45 UTC | 20m |
| 2026-07-01 | JBU1696 | SJO → MCO | Jul 1, 19:16 UTC | Jul 2, 16:50 UTC | 21h 34m |
| 2026-07-01 | JBU39 | - | Jul 1, 15:15 UTC | Jul 1, 17:25 UTC | 2h 10m |
| 2026-07-01 | JBU39 | FLL → SJO | Jul 1, 15:11 UTC | Jul 2, 13:45 UTC | 22h 35m |
| 2026-07-01 | JBU2625 | - | Jul 1, 11:05 UTC | Jul 1, 12:40 UTC | 1h 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 N646JB page for operator, model, and routing details .