Flight
SUT8292
Flight history and live tracking for SUT8292. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Observed route | CYBL → CYVR |
Flight history 15 flights since May 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-17estimated | ? | ? | 18:43Z | 19:28Z | 0h 44m | C-FRJY |
| 2026-08-16estimated | ? | ? | 22:44Z | 23:18Z | 0h 33m | C-FRJY |
Earlier flights (13) - back to 2026-05-26
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-14estimated | CYBL | CYVR | 12:48 PDT | 13:18 PDT | 0h 29m | C-FRJY |
| 2026-07-12estimated | CYBL | CYVR | 14:06 PDT | 14:38 PDT | 0h 32m | C-FRJY |
| 2026-07-11estimated | CYBL | CYVR | 14:56 PDT | 15:26 PDT | 0h 29m | C-FRJY |
| 2026-07-05estimated | CYBL | CYVR | 15:05 PDT | 15:34 PDT | 0h 28m | C-FRJY |
| 2026-07-02estimated | CYCD | CYVR | 14:08 PDT | 14:32 PDT | 0h 23m | C-FRJY |
| 2026-06-27estimated | CYBL | CYVR | 14:52 PDT | 15:22 PDT | 0h 30m | C-FRJY |
| 2026-06-24estimated | CYCD | CYVR | 21:01 PDT | 21:26 PDT | 0h 24m | C-FRJY |
| 2026-06-21estimated | CYBL | CYVR | 16:16 PDT | 16:46 PDT | 0h 29m | C-FRJY |
| 2026-06-20partial | CYVR | ? | 14:16 PDT | C-FRJY | ||
| 2026-06-14estimated | CYBL | CYVR | 13:46 PDT | 14:16 PDT | 0h 29m | C-FRJY |
| 2026-05-28estimated | CYBL | CYVR | 22:44 PDT | 23:12 PDT | 0h 28m | C-FRJY |
| 2026-05-27estimated | CYBL | CYVR | 21:35 PDT | 22:08 PDT | 0h 32m | C-FRJY |
| 2026-05-26estimated | CYBL | CYVR | 18:09 PDT | 18:40 PDT | 0h 30m | C-FRJY |
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]