Flight
DLH288
Flight history and live tracking for DLH288, operated by Lufthansa. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Lufthansa |
| Typical origin | EDDF FRANKFURT MAIN |
| Typical destination | LIPE BOLOGNA |
| Distance | 348 nm |
Flight history 43 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (43) - back to 2026-03-29
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-05-28 | EDDF | LIPE | 22:29 CEST | 23:32 CEST | 1h 02m | D-AISV |
| 2026-05-27 | EDDF | LIPE | 22:22 CEST | 23:30 CEST | 1h 07m | D-AIUA |
| 2026-05-26 | EDDF | LIPE | 21:55 CEST | 22:54 CEST | 0h 58m | D-AIBE |
| 2026-05-25 | EDDF | LIPE | 22:37 CEST | 23:44 CEST | 1h 07m | D-AILH |
| 2026-05-24partial | LIPE | ? | 06:17 CEST | D-AIBC | ||
| 2026-05-23 | EDDF | LIPE | 22:17 CEST | 23:16 CEST | 0h 59m | D-AIBC |
| 2026-05-22estimated | EDDF | LIPE | 22:36 CEST | 23:40 CEST | 1h 03m | D-AIZF |
| 2026-05-21 | EDDF | LIPE | 22:23 CEST | 23:20 CEST | 0h 56m | D-AILN |
| 2026-05-20partial | EDDF | ? | 03:33 CEST | D-AIDJ | ||
| 2026-05-19partial | LIPE | ? | 04:08 CEST | D-AILN | ||
| 2026-05-12partial | LIPE | ? | 06:14 CEST | D-AIBH | ||
| 2026-05-11partial | LIPE | ? | 06:35 CEST | D-AIZD | ||
| 2026-05-10partial | LIPE | ? | 06:24 CEST | D-AIZI | ||
| 2026-05-09partial | LIPE | ? | 06:13 CEST | D-AILH | ||
| 2026-05-08 | EDDF | LIPE | 22:23 CEST | 23:32 CEST | 1h 08m | D-AILH |
| 2026-05-07 | EDDF | LIPE | 22:44 CEST | 23:46 CEST | 1h 01m | D-AIBG |
| 2026-05-06 | EDDF | LIPE | 22:54 CEST | 23:58 CEST | 1h 04m | D-AIBC |
| 2026-05-05 | EDDF | LIPE | 22:10 CEST | 23:14 CEST | 1h 03m | D-AIBF |
| 2026-05-04partial | LIPE | ? | 06:35 CEST | D-AIEP | ||
| 2026-05-03 | EDDF | LIPE | 22:17 CEST | 23:22 CEST | 1h 04m | D-AIEP |
| 2026-05-02estimated | LIPE | ? | 06:09 CEST | 20:48Z | 16h 39m | D-AIZD |
| 2026-05-01partial | LIPE | ? | 06:15 CEST | D-AIZD | ||
| 2026-04-30 | EDDF | LIPE | 22:28 CEST | 23:40 CEST | 1h 11m | D-AIZD |
| 2026-04-29 | EDDF | LIPE | 22:36 CEST | 23:38 CEST | 1h 01m | D-AIZC |
| 2026-04-28 | EDDF | LIPE | 22:00 CEST | 23:02 CEST | 1h 01m | D-AIBJ |
| 2026-04-27 | EDDF | LIPE | 22:29 CEST | 23:34 CEST | 1h 04m | D-AILI |
| 2026-04-26 | EDDF | LIPE | 22:18 CEST | 23:14 CEST | 0h 55m | D-AIBF |
| 2026-04-25 | EDDF | LIPE | 22:15 CEST | 23:14 CEST | 0h 58m | D-AIBJ |
| 2026-04-24 | EDDF | LIPE | 22:24 CEST | 23:26 CEST | 1h 01m | D-AILI |
| 2026-04-23 | EDDF | LIPE | 22:39 CEST | 23:54 CEST | 1h 14m | D-AIZD |
| 2026-04-22estimated | EDDF | LIPE | 22:22 CEST | 23:32 CEST | 1h 09m | D-AILK |
| 2026-04-21 | EDDF | LIPE | 21:51 CEST | 22:46 CEST | 0h 54m | D-AILF |
| 2026-04-20 | EDDF | LIPE | 22:20 CEST | 23:38 CEST | 1h 17m | D-AIBE |
| 2026-04-19estimated | EDDF | LIPE | 22:10 CEST | 23:40 CEST | 1h 30m | D-AILM |
| 2026-04-18 | EDDF | LIPE | 21:58 CEST | 22:58 CEST | 0h 59m | D-AILM |
| 2026-04-12partial | LIPE | ? | 06:20 CEST | D-AILM | ||
| 2026-04-11estimated | EDDF | LIPE | 22:15 CEST | 23:12 CEST | 0h 57m | D-AILM |
| 2026-04-04 | EDDF | LIPE | 22:02 CEST | 23:02 CEST | 0h 59m | D-AIBI |
| 2026-04-03 | EDDF | LIPE | 22:29 CEST | 23:32 CEST | 1h 02m | D-AILM |
| 2026-04-02 | EDDF | LIPE | 22:30 CEST | 23:40 CEST | 1h 09m | D-AILU |
| 2026-03-31 | EDDF | LIPE | 21:59 CEST | 23:04 CEST | 1h 04m | D-AILM |
| 2026-03-30 | EDDF | LIPE | 23:04 CEST | 00:04 CEST | 0h 59m | D-AIST |
| 2026-03-29estimated | EDDF | LIPE | 22:48 CEST | 23:24 CEST | 0h 35m | D-AIBB |
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 DLH288 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]