sensors Mode-S transponder
E8040F
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BBB · BOEING 787-8 Dreamliner
- Hex
- E8040F
- Octal
- 72002017
- Decimal
- 15,205,391
- Country
- CL
- Tail
- CC-BBB
- Type
- B788
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 23d ago
Last known position
Country allocation
The ICAO 24-bit address E8040F 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 |
|---|---|---|---|
| LAN543 | LAN Airlines | 8 | 2026-04-29 |
| LAN542 | LAN Airlines | 5 | 2026-04-28 |
| LAN539 | LAN Airlines | 5 | 2026-04-16 |
| LAN710 | LAN Airlines | 4 | 2026-04-17 |
| LAN538 | LAN Airlines | 4 | 2026-04-16 |
| LAN711 | LAN Airlines | 3 | 2026-04-17 |
| LAN592 | LAN Airlines | 3 | 2026-04-17 |
| LAN500 | LAN Airlines | 3 | 2026-05-03 |
| LAN706 | LAN Airlines | 2 | 2026-05-06 |
| LAN603 | LAN Airlines | 2 | 2026-04-27 |
| LAN602 | LAN Airlines | 2 | 2026-04-27 |
| LAN583 | LAN Airlines | 2 | 2026-05-03 |
| LAN535 | LAN Airlines | 2 | 2026-04-14 |
| LAN533 | LAN Airlines | 2 | 2026-05-05 |
| LAN532 | LAN Airlines | 2 | 2026-05-04 |
| LPE2696 | LAN Peru | 1 | 2026-04-18 |
| LPE2485 | LAN Peru | 1 | 2026-04-19 |
| LPE2484 | LAN Peru | 1 | 2026-04-19 |
| LAN841 | LAN Airlines | 1 | 2026-04-23 |
| LAN705 | LAN Airlines | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-06 | LAN706 | SCL → MAD | May 6, 00:46 UTC | May 6, 10:45 UTC | 10h 0m |
| 2026-05-05 | LAN533 | JFK → SCL | May 5, 00:30 UTC | May 5, 07:35 UTC | 7h 5m |
| 2026-05-04 | LAN532 | SCL → JFK | May 4, 06:15 UTC | May 4, 13:10 UTC | 6h 55m |
| 2026-05-03 | LAN583 | CUN → SCL | May 3, 17:50 UTC | May 3, 22:20 UTC | 4h 30m |
| 2026-05-03 | LAN583 | CUN → SCL | May 3, 14:10 UTC | May 3, 15:35 UTC | 1h 25m |
| 2026-05-03 | LAN500 | SCL → MIA | May 3, 10:50 UTC | May 3, 11:10 UTC | 20m |
| 2026-05-03 | LAN500 | SCL → MIA | May 3, 06:15 UTC | May 3, 09:40 UTC | 3h 25m |
| 2026-05-02 | LAN591 | PUJ → SCL | May 2, 14:00 UTC | May 2, 21:30 UTC | 7h 30m |
| 2026-05-02 | LAN500 | SCL → MIA | May 2, 06:25 UTC | May 2, 11:25 UTC | 5h 0m |
| 2026-04-30 | LAN705 | MAD → SCL | Apr 30, 22:30 UTC | May 1, 09:35 UTC | 11h 5m |
| 2026-04-30 | LAN706 | SCL → MAD | Apr 30, 01:05 UTC | Apr 30, 11:25 UTC | 10h 20m |
| 2026-04-29 | LAN543 | EZE → SCL | Apr 29, 15:35 UTC | Apr 29, 16:00 UTC | 25m |
| 2026-04-29 | LAN543 | EZE → SCL | Apr 29, 04:15 UTC | Apr 29, 12:40 UTC | 8h 26m |
| 2026-04-28 | LAN542 | EZE → MIA | Apr 28, 16:25 UTC | Apr 29, 00:54 UTC | 8h 30m |
| 2026-04-28 | LAN542 | EZE → MIA | Apr 28, 13:45 UTC | Apr 28, 14:15 UTC | 30m |
| 2026-04-27 | LAN603 | LAX → SCL | Apr 27, 23:10 UTC | Apr 28, 02:10 UTC | 3h 0m |
| 2026-04-27 | LAN602 | SCL → LAX | Apr 27, 13:30 UTC | Apr 27, 14:50 UTC | 1h 20m |
| 2026-04-26 | LAN543 | EZE → SCL | Apr 26, 15:30 UTC | Apr 26, 16:00 UTC | 30m |
| 2026-04-26 | LAN543 | EZE → SCL | Apr 26, 04:10 UTC | Apr 26, 12:30 UTC | 8h 20m |
| 2026-04-25 | LAN542 | EZE → MIA | Apr 25, 16:20 UTC | Apr 26, 00:50 UTC | 8h 30m |
| 2026-04-25 | LAN542 | EZE → MIA | Apr 25, 13:45 UTC | Apr 25, 14:20 UTC | 35m |
| 2026-04-25 | LAN542 | EZE → MIA | Apr 25, 12:55 UTC | Apr 25, 13:05 UTC | 10m |
| 2026-04-25 | LAN533 | JFK → SCL | Apr 25, 00:10 UTC | Apr 25, 06:35 UTC | 6h 25m |
| 2026-04-24 | LAN532 | SCL → JFK | Apr 24, 06:35 UTC | Apr 24, 13:15 UTC | 6h 40m |
| 2026-04-23 | LAN841 | SCL → IPC | Apr 23, 13:10 UTC | Apr 23, 13:20 UTC | 10m |
| 2026-04-22 | LAN603 | LAX → SCL | Apr 22, 23:00 UTC | Apr 23, 02:10 UTC | 3h 10m |
| 2026-04-22 | LAN602 | SCL → LAX | Apr 22, 11:45 UTC | Apr 22, 15:20 UTC | 3h 35m |
| 2026-04-19 | LPE2485 | MAD → LIM | Apr 19, 23:55 UTC | Apr 20, 10:20 UTC | 10h 25m |
| 2026-04-19 | LPE2484 | LIM → MAD | Apr 19, 05:35 UTC | Apr 19, 15:05 UTC | 9h 30m |
| 2026-04-18 | LPE2696 | SCL → LIM | Apr 18, 21:15 UTC | Apr 18, 21:25 UTC | 10m |
| 2026-04-18 | LAN543 | EZE → SCL | Apr 18, 15:30 UTC | Apr 18, 15:55 UTC | 25m |
| 2026-04-18 | LAN543 | EZE → SCL | Apr 18, 08:00 UTC | Apr 18, 08:30 UTC | 30m |
| 2026-04-18 | LAN543 | EZE → SCL | Apr 18, 05:30 UTC | Apr 18, 05:40 UTC | 10m |
| 2026-04-18 | LAN543 | EZE → SCL | Apr 18, 04:10 UTC | Apr 18, 12:20 UTC | 8h 10m |
| 2026-04-17 | LAN592 | SCL → PUJ | Apr 17, 23:40 UTC | Apr 18, 00:05 UTC | 25m |
| 2026-04-17 | LAN592 | SCL → PUJ | Apr 17, 17:55 UTC | Apr 17, 19:20 UTC | 1h 25m |
| 2026-04-17 | LAN592 | SCL → PUJ | Apr 17, 16:00 UTC | Apr 17, 16:50 UTC | 50m |
| 2026-04-17 | LAN711 | BOG → SCL | Apr 17, 06:00 UTC | Apr 17, 06:50 UTC | 50m |
| 2026-04-17 | LAN711 | BOG → SCL | Apr 17, 04:30 UTC | Apr 17, 04:45 UTC | 16m |
| 2026-04-17 | LAN710 | SCL → BOG | Apr 17, 01:40 UTC | Apr 17, 02:10 UTC | 30m |
| 2026-04-17 | LAN710 | SCL → BOG | Apr 17, 00:05 UTC | Apr 17, 00:30 UTC | 25m |
| 2026-04-16 | LAN539 | JFK → LIM | Apr 16, 11:09 UTC | Apr 16, 11:20 UTC | 10m |
| 2026-04-16 | LAN539 | JFK → LIM | Apr 16, 10:34 UTC | Apr 16, 11:04 UTC | 30m |
| 2026-04-16 | LAN539 | JFK → LIM | Apr 16, 07:09 UTC | Apr 16, 08:19 UTC | 1h 10m |
| 2026-04-16 | LAN539 | JFK → LIM | Apr 16, 05:09 UTC | Apr 16, 07:05 UTC | 1h 55m |
| 2026-04-16 | LAN539 | JFK → LIM | Apr 16, 04:54 UTC | Apr 16, 05:05 UTC | 10m |
| 2026-04-16 | LAN538 | LIM → JFK | Apr 16, 01:10 UTC | Apr 16, 01:20 UTC | 10m |
| 2026-04-15 | LAN538 | LIM → JFK | Apr 15, 23:10 UTC | Apr 16, 01:05 UTC | 1h 55m |
| 2026-04-15 | LAN538 | LIM → JFK | Apr 15, 21:25 UTC | Apr 15, 23:00 UTC | 1h 35m |
| 2026-04-15 | LAN538 | LIM → JFK | Apr 15, 18:10 UTC | Apr 15, 19:00 UTC | 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-BBB page for operator, model, and routing details .