sensors Mode-S transponder
ACF54F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N934JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- ACF54F
- Octal
- 53172517
- Decimal
- 11,334,991
- Country
- US
- Tail
- N934JB
- Type
- A321
- Flights observed
- 275
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- Jul 26, 21:45 UTC
Current position
Country allocation
The ICAO 24-bit address ACF54F 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 |
|---|---|---|---|
| JBU287 | - | 10 | 2026-07-17 |
| JBU424 | - | 9 | 2026-07-22 |
| JBU1700 | JetBlue Airways | 8 | 2026-06-14 |
| JBU423 | JetBlue Airways | 7 | 2026-07-24 |
| JBU1708 | JetBlue Airways | 6 | 2026-06-06 |
| JBU2501 | JetBlue Airways | 5 | 2026-06-07 |
| JBU219 | - | 5 | 2026-06-24 |
| JBU1833 | - | 5 | 2026-07-14 |
| JBU1401 | - | 5 | 2026-07-21 |
| JBU116 | - | 5 | 2026-07-11 |
| JBU278 | JetBlue Airways | 4 | 2026-07-26 |
| JBU277 | - | 4 | 2026-07-11 |
| JBU2010 | JetBlue Airways | 4 | 2026-04-25 |
| JBU2009 | JetBlue Airways | 4 | 2026-04-25 |
| JBU1400 | - | 4 | 2026-07-10 |
| JBU1223 | - | 4 | 2026-07-18 |
| JBU1190 | - | 4 | 2026-07-12 |
| JBU1071 | JetBlue Airways | 4 | 2026-04-14 |
| JBU934 | - | 3 | 2026-04-13 |
| JBU933 | - | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | JBU1200 | LAX → FLL | Jul 26, 21:00 UTC | Jul 26, 21:45 UTC | 45m |
| 2026-07-26 | JBU2801 | LAX → FLL | Jul 26, 13:30 UTC | Jul 26, 18:10 UTC | 4h 40m |
| 2026-07-26 | JBU278 | SFO → FLL | Jul 26, 05:55 UTC | Jul 26, 11:10 UTC | 5h 16m |
| 2026-07-25 | JBU233 | BTV → JFK | Jul 25, 20:05 UTC | Jul 26, 01:50 UTC | 5h 45m |
| 2026-07-25 | JBU888 | LAX → BOS | Jul 25, 13:15 UTC | Jul 25, 18:20 UTC | 5h 5m |
| 2026-07-24 | JBU423 | BOS → STI | Jul 24, 17:20 UTC | Jul 24, 22:35 UTC | 5h 15m |
| 2026-07-23 | JBU924 | STI → BOS | Jul 23, 22:35 UTC | Jul 24, 03:25 UTC | 4h 50m |
| 2026-07-23 | JBU1123 | JFK → LAX | Jul 23, 15:45 UTC | Jul 23, 20:50 UTC | 5h 5m |
| 2026-07-23 | JBU1224 | LAX → JFK | Jul 23, 07:25 UTC | Jul 23, 12:25 UTC | 5h 0m |
| 2026-07-22 | JBU424 | - | Jul 22, 17:15 UTC | Jul 22, 21:45 UTC | 4h 30m |
| 2026-07-22 | JBU424 | LAX → JFK | Jul 22, 17:10 UTC | Jul 23, 15:45 UTC | 22h 35m |
| 2026-07-22 | JBU1201 | - | Jul 22, 04:10 UTC | Jul 22, 15:20 UTC | 11h 10m |
| 2026-07-21 | JBU1401 | - | Jul 21, 15:15 UTC | Jul 21, 20:00 UTC | 4h 45m |
| 2026-07-21 | JBU700 | LAX → FLL | Jul 21, 07:25 UTC | Jul 21, 12:10 UTC | 4h 45m |
| 2026-07-18 | JBU1223 | JFK → LAX | Jul 18, 00:28 UTC | Jul 18, 10:05 UTC | 9h 38m |
| 2026-07-18 | JBU1223 | - | Jul 18, 00:29 UTC | Jul 18, 05:40 UTC | 5h 11m |
| 2026-07-17 | JBU424 | - | Jul 17, 17:05 UTC | Jul 17, 22:10 UTC | 5h 5m |
| 2026-07-17 | JBU287 | - | Jul 17, 10:10 UTC | Jul 17, 15:25 UTC | 5h 15m |
| 2026-07-16 | JBU215 | JFK → SFO | Jul 16, 15:51 UTC | Jul 17, 15:25 UTC | 23h 34m |
| 2026-07-16 | JBU215 | JFK → SFO | Jul 16, 15:55 UTC | Jul 16, 21:25 UTC | 5h 30m |
| 2026-07-14 | JBU416 | - | Jul 14, 22:40 UTC | Jul 15, 03:55 UTC | 5h 14m |
| 2026-07-14 | JBU1833 | BOS → SFO | Jul 14, 14:40 UTC | Jul 14, 20:05 UTC | 5h 25m |
| 2026-07-14 | JBU1034 | SFO → BOS | Jul 14, 07:50 UTC | Jul 14, 13:10 UTC | 5h 20m |
| 2026-07-13 | JBU733 | BOS → SFO | Jul 13, 22:05 UTC | Jul 14, 03:35 UTC | 5h 30m |
| 2026-07-12 | JBU1634 | - | Jul 12, 19:50 UTC | Jul 13, 01:10 UTC | 5h 20m |
| 2026-07-12 | JBU15 | JFK → SFO | Jul 12, 12:20 UTC | Jul 12, 17:40 UTC | 5h 20m |
| 2026-07-12 | JBU1190 | - | Jul 12, 04:20 UTC | Jul 12, 09:20 UTC | 5h 0m |
| 2026-07-11 | JBU116 | SFO → JFK | Jul 11, 13:30 UTC | Jul 11, 18:35 UTC | 5h 5m |
| 2026-07-11 | JBU116 | SFO → JFK | Jul 11, 13:26 UTC | Jul 12, 09:20 UTC | 19h 55m |
| 2026-07-11 | JBU277 | - | Jul 11, 01:25 UTC | Jul 11, 06:45 UTC | 5h 20m |
| 2026-07-10 | JBU378 | - | Jul 10, 18:20 UTC | Jul 10, 23:35 UTC | 5h 16m |
| 2026-07-10 | JBU377 | - | Jul 10, 11:05 UTC | Jul 10, 16:30 UTC | 5h 25m |
| 2026-07-10 | JBU1400 | - | Jul 10, 04:00 UTC | Jul 10, 08:35 UTC | 4h 35m |
| 2026-07-09 | JBU423 | - | Jul 9, 18:50 UTC | Jul 10, 00:20 UTC | 5h 30m |
| 2026-07-08 | JBU1548 | LAS → JFK | Jul 8, 17:40 UTC | Jul 8, 22:10 UTC | 4h 30m |
| 2026-07-07 | JBU624 | LAX → JFK | Jul 7, 21:38 UTC | Jul 8, 19:45 UTC | 22h 8m |
| 2026-07-07 | JBU604 | YVR → JFK | Jul 7, 06:44 UTC | Jul 8, 02:50 UTC | 20h 6m |
| 2026-07-07 | JBU604 | YVR → JFK | Jul 7, 06:45 UTC | Jul 7, 11:30 UTC | 4h 45m |
| 2026-07-06 | JBU603 | - | Jul 6, 23:55 UTC | Jul 7, 04:45 UTC | 4h 50m |
| 2026-07-06 | JBU603 | - | Jul 6, 23:30 UTC | Jul 6, 23:50 UTC | 20m |
| 2026-07-06 | JBU524 | - | Jul 6, 14:40 UTC | Jul 6, 19:50 UTC | 5h 10m |
| 2026-07-05 | JBU1873 | - | Jul 5, 20:35 UTC | Jul 6, 01:45 UTC | 5h 10m |
| 2026-07-04 | JBU2074 | - | Jul 4, 13:10 UTC | Jul 4, 18:10 UTC | 5h 0m |
| 2026-07-04 | JBU2074 | LAX → EWR | Jul 4, 13:09 UTC | Jul 5, 01:15 UTC | 12h 6m |
| 2026-07-03 | JBU424 | LAX → JFK | Jul 3, 16:55 UTC | Jul 4, 15:45 UTC | 22h 50m |
| 2026-07-03 | JBU1400 | - | Jul 3, 03:50 UTC | Jul 3, 07:45 UTC | 3h 55m |
| 2026-07-03 | JBU1400 | LAX → FLL | Jul 3, 03:45 UTC | Jul 4, 00:30 UTC | 20h 46m |
| 2026-07-02 | JBU487 | - | Jul 2, 20:05 UTC | Jul 3, 01:35 UTC | 5h 30m |
| 2026-07-02 | JBU888 | - | Jul 2, 13:15 UTC | Jul 2, 18:05 UTC | 4h 50m |
| 2026-07-01 | JBU324 | - | Jul 1, 18:45 UTC | Jul 1, 19:45 UTC | 1h 0m |
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 N934JB page for operator, model, and routing details .