Flight
RYR3663
Flight history and live tracking for RYR3663, operated by Ryanair. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Ryanair |
| Observed route | LEZL → LPMG |
Flight history 15 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 12:34Z | 13:18Z | 0h 44m | EI-DYX |
| 2026-08-13estimated | ? | ? | 12:34Z | 13:22Z | 0h 47m | EI-ENT |
Earlier flights (13) - back to 2026-04-02
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 12:30Z | 13:30Z | 0h 59m | EI-EVC |
| 2026-07-16estimated | ? | ? | 12:35Z | 13:32Z | 0h 56m | 9H-QEJ |
| 2026-07-09 | LEZL | LPMG | 14:42 CEST | 14:30 WEST | 0h 47m | 9H-QBC |
| 2026-07-02estimated | LEZL | LPMG | 14:34 CEST | 14:26 WEST | 0h 51m | 9H-QED |
| 2026-06-28 | EGSS | EDDW | 18:10 BST | 20:06 CEST | 0h 55m | EI-DYL |
| 2026-06-25estimated | LEZL | LPPT | 14:39 CEST | 14:30 WEST | 0h 50m | EI-ENW |
| 2026-05-28estimated | LEZL | LPMG | 14:39 CEST | 14:26 WEST | 0h 46m | EI-ENV |
| 2026-05-21 | LEZL | LPPT | 14:48 CEST | 14:42 WEST | 0h 53m | 4CAE65 |
| 2026-05-07estimated | LEZL | LPMG | 14:48 CEST | 14:42 WEST | 0h 53m | EI-DYL |
| 2026-04-30estimated | LEZL | LPPT | 14:38 CEST | 14:30 WEST | 0h 51m | 9H-QCJ |
| 2026-04-23estimated | ? | ? | 12:32Z | 13:20Z | 0h 47m | EI-EMK |
| 2026-04-16estimated | ? | ? | 12:33Z | 14:24Z | 1h 51m | EI-EGA |
| 2026-04-02estimated | ? | ? | 12:32Z | 13:34Z | 1h 01m | 9H-QDP |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when RYR3663 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]