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