sensors Mode-S transponder
E80422
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BDC · BOEING 767-300
- Hex
- E80422
- Octal
- 72002042
- Decimal
- 15,205,410
- Country
- CL
- Tail
- CC-BDC
- Type
- B763
- Flights observed
- 246
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address E80422 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 |
|---|---|---|---|
| LCO3613 | LAN Cargo | 14 | 2026-06-11 |
| LCO3617 | - | 9 | 2026-07-13 |
| LCO1506 | LAN Cargo | 8 | 2026-06-11 |
| LCO3603 | - | 7 | 2026-07-14 |
| LAE2525 | LATAM Cargo Colombia | 7 | 2026-06-22 |
| LAE1812 | LATAM Cargo Colombia | 7 | 2026-05-24 |
| LCO1105 | - | 6 | 2026-06-27 |
| LAE1828 | LATAM Cargo Colombia | 6 | 2026-06-19 |
| LNE117 | - | 5 | 2026-05-04 |
| LCO1511 | LAN Cargo | 5 | 2026-05-12 |
| LAE2512 | LATAM Cargo Colombia | 5 | 2026-06-08 |
| LAE1811 | - | 5 | 2026-07-11 |
| LAE1808 | - | 4 | 2026-06-30 |
| LTG9830 | - | 3 | 2026-06-27 |
| LTG8516 | - | 3 | 2026-07-06 |
| LTG8514 | LATAM Cargo Brasil | 3 | 2026-07-03 |
| LTG8513 | LATAM Cargo Brasil | 3 | 2026-05-07 |
| LNE426 | LATAM Airlines Ecuador | 3 | 2026-06-25 |
| LCO1608 | - | 3 | 2026-06-23 |
| LCO1102 | - | 3 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | LCO3603 | - | Jul 14, 00:20 UTC | Jul 14, 04:00 UTC | 3h 40m |
| 2026-07-13 | LCO3617 | - | Jul 13, 17:15 UTC | Jul 13, 17:45 UTC | 30m |
| 2026-07-13 | LCO3617 | - | Jul 13, 15:30 UTC | Jul 13, 16:05 UTC | 35m |
| 2026-07-13 | LCO3617 | - | Jul 13, 11:45 UTC | Jul 13, 13:50 UTC | 2h 5m |
| 2026-07-12 | LCO3617 | - | Jul 12, 19:35 UTC | Jul 13, 09:35 UTC | 14h 0m |
| 2026-07-12 | LCO3617 | BRU → FRA | Jul 12, 16:30 UTC | Jul 12, 17:05 UTC | 35m |
| 2026-07-12 | LCO3607 | - | Jul 12, 04:25 UTC | Jul 12, 13:10 UTC | 8h 45m |
| 2026-07-11 | LNE617 | - | Jul 11, 14:40 UTC | Jul 12, 02:20 UTC | 11h 40m |
| 2026-07-11 | LAE2545 | - | Jul 11, 11:20 UTC | Jul 11, 11:50 UTC | 30m |
| 2026-07-11 | LAE1811 | - | Jul 11, 03:30 UTC | Jul 11, 03:50 UTC | 20m |
| 2026-07-10 | LTG9832 | - | Jul 10, 16:45 UTC | Jul 10, 20:05 UTC | 3h 20m |
| 2026-07-10 | LTG9832 | - | Jul 10, 07:40 UTC | Jul 10, 15:05 UTC | 7h 25m |
| 2026-07-10 | LAE2502 | - | Jul 10, 04:35 UTC | Jul 10, 05:55 UTC | 1h 20m |
| 2026-07-09 | LAE2502 | - | Jul 9, 20:00 UTC | Jul 10, 03:05 UTC | 7h 5m |
| 2026-07-09 | LAE2544 | - | Jul 9, 14:20 UTC | Jul 9, 17:30 UTC | 3h 10m |
| 2026-07-09 | LAE2543 | - | Jul 9, 12:00 UTC | Jul 9, 12:15 UTC | 15m |
| 2026-07-09 | LAE2543 | - | Jul 9, 09:10 UTC | Jul 9, 09:35 UTC | 25m |
| 2026-07-08 | LCO1505 | - | Jul 8, 17:40 UTC | Jul 8, 22:45 UTC | 5h 5m |
| 2026-07-07 | LCO1102 | - | Jul 7, 22:05 UTC | Jul 8, 03:05 UTC | 5h 0m |
| 2026-07-07 | LAE1802 | - | Jul 7, 13:00 UTC | Jul 7, 18:25 UTC | 5h 25m |
| 2026-07-07 | LAE1801 | - | Jul 7, 09:00 UTC | Jul 7, 11:35 UTC | 2h 35m |
| 2026-07-06 | LTG8478 | - | Jul 6, 14:45 UTC | Jul 6, 15:10 UTC | 25m |
| 2026-07-06 | LTG8478 | - | Jul 6, 05:45 UTC | Jul 6, 08:40 UTC | 2h 55m |
| 2026-07-06 | LTG8516 | - | Jul 6, 02:10 UTC | Jul 6, 02:50 UTC | 40m |
| 2026-07-05 | LTG8516 | - | Jul 5, 22:20 UTC | Jul 5, 23:50 UTC | 1h 30m |
| 2026-07-04 | LTG8516 | - | Jul 4, 15:05 UTC | Jul 4, 19:10 UTC | 4h 5m |
| 2026-07-04 | LTG8506 | - | Jul 4, 03:55 UTC | Jul 4, 12:35 UTC | 8h 40m |
| 2026-07-03 | LTG8507 | - | Jul 3, 12:20 UTC | Jul 4, 01:25 UTC | 13h 5m |
| 2026-07-03 | LTG8514 | FLN → VCP | Jul 3, 09:20 UTC | Jul 3, 10:15 UTC | 55m |
| 2026-07-03 | LTG8514 | FLN → VCP | Jul 3, 07:20 UTC | Jul 3, 08:10 UTC | 50m |
| 2026-07-02 | LTG8514 | FLN → VCP | Jul 2, 12:35 UTC | Jul 3, 01:55 UTC | 13h 20m |
| 2026-07-02 | LTG8504 | SID → BRU | Jul 2, 01:25 UTC | Jul 2, 10:00 UTC | 8h 35m |
| 2026-07-01 | LNE317 | - | Jul 1, 07:00 UTC | Jul 1, 20:10 UTC | 13h 10m |
| 2026-06-30 | LAE1808 | - | Jun 30, 06:15 UTC | Jun 30, 14:00 UTC | 7h 45m |
| 2026-06-29 | LNE120 | UIO → MIA | Jun 29, 09:44 UTC | Jun 29, 21:30 UTC | 11h 45m |
| 2026-06-28 | LAE2548 | - | Jun 28, 20:59 UTC | Jun 28, 21:34 UTC | 35m |
| 2026-06-28 | LAE2807 | MIA → BOG | Jun 28, 05:45 UTC | Jun 28, 07:25 UTC | 1h 40m |
| 2026-06-27 | LTG9830 | - | Jun 27, 13:04 UTC | Jun 28, 02:44 UTC | 13h 40m |
| 2026-06-27 | LCO1204 | - | Jun 27, 08:05 UTC | Jun 27, 10:50 UTC | 2h 45m |
| 2026-06-27 | LCO1105 | - | Jun 27, 01:54 UTC | Jun 27, 02:25 UTC | 30m |
| 2026-06-26 | LCO1105 | - | Jun 26, 15:15 UTC | Jun 26, 23:39 UTC | 8h 25m |
| 2026-06-25 | LNE426 | UIO → MIA | Jun 25, 22:20 UTC | Jun 26, 09:59 UTC | 11h 40m |
| 2026-06-25 | LAE2540 | - | Jun 25, 18:59 UTC | Jun 25, 19:34 UTC | 35m |
| 2026-06-25 | LAE2539 | - | Jun 25, 11:19 UTC | Jun 25, 11:39 UTC | 20m |
| 2026-06-25 | LAE2544 | - | Jun 25, 08:09 UTC | Jun 25, 08:40 UTC | 30m |
| 2026-06-25 | LAE2543 | MIA → BOG | Jun 25, 00:09 UTC | Jun 25, 00:35 UTC | 25m |
| 2026-06-23 | LCO1608 | - | Jun 23, 19:34 UTC | Jun 24, 04:30 UTC | 8h 55m |
| 2026-06-22 | LAE2530 | MIA → MDE | Jun 22, 23:05 UTC | Jun 22, 23:39 UTC | 35m |
| 2026-06-22 | LAE2525 | LAX → SEA | Jun 22, 10:05 UTC | Jun 22, 14:59 UTC | 4h 55m |
| 2026-06-22 | LAE2525 | LAX → SEA | Jun 22, 00:14 UTC | Jun 22, 08:10 UTC | 7h 55m |
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-BDC page for operator, model, and routing details .