sensors Mode-S transponder
E8040B
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-CXI · BOEING 767-300
- Hex
- E8040B
- Octal
- 72002013
- Decimal
- 15,205,387
- Country
- CL
- Tail
- CC-CXI
- Type
- B763
- Flights observed
- 113
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address E8040B 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LPE2479 | - | 12 | 2026-06-19 |
| LPE2478 | LAN Peru | 12 | 2026-06-18 |
| LPE2469 | - | 10 | 2026-06-23 |
| LPE2483 | - | 9 | 2026-06-24 |
| LPE2690 | LAN Peru | 8 | 2026-06-15 |
| LPE2482 | LAN Peru | 8 | 2026-06-09 |
| LPE2694 | LAN Peru | 7 | 2026-06-16 |
| LPE2468 | LAN Peru | 7 | 2026-06-21 |
| LPE2481 | - | 6 | 2026-06-14 |
| LPE2480 | - | 6 | 2026-06-14 |
| LPE2477 | LAN Peru | 6 | 2026-06-17 |
| LPE2476 | LAN Peru | 6 | 2026-06-16 |
| LPE2699 | - | 5 | 2026-06-16 |
| LPE2693 | LAN Peru | 2 | 2026-06-12 |
| LPE2691 | - | 2 | 2026-06-21 |
| LPE2412 | LAN Peru | 2 | 2026-06-06 |
| LPE2698 | LAN Peru | 1 | 2026-06-13 |
| LPE2695 | - | 1 | 2026-06-13 |
| LPE2501 | - | 1 | 2026-06-15 |
| LAN1992 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | LPE2483 | - | Jun 24, 03:29 UTC | Jun 24, 06:15 UTC | 2h 45m |
| 2026-06-23 | LPE2469 | - | Jun 23, 04:50 UTC | Jun 24, 00:25 UTC | 19h 35m |
| 2026-06-23 | LPE2469 | JFK → ATL | Jun 23, 04:09 UTC | Jun 24, 00:25 UTC | 20h 15m |
| 2026-06-21 | LPE2468 | LIM → JFK | Jun 21, 18:50 UTC | Jun 22, 12:49 UTC | 18h 0m |
| 2026-06-21 | LPE2691 | JFK → JFK | Jun 21, 18:14 UTC | Jun 22, 12:49 UTC | 18h 35m |
| 2026-06-20 | LPE2468 | LIM → JFK | Jun 20, 22:25 UTC | Jun 21, 15:30 UTC | 17h 5m |
| 2026-06-19 | LPE2479 | - | Jun 19, 19:04 UTC | Jun 20, 10:39 UTC | 15h 35m |
| 2026-06-18 | LPE2478 | LIM → LAX | Jun 18, 18:50 UTC | Jun 19, 14:19 UTC | 19h 29m |
| 2026-06-18 | LPE2478 | LIM → LAX | Jun 18, 10:40 UTC | Jun 18, 14:25 UTC | 3h 45m |
| 2026-06-17 | LPE2477 | LAX → LIM | Jun 17, 04:45 UTC | Jun 17, 05:55 UTC | 1h 10m |
| 2026-06-16 | LPE2476 | LIM → LAX | Jun 16, 17:40 UTC | Jun 17, 01:35 UTC | 7h 56m |
| 2026-06-16 | LPE2699 | - | Jun 16, 10:00 UTC | Jun 16, 14:45 UTC | 4h 45m |
| 2026-06-16 | LPE2694 | LIM → MIA | Jun 16, 01:35 UTC | Jun 16, 06:50 UTC | 5h 15m |
| 2026-06-15 | LPE2501 | - | Jun 15, 15:45 UTC | Jun 15, 20:54 UTC | 5h 10m |
| 2026-06-15 | LPE2690 | LIM → JFK | Jun 15, 05:00 UTC | Jun 15, 12:05 UTC | 7h 5m |
| 2026-06-14 | LPE2481 | - | Jun 14, 21:05 UTC | Jun 15, 02:04 UTC | 4h 59m |
| 2026-06-14 | LPE2480 | - | Jun 14, 05:45 UTC | Jun 14, 10:45 UTC | 5h 0m |
| 2026-06-13 | LPE2695 | - | Jun 13, 21:35 UTC | Jun 14, 02:25 UTC | 4h 50m |
| 2026-06-13 | LPE2698 | LIM → MIA | Jun 13, 13:45 UTC | Jun 13, 18:50 UTC | 5h 5m |
| 2026-06-13 | LPE2699 | - | Jun 13, 04:30 UTC | Jun 13, 09:20 UTC | 4h 50m |
| 2026-06-12 | LPE2694 | LIM → MIA | Jun 12, 18:55 UTC | Jun 13, 00:05 UTC | 5h 10m |
| 2026-06-12 | LPE2693 | MIA → LIM | Jun 12, 05:55 UTC | Jun 12, 10:45 UTC | 4h 50m |
| 2026-06-11 | LPE2694 | LIM → MIA | Jun 11, 19:05 UTC | Jun 12, 00:05 UTC | 5h 0m |
| 2026-06-11 | LPE2469 | JFK → LIM | Jun 11, 04:20 UTC | Jun 11, 11:20 UTC | 7h 0m |
| 2026-06-10 | LPE2690 | LIM → JFK | Jun 10, 17:55 UTC | Jun 11, 01:55 UTC | 8h 0m |
| 2026-06-10 | LPE2483 | ATL → LIM | Jun 10, 03:30 UTC | Jun 10, 09:25 UTC | 5h 55m |
| 2026-06-09 | LPE2482 | LIM → ATL | Jun 9, 19:30 UTC | Jun 10, 00:10 UTC | 4h 40m |
| 2026-06-09 | LPE2469 | JFK → LIM | Jun 9, 04:15 UTC | Jun 9, 11:05 UTC | 6h 50m |
| 2026-06-08 | LPE2468 | LIM → JFK | Jun 8, 05:35 UTC | Jun 8, 13:00 UTC | 7h 25m |
| 2026-06-07 | LPE2481 | MIA → LIM | Jun 7, 21:00 UTC | Jun 8, 01:55 UTC | 4h 55m |
| 2026-06-07 | LPE2480 | LIM → MIA | Jun 7, 05:50 UTC | Jun 7, 11:10 UTC | 5h 20m |
| 2026-06-06 | LPE2412 | LIM → MDE | Jun 6, 22:20 UTC | Jun 6, 22:30 UTC | 10m |
| 2026-06-06 | LPE2477 | LAX → LIM | Jun 6, 04:45 UTC | Jun 6, 12:35 UTC | 7h 50m |
| 2026-06-05 | LPE2476 | LIM → LAX | Jun 5, 17:25 UTC | Jun 6, 01:45 UTC | 8h 20m |
| 2026-06-05 | LPE2693 | MIA → LIM | Jun 5, 05:55 UTC | Jun 5, 10:35 UTC | 4h 40m |
| 2026-06-04 | LPE2694 | LIM → MIA | Jun 4, 19:45 UTC | Jun 5, 00:50 UTC | 5h 5m |
| 2026-06-04 | LPE2469 | JFK → LIM | Jun 4, 04:15 UTC | Jun 4, 11:15 UTC | 7h 0m |
| 2026-06-03 | LPE2690 | LIM → JFK | Jun 3, 07:50 UTC | Jun 4, 01:15 UTC | 17h 25m |
| 2026-06-03 | LPE2690 | LIM → JFK | Jun 3, 04:50 UTC | Jun 4, 01:15 UTC | 20h 25m |
| 2026-06-03 | LPE2690 | LIM → JFK | Jun 3, 04:15 UTC | Jun 4, 01:15 UTC | 21h 0m |
| 2026-06-02 | LPE2468 | LIM → JFK | Jun 2, 05:35 UTC | Jun 2, 12:45 UTC | 7h 10m |
| 2026-06-01 | LPE2479 | LAX → LIM | Jun 1, 18:50 UTC | Jun 2, 02:40 UTC | 7h 50m |
| 2026-06-01 | LPE2478 | LIM → LAX | Jun 1, 06:50 UTC | Jun 1, 14:50 UTC | 8h 0m |
| 2026-05-31 | LPE2479 | LAX → LIM | May 31, 19:00 UTC | Jun 1, 02:45 UTC | 7h 45m |
| 2026-05-31 | LPE2478 | LIM → LAX | May 31, 10:40 UTC | May 31, 14:30 UTC | 3h 50m |
| 2026-05-30 | LPE2469 | JFK → LIM | May 30, 04:15 UTC | May 30, 11:15 UTC | 7h 0m |
| 2026-05-29 | LPE2690 | LIM → JFK | May 29, 17:55 UTC | May 30, 01:25 UTC | 7h 30m |
| 2026-05-29 | LPE2699 | MIA → LIM | May 29, 04:30 UTC | May 29, 09:25 UTC | 4h 55m |
| 2026-05-28 | LPE2694 | LIM → MIA | May 28, 18:50 UTC | May 29, 00:05 UTC | 5h 15m |
| 2026-05-28 | LPE2469 | JFK → LIM | May 28, 04:15 UTC | May 28, 11:20 UTC | 7h 5m |
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-CXI page for operator, model, and routing details .