Not currently tracked · last seen 1h ago
- Flights observed
- 90 showing last 50
- Avg flight time
- 11h 52m
- Typical route
- SYX → CAN
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-17 | SYX → PVG | Jul 17, 15:55 UTC | Jul 18, 01:20 UTC | 9h 25m |
| 2026-07-17 | SYX → CAN | Jul 17, 13:55 UTC | Jul 17, 14:04 UTC | 10m |
| 2026-07-17 | - | Jul 17, 05:10 UTC | Jul 17, 10:55 UTC | 5h 45m |
| 2026-07-16 | - | Jul 16, 10:50 UTC | Jul 17, 10:44 UTC | 23h 55m |
| 2026-07-15 | - | Jul 15, 14:45 UTC | Jul 16, 06:25 UTC | 15h 40m |
| 2026-07-15 | - | Jul 15, 09:35 UTC | Jul 16, 06:25 UTC | 20h 50m |
| 2026-07-15 | - | Jul 15, 06:05 UTC | Jul 16, 01:25 UTC | 19h 20m |
| 2026-07-14 | - | Jul 14, 14:20 UTC | Jul 15, 09:55 UTC | 19h 34m |
| 2026-07-14 | - | Jul 14, 10:15 UTC | Jul 15, 06:25 UTC | 20h 9m |
| 2026-07-14 | - | Jul 14, 06:50 UTC | Jul 15, 06:25 UTC | 23h 34m |
| 2026-07-14 | - | Jul 14, 01:45 UTC | Jul 14, 14:35 UTC | 12h 50m |
| 2026-07-13 | - | Jul 13, 11:50 UTC | Jul 14, 10:20 UTC | 22h 30m |
| 2026-07-13 | - | Jul 13, 07:05 UTC | Jul 14, 06:45 UTC | 23h 40m |
| 2026-07-13 | - | Jul 13, 04:10 UTC | Jul 14, 02:40 UTC | 22h 30m |
| 2026-07-12 | - | Jul 12, 15:35 UTC | Jul 12, 15:55 UTC | 20m |
| 2026-07-12 | - | Jul 12, 02:10 UTC | Jul 12, 10:01 UTC | 7h 50m |
| 2026-07-11 | - | Jul 11, 05:45 UTC | Jul 11, 14:15 UTC | 8h 30m |
| 2026-07-10 | - | Jul 10, 09:30 UTC | Jul 11, 06:10 UTC | 20h 40m |
| 2026-07-10 | - | Jul 10, 06:50 UTC | Jul 11, 06:10 UTC | 23h 20m |
| 2026-07-10 | - | Jul 10, 01:20 UTC | Jul 10, 10:20 UTC | 9h 0m |
| 2026-07-09 | - | Jul 9, 08:10 UTC | Jul 10, 06:45 UTC | 22h 35m |
| 2026-07-08 | - | Jul 8, 15:45 UTC | Jul 8, 16:10 UTC | 25m |
| 2026-07-08 | - | Jul 8, 13:50 UTC | Jul 8, 14:05 UTC | 15m |
| 2026-07-08 | - | Jul 8, 10:15 UTC | Jul 8, 10:45 UTC | 30m |
| 2026-07-07 | PKX → SYX | Jul 7, 16:50 UTC | Jul 7, 17:10 UTC | 20m |
| 2026-07-07 | PKX → SYX | Jul 7, 14:15 UTC | Jul 7, 14:25 UTC | 10m |
| 2026-07-06 | - | Jul 6, 10:50 UTC | Jul 6, 11:10 UTC | 20m |
| 2026-07-05 | - | Jul 5, 17:15 UTC | Jul 6, 09:00 UTC | 15h 45m |
| 2026-07-05 | - | Jul 5, 09:20 UTC | Jul 6, 08:45 UTC | 23h 25m |
| 2026-07-04 | - | Jul 4, 14:15 UTC | Jul 5, 09:25 UTC | 19h 10m |
| 2026-07-03 | - | Jul 3, 22:55 UTC | Jul 4, 14:35 UTC | 15h 40m |
| 2026-07-02 | - | Jul 2, 11:00 UTC | Jul 2, 11:10 UTC | 10m |
| 2026-07-02 | - | Jul 2, 00:10 UTC | Jul 2, 08:20 UTC | 8h 10m |
| 2026-06-30 | - | Jun 30, 05:05 UTC | Jun 30, 10:45 UTC | 5h 40m |
| 2026-06-28 | - | Jun 28, 13:55 UTC | Jun 28, 14:04 UTC | 10m |
| 2026-06-28 | SYX → CAN | Jun 28, 11:04 UTC | Jun 28, 12:09 UTC | 1h 5m |
| 2026-06-28 | TFU → SYX | Jun 28, 01:04 UTC | Jun 28, 06:15 UTC | 5h 10m |
| 2026-06-27 | - | Jun 27, 04:15 UTC | Jun 28, 01:34 UTC | 21h 20m |
| 2026-06-26 | DQA → CSX | Jun 26, 09:10 UTC | Jun 27, 04:44 UTC | 19h 35m |
| 2026-06-26 | - | Jun 26, 06:29 UTC | Jun 26, 06:45 UTC | 15m |
| 2026-06-14 | - | Jun 14, 15:40 UTC | Jun 14, 15:55 UTC | 15m |
| 2026-06-12 | CAN → SYX | Jun 12, 06:45 UTC | Jun 12, 10:20 UTC | 3h 35m |
| 2026-06-11 | CAN → SYX | Jun 11, 10:50 UTC | Jun 12, 10:20 UTC | 23h 31m |
| 2026-06-11 | KWE → SYX | Jun 11, 10:40 UTC | Jun 12, 07:15 UTC | 20h 36m |
| 2026-06-10 | KWE → SYX | Jun 10, 13:35 UTC | Jun 11, 11:05 UTC | 21h 30m |
| 2026-06-08 | CAN → SYX | Jun 8, 07:25 UTC | Jun 8, 07:50 UTC | 25m |
| 2026-06-07 | SYX → CAN | Jun 7, 06:30 UTC | Jun 7, 10:05 UTC | 3h 35m |
| 2026-06-06 | PVG → SYX | Jun 6, 05:10 UTC | Jun 6, 11:14 UTC | 6h 5m |
| 2026-06-05 | PVG → SYX | Jun 5, 10:50 UTC | Jun 6, 10:45 UTC | 23h 55m |
| 2026-06-05 | PVG → SYX | Jun 5, 10:30 UTC | Jun 6, 06:25 UTC | 19h 55m |
Specifications
| Registration | B-6683 |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 780673 · 36003163 (octal) |
Looking for transponder-level data? View the Mode-S 780673 page for country allocation, callsign history, and ADS-B signal details.
B-6683 frequently asked
What type of aircraft is B-6683?
B-6683 is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for B-6683?
B-6683 broadcasts on Mode-S (ICAO 24-bit) address 780673 (octal 36003163). View the transponder page.
What route does B-6683 typically fly?
B-6683 most frequently flies between SYX and CAN based on observed flights.
Where is B-6683 right now?
B-6683 is not currently being tracked; last seen 1h ago.