| ARRIVED 150 HOUR 11 MINUTES AGO |
 |  |
Departure (JD385 Flight Schedule)
Hangzhou, ChinaHKT 00:00:00 DAY
Arrival (JD385 Flight Schedule)
Melbourne, AustraliaAEDT 00:00:00 DAY
Flight Radar Checker JD 385
Live Flight Tracker Map
Flight JD385 from Hangzhou to Melbourne is operated by Beijing Capital Airlines. Scheduled time of departure from Xiaoshan is 16:00 HKT and scheduled time of arrival in Melbourne Intl is 06:00 AEDT. The duration of the flight is 11 hours 0 minute.
History Flight Information for JD385 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Fri, 13 Nov | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 16:00 HKT | 06:00 AEDT | |||
| Fri, 06 Nov | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 16:00 HKT | 06:00 AEDT | B-8679 (Airbus A333) | 17:11 HKT | 05:15 AEDT |
| Fri, 30 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 16:00 HKT | 06:00 AEDT | 00:36 HKT | 06:22 AEDT | |
| Fri, 23 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | 00:59 HKT | 06:20 AEDT | |
| Wed, 21 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | 20:01 HKT | 06:34 AEDT | |
| Wed, 14 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | 19:54 HKT | 06:29 AEDT | |
| Sun, 11 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | 18:51 HKT | 06:27 AEDT | |
| Fri, 09 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | B-8981 (Airbus A332) | 18:39 HKT | 06:32 AEDT |
| Wed, 07 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 06:00 AEDT | 01:09 HKT | 06:35 AEDT | |
| Sun, 04 Oct | JD385 | Xiaoshan (HGH) | Melbourne Intl (MEL) | 17:15 HKT | 05:00 AEDT | 19:09 HKT | 06:35 AEDT | |
Disclaimer for JD385 Flight Radar Data
Flight JD385 from Xiaoshan to Melbourne Intl data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight JD385 data.
