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