- Flights observed
- 117
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A1E411 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 |
|---|---|---|---|
| JBU724 | JetBlue Airways | 5 | 2026-05-17 |
| JBU1216 | JetBlue Airways | 5 | 2026-05-20 |
| JBU1080 | JetBlue Airways | 5 | 2026-05-28 |
| JBU923 | JetBlue Airways | 4 | 2026-05-02 |
| JBU616 | JetBlue Airways | 4 | 2026-05-15 |
| JBU511 | - | 4 | 2026-04-17 |
| JBU487 | JetBlue Airways | 4 | 2026-04-16 |
| JBU348 | JetBlue Airways | 4 | 2026-05-15 |
| JBU324 | JetBlue Airways | 4 | 2026-04-17 |
| JBU1734 | JetBlue Airways | 4 | 2026-04-28 |
| JBU1515 | JetBlue Airways | 4 | 2026-05-20 |
| JBU133 | JetBlue Airways | 4 | 2026-04-28 |
| JBU354 | JetBlue Airways | 3 | 2026-05-29 |
| JBU223 | JetBlue Airways | 3 | 2026-04-23 |
| JBU1633 | JetBlue Airways | 3 | 2026-05-25 |
| JBU15 | JetBlue Airways | 3 | 2026-05-21 |
| JBU123 | JetBlue Airways | 3 | 2026-05-17 |
| JBU1190 | JetBlue Airways | 3 | 2026-05-20 |
| JBU1189 | JetBlue Airways | 3 | 2026-05-19 |
| JBU115 | JetBlue Airways | 3 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | JBU1488 | LAX → BOS | May 30, 03:33 UTC | May 30, 08:40 UTC | 5h 8m |
| 2026-05-29 | JBU354 | ONT → JFK | May 29, 09:44 UTC | May 30, 08:15 UTC | 22h 32m |
| 2026-05-29 | JBU354 | ONT → JFK | May 29, 09:44 UTC | May 30, 08:15 UTC | 22h 32m |
| 2026-05-29 | JBU353 | JFK → BUR | May 29, 01:15 UTC | May 29, 07:10 UTC | 5h 55m |
| 2026-05-28 | JBU1080 | EDI → BOS | May 28, 10:45 UTC | May 28, 16:15 UTC | 5h 30m |
| 2026-05-28 | JBU1080 | EDI → BOS | May 28, 10:41 UTC | May 29, 10:15 UTC | 23h 34m |
| 2026-05-28 | JBU73 | JFK → BNA | May 28, 01:50 UTC | May 28, 08:25 UTC | 6h 35m |
| 2026-05-27 | JBU72 | SLC → JFK | May 27, 11:50 UTC | May 27, 18:50 UTC | 7h 0m |
| 2026-05-27 | JBU1079 | JFK → MBJ | May 27, 03:09 UTC | May 27, 09:15 UTC | 6h 5m |
| 2026-05-26 | JBU687 | BOS → LAX | May 26, 11:44 UTC | May 26, 17:15 UTC | 5h 30m |
| 2026-05-26 | JBU687 | BOS → LAX | May 26, 11:43 UTC | May 27, 09:25 UTC | 21h 43m |
| 2026-05-25 | JBU1634 | JFK → BTV | May 25, 22:44 UTC | May 26, 03:40 UTC | 4h 55m |
| 2026-05-25 | JBU1633 | BTV → JFK | May 25, 15:05 UTC | May 25, 20:59 UTC | 5h 54m |
| 2026-05-25 | JBU488 | MCO → ORH | May 25, 05:35 UTC | May 25, 10:40 UTC | 5h 5m |
| 2026-05-24 | JBU1926 | LGW → BOS | May 24, 11:46 UTC | May 25, 10:15 UTC | 22h 30m |
| 2026-05-24 | JBU1926 | LGW → BOS | May 24, 11:46 UTC | May 25, 10:15 UTC | 22h 30m |
| 2026-05-24 | JBU2104 | BOS → LGW | May 24, 02:10 UTC | May 24, 08:25 UTC | 6h 15m |
| 2026-05-23 | JBU807 | BOS → SAV | May 23, 12:52 UTC | May 24, 12:15 UTC | 23h 24m |
| 2026-05-22 | JBU823 | JFK → LAX | May 22, 22:04 UTC | May 23, 19:55 UTC | 21h 51m |
| 2026-05-22 | JBU823 | JFK → LAX | May 22, 22:05 UTC | May 23, 03:35 UTC | 5h 29m |
| 2026-05-22 | JBU1079 | JFK → MBJ | May 22, 03:13 UTC | May 23, 02:15 UTC | 23h 3m |
| 2026-05-22 | JBU1079 | JFK → MBJ | May 22, 03:15 UTC | May 22, 04:30 UTC | 1h 15m |
| 2026-05-21 | JBU834 | SFO → BOS | May 21, 19:50 UTC | May 22, 00:55 UTC | 5h 5m |
| 2026-05-21 | JBU15 | JFK → SFO | May 21, 11:50 UTC | May 21, 17:40 UTC | 5h 50m |
| 2026-05-20 | JBU1216 | PUJ → EWR | May 20, 23:40 UTC | May 21, 04:40 UTC | 5h 0m |
| 2026-05-20 | JBU1515 | JFK → SFO | May 20, 12:20 UTC | May 20, 18:30 UTC | 6h 10m |
| 2026-05-20 | JBU1190 | SAN → JFK | May 20, 04:25 UTC | May 20, 09:00 UTC | 4h 36m |
| 2026-05-19 | JBU1189 | JFK → SAN | May 19, 21:35 UTC | May 20, 02:55 UTC | 5h 20m |
| 2026-05-19 | JBU842 | DUB → JFK | May 19, 10:50 UTC | May 19, 17:35 UTC | 6h 45m |
| 2026-05-19 | JBU841 | JFK → SAV | May 19, 01:50 UTC | May 19, 08:05 UTC | 6h 15m |
| 2026-05-18 | JBU224 | LAX → JFK | May 18, 14:25 UTC | May 18, 19:20 UTC | 4h 54m |
| 2026-05-17 | JBU724 | STI → BOS | May 17, 18:15 UTC | May 17, 23:00 UTC | 4h 45m |
| 2026-05-17 | JBU724 | STI → BOS | May 17, 18:10 UTC | May 18, 16:15 UTC | 22h 6m |
| 2026-05-17 | JBU123 | JFK → LAX | May 17, 10:50 UTC | May 17, 16:20 UTC | 5h 30m |
| 2026-05-16 | JBU1457 | JFK → AUA | May 16, 15:35 UTC | May 16, 19:50 UTC | 4h 15m |
| 2026-05-16 | JBU1457 | JFK → AUA | May 16, 15:32 UTC | May 17, 14:15 UTC | 22h 44m |
| 2026-05-15 | JBU348 | LAS → JFK | May 15, 20:00 UTC | May 16, 00:30 UTC | 4h 30m |
| 2026-05-15 | JBU616 | SFO → JFK | May 15, 05:45 UTC | May 15, 10:50 UTC | 5h 5m |
| 2026-05-15 | JBU616 | SFO → JFK | May 15, 05:42 UTC | May 16, 00:40 UTC | 18h 58m |
| 2026-05-14 | JBU354 | ONT → JFK | May 14, 10:04 UTC | May 15, 08:15 UTC | 22h 12m |
| 2026-05-14 | JBU353 | JFK → BUR | May 14, 01:15 UTC | May 15, 00:15 UTC | 23h 1m |
| 2026-05-13 | JBU1080 | EDI → BOS | May 13, 10:34 UTC | May 14, 10:15 UTC | 23h 42m |
| 2026-05-13 | JBU1080 | EDI → BOS | May 13, 10:35 UTC | May 13, 17:15 UTC | 6h 40m |
| 2026-05-13 | JBU73 | JFK → BNA | May 13, 01:45 UTC | May 13, 08:10 UTC | 6h 25m |
| 2026-05-12 | JBU724 | STI → BOS | May 12, 17:55 UTC | May 12, 22:55 UTC | 5h 0m |
| 2026-05-12 | JBU123 | JFK → LAX | May 12, 10:25 UTC | May 12, 15:50 UTC | 5h 25m |
| 2026-05-12 | JBU1216 | PUJ → EWR | May 12, 02:45 UTC | May 12, 03:00 UTC | 15m |
| 2026-05-11 | JBU1216 | PUJ → EWR | May 11, 22:10 UTC | May 11, 22:35 UTC | 24m |
| 2026-05-11 | JBU1515 | JFK → SFO | May 11, 12:15 UTC | May 11, 18:10 UTC | 5h 55m |
| 2026-05-11 | JBU1190 | SAN → JFK | May 11, 04:30 UTC | May 11, 09:20 UTC | 4h 50m |
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 N2205J page for operator, model, and routing details .