Not currently tracked · last seen 1d ago
- Flights observed
- 69 showing last 50
- Avg flight time
- 10h 16m
- Typical route
- EZE → MAD
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-27 | MAD → EZE | May 27, 18:25 UTC | May 28, 06:50 UTC | 12h 25m |
| 2026-05-27 | EZE → MAD | May 27, 03:04 UTC | May 27, 14:30 UTC | 11h 25m |
| 2026-05-25 | CUN → EZE | May 25, 23:10 UTC | May 26, 07:24 UTC | 8h 15m |
| 2026-05-25 | EZE → CUN | May 25, 11:50 UTC | May 25, 20:34 UTC | 8h 44m |
| 2026-05-22 | MAD → EZE | May 22, 18:30 UTC | May 23, 07:05 UTC | 12h 34m |
| 2026-05-22 | EZE → MAD | May 22, 03:15 UTC | May 22, 14:35 UTC | 11h 20m |
| 2026-05-20 | MAD → EZE | May 20, 18:20 UTC | May 21, 06:45 UTC | 12h 25m |
| 2026-05-20 | EZE → MAD | May 20, 03:15 UTC | May 20, 14:45 UTC | 11h 31m |
| 2026-05-18 | FCO → EZE | May 18, 17:50 UTC | May 19, 07:10 UTC | 13h 19m |
| 2026-05-18 | EZE → FCO | May 18, 01:55 UTC | May 18, 14:25 UTC | 12h 30m |
| 2026-05-16 | MIA → EZE | May 16, 22:40 UTC | May 17, 06:50 UTC | 8h 10m |
| 2026-05-16 | EZE → MIA | May 16, 11:21 UTC | May 16, 20:15 UTC | 8h 55m |
| 2026-05-15 | MAD → EZE | May 15, 18:35 UTC | May 16, 06:50 UTC | 12h 16m |
| 2026-05-15 | EZE → MAD | May 15, 03:00 UTC | May 15, 14:40 UTC | 11h 40m |
| 2026-05-12 | MAD → EZE | May 12, 18:25 UTC | May 13, 07:20 UTC | 12h 55m |
| 2026-05-12 | EZE → MAD | May 12, 03:10 UTC | May 12, 14:10 UTC | 11h 0m |
| 2026-05-11 | MAD → EZE | May 11, 09:15 UTC | May 11, 22:15 UTC | 13h 1m |
| 2026-05-10 | EZE → MAD | May 10, 18:25 UTC | May 11, 05:30 UTC | 11h 5m |
| 2026-05-09 | MAD → EZE | May 9, 18:25 UTC | May 10, 06:55 UTC | 12h 30m |
| 2026-05-09 | EZE → MAD | May 9, 03:10 UTC | May 9, 14:50 UTC | 11h 40m |
| 2026-05-05 | MAD → EZE | May 5, 18:15 UTC | May 6, 07:25 UTC | 13h 10m |
| 2026-05-05 | EZE → MAD | May 5, 03:25 UTC | May 5, 14:20 UTC | 10h 55m |
| 2026-05-04 | MAD → EZE | May 4, 09:25 UTC | May 4, 22:40 UTC | 13h 16m |
| 2026-05-03 | EZE → MAD | May 3, 18:20 UTC | May 4, 05:30 UTC | 11h 10m |
| 2026-05-02 | FCO → EZE | May 2, 17:25 UTC | May 3, 07:15 UTC | 13h 49m |
| 2026-05-02 | EZE → FCO | May 2, 02:05 UTC | May 2, 14:40 UTC | 12h 35m |
| 2026-05-01 | MAD → EZE | May 1, 09:20 UTC | May 1, 22:05 UTC | 12h 45m |
| 2026-04-30 | EZE → MAD | Apr 30, 18:30 UTC | May 1, 05:55 UTC | 11h 25m |
| 2026-04-30 | CUN → EZE | Apr 30, 05:20 UTC | Apr 30, 13:25 UTC | 8h 5m |
| 2026-04-29 | EZE → CUN | Apr 29, 02:35 UTC | Apr 29, 11:15 UTC | 8h 41m |
| 2026-04-28 | MAD → EZE | Apr 28, 03:00 UTC | Apr 28, 06:35 UTC | 3h 35m |
| 2026-04-27 | MAD → EZE | Apr 27, 18:20 UTC | Apr 28, 02:40 UTC | 8h 20m |
| 2026-04-27 | EZE → MAD | Apr 27, 03:25 UTC | Apr 27, 15:00 UTC | 11h 35m |
| 2026-04-26 | MAD → EZE | Apr 26, 17:55 UTC | Apr 26, 21:30 UTC | 3h 35m |
| 2026-04-26 | MAD → EZE | Apr 26, 09:20 UTC | Apr 26, 17:25 UTC | 8h 5m |
| 2026-04-25 | EZE → MAD | Apr 25, 18:25 UTC | Apr 26, 05:55 UTC | 11h 30m |
| 2026-04-24 | FCO → EZE | Apr 24, 17:40 UTC | Apr 25, 07:25 UTC | 13h 45m |
| 2026-04-24 | EZE → FCO | Apr 24, 01:50 UTC | Apr 24, 14:40 UTC | 12h 50m |
| 2026-04-23 | MAD → EZE | Apr 23, 09:25 UTC | Apr 23, 22:05 UTC | 12h 39m |
| 2026-04-22 | EZE → MAD | Apr 22, 18:35 UTC | Apr 23, 05:40 UTC | 11h 5m |
| 2026-04-21 | MAD → EZE | Apr 21, 19:15 UTC | Apr 22, 07:50 UTC | 12h 35m |
| 2026-04-21 | EZE → MAD | Apr 21, 12:20 UTC | Apr 21, 16:31 UTC | 4h 10m |
| 2026-04-21 | EZE → MAD | Apr 21, 04:40 UTC | Apr 21, 07:45 UTC | 3h 5m |
| 2026-04-20 | MAD → EZE | Apr 20, 09:25 UTC | Apr 20, 22:20 UTC | 12h 55m |
| 2026-04-19 | EZE → MAD | Apr 19, 18:10 UTC | Apr 20, 05:35 UTC | 11h 25m |
| 2026-04-18 | MAD → EZE | Apr 18, 18:20 UTC | Apr 19, 07:00 UTC | 12h 40m |
| 2026-04-18 | EZE → MAD | Apr 18, 05:25 UTC | Apr 18, 06:10 UTC | 45m |
| 2026-04-18 | EZE → MAD | Apr 18, 04:50 UTC | Apr 18, 06:10 UTC | 1h 20m |
| 2026-04-18 | EZE → MAD | Apr 18, 03:25 UTC | Apr 18, 05:20 UTC | 1h 55m |
| 2026-04-18 | EZE → MAD | Apr 18, 03:05 UTC | Apr 18, 14:50 UTC | 11h 45m |
Specifications
| Registration | LV-FVH |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | E06588 · 70062610 (octal) |
Looking for transponder-level data? View the Mode-S E06588 page for country allocation, callsign history, and ADS-B signal details.
LV-FVH frequently asked
What type of aircraft is LV-FVH?
LV-FVH is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for LV-FVH?
LV-FVH broadcasts on Mode-S (ICAO 24-bit) address E06588 (octal 70062610). View the transponder page.
What route does LV-FVH typically fly?
LV-FVH most frequently flies between EZE and MAD based on observed flights.
Where is LV-FVH right now?
LV-FVH is not currently being tracked; last seen 1d ago.