Flight
KLM998
Flight history and live tracking for KLM998, operated by KLM Royal Dutch Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | KLM Royal Dutch Airlines |
| Typical origin | EGLC CITY |
| Typical destination | EHAM SCHIPHOL |
| Distance | 181 nm |
Flight history 13 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (13) - back to 2026-04-05
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-19estimated | EGLC | EHAM | 21:16 BST | 22:52 CEST | 0h 35m | PH-EXF |
| 2026-07-12 | EGLC | EHAM | 21:09 BST | 22:52 CEST | 0h 43m | PH-EZN |
| 2026-07-05 | EGLC | EHAM | 21:30 BST | 23:16 CEST | 0h 45m | PH-EXY |
| 2026-06-28 | EGLC | EHAM | 20:43 BST | 22:36 CEST | 0h 52m | PH-EXE |
| 2026-06-21 | EGLC | EHAM | 20:55 BST | 22:32 CEST | 0h 36m | PH-EZH |
| 2026-06-14 | EGLC | EHAM | 20:56 BST | 22:38 CEST | 0h 41m | PH-EZS |
| 2026-05-24 | EGLC | EHAM | 20:47 BST | 22:30 CEST | 0h 43m | PH-EZR |
| 2026-05-10 | EGLC | EHAM | 20:52 BST | 22:34 CEST | 0h 41m | PH-EZR |
| 2026-05-03 | EGLC | EHAM | 20:45 BST | 22:26 CEST | 0h 40m | PH-EZO |
| 2026-04-26 | EGLC | EHAM | 20:57 BST | 22:34 CEST | 0h 37m | PH-EZG |
| 2026-04-19estimated | EGLC | EHAM | 20:53 BST | 22:34 CEST | 0h 40m | PH-EXE |
| 2026-04-12 | EGLC | EHAM | 21:10 BST | 22:58 CEST | 0h 47m | PH-EZP |
| 2026-04-05estimated | EGLC | EHAM | 20:41 BST | 22:24 CEST | 0h 43m | PH-EZM |
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 KLM998 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]