sensors Mode-S transponder
E80211
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-CWY · BOEING 767-300
- Hex
- E80211
- Octal
- 72001021
- Decimal
- 15,204,881
- Country
- CL
- Tail
- CC-CWY
- Type
- B763
- Flights observed
- 129
- Distinct callsigns
- 19
- Country
- CL
- Last broadcast
- 19d ago
Last known position
Country allocation
The ICAO 24-bit address E80211 falls within the block assigned to Chile (CL) by ICAO Annex 10, Volume III. Every aircraft registered in Chile 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LPE2694 | LAN Peru | 13 | 2026-06-09 |
| LPE2468 | LAN Peru | 13 | 2026-06-17 |
| LPE2699 | LAN Peru | 12 | 2026-06-10 |
| LPE2482 | LAN Peru | 11 | 2026-06-24 |
| LPE2469 | - | 11 | 2026-06-19 |
| LPE2483 | - | 10 | 2026-06-25 |
| LPE2476 | LAN Peru | 10 | 2026-05-29 |
| LPE2480 | - | 9 | 2026-06-21 |
| LPE2698 | LAN Peru | 7 | 2026-06-22 |
| LPE2477 | LAN Peru | 6 | 2026-05-30 |
| LPE2695 | - | 5 | 2026-06-23 |
| LPE2481 | - | 5 | 2026-06-22 |
| LPE2479 | LAN Peru | 4 | 2026-06-11 |
| LPE2478 | LAN Peru | 4 | 2026-06-11 |
| LPE2693 | LAN Peru | 3 | 2026-05-29 |
| LPE2691 | LAN Peru | 2 | 2026-06-12 |
| LPE2690 | LAN Peru | 2 | 2026-06-07 |
| LPE2387 | LAN Peru | 1 | 2026-05-21 |
| LPE2386 | LAN Peru | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | LPE2483 | - | Jun 25, 05:35 UTC | Jun 25, 08:24 UTC | 2h 50m |
| 2026-06-24 | LPE2482 | LIM → ATL | Jun 24, 23:50 UTC | Jun 25, 03:04 UTC | 3h 15m |
| 2026-06-23 | LPE2695 | - | Jun 23, 21:34 UTC | Jun 23, 23:10 UTC | 1h 35m |
| 2026-06-22 | LPE2698 | LIM → MIA | Jun 22, 22:30 UTC | Jun 23, 19:24 UTC | 20h 55m |
| 2026-06-22 | LPE2481 | - | Jun 22, 21:00 UTC | Jun 23, 19:24 UTC | 22h 25m |
| 2026-06-21 | LPE2480 | - | Jun 21, 21:10 UTC | Jun 22, 11:00 UTC | 13h 50m |
| 2026-06-20 | LPE2695 | - | Jun 20, 21:14 UTC | Jun 21, 10:54 UTC | 13h 40m |
| 2026-06-20 | LPE2698 | LIM → MIA | Jun 20, 04:39 UTC | Jun 20, 18:59 UTC | 14h 20m |
| 2026-06-19 | LPE2469 | - | Jun 19, 04:19 UTC | Jun 20, 00:04 UTC | 19h 45m |
| 2026-06-19 | LPE2469 | - | Jun 19, 04:14 UTC | Jun 20, 00:04 UTC | 19h 50m |
| 2026-06-17 | LPE2468 | LIM → JFK | Jun 17, 18:20 UTC | Jun 18, 13:15 UTC | 18h 55m |
| 2026-06-16 | LPE2468 | LIM → JFK | Jun 16, 21:45 UTC | Jun 17, 12:45 UTC | 15h 0m |
| 2026-06-16 | LPE2698 | LIM → MIA | Jun 16, 13:44 UTC | Jun 16, 18:50 UTC | 5h 5m |
| 2026-06-16 | LPE2469 | - | Jun 16, 04:20 UTC | Jun 16, 11:15 UTC | 6h 55m |
| 2026-06-15 | LPE2468 | LIM → JFK | Jun 15, 05:35 UTC | Jun 15, 12:45 UTC | 7h 10m |
| 2026-06-13 | LPE2481 | MIA → LIM | Jun 13, 21:05 UTC | Jun 14, 02:05 UTC | 5h 0m |
| 2026-06-13 | LPE2480 | - | Jun 13, 05:45 UTC | Jun 13, 10:55 UTC | 5h 10m |
| 2026-06-12 | LPE2691 | JFK → LIM | Jun 12, 18:05 UTC | Jun 13, 01:05 UTC | 7h 0m |
| 2026-06-12 | LPE2468 | LIM → JFK | Jun 12, 06:25 UTC | Jun 12, 13:35 UTC | 7h 10m |
| 2026-06-11 | LPE2479 | LAX → LIM | Jun 11, 18:45 UTC | Jun 12, 02:40 UTC | 7h 56m |
| 2026-06-11 | LPE2478 | LIM → LAX | Jun 11, 06:25 UTC | Jun 11, 14:25 UTC | 8h 0m |
| 2026-06-10 | LPE2699 | MIA → LIM | Jun 10, 04:25 UTC | Jun 10, 09:25 UTC | 5h 0m |
| 2026-06-09 | LPE2694 | LIM → MIA | Jun 9, 19:45 UTC | Jun 10, 00:10 UTC | 4h 25m |
| 2026-06-09 | LPE2699 | MIA → LIM | Jun 9, 04:25 UTC | Jun 9, 09:10 UTC | 4h 45m |
| 2026-06-08 | LPE2694 | LIM → MIA | Jun 8, 19:15 UTC | Jun 9, 00:40 UTC | 5h 25m |
| 2026-06-08 | LPE2469 | JFK → LIM | Jun 8, 04:15 UTC | Jun 8, 11:00 UTC | 6h 45m |
| 2026-06-07 | LPE2690 | LIM → JFK | Jun 7, 17:20 UTC | Jun 8, 00:45 UTC | 7h 25m |
| 2026-06-06 | LPE2479 | LAX → LIM | Jun 6, 20:05 UTC | Jun 7, 03:35 UTC | 7h 30m |
| 2026-06-06 | LPE2478 | LIM → LAX | Jun 6, 06:15 UTC | Jun 6, 14:34 UTC | 8h 20m |
| 2026-06-03 | LPE2699 | MIA → LIM | Jun 3, 04:25 UTC | Jun 3, 06:00 UTC | 1h 35m |
| 2026-06-02 | LPE2694 | LIM → MIA | Jun 2, 23:45 UTC | Jun 3, 00:20 UTC | 35m |
| 2026-06-02 | LPE2694 | LIM → MIA | Jun 2, 18:55 UTC | Jun 2, 21:15 UTC | 2h 20m |
| 2026-06-02 | LPE2699 | MIA → LIM | Jun 2, 04:25 UTC | Jun 2, 09:20 UTC | 4h 55m |
| 2026-06-01 | LPE2694 | LIM → MIA | Jun 1, 19:05 UTC | Jun 2, 00:45 UTC | 5h 40m |
| 2026-06-01 | LPE2699 | MIA → LIM | Jun 1, 04:20 UTC | Jun 1, 09:15 UTC | 4h 55m |
| 2026-05-31 | LPE2694 | LIM → MIA | May 31, 23:40 UTC | Jun 1, 00:00 UTC | 20m |
| 2026-05-31 | LPE2694 | LIM → MIA | May 31, 18:55 UTC | May 31, 22:25 UTC | 3h 30m |
| 2026-05-31 | LPE2483 | ATL → LIM | May 31, 08:40 UTC | May 31, 09:20 UTC | 40m |
| 2026-05-30 | LPE2482 | LIM → ATL | May 30, 17:40 UTC | May 31, 00:05 UTC | 6h 25m |
| 2026-05-30 | LPE2477 | LAX → LIM | May 30, 04:50 UTC | May 30, 12:30 UTC | 7h 40m |
| 2026-05-29 | LPE2476 | LIM → LAX | May 29, 17:40 UTC | May 30, 01:50 UTC | 8h 10m |
| 2026-05-29 | LPE2693 | MIA → LIM | May 29, 05:55 UTC | May 29, 10:50 UTC | 4h 55m |
| 2026-05-28 | LPE2698 | LIM → MIA | May 28, 13:45 UTC | May 28, 18:45 UTC | 5h 0m |
| 2026-05-28 | LPE2699 | MIA → LIM | May 28, 04:20 UTC | May 28, 09:20 UTC | 5h 0m |
| 2026-05-27 | LPE2694 | LIM → MIA | May 27, 19:15 UTC | May 28, 00:25 UTC | 5h 10m |
| 2026-05-26 | LPE2695 | MIA → LIM | May 26, 22:09 UTC | May 27, 03:09 UTC | 5h 0m |
| 2026-05-26 | LPE2698 | LIM → MIA | May 26, 14:30 UTC | May 26, 19:40 UTC | 5h 10m |
| 2026-05-26 | LPE2699 | MIA → LIM | May 26, 04:35 UTC | May 26, 09:35 UTC | 5h 0m |
| 2026-05-25 | LPE2694 | LIM → MIA | May 25, 19:00 UTC | May 26, 00:09 UTC | 5h 9m |
| 2026-05-25 | LPE2483 | ATL → LIM | May 25, 03:35 UTC | May 25, 09:25 UTC | 5h 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 CC-CWY page for operator, model, and routing details .