sensors Mode-S transponder
E8021A
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-CXD · BOEING 767-300
- Hex
- E8021A
- Octal
- 72001032
- Decimal
- 15,204,890
- Country
- CL
- Tail
- CC-CXD
- Type
- B763
- Flights observed
- 109
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address E8021A 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 |
|---|---|---|---|
| LAE1801 | - | 6 | 2026-07-11 |
| LCO3606 | LAN Cargo | 5 | 2026-04-24 |
| LAE2525 | - | 5 | 2026-07-06 |
| LAE1807 | - | 5 | 2026-07-02 |
| LAE2536 | - | 4 | 2026-04-13 |
| LAE1828 | LATAM Cargo Colombia | 4 | 2026-05-07 |
| LTG8451 | - | 3 | 2026-07-12 |
| LCO3611 | LAN Cargo | 3 | 2026-05-05 |
| LCO1105 | LAN Cargo | 3 | 2026-04-18 |
| LCO1104 | LAN Cargo | 3 | 2026-04-18 |
| LAE1820 | LATAM Cargo Colombia | 3 | 2026-04-23 |
| LAE1802 | - | 3 | 2026-07-11 |
| LTG9835 | LATAM Cargo Brasil | 2 | 2026-05-03 |
| LTG8513 | - | 2 | 2026-07-09 |
| LTG8460 | - | 2 | 2026-07-12 |
| LTG8430 | - | 2 | 2026-07-09 |
| LNE511 | - | 2 | 2026-07-10 |
| LNE120 | LATAM Airlines Ecuador | 2 | 2026-04-27 |
| LCO3616 | LAN Cargo | 2 | 2026-04-26 |
| LCO1767 | - | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | LAE2801 | - | Jul 13, 20:05 UTC | Jul 13, 20:30 UTC | 25m |
| 2026-07-12 | LTG8460 | - | Jul 12, 20:40 UTC | Jul 13, 12:55 UTC | 16h 15m |
| 2026-07-12 | LTG8451 | - | Jul 12, 16:35 UTC | Jul 12, 17:05 UTC | 30m |
| 2026-07-12 | LTG8451 | - | Jul 12, 14:15 UTC | Jul 12, 14:55 UTC | 40m |
| 2026-07-12 | LTG8451 | - | Jul 12, 05:35 UTC | Jul 12, 12:35 UTC | 7h 0m |
| 2026-07-11 | LAE1802 | - | Jul 11, 22:50 UTC | Jul 12, 01:15 UTC | 2h 25m |
| 2026-07-11 | LAE1801 | GUA → SJO | Jul 11, 19:10 UTC | Jul 11, 20:30 UTC | 1h 20m |
| 2026-07-11 | LAE1801 | - | Jul 11, 17:05 UTC | Jul 11, 17:20 UTC | 15m |
| 2026-07-11 | LAE1801 | - | Jul 11, 15:00 UTC | Jul 11, 16:35 UTC | 1h 35m |
| 2026-07-10 | LNE511 | - | Jul 10, 21:05 UTC | Jul 11, 11:40 UTC | 14h 35m |
| 2026-07-09 | LTG8430 | - | Jul 9, 17:55 UTC | Jul 9, 21:15 UTC | 3h 20m |
| 2026-07-09 | LTG8430 | - | Jul 9, 09:55 UTC | Jul 9, 16:20 UTC | 6h 25m |
| 2026-07-09 | LTG8513 | - | Jul 9, 08:10 UTC | Jul 9, 08:30 UTC | 20m |
| 2026-07-08 | LTG8513 | - | Jul 8, 16:10 UTC | Jul 9, 05:45 UTC | 13h 35m |
| 2026-07-08 | LTG8503 | - | Jul 8, 04:45 UTC | Jul 8, 13:35 UTC | 8h 50m |
| 2026-07-07 | LAE2802 | - | Jul 7, 23:40 UTC | Jul 8, 00:10 UTC | 30m |
| 2026-07-07 | LAE2802 | - | Jul 7, 21:00 UTC | Jul 7, 21:15 UTC | 15m |
| 2026-07-07 | LAE2803 | - | Jul 7, 15:15 UTC | Jul 7, 18:20 UTC | 3h 5m |
| 2026-07-07 | LAE2530 | - | Jul 7, 06:15 UTC | Jul 7, 06:50 UTC | 35m |
| 2026-07-06 | LAE2525 | - | Jul 6, 13:55 UTC | Jul 7, 01:25 UTC | 11h 30m |
| 2026-07-06 | LAE2525 | - | Jul 6, 03:15 UTC | Jul 6, 11:15 UTC | 8h 0m |
| 2026-07-05 | LAE2525 | - | Jul 5, 17:15 UTC | Jul 5, 22:40 UTC | 5h 25m |
| 2026-07-05 | LAE2525 | - | Jul 5, 12:20 UTC | Jul 5, 14:25 UTC | 2h 5m |
| 2026-07-04 | LAE2525 | - | Jul 4, 16:40 UTC | Jul 5, 09:35 UTC | 16h 55m |
| 2026-07-04 | LNE512 | UIO → MIA | Jul 4, 08:40 UTC | Jul 4, 09:10 UTC | 30m |
| 2026-07-03 | LNE511 | - | Jul 3, 14:00 UTC | Jul 3, 22:45 UTC | 8h 45m |
| 2026-07-03 | LAE1809 | - | Jul 3, 08:15 UTC | Jul 3, 08:40 UTC | 25m |
| 2026-07-02 | LAE1807 | - | Jul 2, 18:35 UTC | Jul 2, 22:50 UTC | 4h 15m |
| 2026-05-08 | LCO1767 | - | May 8, 10:59 UTC | May 8, 12:14 UTC | 1h 15m |
| 2026-05-08 | LCO1767 | - | May 8, 08:14 UTC | May 8, 09:49 UTC | 1h 35m |
| 2026-05-07 | LAE1828 | LAX → MIA | May 7, 22:54 UTC | May 8, 06:39 UTC | 7h 45m |
| 2026-05-07 | LAE1828 | LAX → MIA | May 7, 15:20 UTC | May 7, 20:25 UTC | 5h 5m |
| 2026-05-07 | LAE1828 | LAX → MIA | May 7, 09:10 UTC | May 7, 11:30 UTC | 2h 20m |
| 2026-05-06 | LAE1828 | LAX → MIA | May 6, 15:20 UTC | May 7, 07:00 UTC | 15h 39m |
| 2026-05-06 | LAE1806 | BOG → MIA | May 6, 10:35 UTC | May 6, 12:50 UTC | 2h 15m |
| 2026-05-06 | LAE1805 | MIA → BOG | May 6, 07:01 UTC | May 6, 07:35 UTC | 35m |
| 2026-05-05 | LCO3611 | FRA → BRU | May 5, 14:30 UTC | May 6, 03:40 UTC | 13h 10m |
| 2026-05-05 | LCO3611 | FRA → BRU | May 5, 12:10 UTC | May 5, 12:45 UTC | 35m |
| 2026-05-04 | LCO3611 | FRA → BRU | May 4, 18:45 UTC | May 5, 09:00 UTC | 14h 15m |
| 2026-05-04 | LCO3601 | MIA → BRU | May 4, 07:30 UTC | May 4, 15:55 UTC | 8h 25m |
| 2026-05-03 | LCO1618 | UIO → MIA | May 3, 20:05 UTC | May 4, 01:20 UTC | 5h 15m |
| 2026-05-03 | LCO1751 | MIA → SJK | May 3, 11:00 UTC | May 3, 11:20 UTC | 20m |
| 2026-05-03 | LTG9835 | MIA → GRU | May 3, 05:00 UTC | May 3, 05:20 UTC | 20m |
| 2026-05-02 | LTG9835 | MIA → GRU | May 2, 19:20 UTC | May 3, 03:15 UTC | 7h 55m |
| 2026-05-02 | LCO1501 | AMS → MIA | May 2, 04:30 UTC | May 2, 09:45 UTC | 5h 15m |
| 2026-05-01 | LCO1401 | GRU → SCL | May 1, 19:35 UTC | May 1, 20:20 UTC | 45m |
| 2026-05-01 | LTG6550 | GRU → MAO | May 1, 08:20 UTC | May 1, 17:10 UTC | 8h 50m |
| 2026-04-30 | LTG9828 | FLN → CNF | Apr 30, 20:45 UTC | May 1, 05:35 UTC | 8h 50m |
| 2026-04-30 | LCO1614 | - | Apr 30, 17:00 UTC | Apr 30, 18:30 UTC | 1h 30m |
| 2026-04-30 | LCO1607 | ASU → SCL | Apr 30, 00:20 UTC | Apr 30, 07:30 UTC | 7h 10m |
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-CXD page for operator, model, and routing details .