sensors Mode-S transponder
A1A435
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2047J · AIRBUS A-321neo · operated by UMB BANK NA TRUSTEE
- Hex
- A1A435
- Octal
- 50322065
- Decimal
- 10,593,333
- Country
- US
- Tail
- N2047J
- Type
- A21N
- Flights observed
- 178
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A1A435 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 |
|---|---|---|---|
| JBU882 | JetBlue Airways | 9 | 2026-04-21 |
| JBU881 | - | 6 | 2026-04-21 |
| JBU836 | JetBlue Airways | 6 | 2026-05-13 |
| JBU1965 | - | 6 | 2026-07-13 |
| JBU1794 | - | 6 | 2026-04-14 |
| JBU610 | - | 5 | 2026-06-22 |
| JBU465 | - | 5 | 2026-07-08 |
| JBU2709 | JetBlue Airways | 5 | 2026-05-22 |
| JBU1929 | JetBlue Airways | 5 | 2026-06-07 |
| JBU1818 | JetBlue Airways | 5 | 2026-05-04 |
| JBU117 | - | 5 | 2026-07-12 |
| JBU939 | JetBlue Airways | 4 | 2026-06-14 |
| JBU771 | JetBlue Airways | 4 | 2026-06-06 |
| JBU509 | JetBlue Airways | 4 | 2026-05-19 |
| JBU1533 | JetBlue Airways | 4 | 2026-07-03 |
| JBU1255 | - | 4 | 2026-07-10 |
| JBU505 | - | 3 | 2026-07-09 |
| JBU466 | JetBlue Airways | 3 | 2026-06-10 |
| JBU2904 | - | 3 | 2026-07-08 |
| JBU2210 | JetBlue Airways | 3 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1965 | JFK → GEO | Jul 13, 23:13 UTC | Jul 14, 14:25 UTC | 15h 13m |
| 2026-07-13 | JBU788 | SXM → JFK | Jul 13, 15:09 UTC | Jul 14, 10:55 UTC | 19h 47m |
| 2026-07-13 | JBU787 | JFK → SXM | Jul 13, 10:18 UTC | Jul 14, 06:55 UTC | 20h 38m |
| 2026-07-12 | JBU2018 | - | Jul 12, 19:45 UTC | Jul 13, 00:10 UTC | 4h 25m |
| 2026-07-12 | JBU2018 | POS → JFK | Jul 12, 19:32 UTC | Jul 13, 18:55 UTC | 23h 24m |
| 2026-07-12 | JBU117 | - | Jul 12, 13:01 UTC | Jul 12, 17:15 UTC | 4h 15m |
| 2026-07-12 | JBU1770 | - | Jul 12, 01:35 UTC | Jul 12, 05:10 UTC | 3h 35m |
| 2026-07-10 | JBU1255 | - | Jul 10, 16:45 UTC | Jul 10, 18:40 UTC | 1h 55m |
| 2026-07-10 | JBU1255 | FLL → GYE | Jul 10, 16:42 UTC | Jul 10, 18:40 UTC | 1h 59m |
| 2026-07-09 | JBU505 | JFK → FLL | Jul 9, 10:45 UTC | Jul 9, 22:55 UTC | 12h 10m |
| 2026-07-08 | JBU465 | JFK → GEO | Jul 8, 15:57 UTC | Jul 9, 13:10 UTC | 21h 13m |
| 2026-07-08 | JBU2904 | - | Jul 8, 12:45 UTC | Jul 8, 14:05 UTC | 1h 20m |
| 2026-07-08 | JBU2904 | - | Jul 8, 10:25 UTC | Jul 8, 10:40 UTC | 15m |
| 2026-07-08 | JBU2904 | SJU → JFK | Jul 8, 10:22 UTC | Jul 9, 03:40 UTC | 17h 19m |
| 2026-07-08 | JBU303 | - | Jul 8, 04:30 UTC | Jul 8, 04:50 UTC | 20m |
| 2026-07-08 | JBU303 | - | Jul 8, 01:35 UTC | Jul 8, 02:15 UTC | 40m |
| 2026-07-07 | JBU1004 | - | Jul 7, 22:35 UTC | Jul 7, 23:20 UTC | 45m |
| 2026-07-07 | JBU1004 | - | Jul 7, 19:55 UTC | Jul 7, 20:15 UTC | 20m |
| 2026-07-07 | JBU503 | - | Jul 7, 17:20 UTC | Jul 7, 17:45 UTC | 25m |
| 2026-07-07 | JBU503 | - | Jul 7, 14:30 UTC | Jul 7, 15:05 UTC | 35m |
| 2026-07-07 | JBU160 | - | Jul 7, 09:00 UTC | Jul 7, 11:15 UTC | 2h 15m |
| 2026-07-06 | JBU160 | - | Jul 6, 09:20 UTC | Jul 7, 09:15 UTC | 23h 55m |
| 2026-07-06 | JBU1059 | - | Jul 6, 07:10 UTC | Jul 6, 09:25 UTC | 2h 15m |
| 2026-07-05 | JBU1188 | - | Jul 5, 19:30 UTC | Jul 5, 23:05 UTC | 3h 35m |
| 2026-07-04 | JBU1965 | JFK → GEO | Jul 4, 23:06 UTC | Jul 5, 19:55 UTC | 20h 49m |
| 2026-07-04 | JBU380 | MBJ → JFK | Jul 4, 16:46 UTC | Jul 5, 11:05 UTC | 18h 19m |
| 2026-07-04 | JBU1179 | - | Jul 4, 11:40 UTC | Jul 4, 14:00 UTC | 2h 20m |
| 2026-07-03 | JBU1533 | JFK → CTG | Jul 3, 13:46 UTC | Jul 4, 13:15 UTC | 23h 30m |
| 2026-07-02 | JBU2018 | POS → JFK | Jul 2, 19:19 UTC | Jul 3, 16:15 UTC | 20h 57m |
| 2026-07-02 | JBU117 | JFK → POS | Jul 2, 13:16 UTC | Jul 2, 23:55 UTC | 10h 39m |
| 2026-07-01 | JBU1965 | JFK → GEO | Jul 1, 21:27 UTC | Jul 2, 20:50 UTC | 23h 23m |
| 2026-07-01 | JBU1769 | JFK → GYE | Jul 1, 03:52 UTC | Jul 2, 02:05 UTC | 22h 14m |
| 2026-06-30 | JBU1533 | JFK → CTG | Jun 30, 13:45 UTC | Jun 30, 16:05 UTC | 2h 20m |
| 2026-06-30 | JBU1533 | JFK → CTG | Jun 30, 13:43 UTC | Jul 1, 07:35 UTC | 17h 52m |
| 2026-06-29 | JBU1691 | JFK → LIR | Jun 29, 13:42 UTC | Jun 30, 01:30 UTC | 11h 49m |
| 2026-06-29 | JBU1691 | JFK → LIR | Jun 29, 13:44 UTC | Jun 29, 17:45 UTC | 4h 0m |
| 2026-06-28 | JBU1965 | - | Jun 28, 22:04 UTC | Jun 29, 09:50 UTC | 11h 45m |
| 2026-06-28 | JBU1769 | JFK → JFK | Jun 28, 03:55 UTC | Jun 28, 18:14 UTC | 14h 20m |
| 2026-06-27 | JBU1532 | CTG → JFK | Jun 27, 19:59 UTC | Jun 28, 18:19 UTC | 22h 21m |
| 2026-06-27 | JBU1532 | JFK → JFK | Jun 27, 14:20 UTC | Jun 28, 00:59 UTC | 10h 40m |
| 2026-06-26 | JBU117 | - | Jun 26, 13:04 UTC | Jun 26, 16:49 UTC | 3h 45m |
| 2026-06-26 | JBU117 | JFK → POS | Jun 26, 13:02 UTC | Jun 27, 00:14 UTC | 11h 13m |
| 2026-06-26 | JBU1966 | - | Jun 26, 00:24 UTC | Jun 26, 09:20 UTC | 8h 55m |
| 2026-06-25 | JBU1965 | - | Jun 25, 21:35 UTC | Jun 25, 21:55 UTC | 20m |
| 2026-06-25 | JBU1769 | JFK → JFK | Jun 25, 03:34 UTC | Jun 25, 18:04 UTC | 14h 30m |
| 2026-06-24 | JBU1668 | PUJ → JFK | Jun 24, 20:54 UTC | Jun 25, 18:04 UTC | 21h 11m |
| 2026-06-24 | JBU1669 | - | Jun 24, 15:29 UTC | Jun 24, 15:59 UTC | 30m |
| 2026-06-24 | JBU1669 | JFK → PUJ | Jun 24, 15:29 UTC | Jun 25, 14:29 UTC | 23h 1m |
| 2026-06-23 | JBU361 | JFK → JFK | Jun 23, 13:00 UTC | Jun 23, 23:34 UTC | 10h 35m |
| 2026-06-22 | JBU610 | SDQ → JFK | Jun 22, 09:58 UTC | Jun 23, 02:34 UTC | 16h 37m |
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 N2047J page for operator, model, and routing details .