Position Info
Aircraft Info
Aircraft Model
Registration
Mode-S
Serial Number
4696
Last Activity
5 hours ago
Last Known Location
Huizhou, GD, China




























| Date | Flight | Origin | STD | ATD | Destination | STA | Delay | Status | Duration | Replay |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026 Feb 11 | Nanchong (NAO/ZUNC) | 21:31 CST | Departed | |||||||
| 2026 Feb 11 | First seen near Huizhou, GD, China | Status N/A | ||||||||
| 2026 Feb 11 | Chongqing (CKG/ZUCK) | 15:19 CST | Huizhou, GD (HUZ/ZGHZ) | 17:04 CST | Landed 17:01 CST Landing time derived from ADS-B/Radar data | 01h41m | ||||
| 2026 Feb 11 | Chongqing (CKG/ZUCK) | 08:22 CST | Departed | |||||||
| 2026 Feb 10 | Zhuhai (ZUH/ZGSD) | 20:57 CST | Chongqing (CKG/ZUCK) | 22:52 CST | Landed 22:53 CST Landing time derived from ADS-B/Radar data | 01h55m | ||||
| 2026 Feb 10 | Chongqing (CKG/ZUCK) | 17:49 CST | Zhuhai (ZUH/ZGSD) | 19:28 CST | Landed 19:30 CST Landing time derived from ADS-B/Radar data | 01h41m | ||||
| 2026 Feb 10 | Nanjing (NKG/ZSNJ) | Chongqing (CKG/ZUCK) | Landed 15:37 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 10 | Chongqing (CKG/ZUCK) | 10:29 CST | Last seen near Nanjing, China | Landed | ||||||
| 2026 Feb 9 | First seen near Beijing, BJ, China | Last seen near Xinzhu, China | Landed | |||||||
| 2026 Feb 9 | Chongqing (CKG/ZUCK) | 14:25 CST | Beijing, BJ (PKX/ZBAD) | 16:23 CST | Landed 16:22 CST Landing time derived from ADS-B/Radar data | 01h57m | ||||
| 2026 Feb 9 | Xianyang (XIY/ZLXY) | 11:20 CST | Last seen near Xi'an, China | Landed | ||||||
| 2026 Feb 9 | Chongqing (CKG/ZUCK) | 08:25 CST | Last seen near Chongqing, China | Landed | ||||||
| 2026 Feb 8 | Guangzhou (CAN/ZGGG) | 22:30 CST | Last seen near Guangzhou, China | Landed | ||||||
| 2026 Feb 8 | Lijiang (LJG/ZPLJ) | 18:35 CST | Foshan, GD (FUO/ZGFS) | Landed 20:08 CST Landing time derived from ADS-B/Radar data | 01h33m | |||||
| 2026 Feb 8 | Guangzhou (CAN/ZGGG) | 14:55 CST | Lijiang (LJG/ZPLJ) | 17:31 CST | Landed 17:27 CST Landing time derived from ADS-B/Radar data | 02h32m | ||||
| 2026 Feb 8 | Guangzhou (CAN/ZGGG) | 07:48 CST | Jinghong (JHG/ZPJH) | 10:24 CST | Landed 10:23 CST Landing time derived from ADS-B/Radar data | 02h34m | ||||
| 2026 Feb 7 | Shijiazhuang (SJW/ZBSJ) | 20:09 CST | Last seen near Foshan, GD, China | Landed | ||||||
| 2026 Feb 7 | Guangzhou (CAN/ZGGG) | 16:23 CST | Last seen near Shijiazhuang, China | Landed | ||||||
| 2026 Feb 7 | First seen near Jinghong, China | Foshan, GD (FUO/ZGFS) | Landed 13:35 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 7 | Guangzhou (CAN/ZGGG) | 07:41 CST | Jinghong (JHG/ZPJH) | 10:17 CST | Landed 10:15 CST Landing time derived from ADS-B/Radar data | 02h34m | ||||
| 2026 Feb 6 | First seen near Jinghong, China | Foshan, GD (FUO/ZGFS) | Landed 23:30 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 6 | Guangzhou (CAN/ZGGG) | 17:34 CST | Jinghong (JHG/ZPJH) | 20:08 CST | Landed 20:21 CST Landing time derived from ADS-B/Radar data | 02h46m | ||||
| 2026 Feb 6 | Tianjin (TSN/ZBTJ) | 12:34 CST | Foshan, GD (FUO/ZGFS) | Landed 15:39 CST Landing time derived from ADS-B/Radar data | 03h05m | |||||
| 2026 Feb 6 | First seen near Guangzhou, China | Last seen near Tianjin, China | Landed | |||||||
| 2026 Feb 5 | First seen near Jinghong, China | Guangzhou (CAN/ZGGG) | Landed 22:55 CST Landing time derived from ADS-B/Radar data | |||||||
| 2026 Feb 5 | Guangzhou (CAN/ZGGG) | 17:25 CST | Jinghong (JHG/ZPJH) | 19:59 CST | Landed 20:08 CST Landing time derived from ADS-B/Radar data | 02h42m | ||||
| 2026 Feb 5 | Tianjin (TSN/ZBTJ) | 12:33 CST | Foshan, GD (FUO/ZGFS) | Landed 15:25 CST Landing time derived from ADS-B/Radar data | 02h51m | |||||
| 2026 Feb 5 | Guangzhou (CAN/ZGGG) | 08:28 CST | Tianjin (TSN/ZBTJ) | 11:04 CST | Landed 11:00 CST Landing time derived from ADS-B/Radar data | 02h31m |
Flight history for B-6761 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.