sensors Mode-S transponder
A7F6F6
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N612JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7F6F6
- Octal
- 51773366
- Decimal
- 11,007,734
- Country
- US
- Tail
- N612JB
- Type
- A320
- Flights observed
- 297
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A7F6F6 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 |
|---|---|---|---|
| JBU1042 | JetBlue Airways | 6 | 2026-06-18 |
| JBU1471 | - | 5 | 2026-07-08 |
| JBU2433 | JetBlue Airways | 4 | 2026-06-09 |
| JBU1793 | JetBlue Airways | 4 | 2026-05-07 |
| JBU1112 | JetBlue Airways | 4 | 2026-05-08 |
| JBU1043 | JetBlue Airways | 4 | 2026-06-06 |
| JBU808 | - | 3 | 2026-06-16 |
| JBU534 | JetBlue Airways | 3 | 2026-05-29 |
| JBU2475 | JetBlue Airways | 3 | 2026-04-14 |
| JBU225 | JetBlue Airways | 3 | 2026-04-18 |
| JBU1812 | JetBlue Airways | 3 | 2026-05-03 |
| JBU1691 | JetBlue Airways | 3 | 2026-05-31 |
| JBU1568 | JetBlue Airways | 3 | 2026-06-05 |
| JBU1202 | JetBlue Airways | 3 | 2026-05-10 |
| JBU1144 | - | 3 | 2026-06-26 |
| JBU1138 | JetBlue Airways | 3 | 2026-04-17 |
| JBU1039 | JetBlue Airways | 3 | 2026-04-16 |
| JBU1016 | - | 3 | 2026-06-20 |
| JBU998 | - | 2 | 2026-04-13 |
| JBU987 | JetBlue Airways | 2 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1233 | - | Jul 14, 09:15 UTC | Jul 14, 09:50 UTC | 35m |
| 2026-07-14 | JBU1233 | MCO → SJU | Jul 14, 09:14 UTC | Jul 15, 01:30 UTC | 16h 16m |
| 2026-07-13 | JBU483 | - | Jul 13, 22:50 UTC | Jul 14, 01:05 UTC | 2h 15m |
| 2026-07-13 | JBU1902 | FLL → JFK | Jul 13, 03:24 UTC | Jul 14, 01:20 UTC | 21h 57m |
| 2026-07-13 | JBU326 | MBJ → FLL | Jul 13, 00:29 UTC | Jul 13, 23:30 UTC | 23h 2m |
| 2026-07-12 | JBU1698 | FLL → ATL | Jul 12, 15:26 UTC | Jul 13, 12:25 UTC | 21h 0m |
| 2026-07-11 | JBU399 | LGA → MCO | Jul 11, 20:04 UTC | Jul 12, 19:30 UTC | 23h 27m |
| 2026-07-11 | JBU172 | FLL → LGA | Jul 11, 15:25 UTC | Jul 12, 12:50 UTC | 21h 26m |
| 2026-07-10 | JBU590 | - | Jul 10, 21:00 UTC | Jul 10, 22:50 UTC | 1h 50m |
| 2026-07-10 | JBU590 | SDQ → FLL | Jul 10, 20:46 UTC | Jul 11, 19:30 UTC | 22h 45m |
| 2026-07-10 | JBU589 | - | Jul 10, 17:15 UTC | Jul 10, 18:45 UTC | 1h 30m |
| 2026-07-10 | JBU959 | BDL → FLL | Jul 10, 12:15 UTC | Jul 10, 14:55 UTC | 2h 40m |
| 2026-07-10 | JBU276 | - | Jul 10, 01:05 UTC | Jul 10, 03:05 UTC | 2h 0m |
| 2026-07-09 | JBU276 | - | Jul 9, 23:15 UTC | Jul 9, 23:30 UTC | 15m |
| 2026-07-09 | JBU2851 | - | Jul 9, 21:40 UTC | Jul 9, 21:50 UTC | 10m |
| 2026-07-09 | JBU2851 | - | Jul 9, 19:15 UTC | Jul 9, 20:05 UTC | 50m |
| 2026-07-09 | JBU1447 | - | Jul 9, 15:15 UTC | Jul 9, 17:45 UTC | 2h 30m |
| 2026-07-09 | JBU814 | - | Jul 9, 11:05 UTC | Jul 9, 13:35 UTC | 2h 30m |
| 2026-07-08 | JBU41 | FLL → MDE | Jul 8, 16:49 UTC | Jul 9, 15:30 UTC | 22h 41m |
| 2026-07-08 | JBU1471 | LGA → FLL | Jul 8, 12:21 UTC | Jul 9, 11:30 UTC | 23h 9m |
| 2026-07-08 | JBU1471 | LGA → FLL | Jul 8, 12:25 UTC | Jul 8, 14:45 UTC | 2h 20m |
| 2026-07-07 | JBU1098 | MCO → LGA | Jul 7, 00:15 UTC | Jul 7, 02:35 UTC | 2h 20m |
| 2026-07-06 | JBU240 | - | Jul 6, 19:35 UTC | Jul 6, 20:20 UTC | 45m |
| 2026-07-05 | JBU2098 | - | Jul 5, 21:45 UTC | Jul 5, 23:15 UTC | 1h 30m |
| 2026-07-05 | JBU2098 | FLL → ATL | Jul 5, 21:43 UTC | Jul 6, 20:35 UTC | 22h 52m |
| 2026-07-05 | JBU2201 | JFK → FLL | Jul 5, 16:55 UTC | Jul 5, 19:20 UTC | 2h 25m |
| 2026-07-05 | JBU1002 | - | Jul 5, 12:45 UTC | Jul 5, 15:20 UTC | 2h 35m |
| 2026-07-04 | JBU1157 | FLL → LIR | Jul 4, 15:02 UTC | Jul 5, 13:30 UTC | 22h 28m |
| 2026-07-03 | JBU974 | AUA → BOS | Jul 3, 21:58 UTC | Jul 4, 21:25 UTC | 23h 28m |
| 2026-07-03 | JBU1160 | PHL → BOS | Jul 3, 12:40 UTC | Jul 4, 11:30 UTC | 22h 50m |
| 2026-07-03 | JBU1159 | BOS → PHL | Jul 3, 10:23 UTC | Jul 4, 09:25 UTC | 23h 2m |
| 2026-07-02 | JBU137 | BDL → MCO | Jul 2, 20:50 UTC | Jul 3, 19:30 UTC | 22h 41m |
| 2026-07-02 | JBU2938 | MCO → BDL | Jul 2, 17:00 UTC | Jul 3, 15:30 UTC | 22h 31m |
| 2026-07-01 | JBU1152 | MCO → BOS | Jul 1, 21:54 UTC | Jul 2, 21:30 UTC | 23h 36m |
| 2026-07-01 | JBU546 | MCO → ISP | Jul 1, 12:13 UTC | Jul 2, 09:50 UTC | 21h 37m |
| 2026-07-01 | JBU229 | BQN → MCO | Jul 1, 05:47 UTC | Jul 2, 04:35 UTC | 22h 49m |
| 2026-07-01 | JBU730 | MCO → BQN | Jul 1, 02:17 UTC | Jul 2, 01:30 UTC | 23h 14m |
| 2026-07-01 | JBU730 | - | Jul 1, 02:20 UTC | Jul 1, 03:00 UTC | 40m |
| 2026-06-30 | JBU499 | - | Jun 30, 23:20 UTC | Jun 30, 23:55 UTC | 35m |
| 2026-06-30 | JBU499 | - | Jun 30, 15:45 UTC | Jun 30, 18:40 UTC | 2h 55m |
| 2026-06-30 | JBU1062 | - | Jun 30, 11:50 UTC | Jun 30, 14:15 UTC | 2h 25m |
| 2026-06-29 | JBU24 | PBI → DCA | Jun 29, 18:30 UTC | Jun 29, 20:24 UTC | 1h 55m |
| 2026-06-29 | JBU24 | PBI → DCA | Jun 29, 18:29 UTC | Jun 30, 17:30 UTC | 23h 2m |
| 2026-06-29 | JBU2143 | - | Jun 29, 14:44 UTC | Jun 29, 16:55 UTC | 2h 10m |
| 2026-06-29 | JBU306 | - | Jun 29, 10:44 UTC | Jun 29, 13:19 UTC | 2h 35m |
| 2026-06-29 | JBU305 | EWR → FLL | Jun 29, 00:34 UTC | Jun 29, 02:59 UTC | 2h 25m |
| 2026-06-28 | JBU1728 | MCO → EWR | Jun 28, 02:59 UTC | Jun 29, 01:29 UTC | 22h 31m |
| 2026-06-27 | JBU399 | TPA → MCO | Jun 27, 23:44 UTC | Jun 28, 21:24 UTC | 21h 41m |
| 2026-06-27 | JBU1505 | EWR → FLL | Jun 27, 10:49 UTC | Jun 28, 05:15 UTC | 18h 26m |
| 2026-06-27 | JBU2128 | MCO → EWR | Jun 27, 01:19 UTC | Jun 27, 04:09 UTC | 2h 50m |
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 N612JB page for operator, model, and routing details .