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