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