sensors Mode-S transponder
A36B73
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3196J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A36B73
- Octal
- 50665563
- Decimal
- 10,709,875
- Country
- US
- Tail
- N3196J
- Type
- BCS3
- Flights observed
- 272
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address A36B73 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 |
|---|---|---|---|
| JBU2725 | JetBlue Airways | 6 | 2026-05-18 |
| JBU2587 | JetBlue Airways | 6 | 2026-05-16 |
| JBU185 | - | 5 | 2026-07-02 |
| JBU1365 | JetBlue Airways | 5 | 2026-05-18 |
| JBU509 | - | 4 | 2026-06-22 |
| JBU359 | JetBlue Airways | 4 | 2026-05-17 |
| JBU349 | JetBlue Airways | 4 | 2026-06-03 |
| JBU312 | JetBlue Airways | 4 | 2026-05-27 |
| JBU226 | JetBlue Airways | 4 | 2026-05-18 |
| JBU2032 | JetBlue Airways | 4 | 2026-05-24 |
| JBU1931 | JetBlue Airways | 4 | 2026-05-24 |
| JBU1154 | - | 4 | 2026-06-30 |
| JBU392 | JetBlue Airways | 3 | 2026-05-03 |
| JBU2768 | JetBlue Airways | 3 | 2026-05-12 |
| JBU2602 | JetBlue Airways | 3 | 2026-06-08 |
| JBU250 | JetBlue Airways | 3 | 2026-06-03 |
| JBU2473 | JetBlue Airways | 3 | 2026-05-11 |
| JBU2324 | JetBlue Airways | 3 | 2026-06-11 |
| JBU2286 | - | 3 | 2026-06-28 |
| JBU2229 | JetBlue Airways | 3 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | JBU8450 | BOS → YMX | Jul 8, 20:34 UTC | Jul 8, 21:50 UTC | 1h 17m |
| 2026-07-08 | JBU8450 | - | Jul 8, 20:35 UTC | Jul 8, 21:25 UTC | 50m |
| 2026-07-04 | JBU1595 | BOS → BOS | Jul 4, 19:15 UTC | Jul 4, 19:25 UTC | 10m |
| 2026-07-04 | JBU386 | - | Jul 4, 14:55 UTC | Jul 4, 16:05 UTC | 1h 10m |
| 2026-07-04 | JBU385 | - | Jul 4, 12:10 UTC | Jul 4, 13:25 UTC | 1h 15m |
| 2026-07-03 | JBU1232 | - | Jul 3, 17:10 UTC | Jul 3, 19:40 UTC | 2h 30m |
| 2026-07-03 | JBU1232 | VRB → BOS | Jul 3, 17:07 UTC | Jul 4, 16:40 UTC | 23h 33m |
| 2026-07-03 | JBU1231 | - | Jul 3, 13:10 UTC | Jul 3, 15:40 UTC | 2h 30m |
| 2026-07-03 | MX3196 | BOS → BOS | Jul 3, 11:00 UTC | Jul 3, 11:05 UTC | 5m |
| 2026-07-02 | JBU185 | - | Jul 2, 05:05 UTC | Jul 2, 06:00 UTC | 55m |
| 2026-07-02 | JBU185 | JFK → RDU | Jul 2, 05:05 UTC | Jul 3, 00:25 UTC | 19h 20m |
| 2026-06-30 | JBU860 | - | Jun 30, 19:35 UTC | Jul 1, 04:00 UTC | 8h 25m |
| 2026-06-30 | JBU1154 | PBI → JFK | Jun 30, 14:55 UTC | Jun 30, 17:20 UTC | 2h 25m |
| 2026-06-30 | JBU953 | - | Jun 30, 11:15 UTC | Jun 30, 13:30 UTC | 2h 15m |
| 2026-06-29 | JBU1964 | JFK → HYA | Jun 29, 17:49 UTC | Jun 30, 16:45 UTC | 22h 56m |
| 2026-06-29 | JBU185 | JFK → RDU | Jun 29, 02:16 UTC | Jun 30, 00:45 UTC | 22h 29m |
| 2026-06-28 | JBU2286 | RDU → JFK | Jun 28, 22:24 UTC | Jun 28, 23:34 UTC | 1h 10m |
| 2026-06-28 | JBU2286 | RDU → JFK | Jun 28, 22:24 UTC | Jun 29, 18:39 UTC | 20h 16m |
| 2026-06-28 | JBU2785 | - | Jun 28, 19:49 UTC | Jun 28, 20:54 UTC | 1h 5m |
| 2026-06-28 | JBU92 | - | Jun 28, 16:25 UTC | Jun 28, 17:04 UTC | 40m |
| 2026-06-28 | JBU2091 | - | Jun 28, 14:19 UTC | Jun 28, 14:54 UTC | 35m |
| 2026-06-27 | JBU36 | STI → JFK | Jun 27, 19:19 UTC | Jun 28, 16:45 UTC | 21h 26m |
| 2026-06-27 | JBU237 | JFK → STI | Jun 27, 13:58 UTC | Jun 28, 10:55 UTC | 20h 57m |
| 2026-06-27 | JBU955 | JFK → DCA | Jun 27, 02:14 UTC | Jun 27, 03:09 UTC | 55m |
| 2026-06-27 | JBU955 | JFK → DCA | Jun 27, 02:11 UTC | Jun 27, 23:34 UTC | 21h 24m |
| 2026-06-26 | JBU678 | JAX → JFK | Jun 26, 21:45 UTC | Jun 26, 23:55 UTC | 2h 10m |
| 2026-06-26 | JBU677 | - | Jun 26, 18:29 UTC | Jun 26, 20:29 UTC | 2h 0m |
| 2026-06-26 | JBU2474 | - | Jun 26, 14:55 UTC | Jun 26, 16:24 UTC | 1h 30m |
| 2026-06-26 | JBU1273 | - | Jun 26, 12:05 UTC | Jun 26, 13:34 UTC | 1h 30m |
| 2026-06-25 | JBU1232 | VRB → BOS | Jun 25, 17:22 UTC | Jun 26, 16:30 UTC | 23h 8m |
| 2026-06-25 | JBU1231 | BOS → VRB | Jun 25, 13:01 UTC | Jun 26, 12:44 UTC | 23h 44m |
| 2026-06-25 | JBU185 | JFK → RDU | Jun 25, 02:27 UTC | Jun 26, 00:39 UTC | 22h 13m |
| 2026-06-24 | JBU2286 | RDU → JFK | Jun 24, 23:29 UTC | Jun 25, 22:45 UTC | 23h 16m |
| 2026-06-24 | JBU1154 | - | Jun 24, 14:34 UTC | Jun 24, 16:54 UTC | 2h 20m |
| 2026-06-24 | JBU1154 | PBI → JFK | Jun 24, 14:31 UTC | Jun 25, 12:44 UTC | 22h 14m |
| 2026-06-24 | JBU21 | MCO → MBJ | Jun 24, 10:25 UTC | Jun 24, 13:10 UTC | 2h 45m |
| 2026-06-23 | JBU1018 | JFK → BOS | Jun 23, 14:19 UTC | Jun 23, 15:04 UTC | 45m |
| 2026-06-23 | JBU1018 | JFK → BOS | Jun 23, 14:20 UTC | Jun 24, 12:44 UTC | 22h 25m |
| 2026-06-23 | JBU1678 | - | Jun 23, 10:24 UTC | Jun 23, 12:15 UTC | 1h 50m |
| 2026-06-22 | JBU509 | - | Jun 22, 21:35 UTC | Jun 22, 23:55 UTC | 2h 20m |
| 2026-06-22 | JBU1238 | - | Jun 22, 15:40 UTC | Jun 22, 19:24 UTC | 3h 45m |
| 2026-06-21 | JBU639 | BOS → AUS | Jun 21, 18:57 UTC | Jun 22, 18:44 UTC | 23h 48m |
| 2026-06-21 | JBU639 | BOS → AUS | Jun 21, 19:00 UTC | Jun 21, 22:40 UTC | 3h 40m |
| 2026-06-21 | JBU2454 | DCA → BOS | Jun 21, 15:25 UTC | Jun 21, 16:25 UTC | 1h 0m |
| 2026-06-21 | JBU2024 | MCO → DCA | Jun 21, 11:55 UTC | Jun 21, 13:39 UTC | 1h 45m |
| 2026-06-20 | JBU2523 | DCA → MCO | Jun 20, 23:25 UTC | Jun 21, 01:19 UTC | 1h 55m |
| 2026-06-20 | JBU2122 | ACK → HPN | Jun 20, 00:18 UTC | Jun 20, 20:45 UTC | 20h 27m |
| 2026-06-19 | JBU2494 | DCA → ACK | Jun 19, 22:04 UTC | Jun 20, 20:45 UTC | 22h 41m |
| 2026-06-19 | JBU855 | BOS → DCA | Jun 19, 17:29 UTC | Jun 19, 18:54 UTC | 1h 25m |
| 2026-06-19 | JBU855 | BOS → DCA | Jun 19, 17:30 UTC | Jun 20, 16:19 UTC | 22h 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 N3196J page for operator, model, and routing details .