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