Flight
DLZFN
Flight history and live tracking for DLZFN. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 52 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-13partial | EDLE | ? | 09:59 CEST | D-LZFN |
Earlier flights (51) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23partial | EDLE | ? | 11:34 CEST | D-LZFN | ||
| 2026-07-18 | EDLE | EDDL | 09:02 CEST | 13:00 CEST | 3h 58m | D-LZFN |
| 2026-07-14 | EGLC | EDLE | 08:27 BST | 19:44 CEST | 10h 16m | D-LZFN |
| 2026-07-11partial | EGLC | ? | 08:57 BST | D-LZFN | ||
| 2026-07-10partial | EGLC | ? | 08:56 BST | D-LZFN | ||
| 2026-07-09partial | EGLC | ? | 10:09 BST | D-LZFN | ||
| 2026-07-08partial | EGLC | ? | 08:37 BST | D-LZFN | ||
| 2026-07-05partial | EGLC | ? | 09:05 BST | D-LZFN | ||
| 2026-07-03partial | EGLC | ? | 11:54 BST | D-LZFN | ||
| 2026-07-01estimated | LFAC | EGLC | 09:26 CEST | 11:42 BST | 3h 15m | D-LZFN |
| 2026-06-30 | EDLE | EBFN | 10:42 CEST | 15:12 CEST | 4h 30m | D-LZFN |
| 2026-06-28partial | EDLE | ? | 09:58 CEST | D-LZFN | ||
| 2026-06-27partial | EDLE | ? | 08:59 CEST | D-LZFN | ||
| 2026-06-26partial | EDLE | ? | 09:18 CEST | D-LZFN | ||
| 2026-06-21partial | EDLE | ? | 11:58 CEST | D-LZFN | ||
| 2026-06-20partial | EDLE | ? | 09:05 CEST | D-LZFN | ||
| 2026-06-19partial | EDLE | ? | 10:30 CEST | D-LZFN | ||
| 2026-06-17 | LFSF | EDLE | 09:02 CEST | 16:48 CEST | 7h 45m | D-LZFN |
| 2026-06-14partial | LFRM | ? | 08:52 CEST | D-LZFN | ||
| 2026-06-13partial | LFRM | ? | 09:19 CEST | D-LZFN | ||
| 2026-06-12partial | LFRM | ? | 10:23 CEST | D-LZFN | ||
| 2026-05-29partial | EDDK | ? | 10:01 CEST | D-LZFN | ||
| 2026-05-28 | EDLE | EDDK | 09:35 CEST | 12:06 CEST | 2h 31m | D-LZFN |
| 2026-05-25partial | EDLE | ? | 10:01 CEST | D-LZFN | ||
| 2026-05-24partial | EDLE | ? | 09:56 CEST | D-LZFN | ||
| 2026-05-23partial | EDLE | ? | 10:49 CEST | D-LZFN | ||
| 2026-05-22partial | EDLE | ? | 12:03 CEST | D-LZFN | ||
| 2026-05-21partial | EDLE | ? | 11:13 CEST | D-LZFN | ||
| 2026-05-19partial | EDLE | ? | 17:26 CEST | D-LZFN | ||
| 2026-05-12partial | EDLE | ? | 17:52 CEST | D-LZFN | ||
| 2026-05-10 | EDNY | EDLE | 09:21 CEST | 16:32 CEST | 7h 10m | D-LZFN |
| 2026-05-08partial | EDNY | ? | 09:56 CEST | D-LZFN | ||
| 2026-05-04partial | EDNY | ? | 09:22 CEST | D-LZFN | ||
| 2026-05-03partial | EDNY | ? | 08:58 CEST | D-LZFN | ||
| 2026-05-02partial | EDNY | ? | 09:09 CEST | D-LZFN | ||
| 2026-05-01partial | EDNY | ? | 10:09 CEST | D-LZFN | ||
| 2026-04-28 | LOLW | EDNY | 08:54 CEST | 18:56 CEST | 10h 01m | D-LZFN |
| 2026-04-27estimated | LJMB | LOLW | 07:54 CEST | 13:16 CEST | 5h 21m | D-LZFN |
| 2026-04-24partial | LOAN | ? | 11:57 CEST | D-LZFN | ||
| 2026-04-23estimated | LIPE | LIPQ | 09:09 CEST | 11:54 CEST | 2h 44m | D-LZFN |
| 2026-04-19partial | LIPE | ? | 09:35 CEST | D-LZFN | ||
| 2026-04-18partial | LIPE | ? | 09:12 CEST | D-LZFN | ||
| 2026-04-17estimated | LJPZ | LIPE | 11:19 CEST | 18:56 CEST | 7h 36m | D-LZFN |
| 2026-04-16estimated | LOLW | LJSG | 08:35 CEST | 13:26 CEST | 4h 50m | D-LZFN |
| 2026-04-15 | EDNY | LOLW | 12:19 CEST | 17:56 CEST | 5h 36m | D-LZFN |
| 2026-04-11partial | EDNY | ? | 11:31 CEST | D-LZFN | ||
| 2026-04-06partial | EDNY | ? | 09:22 CEST | D-LZFN | ||
| 2026-04-04partial | EDNY | ? | 14:32 CEST | D-LZFN | ||
| 2026-04-03partial | EDNY | ? | 10:13 CEST | D-LZFN | ||
| 2026-04-02partial | EDNY | ? | 09:57 CEST | D-LZFN | ||
| 2026-03-13partial | EDNY | ? | 11:46 CET | D-LZFN |
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.
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]