Facebook
X
Position Info
Aircraft Info
Aircraft Model
Registration
Mode-S
Serial Number
4365
Last Activity
3 hours ago
Last Known Location
Yichang, China
| Date | Flight | Origin | STD | ATD | Destination | STA | Delay | Status | Duration | Replay |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026 Feb 11 | First seen near Jingzhou, China | Status N/A | ||||||||
| 2026 Feb 11 | Chongqing (CKG/ZUCK) | 16:40 CST | Departed | |||||||
| 2026 Feb 11 | Chongqing (CKG/ZUCK) | 08:19 CST | Chongqing (CKG/ZUCK) | Landed 14:37 CST Landing time derived from ADS-B/Radar data | 06h18m | |||||
| 2026 Feb 10 | First seen near Ningbo, China | Last seen near Jingdezhen, China | Status N/A | |||||||
| 2026 Feb 10 | Chongqing (CKG/ZUCK) | 18:40 CST | Ningbo (NGB/ZSNB) | Landed 20:33 CST Landing time derived from ADS-B/Radar data | 01h53m | |||||
| 2026 Feb 10 | Huizhou, GD (HUZ/ZGHZ) | Chongqing (CKG/ZUCK) | Landed 17:16 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 10 | Jianyang, Chengdu (TFU/ZUTF) | Huizhou, GD (HUZ/ZGHZ) | Landed 14:16 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 10 | Huizhou, GD (HUZ/ZGHZ) | 07:54 CST | Jianyang, Chengdu (TFU/ZUTF) | 10:05 CST | Landed 10:10 CST Landing time derived from ADS-B/Radar data | 02h15m | ||||
| 2026 Feb 9 | Nanchong (NAO/ZUNC) | 22:05 CST | Last seen near Huizhou, GD, China | Landed | ||||||
| 2026 Feb 9 | First seen near Huizhou, GD, China | Last seen near Nanchong, China | Landed | |||||||
| 2026 Feb 9 | Chongqing (CKG/ZUCK) | 15:41 CST | Huizhou, GD (HUZ/ZGHZ) | 17:26 CST | Landed 17:25 CST Landing time derived from ADS-B/Radar data | 01h44m | ||||
| 2026 Feb 9 | Nanjing (NKG/ZSNJ) | Chongqing (CKG/ZUCK) | Landed 14:03 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 9 | Chongqing (CKG/ZUCK) | 08:01 CST | Last seen near Chongqing, China | Landed | ||||||
| 2026 Feb 8 | Chongqing (CKG/ZUCK) | 14:35 CST | Yining (YIN/ZWYN) | 19:04 CST | Landed 18:44 CST Landing time derived from ADS-B/Radar data | 04h08m | ||||
| 2026 Feb 8 | First seen near Renhuai City, GZ, China | Chongqing (CKG/ZUCK) | Landed 12:22 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 8 | Chongqing (CKG/ZUCK) | 08:31 CST | Last seen near Chongqing, China | Landed | ||||||
| 2026 Feb 7 | Chongqing (CKG/ZUCK) | 20:08 CST | Jinghong (JHG/ZPJH) | 21:57 CST | Landed 21:57 CST Landing time derived from ADS-B/Radar data | 01h49m | ||||
| 2026 Feb 7 | Guangzhou (CAN/ZGGG) | 15:48 CST | Chongqing (CKG/ZUCK) | 17:29 CST | Landed 17:25 CST Landing time derived from ADS-B/Radar data | 01h37m | ||||
| 2026 Feb 7 | Chongqing (CKG/ZUCK) | 12:45 CST | Foshan, GD (FUO/ZGFS) | Landed 14:05 CST Landing time derived from ADS-B/Radar data | 01h20m | |||||
| 2026 Feb 7 | Taizhou (HYN/ZSLQ) | 07:48 CST | Last seen near Yichun, JX, China | Landed | ||||||
| 2026 Feb 6 | First seen near Taizhou, China | Last seen near Wenzhou, China | Landed | |||||||
| 2026 Feb 6 | Shenzhen (SZX/ZGSZ) | 15:20 CST | Taizhou (HYN/ZSLQ) | 17:01 CST | Landed | |||||
| 2026 Feb 6 | Taizhou (HYN/ZSLQ) | 12:37 CST | Shenzhen (SZX/ZGSZ) | 14:24 CST | Landed 14:29 CST Landing time derived from ADS-B/Radar data | 01h51m | ||||
| 2026 Feb 6 | Chongqing (CKG/ZUCK) | 08:56 CST | Taizhou (HYN/ZSLQ) | 11:02 CST | Landed | |||||
| 2026 Feb 5 | Sanya (SYX/ZJSY) | 21:55 CST | Chongqing (CKG/ZUCK) | 23:55 CST | Landed 23:54 CST Landing time derived from ADS-B/Radar data | 01h58m | ||||
| 2026 Feb 5 | Chongqing (CKG/ZUCK) | 17:58 CST | Sanya (SYX/ZJSY) | 20:19 CST | Landed 20:07 CST Landing time derived from ADS-B/Radar data | 02h09m | ||||
| 2026 Feb 5 | Shanghai (PVG/ZSPD) | 12:24 CST | Chongqing (CKG/ZUCK) | 15:00 CST | Landed 15:05 CST Landing time derived from ADS-B/Radar data | 02h41m | ||||
| 2026 Feb 5 | Chongqing (CKG/ZUCK) | 08:36 CST | Shanghai (PVG/ZSPD) | 10:27 CST | Landed 10:23 CST Landing time derived from ADS-B/Radar data | 01h47m |
Flight history for B-6681 is available for a period over 7 days under our Basic subscription. More details here
More airport data is available for purchase. Please check our On Demand API.