Flight
DEPIQ
Flight history and live tracking for DEPIQ. 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 Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-16estimated | ? | ? | 10:28Z | 12:40Z | 2h 11m | 3D2D24 |
| 2026-08-13estimated | ? | ? | 13:44Z | 15:44Z | 1h 59m | 3D2D24 |
| 2026-08-12estimated | EDDK | ? | 15:30 CEST | 15:06Z | 1h 35m | 3D2D24 |
Earlier flights (14) - back to 2026-04-06
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-06-27 | ETSL | EDMA | 11:18 CEST | 15:42 CEST | 4h 24m | 3D2D24 |
| 2026-06-26estimated | EDLN | ETSL | 16:57 CEST | 18:56 CEST | 1h 58m | 3D2D24 |
| 2026-06-25 | ETSL | EDLN | 07:40 CEST | 09:44 CEST | 2h 04m | 3D2D24 |
| 2026-06-21estimated | EDFE | EDPA | 17:19 CEST | 18:22 CEST | 1h 02m | 3D2D24 |
| 2026-06-20estimated | ETSL | ETIE | 12:00 CEST | 12:58 CEST | 0h 57m | 3D2D24 |
| 2026-05-29estimated | EDDK | ETSL | 16:05 CEST | 17:48 CEST | 1h 42m | 3D2D24 |
| 2026-05-25estimated | EDGS | EDDK | 11:44 CEST | 16:22 CEST | 4h 38m | 3D2D24 |
| 2026-05-24estimated | ETSL | EDFQ | 11:26 CEST | 13:08 CEST | 1h 41m | 3D2D24 |
| 2026-05-22estimated | ? | ? | 11:24Z | 11:44Z | 0h 20m | 3D2D24 |
| 2026-05-19 | ETSL | ETSF | 04:16 CEST | 05:38 CEST | 1h 21m | 3D2D24 |
| 2026-04-22estimated | ? | ? | 12:51Z | 14:42Z | 1h 50m | 3D2D24 |
| 2026-04-19 | EDKA | ? | 14:01 CEST | 13:54Z | 1h 52m | 3D2D24 |
| 2026-04-18 | ? | EDKA | 08:41Z | 12:48 CEST | 2h 06m | 3D2D24 |
| 2026-04-06estimated | ? | ? | 09:47Z | 16:20Z | 6h 32m | 3D2D24 |
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]