sensors Mode-S transponder
AD935B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N974JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD935B
- Octal
- 53311533
- Decimal
- 11,375,451
- Country
- US
- Tail
- N974JT
- Type
- A321
- Flights observed
- 254
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address AD935B 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 |
|---|---|---|---|
| JBU1347 | - | 7 | 2026-07-02 |
| JBU904 | - | 6 | 2026-07-08 |
| JBU322 | JetBlue Airways | 6 | 2026-05-20 |
| JBU474 | JetBlue Airways | 5 | 2026-05-14 |
| JBU373 | JetBlue Airways | 5 | 2026-05-14 |
| JBU255 | - | 5 | 2026-07-07 |
| JBU2173 | - | 5 | 2026-07-11 |
| JBU574 | - | 4 | 2026-07-11 |
| JBU361 | - | 4 | 2026-06-30 |
| JBU168 | - | 4 | 2026-06-22 |
| JBU1348 | JetBlue Airways | 4 | 2026-05-24 |
| JBU970 | JetBlue Airways | 3 | 2026-05-17 |
| JBU937 | JetBlue Airways | 3 | 2026-06-06 |
| JBU909 | JetBlue Airways | 3 | 2026-04-28 |
| JBU803 | - | 3 | 2026-06-29 |
| JBU662 | - | 3 | 2026-06-30 |
| JBU651 | JetBlue Airways | 3 | 2026-05-20 |
| JBU58 | JetBlue Airways | 3 | 2026-06-22 |
| JBU561 | JetBlue Airways | 3 | 2026-05-11 |
| JBU521 | JetBlue Airways | 3 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1829 | - | Jul 14, 17:30 UTC | Jul 14, 18:20 UTC | 50m |
| 2026-07-13 | JBU9 | JFK → SDQ | Jul 13, 21:12 UTC | Jul 14, 18:20 UTC | 21h 9m |
| 2026-07-13 | JBU9 | - | Jul 13, 21:15 UTC | Jul 13, 21:55 UTC | 40m |
| 2026-07-13 | JBU602 | FLL → JFK | Jul 13, 16:10 UTC | Jul 13, 18:25 UTC | 2h 15m |
| 2026-07-13 | JBU1601 | JFK → FLL | Jul 13, 11:20 UTC | Jul 13, 13:40 UTC | 2h 20m |
| 2026-07-12 | JBU2110 | - | Jul 12, 14:05 UTC | Jul 12, 15:01 UTC | 55m |
| 2026-07-12 | JBU2110 | SDQ → JFK | Jul 12, 11:45 UTC | Jul 13, 00:55 UTC | 13h 11m |
| 2026-07-12 | JBU2829 | - | Jul 12, 03:10 UTC | Jul 12, 04:05 UTC | 55m |
| 2026-07-11 | JBU574 | - | Jul 11, 23:15 UTC | Jul 11, 23:55 UTC | 40m |
| 2026-07-11 | JBU574 | - | Jul 11, 19:45 UTC | Jul 11, 19:55 UTC | 10m |
| 2026-07-11 | JBU2173 | BOS → AUA | Jul 11, 14:10 UTC | Jul 11, 18:20 UTC | 4h 10m |
| 2026-07-10 | JBU1830 | SDQ → BOS | Jul 10, 09:19 UTC | Jul 11, 07:40 UTC | 22h 22m |
| 2026-07-10 | JBU2829 | BOS → SDQ | Jul 10, 00:33 UTC | Jul 10, 21:00 UTC | 20h 28m |
| 2026-07-09 | JBU2173 | BOS → AUA | Jul 9, 12:11 UTC | Jul 10, 03:40 UTC | 15h 29m |
| 2026-07-09 | JBU2173 | BOS → AUA | Jul 9, 12:11 UTC | Jul 10, 03:40 UTC | 15h 29m |
| 2026-07-08 | JBU337 | JFK → STI | Jul 8, 18:05 UTC | Jul 9, 16:30 UTC | 22h 26m |
| 2026-07-08 | JBU904 | - | Jul 8, 14:05 UTC | Jul 8, 15:25 UTC | 1h 20m |
| 2026-07-08 | JBU904 | - | Jul 8, 11:40 UTC | Jul 8, 11:55 UTC | 15m |
| 2026-07-08 | JBU904 | SJU → JFK | Jul 8, 11:38 UTC | Jul 9, 10:45 UTC | 23h 7m |
| 2026-07-07 | JBU255 | - | Jul 7, 14:40 UTC | Jul 7, 15:55 UTC | 1h 15m |
| 2026-07-07 | JBU255 | JFK → PLS | Jul 7, 14:38 UTC | Jul 8, 11:55 UTC | 21h 18m |
| 2026-07-07 | JBU816 | - | Jul 7, 07:50 UTC | Jul 7, 12:50 UTC | 5h 0m |
| 2026-07-07 | JBU615 | JFK → SFO | Jul 7, 00:50 UTC | Jul 7, 06:20 UTC | 5h 30m |
| 2026-07-06 | JBU1858 | - | Jul 6, 20:35 UTC | Jul 6, 22:05 UTC | 1h 30m |
| 2026-07-06 | JBU1858 | - | Jul 6, 17:35 UTC | Jul 6, 17:50 UTC | 15m |
| 2026-07-06 | JBU757 | JFK → AUA | Jul 6, 12:05 UTC | Jul 6, 16:05 UTC | 4h 0m |
| 2026-07-05 | JBU1601 | JFK → FLL | Jul 5, 16:25 UTC | Jul 5, 18:50 UTC | 2h 25m |
| 2026-07-05 | JBU1601 | JFK → FLL | Jul 5, 16:21 UTC | Jul 6, 12:50 UTC | 20h 30m |
| 2026-07-05 | JBU454 | - | Jul 5, 04:55 UTC | Jul 5, 06:15 UTC | 1h 20m |
| 2026-07-05 | JBU454 | - | Jul 5, 00:15 UTC | Jul 5, 04:50 UTC | 4h 35m |
| 2026-07-04 | JBU355 | JFK → ONT | Jul 4, 03:05 UTC | Jul 4, 09:00 UTC | 5h 55m |
| 2026-07-03 | JBU255 | JFK → PLS | Jul 3, 13:20 UTC | Jul 4, 09:00 UTC | 19h 41m |
| 2026-07-03 | JBU162 | SMF → JFK | Jul 3, 06:25 UTC | Jul 3, 11:20 UTC | 4h 55m |
| 2026-07-03 | JBU162 | SMF → JFK | Jul 3, 06:25 UTC | Jul 4, 04:45 UTC | 22h 20m |
| 2026-07-02 | JBU161 | JFK → SMF | Jul 2, 22:45 UTC | Jul 3, 04:10 UTC | 5h 25m |
| 2026-07-02 | JBU1604 | - | Jul 2, 19:50 UTC | Jul 2, 20:50 UTC | 1h 0m |
| 2026-07-02 | JBU1604 | - | Jul 2, 17:20 UTC | Jul 2, 17:40 UTC | 20m |
| 2026-07-02 | JBU1347 | - | Jul 2, 15:10 UTC | Jul 2, 15:30 UTC | 20m |
| 2026-07-02 | JBU1347 | - | Jul 2, 12:20 UTC | Jul 2, 13:00 UTC | 40m |
| 2026-07-01 | JBU1603 | JFK → SJU | Jul 1, 13:10 UTC | Jul 2, 12:45 UTC | 23h 35m |
| 2026-06-30 | JBU662 | BGI → JFK | Jun 30, 18:18 UTC | Jul 1, 16:20 UTC | 22h 2m |
| 2026-06-30 | JBU361 | JFK → JFK | Jun 30, 12:15 UTC | Jun 30, 22:45 UTC | 10h 30m |
| 2026-06-30 | JBU704 | - | Jun 30, 01:14 UTC | Jun 30, 04:40 UTC | 3h 26m |
| 2026-06-29 | JBU803 | - | Jun 29, 20:49 UTC | Jun 29, 23:54 UTC | 3h 5m |
| 2026-06-29 | JBU2137 | - | Jun 29, 09:25 UTC | Jun 29, 17:59 UTC | 8h 35m |
| 2026-06-28 | JBU1532 | CTG → JFK | Jun 28, 19:53 UTC | Jun 29, 17:59 UTC | 22h 7m |
| 2026-06-28 | JBU1533 | JFK → CTG | Jun 28, 13:40 UTC | Jun 29, 00:10 UTC | 10h 30m |
| 2026-06-28 | JBU1117 | - | Jun 28, 02:05 UTC | Jun 28, 02:49 UTC | 45m |
| 2026-06-27 | JBU774 | - | Jun 27, 19:59 UTC | Jun 27, 20:55 UTC | 55m |
| 2026-06-27 | JBU774 | - | Jun 27, 16:35 UTC | Jun 27, 16:44 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 N974JT page for operator, model, and routing details .