Flight
GBRDD
Flight history and live tracking for GBRDD. 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 Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-16 | EGBP | EGBJ | 11:04 BST | 18:04 BST | 6h 59m | G-BRDD |
Earlier flights (17) - back to 2026-03-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18 | EGBP | EGBJ | 15:08 BST | 17:24 BST | 2h 15m | G-BRDD |
| 2026-07-17partial | EGBJ | ? | 17:36 BST | G-BRDD | ||
| 2026-07-12 | EGOS | EGBJ | 17:24 BST | 17:58 BST | 0h 33m | G-BRDD |
| 2026-07-06partial | EGBJ | ? | 20:23 BST | G-BRDD | ||
| 2026-07-05 | EGBP | EGBJ | 12:09 BST | 19:14 BST | 7h 04m | G-BRDD |
| 2026-07-04partial | EGBJ | ? | 11:51 BST | G-BRDD | ||
| 2026-06-20 | EGBP | EGBJ | 18:19 BST | 18:44 BST | 0h 24m | G-BRDD |
| 2026-06-15estimated | EGDM | EGBP | 12:33 BST | 13:32 BST | 0h 58m | G-BRDD |
| 2026-06-13estimated | EGBJ | EGDM | 10:17 BST | 11:00 BST | 0h 42m | G-BRDD |
| 2026-05-26 | EGTG | EGBJ | 20:28 BST | 21:02 BST | 0h 34m | G-BRDD |
| 2026-05-24 | EGBP | EGBJ | 12:06 BST | 20:14 BST | 8h 07m | G-BRDD |
| 2026-05-01estimated | EGHS | EGVA | 18:28 BST | 18:54 BST | 0h 25m | G-BRDD |
| 2026-04-30partial | EGBJ | ? | 10:53 BST | G-BRDD | ||
| 2026-04-28partial | EGBJ | ? | 14:47 BST | G-BRDD | ||
| 2026-04-27partial | EGBJ | ? | 10:15 BST | G-BRDD | ||
| 2026-04-26partial | EGBJ | ? | 11:46 BST | G-BRDD | ||
| 2026-03-14partial | EGBJ | ? | 12:20 GMT | G-BRDD |
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 GBRDD 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]