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