sensors Mode-S transponder
A6C013
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N534JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A6C013
- Octal
- 51540023
- Decimal
- 10,928,147
- Country
- US
- Tail
- N534JB
- Type
- A320
- Flights observed
- 296
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A6C013 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 |
|---|---|---|---|
| JBU928 | JetBlue Airways | 6 | 2026-05-22 |
| JBU753 | - | 5 | 2026-06-22 |
| JBU276 | JetBlue Airways | 5 | 2026-06-18 |
| JBU959 | - | 4 | 2026-07-05 |
| JBU1229 | JetBlue Airways | 4 | 2026-04-13 |
| JBU85 | JetBlue Airways | 3 | 2026-05-26 |
| JBU491 | - | 3 | 2026-07-01 |
| JBU433 | JetBlue Airways | 3 | 2026-05-01 |
| JBU251 | - | 3 | 2026-06-16 |
| JBU197 | - | 3 | 2026-07-03 |
| JBU1797 | JetBlue Airways | 3 | 2026-06-07 |
| JBU1754 | JetBlue Airways | 3 | 2026-05-29 |
| JBU1751 | JetBlue Airways | 3 | 2026-05-18 |
| JBU1529 | JetBlue Airways | 3 | 2026-06-04 |
| JBU1321 | JetBlue Airways | 3 | 2026-05-11 |
| JBU1168 | JetBlue Airways | 3 | 2026-05-21 |
| JBU113 | JetBlue Airways | 3 | 2026-05-31 |
| JBU1112 | - | 3 | 2026-06-27 |
| JBU1033 | JetBlue Airways | 3 | 2026-05-04 |
| JBU953 | JetBlue Airways | 2 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU947 | - | Jul 14, 11:40 UTC | Jul 14, 18:45 UTC | 7h 5m |
| 2026-07-14 | JBU504 | - | Jul 14, 01:25 UTC | Jul 14, 04:50 UTC | 3h 25m |
| 2026-07-13 | JBU375 | PHL → FLL | Jul 13, 10:02 UTC | Jul 14, 04:55 UTC | 18h 54m |
| 2026-07-12 | JBU313 | ISP → FLL | Jul 12, 21:05 UTC | Jul 13, 20:30 UTC | 23h 26m |
| 2026-07-12 | JBU2433 | - | Jul 12, 13:55 UTC | Jul 13, 10:45 UTC | 20h 51m |
| 2026-07-12 | JBU1480 | FLL → DCA | Jul 12, 10:39 UTC | Jul 13, 03:55 UTC | 17h 17m |
| 2026-07-11 | JBU472 | FLL → LGA | Jul 11, 21:35 UTC | Jul 12, 18:45 UTC | 21h 11m |
| 2026-07-11 | JBU1018 | JFK → BOS | Jul 11, 15:15 UTC | Jul 12, 14:45 UTC | 23h 31m |
| 2026-07-11 | JBU1905 | FLL → TPA | Jul 11, 00:46 UTC | Jul 11, 22:45 UTC | 22h 0m |
| 2026-07-10 | JBU1496 | CUN → FLL | Jul 10, 20:34 UTC | Jul 11, 18:45 UTC | 22h 12m |
| 2026-07-10 | JBU351 | BOS → MCO | Jul 10, 12:28 UTC | Jul 11, 10:45 UTC | 22h 18m |
| 2026-07-09 | JBU270 | FLL → BOS | Jul 9, 23:36 UTC | Jul 10, 21:55 UTC | 22h 20m |
| 2026-07-09 | JBU269 | BOS → FLL | Jul 9, 18:04 UTC | Jul 10, 16:45 UTC | 22h 41m |
| 2026-07-09 | JBU1018 | JFK → BOS | Jul 9, 14:40 UTC | Jul 10, 12:45 UTC | 22h 6m |
| 2026-07-09 | JBU126 | TPA → JFK | Jul 9, 10:23 UTC | Jul 10, 03:20 UTC | 16h 58m |
| 2026-07-09 | JBU2752 | SJU → TPA | Jul 9, 00:20 UTC | Jul 9, 20:50 UTC | 20h 30m |
| 2026-07-08 | JBU929 | ORF → SJU | Jul 8, 19:50 UTC | Jul 9, 18:45 UTC | 22h 55m |
| 2026-07-08 | JBU1089 | EWR → SJU | Jul 8, 09:59 UTC | Jul 9, 02:55 UTC | 16h 57m |
| 2026-07-07 | JBU1990 | SJU → EWR | Jul 7, 23:57 UTC | Jul 8, 21:15 UTC | 21h 19m |
| 2026-07-07 | JBU238 | SDQ → SJU | Jul 7, 21:21 UTC | Jul 8, 20:45 UTC | 23h 25m |
| 2026-07-07 | JBU504 | SJU → JFK | Jul 7, 01:23 UTC | Jul 8, 00:10 UTC | 22h 47m |
| 2026-07-06 | JBU1704 | MDE → SJU | Jul 6, 20:38 UTC | Jul 7, 17:25 UTC | 20h 47m |
| 2026-07-06 | JBU41 | - | Jul 6, 16:10 UTC | Jul 6, 16:40 UTC | 30m |
| 2026-07-06 | JBU1594 | - | Jul 6, 13:50 UTC | Jul 6, 14:20 UTC | 30m |
| 2026-07-06 | JBU1593 | - | Jul 6, 11:55 UTC | Jul 6, 12:10 UTC | 15m |
| 2026-07-05 | JBU1393 | - | Jul 5, 15:55 UTC | Jul 5, 16:15 UTC | 20m |
| 2026-07-05 | JBU1393 | FLL → NAS | Jul 5, 15:53 UTC | Jul 6, 14:20 UTC | 22h 28m |
| 2026-07-05 | JBU959 | - | Jul 5, 11:30 UTC | Jul 5, 14:05 UTC | 2h 35m |
| 2026-07-05 | JBU460 | - | Jul 5, 00:50 UTC | Jul 5, 03:55 UTC | 3h 5m |
| 2026-07-04 | JBU1496 | - | Jul 4, 19:55 UTC | Jul 4, 21:15 UTC | 1h 20m |
| 2026-07-03 | JBU197 | - | Jul 3, 23:50 UTC | Jul 4, 05:15 UTC | 5h 25m |
| 2026-07-03 | JBU197 | BOS → SEA | Jul 3, 23:45 UTC | Jul 4, 21:15 UTC | 21h 30m |
| 2026-07-03 | JBU197 | BOS → BOS | Jul 3, 22:50 UTC | Jul 3, 22:55 UTC | 5m |
| 2026-07-03 | JBU1806 | - | Jul 3, 19:35 UTC | Jul 3, 21:40 UTC | 2h 5m |
| 2026-07-03 | JBU2421 | BOS → PBI | Jul 3, 02:25 UTC | Jul 4, 00:45 UTC | 22h 20m |
| 2026-07-02 | JBU2896 | PUJ → BOS | Jul 2, 14:38 UTC | Jul 3, 12:45 UTC | 22h 7m |
| 2026-07-02 | JBU2896 | - | Jul 2, 11:20 UTC | Jul 2, 18:15 UTC | 6h 55m |
| 2026-07-01 | JBU759 | BDL → FLL | Jul 1, 21:40 UTC | Jul 2, 00:15 UTC | 2h 35m |
| 2026-07-01 | JBU760 | - | Jul 1, 17:45 UTC | Jul 1, 20:20 UTC | 2h 35m |
| 2026-07-01 | JBU491 | BUF → LAX | Jul 1, 00:30 UTC | Jul 1, 05:20 UTC | 4h 50m |
| 2026-07-01 | JBU491 | BUF → LAX | Jul 1, 00:27 UTC | Jul 1, 22:45 UTC | 22h 19m |
| 2026-06-30 | JBU1115 | - | Jun 30, 22:00 UTC | Jun 30, 23:05 UTC | 1h 5m |
| 2026-06-30 | JBU68 | - | Jun 30, 18:10 UTC | Jun 30, 20:00 UTC | 1h 50m |
| 2026-06-30 | JBU267 | - | Jun 30, 15:00 UTC | Jun 30, 16:55 UTC | 1h 55m |
| 2026-06-30 | JBU690 | - | Jun 30, 10:50 UTC | Jun 30, 13:45 UTC | 2h 55m |
| 2026-06-30 | JBU613 | - | Jun 30, 02:15 UTC | Jun 30, 04:30 UTC | 2h 15m |
| 2026-06-29 | JBU1694 | - | Jun 29, 22:35 UTC | Jun 30, 00:55 UTC | 2h 20m |
| 2026-06-29 | JBU599 | LGA → MCO | Jun 29, 11:14 UTC | Jun 29, 13:24 UTC | 2h 10m |
| 2026-06-29 | JBU798 | MCO → LGA | Jun 29, 00:14 UTC | Jun 29, 02:35 UTC | 2h 20m |
| 2026-06-28 | JBU102 | JFK → BUF | Jun 28, 03:00 UTC | Jun 29, 02:39 UTC | 23h 40m |
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 N534JB page for operator, model, and routing details .