Flight
ABD2617
Flight history and live tracking for ABD2617. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 41 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-29estimated | EBLG | FOOM | 10:54 CEST | 11:40 WAT | 1h 45m | 9H-AKA |
| 2026-09-23estimated | EBLG | FOOM | 05:36 CEST | 07:50 WAT | 3h 13m | TF-AME |
| 2026-09-15estimated | ? | ? | 12:53Z | 13:36Z | 0h 42m | TF-AMM |
Earlier flights (38) - back to 2025-08-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-27estimated | ? | ? | 00:00Z | 01:00Z | 1h 00m | 4CC58A |
| 2026-08-26estimated | EBLG | FOOM | 01:09 CEST | 00:58 WAT | 0h 48m | 4CC58A |
| 2026-08-18estimated | ? | ? | 00:00Z | 08:16Z | 8h 15m | 9H-AKA |
| 2026-08-17estimated | EBLG | FOOM | 01:11 CEST | 00:58 WAT | 0h 47m | 9H-AKA |
| 2026-07-16estimated | EBLG | FOOM | 09:05 CEST | 17:10 WAT | 9h 04m | 4CC58A |
| 2026-07-09estimated | ? | ? | 01:25Z | 11:34Z | 10h 08m | TF-AMM |
| 2026-07-08estimated | EBLG | FOOM | 19:18 CEST | 19:58 WAT | 1h 39m | TF-AMM |
| 2026-06-30partial | ? | ? | 00:00Z | TF-AMU | ||
| 2026-06-29estimated | EBLG | FOOM | 00:23 CEST | 00:58 WAT | 1h 34m | TF-AMU |
| 2026-06-22estimated | EBLG | FOOM | 22:19 CEST | 22:50 WAT | 1h 30m | TF-AMU |
| 2026-06-14estimated | EBLG | FOOM | 11:56 CEST | 12:50 WAT | 1h 53m | TF-AME |
| 2026-05-26estimated | EBLG | FOOM | 14:13 CEST | 22:42 WAT | 9h 28m | 4CC58A |
| 2026-05-19estimated | EBLG | FGBT | 06:49 CEST | 07:44 WAT | 1h 54m | TF-AME |
| 2026-05-07estimated | FKKI | ? | 03:05 WAT | 11:14Z | 9h 09m | TF-AME |
| 2026-05-06estimated | EBLG | FOOM | 22:08 CEST | 22:50 WAT | 1h 41m | TF-AME |
| 2026-04-28estimated | EBLG | FOOM | 07:32 CEST | 08:22 WAT | 1h 49m | 4CC58A |
| 2026-04-21estimated | EBLG | FOOM | 11:24 CEST | 19:24 WAT | 8h 59m | 4CC58A |
| 2026-04-14estimated | ? | ? | 08:28Z | 09:00Z | 0h 31m | TF-AME |
| 2026-04-13estimated | EBLG | FOOM | 23:19 CEST | 00:00 WAT | 1h 40m | TF-AME |
| 2026-03-31estimated | EBLG | FOOM | 07:47 CEST | 08:14 WAT | 1h 26m | 4CC58A |
| 2026-03-05estimated | EBLG | FOOM | 03:44 CET | 05:44 WAT | 1h 59m | TF-AME |
| 2026-02-25estimated | EBLG | FOOM | 01:00 CET | 03:04 WAT | 2h 04m | TF-AME |
| 2026-02-18estimated | EBLG | FOOM | 22:54 CET | 00:59 WAT | 2h 05m | TF-AMM |
| 2026-02-10 | EBLG | ? | 03:04 CET | 03:16Z | 1h 12m | 4CC4BD |
| 2026-02-10estimated | EBLG | FOOM | 02:50 CET | 04:58 WAT | 2h 08m | TF-AMM |
| 2026-02-03estimated | EBLG | FOOM | 01:00 CET | 02:52 WAT | 1h 51m | TF-AME |
| 2026-01-26estimated | EBLG | FOOM | 23:09 CET | 00:58 WAT | 1h 48m | TF-AME |
| 2026-01-20estimated | ? | ? | 00:00Z | 01:20Z | 1h 20m | TF-AME |
| 2026-01-19estimated | EBLG | FOOM | 00:17 CET | 00:58 WAT | 0h 40m | TF-AME |
| 2026-01-06estimated | EBLG | FOOM | 02:12 CET | 04:20 WAT | 2h 08m | TF-AME |
| 2025-12-16estimated | ? | ? | 00:00Z | 01:50Z | 1h 50m | 4CC58A |
| 2025-12-15partial | EBLG | ? | 00:35 CET | 4CC58A | ||
| 2025-10-28estimated | EBLG | FOOM | 11:31 CET | 13:06 WAT | 1h 34m | 4CC58A |
| 2025-10-22estimated | EBLG | FOOM | 08:44 CEST | 20:24 WAT | 12h 39m | 4CC58A |
| 2025-10-14estimated | EBLG | FOOM | 14:24 CEST | 15:18 WAT | 1h 53m | TF-AMM |
| 2025-10-07estimated | EBLG | FOOM | 23:55 CEST | 00:48 WAT | 1h 53m | TF-AMU |
| 2025-08-21estimated | ? | ? | 00:00Z | 02:31Z | 2h 31m | TF-AME |
| 2025-08-20estimated | EBLG | FOOM | 22:13 CEST | 00:58 WAT | 3h 44m | TF-AME |
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 ABD2617 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 archive (from $9.99, with a free one-day sample). Questions: [email protected]