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