Flight
EPA6269
Flight history and live tracking for EPA6269, operated by Shenzhen Donghai Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Shenzhen Donghai Airlines |
| Observed route | ZGSZ → VHSK |
Flight history 50 flights since Feb 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21partial | ZGSZ | ? | 13:38 CST | 7822AB | ||
| 2026-08-14partial | ZGSZ | ? | 14:43 CST | B-1105 | ||
| 2026-08-12partial | ZGSZ | ? | 13:38 CST | B-7630 |
Earlier flights (47) - back to 2026-02-16
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22partial | ZGSZ | ? | 14:26 CST | B-1705 | ||
| 2026-07-20partial | ZGSZ | ? | 13:31 CST | B-1532 | ||
| 2026-07-19partial | ZGSZ | ? | 13:34 CST | B-1462 | ||
| 2026-07-17partial | ZGSZ | ? | 13:38 CST | B-7300 | ||
| 2026-07-15partial | ZGSZ | ? | 15:58 CST | B-7631 | ||
| 2026-07-13partial | ZGSZ | ? | 13:28 CST | 7823A4 | ||
| 2026-07-12partial | ZGSZ | ? | 13:36 CST | B-204N | ||
| 2026-07-10partial | ZGSZ | ? | 13:49 CST | B-1575 | ||
| 2026-07-08partial | ZGSZ | ? | 16:42 CST | B-1104 | ||
| 2026-07-06 | ZGSZ | VHSK | 14:01 CST | 07:16 HKT | 17h 15m | B-1104 |
| 2026-07-04 | ZGSZ | ZGGG | 08:39 CST | 19:31 CST | 10h 51m | B-1771 |
| 2026-07-01partial | ZGSZ | ? | 13:41 CST | B-7300 | ||
| 2026-06-29partial | ZGSZ | ? | 13:31 CST | 7822AB | ||
| 2026-06-24partial | ZGSZ | ? | 13:38 CST | B-204N | ||
| 2026-06-20estimated | ? | ? | 02:21Z | 05:40Z | 3h 18m | B-7100 |
| 2026-06-19 | ZGSZ | VHSK | 14:47 CST | 06:48 HKT | 16h 00m | B-1575 |
| 2026-06-17partial | ZGSZ | ? | 13:50 CST | B-1415 | ||
| 2026-06-15 | ZGSZ | VHSK | 15:44 CST | 06:54 HKT | 15h 10m | B-1415 |
| 2026-06-14partial | ZGSZ | ? | 15:06 CST | 7822AB | ||
| 2026-06-12partial | ZGSZ | ? | 13:50 CST | B-1575 | ||
| 2026-05-27 | ZGSZ | VHSK | 13:40 CST | 06:50 HKT | 17h 10m | 7822AB |
| 2026-05-25partial | ZGSZ | ? | 13:57 CST | B-1705 | ||
| 2026-05-22partial | ZGSZ | ? | 14:47 CST | B-7631 | ||
| 2026-05-20partial | ZGGG | ? | 08:30 CST | B-1770 | ||
| 2026-05-19partial | ZGSZ | ? | 10:17 CST | B-1590 | ||
| 2026-05-11 | ZGSZ | VHSK | 13:13 CST | 06:42 HKT | 17h 28m | B-1104 |
| 2026-05-10partial | ZGSZ | ? | 13:06 CST | 7822AB | ||
| 2026-05-08 | ZGSZ | VHSK | 13:27 CST | 07:00 HKT | 17h 32m | B-7630 |
| 2026-05-06 | ZGSZ | VHSK | 17:07 CST | 07:12 HKT | 14h 05m | 7822AB |
| 2026-05-04partial | ZGSZ | ? | 13:24 CST | B-7631 | ||
| 2026-05-03estimated | ZGSZ | VMMC | 14:26 CST | 01:16 CST | 10h 49m | B-7630 |
| 2026-05-01partial | ZGSZ | ? | 13:17 CST | B-1771 | ||
| 2026-04-30estimated | ZGSZ | ZGGG | 10:47 CST | 17:46 CST | 6h 58m | B-1533 |
| 2026-04-27partial | ZGSZ | ? | 13:14 CST | B-204N | ||
| 2026-04-26partial | ZGSZ | ? | 15:36 CST | B-1771 | ||
| 2026-04-24partial | ZGSZ | ? | 13:50 CST | B-7630 | ||
| 2026-04-22partial | ZGSZ | ? | 13:27 CST | B-1575 | ||
| 2026-04-20partial | ZGSZ | ? | 14:14 CST | B-1104 | ||
| 2026-04-16partial | ZGSZ | ? | 08:37 CST | B-1533 | ||
| 2026-04-13partial | ZGSZ | ? | 13:19 CST | B-1770 | ||
| 2026-04-12partial | ZGSZ | ? | 13:22 CST | B-1104 | ||
| 2026-04-06partial | ZGSZ | ? | 13:53 CST | B-1532 | ||
| 2026-04-03partial | ZGSZ | ? | 14:19 CST | B-1771 | ||
| 2026-04-01estimated | ? | ? | 05:11Z | 23:00Z | 17h 48m | B-1590 |
| 2026-03-30partial | ZGSZ | ? | 15:15 CST | 7823A4 | ||
| 2026-03-13partial | ZGSZ | ? | 13:10 CST | B-7631 | ||
| 2026-02-16 | ZGSZ | ? | 13:15 CST | 12:07Z | 6h 52m | 78123E |
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 EPA6269 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]