sensors Mode-S transponder
A33CA9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3077J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A33CA9
- Octal
- 50636251
- Decimal
- 10,697,897
- Country
- US
- Tail
- N3077J
- Type
- BCS3
- Flights observed
- 213
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A33CA9 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 |
|---|---|---|---|
| JBU2523 | JetBlue Airways | 4 | 2026-06-15 |
| JBU2324 | - | 4 | 2026-06-21 |
| JBU855 | - | 3 | 2026-06-24 |
| JBU817 | - | 3 | 2026-06-30 |
| JBU72 | - | 3 | 2026-04-13 |
| JBU71 | JetBlue Airways | 3 | 2026-04-13 |
| JBU678 | - | 3 | 2026-04-13 |
| JBU2602 | JetBlue Airways | 3 | 2026-06-13 |
| JBU2467 | - | 3 | 2026-07-04 |
| JBU2184 | JetBlue Airways | 3 | 2026-06-26 |
| JBU163 | JetBlue Airways | 3 | 2026-05-18 |
| JBU1414 | - | 3 | 2026-07-04 |
| JBU130 | JetBlue Airways | 3 | 2026-06-05 |
| JBU125 | - | 3 | 2026-07-09 |
| JBU1198 | - | 3 | 2026-07-12 |
| JBU1044 | - | 3 | 2026-06-14 |
| JBU97 | JetBlue Airways | 2 | 2026-06-07 |
| JBU932 | JetBlue Airways | 2 | 2026-06-18 |
| JBU8564 | JetBlue Airways | 2 | 2026-05-07 |
| JBU8452 | JetBlue Airways | 2 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1273 | JFK → JFK | Jul 13, 12:15 UTC | Jul 13, 12:45 UTC | 30m |
| 2026-07-12 | JBU1198 | PIT → JFK | Jul 12, 10:32 UTC | Jul 13, 02:30 UTC | 15h 59m |
| 2026-07-11 | JBU2786 | - | Jul 11, 15:20 UTC | Jul 11, 16:25 UTC | 1h 5m |
| 2026-07-11 | JBU2786 | RDU → JFK | Jul 11, 15:19 UTC | Jul 12, 14:15 UTC | 22h 57m |
| 2026-07-11 | JBU2285 | JFK → RDU | Jul 11, 13:05 UTC | Jul 11, 14:15 UTC | 1h 10m |
| 2026-07-11 | JBU359 | BUR → JFK | Jul 11, 05:05 UTC | Jul 11, 09:55 UTC | 4h 50m |
| 2026-07-10 | JBU358 | JFK → BUR | Jul 10, 22:20 UTC | Jul 11, 03:45 UTC | 5h 25m |
| 2026-07-10 | JBU626 | TPA → JFK | Jul 10, 13:35 UTC | Jul 10, 15:50 UTC | 2h 15m |
| 2026-07-09 | JBU125 | - | Jul 9, 16:55 UTC | Jul 9, 19:15 UTC | 2h 20m |
| 2026-07-09 | JBU626 | TPA → JFK | Jul 9, 13:20 UTC | Jul 9, 15:30 UTC | 2h 10m |
| 2026-07-08 | JBU125 | JFK → TPA | Jul 8, 17:25 UTC | Jul 8, 19:50 UTC | 2h 25m |
| 2026-07-08 | JBU125 | JFK → TPA | Jul 8, 17:25 UTC | Jul 9, 14:15 UTC | 20h 50m |
| 2026-07-06 | JBU142 | SAV → JFK | Jul 6, 16:22 UTC | Jul 6, 19:00 UTC | 2h 39m |
| 2026-07-06 | JBU993 | BOS → DEN | Jul 6, 01:23 UTC | Jul 6, 19:00 UTC | 17h 38m |
| 2026-07-05 | JBU2666 | HPN → ACK | Jul 5, 21:10 UTC | Jul 6, 19:00 UTC | 21h 51m |
| 2026-07-05 | JBU2665 | ACK → HPN | Jul 5, 18:34 UTC | Jul 6, 18:15 UTC | 23h 41m |
| 2026-07-05 | JBU1883 | BOS → RDU | Jul 5, 10:39 UTC | Jul 6, 10:15 UTC | 23h 37m |
| 2026-07-04 | JBU2467 | - | Jul 4, 19:55 UTC | Jul 4, 21:55 UTC | 2h 0m |
| 2026-07-04 | JBU2467 | BOS → CHS | Jul 4, 19:55 UTC | Jul 5, 17:15 UTC | 21h 20m |
| 2026-07-04 | JBU266 | RSW → BOS | Jul 4, 15:20 UTC | Jul 4, 18:05 UTC | 2h 45m |
| 2026-07-04 | JBU1414 | BOS → RSW | Jul 4, 11:00 UTC | Jul 4, 13:55 UTC | 2h 55m |
| 2026-07-03 | JBU1414 | DCA → BOS | Jul 3, 20:45 UTC | Jul 3, 21:50 UTC | 1h 5m |
| 2026-07-02 | JBU36 | STI → JFK | Jul 2, 19:09 UTC | Jul 3, 12:45 UTC | 17h 36m |
| 2026-07-02 | JBU237 | - | Jul 2, 14:40 UTC | Jul 2, 22:25 UTC | 7h 45m |
| 2026-07-01 | JBU210 | JFK → JFK | Jul 1, 19:05 UTC | Jul 2, 03:40 UTC | 8h 35m |
| 2026-06-30 | JBU817 | BOS → JFK | Jun 30, 23:54 UTC | Jul 1, 19:30 UTC | 19h 37m |
| 2026-06-30 | JBU818 | JFK → BOS | Jun 30, 21:48 UTC | Jul 1, 19:30 UTC | 21h 43m |
| 2026-06-30 | JBU1018 | JFK → BOS | Jun 30, 14:20 UTC | Jun 30, 15:05 UTC | 45m |
| 2026-06-30 | JBU1018 | JFK → BOS | Jun 30, 14:15 UTC | Jul 1, 09:00 UTC | 18h 46m |
| 2026-06-29 | JBU817 | - | Jun 29, 23:44 UTC | Jun 30, 00:25 UTC | 40m |
| 2026-06-29 | JBU1500 | - | Jun 29, 19:15 UTC | Jun 29, 21:44 UTC | 2h 30m |
| 2026-06-28 | JBU509 | BOS → JAX | Jun 28, 23:03 UTC | Jun 29, 22:15 UTC | 23h 12m |
| 2026-06-28 | JBU494 | - | Jun 28, 17:50 UTC | Jun 28, 21:30 UTC | 3h 40m |
| 2026-06-28 | JBU494 | DEN → BOS | Jun 28, 17:47 UTC | Jun 29, 16:15 UTC | 22h 28m |
| 2026-06-28 | JBU493 | BOS → DEN | Jun 28, 12:09 UTC | Jun 28, 16:14 UTC | 4h 5m |
| 2026-06-26 | JBU2185 | BOS → PIT | Jun 26, 21:54 UTC | Jun 27, 14:49 UTC | 16h 56m |
| 2026-06-26 | JBU2184 | RDU → BOS | Jun 26, 18:37 UTC | Jun 27, 14:49 UTC | 20h 13m |
| 2026-06-26 | JBU554 | DCA → BOS | Jun 26, 13:07 UTC | Jun 27, 11:59 UTC | 22h 53m |
| 2026-06-26 | JBU560 | PHL → BOS | Jun 26, 01:34 UTC | Jun 26, 23:19 UTC | 21h 46m |
| 2026-06-25 | JBU2493 | ACK → DCA | Jun 25, 18:37 UTC | Jun 26, 17:25 UTC | 22h 48m |
| 2026-06-25 | JBU2121 | - | Jun 25, 12:54 UTC | Jun 25, 13:35 UTC | 40m |
| 2026-06-25 | JBU2121 | HPN → ACK | Jun 25, 12:54 UTC | Jun 26, 11:55 UTC | 23h 1m |
| 2026-06-24 | JBU2122 | - | Jun 24, 22:10 UTC | Jun 24, 22:49 UTC | 40m |
| 2026-06-24 | JBU2494 | DCA → ACK | Jun 24, 20:09 UTC | Jun 24, 21:09 UTC | 1h 0m |
| 2026-06-24 | JBU855 | BOS → DCA | Jun 24, 17:14 UTC | Jun 24, 18:34 UTC | 1h 20m |
| 2026-06-24 | JBU855 | BOS → BOS | Jun 24, 16:50 UTC | Jun 24, 16:54 UTC | 5m |
| 2026-06-24 | JBU2066 | BOS → BOS | Jun 24, 15:54 UTC | Jun 24, 15:59 UTC | 5m |
| 2026-06-23 | JBU896 | ATL → BOS | Jun 23, 17:43 UTC | Jun 24, 08:30 UTC | 14h 47m |
| 2026-06-23 | JBU1097 | BOS → ATL | Jun 23, 12:42 UTC | Jun 24, 08:30 UTC | 19h 48m |
| 2026-06-23 | JBU1097 | BOS → ATL | Jun 23, 12:45 UTC | Jun 23, 15:15 UTC | 2h 30m |
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 N3077J page for operator, model, and routing details .