Not currently tracked · last seen 5d ago
- Flights observed
- 22
- Avg flight time
- 7h 55m
- Typical route
- PVG → HKG
- Last seen
- 5d ago
Last known area
Recent flights last 22
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | CTU → HGH | May 29, 00:05 UTC | May 29, 00:20 UTC | 15m |
| 2026-05-23 | HKG → PVG | May 23, 09:15 UTC | May 23, 10:35 UTC | 1h 20m |
| 2026-05-23 | PVG → HKG | May 23, 06:05 UTC | May 23, 07:25 UTC | 1h 20m |
| 2026-05-22 | PVG → HKG | May 22, 10:20 UTC | May 23, 07:25 UTC | 21h 5m |
| 2026-05-22 | PVG → HKG | May 22, 10:10 UTC | May 23, 07:25 UTC | 21h 15m |
| 2026-05-22 | HKG → PVG | May 22, 09:20 UTC | May 22, 09:35 UTC | 15m |
| 2026-05-22 | PVG → HKG | May 22, 07:05 UTC | May 22, 07:20 UTC | 15m |
| 2026-05-22 | PVG → HKG | May 22, 06:00 UTC | May 22, 06:25 UTC | 25m |
| 2026-05-18 | DQA → PVG | May 18, 11:35 UTC | May 18, 12:05 UTC | 30m |
| 2026-05-03 | SHA → XMN | May 3, 06:35 UTC | May 3, 07:05 UTC | 30m |
| 2026-05-02 | PVG → SHE | May 2, 08:35 UTC | May 3, 07:05 UTC | 22h 29m |
| 2026-05-01 | PVG → ZHA | May 1, 23:20 UTC | May 2, 08:45 UTC | 9h 25m |
| 2026-05-01 | PVG → ZHA | May 1, 08:35 UTC | May 2, 05:50 UTC | 21h 15m |
| 2026-05-01 | PVG → ZHA | May 1, 05:50 UTC | May 2, 00:10 UTC | 18h 20m |
| 2026-04-29 | SYX → PVG | Apr 29, 16:25 UTC | Apr 30, 00:00 UTC | 7h 34m |
| 2026-04-29 | SYX → PVG | Apr 29, 00:30 UTC | Apr 30, 00:00 UTC | 23h 30m |
| 2026-04-25 | SZX → CKG | Apr 25, 13:30 UTC | Apr 25, 13:40 UTC | 10m |
| 2026-04-20 | HKG → HFE | Apr 20, 10:15 UTC | Apr 20, 10:35 UTC | 20m |
| 2026-04-20 | HFE → HKG | Apr 20, 08:30 UTC | Apr 20, 08:55 UTC | 25m |
| 2026-04-19 | HFE → HKG | Apr 19, 10:25 UTC | Apr 20, 08:55 UTC | 22h 30m |
| 2026-04-19 | HFE → HKG | Apr 19, 08:20 UTC | Apr 19, 09:00 UTC | 40m |
| 2026-04-13 | - | Apr 13, 03:10 UTC | Apr 13, 03:25 UTC | 15m |
Specifications
| Registration | B-6012 |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 79A061 · 36320141 (octal) |
Looking for transponder-level data? View the Mode-S 79A061 page for country allocation, callsign history, and ADS-B signal details.
B-6012 frequently asked
What type of aircraft is B-6012?
B-6012 is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for B-6012?
B-6012 broadcasts on Mode-S (ICAO 24-bit) address 79A061 (octal 36320141). View the transponder page.
What route does B-6012 typically fly?
B-6012 most frequently flies between PVG and HKG based on observed flights.
Where is B-6012 right now?
B-6012 is not currently being tracked; last seen 5d ago.