sensors Mode-S transponder
A7BFA0
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N599JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7BFA0
- Octal
- 51737640
- Decimal
- 10,993,568
- Country
- US
- Tail
- N599JB
- Type
- A320
- Flights observed
- 227
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A7BFA0 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 |
|---|---|---|---|
| JBU2937 | JetBlue Airways | 4 | 2026-06-27 |
| JBU1903 | JetBlue Airways | 4 | 2026-06-02 |
| JBU861 | JetBlue Airways | 3 | 2026-06-01 |
| JBU709 | JetBlue Airways | 3 | 2026-04-21 |
| JBU403 | JetBlue Airways | 3 | 2026-06-05 |
| JBU2390 | - | 3 | 2026-04-13 |
| JBU2389 | - | 3 | 2026-07-05 |
| JBU1742 | - | 3 | 2026-06-19 |
| JBU1527 | JetBlue Airways | 3 | 2026-04-13 |
| JBU1405 | - | 3 | 2026-04-13 |
| JBU1371 | JetBlue Airways | 3 | 2026-07-04 |
| JBU979 | - | 2 | 2026-06-26 |
| JBU927 | - | 2 | 2026-06-30 |
| JBU914 | JetBlue Airways | 2 | 2026-04-14 |
| JBU8557 | JetBlue Airways | 2 | 2026-04-15 |
| JBU847 | - | 2 | 2026-07-06 |
| JBU769 | - | 2 | 2026-07-09 |
| JBU710 | JetBlue Airways | 2 | 2026-05-28 |
| JBU698 | - | 2 | 2026-06-25 |
| JBU613 | JetBlue Airways | 2 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1196 | - | Jul 13, 23:10 UTC | Jul 14, 01:45 UTC | 2h 35m |
| 2026-07-13 | JBU1775 | FLL → KIN | Jul 13, 03:06 UTC | Jul 14, 01:45 UTC | 22h 40m |
| 2026-07-12 | JBU1975 | FLL → KIN | Jul 12, 21:14 UTC | Jul 13, 16:55 UTC | 19h 42m |
| 2026-07-12 | JBU1676 | KIN → FLL | Jul 12, 17:17 UTC | Jul 13, 13:40 UTC | 20h 24m |
| 2026-07-12 | JBU1675 | - | Jul 12, 14:30 UTC | Jul 12, 15:05 UTC | 35m |
| 2026-07-12 | JBU1675 | FLL → KIN | Jul 12, 14:30 UTC | Jul 13, 13:40 UTC | 23h 11m |
| 2026-07-12 | JBU1906 | TPA → FLL | Jul 12, 11:50 UTC | Jul 12, 12:30 UTC | 40m |
| 2026-07-12 | JBU1905 | - | Jul 12, 00:20 UTC | Jul 12, 01:00 UTC | 40m |
| 2026-07-11 | JBU864 | - | Jul 11, 19:55 UTC | Jul 11, 22:30 UTC | 2h 35m |
| 2026-07-11 | JBU663 | PPM → ORD | Jul 11, 15:15 UTC | Jul 11, 18:05 UTC | 2h 50m |
| 2026-07-10 | JBU2090 | SAP → FLL | Jul 10, 20:42 UTC | Jul 11, 20:00 UTC | 23h 19m |
| 2026-07-10 | JBU2089 | FLL → SAP | Jul 10, 17:17 UTC | Jul 11, 16:00 UTC | 22h 44m |
| 2026-07-09 | JBU1496 | CUN → FLL | Jul 9, 20:47 UTC | Jul 10, 18:55 UTC | 22h 8m |
| 2026-07-09 | JBU1013 | - | Jul 9, 17:25 UTC | Jul 9, 18:00 UTC | 35m |
| 2026-07-09 | JBU1013 | MCO → CUN | Jul 9, 17:22 UTC | Jul 10, 14:45 UTC | 21h 23m |
| 2026-07-09 | JBU769 | - | Jul 9, 13:45 UTC | Jul 9, 15:25 UTC | 1h 40m |
| 2026-07-09 | JBU770 | MCO → RIC | Jul 9, 10:40 UTC | Jul 9, 12:20 UTC | 1h 40m |
| 2026-07-08 | JBU352 | MCO → BOS | Jul 8, 10:14 UTC | Jul 9, 01:25 UTC | 15h 12m |
| 2026-07-08 | JBU1134 | SJU → MCO | Jul 8, 02:33 UTC | Jul 9, 01:25 UTC | 22h 53m |
| 2026-07-07 | JBU1704 | MDE → SJU | Jul 7, 20:49 UTC | Jul 8, 19:35 UTC | 22h 47m |
| 2026-07-07 | JBU769 | RIC → MCO | Jul 7, 10:13 UTC | Jul 8, 05:20 UTC | 19h 8m |
| 2026-07-06 | JBU847 | - | Jul 6, 21:40 UTC | Jul 7, 00:00 UTC | 2h 20m |
| 2026-07-06 | JBU847 | ISP → MCO | Jul 6, 21:38 UTC | Jul 7, 17:05 UTC | 19h 28m |
| 2026-07-06 | JBU544 | - | Jul 6, 17:40 UTC | Jul 6, 20:05 UTC | 2h 25m |
| 2026-07-06 | JBU1241 | - | Jul 6, 13:20 UTC | Jul 6, 15:50 UTC | 2h 30m |
| 2026-07-05 | JBU2890 | SJU → EWR | Jul 5, 10:14 UTC | Jul 6, 03:10 UTC | 16h 57m |
| 2026-07-05 | JBU2389 | EWR → SJU | Jul 5, 03:56 UTC | Jul 5, 23:50 UTC | 19h 54m |
| 2026-07-04 | JBU1371 | LGA → FLL | Jul 4, 18:24 UTC | Jul 5, 16:20 UTC | 21h 57m |
| 2026-07-04 | JBU1371 | LGA → FLL | Jul 4, 18:25 UTC | Jul 4, 20:00 UTC | 1h 35m |
| 2026-07-04 | JBU1062 | - | Jul 4, 14:10 UTC | Jul 4, 16:30 UTC | 2h 20m |
| 2026-07-03 | JBU2795 | - | Jul 3, 16:00 UTC | Jul 3, 17:30 UTC | 1h 30m |
| 2026-07-03 | JBU2795 | FLL → CUN | Jul 3, 15:59 UTC | Jul 4, 05:20 UTC | 13h 22m |
| 2026-07-03 | JBU2282 | - | Jul 3, 11:25 UTC | Jul 3, 13:45 UTC | 2h 20m |
| 2026-07-02 | JBU1067 | - | Jul 2, 11:10 UTC | Jul 2, 13:35 UTC | 2h 25m |
| 2026-07-02 | JBU1067 | HPN → PBI | Jul 2, 11:05 UTC | Jul 3, 03:35 UTC | 16h 31m |
| 2026-07-01 | JBU225 | JFK → TPA | Jul 1, 10:37 UTC | Jul 2, 02:30 UTC | 15h 54m |
| 2026-06-30 | JBU18 | POS → JFK | Jun 30, 23:45 UTC | Jul 1, 21:30 UTC | 21h 46m |
| 2026-06-30 | JBU927 | EWR → MCO | Jun 30, 09:40 UTC | Jun 30, 11:40 UTC | 2h 0m |
| 2026-06-30 | JBU927 | EWR → MCO | Jun 30, 09:37 UTC | Jul 1, 04:35 UTC | 18h 59m |
| 2026-06-30 | JBU2128 | - | Jun 30, 01:19 UTC | Jun 30, 03:30 UTC | 2h 11m |
| 2026-06-29 | JBU1143 | - | Jun 29, 20:49 UTC | Jun 29, 23:29 UTC | 2h 40m |
| 2026-06-29 | JBU1144 | - | Jun 29, 16:55 UTC | Jun 29, 19:24 UTC | 2h 30m |
| 2026-06-29 | JBU430 | - | Jun 29, 09:29 UTC | Jun 29, 15:30 UTC | 6h 0m |
| 2026-06-29 | JBU283 | - | Jun 29, 02:35 UTC | Jun 29, 04:39 UTC | 2h 5m |
| 2026-06-29 | JBU317 | BOS → JFK | Jun 29, 00:00 UTC | Jun 29, 00:39 UTC | 40m |
| 2026-06-28 | JBU1216 | - | Jun 28, 20:45 UTC | Jun 28, 21:40 UTC | 55m |
| 2026-06-28 | JBU433 | BTV → JFK | Jun 28, 01:46 UTC | Jun 29, 00:00 UTC | 22h 14m |
| 2026-06-27 | JBU2937 | BDL → MCO | Jun 27, 19:38 UTC | Jun 28, 18:00 UTC | 22h 22m |
| 2026-06-27 | JBU2937 | BDL → MCO | Jun 27, 19:39 UTC | Jun 27, 19:59 UTC | 20m |
| 2026-06-27 | JBU2938 | MCO → BDL | Jun 27, 15:14 UTC | Jun 27, 17:34 UTC | 2h 20m |
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 N599JB page for operator, model, and routing details .