Flight
NOS47YJ
Flight history and live tracking for NOS47YJ, operated by Neos. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Neos |
| Observed route | LIPX → LGSA |
Flight history 14 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 16:31Z | 23:18Z | 6h 46m | EI-HIM |
Earlier flights (13) - back to 2026-04-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | LIPX | LGSA | 18:00 CEST | 01:24 EEST | 6h 23m | EI-HIM |
| 2026-07-11estimated | LIPX | LGSA | 18:04 CEST | 20:40 EEST | 1h 35m | EI-HIM |
| 2026-07-04estimated | LIPX | LGSA | 18:09 CEST | 01:30 EEST | 6h 20m | EI-RZB |
| 2026-06-27 | LIPX | LGIR | 18:45 CEST | 02:37 EEST | 6h 52m | EI-RZA |
| 2026-06-20estimated | LIPX | LGSA | 18:41 CEST | 21:20 EEST | 1h 38m | 4CAE05 |
| 2026-06-13estimated | LIPX | LGSA | 19:58 CEST | 22:24 EEST | 1h 26m | EI-RZB |
| 2026-05-23estimated | LIPX | LGSA | 11:44 CEST | 14:14 EEST | 1h 29m | EI-RZB |
| 2026-05-09estimated | LIPX | LGSA | 11:23 CEST | 18:58 EEST | 6h 34m | EI-RZB |
| 2026-05-02estimated | LIPX | LGST | 08:16 CEST | 15:47 EEST | 6h 31m | EI-RZB |
| 2026-04-25 | LIPX | LGIR | 08:09 CEST | 16:04 EEST | 6h 54m | EI-RZC |
| 2026-04-18estimated | LIPX | LGSA | 07:46 CEST | 11:40 EEST | 2h 54m | EI-RZB |
| 2026-04-11estimated | LIPX | LGSA | 08:05 CEST | 11:00 EEST | 1h 54m | EI-RZC |
| 2026-04-04estimated | ? | ? | 05:56Z | 12:24Z | 6h 27m | 4CAEB1 |
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 NOS47YJ 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]