sensors Mode-S transponder
A1BC29
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2102J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1BC29
- Octal
- 50336051
- Decimal
- 10,599,465
- Country
- US
- Tail
- N2102J
- Type
- A21N
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address A1BC29 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 |
|---|---|---|---|
| JBU965 | JetBlue Airways | 14 | 2026-05-15 |
| JBU966 | JetBlue Airways | 13 | 2026-05-12 |
| JBU882 | JetBlue Airways | 9 | 2026-05-03 |
| JBU505 | - | 8 | 2026-07-12 |
| JBU881 | JetBlue Airways | 7 | 2026-05-03 |
| JBU2018 | - | 7 | 2026-07-11 |
| JBU939 | JetBlue Airways | 6 | 2026-05-01 |
| JBU117 | - | 6 | 2026-07-10 |
| JBU466 | - | 5 | 2026-07-09 |
| JBU788 | - | 4 | 2026-07-08 |
| JBU787 | JetBlue Airways | 4 | 2026-06-17 |
| JBU528 | JetBlue Airways | 4 | 2026-05-31 |
| JBU509 | JetBlue Airways | 4 | 2026-05-08 |
| JBU465 | - | 4 | 2026-06-18 |
| JBU1966 | - | 4 | 2026-07-09 |
| JBU1929 | JetBlue Airways | 4 | 2026-05-27 |
| JBU1769 | - | 4 | 2026-07-07 |
| JBU1255 | JetBlue Airways | 4 | 2026-05-19 |
| JBU887 | - | 3 | 2026-07-06 |
| JBU637 | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1149 | - | Jul 13, 23:40 UTC | Jul 14, 01:35 UTC | 1h 55m |
| 2026-07-13 | JBU1612 | AUA → FLL | Jul 13, 19:00 UTC | Jul 13, 21:35 UTC | 2h 35m |
| 2026-07-13 | JBU706 | - | Jul 13, 02:01 UTC | Jul 13, 04:35 UTC | 2h 35m |
| 2026-07-13 | JBU706 | FLL → EWR | Jul 13, 01:59 UTC | Jul 14, 00:15 UTC | 22h 17m |
| 2026-07-12 | JBU505 | JFK → FLL | Jul 12, 10:50 UTC | Jul 12, 22:55 UTC | 12h 5m |
| 2026-07-11 | JBU2018 | - | Jul 11, 19:35 UTC | Jul 12, 00:01 UTC | 4h 25m |
| 2026-07-10 | JBU117 | JFK → POS | Jul 10, 15:41 UTC | Jul 10, 19:50 UTC | 4h 10m |
| 2026-07-09 | JBU466 | GEO → JFK | Jul 9, 22:37 UTC | Jul 10, 19:50 UTC | 21h 14m |
| 2026-07-09 | JBU1966 | GEO → JFK | Jul 9, 07:52 UTC | Jul 10, 04:00 UTC | 20h 8m |
| 2026-07-08 | JBU788 | SXM → JFK | Jul 8, 15:20 UTC | Jul 9, 13:40 UTC | 22h 20m |
| 2026-07-08 | JBU60 | KIN → JFK | Jul 8, 03:05 UTC | Jul 9, 01:35 UTC | 22h 31m |
| 2026-07-07 | JBU1759 | - | Jul 7, 21:55 UTC | Jul 8, 06:15 UTC | 8h 20m |
| 2026-07-07 | JBU1769 | JFK → JFK | Jul 7, 03:50 UTC | Jul 7, 18:05 UTC | 14h 15m |
| 2026-07-06 | JBU887 | JFK → SXM | Jul 6, 16:19 UTC | Jul 7, 16:15 UTC | 23h 56m |
| 2026-07-06 | JBU887 | - | Jul 6, 16:20 UTC | Jul 6, 19:30 UTC | 3h 10m |
| 2026-07-05 | JBU309 | JFK → JFK | Jul 5, 23:25 UTC | Jul 6, 13:25 UTC | 14h 0m |
| 2026-07-05 | JBU1737 | JFK → JFK | Jul 5, 12:00 UTC | Jul 5, 20:15 UTC | 8h 15m |
| 2026-07-04 | JBU117 | JFK → POS | Jul 4, 17:09 UTC | Jul 5, 12:45 UTC | 19h 36m |
| 2026-07-04 | JBU1966 | GEO → JFK | Jul 4, 04:11 UTC | Jul 5, 00:35 UTC | 20h 25m |
| 2026-07-03 | JBU1770 | GYE → JFK | Jul 3, 12:16 UTC | Jul 4, 09:30 UTC | 21h 14m |
| 2026-07-03 | JBU1769 | - | Jul 3, 04:05 UTC | Jul 3, 07:45 UTC | 3h 40m |
| 2026-07-02 | JBU1533 | JFK → CTG | Jul 2, 14:15 UTC | Jul 3, 01:30 UTC | 11h 15m |
| 2026-07-01 | JBU117 | - | Jul 1, 12:45 UTC | Jul 1, 16:00 UTC | 3h 15m |
| 2026-07-01 | JBU117 | JFK → POS | Jul 1, 12:40 UTC | Jul 2, 00:00 UTC | 11h 21m |
| 2026-06-30 | JBU1966 | - | Jun 30, 21:25 UTC | Jul 1, 09:20 UTC | 11h 55m |
| 2026-06-30 | JBU1770 | GYE → JFK | Jun 30, 12:06 UTC | Jul 1, 09:25 UTC | 21h 20m |
| 2026-06-30 | JBU1769 | JFK → JFK | Jun 30, 04:35 UTC | Jun 30, 18:05 UTC | 13h 30m |
| 2026-06-29 | JBU1533 | JFK → CTG | Jun 29, 14:19 UTC | Jun 30, 00:20 UTC | 10h 0m |
| 2026-06-28 | JBU2018 | - | Jun 28, 19:34 UTC | Jun 29, 00:10 UTC | 4h 35m |
| 2026-06-28 | JBU2018 | POS → JFK | Jun 28, 19:24 UTC | Jun 29, 16:50 UTC | 21h 26m |
| 2026-06-27 | JBU637 | - | Jun 27, 22:29 UTC | Jun 27, 23:00 UTC | 30m |
| 2026-06-27 | JBU637 | JFK → STI | Jun 27, 22:28 UTC | Jun 28, 20:54 UTC | 22h 27m |
| 2026-06-27 | JBU380 | JFK → JFK | Jun 27, 11:25 UTC | Jun 27, 19:49 UTC | 8h 25m |
| 2026-06-26 | JBU1936 | JFK → JFK | Jun 26, 22:34 UTC | Jun 27, 08:20 UTC | 9h 45m |
| 2026-06-26 | JBU380 | JFK → JFK | Jun 26, 11:20 UTC | Jun 26, 19:55 UTC | 8h 35m |
| 2026-06-25 | JBU2018 | JFK → JFK | Jun 25, 12:44 UTC | Jun 25, 23:44 UTC | 11h 0m |
| 2026-06-24 | JBU2662 | JFK → JFK | Jun 24, 15:24 UTC | Jun 25, 01:44 UTC | 10h 20m |
| 2026-06-24 | JBU1966 | GEO → JFK | Jun 24, 04:02 UTC | Jun 25, 02:10 UTC | 22h 8m |
| 2026-06-23 | JBU1965 | - | Jun 23, 21:14 UTC | Jun 24, 06:15 UTC | 9h 0m |
| 2026-06-23 | JBU1769 | JFK → JFK | Jun 23, 04:19 UTC | Jun 23, 18:20 UTC | 14h 0m |
| 2026-06-22 | JBU1188 | - | Jun 22, 13:49 UTC | Jun 22, 23:10 UTC | 9h 20m |
| 2026-06-21 | JBU637 | JFK → STI | Jun 21, 22:44 UTC | Jun 22, 10:19 UTC | 11h 35m |
| 2026-06-21 | JBU380 | MBJ → JFK | Jun 21, 11:30 UTC | Jun 21, 19:55 UTC | 8h 25m |
| 2026-06-20 | JBU1869 | JFK → PUJ | Jun 20, 14:29 UTC | Jun 20, 15:04 UTC | 35m |
| 2026-06-20 | JBU1869 | JFK → PUJ | Jun 20, 14:29 UTC | Jun 21, 12:14 UTC | 21h 46m |
| 2026-06-20 | JBU130 | RSW → JFK | Jun 20, 10:09 UTC | Jun 20, 12:24 UTC | 2h 15m |
| 2026-06-20 | JBU2129 | BOS → SDQ | Jun 20, 02:04 UTC | Jun 20, 04:54 UTC | 2h 50m |
| 2026-06-19 | JBU1188 | - | Jun 19, 19:29 UTC | Jun 19, 23:04 UTC | 3h 35m |
| 2026-06-18 | JBU466 | RSW → BOS | Jun 18, 22:22 UTC | Jun 19, 22:14 UTC | 23h 53m |
| 2026-06-18 | JBU466 | RSW → BOS | Jun 18, 22:22 UTC | Jun 19, 22:14 UTC | 23h 53m |
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 N2102J page for operator, model, and routing details .