sensors Mode-S transponder
A3311B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3044J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A3311B
- Octal
- 50630433
- Decimal
- 10,694,939
- Country
- US
- Tail
- N3044J
- Type
- BCS3
- Flights observed
- 308
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 33m ago
Last known position
Country allocation
The ICAO 24-bit address A3311B 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 |
|---|---|---|---|
| JBU163 | JetBlue Airways | 5 | 2026-05-14 |
| JBU934 | - | 4 | 2026-07-12 |
| JBU896 | - | 4 | 2026-06-19 |
| JBU818 | JetBlue Airways | 4 | 2026-06-17 |
| JBU360 | JetBlue Airways | 4 | 2026-05-17 |
| JBU2625 | JetBlue Airways | 4 | 2026-05-25 |
| JBU2459 | - | 4 | 2026-07-04 |
| JBU1851 | JetBlue Airways | 4 | 2026-06-03 |
| JBU183 | - | 4 | 2026-07-11 |
| JBU128 | - | 4 | 2026-07-13 |
| JBU1273 | JetBlue Airways | 4 | 2026-06-10 |
| JBU855 | JetBlue Airways | 3 | 2026-04-18 |
| JBU72 | JetBlue Airways | 3 | 2026-04-14 |
| JBU560 | JetBlue Airways | 3 | 2026-07-05 |
| JBU2626 | JetBlue Airways | 3 | 2026-05-27 |
| JBU2474 | JetBlue Airways | 3 | 2026-05-14 |
| JBU2133 | - | 3 | 2026-07-12 |
| JBU2032 | JetBlue Airways | 3 | 2026-05-28 |
| JBU1852 | JetBlue Airways | 3 | 2026-06-04 |
| JBU184 | - | 3 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU128 | MCO → EWR | Jul 13, 19:50 UTC | Jul 14, 06:45 UTC | 10h 56m |
| 2026-07-13 | JBU1923 | DCA → MCO | Jul 13, 16:33 UTC | Jul 14, 06:45 UTC | 14h 13m |
| 2026-07-13 | JBU229 | BQN → MCO | Jul 13, 00:35 UTC | Jul 13, 22:10 UTC | 21h 36m |
| 2026-07-12 | JBU229 | MCO → MCO | Jul 12, 20:10 UTC | Jul 13, 03:05 UTC | 6h 55m |
| 2026-07-12 | JBU730 | - | Jul 12, 16:05 UTC | Jul 12, 17:01 UTC | 55m |
| 2026-07-12 | JBU934 | - | Jul 12, 14:25 UTC | Jul 12, 14:40 UTC | 15m |
| 2026-07-12 | JBU2133 | - | Jul 12, 12:50 UTC | Jul 12, 13:10 UTC | 20m |
| 2026-07-12 | JBU1043 | - | Jul 12, 10:35 UTC | Jul 12, 11:10 UTC | 35m |
| 2026-07-11 | JBU1043 | - | Jul 11, 19:10 UTC | Jul 11, 21:30 UTC | 2h 20m |
| 2026-07-11 | JBU1042 | - | Jul 11, 15:40 UTC | Jul 11, 17:50 UTC | 2h 10m |
| 2026-07-11 | JBU183 | JFK → ORL | Jul 11, 11:55 UTC | Jul 11, 14:10 UTC | 2h 15m |
| 2026-07-10 | JBU8415 | MCO → VRB | Jul 10, 16:59 UTC | Jul 11, 16:45 UTC | 23h 47m |
| 2026-07-10 | JBU8416 | - | Jul 10, 17:00 UTC | Jul 10, 17:20 UTC | 20m |
| 2026-07-09 | JBU8416 | VRB → MCO | Jul 9, 18:38 UTC | Jul 10, 16:45 UTC | 22h 7m |
| 2026-07-09 | JBU1206 | ORD → JFK | Jul 9, 11:18 UTC | Jul 9, 19:20 UTC | 8h 2m |
| 2026-07-08 | JBU237 | JFK → STI | Jul 8, 15:00 UTC | Jul 9, 13:05 UTC | 22h 5m |
| 2026-07-08 | JBU1206 | ORD → JFK | Jul 8, 11:20 UTC | Jul 8, 13:05 UTC | 1h 45m |
| 2026-07-08 | JBU1206 | ORD → JFK | Jul 8, 11:18 UTC | Jul 9, 09:55 UTC | 22h 37m |
| 2026-07-07 | JBU805 | JFK → ORD | Jul 7, 23:30 UTC | Jul 8, 01:30 UTC | 2h 0m |
| 2026-07-06 | JBU59 | JFK → JFK | Jul 6, 09:35 UTC | Jul 6, 18:50 UTC | 9h 15m |
| 2026-07-05 | JBU1382 | IAH → JFK | Jul 5, 17:08 UTC | Jul 6, 16:45 UTC | 23h 37m |
| 2026-07-05 | JBU560 | PHL → BOS | Jul 5, 01:02 UTC | Jul 5, 20:30 UTC | 19h 29m |
| 2026-07-05 | JBU560 | PHL → BOS | Jul 5, 01:05 UTC | Jul 5, 02:10 UTC | 1h 5m |
| 2026-07-04 | JBU2459 | - | Jul 4, 22:35 UTC | Jul 4, 23:30 UTC | 55m |
| 2026-07-04 | JBU1500 | - | Jul 4, 18:45 UTC | Jul 4, 21:10 UTC | 2h 25m |
| 2026-07-03 | JBU2459 | BOS → PHL | Jul 3, 23:37 UTC | Jul 4, 22:45 UTC | 23h 9m |
| 2026-07-03 | JBU165 | - | Jul 3, 15:00 UTC | Jul 3, 17:45 UTC | 2h 45m |
| 2026-07-03 | JBU165 | BOS → RSW | Jul 3, 14:58 UTC | Jul 4, 14:45 UTC | 23h 48m |
| 2026-07-03 | JBU96 | PDX → BOS | Jul 3, 07:35 UTC | Jul 3, 13:00 UTC | 5h 25m |
| 2026-07-03 | JBU95 | - | Jul 3, 00:40 UTC | Jul 3, 06:15 UTC | 5h 35m |
| 2026-07-02 | JBU1336 | DTW → BOS | Jul 2, 21:40 UTC | Jul 2, 23:15 UTC | 1h 35m |
| 2026-07-02 | JBU837 | BOS → DTW | Jul 2, 19:05 UTC | Jul 2, 20:35 UTC | 1h 30m |
| 2026-07-02 | JBU150 | - | Jul 2, 14:45 UTC | Jul 2, 16:45 UTC | 2h 0m |
| 2026-07-01 | JBU625 | JFK → TPA | Jul 1, 19:15 UTC | Jul 2, 18:40 UTC | 23h 25m |
| 2026-07-01 | JBU184 | MCO → JFK | Jul 1, 15:20 UTC | Jul 1, 17:35 UTC | 2h 15m |
| 2026-07-01 | JBU184 | MCO → JFK | Jul 1, 15:18 UTC | Jul 2, 14:45 UTC | 23h 27m |
| 2026-07-01 | JBU737 | BDL → MCO | Jul 1, 11:30 UTC | Jul 1, 13:55 UTC | 2h 25m |
| 2026-07-01 | JBU338 | MCO → BDL | Jul 1, 01:30 UTC | Jul 1, 03:55 UTC | 2h 25m |
| 2026-06-30 | JBU2134 | - | Jun 30, 22:20 UTC | Jun 30, 23:20 UTC | 1h 0m |
| 2026-06-30 | JBU2134 | - | Jun 30, 20:35 UTC | Jun 30, 20:50 UTC | 15m |
| 2026-06-30 | JBU1033 | - | Jun 30, 18:50 UTC | Jun 30, 19:10 UTC | 20m |
| 2026-06-30 | JBU1033 | - | Jun 30, 16:35 UTC | Jun 30, 17:10 UTC | 35m |
| 2026-06-30 | JBU183 | BOS → RDU | Jun 30, 12:40 UTC | Jun 30, 14:40 UTC | 2h 0m |
| 2026-06-29 | JBU26 | TPA → JFK | Jun 29, 23:49 UTC | Jun 30, 02:20 UTC | 2h 31m |
| 2026-06-29 | JBU625 | - | Jun 29, 19:54 UTC | Jun 29, 22:30 UTC | 2h 35m |
| 2026-06-29 | JBU92 | - | Jun 29, 16:29 UTC | Jun 29, 17:05 UTC | 35m |
| 2026-06-29 | JBU2091 | - | Jun 29, 14:50 UTC | Jun 29, 15:24 UTC | 35m |
| 2026-06-28 | JBU184 | MCO → JFK | Jun 28, 15:11 UTC | Jun 29, 14:44 UTC | 23h 34m |
| 2026-06-27 | JBU522 | MBJ → MCO | Jun 27, 21:13 UTC | Jun 28, 20:45 UTC | 23h 32m |
| 2026-06-27 | JBU2265 | MCO → STI | Jun 27, 09:33 UTC | Jun 28, 05:09 UTC | 19h 37m |
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 N3044J page for operator, model, and routing details .