Flight
BRK99
Flight history and live tracking for BRK99. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 18 flights since Dec 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-14 | KPSM | LHPA | 22:14 EDT | 17:06 CEST | 12h 51m | 02 |
Earlier flights (17) - back to 2025-12-11
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-19partial | LHPA | ? | 10:47 CEST | 01 | ||
| 2026-08-16 | ESOE | LHPA | 11:18 CEST | 16:06 CEST | 4h 47m | 01 |
| 2026-07-06partial | LHPA | ? | 15:47 CEST | 03 | ||
| 2026-07-06partial | LHPA | ? | 10:03 CEST | 03 | ||
| 2026-02-20 | EDDN | LHPA | 14:23 CET | 15:24 CET | 1h 00m | 01 |
| 2026-02-20partial | EDDN | ? | 11:07 CET | 01 | ||
| 2026-02-19estimated | ? | EDDN | 16:10Z | 18:16 CET | 1h 06m | 01 |
| 2026-02-19partial | EDDN | ? | 14:15 CET | 01 | ||
| 2026-02-19estimated | ? | ? | 09:42Z | 10:42Z | 1h 00m | 01 |
| 2026-02-18 | ETAR | EDDN | 15:14 CET | 18:32 CET | 3h 17m | 01 |
| 2026-02-18 | LIPA | ETAR | 14:13 CET | 15:14 CET | 1h 01m | 01 |
| 2026-02-18partial | LIPA | ? | 10:46 CET | 01 | ||
| 2026-02-17partial | LIPA | ? | 16:06 CET | 01 | ||
| 2026-02-17partial | LIPA | ? | 12:52 CET | 01 | ||
| 2026-02-17 | LHPA | LIPA | 08:06 CET | 08:56 CET | 0h 49m | 01 |
| 2025-12-11 | KPSM | KSKF | 15:54 EST | 18:58 CST | 4h 04m | 477FF2 |
| 2025-12-11 | LHPA | KPSM | 11:08 CET | 14:16 EST | 9h 07m | 02 |
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 BRK99 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]