sensors Mode-S transponder
A7FAAD
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N613JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7FAAD
- Octal
- 51775255
- Decimal
- 11,008,685
- Country
- US
- Tail
- N613JB
- Type
- A320
- Flights observed
- 279
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A7FAAD 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 |
|---|---|---|---|
| JBU2031 | - | 6 | 2026-07-10 |
| JBU1751 | - | 5 | 2026-07-08 |
| JBU504 | - | 4 | 2026-07-09 |
| JBU351 | - | 4 | 2026-07-11 |
| JBU1241 | JetBlue Airways | 4 | 2026-06-06 |
| JBU97 | JetBlue Airways | 3 | 2026-04-17 |
| JBU572 | - | 3 | 2026-06-20 |
| JBU389 | - | 3 | 2026-04-16 |
| JBU368 | - | 3 | 2026-07-07 |
| JBU337 | JetBlue Airways | 3 | 2026-05-19 |
| JBU1692 | JetBlue Airways | 3 | 2026-04-17 |
| JBU1641 | JetBlue Airways | 3 | 2026-04-27 |
| JBU1154 | JetBlue Airways | 3 | 2026-06-07 |
| JBU98 | JetBlue Airways | 2 | 2026-04-17 |
| JBU94 | JetBlue Airways | 2 | 2026-05-26 |
| JBU884 | JetBlue Airways | 2 | 2026-05-23 |
| JBU851 | - | 2 | 2026-06-22 |
| JBU850 | - | 2 | 2026-07-01 |
| JBU83 | JetBlue Airways | 2 | 2026-05-29 |
| JBU773 | - | 2 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1717 | PSE → FLL | Jul 14, 08:57 UTC | Jul 14, 15:15 UTC | 6h 19m |
| 2026-07-13 | JBU2182 | - | Jul 13, 17:55 UTC | Jul 13, 20:40 UTC | 2h 45m |
| 2026-07-13 | JBU2182 | FLL → DFW | Jul 13, 17:51 UTC | Jul 14, 15:15 UTC | 21h 25m |
| 2026-07-13 | JBU669 | BOS → FLL | Jul 13, 12:15 UTC | Jul 13, 15:05 UTC | 2h 50m |
| 2026-07-13 | JBU50 | - | Jul 13, 05:10 UTC | Jul 13, 09:50 UTC | 4h 40m |
| 2026-07-12 | JBU49 | - | Jul 12, 22:25 UTC | Jul 13, 04:00 UTC | 5h 35m |
| 2026-07-12 | JBU1354 | DCA → BOS | Jul 12, 19:25 UTC | Jul 12, 20:35 UTC | 1h 10m |
| 2026-07-12 | JBU2334 | - | Jul 12, 16:01 UTC | Jul 12, 17:55 UTC | 1h 55m |
| 2026-07-11 | JBU769 | RIC → MCO | Jul 11, 20:20 UTC | Jul 12, 19:10 UTC | 22h 51m |
| 2026-07-11 | JBU351 | BOS → MCO | Jul 11, 12:21 UTC | Jul 12, 10:10 UTC | 21h 50m |
| 2026-07-11 | JBU462 | SJU → BOS | Jul 11, 03:06 UTC | Jul 11, 23:15 UTC | 20h 10m |
| 2026-07-10 | JBU2031 | - | Jul 10, 22:05 UTC | Jul 10, 22:20 UTC | 15m |
| 2026-07-10 | JBU2031 | SJU → PUJ | Jul 10, 22:04 UTC | Jul 11, 21:15 UTC | 23h 12m |
| 2026-07-09 | JBU944 | BZN → PIT | Jul 9, 17:58 UTC | Jul 10, 12:35 UTC | 18h 37m |
| 2026-07-09 | JBU504 | - | Jul 9, 00:25 UTC | Jul 9, 03:45 UTC | 3h 20m |
| 2026-07-09 | JBU504 | SJU → JFK | Jul 9, 00:24 UTC | Jul 9, 21:55 UTC | 21h 31m |
| 2026-07-08 | JBU2941 | - | Jul 8, 22:40 UTC | Jul 8, 22:50 UTC | 10m |
| 2026-07-08 | JBU2031 | - | Jul 8, 20:05 UTC | Jul 8, 20:20 UTC | 15m |
| 2026-07-08 | JBU1751 | - | Jul 8, 17:55 UTC | Jul 8, 18:05 UTC | 10m |
| 2026-07-08 | JBU1751 | - | Jul 8, 15:25 UTC | Jul 8, 16:20 UTC | 55m |
| 2026-07-08 | JBU1447 | - | Jul 8, 11:40 UTC | Jul 8, 14:00 UTC | 2h 20m |
| 2026-07-07 | JBU367 | HPN → PBI | Jul 7, 18:40 UTC | Jul 8, 16:20 UTC | 21h 41m |
| 2026-07-07 | JBU1551 | HPN → RSW | Jul 7, 10:56 UTC | Jul 8, 01:55 UTC | 15h 0m |
| 2026-07-07 | JBU368 | PBI → HPN | Jul 7, 02:52 UTC | Jul 8, 01:15 UTC | 22h 24m |
| 2026-07-06 | JBU698 | MCO → LGA | Jul 6, 17:37 UTC | Jul 7, 17:10 UTC | 23h 34m |
| 2026-07-06 | JBU351 | BOS → MCO | Jul 6, 12:51 UTC | Jul 7, 11:15 UTC | 22h 25m |
| 2026-07-05 | JBU974 | AUA → BOS | Jul 5, 21:51 UTC | Jul 6, 20:10 UTC | 22h 19m |
| 2026-07-05 | JBU773 | - | Jul 5, 15:55 UTC | Jul 5, 17:15 UTC | 1h 20m |
| 2026-07-05 | JBU773 | BOS → AUA | Jul 5, 15:53 UTC | Jul 6, 15:15 UTC | 23h 22m |
| 2026-07-05 | JBU322 | - | Jul 5, 11:05 UTC | Jul 5, 13:45 UTC | 2h 40m |
| 2026-07-05 | JBU143 | - | Jul 5, 05:25 UTC | Jul 5, 07:35 UTC | 2h 10m |
| 2026-07-04 | JBU1230 | CUN → EWR | Jul 4, 18:15 UTC | Jul 4, 21:35 UTC | 3h 20m |
| 2026-07-04 | JBU770 | MCO → RIC | Jul 4, 01:36 UTC | Jul 5, 01:15 UTC | 23h 39m |
| 2026-07-03 | JBU499 | LGA → MCO | Jul 3, 14:25 UTC | Jul 4, 13:10 UTC | 22h 45m |
| 2026-07-02 | JBU1880 | FLL → DCA | Jul 2, 20:32 UTC | Jul 3, 18:40 UTC | 22h 9m |
| 2026-07-01 | JBU850 | STI → JFK | Jul 1, 22:09 UTC | Jul 2, 21:15 UTC | 23h 6m |
| 2026-07-01 | JBU850 | JFK → JFK | Jul 1, 17:30 UTC | Jul 2, 01:20 UTC | 7h 50m |
| 2026-07-01 | JBU2102 | - | Jul 1, 13:15 UTC | Jul 1, 15:30 UTC | 2h 15m |
| 2026-07-01 | JBU754 | SJU → FLL | Jul 1, 09:40 UTC | Jul 1, 11:50 UTC | 2h 10m |
| 2026-06-29 | JBU703 | - | Jun 29, 16:29 UTC | Jun 29, 19:44 UTC | 3h 15m |
| 2026-06-29 | JBU1017 | BOS → JFK | Jun 29, 13:00 UTC | Jun 29, 13:39 UTC | 40m |
| 2026-06-28 | JBU1194 | - | Jun 28, 15:34 UTC | Jun 29, 00:24 UTC | 8h 50m |
| 2026-06-27 | JBU1194 | MBJ → JFK | Jun 27, 21:01 UTC | Jun 28, 18:25 UTC | 21h 24m |
| 2026-06-27 | JBU1193 | - | Jun 27, 15:30 UTC | Jun 27, 18:35 UTC | 3h 5m |
| 2026-06-27 | JBU1193 | BOS → MBJ | Jun 27, 15:28 UTC | Jun 28, 15:14 UTC | 23h 47m |
| 2026-06-27 | JBU690 | FLL → BOS | Jun 27, 10:40 UTC | Jun 27, 13:24 UTC | 2h 45m |
| 2026-06-26 | JBU1799 | ORF → FLL | Jun 26, 16:49 UTC | Jun 27, 13:30 UTC | 20h 41m |
| 2026-06-26 | JBU1906 | TPA → FLL | Jun 26, 11:45 UTC | Jun 27, 11:14 UTC | 23h 30m |
| 2026-06-25 | JBU1454 | SJU → FLL | Jun 25, 20:42 UTC | Jun 26, 18:44 UTC | 22h 3m |
| 2026-06-25 | JBU1433 | - | Jun 25, 02:49 UTC | Jun 25, 03:15 UTC | 25m |
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 N613JB page for operator, model, and routing details .