sensors Mode-S transponder
ADE609
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N995JL · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- ADE609
- Octal
- 53363011
- Decimal
- 11,396,617
- Country
- US
- Tail
- N995JL
- Type
- A321
- Flights observed
- 270
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address ADE609 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 |
|---|---|---|---|
| JBU803 | JetBlue Airways | 7 | 2026-05-31 |
| JBU771 | JetBlue Airways | 7 | 2026-06-07 |
| JBU1323 | JetBlue Airways | 6 | 2026-05-14 |
| JBU772 | JetBlue Airways | 5 | 2026-06-07 |
| JBU474 | - | 5 | 2026-07-10 |
| JBU453 | JetBlue Airways | 5 | 2026-05-16 |
| JBU21 | JetBlue Airways | 5 | 2026-05-26 |
| JBU904 | JetBlue Airways | 4 | 2026-06-11 |
| JBU791 | JetBlue Airways | 4 | 2026-06-01 |
| JBU373 | JetBlue Airways | 4 | 2026-06-25 |
| JBU321 | JetBlue Airways | 4 | 2026-04-27 |
| JBU2851 | JetBlue Airways | 4 | 2026-06-01 |
| JBU255 | - | 4 | 2026-07-09 |
| JBU171 | JetBlue Airways | 4 | 2026-04-13 |
| JBU1604 | - | 4 | 2026-06-29 |
| JBU1603 | - | 4 | 2026-06-28 |
| JBU1347 | - | 4 | 2026-06-29 |
| JBU1254 | JetBlue Airways | 4 | 2026-04-24 |
| JBU1192 | JetBlue Airways | 4 | 2026-05-30 |
| JBU8371 | JetBlue Airways | 3 | 2026-06-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU585 | JFK → RDU | Jul 14, 00:41 UTC | Jul 14, 16:05 UTC | 15h 25m |
| 2026-07-13 | JBU1682 | UVF → JFK | Jul 13, 17:58 UTC | Jul 14, 16:05 UTC | 22h 8m |
| 2026-07-13 | JBU1681 | - | Jul 13, 12:05 UTC | Jul 13, 15:10 UTC | 3h 5m |
| 2026-07-12 | JBU1691 | JFK → JFK | Jul 12, 13:30 UTC | Jul 13, 01:25 UTC | 11h 55m |
| 2026-07-11 | JBU168 | PUJ → JFK | Jul 11, 17:03 UTC | Jul 12, 16:01 UTC | 22h 58m |
| 2026-07-11 | JBU1936 | STI → JFK | Jul 11, 04:24 UTC | Jul 12, 04:01 UTC | 23h 37m |
| 2026-07-10 | JBU1159 | - | Jul 10, 12:05 UTC | Jul 10, 13:00 UTC | 55m |
| 2026-07-10 | JBU1159 | BOS → PHL | Jul 10, 12:03 UTC | Jul 11, 07:25 UTC | 19h 23m |
| 2026-07-10 | JBU474 | - | Jul 10, 00:50 UTC | Jul 10, 04:35 UTC | 3h 45m |
| 2026-07-10 | JBU474 | - | Jul 10, 00:00 UTC | Jul 10, 00:15 UTC | 15m |
| 2026-07-09 | JBU255 | - | Jul 9, 15:35 UTC | Jul 9, 23:00 UTC | 7h 25m |
| 2026-07-08 | JBU1533 | JFK → CTG | Jul 8, 13:59 UTC | Jul 9, 00:25 UTC | 10h 26m |
| 2026-07-08 | JBU1059 | JFK → KIN | Jul 8, 02:38 UTC | Jul 9, 00:25 UTC | 21h 47m |
| 2026-07-07 | JBU662 | BGI → JFK | Jul 7, 18:45 UTC | Jul 8, 16:25 UTC | 21h 40m |
| 2026-07-07 | JBU361 | - | Jul 7, 16:55 UTC | Jul 7, 17:10 UTC | 15m |
| 2026-07-07 | JBU361 | - | Jul 7, 12:15 UTC | Jul 7, 16:15 UTC | 4h 0m |
| 2026-07-07 | JBU361 | JFK → BGI | Jul 7, 12:13 UTC | Jul 8, 10:15 UTC | 22h 3m |
| 2026-07-06 | JBU1457 | - | Jul 6, 22:10 UTC | Jul 6, 22:25 UTC | 15m |
| 2026-07-06 | JBU1457 | JFK → AUA | Jul 6, 18:12 UTC | Jul 7, 16:15 UTC | 22h 3m |
| 2026-07-06 | JBU1457 | - | Jul 6, 18:15 UTC | Jul 6, 19:00 UTC | 45m |
| 2026-07-06 | JBU536 | JFK → JFK | Jul 6, 06:10 UTC | Jul 6, 15:00 UTC | 8h 50m |
| 2026-07-05 | JBU279 | JFK → MBJ | Jul 5, 13:53 UTC | Jul 6, 06:45 UTC | 16h 52m |
| 2026-07-05 | JBU636 | STI → JFK | Jul 5, 02:50 UTC | Jul 6, 02:15 UTC | 23h 25m |
| 2026-07-04 | JBU1830 | SDQ → BOS | Jul 4, 10:15 UTC | Jul 5, 06:30 UTC | 20h 15m |
| 2026-07-03 | JBU9 | JFK → SDQ | Jul 3, 21:04 UTC | Jul 4, 18:25 UTC | 21h 21m |
| 2026-07-03 | JBU1436 | STI → JFK | Jul 3, 15:12 UTC | Jul 4, 14:15 UTC | 23h 4m |
| 2026-07-03 | JBU1436 | JFK → JFK | Jul 3, 10:15 UTC | Jul 3, 18:30 UTC | 8h 15m |
| 2026-07-02 | JBU1691 | JFK → LIR | Jul 2, 13:53 UTC | Jul 3, 11:00 UTC | 21h 8m |
| 2026-07-02 | JBU160 | KIN → JFK | Jul 2, 07:35 UTC | Jul 3, 01:00 UTC | 17h 25m |
| 2026-07-01 | JBU151 | JFK → CUN | Jul 1, 13:02 UTC | Jul 2, 11:05 UTC | 22h 3m |
| 2026-07-01 | JBU937 | - | Jul 1, 02:00 UTC | Jul 1, 02:25 UTC | 25m |
| 2026-07-01 | JBU937 | JFK → STI | Jul 1, 02:00 UTC | Jul 1, 21:55 UTC | 19h 56m |
| 2026-06-30 | JBU627 | JFK → POP | Jun 30, 14:40 UTC | Jun 30, 23:05 UTC | 8h 25m |
| 2026-06-30 | JBU355 | JFK → ONT | Jun 30, 00:43 UTC | Jun 30, 23:05 UTC | 22h 23m |
| 2026-06-29 | JBU1604 | - | Jun 29, 18:49 UTC | Jun 29, 22:15 UTC | 3h 25m |
| 2026-06-29 | JBU1604 | SJU → JFK | Jun 29, 18:46 UTC | Jun 30, 15:50 UTC | 21h 5m |
| 2026-06-29 | JBU1347 | - | Jun 29, 17:05 UTC | Jun 29, 17:19 UTC | 15m |
| 2026-06-29 | JBU1347 | - | Jun 29, 13:30 UTC | Jun 29, 15:30 UTC | 2h 0m |
| 2026-06-28 | JBU2831 | - | Jun 28, 18:05 UTC | Jun 28, 18:14 UTC | 10m |
| 2026-06-28 | JBU1603 | - | Jun 28, 16:00 UTC | Jun 28, 16:19 UTC | 20m |
| 2026-06-28 | JBU1603 | - | Jun 28, 13:04 UTC | Jun 28, 13:34 UTC | 30m |
| 2026-06-28 | JBU1603 | JFK → SJU | Jun 28, 13:03 UTC | Jun 29, 10:40 UTC | 21h 37m |
| 2026-06-28 | JBU636 | - | Jun 28, 00:15 UTC | Jun 28, 08:25 UTC | 8h 10m |
| 2026-06-27 | JBU2023 | BOS → BOS | Jun 27, 23:00 UTC | Jun 27, 23:04 UTC | 5m |
| 2026-06-27 | JBU2023 | - | Jun 27, 15:10 UTC | Jun 27, 16:20 UTC | 1h 10m |
| 2026-06-27 | JBU385 | BOS → PIT | Jun 27, 12:15 UTC | Jun 27, 13:40 UTC | 1h 25m |
| 2026-06-26 | JBU398 | SEA → BOS | Jun 26, 21:55 UTC | Jun 27, 02:39 UTC | 4h 45m |
| 2026-06-26 | JBU397 | BOS → SEA | Jun 26, 11:34 UTC | Jun 26, 17:35 UTC | 6h 0m |
| 2026-06-25 | JBU474 | - | Jun 25, 21:10 UTC | Jun 26, 01:05 UTC | 3h 55m |
| 2026-06-25 | JBU474 | - | Jun 25, 20:25 UTC | Jun 25, 20:39 UTC | 15m |
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 N995JL page for operator, model, and routing details .