Flight
FZA6597
Flight history and live tracking for FZA6597, operated by Fuzhou Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Fuzhou Airlines |
| Typical origin | ZGHA HUANGHUA |
| Typical destination | ZJSY Sanya Phoenix International Airport |
| Distance | 629 nm |
Flight history 43 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-05estimated | ? | ? | 01:36Z | 13:26Z | 11h 50m | B-5182 |
| 2026-10-02estimated | ? | ? | 01:48Z | 02:26Z | 0h 37m | B-5182 |
| 2026-09-28estimated | ? | ? | 02:02Z | 07:22Z | 5h 20m | B-1906 |
| 2026-09-25estimated | ? | ? | 01:37Z | 13:06Z | 11h 28m | B-1906 |
| 2026-09-21estimated | ? | ? | 02:02Z | 02:42Z | 0h 39m | B-1905 |
| 2026-09-18estimated | ? | ? | 01:39Z | 02:16Z | 0h 36m | B-1480 |
| 2026-09-14estimated | ? | ? | 02:04Z | 07:06Z | 5h 02m | B-1351 |
| 2026-09-11estimated | ? | ? | 01:40Z | 02:12Z | 0h 31m | B-5182 |
Earlier flights (35) - back to 2026-01-27
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-07estimated | ? | ? | 01:58Z | 09:18Z | 7h 19m | B-1905 |
| 2026-09-04estimated | ? | ? | 01:25Z | 13:24Z | 11h 58m | B-1559 |
| 2026-08-31estimated | ? | ? | 02:06Z | 06:50Z | 4h 44m | B-5503 |
| 2026-08-28estimated | ? | ? | 01:54Z | 06:30Z | 4h 36m | B-1906 |
| 2026-08-24estimated | ? | ? | 02:16Z | 02:58Z | 0h 41m | B-1906 |
| 2026-08-21estimated | ? | ? | 01:51Z | 13:25Z | 11h 33m | B-1906 |
| 2026-08-17estimated | ? | ? | 01:49Z | 13:40Z | 11h 50m | B-5503 |
| 2026-08-14estimated | ? | ? | 01:39Z | 16:15Z | 14h 35m | B-1905 |
| 2026-07-17estimated | ? | ? | 02:21Z | 03:00Z | 0h 38m | B-5503 |
| 2026-07-13estimated | ? | ? | 02:07Z | 13:34Z | 11h 26m | B-1906 |
| 2026-07-10estimated | ZBTJ | ? | 09:52 CST | 09:14Z | 7h 21m | B-5430 |
| 2026-06-26estimated | ZBAA | ? | 09:37 CST | 06:46Z | 5h 09m | B-7377 |
| 2026-06-19estimated | ? | ? | 01:27Z | 13:16Z | 11h 49m | B-7377 |
| 2026-06-14estimated | ? | ? | 01:24Z | 13:20Z | 11h 55m | B-1905 |
| 2026-05-10estimated | ZBAA | ? | 09:28 CST | 02:04Z | 0h 35m | B-5503 |
| 2026-05-03estimated | ZBAA | ? | 09:40 CST | 02:18Z | 0h 37m | B-7377 |
| 2026-03-14estimated | ? | ? | 00:35Z | 01:14Z | 0h 38m | B-1433 |
| 2026-03-12estimated | ? | ? | 00:12Z | 00:46Z | 0h 33m | B-5503 |
| 2026-03-10estimated | ? | ? | 00:23Z | 01:02Z | 0h 39m | B-1906 |
| 2026-03-05estimated | ? | ? | 00:35Z | 00:58Z | 0h 22m | B-7395 |
| 2026-03-03estimated | ? | ? | 00:26Z | 01:08Z | 0h 41m | B-5430 |
| 2026-02-28estimated | ? | ? | 00:27Z | 01:06Z | 0h 38m | B-5430 |
| 2026-02-26estimated | ? | ? | 00:43Z | 01:28Z | 0h 44m | B-5430 |
| 2026-02-24estimated | ? | ? | 00:20Z | 00:58Z | 0h 38m | B-5430 |
| 2026-02-21estimated | ? | ? | 00:32Z | 01:16Z | 0h 43m | B-5430 |
| 2026-02-19estimated | ? | ? | 00:20Z | 00:42Z | 0h 22m | B-1435 |
| 2026-02-17estimated | ? | ? | 02:40Z | 03:20Z | 0h 39m | B-5430 |
| 2026-02-14estimated | ? | ? | 00:41Z | 01:20Z | 0h 38m | B-5430 |
| 2026-02-12estimated | ? | ? | 00:24Z | 01:04Z | 0h 39m | B-1562 |
| 2026-02-07estimated | ? | ? | 00:31Z | 01:10Z | 0h 38m | B-5430 |
| 2026-02-05estimated | ? | ? | 00:49Z | 01:30Z | 0h 41m | B-1562 |
| 2026-02-03estimated | ? | ? | 00:31Z | 01:08Z | 0h 36m | B-1559 |
| 2026-01-31estimated | ? | ? | 00:22Z | 01:06Z | 0h 43m | B-1562 |
| 2026-01-29estimated | ? | ? | 00:22Z | 00:56Z | 0h 33m | B-1562 |
| 2026-01-27estimated | ? | ? | 00:38Z | 05:36Z | 4h 58m | B-1562 |
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 FZA6597 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]