Flight
JAF3LY
Flight history and live tracking for JAF3LY, operated by Jetairfly. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Jetairfly |
| Observed route | EBBR → LEVX |
Flight history 16 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (16) - back to 2026-01-03
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-03-16estimated | ? | ? | 04:59Z | 08:58Z | 3h 58m | OO-TMZ |
| 2026-03-15estimated | ? | ? | 05:17Z | 09:10Z | 3h 52m | OO-TNB |
| 2026-03-14 | EBBR | ? | 06:08 CET | 10:54Z | 5h 46m | OO-JEF |
| 2026-03-13estimated | ? | ? | 05:03Z | 09:10Z | 4h 07m | 44D1A6 |
| 2026-03-11 | EBBR | ? | 06:45 CET | 08:23Z | 2h 37m | 44D1A6 |
| 2026-03-08 | EBBR | ? | 06:34 CET | 07:50Z | 2h 16m | 44D1A6 |
| 2026-03-02 | EBBR | ? | 06:19 CET | 06:20Z | 1h 01m | 44A8A6 |
| 2026-02-16 | EBBR | ? | 06:16 CET | 08:06Z | 2h 49m | 44D1A2 |
| 2026-02-15 | EBBR | ? | 07:36 CET | 08:54Z | 2h 17m | 408026 |
| 2026-02-14 | EBBR | ? | 06:55 CET | 07:11Z | 1h 15m | 406696 |
| 2026-02-12 | EBBR | ? | 06:18 CET | 08:43Z | 3h 25m | 44D1A5 |
| 2026-02-10 | EBBR | ? | 13:50 CET | 16:23Z | 3h 32m | 44D1A7 |
| 2026-02-08 | EBBR | ? | 06:19 CET | 08:02Z | 2h 43m | 44A838 |
| 2026-02-07 | EBBR | ? | 06:22 CET | 08:09Z | 2h 46m | 44D1A5 |
| 2026-02-05 | EBBR | ? | 06:19 CET | 09:18Z | 3h 59m | 44D1A5 |
| 2026-01-03 | EBBR | LEVX | 06:18 CET | 08:13 CET | 1h 55m | 44D1C2 |
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 JAF3LY 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]