sensors Mode-S transponder
A3556F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3138J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A3556F
- Octal
- 50652557
- Decimal
- 10,704,239
- Country
- US
- Tail
- N3138J
- Type
- BCS3
- Flights observed
- 335
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 57m ago
Last known position
Country allocation
The ICAO 24-bit address A3556F 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 |
|---|---|---|---|
| JBU2602 | - | 8 | 2026-07-05 |
| JBU374 | - | 5 | 2026-07-04 |
| JBU2474 | - | 5 | 2026-07-07 |
| JBU791 | - | 4 | 2026-07-09 |
| JBU1254 | - | 4 | 2026-06-23 |
| JBU1093 | JetBlue Airways | 4 | 2026-04-21 |
| JBU896 | JetBlue Airways | 3 | 2026-06-04 |
| JBU895 | JetBlue Airways | 3 | 2026-06-07 |
| JBU640 | JetBlue Airways | 3 | 2026-06-16 |
| JBU618 | JetBlue Airways | 3 | 2026-05-10 |
| JBU592 | - | 3 | 2026-07-06 |
| JBU266 | JetBlue Airways | 3 | 2026-05-24 |
| JBU2468 | JetBlue Airways | 3 | 2026-05-18 |
| JBU2119 | JetBlue Airways | 3 | 2026-04-16 |
| JBU2004 | JetBlue Airways | 3 | 2026-05-05 |
| JBU164 | JetBlue Airways | 3 | 2026-05-15 |
| JBU163 | JetBlue Airways | 3 | 2026-05-15 |
| JBU1604 | JetBlue Airways | 3 | 2026-05-27 |
| JBU1500 | JetBlue Airways | 3 | 2026-05-19 |
| JBU1420 | JetBlue Airways | 3 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2185 | BOS → PIT | Jul 14, 22:21 UTC | Jul 15, 01:45 UTC | 3h 24m |
| 2026-07-14 | JBU1232 | VRB → BOS | Jul 14, 17:05 UTC | Jul 15, 01:45 UTC | 8h 40m |
| 2026-07-14 | JBU715 | BOS → BUF | Jul 14, 02:22 UTC | Jul 15, 01:45 UTC | 23h 23m |
| 2026-07-13 | JBU771 | BOS → CUN | Jul 13, 14:26 UTC | Jul 14, 13:45 UTC | 23h 20m |
| 2026-07-12 | JBU2324 | MCO → DCA | Jul 12, 19:35 UTC | Jul 13, 17:45 UTC | 22h 11m |
| 2026-07-12 | JBU1086 | MCO → BUF | Jul 12, 10:38 UTC | Jul 13, 09:00 UTC | 22h 23m |
| 2026-07-12 | JBU1827 | EWR → MCO | Jul 12, 01:26 UTC | Jul 12, 23:45 UTC | 22h 20m |
| 2026-07-11 | JBU128 | MCO → EWR | Jul 11, 21:11 UTC | Jul 12, 19:45 UTC | 22h 35m |
| 2026-07-11 | JBU51 | BOS → MCO | Jul 11, 16:49 UTC | Jul 12, 15:45 UTC | 22h 57m |
| 2026-07-11 | JBU1282 | RIC → BOS | Jul 11, 14:15 UTC | Jul 12, 13:01 UTC | 22h 46m |
| 2026-07-10 | JBU1782 | VPS → BOS | Jul 10, 21:32 UTC | Jul 11, 19:45 UTC | 22h 14m |
| 2026-07-10 | JBU2040 | CLE → BOS | Jul 10, 14:10 UTC | Jul 11, 11:45 UTC | 21h 36m |
| 2026-07-09 | JBU811 | BOS → ORD | Jul 9, 23:27 UTC | Jul 10, 21:45 UTC | 22h 19m |
| 2026-07-09 | JBU791 | BOS → TPA | Jul 9, 14:50 UTC | Jul 10, 12:55 UTC | 22h 6m |
| 2026-07-09 | JBU820 | SDQ → JFK | Jul 9, 03:05 UTC | Jul 10, 01:45 UTC | 22h 40m |
| 2026-07-08 | JBU1060 | KIN → JFK | Jul 8, 14:17 UTC | Jul 9, 04:25 UTC | 14h 9m |
| 2026-07-08 | JBU59 | JFK → KIN | Jul 8, 09:18 UTC | Jul 9, 04:25 UTC | 19h 8m |
| 2026-07-07 | JBU803 | JFK → SJU | Jul 7, 23:40 UTC | Jul 8, 21:45 UTC | 22h 5m |
| 2026-07-07 | JBU2474 | CHS → JFK | Jul 7, 15:13 UTC | Jul 8, 11:45 UTC | 20h 33m |
| 2026-07-07 | JBU917 | BOS → JFK | Jul 7, 09:27 UTC | Jul 8, 07:35 UTC | 22h 9m |
| 2026-07-06 | JBU592 | TPA → BOS | Jul 6, 22:05 UTC | Jul 7, 00:40 UTC | 2h 35m |
| 2026-07-06 | JBU592 | TPA → BOS | Jul 6, 22:00 UTC | Jul 7, 21:35 UTC | 23h 36m |
| 2026-07-06 | JBU2152 | - | Jul 6, 18:45 UTC | Jul 6, 19:55 UTC | 1h 10m |
| 2026-07-06 | JBU2152 | - | Jul 6, 17:00 UTC | Jul 6, 17:15 UTC | 15m |
| 2026-07-05 | JBU2602 | - | Jul 5, 23:45 UTC | Jul 6, 01:45 UTC | 2h 0m |
| 2026-07-05 | JBU2602 | - | Jul 5, 21:45 UTC | Jul 5, 21:55 UTC | 10m |
| 2026-07-05 | JBU2602 | SJU → HPN | Jul 5, 21:40 UTC | Jul 6, 19:45 UTC | 22h 5m |
| 2026-07-05 | JBU1047 | - | Jul 5, 20:10 UTC | Jul 5, 20:20 UTC | 10m |
| 2026-07-05 | JBU751 | TPA → SJU | Jul 5, 01:06 UTC | Jul 5, 23:45 UTC | 22h 40m |
| 2026-07-04 | JBU791 | - | Jul 4, 11:05 UTC | Jul 4, 11:50 UTC | 45m |
| 2026-07-04 | JBU374 | SYR → BOS | Jul 4, 11:03 UTC | Jul 5, 03:50 UTC | 16h 48m |
| 2026-07-04 | JBU1516 | - | Jul 4, 04:45 UTC | Jul 4, 05:20 UTC | 35m |
| 2026-07-03 | JBU1539 | - | Jul 3, 22:55 UTC | Jul 3, 23:35 UTC | 40m |
| 2026-07-03 | JBU1538 | JFK → MVY | Jul 3, 20:55 UTC | Jul 3, 21:30 UTC | 35m |
| 2026-07-03 | JBU1374 | - | Jul 3, 16:40 UTC | Jul 3, 18:45 UTC | 2h 5m |
| 2026-07-03 | JBU1373 | - | Jul 3, 13:35 UTC | Jul 3, 15:20 UTC | 1h 45m |
| 2026-07-02 | JBU405 | JFK → ORD | Jul 2, 18:45 UTC | Jul 2, 20:45 UTC | 2h 0m |
| 2026-07-02 | JBU405 | JFK → ORD | Jul 2, 18:45 UTC | Jul 3, 17:45 UTC | 23h 1m |
| 2026-07-02 | JBU1154 | - | Jul 2, 14:45 UTC | Jul 2, 17:00 UTC | 2h 15m |
| 2026-07-02 | JBU953 | - | Jul 2, 10:50 UTC | Jul 2, 13:10 UTC | 2h 20m |
| 2026-07-01 | JBU860 | JFK → JFK | Jul 1, 19:25 UTC | Jul 2, 04:00 UTC | 8h 35m |
| 2026-07-01 | JBU854 | - | Jul 1, 14:30 UTC | Jul 1, 16:45 UTC | 2h 15m |
| 2026-07-01 | JBU953 | - | Jul 1, 10:50 UTC | Jul 1, 13:05 UTC | 2h 15m |
| 2026-06-30 | JBU737 | - | Jun 30, 11:20 UTC | Jun 30, 13:35 UTC | 2h 15m |
| 2026-06-30 | JBU737 | BDL → MCO | Jun 30, 11:19 UTC | Jul 1, 01:35 UTC | 14h 17m |
| 2026-06-30 | JBU338 | MCO → BDL | Jun 30, 01:04 UTC | Jun 30, 03:25 UTC | 2h 21m |
| 2026-06-29 | JBU2134 | - | Jun 29, 22:59 UTC | Jun 29, 23:49 UTC | 50m |
| 2026-06-29 | JBU2134 | - | Jun 29, 21:05 UTC | Jun 29, 21:19 UTC | 15m |
| 2026-06-29 | JBU1033 | - | Jun 29, 18:49 UTC | Jun 29, 19:09 UTC | 20m |
| 2026-06-29 | JBU1033 | - | Jun 29, 16:39 UTC | Jun 29, 17:19 UTC | 40m |
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 N3138J page for operator, model, and routing details .