sensors Mode-S transponder
A85C3E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N638JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A85C3E
- Octal
- 52056076
- Decimal
- 11,033,662
- Country
- US
- Tail
- N638JB
- Type
- A320
- Flights observed
- 280
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address A85C3E 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 |
|---|---|---|---|
| JBU1640 | JetBlue Airways | 5 | 2026-06-10 |
| JBU768 | JetBlue Airways | 4 | 2026-05-17 |
| JBU687 | JetBlue Airways | 4 | 2026-04-17 |
| JBU68 | - | 4 | 2026-07-06 |
| JBU158 | JetBlue Airways | 4 | 2026-06-01 |
| JBU504 | - | 3 | 2026-07-03 |
| JBU395 | JetBlue Airways | 3 | 2026-05-08 |
| JBU383 | JetBlue Airways | 3 | 2026-04-21 |
| JBU2602 | JetBlue Airways | 3 | 2026-04-26 |
| JBU2153 | JetBlue Airways | 3 | 2026-06-07 |
| JBU1639 | JetBlue Airways | 3 | 2026-06-10 |
| JBU1605 | - | 3 | 2026-04-13 |
| JBU133 | JetBlue Airways | 3 | 2026-05-17 |
| JBU1294 | JetBlue Airways | 3 | 2026-04-29 |
| JBU1237 | - | 3 | 2026-07-04 |
| JBU1196 | JetBlue Airways | 3 | 2026-05-25 |
| JBU1184 | JetBlue Airways | 3 | 2026-05-04 |
| JBU1036 | JetBlue Airways | 3 | 2026-04-25 |
| JBU947 | - | 2 | 2026-06-23 |
| JBU939 | - | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | JBU8585 | JFK → SAL | Jul 10, 12:40 UTC | Jul 10, 14:50 UTC | 2h 10m |
| 2026-07-09 | JBU320 | - | Jul 9, 10:55 UTC | Jul 9, 11:30 UTC | 35m |
| 2026-07-09 | JBU320 | ATL → JFK | Jul 9, 10:51 UTC | Jul 10, 02:45 UTC | 15h 54m |
| 2026-07-09 | JBU1798 | - | Jul 9, 01:10 UTC | Jul 9, 02:35 UTC | 1h 25m |
| 2026-07-08 | JBU1131 | - | Jul 8, 22:40 UTC | Jul 8, 23:50 UTC | 1h 10m |
| 2026-07-08 | JBU1697 | - | Jul 8, 02:40 UTC | Jul 8, 04:05 UTC | 1h 25m |
| 2026-07-08 | JBU1697 | ATL → FLL | Jul 8, 02:38 UTC | Jul 9, 01:30 UTC | 22h 52m |
| 2026-07-07 | JBU2098 | - | Jul 7, 23:30 UTC | Jul 8, 00:50 UTC | 1h 20m |
| 2026-07-07 | JBU1496 | CUN → FLL | Jul 7, 20:00 UTC | Jul 7, 21:15 UTC | 1h 15m |
| 2026-07-07 | JBU771 | BOS → CUN | Jul 7, 14:25 UTC | Jul 7, 18:30 UTC | 4h 5m |
| 2026-07-06 | JBU68 | - | Jul 6, 19:55 UTC | Jul 6, 21:40 UTC | 1h 45m |
| 2026-07-06 | JBU68 | CHS → BOS | Jul 6, 19:50 UTC | Jul 7, 18:30 UTC | 22h 41m |
| 2026-07-06 | JBU267 | - | Jul 6, 15:00 UTC | Jul 6, 16:50 UTC | 1h 50m |
| 2026-07-05 | JBU2275 | PHL → FLL | Jul 5, 21:20 UTC | Jul 6, 16:50 UTC | 19h 30m |
| 2026-07-05 | JBU2276 | - | Jul 5, 17:10 UTC | Jul 5, 17:30 UTC | 20m |
| 2026-07-05 | JBU669 | BOS → FLL | Jul 5, 12:48 UTC | Jul 6, 11:30 UTC | 22h 43m |
| 2026-07-05 | JBU669 | BOS → FLL | Jul 5, 12:50 UTC | Jul 5, 15:45 UTC | 2h 55m |
| 2026-07-05 | JBU1136 | - | Jul 5, 00:45 UTC | Jul 5, 02:05 UTC | 1h 20m |
| 2026-07-04 | JBU1237 | BOS → DTW | Jul 4, 21:25 UTC | Jul 4, 23:30 UTC | 2h 5m |
| 2026-07-04 | JBU1979 | DCA → FLL | Jul 4, 01:34 UTC | Jul 5, 01:30 UTC | 23h 56m |
| 2026-07-03 | JBU1880 | - | Jul 3, 21:00 UTC | Jul 3, 22:55 UTC | 1h 55m |
| 2026-07-03 | JBU1880 | FLL → DCA | Jul 3, 20:59 UTC | Jul 4, 18:35 UTC | 21h 36m |
| 2026-07-03 | JBU2201 | JFK → FLL | Jul 3, 17:10 UTC | Jul 3, 19:30 UTC | 2h 20m |
| 2026-07-03 | JBU504 | - | Jul 3, 02:45 UTC | Jul 3, 03:40 UTC | 55m |
| 2026-07-03 | JBU504 | - | Jul 3, 00:15 UTC | Jul 3, 00:25 UTC | 10m |
| 2026-07-02 | JBU2031 | - | Jul 2, 19:35 UTC | Jul 2, 19:50 UTC | 15m |
| 2026-07-02 | JBU2332 | - | Jul 2, 17:45 UTC | Jul 2, 17:55 UTC | 10m |
| 2026-07-02 | JBU2831 | - | Jul 2, 15:20 UTC | Jul 2, 15:35 UTC | 15m |
| 2026-07-02 | JBU1089 | - | Jul 2, 13:00 UTC | Jul 2, 13:30 UTC | 30m |
| 2026-07-02 | JBU1089 | - | Jul 2, 10:10 UTC | Jul 2, 10:55 UTC | 45m |
| 2026-07-02 | JBU894 | - | Jul 2, 01:10 UTC | Jul 2, 02:10 UTC | 1h 0m |
| 2026-07-01 | JBU1607 | SJU → STI | Jul 1, 20:30 UTC | Jul 1, 20:45 UTC | 15m |
| 2026-07-01 | JBU2332 | - | Jul 1, 17:55 UTC | Jul 1, 18:05 UTC | 10m |
| 2026-06-30 | JBU1003 | MCO → SJU | Jun 30, 22:45 UTC | Jul 1, 20:45 UTC | 22h 1m |
| 2026-06-30 | JBU552 | MCO → BOS | Jun 30, 12:55 UTC | Jul 1, 01:25 UTC | 12h 31m |
| 2026-06-29 | JBU2018 | - | Jun 29, 19:54 UTC | Jun 30, 01:00 UTC | 5h 5m |
| 2026-06-29 | JBU2018 | POS → JFK | Jun 29, 19:37 UTC | Jun 30, 19:30 UTC | 23h 54m |
| 2026-06-29 | JBU117 | - | Jun 29, 13:14 UTC | Jun 29, 17:19 UTC | 4h 5m |
| 2026-06-29 | JBU66 | ABQ → JFK | Jun 29, 06:54 UTC | Jun 29, 10:29 UTC | 3h 35m |
| 2026-06-28 | JBU65 | JFK → ABQ | Jun 28, 23:39 UTC | Jun 29, 03:49 UTC | 4h 10m |
| 2026-06-28 | JBU779 | JFK → JFK | Jun 28, 12:29 UTC | Jun 28, 20:54 UTC | 8h 25m |
| 2026-06-27 | JBU939 | - | Jun 27, 13:35 UTC | Jun 27, 17:29 UTC | 3h 55m |
| 2026-06-27 | JBU939 | JFK → SJD | Jun 27, 13:32 UTC | Jun 28, 01:29 UTC | 11h 58m |
| 2026-06-27 | JBU1185 | ROC → JFK | Jun 27, 10:29 UTC | Jun 27, 11:25 UTC | 55m |
| 2026-06-26 | JBU149 | JFK → GND | Jun 26, 13:36 UTC | Jun 27, 13:30 UTC | 23h 54m |
| 2026-06-25 | JBU1496 | CUN → FLL | Jun 25, 19:51 UTC | Jun 26, 17:15 UTC | 21h 24m |
| 2026-06-25 | JBU771 | BOS → CUN | Jun 25, 14:09 UTC | Jun 26, 13:30 UTC | 23h 21m |
| 2026-06-24 | JBU1237 | BOS → DTW | Jun 24, 20:12 UTC | Jun 25, 18:04 UTC | 21h 53m |
| 2026-06-24 | JBU2102 | - | Jun 24, 13:20 UTC | Jun 24, 15:44 UTC | 2h 25m |
| 2026-06-24 | JBU2102 | FLL → JFK | Jun 24, 13:17 UTC | Jun 25, 00:44 UTC | 11h 28m |
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 N638JB page for operator, model, and routing details .