sensors Mode-S transponder
AA4252
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N760JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AA4252
- Octal
- 52441122
- Decimal
- 11,158,098
- Country
- US
- Tail
- N760JB
- Type
- A320
- Flights observed
- 305
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address AA4252 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 |
|---|---|---|---|
| JBU1553 | - | 7 | 2026-07-01 |
| JBU2153 | - | 4 | 2026-07-13 |
| JBU1851 | JetBlue Airways | 4 | 2026-05-13 |
| JBU1797 | - | 4 | 2026-06-29 |
| JBU1704 | - | 4 | 2026-06-21 |
| JBU1698 | - | 4 | 2026-06-19 |
| JBU154 | - | 4 | 2026-07-12 |
| JBU936 | JetBlue Airways | 3 | 2026-07-01 |
| JBU2838 | JetBlue Airways | 3 | 2026-05-19 |
| JBU222 | JetBlue Airways | 3 | 2026-05-12 |
| JBU1852 | JetBlue Airways | 3 | 2026-04-14 |
| JBU1754 | JetBlue Airways | 3 | 2026-05-23 |
| JBU1638 | JetBlue Airways | 3 | 2026-05-16 |
| JBU1601 | JetBlue Airways | 3 | 2026-05-02 |
| JBU152 | JetBlue Airways | 3 | 2026-05-09 |
| JBU151 | JetBlue Airways | 3 | 2026-05-09 |
| JBU1471 | JetBlue Airways | 3 | 2026-05-28 |
| JBU1378 | JetBlue Airways | 3 | 2026-04-16 |
| JBU1237 | - | 3 | 2026-06-27 |
| JBU121 | JetBlue Airways | 3 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1434 | SJU → MCO | Jul 14, 09:08 UTC | Jul 14, 15:35 UTC | 6h 28m |
| 2026-07-13 | JBU1475 | BDL → SJU | Jul 13, 16:07 UTC | Jul 14, 14:30 UTC | 22h 24m |
| 2026-07-13 | JBU1476 | SJU → BDL | Jul 13, 11:15 UTC | Jul 14, 03:10 UTC | 15h 56m |
| 2026-07-13 | JBU2153 | - | Jul 13, 02:01 UTC | Jul 13, 02:25 UTC | 25m |
| 2026-07-12 | JBU154 | SJU → FLL | Jul 12, 22:25 UTC | Jul 13, 00:40 UTC | 2h 15m |
| 2026-07-12 | JBU154 | SJU → FLL | Jul 12, 22:23 UTC | Jul 13, 16:55 UTC | 18h 33m |
| 2026-07-12 | JBU2632 | - | Jul 12, 20:55 UTC | Jul 12, 21:10 UTC | 15m |
| 2026-07-12 | JBU2631 | - | Jul 12, 19:20 UTC | Jul 12, 19:35 UTC | 15m |
| 2026-07-12 | JBU133 | - | Jul 12, 15:30 UTC | Jul 12, 18:05 UTC | 2h 35m |
| 2026-07-12 | JBU2695 | - | Jul 12, 11:45 UTC | Jul 12, 13:50 UTC | 2h 5m |
| 2026-07-11 | JBU1366 | - | Jul 11, 18:15 UTC | Jul 11, 18:30 UTC | 15m |
| 2026-07-11 | JBU1365 | - | Jul 11, 15:15 UTC | Jul 11, 16:35 UTC | 1h 20m |
| 2026-07-11 | JBU1365 | TPA → CUN | Jul 11, 15:11 UTC | Jul 12, 14:30 UTC | 23h 20m |
| 2026-07-11 | JBU8425 | JFK → TPA | Jul 11, 10:30 UTC | Jul 11, 12:45 UTC | 2h 15m |
| 2026-07-09 | JBU1112 | CUR → JFK | Jul 9, 22:46 UTC | Jul 10, 15:25 UTC | 16h 40m |
| 2026-07-09 | JBU1185 | ROC → JFK | Jul 9, 10:49 UTC | Jul 10, 03:55 UTC | 17h 6m |
| 2026-07-09 | JBU1186 | JFK → ROC | Jul 9, 02:36 UTC | Jul 10, 02:30 UTC | 23h 55m |
| 2026-07-08 | JBU350 | - | Jul 8, 20:10 UTC | Jul 9, 00:25 UTC | 4h 15m |
| 2026-07-08 | JBU350 | GND → JFK | Jul 8, 20:00 UTC | Jul 9, 17:20 UTC | 21h 20m |
| 2026-07-08 | JBU149 | - | Jul 8, 13:45 UTC | Jul 8, 18:20 UTC | 4h 35m |
| 2026-07-08 | JBU1794 | - | Jul 8, 01:25 UTC | Jul 8, 03:45 UTC | 2h 20m |
| 2026-07-07 | JBU1794 | - | Jul 7, 23:00 UTC | Jul 7, 23:40 UTC | 40m |
| 2026-07-07 | JBU1793 | - | Jul 7, 15:00 UTC | Jul 7, 19:15 UTC | 4h 15m |
| 2026-07-06 | JBU2662 | - | Jul 6, 21:25 UTC | Jul 7, 01:40 UTC | 4h 15m |
| 2026-07-06 | JBU2661 | - | Jul 6, 19:25 UTC | Jul 6, 19:45 UTC | 20m |
| 2026-07-06 | JBU2661 | - | Jul 6, 15:25 UTC | Jul 6, 18:45 UTC | 3h 20m |
| 2026-07-05 | JBU308 | JFK → PWM | Jul 5, 06:21 UTC | Jul 6, 04:30 UTC | 22h 9m |
| 2026-07-04 | JBU2032 | BDA → JFK | Jul 4, 18:53 UTC | Jul 5, 11:05 UTC | 16h 12m |
| 2026-07-04 | JBU126 | TPA → JFK | Jul 4, 10:16 UTC | Jul 5, 07:15 UTC | 21h 0m |
| 2026-07-04 | JBU2752 | SJU → TPA | Jul 4, 02:55 UTC | Jul 4, 20:55 UTC | 18h 1m |
| 2026-07-03 | JBU153 | FLL → SJU | Jul 3, 23:31 UTC | Jul 4, 20:55 UTC | 21h 25m |
| 2026-07-03 | JBU1158 | LIR → FLL | Jul 3, 19:06 UTC | Jul 4, 16:40 UTC | 21h 34m |
| 2026-07-03 | JBU462 | SJU → BOS | Jul 3, 00:45 UTC | Jul 4, 00:05 UTC | 23h 20m |
| 2026-07-03 | JBU462 | SJU → BOS | Jul 3, 00:45 UTC | Jul 4, 00:05 UTC | 23h 20m |
| 2026-07-02 | JBU1719 | - | Jul 2, 19:35 UTC | Jul 2, 22:40 UTC | 3h 5m |
| 2026-07-01 | JBU2931 | SJU → PUJ | Jul 1, 22:37 UTC | Jul 2, 22:30 UTC | 23h 54m |
| 2026-07-01 | JBU435 | STT → SJU | Jul 1, 20:33 UTC | Jul 2, 17:50 UTC | 21h 17m |
| 2026-07-01 | JBU936 | SJU → STT | Jul 1, 19:15 UTC | Jul 1, 19:25 UTC | 10m |
| 2026-07-01 | JBU936 | SJU → STT | Jul 1, 19:13 UTC | Jul 2, 17:50 UTC | 22h 37m |
| 2026-07-01 | JBU1553 | - | Jul 1, 17:50 UTC | Jul 1, 18:00 UTC | 10m |
| 2026-07-01 | JBU1553 | - | Jul 1, 15:50 UTC | Jul 1, 16:15 UTC | 25m |
| 2026-07-01 | JBU2005 | - | Jul 1, 11:25 UTC | Jul 1, 13:45 UTC | 2h 20m |
| 2026-06-30 | JBU293 | MCO → SJU | Jun 30, 10:11 UTC | Jul 1, 03:35 UTC | 17h 24m |
| 2026-06-30 | JBU334 | SJU → MCO | Jun 30, 02:52 UTC | Jul 1, 02:30 UTC | 23h 38m |
| 2026-06-29 | JBU2549 | FLL → SDQ | Jun 29, 15:30 UTC | Jun 30, 14:05 UTC | 22h 35m |
| 2026-06-29 | JBU1797 | ATL → FLL | Jun 29, 11:39 UTC | Jun 29, 13:04 UTC | 1h 25m |
| 2026-06-29 | JBU1797 | ATL → FLL | Jun 29, 11:39 UTC | Jun 30, 10:30 UTC | 22h 52m |
| 2026-06-29 | JBU1798 | PPM → ATL | Jun 29, 00:14 UTC | Jun 29, 01:29 UTC | 1h 15m |
| 2026-06-28 | JBU1158 | - | Jun 28, 15:09 UTC | Jun 28, 21:34 UTC | 6h 25m |
| 2026-06-28 | JBU1136 | - | Jun 28, 00:04 UTC | Jun 28, 00:30 UTC | 25m |
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 N760JB page for operator, model, and routing details .