sensors Mode-S transponder
A383F3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3255J · operated by JETBLUE AIRWAYS CORP
- Hex
- A383F3
- Octal
- 50701763
- Decimal
- 10,716,147
- Country
- US
- Tail
- N3255J
- Type
- BCS3
- Flights observed
- 312
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A383F3 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 |
|---|---|---|---|
| JBU899 | JetBlue Airways | 4 | 2026-06-07 |
| JBU845 | - | 4 | 2026-06-21 |
| JBU386 | - | 4 | 2026-07-07 |
| JBU2493 | - | 4 | 2026-07-05 |
| JBU2271 | JetBlue Airways | 4 | 2026-06-07 |
| JBU2055 | JetBlue Airways | 4 | 2026-04-16 |
| JBU1971 | JetBlue Airways | 4 | 2026-05-31 |
| JBU1697 | JetBlue Airways | 4 | 2026-05-04 |
| JBU1003 | JetBlue Airways | 4 | 2026-06-16 |
| JBU803 | - | 3 | 2026-07-10 |
| JBU791 | JetBlue Airways | 3 | 2026-06-25 |
| JBU751 | - | 3 | 2026-06-26 |
| JBU522 | - | 3 | 2026-07-12 |
| JBU501 | JetBlue Airways | 3 | 2026-05-30 |
| JBU471 | JetBlue Airways | 3 | 2026-06-06 |
| JBU2854 | JetBlue Airways | 3 | 2026-05-13 |
| JBU249 | JetBlue Airways | 3 | 2026-04-20 |
| JBU2324 | JetBlue Airways | 3 | 2026-06-13 |
| JBU2285 | - | 3 | 2026-07-02 |
| JBU2272 | JetBlue Airways | 3 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1086 | MCO → BUF | Jul 14, 10:32 UTC | Jul 14, 18:45 UTC | 8h 14m |
| 2026-07-13 | JBU1539 | MVY → JFK | Jul 13, 21:32 UTC | Jul 14, 18:45 UTC | 21h 14m |
| 2026-07-13 | JBU338 | - | Jul 13, 00:55 UTC | Jul 13, 03:25 UTC | 2h 30m |
| 2026-07-13 | JBU338 | MCO → BDL | Jul 13, 00:54 UTC | Jul 13, 22:20 UTC | 21h 27m |
| 2026-07-12 | JBU522 | MCO → MCO | Jul 12, 17:40 UTC | Jul 12, 22:40 UTC | 5h 0m |
| 2026-07-12 | JBU1406 | - | Jul 12, 09:20 UTC | Jul 12, 15:15 UTC | 5h 55m |
| 2026-07-12 | JBU1083 | JFK → MCO | Jul 12, 02:40 UTC | Jul 12, 04:45 UTC | 2h 5m |
| 2026-07-11 | JBU2901 | - | Jul 11, 20:10 UTC | Jul 11, 21:05 UTC | 55m |
| 2026-07-11 | JBU2902 | JFK → BUF | Jul 11, 18:05 UTC | Jul 11, 19:05 UTC | 1h 0m |
| 2026-07-10 | JBU210 | JFK → JFK | Jul 10, 18:55 UTC | Jul 11, 03:05 UTC | 8h 10m |
| 2026-07-10 | JBU1154 | - | Jul 10, 14:55 UTC | Jul 10, 17:05 UTC | 2h 10m |
| 2026-07-10 | JBU803 | - | Jul 10, 01:20 UTC | Jul 10, 01:40 UTC | 20m |
| 2026-07-09 | JBU803 | - | Jul 9, 21:45 UTC | Jul 9, 23:10 UTC | 1h 25m |
| 2026-07-09 | JBU803 | JFK → SJU | Jul 9, 21:45 UTC | Jul 10, 19:40 UTC | 21h 55m |
| 2026-07-09 | JBU704 | SJU → JFK | Jul 9, 16:01 UTC | Jul 10, 12:55 UTC | 20h 55m |
| 2026-07-09 | JBU80 | - | Jul 9, 15:10 UTC | Jul 9, 19:45 UTC | 4h 35m |
| 2026-07-08 | JBU81 | - | Jul 8, 23:10 UTC | Jul 9, 04:35 UTC | 5h 25m |
| 2026-07-08 | JBU206 | BOS → PQI | Jul 8, 03:29 UTC | Jul 9, 02:45 UTC | 23h 17m |
| 2026-07-07 | JBU386 | - | Jul 7, 17:10 UTC | Jul 7, 18:30 UTC | 1h 20m |
| 2026-07-07 | JBU386 | PIT → BOS | Jul 7, 17:05 UTC | Jul 8, 16:00 UTC | 22h 56m |
| 2026-07-07 | JBU385 | - | Jul 7, 14:30 UTC | Jul 7, 15:50 UTC | 1h 20m |
| 2026-07-06 | JBU932 | IAH → BOS | Jul 6, 23:00 UTC | Jul 7, 02:10 UTC | 3h 10m |
| 2026-07-06 | JBU1854 | DCA → BOS | Jul 6, 04:25 UTC | Jul 6, 05:45 UTC | 1h 20m |
| 2026-07-06 | JBU1854 | DCA → BOS | Jul 6, 04:25 UTC | Jul 7, 02:45 UTC | 22h 20m |
| 2026-07-05 | JBU1355 | BOS → DCA | Jul 5, 20:40 UTC | Jul 5, 21:50 UTC | 1h 10m |
| 2026-07-05 | JBU1254 | DCA → BOS | Jul 5, 18:15 UTC | Jul 5, 19:15 UTC | 1h 0m |
| 2026-07-05 | JBU2493 | - | Jul 5, 15:40 UTC | Jul 5, 17:00 UTC | 1h 20m |
| 2026-07-05 | JBU2121 | - | Jul 5, 13:05 UTC | Jul 5, 13:35 UTC | 30m |
| 2026-07-04 | JBU2122 | - | Jul 4, 21:50 UTC | Jul 4, 22:30 UTC | 40m |
| 2026-07-04 | JBU2432 | - | Jul 4, 19:10 UTC | Jul 4, 19:50 UTC | 40m |
| 2026-07-04 | JBU831 | - | Jul 4, 15:55 UTC | Jul 4, 16:50 UTC | 55m |
| 2026-07-03 | JBU2122 | ACK → HPN | Jul 3, 22:15 UTC | Jul 4, 19:50 UTC | 21h 35m |
| 2026-07-03 | JBU2494 | DCA → ACK | Jul 3, 20:00 UTC | Jul 4, 16:55 UTC | 20h 55m |
| 2026-07-03 | JBU855 | BOS → DCA | Jul 3, 17:26 UTC | Jul 4, 16:45 UTC | 23h 19m |
| 2026-07-03 | JBU806 | BNA → BOS | Jul 3, 13:45 UTC | Jul 3, 22:55 UTC | 9h 10m |
| 2026-07-02 | JBU22 | - | Jul 2, 21:55 UTC | Jul 3, 00:30 UTC | 2h 35m |
| 2026-07-02 | JBU22 | PBI → BOS | Jul 2, 21:53 UTC | Jul 3, 20:45 UTC | 22h 52m |
| 2026-07-02 | JBU53 | - | Jul 2, 18:15 UTC | Jul 2, 20:35 UTC | 2h 20m |
| 2026-07-02 | JBU2786 | - | Jul 2, 15:10 UTC | Jul 2, 16:25 UTC | 1h 15m |
| 2026-07-02 | JBU2285 | JFK → RDU | Jul 2, 12:55 UTC | Jul 2, 14:00 UTC | 1h 5m |
| 2026-07-02 | JBU1198 | - | Jul 2, 09:40 UTC | Jul 2, 10:45 UTC | 1h 5m |
| 2026-07-02 | JBU1785 | - | Jul 2, 03:15 UTC | Jul 2, 04:30 UTC | 1h 15m |
| 2026-07-02 | JBU1814 | ORF → BOS | Jul 2, 00:25 UTC | Jul 2, 01:45 UTC | 1h 20m |
| 2026-07-01 | JBU1813 | BOS → ORF | Jul 1, 19:45 UTC | Jul 1, 20:55 UTC | 1h 10m |
| 2026-07-01 | JBU266 | RSW → BOS | Jul 1, 15:20 UTC | Jul 1, 18:05 UTC | 2h 45m |
| 2026-06-30 | JBU391 | BOS → TPA | Jun 30, 20:40 UTC | Jul 1, 18:15 UTC | 21h 36m |
| 2026-06-30 | JBU896 | ATL → BOS | Jun 30, 16:10 UTC | Jul 1, 13:55 UTC | 21h 46m |
| 2026-06-29 | JBU811 | BOS → ORD | Jun 29, 21:59 UTC | Jun 30, 20:40 UTC | 22h 42m |
| 2026-06-29 | JBU837 | BOS → DTW | Jun 29, 16:15 UTC | Jun 29, 17:45 UTC | 1h 30m |
| 2026-06-29 | JBU837 | BOS → DTW | Jun 29, 16:10 UTC | Jun 30, 14:45 UTC | 22h 36m |
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 N3255J page for operator, model, and routing details .