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