Flight
DEFLP
Flight history and live tracking for DEFLP. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 17 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (17) - back to 2026-03-15
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-17partial | EDLW | ? | 11:14 CEST | D-EFLP | ||
| 2026-07-12estimated | EDLW | ETUO | 10:17 CEST | 16:56 CEST | 6h 38m | D-EFLP |
| 2026-07-11 | EDLW | ETUO | 09:24 CEST | 10:30 CEST | 1h 05m | D-EFLP |
| 2026-07-06estimated | EDLA | EDLW | 10:58 CEST | 19:46 CEST | 8h 47m | D-EFLP |
| 2026-07-04partial | EDLW | ? | 14:42 CEST | D-EFLP | ||
| 2026-07-02estimated | EDLW | ETHB | 10:54 CEST | 11:48 CEST | 0h 53m | D-EFLP |
| 2026-06-26partial | EDLW | ? | 17:28 CEST | D-EFLP | ||
| 2026-06-24partial | EDLW | ? | 18:01 CEST | D-EFLP | ||
| 2026-06-23partial | EDLW | ? | 19:59 CEST | D-EFLP | ||
| 2026-06-19estimated | EDLW | EDDG | 10:59 CEST | 19:54 CEST | 8h 54m | D-EFLP |
| 2026-06-17 | EDLE | EDDK | 11:24 CEST | 12:16 CEST | 0h 51m | D-EFLP |
| 2026-05-24estimated | ETNJ | EDDG | 16:25 CEST | 17:00 CEST | 0h 35m | D-EFLP |
| 2026-04-26partial | EDLW | ? | 17:25 CEST | D-EFLP | ||
| 2026-04-21 | EDVM | EDLW | 19:59 CEST | 20:50 CEST | 0h 50m | D-EFLP |
| 2026-04-06partial | EDLW | ? | 10:58 CEST | D-EFLP | ||
| 2026-04-03partial | EDLW | ? | 10:20 CEST | D-EFLP | ||
| 2026-03-15partial | EDLW | ? | 13:56 CET | D-EFLP |
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 DEFLP 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]