sensors Mode-S transponder
A67883
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N516JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A67883
- Octal
- 51474203
- Decimal
- 10,909,827
- Country
- US
- Tail
- N516JB
- Type
- A320
- Flights observed
- 291
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A67883 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 |
|---|---|---|---|
| JBU768 | JetBlue Airways | 4 | 2026-05-25 |
| JBU406 | - | 4 | 2026-06-30 |
| JBU2840 | JetBlue Airways | 4 | 2026-05-18 |
| JBU1252 | JetBlue Airways | 4 | 2026-05-25 |
| JBU709 | - | 3 | 2026-07-05 |
| JBU572 | - | 3 | 2026-06-24 |
| JBU564 | JetBlue Airways | 3 | 2026-06-09 |
| JBU465 | JetBlue Airways | 3 | 2026-04-14 |
| JBU444 | - | 3 | 2026-07-11 |
| JBU403 | JetBlue Airways | 3 | 2026-06-03 |
| JBU297 | - | 3 | 2026-07-02 |
| JBU2929 | - | 3 | 2026-04-13 |
| JBU1731 | JetBlue Airways | 3 | 2026-05-21 |
| JBU1475 | JetBlue Airways | 3 | 2026-06-06 |
| JBU1186 | - | 3 | 2026-07-03 |
| JBU1185 | - | 3 | 2026-07-03 |
| JBU106 | JetBlue Airways | 3 | 2026-06-13 |
| JBU967 | JetBlue Airways | 2 | 2026-04-15 |
| JBU959 | JetBlue Airways | 2 | 2026-04-16 |
| JBU94 | JetBlue Airways | 2 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU1948 | - | Jul 15, 01:20 UTC | Jul 15, 02:05 UTC | 45m |
| 2026-07-14 | JBU2595 | - | Jul 14, 20:25 UTC | Jul 14, 22:30 UTC | 2h 5m |
| 2026-07-14 | JBU2094 | - | Jul 14, 17:05 UTC | Jul 14, 19:15 UTC | 2h 10m |
| 2026-07-14 | JBU2547 | MCO → FLL | Jul 14, 14:30 UTC | Jul 14, 15:05 UTC | 35m |
| 2026-07-14 | JBU234 | BDL → MCO | Jul 14, 01:50 UTC | Jul 14, 09:10 UTC | 7h 20m |
| 2026-07-13 | JBU2450 | STI → FLL | Jul 13, 09:02 UTC | Jul 14, 08:45 UTC | 23h 44m |
| 2026-07-13 | JBU2449 | FLL → STI | Jul 13, 02:29 UTC | Jul 14, 00:35 UTC | 22h 7m |
| 2026-07-12 | JBU517 | BOS → JFK | Jul 12, 15:36 UTC | Jul 13, 14:45 UTC | 23h 10m |
| 2026-07-12 | JBU518 | FLL → ATL | Jul 12, 10:37 UTC | Jul 13, 02:55 UTC | 16h 19m |
| 2026-07-12 | JBU1979 | DCA → FLL | Jul 12, 02:59 UTC | Jul 13, 02:45 UTC | 23h 47m |
| 2026-07-11 | JBU444 | - | Jul 11, 15:05 UTC | Jul 12, 14:15 UTC | 23h 11m |
| 2026-07-10 | JBU1354 | DCA → BOS | Jul 10, 18:55 UTC | Jul 10, 19:55 UTC | 1h 0m |
| 2026-07-10 | JBU1354 | DCA → BOS | Jul 10, 18:54 UTC | Jul 11, 17:20 UTC | 22h 27m |
| 2026-07-09 | JBU256 | BZN → BOS | Jul 9, 20:04 UTC | Jul 10, 13:20 UTC | 17h 16m |
| 2026-07-09 | JBU257 | BOS → BOS | Jul 9, 12:55 UTC | Jul 9, 23:50 UTC | 10h 55m |
| 2026-07-09 | JBU462 | - | Jul 9, 00:55 UTC | Jul 9, 04:25 UTC | 3h 30m |
| 2026-07-08 | JBU1743 | - | Jul 8, 23:15 UTC | Jul 8, 23:35 UTC | 20m |
| 2026-07-08 | JBU1743 | - | Jul 8, 20:50 UTC | Jul 8, 21:35 UTC | 45m |
| 2026-07-08 | JBU1742 | - | Jul 8, 18:15 UTC | Jul 8, 19:25 UTC | 1h 10m |
| 2026-07-08 | JBU1742 | - | Jul 8, 16:35 UTC | Jul 8, 16:50 UTC | 15m |
| 2026-07-08 | JBU635 | - | Jul 8, 15:05 UTC | Jul 8, 15:20 UTC | 15m |
| 2026-07-08 | JBU635 | - | Jul 8, 11:20 UTC | Jul 8, 12:50 UTC | 1h 30m |
| 2026-07-07 | JBU1142 | PBI → BDL | Jul 7, 14:58 UTC | Jul 8, 12:50 UTC | 21h 53m |
| 2026-07-07 | JBU548 | TPA → HPN | Jul 7, 03:02 UTC | Jul 8, 02:05 UTC | 23h 3m |
| 2026-07-06 | JBU873 | EWR → TPA | Jul 6, 23:25 UTC | Jul 7, 22:35 UTC | 23h 11m |
| 2026-07-06 | JBU2219 | EWR → AUA | Jul 6, 11:14 UTC | Jul 7, 05:40 UTC | 18h 27m |
| 2026-07-05 | JBU1016 | PUJ → EWR | Jul 5, 20:41 UTC | Jul 6, 17:15 UTC | 20h 35m |
| 2026-07-05 | JBU1015 | EWR → PUJ | Jul 5, 15:35 UTC | Jul 6, 14:45 UTC | 23h 10m |
| 2026-07-05 | JBU709 | JFK → SDQ | Jul 5, 05:14 UTC | Jul 6, 00:20 UTC | 19h 6m |
| 2026-07-04 | JBU279 | JFK → MBJ | Jul 4, 15:44 UTC | Jul 5, 13:55 UTC | 22h 11m |
| 2026-07-04 | JBU279 | - | Jul 4, 15:45 UTC | Jul 4, 18:55 UTC | 3h 10m |
| 2026-07-03 | JBU1185 | ROC → JFK | Jul 3, 10:40 UTC | Jul 4, 03:55 UTC | 17h 16m |
| 2026-07-03 | JBU1186 | JFK → ROC | Jul 3, 02:41 UTC | Jul 4, 00:45 UTC | 22h 4m |
| 2026-07-02 | JBU297 | - | Jul 2, 20:10 UTC | Jul 2, 20:35 UTC | 25m |
| 2026-07-02 | JBU297 | SKB → JFK | Jul 2, 19:54 UTC | Jul 3, 17:35 UTC | 21h 41m |
| 2026-07-02 | JBU296 | - | Jul 2, 14:55 UTC | Jul 2, 18:15 UTC | 3h 20m |
| 2026-07-02 | JBU130 | RSW → JFK | Jul 2, 10:15 UTC | Jul 2, 12:35 UTC | 2h 20m |
| 2026-07-02 | JBU2129 | JFK → RSW | Jul 2, 02:40 UTC | Jul 2, 05:05 UTC | 2h 25m |
| 2026-07-01 | JBU1112 | - | Jul 1, 19:30 UTC | Jul 1, 23:30 UTC | 4h 0m |
| 2026-06-30 | JBU406 | ORD → JFK | Jun 30, 23:45 UTC | Jul 1, 01:25 UTC | 1h 40m |
| 2026-06-30 | JBU406 | ORD → JFK | Jun 30, 23:42 UTC | Jul 1, 22:45 UTC | 23h 4m |
| 2026-06-30 | JBU405 | - | Jun 30, 20:00 UTC | Jun 30, 21:55 UTC | 1h 55m |
| 2026-06-29 | JBU1185 | ROC → JFK | Jun 29, 10:35 UTC | Jun 30, 02:15 UTC | 15h 41m |
| 2026-06-29 | JBU1185 | ROC → JFK | Jun 29, 10:40 UTC | Jun 29, 11:25 UTC | 45m |
| 2026-06-29 | JBU1186 | - | Jun 29, 02:54 UTC | Jun 29, 03:44 UTC | 50m |
| 2026-06-28 | JBU297 | - | Jun 28, 21:04 UTC | Jun 29, 00:39 UTC | 3h 35m |
| 2026-06-28 | JBU296 | - | Jun 28, 16:00 UTC | Jun 28, 19:20 UTC | 3h 20m |
| 2026-06-27 | JBU766 | GCM → JFK | Jun 27, 19:08 UTC | Jun 28, 16:35 UTC | 21h 27m |
| 2026-06-27 | JBU766 | JFK → JFK | Jun 27, 14:25 UTC | Jun 27, 23:25 UTC | 9h 0m |
| 2026-06-26 | JBU1111 | JFK → CUR | Jun 26, 13:49 UTC | Jun 26, 23:34 UTC | 9h 46m |
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 N516JB page for operator, model, and routing details .