sensors Mode-S transponder
A35FC2
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3162J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A35FC2
- Octal
- 50657702
- Decimal
- 10,706,882
- Country
- US
- Tail
- N3162J
- Type
- BCS3
- Flights observed
- 281
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 20m ago
Current position
Country allocation
The ICAO 24-bit address A35FC2 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 |
|---|---|---|---|
| JBU1231 | - | 7 | 2026-07-11 |
| JBU1786 | JetBlue Airways | 6 | 2026-06-23 |
| JBU1441 | JetBlue Airways | 5 | 2026-05-22 |
| JBU932 | JetBlue Airways | 4 | 2026-06-07 |
| JBU1365 | JetBlue Airways | 4 | 2026-05-09 |
| JBU896 | - | 3 | 2026-07-10 |
| JBU811 | JetBlue Airways | 3 | 2026-05-16 |
| JBU810 | - | 3 | 2026-06-21 |
| JBU726 | JetBlue Airways | 3 | 2026-04-13 |
| JBU68 | JetBlue Airways | 3 | 2026-05-26 |
| JBU678 | - | 3 | 2026-06-27 |
| JBU677 | - | 3 | 2026-06-27 |
| JBU393 | JetBlue Airways | 3 | 2026-05-18 |
| JBU317 | JetBlue Airways | 3 | 2026-05-30 |
| JBU2922 | - | 3 | 2026-06-30 |
| JBU2725 | JetBlue Airways | 3 | 2026-05-09 |
| JBU267 | JetBlue Airways | 3 | 2026-05-26 |
| JBU2587 | JetBlue Airways | 3 | 2026-05-10 |
| JBU2474 | - | 3 | 2026-06-27 |
| JBU2186 | - | 3 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU401 | BOS → MSY | Jul 14, 15:22 UTC | Jul 14, 20:30 UTC | 5h 9m |
| 2026-07-14 | JBU401 | BOS → MSY | Jul 14, 15:25 UTC | Jul 14, 18:20 UTC | 2h 55m |
| 2026-07-14 | JBU638 | AUS → BOS | Jul 14, 01:00 UTC | Jul 14, 05:00 UTC | 4h 0m |
| 2026-07-13 | JBU639 | BOS → AUS | Jul 13, 18:45 UTC | Jul 13, 22:25 UTC | 3h 40m |
| 2026-07-13 | JBU1310 | - | Jul 13, 14:50 UTC | Jul 13, 17:10 UTC | 2h 20m |
| 2026-07-12 | JBU1351 | ACK → BOS | Jul 12, 22:11 UTC | Jul 13, 20:30 UTC | 22h 20m |
| 2026-07-12 | JBU2665 | ACK → HPN | Jul 12, 18:15 UTC | Jul 13, 16:30 UTC | 22h 16m |
| 2026-07-12 | JBU1883 | BOS → RDU | Jul 12, 10:35 UTC | Jul 13, 10:30 UTC | 23h 56m |
| 2026-07-11 | JBU1232 | VRB → BOS | Jul 11, 18:29 UTC | Jul 12, 16:30 UTC | 22h 2m |
| 2026-07-11 | JBU1231 | BOS → VRB | Jul 11, 13:10 UTC | Jul 12, 12:05 UTC | 22h 56m |
| 2026-07-11 | JBU1231 | - | Jul 11, 13:10 UTC | Jul 11, 15:45 UTC | 2h 35m |
| 2026-07-11 | JBU716 | - | Jul 11, 10:10 UTC | Jul 11, 11:05 UTC | 55m |
| 2026-07-11 | JBU715 | BOS → BUF | Jul 11, 03:30 UTC | Jul 11, 04:35 UTC | 1h 5m |
| 2026-07-10 | JBU2468 | - | Jul 10, 23:45 UTC | Jul 11, 01:35 UTC | 1h 50m |
| 2026-07-10 | JBU2467 | - | Jul 10, 19:50 UTC | Jul 10, 21:50 UTC | 2h 0m |
| 2026-07-10 | JBU896 | ATL → BOS | Jul 10, 16:25 UTC | Jul 10, 18:30 UTC | 2h 5m |
| 2026-07-10 | JBU1097 | BOS → ATL | Jul 10, 12:55 UTC | Jul 10, 15:05 UTC | 2h 10m |
| 2026-07-10 | JBU1632 | - | Jul 10, 03:50 UTC | Jul 10, 07:05 UTC | 3h 15m |
| 2026-07-09 | JBU1484 | RDU → BOS | Jul 9, 11:51 UTC | Jul 10, 07:50 UTC | 20h 0m |
| 2026-07-08 | JBU2785 | JFK → RDU | Jul 8, 19:19 UTC | Jul 9, 18:25 UTC | 23h 7m |
| 2026-07-08 | JBU184 | MCO → JFK | Jul 8, 15:21 UTC | Jul 9, 14:30 UTC | 23h 10m |
| 2026-07-08 | JBU737 | BDL → MCO | Jul 8, 11:24 UTC | Jul 9, 02:50 UTC | 15h 26m |
| 2026-07-07 | JBU8427 | EWR → MCO | Jul 7, 18:35 UTC | Jul 7, 20:45 UTC | 2h 10m |
| 2026-07-07 | JBU8427 | EWR → MCO | Jul 7, 18:30 UTC | Jul 8, 16:30 UTC | 22h 1m |
| 2026-07-05 | JBU128 | MCO → EWR | Jul 5, 21:00 UTC | Jul 5, 23:15 UTC | 2h 15m |
| 2026-07-05 | JBU128 | MCO → EWR | Jul 5, 20:55 UTC | Jul 6, 18:50 UTC | 21h 55m |
| 2026-07-05 | JBU934 | - | Jul 5, 17:15 UTC | Jul 5, 18:05 UTC | 50m |
| 2026-07-05 | JBU934 | - | Jul 5, 15:25 UTC | Jul 5, 15:35 UTC | 10m |
| 2026-07-05 | JBU2133 | - | Jul 5, 13:30 UTC | Jul 5, 13:55 UTC | 25m |
| 2026-07-05 | JBU2133 | - | Jul 5, 11:20 UTC | Jul 5, 11:55 UTC | 35m |
| 2026-07-04 | JBU286 | RDU → JFK | Jul 4, 11:03 UTC | Jul 5, 10:30 UTC | 23h 27m |
| 2026-07-04 | JBU2954 | DCA → BOS | Jul 4, 00:10 UTC | Jul 4, 22:30 UTC | 22h 20m |
| 2026-07-03 | JBU2324 | MCO → DCA | Jul 3, 18:23 UTC | Jul 4, 12:15 UTC | 17h 53m |
| 2026-07-03 | JBU1406 | SDQ → MCO | Jul 3, 13:12 UTC | Jul 4, 12:15 UTC | 23h 4m |
| 2026-07-03 | JBU1406 | MCO → MCO | Jul 3, 09:15 UTC | Jul 3, 15:25 UTC | 6h 10m |
| 2026-07-02 | JBU1727 | EWR → MCO | Jul 2, 23:30 UTC | Jul 3, 01:35 UTC | 2h 5m |
| 2026-07-02 | JBU1083 | JFK → MCO | Jul 2, 02:50 UTC | Jul 3, 00:30 UTC | 21h 40m |
| 2026-07-02 | JBU192 | - | Jul 2, 00:15 UTC | Jul 2, 00:50 UTC | 35m |
| 2026-07-02 | JBU192 | ACK → JFK | Jul 2, 00:10 UTC | Jul 2, 21:55 UTC | 21h 45m |
| 2026-07-01 | JBU2291 | - | Jul 1, 22:30 UTC | Jul 1, 23:15 UTC | 45m |
| 2026-07-01 | JBU1716 | - | Jul 1, 18:45 UTC | Jul 1, 20:55 UTC | 2h 10m |
| 2026-06-30 | JBU805 | - | Jun 30, 23:55 UTC | Jul 1, 01:50 UTC | 1h 55m |
| 2026-06-30 | JBU805 | JFK → ORD | Jun 30, 23:55 UTC | Jul 1, 22:30 UTC | 22h 36m |
| 2026-06-30 | JBU2922 | - | Jun 30, 19:05 UTC | Jun 30, 21:05 UTC | 2h 0m |
| 2026-06-30 | JBU121 | - | Jun 30, 14:40 UTC | Jun 30, 17:00 UTC | 2h 20m |
| 2026-06-30 | JBU286 | - | Jun 30, 11:05 UTC | Jun 30, 12:15 UTC | 1h 10m |
| 2026-06-30 | JBU185 | JFK → RDU | Jun 30, 01:40 UTC | Jun 30, 02:45 UTC | 1h 5m |
| 2026-06-29 | JBU2286 | - | Jun 29, 22:24 UTC | Jun 29, 23:39 UTC | 1h 15m |
| 2026-06-29 | JBU2785 | - | Jun 29, 19:24 UTC | Jun 29, 20:30 UTC | 1h 5m |
| 2026-06-29 | JBU1868 | - | Jun 29, 14:39 UTC | Jun 29, 16:44 UTC | 2h 5m |
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 N3162J page for operator, model, and routing details .