Flight
GAXNS
Flight history and live tracking for GAXNS. 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 Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21partial | EGNE | ? | 11:34 BST | G-AXNS | ||
| 2026-08-19 | EGCJ | EGNE | 14:53 BST | 15:28 BST | 0h 34m | G-AXNS |
Earlier flights (16) - back to 2026-04-27
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23partial | EGCN | ? | 11:15Z | G-AXNS | ||
| 2026-07-22estimated | EGNU | EGCN | 14:16 BST | 15:38Z | 2h 21m | G-AXNS |
| 2026-07-19estimated | ? | ? | 09:57Z | 14:02Z | 4h 04m | G-AXNS |
| 2026-07-18partial | EGCN | ? | 09:09Z | G-AXNS | ||
| 2026-07-17partial | EGCN | ? | 14:15Z | G-AXNS | ||
| 2026-06-25estimated | EGCF | EGXP | 09:43 BST | 10:28 BST | 0h 44m | G-AXNS |
| 2026-06-24partial | EGNE | ? | 16:04 BST | G-AXNS | ||
| 2026-06-24 | EGCF | EGNE | 10:40 BST | 16:40 BST | 5h 59m | G-AXNS |
| 2026-05-29estimated | EGJJ | EGBN | 09:23 BST | 16:06 BST | 6h 42m | G-AXNS |
| 2026-05-28estimated | EGBN | EGJJ | 08:53 BST | 14:46 BST | 5h 52m | G-AXNS |
| 2026-05-27estimated | EGBN | EGCF | 12:04 BST | 15:36 BST | 3h 31m | G-AXNS |
| 2026-05-24estimated | EGBN | EGCF | 11:39 BST | 15:08 BST | 3h 28m | G-AXNS |
| 2026-05-23estimated | EGCD | EGSY | 11:25 BST | 16:14 BST | 4h 49m | G-AXNS |
| 2026-05-22partial | EGCN | ? | 09:21Z | G-AXNS | ||
| 2026-05-20estimated | EGCF | EGXW | 01:24 BST | 15:50 BST | 14h 25m | G-AXNS |
| 2026-04-27estimated | EGNX | EGXW | 10:49 BST | 13:30 BST | 2h 40m | G-AXNS |
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.
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]