sensors Mode-S transponder
A874E1
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N644JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A874E1
- Octal
- 52072341
- Decimal
- 11,039,969
- Country
- US
- Tail
- N644JB
- Type
- A320
- Flights observed
- 233
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address A874E1 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 |
|---|---|---|---|
| JBU403 | - | 7 | 2026-07-12 |
| JBU1833 | JetBlue Airways | 4 | 2026-04-18 |
| JBU1457 | JetBlue Airways | 4 | 2026-05-08 |
| JBU891 | - | 3 | 2026-06-26 |
| JBU87 | JetBlue Airways | 3 | 2026-06-01 |
| JBU499 | JetBlue Airways | 3 | 2026-05-25 |
| JBU198 | JetBlue Airways | 3 | 2026-06-19 |
| JBU197 | JetBlue Airways | 3 | 2026-06-19 |
| JBU1434 | JetBlue Airways | 3 | 2026-06-20 |
| JBU1366 | - | 3 | 2026-06-26 |
| JBU1168 | - | 3 | 2026-06-21 |
| JBU1129 | - | 3 | 2026-07-11 |
| JBU919 | - | 2 | 2026-06-27 |
| JBU9 | JetBlue Airways | 2 | 2026-05-09 |
| JBU88 | JetBlue Airways | 2 | 2026-06-01 |
| JBU83 | - | 2 | 2026-07-02 |
| JBU772 | - | 2 | 2026-06-24 |
| JBU768 | JetBlue Airways | 2 | 2026-05-07 |
| JBU690 | - | 2 | 2026-07-01 |
| JBU688 | JetBlue Airways | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | JBU193 | - | Jul 17, 03:39 UTC | Jul 17, 04:35 UTC | 55m |
| 2026-07-17 | JBU193 | EWR → STI | Jul 17, 03:38 UTC | Jul 17, 21:10 UTC | 17h 32m |
| 2026-07-16 | JBU106 | - | Jul 16, 22:55 UTC | Jul 17, 01:15 UTC | 2h 20m |
| 2026-07-16 | JBU2925 | - | Jul 16, 18:05 UTC | Jul 16, 19:55 UTC | 1h 50m |
| 2026-07-16 | JBU2926 | - | Jul 16, 15:05 UTC | Jul 16, 16:44 UTC | 1h 40m |
| 2026-07-16 | JBU513 | - | Jul 16, 10:10 UTC | Jul 16, 12:34 UTC | 2h 25m |
| 2026-07-15 | JBU1698 | FLL → ATL | Jul 15, 16:31 UTC | Jul 16, 16:15 UTC | 23h 44m |
| 2026-07-15 | JBU1471 | LGA → FLL | Jul 15, 12:05 UTC | Jul 15, 14:25 UTC | 2h 20m |
| 2026-07-14 | JBU367 | - | Jul 14, 18:45 UTC | Jul 14, 20:55 UTC | 2h 10m |
| 2026-07-14 | JBU367 | - | Jul 14, 18:41 UTC | Jul 15, 18:05 UTC | 23h 24m |
| 2026-07-14 | JBU1552 | RSW → HPN | Jul 14, 14:30 UTC | Jul 14, 17:15 UTC | 2h 45m |
| 2026-07-14 | JBU1551 | - | Jul 14, 10:40 UTC | Jul 14, 13:05 UTC | 2h 25m |
| 2026-07-13 | JBU1461 | LGA → PBI | Jul 13, 11:30 UTC | Jul 13, 13:45 UTC | 2h 15m |
| 2026-07-13 | JBU1461 | - | Jul 13, 11:28 UTC | Jul 14, 01:25 UTC | 13h 58m |
| 2026-07-12 | JBU2154 | - | Jul 12, 13:55 UTC | Jul 12, 14:10 UTC | 15m |
| 2026-07-12 | JBU403 | - | Jul 12, 12:20 UTC | Jul 12, 12:45 UTC | 25m |
| 2026-07-12 | JBU403 | - | Jul 12, 10:10 UTC | Jul 12, 10:20 UTC | 10m |
| 2026-07-12 | JBU403 | - | Jul 12, 09:30 UTC | Jul 12, 10:05 UTC | 35m |
| 2026-07-12 | JBU403 | JFK → SJU | Jul 12, 09:27 UTC | Jul 13, 01:25 UTC | 15h 59m |
| 2026-07-11 | JBU939 | JFK → SJD | Jul 11, 13:30 UTC | Jul 12, 10:20 UTC | 20h 51m |
| 2026-07-11 | JBU1129 | - | Jul 11, 10:10 UTC | Jul 11, 10:40 UTC | 30m |
| 2026-07-11 | JBU1129 | PVD → JFK | Jul 11, 10:05 UTC | Jul 12, 01:00 UTC | 14h 56m |
| 2026-07-10 | JBU1196 | - | Jul 10, 23:10 UTC | Jul 11, 01:40 UTC | 2h 30m |
| 2026-07-10 | JBU1775 | FLL → KIN | Jul 10, 03:24 UTC | Jul 11, 01:40 UTC | 22h 17m |
| 2026-07-09 | JBU1675 | FLL → KIN | Jul 9, 14:30 UTC | Jul 10, 13:45 UTC | 23h 15m |
| 2026-07-08 | JBU126 | TPA → JFK | Jul 8, 10:32 UTC | Jul 9, 03:55 UTC | 17h 24m |
| 2026-07-08 | JBU1905 | FLL → TPA | Jul 8, 00:44 UTC | Jul 9, 00:10 UTC | 23h 27m |
| 2026-07-07 | JBU1703 | - | Jul 7, 13:55 UTC | Jul 7, 14:10 UTC | 15m |
| 2026-07-07 | JBU1703 | SJU → MDE | Jul 7, 13:52 UTC | Jul 8, 12:15 UTC | 22h 23m |
| 2026-07-07 | JBU275 | BDL → SJU | Jul 7, 01:15 UTC | Jul 7, 04:40 UTC | 3h 25m |
| 2026-07-06 | JBU438 | MCO → BDL | Jul 6, 21:25 UTC | Jul 6, 23:45 UTC | 2h 20m |
| 2026-07-06 | JBU1778 | MCO → MCO | Jul 6, 12:25 UTC | Jul 6, 18:30 UTC | 6h 5m |
| 2026-07-05 | JBU1130 | - | Jul 5, 20:50 UTC | Jul 5, 22:05 UTC | 1h 15m |
| 2026-07-05 | JBU1130 | FLL → CHS | Jul 5, 20:49 UTC | Jul 6, 20:15 UTC | 23h 27m |
| 2026-07-05 | JBU1371 | LGA → FLL | Jul 5, 16:20 UTC | Jul 5, 18:45 UTC | 2h 25m |
| 2026-07-05 | JBU1062 | - | Jul 5, 12:05 UTC | Jul 5, 14:20 UTC | 2h 15m |
| 2026-07-05 | JBU2334 | - | Jul 5, 01:45 UTC | Jul 5, 05:25 UTC | 3h 40m |
| 2026-07-04 | JBU2433 | DCA → PBI | Jul 4, 11:55 UTC | Jul 4, 13:55 UTC | 2h 0m |
| 2026-07-03 | JBU2424 | - | Jul 3, 21:55 UTC | Jul 3, 23:35 UTC | 1h 40m |
| 2026-07-03 | JBU2251 | BOS → MCO | Jul 3, 17:55 UTC | Jul 3, 20:30 UTC | 2h 35m |
| 2026-07-03 | JBU862 | - | Jul 3, 12:45 UTC | Jul 3, 16:25 UTC | 3h 40m |
| 2026-07-02 | JBU83 | JFK → MCO | Jul 2, 16:32 UTC | Jul 3, 16:15 UTC | 23h 44m |
| 2026-07-02 | JBU1901 | BUF → JFK | Jul 2, 13:23 UTC | Jul 3, 08:35 UTC | 19h 13m |
| 2026-07-02 | JBU491 | BUF → LAX | Jul 2, 00:50 UTC | Jul 2, 22:40 UTC | 21h 50m |
| 2026-07-01 | JBU690 | FLL → BOS | Jul 1, 10:40 UTC | Jul 2, 10:15 UTC | 23h 35m |
| 2026-06-30 | JBU2420 | - | Jun 30, 16:55 UTC | Jun 30, 20:15 UTC | 3h 20m |
| 2026-06-30 | JBU2420 | AUA → EWR | Jun 30, 16:50 UTC | Jul 1, 16:15 UTC | 23h 26m |
| 2026-06-30 | JBU2219 | - | Jun 30, 14:50 UTC | Jun 30, 15:05 UTC | 15m |
| 2026-06-30 | JBU2219 | - | Jun 30, 10:55 UTC | Jun 30, 14:10 UTC | 3h 15m |
| 2026-06-29 | JBU2332 | PUJ → SJU | Jun 29, 17:31 UTC | Jun 30, 15:05 UTC | 21h 35m |
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 N644JB page for operator, model, and routing details .