sensors Mode-S transponder
AD2F71
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N949JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD2F71
- Octal
- 53227561
- Decimal
- 11,349,873
- Country
- US
- Tail
- N949JT
- Type
- A321
- Flights observed
- 257
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address AD2F71 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 |
|---|---|---|---|
| JBU397 | - | 6 | 2026-07-10 |
| JBU373 | - | 6 | 2026-07-08 |
| JBU1347 | - | 6 | 2026-07-03 |
| JBU709 | JetBlue Airways | 5 | 2026-06-14 |
| JBU904 | - | 4 | 2026-07-04 |
| JBU803 | - | 4 | 2026-06-24 |
| JBU70 | JetBlue Airways | 4 | 2026-04-24 |
| JBU574 | JetBlue Airways | 4 | 2026-05-18 |
| JBU303 | JetBlue Airways | 4 | 2026-06-01 |
| JBU2904 | - | 4 | 2026-06-25 |
| JBU268 | JetBlue Airways | 4 | 2026-06-28 |
| JBU2173 | JetBlue Airways | 4 | 2026-05-18 |
| JBU1922 | JetBlue Airways | 4 | 2026-04-19 |
| JBU1830 | - | 4 | 2026-06-14 |
| JBU165 | JetBlue Airways | 4 | 2026-05-20 |
| JBU1348 | - | 4 | 2026-07-03 |
| JBU69 | JetBlue Airways | 3 | 2026-04-24 |
| JBU58 | JetBlue Airways | 3 | 2026-06-20 |
| JBU521 | JetBlue Airways | 3 | 2026-04-18 |
| JBU504 | JetBlue Airways | 3 | 2026-06-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2023 | BOS → STI | Jul 13, 18:08 UTC | Jul 14, 02:15 UTC | 8h 8m |
| 2026-07-13 | JBU937 | JFK → STI | Jul 13, 01:30 UTC | Jul 13, 19:05 UTC | 17h 36m |
| 2026-07-12 | JBU1858 | AUA → JFK | Jul 12, 17:46 UTC | Jul 13, 16:05 UTC | 22h 20m |
| 2026-07-12 | JBU757 | JFK → AUA | Jul 12, 11:51 UTC | Jul 13, 02:15 UTC | 14h 25m |
| 2026-07-11 | JBU850 | STI → JFK | Jul 11, 21:46 UTC | Jul 12, 18:01 UTC | 20h 15m |
| 2026-07-11 | JBU1323 | BOS → STI | Jul 11, 02:31 UTC | Jul 12, 01:00 UTC | 22h 30m |
| 2026-07-11 | JBU1323 | - | Jul 11, 02:35 UTC | Jul 11, 03:35 UTC | 1h 0m |
| 2026-07-10 | JBU398 | SEA → BOS | Jul 10, 19:20 UTC | Jul 11, 00:10 UTC | 4h 50m |
| 2026-07-10 | JBU397 | BOS → SEA | Jul 10, 11:30 UTC | Jul 10, 17:00 UTC | 5h 30m |
| 2026-07-09 | JBU396 | PDX → BOS | Jul 9, 21:40 UTC | Jul 10, 02:25 UTC | 4h 45m |
| 2026-07-09 | JBU395 | BOS → PDX | Jul 9, 14:15 UTC | Jul 9, 19:45 UTC | 5h 30m |
| 2026-07-08 | JBU474 | AUA → BOS | Jul 8, 21:24 UTC | Jul 9, 19:45 UTC | 22h 22m |
| 2026-07-08 | JBU373 | - | Jul 8, 19:10 UTC | Jul 8, 19:30 UTC | 20m |
| 2026-07-08 | JBU373 | BOS → AUA | Jul 8, 14:55 UTC | Jul 9, 14:15 UTC | 23h 20m |
| 2026-07-08 | JBU373 | - | Jul 8, 14:55 UTC | Jul 8, 18:35 UTC | 3h 40m |
| 2026-07-07 | JBU1829 | BOS → SDQ | Jul 7, 18:08 UTC | Jul 8, 16:15 UTC | 22h 7m |
| 2026-07-07 | JBU2637 | JFK → STI | Jul 7, 01:02 UTC | Jul 7, 18:40 UTC | 17h 39m |
| 2026-07-07 | JBU2637 | - | Jul 7, 01:05 UTC | Jul 7, 03:55 UTC | 2h 50m |
| 2026-07-06 | JBU168 | JFK → JFK | Jul 6, 11:45 UTC | Jul 6, 20:40 UTC | 8h 55m |
| 2026-07-05 | JBU1759 | JFK → JFK | Jul 5, 23:30 UTC | Jul 6, 08:30 UTC | 9h 0m |
| 2026-07-05 | JBU1104 | SJU → JFK | Jul 5, 00:24 UTC | Jul 6, 00:15 UTC | 23h 52m |
| 2026-07-04 | JBU904 | - | Jul 4, 14:55 UTC | Jul 4, 17:05 UTC | 2h 10m |
| 2026-07-04 | JBU904 | - | Jul 4, 12:30 UTC | Jul 4, 12:40 UTC | 10m |
| 2026-07-04 | JBU904 | SJU → JFK | Jul 4, 12:26 UTC | Jul 5, 12:15 UTC | 23h 49m |
| 2026-07-03 | JBU1347 | - | Jul 3, 15:40 UTC | Jul 3, 16:05 UTC | 25m |
| 2026-07-03 | JBU1347 | DCA → SJU | Jul 3, 12:40 UTC | Jul 4, 02:05 UTC | 13h 25m |
| 2026-07-03 | JBU1347 | - | Jul 3, 12:45 UTC | Jul 3, 13:25 UTC | 40m |
| 2026-07-03 | JBU1348 | - | Jul 3, 00:15 UTC | Jul 3, 01:20 UTC | 1h 5m |
| 2026-07-02 | JBU1348 | - | Jul 2, 22:00 UTC | Jul 2, 22:10 UTC | 10m |
| 2026-07-02 | JBU1603 | - | Jul 2, 16:05 UTC | Jul 2, 16:25 UTC | 20m |
| 2026-07-02 | JBU1603 | - | Jul 2, 13:05 UTC | Jul 2, 13:45 UTC | 40m |
| 2026-07-01 | JBU279 | JFK → JFK | Jul 1, 14:00 UTC | Jul 1, 22:30 UTC | 8h 30m |
| 2026-07-01 | JBU162 | - | Jul 1, 06:35 UTC | Jul 1, 11:35 UTC | 5h 0m |
| 2026-06-30 | JBU161 | - | Jun 30, 23:00 UTC | Jul 1, 04:30 UTC | 5h 30m |
| 2026-06-30 | JBU1604 | - | Jun 30, 20:20 UTC | Jun 30, 20:55 UTC | 35m |
| 2026-06-30 | JBU1604 | - | Jun 30, 17:25 UTC | Jun 30, 17:40 UTC | 15m |
| 2026-06-30 | JBU1347 | - | Jun 30, 15:30 UTC | Jun 30, 15:40 UTC | 10m |
| 2026-06-30 | JBU1347 | - | Jun 30, 12:25 UTC | Jun 30, 13:05 UTC | 40m |
| 2026-06-29 | JBU1348 | - | Jun 29, 23:49 UTC | Jun 30, 01:40 UTC | 1h 51m |
| 2026-06-29 | JBU1348 | - | Jun 29, 22:05 UTC | Jun 29, 22:19 UTC | 15m |
| 2026-06-28 | JBU1759 | JFK → KIN | Jun 28, 22:44 UTC | Jun 29, 22:15 UTC | 23h 31m |
| 2026-06-28 | JBU268 | PUJ → JFK | Jun 28, 15:54 UTC | Jun 29, 08:29 UTC | 16h 36m |
| 2026-06-28 | JBU1104 | SJU → JFK | Jun 28, 01:26 UTC | Jun 29, 00:00 UTC | 22h 34m |
| 2026-06-28 | JBU1104 | SJU → JFK | Jun 28, 01:26 UTC | Jun 29, 00:00 UTC | 22h 34m |
| 2026-06-27 | JBU903 | JFK → SJU | Jun 27, 21:00 UTC | Jun 28, 19:25 UTC | 22h 25m |
| 2026-06-27 | JBU2137 | - | Jun 27, 09:24 UTC | Jun 27, 10:00 UTC | 35m |
| 2026-06-27 | JBU2137 | JFK → STI | Jun 27, 09:22 UTC | Jun 28, 04:59 UTC | 19h 38m |
| 2026-06-26 | JBU1533 | JFK → CTG | Jun 26, 13:55 UTC | Jun 27, 00:39 UTC | 10h 45m |
| 2026-06-25 | JBU1004 | - | Jun 25, 22:24 UTC | Jun 25, 22:59 UTC | 35m |
| 2026-06-25 | JBU1004 | - | Jun 25, 19:44 UTC | Jun 25, 19:54 UTC | 10m |
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 N949JT page for operator, model, and routing details .