Not currently tracked · last seen 5h ago
- Flights observed
- 168 showing last 50
- Avg flight time
- 3h 48m
- Typical route
- AEP → TUC
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | AEP → BRC | May 29, 22:30 UTC | May 30, 03:20 UTC | 4h 50m |
| 2026-05-29 | ASU → AEP | May 29, 19:10 UTC | May 29, 20:40 UTC | 1h 30m |
| 2026-05-29 | AEP → ASU | May 29, 16:35 UTC | May 29, 17:55 UTC | 1h 20m |
| 2026-05-26 | AEP → SLA | May 26, 23:25 UTC | May 27, 03:59 UTC | 4h 35m |
| 2026-05-26 | AEP → RES | May 26, 18:59 UTC | May 26, 22:15 UTC | 3h 15m |
| 2026-05-25 | AEP → TUC | May 25, 21:15 UTC | May 26, 01:14 UTC | 4h 0m |
| 2026-05-25 | NAT → EZE | May 25, 07:20 UTC | May 25, 19:25 UTC | 12h 4m |
| 2026-05-24 | IGR → AEP | May 24, 23:30 UTC | May 24, 23:46 UTC | 16m |
| 2026-05-24 | AEP → IGR | May 24, 21:00 UTC | May 24, 21:45 UTC | 45m |
| 2026-05-24 | EZE → REC | May 24, 07:50 UTC | May 24, 19:10 UTC | 11h 20m |
| 2026-05-23 | AEP → TUC | May 23, 23:05 UTC | May 24, 03:20 UTC | 4h 15m |
| 2026-05-23 | AEP → TUC | May 23, 17:45 UTC | May 23, 21:45 UTC | 4h 0m |
| 2026-05-23 | EZE → BRC | May 23, 10:20 UTC | May 23, 15:05 UTC | 4h 45m |
| 2026-05-23 | GIG → ASU | May 23, 01:45 UTC | May 23, 03:10 UTC | 1h 24m |
| 2026-05-22 | GIG → ASU | May 22, 22:20 UTC | May 23, 00:30 UTC | 2h 10m |
| 2026-05-22 | AEP → GIG | May 22, 18:35 UTC | May 22, 21:05 UTC | 2h 30m |
| 2026-05-22 | AEP → MDZ | May 22, 12:50 UTC | May 22, 16:35 UTC | 3h 45m |
| 2026-05-22 | AEP → COR | May 22, 08:45 UTC | May 22, 11:45 UTC | 3h 0m |
| 2026-05-22 | COR → AEP | May 22, 01:20 UTC | May 22, 04:10 UTC | 2h 50m |
| 2026-05-21 | MDZ → AEP | May 21, 20:20 UTC | May 22, 00:20 UTC | 4h 0m |
| 2026-05-21 | IGR → EZE | May 21, 17:35 UTC | May 21, 19:05 UTC | 1h 30m |
| 2026-05-21 | AEP → IGR | May 21, 15:10 UTC | May 21, 16:30 UTC | 1h 20m |
| 2026-05-21 | IGR → EZE | May 21, 12:20 UTC | May 21, 14:00 UTC | 1h 40m |
| 2026-05-21 | AEP → IGR | May 21, 09:40 UTC | May 21, 10:55 UTC | 1h 15m |
| 2026-05-21 | RES → AEP | May 21, 00:00 UTC | May 21, 03:15 UTC | 3h 15m |
| 2026-05-20 | AEP → CRD | May 20, 17:15 UTC | May 20, 22:55 UTC | 5h 40m |
| 2026-05-20 | BRC → AEP | May 20, 10:20 UTC | May 20, 15:15 UTC | 4h 55m |
| 2026-05-19 | AEP → MDZ | May 19, 16:05 UTC | May 19, 19:45 UTC | 3h 40m |
| 2026-05-19 | AEP → REL | May 19, 10:40 UTC | May 19, 14:55 UTC | 4h 15m |
| 2026-05-18 | AEP → RES | May 18, 23:10 UTC | May 19, 02:40 UTC | 3h 30m |
| 2026-05-18 | AEP → CPC | May 18, 16:20 UTC | May 18, 20:55 UTC | 4h 34m |
| 2026-05-18 | AEP → REL | May 18, 10:40 UTC | May 18, 14:45 UTC | 4h 5m |
| 2026-05-17 | AEP → BRC | May 17, 21:20 UTC | May 18, 02:10 UTC | 4h 50m |
| 2026-05-17 | NAT → EZE | May 17, 07:20 UTC | May 17, 19:10 UTC | 11h 50m |
| 2026-05-16 | AEP → SLA | May 16, 22:30 UTC | May 17, 03:05 UTC | 4h 35m |
| 2026-05-16 | ASU → AEP | May 16, 19:35 UTC | May 16, 20:55 UTC | 1h 20m |
| 2026-05-16 | AEP → ASU | May 16, 16:25 UTC | May 16, 17:45 UTC | 1h 20m |
| 2026-05-16 | AEP → CRD | May 16, 09:31 UTC | May 16, 14:25 UTC | 4h 55m |
| 2026-05-15 | AEP → SLA | May 15, 21:20 UTC | May 16, 01:50 UTC | 4h 30m |
| 2026-05-15 | NAT → EZE | May 15, 07:30 UTC | May 15, 19:55 UTC | 12h 24m |
| 2026-05-15 | AEP → TUC | May 15, 00:20 UTC | May 15, 04:15 UTC | 3h 55m |
| 2026-05-14 | RES → AEP | May 14, 19:50 UTC | May 14, 23:00 UTC | 3h 10m |
| 2026-05-14 | AEP → CPC | May 14, 14:10 UTC | May 14, 18:40 UTC | 4h 30m |
| 2026-05-14 | AEP → CRD | May 14, 07:50 UTC | May 14, 12:55 UTC | 5h 5m |
| 2026-05-13 | AEP → NQN | May 13, 22:35 UTC | May 14, 02:30 UTC | 3h 55m |
| 2026-05-13 | ASU → AEP | May 13, 19:30 UTC | May 13, 20:55 UTC | 1h 25m |
| 2026-05-13 | AEP → ASU | May 13, 16:50 UTC | May 13, 18:05 UTC | 1h 15m |
| 2026-05-13 | MDZ → EZE | May 13, 14:10 UTC | May 13, 14:25 UTC | 15m |
| 2026-05-12 | COR → EZE | May 12, 15:25 UTC | May 12, 15:40 UTC | 15m |
| 2026-05-11 | AEP → CPC | May 11, 16:10 UTC | May 11, 20:50 UTC | 4h 40m |
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 TUC based on observed flights.
Where is LV-IVO right now?
LV-IVO is not currently being tracked; last seen 5h ago.