Not currently tracked · last seen 4h ago
- Flights observed
- 269 showing last 50
- Avg flight time
- 3h 37m
- Typical route
- AEP → AEP
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 19:30 UTC | Jul 14, 03:15 UTC | 7h 45m |
| 2026-07-13 | GRU → AEP | Jul 13, 13:35 UTC | Jul 13, 16:20 UTC | 2h 45m |
| 2026-07-13 | - | Jul 13, 09:45 UTC | Jul 13, 11:50 UTC | 2h 5m |
| 2026-07-13 | - | Jul 13, 02:30 UTC | Jul 13, 03:05 UTC | 35m |
| 2026-07-13 | - | Jul 13, 00:55 UTC | Jul 13, 01:30 UTC | 35m |
| 2026-07-12 | - | Jul 12, 21:40 UTC | Jul 12, 23:25 UTC | 1h 45m |
| 2026-07-12 | - | Jul 12, 19:20 UTC | Jul 12, 20:25 UTC | 1h 5m |
| 2026-07-12 | - | Jul 12, 17:01 UTC | Jul 12, 18:30 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 14:15 UTC | Jul 12, 15:25 UTC | 1h 10m |
| 2026-07-11 | - | Jul 11, 22:40 UTC | Jul 12, 12:10 UTC | 13h 30m |
| 2026-07-11 | COR → AEP | Jul 11, 20:20 UTC | Jul 11, 21:25 UTC | 1h 5m |
| 2026-07-11 | AEP → COR | Jul 11, 14:50 UTC | Jul 11, 19:20 UTC | 4h 30m |
| 2026-07-11 | AEP → AEP | Jul 11, 08:01 UTC | Jul 11, 13:15 UTC | 5h 15m |
| 2026-07-10 | - | Jul 10, 21:10 UTC | Jul 11, 02:20 UTC | 5h 10m |
| 2026-07-10 | - | Jul 10, 19:40 UTC | Jul 10, 20:15 UTC | 35m |
| 2026-07-10 | AEP → AEP | Jul 10, 12:50 UTC | Jul 10, 18:05 UTC | 5h 15m |
| 2026-07-10 | - | Jul 10, 07:55 UTC | Jul 10, 10:30 UTC | 2h 35m |
| 2026-07-10 | - | Jul 10, 04:05 UTC | Jul 10, 06:20 UTC | 2h 15m |
| 2026-07-09 | AEP → AEP | Jul 9, 19:45 UTC | Jul 10, 03:10 UTC | 7h 25m |
| 2026-07-09 | EZE → AEP | Jul 9, 11:35 UTC | Jul 9, 16:25 UTC | 4h 50m |
| 2026-07-08 | - | Jul 8, 21:50 UTC | Jul 9, 02:30 UTC | 4h 40m |
| 2026-07-08 | - | Jul 8, 20:20 UTC | Jul 8, 20:55 UTC | 35m |
| 2026-07-08 | - | Jul 8, 11:10 UTC | Jul 8, 18:50 UTC | 7h 40m |
| 2026-07-08 | - | Jul 8, 02:10 UTC | Jul 8, 02:45 UTC | 35m |
| 2026-07-07 | - | Jul 7, 21:30 UTC | Jul 7, 22:05 UTC | 35m |
| 2026-07-07 | AEP → AEP | Jul 7, 07:45 UTC | Jul 7, 15:35 UTC | 7h 50m |
| 2026-07-07 | - | Jul 7, 01:40 UTC | Jul 7, 02:55 UTC | 1h 15m |
| 2026-07-06 | - | Jul 6, 23:15 UTC | Jul 7, 00:15 UTC | 1h 0m |
| 2026-07-06 | COR → AEP | Jul 6, 17:05 UTC | Jul 6, 22:05 UTC | 5h 0m |
| 2026-07-06 | AEP → COR | Jul 6, 14:40 UTC | Jul 6, 15:45 UTC | 1h 5m |
| 2026-07-06 | - | Jul 6, 12:25 UTC | Jul 6, 13:10 UTC | 45m |
| 2026-07-06 | - | Jul 6, 10:40 UTC | Jul 6, 11:10 UTC | 30m |
| 2026-07-05 | AEP → AEP | Jul 5, 22:40 UTC | Jul 6, 09:00 UTC | 10h 20m |
| 2026-07-05 | AEP → AEP | Jul 5, 17:25 UTC | Jul 5, 21:15 UTC | 3h 50m |
| 2026-07-05 | GRU → AEP | Jul 5, 15:45 UTC | Jul 5, 16:10 UTC | 25m |
| 2026-07-05 | GRU → AEP | Jul 5, 13:30 UTC | Jul 5, 14:30 UTC | 1h 0m |
| 2026-07-05 | - | Jul 5, 09:35 UTC | Jul 5, 11:35 UTC | 2h 0m |
| 2026-07-04 | AEP → AEP | Jul 4, 14:50 UTC | Jul 4, 23:40 UTC | 8h 50m |
| 2026-07-04 | - | Jul 4, 11:30 UTC | Jul 4, 13:15 UTC | 1h 45m |
| 2026-07-04 | - | Jul 4, 08:55 UTC | Jul 4, 10:10 UTC | 1h 15m |
| 2026-07-04 | - | Jul 4, 04:20 UTC | Jul 4, 07:25 UTC | 3h 5m |
| 2026-07-04 | AEP → GIG | Jul 4, 00:15 UTC | Jul 4, 02:40 UTC | 2h 25m |
| 2026-07-03 | - | Jul 3, 15:05 UTC | Jul 3, 22:40 UTC | 7h 35m |
| 2026-07-03 | - | Jul 3, 11:45 UTC | Jul 3, 13:45 UTC | 2h 0m |
| 2026-07-03 | AEP → AEP | Jul 3, 01:10 UTC | Jul 3, 08:05 UTC | 6h 55m |
| 2026-07-02 | AEP → AEP | Jul 2, 14:30 UTC | Jul 2, 23:45 UTC | 9h 15m |
| 2026-07-02 | AEP → AEP | Jul 2, 08:15 UTC | Jul 2, 12:55 UTC | 4h 40m |
| 2026-07-01 | AEP → AEP | Jul 1, 19:30 UTC | Jul 2, 03:15 UTC | 7h 45m |
| 2026-07-01 | GRU → AEP | Jul 1, 13:25 UTC | Jul 1, 16:10 UTC | 2h 45m |
| 2026-07-01 | - | Jul 1, 09:35 UTC | Jul 1, 11:50 UTC | 2h 15m |
Specifications
| Registration | LV-HKU |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | E082D5 · 70101325 (octal) |
Looking for transponder-level data? View the Mode-S E082D5 page for country allocation, callsign history, and ADS-B signal details.
LV-HKU frequently asked
What type of aircraft is LV-HKU?
LV-HKU is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for LV-HKU?
LV-HKU broadcasts on Mode-S (ICAO 24-bit) address E082D5 (octal 70101325). View the transponder page.
What route does LV-HKU typically fly?
LV-HKU most frequently flies between AEP and AEP based on observed flights.
Where is LV-HKU right now?
LV-HKU is not currently being tracked; last seen 4h ago.