Not currently tracked · last seen 9d ago
- Flights observed
- 48
- Avg flight time
- 3h 42m
- Typical route
- PVG → HKG
- Last seen
- 9d ago
Last known area
Recent flights last 48
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-07 | HKG → PVG | Jun 7, 08:35 UTC | Jun 7, 08:55 UTC | 20m |
| 2026-06-07 | HKG → PVG | Jun 7, 07:35 UTC | Jun 7, 07:50 UTC | 15m |
| 2026-06-07 | PVG → HKG | Jun 7, 03:50 UTC | Jun 7, 05:15 UTC | 1h 25m |
| 2026-05-29 | HKG → PVG | May 29, 07:20 UTC | May 29, 08:35 UTC | 1h 15m |
| 2026-05-29 | PVG → HKG | May 29, 04:15 UTC | May 29, 05:35 UTC | 1h 20m |
| 2026-05-28 | PEK → PVG | May 28, 06:45 UTC | May 28, 06:55 UTC | 10m |
| 2026-05-26 | HKG → PVG | May 26, 12:24 UTC | May 27, 03:04 UTC | 14h 40m |
| 2026-05-26 | PVG → HKG | May 26, 05:30 UTC | May 26, 10:39 UTC | 5h 10m |
| 2026-05-24 | HKG → PVG | May 24, 06:05 UTC | May 24, 06:30 UTC | 25m |
| 2026-05-24 | HKG → PVG | May 24, 05:10 UTC | May 24, 05:30 UTC | 20m |
| 2026-05-24 | PVG → HKG | May 24, 01:50 UTC | May 24, 03:10 UTC | 1h 20m |
| 2026-05-21 | PVG → PEK | May 21, 09:20 UTC | May 21, 09:30 UTC | 10m |
| 2026-05-20 | HKG → PVG | May 20, 07:20 UTC | May 20, 08:35 UTC | 1h 15m |
| 2026-05-20 | PVG → HKG | May 20, 04:05 UTC | May 20, 05:25 UTC | 1h 21m |
| 2026-05-17 | SZX → PVG | May 17, 05:30 UTC | May 17, 05:40 UTC | 10m |
| 2026-05-16 | HKG → PVG | May 16, 07:35 UTC | May 16, 08:51 UTC | 1h 15m |
| 2026-05-16 | PVG → HKG | May 16, 04:10 UTC | May 16, 05:40 UTC | 1h 30m |
| 2026-05-15 | HKG → PVG | May 15, 09:05 UTC | May 15, 10:15 UTC | 1h 10m |
| 2026-05-15 | PVG → HKG | May 15, 04:20 UTC | May 15, 05:50 UTC | 1h 30m |
| 2026-05-14 | PVG → HKG | May 14, 09:10 UTC | May 15, 05:50 UTC | 20h 40m |
| 2026-05-14 | PVG → MFM | May 14, 07:00 UTC | May 14, 07:15 UTC | 15m |
| 2026-05-14 | PVG → MFM | May 14, 05:50 UTC | May 14, 06:20 UTC | 30m |
| 2026-05-13 | PUS → PVG | May 13, 03:50 UTC | May 13, 04:00 UTC | 10m |
| 2026-05-11 | MFM → PVG | May 11, 09:00 UTC | May 11, 10:00 UTC | 1h 0m |
| 2026-05-11 | PVG → MFM | May 11, 05:45 UTC | May 11, 07:00 UTC | 1h 15m |
| 2026-05-10 | HKG → PVG | May 10, 06:25 UTC | May 11, 06:10 UTC | 23h 45m |
| 2026-05-10 | HKG → PVG | May 10, 05:34 UTC | May 10, 06:50 UTC | 1h 15m |
| 2026-05-10 | PVG → HKG | May 10, 02:39 UTC | May 10, 04:09 UTC | 1h 30m |
| 2026-05-07 | HKG → PVG | May 7, 07:20 UTC | May 7, 08:30 UTC | 1h 10m |
| 2026-05-07 | PVG → HKG | May 7, 05:20 UTC | May 7, 05:40 UTC | 20m |
| 2026-05-07 | PVG → HKG | May 7, 04:10 UTC | May 7, 04:30 UTC | 20m |
| 2026-05-06 | PVG → HKG | May 6, 08:30 UTC | May 7, 04:30 UTC | 19h 59m |
| 2026-05-06 | HKG → PVG | May 6, 07:30 UTC | May 7, 04:30 UTC | 20h 59m |
| 2026-05-06 | PVG → HKG | May 6, 05:20 UTC | May 6, 05:40 UTC | 20m |
| 2026-05-06 | PVG → HKG | May 6, 04:15 UTC | May 6, 04:35 UTC | 20m |
| 2026-05-05 | PVG → PEK | May 5, 04:35 UTC | May 5, 04:45 UTC | 10m |
| 2026-05-04 | HKG → PVG | May 4, 08:00 UTC | May 4, 08:20 UTC | 20m |
| 2026-05-04 | HKG → PVG | May 4, 07:15 UTC | May 4, 07:30 UTC | 15m |
| 2026-05-04 | PVG → HKG | May 4, 04:09 UTC | May 4, 05:40 UTC | 1h 30m |
| 2026-05-03 | HKG → PVG | May 3, 07:30 UTC | May 3, 08:45 UTC | 1h 15m |
| 2026-05-03 | PVG → HKG | May 3, 05:15 UTC | May 3, 05:35 UTC | 20m |
| 2026-05-03 | PVG → HKG | May 3, 04:05 UTC | May 3, 04:35 UTC | 30m |
| 2026-05-02 | PVG → HKG | May 2, 08:20 UTC | May 3, 04:35 UTC | 20h 14m |
| 2026-05-02 | HKG → PVG | May 2, 07:15 UTC | May 3, 04:35 UTC | 21h 19m |
| 2026-05-02 | PVG → HKG | May 2, 05:35 UTC | May 2, 05:55 UTC | 20m |
| 2026-05-02 | PVG → HKG | May 2, 04:20 UTC | May 2, 04:45 UTC | 25m |
| 2026-04-25 | HKG → PVG | Apr 25, 07:35 UTC | Apr 25, 08:00 UTC | 25m |
| 2026-04-25 | PVG → HKG | Apr 25, 04:20 UTC | Apr 25, 05:55 UTC | 1h 35m |
Specifications
| Registration | B-6642 |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 780611 · 36003021 (octal) |
Looking for transponder-level data? View the Mode-S 780611 page for country allocation, callsign history, and ADS-B signal details.
B-6642 frequently asked
What type of aircraft is B-6642?
B-6642 is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for B-6642?
B-6642 broadcasts on Mode-S (ICAO 24-bit) address 780611 (octal 36003021). View the transponder page.
What route does B-6642 typically fly?
B-6642 most frequently flies between PVG and HKG based on observed flights.
Where is B-6642 right now?
B-6642 is not currently being tracked; last seen 9d ago.