sensors Mode-S transponder
AD0074
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N937JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD0074
- Octal
- 53200164
- Decimal
- 11,337,844
- Country
- US
- Tail
- N937JB
- Type
- A321
- Flights observed
- 257
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address AD0074 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 |
|---|---|---|---|
| JBU2501 | - | 8 | 2026-06-21 |
| JBU1833 | - | 8 | 2026-07-09 |
| JBU723 | JetBlue Airways | 6 | 2026-05-05 |
| JBU615 | - | 6 | 2026-07-10 |
| JBU2801 | - | 6 | 2026-06-25 |
| JBU816 | - | 5 | 2026-06-30 |
| JBU515 | - | 5 | 2026-07-02 |
| JBU287 | JetBlue Airways | 5 | 2026-05-27 |
| JBU2832 | - | 5 | 2026-06-30 |
| JBU1200 | JetBlue Airways | 5 | 2026-06-25 |
| JBU734 | - | 4 | 2026-06-14 |
| JBU711 | JetBlue Airways | 4 | 2026-06-08 |
| JBU624 | - | 4 | 2026-07-11 |
| JBU608 | - | 4 | 2026-06-25 |
| JBU2577 | JetBlue Airways | 4 | 2026-04-15 |
| JBU233 | JetBlue Airways | 4 | 2026-06-08 |
| JBU19 | JetBlue Airways | 4 | 2026-04-15 |
| JBU1700 | - | 4 | 2026-06-19 |
| JBU15 | JetBlue Airways | 4 | 2026-07-08 |
| JBU988 | - | 3 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1388 | - | Jul 14, 18:05 UTC | Jul 14, 19:00 UTC | 55m |
| 2026-07-14 | JBU1573 | - | Jul 14, 11:20 UTC | Jul 14, 16:05 UTC | 4h 45m |
| 2026-07-14 | JBU1574 | - | Jul 14, 03:55 UTC | Jul 14, 08:50 UTC | 4h 55m |
| 2026-07-13 | JBU1523 | - | Jul 13, 20:35 UTC | Jul 14, 01:20 UTC | 4h 45m |
| 2026-07-13 | JBU1223 | JFK → LAX | Jul 13, 02:24 UTC | Jul 14, 01:00 UTC | 22h 37m |
| 2026-07-12 | JBU190 | SAN → JFK | Jul 12, 19:09 UTC | Jul 13, 17:00 UTC | 21h 52m |
| 2026-07-11 | JBU624 | - | Jul 11, 21:50 UTC | Jul 12, 02:55 UTC | 5h 5m |
| 2026-07-11 | JBU624 | LAX → JFK | Jul 11, 21:47 UTC | Jul 12, 18:15 UTC | 20h 29m |
| 2026-07-11 | JBU523 | - | Jul 11, 14:45 UTC | Jul 11, 20:05 UTC | 5h 20m |
| 2026-07-10 | JBU615 | - | Jul 10, 23:55 UTC | Jul 11, 05:55 UTC | 6h 0m |
| 2026-07-10 | JBU615 | JFK → SFO | Jul 10, 23:54 UTC | Jul 11, 23:00 UTC | 23h 7m |
| 2026-07-09 | JBU416 | OAK → JFK | Jul 9, 23:55 UTC | Jul 10, 05:00 UTC | 5h 5m |
| 2026-07-09 | JBU1833 | - | Jul 9, 15:15 UTC | Jul 9, 21:20 UTC | 6h 5m |
| 2026-07-09 | JBU1833 | BOS → BOS | Jul 9, 14:25 UTC | Jul 9, 14:30 UTC | 5m |
| 2026-07-08 | JBU1634 | SFO → BOS | Jul 8, 20:15 UTC | Jul 9, 01:25 UTC | 5h 10m |
| 2026-07-08 | JBU15 | JFK → SFO | Jul 8, 13:15 UTC | Jul 8, 18:40 UTC | 5h 25m |
| 2026-07-07 | JBU2922 | NAS → JFK | Jul 7, 18:28 UTC | Jul 8, 17:00 UTC | 22h 33m |
| 2026-07-07 | JBU121 | - | Jul 7, 14:35 UTC | Jul 7, 20:40 UTC | 6h 5m |
| 2026-07-06 | JBU1833 | - | Jul 6, 15:50 UTC | Jul 6, 21:00 UTC | 5h 10m |
| 2026-07-06 | JBU1833 | BOS → SFO | Jul 6, 15:50 UTC | Jul 7, 15:00 UTC | 23h 11m |
| 2026-07-06 | JBU1034 | - | Jul 6, 08:05 UTC | Jul 6, 13:15 UTC | 5h 10m |
| 2026-07-06 | JBU1633 | - | Jul 6, 00:35 UTC | Jul 6, 06:40 UTC | 6h 5m |
| 2026-07-05 | JBU413 | BOS → SFO | Jul 5, 01:31 UTC | Jul 6, 01:00 UTC | 23h 30m |
| 2026-07-05 | JBU413 | - | Jul 5, 01:35 UTC | Jul 5, 07:20 UTC | 5h 45m |
| 2026-07-04 | JBU1878 | - | Jul 4, 17:30 UTC | Jul 4, 20:55 UTC | 3h 25m |
| 2026-07-04 | JBU1877 | BOS → SXM | Jul 4, 11:40 UTC | Jul 4, 15:15 UTC | 3h 36m |
| 2026-07-04 | JBU1877 | BOS → SXM | Jul 4, 11:45 UTC | Jul 4, 15:15 UTC | 3h 30m |
| 2026-07-03 | JBU15 | JFK → SFO | Jul 3, 12:30 UTC | Jul 3, 18:05 UTC | 5h 35m |
| 2026-07-03 | JBU15 | JFK → SFO | Jul 3, 12:30 UTC | Jul 4, 01:10 UTC | 12h 40m |
| 2026-07-02 | JBU1487 | BOS → LAX | Jul 2, 15:43 UTC | Jul 3, 15:00 UTC | 23h 17m |
| 2026-07-02 | JBU1034 | - | Jul 2, 08:50 UTC | Jul 2, 09:00 UTC | 10m |
| 2026-07-02 | JBU515 | - | Jul 2, 01:40 UTC | Jul 2, 07:10 UTC | 5h 30m |
| 2026-07-02 | JBU515 | JFK → SFO | Jul 2, 01:35 UTC | Jul 3, 01:00 UTC | 23h 25m |
| 2026-07-01 | JBU348 | LAS → JFK | Jul 1, 18:30 UTC | Jul 1, 23:05 UTC | 4h 35m |
| 2026-07-01 | JBU2821 | - | Jul 1, 12:25 UTC | Jul 1, 16:45 UTC | 4h 20m |
| 2026-06-30 | JBU2832 | - | Jun 30, 23:05 UTC | Jul 1, 03:15 UTC | 4h 10m |
| 2026-06-30 | JBU511 | - | Jun 30, 15:25 UTC | Jun 30, 20:10 UTC | 4h 45m |
| 2026-06-30 | JBU816 | - | Jun 30, 08:10 UTC | Jun 30, 13:15 UTC | 5h 5m |
| 2026-06-30 | JBU615 | JFK → SFO | Jun 30, 01:09 UTC | Jun 30, 06:45 UTC | 5h 36m |
| 2026-06-29 | JBU316 | - | Jun 29, 15:09 UTC | Jun 29, 20:04 UTC | 4h 55m |
| 2026-06-29 | JBU277 | FXE → SFO | Jun 29, 01:20 UTC | Jun 29, 06:44 UTC | 5h 25m |
| 2026-06-28 | JBU377 | - | Jun 28, 11:04 UTC | Jun 28, 16:35 UTC | 5h 30m |
| 2026-06-28 | JBU377 | FLL → SFO | Jun 28, 11:02 UTC | Jun 29, 06:59 UTC | 19h 58m |
| 2026-06-28 | JBU1400 | - | Jun 28, 04:05 UTC | Jun 28, 08:44 UTC | 4h 40m |
| 2026-06-27 | JBU1873 | - | Jun 27, 19:49 UTC | Jun 28, 01:10 UTC | 5h 20m |
| 2026-06-27 | JBU2074 | - | Jun 27, 13:35 UTC | Jun 27, 18:15 UTC | 4h 40m |
| 2026-06-26 | JBU424 | - | Jun 26, 17:00 UTC | Jun 26, 21:39 UTC | 4h 40m |
| 2026-06-26 | JBU424 | LAX → JFK | Jun 26, 16:57 UTC | Jun 27, 15:00 UTC | 22h 3m |
| 2026-06-26 | JBU1201 | - | Jun 26, 10:30 UTC | Jun 26, 15:25 UTC | 4h 55m |
| 2026-06-25 | JBU1200 | LAX → FLL | Jun 25, 21:25 UTC | Jun 26, 02:00 UTC | 4h 35m |
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 N937JB page for operator, model, and routing details .