Not currently tracked · last seen 1h ago
- Flights observed
- 93 showing last 50
- Avg flight time
- 11h 39m
- Typical route
- CUN → EZE
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 03:50 UTC | Jul 14, 08:30 UTC | 4h 40m |
| 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 |
| 2026-06-02 | EZE → FCO | Jun 2, 02:05 UTC | Jun 2, 02:35 UTC | 30m |
| 2026-05-31 | MAD → EZE | May 31, 18:45 UTC | Jun 1, 07:10 UTC | 12h 25m |
| 2026-05-31 | EZE → MAD | May 31, 12:10 UTC | May 31, 14:35 UTC | 2h 25m |
| 2026-05-30 | PUJ → EZE | May 30, 02:15 UTC | May 30, 20:05 UTC | 17h 50m |
| 2026-05-28 | CUN → EZE | May 28, 03:05 UTC | May 28, 22:30 UTC | 19h 25m |
| 2026-05-28 | CUN → EZE | May 28, 02:35 UTC | May 28, 22:30 UTC | 19h 55m |
| 2026-05-23 | CUN → EZE | May 23, 23:00 UTC | May 24, 06:55 UTC | 7h 55m |
| 2026-05-23 | EZE → CUN | May 23, 11:55 UTC | May 23, 20:50 UTC | 8h 55m |
| 2026-05-22 | CUN → EZE | May 22, 14:00 UTC | May 22, 22:15 UTC | 8h 15m |
| 2026-05-22 | EZE → CUN | May 22, 02:35 UTC | May 22, 11:35 UTC | 9h 0m |
| 2026-05-21 | CUN → EZE | May 21, 14:05 UTC | May 21, 22:15 UTC | 8h 10m |
| 2026-05-21 | EZE → CUN | May 21, 02:30 UTC | May 21, 11:15 UTC | 8h 45m |
| 2026-05-17 | PUJ → EZE | May 17, 13:05 UTC | May 18, 07:05 UTC | 18h 0m |
| 2026-05-17 | EZE → PUJ | May 17, 11:50 UTC | May 18, 07:05 UTC | 19h 15m |
| 2026-05-16 | CUN → EZE | May 16, 23:20 UTC | May 17, 07:10 UTC | 7h 50m |
| 2026-05-16 | EZE → CUN | May 16, 11:46 UTC | May 16, 20:55 UTC | 9h 10m |
| 2026-05-15 | PUJ → EZE | May 15, 13:05 UTC | May 16, 07:05 UTC | 18h 0m |
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 CUN and EZE based on observed flights.
Where is LV-KHT right now?
LV-KHT is not currently being tracked; last seen 1h ago.