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