Not currently tracked · last seen 23d ago
- Flights observed
- 133 showing last 50
- Avg flight time
- 9h 46m
- Typical route
- GYD → SAW
- Last seen
- 23d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-20 | - | Jun 20, 11:34 UTC | Jun 20, 21:34 UTC | 10h 0m |
| 2026-06-19 | - | Jun 19, 14:19 UTC | Jun 20, 09:54 UTC | 19h 35m |
| 2026-06-19 | BUS → VIE | Jun 19, 14:09 UTC | Jun 20, 09:54 UTC | 19h 45m |
| 2026-06-19 | - | Jun 19, 07:54 UTC | Jun 19, 13:09 UTC | 5h 15m |
| 2026-06-19 | - | Jun 19, 05:54 UTC | Jun 19, 06:14 UTC | 20m |
| 2026-06-18 | - | Jun 18, 22:05 UTC | Jun 19, 05:19 UTC | 7h 14m |
| 2026-06-18 | - | Jun 18, 08:20 UTC | Jun 18, 20:40 UTC | 12h 20m |
| 2026-06-18 | - | Jun 18, 06:20 UTC | Jun 18, 06:45 UTC | 25m |
| 2026-06-17 | - | Jun 17, 11:15 UTC | Jun 18, 05:40 UTC | 18h 25m |
| 2026-06-16 | - | Jun 16, 14:20 UTC | Jun 17, 09:55 UTC | 19h 36m |
| 2026-06-16 | - | Jun 16, 13:09 UTC | Jun 17, 09:55 UTC | 20h 46m |
| 2026-06-16 | - | Jun 16, 09:15 UTC | Jun 16, 11:45 UTC | 2h 30m |
| 2026-06-14 | ADB → GYD | Jun 14, 10:00 UTC | Jun 14, 12:05 UTC | 2h 5m |
| 2026-06-13 | GYD → ADB | Jun 13, 22:10 UTC | Jun 14, 08:10 UTC | 10h 0m |
| 2026-06-13 | SAW → GYD | Jun 13, 07:45 UTC | Jun 13, 20:45 UTC | 13h 0m |
| 2026-06-13 | GYD → SAW | Jun 13, 05:45 UTC | Jun 13, 06:00 UTC | 15m |
| 2026-06-13 | GYD → SAW | Jun 13, 03:35 UTC | Jun 13, 05:05 UTC | 1h 29m |
| 2026-06-12 | GYD → ESB | Jun 12, 16:45 UTC | Jun 12, 21:35 UTC | 4h 50m |
| 2026-06-12 | TBS → GYD | Jun 12, 13:40 UTC | Jun 12, 14:10 UTC | 30m |
| 2026-06-12 | GYD → TBS | Jun 12, 08:15 UTC | Jun 12, 12:00 UTC | 3h 45m |
| 2026-06-12 | - | Jun 12, 06:20 UTC | Jun 12, 06:50 UTC | 30m |
| 2026-06-11 | SAW → GYD | Jun 11, 13:15 UTC | Jun 11, 15:10 UTC | 1h 55m |
| 2026-06-11 | GYD → SAW | Jun 11, 09:30 UTC | Jun 11, 11:45 UTC | 2h 15m |
| 2026-06-09 | TIV → GYD | Jun 9, 10:45 UTC | Jun 9, 13:40 UTC | 2h 55m |
| 2026-06-09 | GYD → TIV | Jun 9, 06:10 UTC | Jun 9, 09:10 UTC | 3h 0m |
| 2026-06-07 | SAW → GYD | Jun 7, 13:20 UTC | Jun 7, 15:10 UTC | 1h 50m |
| 2026-06-07 | GYD → SAW | Jun 7, 09:30 UTC | Jun 7, 11:50 UTC | 2h 20m |
| 2026-06-06 | GYD → SAW | Jun 6, 14:20 UTC | Jun 7, 11:50 UTC | 21h 30m |
| 2026-06-06 | GYD → SAW | Jun 6, 12:20 UTC | Jun 7, 11:50 UTC | 23h 30m |
| 2026-06-06 | PRG → GYD | Jun 6, 11:09 UTC | Jun 7, 10:15 UTC | 23h 5m |
| 2026-06-05 | GYD → PRG | Jun 5, 14:20 UTC | Jun 6, 09:50 UTC | 19h 30m |
| 2026-06-05 | GYD → PRG | Jun 5, 12:20 UTC | Jun 6, 09:50 UTC | 21h 30m |
| 2026-06-05 | GYD → PRG | Jun 5, 11:20 UTC | Jun 6, 09:50 UTC | 22h 30m |
| 2026-06-05 | GYD → PRG | Jun 5, 06:20 UTC | Jun 5, 09:45 UTC | 3h 25m |
| 2026-06-04 | IST → GYD | Jun 4, 20:15 UTC | Jun 4, 22:30 UTC | 2h 15m |
| 2026-06-04 | GYD → IST | Jun 4, 18:15 UTC | Jun 4, 18:35 UTC | 20m |
| 2026-06-04 | TIV → GYD | Jun 4, 10:45 UTC | Jun 4, 17:40 UTC | 6h 55m |
| 2026-06-04 | GYD → TIV | Jun 4, 06:00 UTC | Jun 4, 09:10 UTC | 3h 10m |
| 2026-06-02 | VIE → GYD | Jun 2, 11:30 UTC | Jun 2, 14:40 UTC | 3h 10m |
| 2026-06-02 | GYD → VIE | Jun 2, 06:40 UTC | Jun 2, 09:55 UTC | 3h 15m |
| 2026-06-01 | GYD → VIE | Jun 1, 12:20 UTC | Jun 2, 09:55 UTC | 21h 35m |
| 2026-06-01 | GYD → VIE | Jun 1, 10:35 UTC | Jun 2, 09:55 UTC | 23h 20m |
| 2026-05-31 | SAW → GYD | May 31, 13:20 UTC | Jun 1, 07:50 UTC | 18h 30m |
| 2026-05-31 | GYD → SAW | May 31, 11:30 UTC | May 31, 11:50 UTC | 20m |
| 2026-05-30 | GYD → SAW | May 30, 16:55 UTC | May 31, 11:00 UTC | 18h 5m |
| 2026-05-30 | GYD → SAW | May 30, 12:50 UTC | May 31, 11:00 UTC | 22h 10m |
| 2026-05-30 | MXP → GYD | May 30, 10:20 UTC | May 31, 10:15 UTC | 23h 55m |
| 2026-05-30 | MXP → GYD | May 30, 09:55 UTC | May 30, 21:25 UTC | 11h 30m |
| 2026-05-30 | GYD → MXP | May 30, 04:20 UTC | May 30, 08:20 UTC | 4h 0m |
| 2026-05-29 | MXP → GYD | May 29, 10:00 UTC | May 29, 13:55 UTC | 3h 55m |
Specifications
| Registration | LY-JAM |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 503D79 · 24036571 (octal) |
Looking for transponder-level data? View the Mode-S 503D79 page for country allocation, callsign history, and ADS-B signal details.
LY-JAM frequently asked
What type of aircraft is LY-JAM?
LY-JAM is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for LY-JAM?
LY-JAM broadcasts on Mode-S (ICAO 24-bit) address 503D79 (octal 24036571). View the transponder page.
What route does LY-JAM typically fly?
LY-JAM most frequently flies between GYD and SAW based on observed flights.
Where is LY-JAM right now?
LY-JAM is not currently being tracked; last seen 23d ago.