sensors Mode-S transponder
A3549D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3132J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A3549D
- Octal
- 50652235
- Decimal
- 10,704,029
- Country
- US
- Tail
- N3132J
- Type
- BCS3
- Flights observed
- 307
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A3549D 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 |
|---|---|---|---|
| JBU2876 | JetBlue Airways | 5 | 2026-04-16 |
| JBU927 | JetBlue Airways | 4 | 2026-04-16 |
| JBU828 | JetBlue Airways | 4 | 2026-04-15 |
| JBU2602 | - | 4 | 2026-06-30 |
| JBU204 | JetBlue Airways | 4 | 2026-04-30 |
| JBU1875 | JetBlue Airways | 4 | 2026-04-16 |
| JBU143 | JetBlue Airways | 4 | 2026-06-05 |
| JBU1055 | - | 4 | 2026-06-24 |
| JBU918 | JetBlue Airways | 3 | 2026-05-02 |
| JBU811 | - | 3 | 2026-06-22 |
| JBU506 | JetBlue Airways | 3 | 2026-06-24 |
| JBU366 | - | 3 | 2026-04-13 |
| JBU2549 | JetBlue Airways | 3 | 2026-05-18 |
| JBU2448 | JetBlue Airways | 3 | 2026-05-18 |
| JBU2432 | JetBlue Airways | 3 | 2026-06-04 |
| JBU2285 | - | 3 | 2026-06-28 |
| JBU2265 | - | 3 | 2026-07-13 |
| JBU2230 | JetBlue Airways | 3 | 2026-05-12 |
| JBU2144 | JetBlue Airways | 3 | 2026-06-05 |
| JBU209 | JetBlue Airways | 3 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU1096 | BOS → BOS | Jul 15, 01:35 UTC | Jul 15, 01:45 UTC | 10m |
| 2026-07-14 | JBU1096 | - | Jul 14, 23:20 UTC | Jul 15, 01:30 UTC | 2h 10m |
| 2026-07-14 | JBU419 | JFK → ATL | Jul 14, 19:40 UTC | Jul 14, 21:35 UTC | 1h 55m |
| 2026-07-14 | JBU184 | MCO → JFK | Jul 14, 15:35 UTC | Jul 14, 18:00 UTC | 2h 25m |
| 2026-07-14 | JBU737 | - | Jul 14, 11:30 UTC | Jul 14, 13:45 UTC | 2h 15m |
| 2026-07-13 | JBU2265 | MCO → STI | Jul 13, 09:34 UTC | Jul 14, 03:15 UTC | 17h 42m |
| 2026-07-12 | JBU1955 | BOS → DCA | Jul 12, 21:48 UTC | Jul 13, 18:35 UTC | 20h 48m |
| 2026-07-12 | JBU1231 | BOS → VRB | Jul 12, 12:45 UTC | Jul 13, 10:15 UTC | 21h 31m |
| 2026-07-12 | JBU516 | BUF → BOS | Jul 12, 03:47 UTC | Jul 13, 02:45 UTC | 22h 59m |
| 2026-07-11 | JBU2251 | BOS → MCO | Jul 11, 18:03 UTC | Jul 12, 17:15 UTC | 23h 13m |
| 2026-07-11 | JBU1207 | BOS → BNA | Jul 11, 10:44 UTC | Jul 12, 07:50 UTC | 21h 7m |
| 2026-07-10 | JBU1596 | PUJ → BOS | Jul 10, 23:22 UTC | Jul 11, 22:20 UTC | 22h 59m |
| 2026-07-10 | JBU741 | JFK → SAV | Jul 10, 10:35 UTC | Jul 10, 12:15 UTC | 1h 40m |
| 2026-07-10 | JBU741 | JFK → SAV | Jul 10, 10:35 UTC | Jul 11, 03:05 UTC | 16h 31m |
| 2026-07-10 | JBU26 | TPA → JFK | Jul 10, 00:45 UTC | Jul 10, 03:15 UTC | 2h 30m |
| 2026-07-09 | JBU625 | JFK → TPA | Jul 9, 20:35 UTC | Jul 9, 23:00 UTC | 2h 25m |
| 2026-07-09 | JBU8449 | - | Jul 9, 17:30 UTC | Jul 9, 18:45 UTC | 1h 15m |
| 2026-07-08 | JBU1195 | - | Jul 8, 04:50 UTC | Jul 8, 05:45 UTC | 55m |
| 2026-07-07 | JBU1498 | DEN → JFK | Jul 7, 20:50 UTC | Jul 8, 00:15 UTC | 3h 25m |
| 2026-07-07 | JBU1497 | JFK → DEN | Jul 7, 14:55 UTC | Jul 7, 18:30 UTC | 3h 35m |
| 2026-07-07 | JBU854 | - | Jul 7, 11:05 UTC | Jul 7, 13:10 UTC | 2h 5m |
| 2026-07-05 | JBU1814 | ORF → BOS | Jul 5, 23:35 UTC | Jul 6, 00:45 UTC | 1h 10m |
| 2026-07-05 | JBU1814 | ORF → BOS | Jul 5, 23:31 UTC | Jul 6, 17:00 UTC | 17h 30m |
| 2026-07-05 | JBU1813 | - | Jul 5, 21:20 UTC | Jul 5, 22:30 UTC | 1h 10m |
| 2026-07-05 | JBU1813 | BOS → BOS | Jul 5, 12:40 UTC | Jul 5, 18:15 UTC | 5h 35m |
| 2026-07-04 | JBU8364 | DCA → BOS | Jul 4, 22:50 UTC | Jul 5, 01:55 UTC | 3h 5m |
| 2026-07-04 | JBU8364 | DCA → BOS | Jul 4, 21:57 UTC | Jul 5, 21:15 UTC | 23h 18m |
| 2026-07-02 | JBU521 | MCO → MBJ | Jul 2, 17:41 UTC | Jul 2, 18:35 UTC | 54m |
| 2026-07-02 | JBU2266 | STI → MCO | Jul 2, 12:58 UTC | Jul 2, 18:35 UTC | 5h 37m |
| 2026-07-01 | JBU1355 | - | Jul 1, 20:10 UTC | Jul 1, 21:20 UTC | 1h 10m |
| 2026-07-01 | JBU1355 | BOS → DCA | Jul 1, 20:08 UTC | Jul 2, 18:35 UTC | 22h 27m |
| 2026-07-01 | JBU1254 | - | Jul 1, 17:40 UTC | Jul 1, 18:40 UTC | 1h 0m |
| 2026-07-01 | JBU2493 | - | Jul 1, 15:00 UTC | Jul 1, 16:10 UTC | 1h 10m |
| 2026-06-30 | JBU2602 | - | Jun 30, 23:40 UTC | Jul 1, 01:10 UTC | 1h 30m |
| 2026-06-30 | JBU2602 | - | Jun 30, 21:15 UTC | Jun 30, 21:25 UTC | 10m |
| 2026-06-30 | JBU2602 | SJU → HPN | Jun 30, 21:10 UTC | Jul 1, 19:15 UTC | 22h 6m |
| 2026-06-30 | JBU1047 | - | Jun 30, 19:25 UTC | Jun 30, 19:50 UTC | 25m |
| 2026-06-30 | JBU1047 | - | Jun 30, 16:15 UTC | Jun 30, 17:20 UTC | 1h 5m |
| 2026-06-30 | JBU1048 | - | Jun 30, 14:00 UTC | Jun 30, 14:45 UTC | 45m |
| 2026-06-30 | JBU1048 | - | Jun 30, 11:15 UTC | Jun 30, 11:30 UTC | 15m |
| 2026-06-30 | JBU751 | - | Jun 30, 03:50 UTC | Jun 30, 04:05 UTC | 15m |
| 2026-06-30 | JBU751 | - | Jun 30, 01:25 UTC | Jun 30, 02:20 UTC | 56m |
| 2026-06-29 | JBU533 | BDL → TPA | Jun 29, 21:19 UTC | Jun 29, 23:54 UTC | 2h 35m |
| 2026-06-29 | JBU534 | TPA → BDL | Jun 29, 17:30 UTC | Jun 29, 20:00 UTC | 2h 30m |
| 2026-06-28 | JBU406 | ORD → JFK | Jun 28, 23:34 UTC | Jun 29, 23:14 UTC | 23h 41m |
| 2026-06-28 | JBU2285 | JFK → RDU | Jun 28, 14:08 UTC | Jun 29, 13:14 UTC | 23h 7m |
| 2026-06-28 | JBU1195 | JFK → PIT | Jun 28, 03:01 UTC | Jun 29, 01:14 UTC | 22h 14m |
| 2026-06-27 | JBU192 | - | Jun 27, 20:44 UTC | Jun 27, 21:15 UTC | 30m |
| 2026-06-27 | JBU192 | ACK → JFK | Jun 27, 20:38 UTC | Jun 28, 17:50 UTC | 21h 12m |
| 2026-06-27 | JBU2291 | - | Jun 27, 18:29 UTC | Jun 27, 19:09 UTC | 40m |
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 N3132J page for operator, model, and routing details .