sensors Mode-S transponder
A85FF5
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N639JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A85FF5
- Octal
- 52057765
- Decimal
- 11,034,613
- Country
- US
- Tail
- N639JB
- Type
- A320
- Flights observed
- 290
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address A85FF5 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 |
|---|---|---|---|
| JBU404 | - | 7 | 2026-07-07 |
| JBU379 | JetBlue Airways | 5 | 2026-06-14 |
| JBU1067 | JetBlue Airways | 5 | 2026-06-06 |
| JBU58 | JetBlue Airways | 4 | 2026-05-19 |
| JBU57 | JetBlue Airways | 4 | 2026-05-19 |
| JBU144 | JetBlue Airways | 4 | 2026-05-16 |
| JBU968 | JetBlue Airways | 3 | 2026-04-15 |
| JBU2153 | JetBlue Airways | 3 | 2026-05-23 |
| JBU2080 | - | 3 | 2026-07-12 |
| JBU1696 | JetBlue Airways | 3 | 2026-06-14 |
| JBU1695 | JetBlue Airways | 3 | 2026-05-14 |
| JBU1587 | JetBlue Airways | 3 | 2026-05-20 |
| JBU1476 | - | 3 | 2026-06-28 |
| JBU1475 | - | 3 | 2026-06-28 |
| JBU1468 | JetBlue Airways | 3 | 2026-06-05 |
| JBU1241 | JetBlue Airways | 3 | 2026-05-15 |
| JBU1229 | JetBlue Airways | 3 | 2026-06-18 |
| JBU1158 | - | 3 | 2026-07-01 |
| JBU1142 | JetBlue Airways | 3 | 2026-05-15 |
| JBU1085 | JetBlue Airways | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU789 | DTW → FLL | Jul 13, 20:07 UTC | Jul 13, 22:45 UTC | 2h 39m |
| 2026-07-13 | JBU790 | FLL → DTW | Jul 13, 16:17 UTC | Jul 13, 22:45 UTC | 6h 29m |
| 2026-07-13 | JBU2380 | IAH → FLL | Jul 13, 12:47 UTC | Jul 13, 22:45 UTC | 9h 59m |
| 2026-07-13 | JBU2779 | - | Jul 13, 02:10 UTC | Jul 13, 04:15 UTC | 2h 5m |
| 2026-07-13 | JBU2779 | FLL → IAH | Jul 13, 02:07 UTC | Jul 13, 22:45 UTC | 20h 39m |
| 2026-07-12 | JBU2119 | ORH → FLL | Jul 12, 20:55 UTC | Jul 12, 23:35 UTC | 2h 40m |
| 2026-07-12 | JBU2020 | - | Jul 12, 16:50 UTC | Jul 12, 19:20 UTC | 2h 30m |
| 2026-07-12 | JBU2080 | - | Jul 12, 01:15 UTC | Jul 12, 03:10 UTC | 1h 55m |
| 2026-07-12 | JBU2080 | FLL → DCA | Jul 12, 01:13 UTC | Jul 12, 23:15 UTC | 22h 3m |
| 2026-07-11 | JBU2780 | - | Jul 11, 20:25 UTC | Jul 11, 22:30 UTC | 2h 5m |
| 2026-07-09 | JBU2182 | FLL → DFW | Jul 9, 18:21 UTC | Jul 10, 06:20 UTC | 11h 59m |
| 2026-07-09 | JBU725 | RDU → FLL | Jul 9, 15:25 UTC | Jul 10, 06:20 UTC | 14h 55m |
| 2026-07-09 | JBU726 | - | Jul 9, 11:45 UTC | Jul 9, 13:20 UTC | 1h 35m |
| 2026-07-08 | JBU1167 | HPN → PBI | Jul 8, 18:15 UTC | Jul 9, 17:00 UTC | 22h 46m |
| 2026-07-08 | JBU8514 | EWR → HPN | Jul 8, 16:32 UTC | Jul 9, 13:20 UTC | 20h 49m |
| 2026-07-08 | JBU894 | STI → EWR | Jul 8, 00:47 UTC | Jul 8, 23:15 UTC | 22h 28m |
| 2026-07-07 | JBU1607 | SJU → STI | Jul 7, 21:59 UTC | Jul 8, 20:30 UTC | 22h 32m |
| 2026-07-07 | JBU1903 | RDU → SJU | Jul 7, 16:50 UTC | Jul 8, 04:25 UTC | 11h 36m |
| 2026-07-07 | JBU404 | CLT → RDU | Jul 7, 02:07 UTC | Jul 7, 22:15 UTC | 20h 9m |
| 2026-07-06 | JBU404 | - | Jul 6, 22:50 UTC | Jul 7, 00:15 UTC | 1h 25m |
| 2026-07-06 | JBU404 | - | Jul 6, 20:25 UTC | Jul 6, 20:40 UTC | 15m |
| 2026-07-06 | JBU404 | SJU → CLT | Jul 6, 20:24 UTC | Jul 7, 17:25 UTC | 21h 1m |
| 2026-07-06 | JBU133 | - | Jul 6, 17:15 UTC | Jul 6, 17:35 UTC | 20m |
| 2026-07-06 | JBU133 | - | Jul 6, 15:10 UTC | Jul 6, 15:45 UTC | 35m |
| 2026-07-05 | JBU1043 | - | Jul 5, 23:00 UTC | Jul 6, 01:20 UTC | 2h 20m |
| 2026-07-05 | JBU1042 | SAV → JFK | Jul 5, 19:25 UTC | Jul 5, 21:55 UTC | 2h 30m |
| 2026-07-05 | JBU651 | BOS → MCO | Jul 5, 14:50 UTC | Jul 5, 17:25 UTC | 2h 35m |
| 2026-07-05 | JBU690 | - | Jul 5, 10:45 UTC | Jul 5, 13:25 UTC | 2h 40m |
| 2026-07-04 | JBU2831 | SJU → PUJ | Jul 4, 16:42 UTC | Jul 5, 13:15 UTC | 20h 33m |
| 2026-07-04 | JBU761 | BOS → SJU | Jul 4, 11:08 UTC | Jul 4, 21:00 UTC | 9h 52m |
| 2026-07-04 | JBU761 | BOS → SJU | Jul 4, 11:10 UTC | Jul 4, 14:40 UTC | 3h 30m |
| 2026-07-03 | JBU808 | - | Jul 3, 20:45 UTC | Jul 4, 00:20 UTC | 3h 35m |
| 2026-07-03 | JBU808 | - | Jul 3, 19:25 UTC | Jul 3, 19:45 UTC | 20m |
| 2026-07-03 | JBU807 | - | Jul 3, 17:55 UTC | Jul 3, 18:05 UTC | 10m |
| 2026-07-03 | JBU807 | - | Jul 3, 14:45 UTC | Jul 3, 15:20 UTC | 35m |
| 2026-07-02 | JBU1495 | - | Jul 2, 20:15 UTC | Jul 2, 21:15 UTC | 1h 0m |
| 2026-07-02 | JBU1495 | FLL → CUN | Jul 2, 20:10 UTC | Jul 3, 18:05 UTC | 21h 56m |
| 2026-07-02 | JBU1394 | - | Jul 2, 17:50 UTC | Jul 2, 18:20 UTC | 30m |
| 2026-07-02 | JBU1493 | - | Jul 2, 15:05 UTC | Jul 2, 15:25 UTC | 20m |
| 2026-07-02 | JBU375 | PVD → MCO | Jul 2, 11:10 UTC | Jul 2, 13:35 UTC | 2h 25m |
| 2026-07-02 | JBU376 | - | Jul 2, 01:05 UTC | Jul 2, 03:15 UTC | 2h 10m |
| 2026-07-01 | JBU1158 | - | Jul 1, 15:45 UTC | Jul 1, 22:10 UTC | 6h 25m |
| 2026-06-30 | JBU1612 | AUA → FLL | Jun 30, 19:26 UTC | Jul 1, 17:40 UTC | 22h 14m |
| 2026-06-30 | JBU1611 | - | Jun 30, 15:30 UTC | Jun 30, 16:55 UTC | 1h 25m |
| 2026-06-30 | JBU1611 | FLL → AUA | Jun 30, 15:26 UTC | Jul 1, 14:10 UTC | 22h 45m |
| 2026-06-30 | JBU959 | - | Jun 30, 11:10 UTC | Jun 30, 13:50 UTC | 2h 40m |
| 2026-06-30 | JBU460 | - | Jun 30, 00:39 UTC | Jun 30, 03:05 UTC | 2h 25m |
| 2026-06-29 | JBU2271 | FLL → AUS | Jun 29, 01:24 UTC | Jun 30, 01:14 UTC | 23h 51m |
| 2026-06-28 | JBU1475 | BDL → SJU | Jun 28, 17:02 UTC | Jun 29, 13:39 UTC | 20h 38m |
| 2026-06-28 | JBU1476 | - | Jun 28, 13:00 UTC | Jun 28, 15:14 UTC | 2h 15m |
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 N639JB page for operator, model, and routing details .