Not currently tracked · last seen Jul 26, 22:45 UTC
- Flights observed
- 110 showing last 50
- Avg flight time
- 10h 55m
- Typical route
- EZE → PUJ
- Last seen
- Jul 26, 22:45 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | AEP → IGR | Jul 26, 21:50 UTC | Jul 26, 22:45 UTC | 55m |
| 2026-07-26 | GIG → AEP | Jul 26, 14:55 UTC | Jul 26, 17:55 UTC | 3h 0m |
| 2026-07-26 | AEP → GIG | Jul 26, 10:35 UTC | Jul 26, 12:50 UTC | 2h 15m |
| 2026-07-25 | EZE → USH | Jul 25, 17:55 UTC | Jul 26, 01:30 UTC | 7h 35m |
| 2026-07-24 | FCO → EZE | Jul 24, 22:20 UTC | Jul 25, 11:55 UTC | 13h 35m |
| 2026-07-24 | EZE → FCO | Jul 24, 06:55 UTC | Jul 24, 19:50 UTC | 12h 55m |
| 2026-07-23 | USH → AEP | Jul 23, 18:25 UTC | Jul 24, 02:20 UTC | 7h 55m |
| 2026-07-22 | EZE → PUJ | Jul 22, 21:15 UTC | Jul 23, 05:40 UTC | 8h 25m |
| 2026-07-22 | EZE → PUJ | Jul 22, 11:25 UTC | Jul 22, 19:10 UTC | 7h 45m |
| 2026-07-20 | - | Jul 20, 19:50 UTC | Jul 21, 08:15 UTC | 12h 25m |
| 2026-07-20 | EZE → MAD | Jul 20, 03:25 UTC | Jul 20, 15:10 UTC | 11h 45m |
| 2026-07-19 | MAD → EZE | Jul 19, 09:25 UTC | Jul 19, 21:55 UTC | 12h 30m |
| 2026-07-18 | EZE → MAD | Jul 18, 19:05 UTC | Jul 19, 06:30 UTC | 11h 25m |
| 2026-07-18 | - | Jul 18, 02:05 UTC | Jul 18, 10:15 UTC | 8h 11m |
| 2026-07-17 | EZE → MIA | Jul 17, 02:10 UTC | Jul 17, 10:50 UTC | 8h 40m |
| 2026-07-16 | - | Jul 16, 05:20 UTC | Jul 16, 22:55 UTC | 17h 35m |
| 2026-07-14 | - | Jul 14, 22:55 UTC | Jul 15, 07:20 UTC | 8h 25m |
| 2026-07-14 | - | Jul 14, 03:50 UTC | Jul 14, 12:20 UTC | 8h 30m |
| 2026-07-12 | CUN → EZE | Jul 12, 13:40 UTC | Jul 13, 02:05 UTC | 12h 25m |
| 2026-07-12 | - | Jul 12, 03:30 UTC | Jul 12, 12:01 UTC | 8h 30m |
| 2026-07-11 | - | Jul 11, 05:25 UTC | Jul 11, 23:00 UTC | 17h 35m |
| 2026-07-10 | CUN → EZE | Jul 10, 13:35 UTC | Jul 11, 01:40 UTC | 12h 6m |
| 2026-07-10 | - | Jul 10, 02:55 UTC | Jul 10, 11:45 UTC | 8h 50m |
| 2026-07-08 | - | Jul 8, 22:35 UTC | Jul 9, 07:05 UTC | 8h 30m |
| 2026-07-08 | - | Jul 8, 03:50 UTC | Jul 8, 12:30 UTC | 8h 40m |
| 2026-07-07 | MIA → EZE | Jul 7, 01:40 UTC | Jul 7, 10:15 UTC | 8h 35m |
| 2026-07-06 | - | Jul 6, 10:45 UTC | Jul 6, 11:15 UTC | 30m |
| 2026-07-06 | - | Jul 6, 02:05 UTC | Jul 6, 07:15 UTC | 5h 10m |
| 2026-07-03 | MAD → EZE | Jul 3, 09:50 UTC | Jul 3, 22:30 UTC | 12h 40m |
| 2026-07-02 | EZE → MAD | Jul 2, 18:20 UTC | Jul 3, 05:50 UTC | 11h 30m |
| 2026-06-29 | - | Jun 29, 17:34 UTC | Jun 30, 07:20 UTC | 13h 45m |
| 2026-06-29 | - | Jun 29, 01:50 UTC | Jun 29, 14:29 UTC | 12h 40m |
| 2026-06-28 | MAD → EZE | Jun 28, 09:25 UTC | Jun 28, 21:34 UTC | 12h 10m |
| 2026-06-27 | EZE → MAD | Jun 27, 18:35 UTC | Jun 28, 06:24 UTC | 11h 50m |
| 2026-06-26 | - | Jun 26, 19:45 UTC | Jun 27, 09:04 UTC | 13h 20m |
| 2026-06-26 | - | Jun 26, 03:50 UTC | Jun 26, 16:54 UTC | 13h 5m |
| 2026-06-22 | CUN → EZE | Jun 22, 20:55 UTC | Jun 23, 05:00 UTC | 8h 5m |
| 2026-06-22 | - | Jun 22, 05:44 UTC | Jun 22, 19:05 UTC | 13h 20m |
| 2026-06-19 | - | Jun 19, 09:44 UTC | Jun 20, 01:34 UTC | 15h 50m |
| 2026-06-19 | - | Jun 19, 03:05 UTC | Jun 20, 01:34 UTC | 22h 30m |
| 2026-06-19 | - | Jun 19, 02:45 UTC | Jun 20, 00:59 UTC | 22h 15m |
| 2026-06-13 | PUJ → EZE | Jun 13, 05:40 UTC | Jun 13, 23:20 UTC | 17h 40m |
| 2026-06-08 | EZE → PUJ | Jun 8, 21:20 UTC | Jun 9, 05:40 UTC | 8h 20m |
| 2026-06-08 | EZE → PUJ | Jun 8, 05:40 UTC | Jun 8, 19:00 UTC | 13h 20m |
| 2026-06-07 | EZE → CUN | Jun 7, 13:40 UTC | Jun 8, 02:05 UTC | 12h 25m |
| 2026-06-07 | EZE → CUN | Jun 7, 02:45 UTC | Jun 7, 11:55 UTC | 9h 10m |
| 2026-06-05 | EZE → CUN | Jun 5, 14:10 UTC | Jun 6, 03:00 UTC | 12h 50m |
| 2026-06-05 | EZE → CUN | Jun 5, 02:45 UTC | Jun 5, 11:50 UTC | 9h 5m |
| 2026-06-02 | FCO → EZE | Jun 2, 17:30 UTC | Jun 3, 07:15 UTC | 13h 45m |
| 2026-06-02 | EZE → FCO | Jun 2, 03:15 UTC | Jun 2, 14:45 UTC | 11h 30m |
Specifications
| Registration | LV-KHT |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | E0B214 · 70131024 (octal) |
Looking for transponder-level data? View the Mode-S E0B214 page for country allocation, callsign history, and ADS-B signal details.
LV-KHT frequently asked
What type of aircraft is LV-KHT?
LV-KHT is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for LV-KHT?
LV-KHT broadcasts on Mode-S (ICAO 24-bit) address E0B214 (octal 70131024). View the transponder page.
What route does LV-KHT typically fly?
LV-KHT most frequently flies between EZE and PUJ based on observed flights.
Where is LV-KHT right now?
LV-KHT is not currently being tracked; last seen Jul 26, 22:45 UTC.