sensors Mode-S transponder
AC7B1B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N903JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AC7B1B
- Octal
- 53075433
- Decimal
- 11,303,707
- Country
- US
- Tail
- N903JB
- Type
- A321
- Flights observed
- 247
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address AC7B1B 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 |
|---|---|---|---|
| JBU1348 | - | 7 | 2026-07-05 |
| JBU2924 | - | 6 | 2026-07-12 |
| JBU2903 | - | 6 | 2026-07-12 |
| JBU762 | JetBlue Airways | 5 | 2026-06-02 |
| JBU2269 | JetBlue Airways | 5 | 2026-05-20 |
| JBU2173 | - | 5 | 2026-07-13 |
| JBU1347 | - | 5 | 2026-07-06 |
| JBU862 | JetBlue Airways | 4 | 2026-04-30 |
| JBU761 | JetBlue Airways | 4 | 2026-06-06 |
| JBU602 | - | 4 | 2026-06-25 |
| JBU466 | JetBlue Airways | 4 | 2026-05-20 |
| JBU398 | - | 4 | 2026-07-03 |
| JBU2904 | - | 4 | 2026-07-05 |
| JBU1 | JetBlue Airways | 4 | 2026-05-16 |
| JBU9999 | - | 3 | 2026-07-13 |
| JBU904 | - | 3 | 2026-07-12 |
| JBU898 | JetBlue Airways | 3 | 2026-04-18 |
| JBU771 | JetBlue Airways | 3 | 2026-05-27 |
| JBU765 | - | 3 | 2026-04-13 |
| JBU651 | JetBlue Airways | 3 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2110 | SDQ → JFK | Jul 14, 11:42 UTC | Jul 15, 00:15 UTC | 12h 33m |
| 2026-07-14 | JBU2829 | BOS → SDQ | Jul 14, 00:36 UTC | Jul 14, 22:45 UTC | 22h 9m |
| 2026-07-14 | JBU2829 | - | Jul 14, 00:35 UTC | Jul 14, 01:10 UTC | 35m |
| 2026-07-13 | JBU574 | - | Jul 13, 20:25 UTC | Jul 13, 21:30 UTC | 1h 5m |
| 2026-07-13 | JBU574 | - | Jul 13, 17:15 UTC | Jul 13, 17:30 UTC | 15m |
| 2026-07-13 | JBU2173 | - | Jul 13, 15:15 UTC | Jul 13, 15:35 UTC | 20m |
| 2026-07-13 | JBU2173 | - | Jul 13, 12:10 UTC | Jul 13, 14:40 UTC | 2h 30m |
| 2026-07-13 | JBU2173 | - | Jul 13, 11:20 UTC | Jul 13, 12:05 UTC | 45m |
| 2026-07-13 | JBU9999 | BOS → BOS | Jul 13, 07:10 UTC | Jul 13, 07:25 UTC | 15m |
| 2026-07-13 | JBU9999 | BOS → BOS | Jul 13, 06:05 UTC | Jul 13, 06:10 UTC | 5m |
| 2026-07-13 | JBU9999 | BOS → BOS | Jul 13, 05:40 UTC | Jul 13, 05:45 UTC | 5m |
| 2026-07-12 | JBU2924 | - | Jul 12, 18:10 UTC | Jul 13, 02:15 UTC | 8h 5m |
| 2026-07-12 | JBU904 | - | Jul 12, 14:50 UTC | Jul 12, 15:50 UTC | 1h 0m |
| 2026-07-12 | JBU904 | - | Jul 12, 12:30 UTC | Jul 12, 12:40 UTC | 10m |
| 2026-07-12 | JBU2903 | JFK → SJU | Jul 12, 00:40 UTC | Jul 12, 03:55 UTC | 3h 15m |
| 2026-07-11 | JBU779 | JFK → JFK | Jul 11, 12:15 UTC | Jul 11, 20:35 UTC | 8h 20m |
| 2026-07-10 | JBU627 | JFK → JFK | Jul 10, 16:25 UTC | Jul 11, 00:20 UTC | 7h 56m |
| 2026-07-10 | JBU454 | - | Jul 10, 07:25 UTC | Jul 10, 12:10 UTC | 4h 45m |
| 2026-07-09 | JBU355 | JFK → ONT | Jul 9, 23:55 UTC | Jul 10, 05:40 UTC | 5h 45m |
| 2026-07-09 | JBU1858 | - | Jul 9, 18:30 UTC | Jul 9, 21:50 UTC | 3h 20m |
| 2026-07-09 | JBU1858 | - | Jul 9, 17:40 UTC | Jul 9, 17:55 UTC | 15m |
| 2026-07-09 | JBU757 | - | Jul 9, 15:25 UTC | Jul 9, 15:45 UTC | 20m |
| 2026-07-08 | JBU859 | JFK → KIN | Jul 8, 20:36 UTC | Jul 9, 18:30 UTC | 21h 54m |
| 2026-07-08 | JBU859 | - | Jul 8, 20:40 UTC | Jul 8, 23:00 UTC | 2h 20m |
| 2026-07-08 | JBU1436 | JFK → JFK | Jul 8, 09:25 UTC | Jul 8, 17:55 UTC | 8h 30m |
| 2026-07-07 | JBU1692 | LIR → JFK | Jul 7, 20:36 UTC | Jul 8, 18:00 UTC | 21h 25m |
| 2026-07-07 | JBU1691 | JFK → LIR | Jul 7, 14:40 UTC | Jul 7, 18:45 UTC | 4h 5m |
| 2026-07-07 | JBU1691 | JFK → LIR | Jul 7, 14:40 UTC | Jul 8, 10:20 UTC | 19h 41m |
| 2026-07-06 | JBU1604 | SJU → JFK | Jul 6, 17:36 UTC | Jul 7, 14:45 UTC | 21h 9m |
| 2026-07-06 | JBU1347 | DCA → SJU | Jul 6, 12:41 UTC | Jul 7, 09:30 UTC | 20h 50m |
| 2026-07-05 | JBU1348 | SJU → DCA | Jul 5, 22:40 UTC | Jul 6, 20:45 UTC | 22h 5m |
| 2026-07-05 | JBU2904 | - | Jul 5, 11:40 UTC | Jul 5, 12:45 UTC | 1h 5m |
| 2026-07-05 | JBU2904 | - | Jul 5, 09:10 UTC | Jul 5, 09:25 UTC | 15m |
| 2026-07-05 | JBU2904 | SJU → JFK | Jul 5, 09:08 UTC | Jul 6, 02:25 UTC | 17h 17m |
| 2026-07-05 | JBU2903 | - | Jul 5, 02:50 UTC | Jul 5, 03:15 UTC | 25m |
| 2026-07-04 | JBU2903 | - | Jul 4, 23:55 UTC | Jul 5, 00:40 UTC | 45m |
| 2026-07-04 | JBU2110 | - | Jul 4, 03:40 UTC | Jul 4, 15:35 UTC | 11h 55m |
| 2026-07-03 | JBU398 | SEA → BOS | Jul 3, 19:30 UTC | Jul 4, 01:10 UTC | 5h 40m |
| 2026-07-03 | JBU2924 | STI → BOS | Jul 3, 00:56 UTC | Jul 4, 00:45 UTC | 23h 49m |
| 2026-07-02 | JBU337 | JFK → STI | Jul 2, 20:05 UTC | Jul 3, 17:50 UTC | 21h 45m |
| 2026-07-02 | JBU1436 | STI → JFK | Jul 2, 14:10 UTC | Jul 3, 12:45 UTC | 22h 35m |
| 2026-07-02 | JBU2137 | JFK → STI | Jul 2, 09:17 UTC | Jul 3, 04:50 UTC | 19h 33m |
| 2026-07-01 | JBU1668 | PUJ → JFK | Jul 1, 21:06 UTC | Jul 2, 20:45 UTC | 23h 39m |
| 2026-07-01 | JBU1669 | JFK → PUJ | Jul 1, 16:07 UTC | Jul 2, 14:30 UTC | 22h 23m |
| 2026-07-01 | JBU1017 | BOS → JFK | Jul 1, 12:50 UTC | Jul 2, 10:00 UTC | 21h 10m |
| 2026-06-30 | JBU373 | BOS → AUA | Jun 30, 19:15 UTC | Jun 30, 19:40 UTC | 25m |
| 2026-06-30 | JBU373 | BOS → AUA | Jun 30, 15:15 UTC | Jul 1, 13:40 UTC | 22h 25m |
| 2026-06-30 | JBU373 | BOS → AUA | Jun 30, 15:20 UTC | Jun 30, 18:35 UTC | 3h 15m |
| 2026-06-29 | JBU2924 | - | Jun 29, 18:19 UTC | Jun 30, 02:30 UTC | 8h 11m |
| 2026-06-29 | JBU904 | SJU → JFK | Jun 29, 12:05 UTC | Jun 29, 15:34 UTC | 3h 30m |
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 N903JB page for operator, model, and routing details .