Not currently tracked · last seen 14d ago
- Flights observed
- 79 showing last 50
- Avg flight time
- 2h 30m
- Typical route
- PEK → SZX
- Last seen
- 14d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-15 | SZX → PEK | May 15, 04:40 UTC | May 15, 04:55 UTC | 15m |
| 2026-05-13 | PEK → SZX | May 13, 04:45 UTC | May 13, 05:05 UTC | 20m |
| 2026-05-11 | PEK → SZX | May 11, 05:35 UTC | May 11, 05:55 UTC | 20m |
| 2026-05-09 | PEK → CAN | May 9, 23:30 UTC | May 9, 23:50 UTC | 20m |
| 2026-05-09 | PEK → SHA | May 9, 10:50 UTC | May 9, 11:00 UTC | 10m |
| 2026-05-09 | SZX → PEK | May 9, 04:00 UTC | May 9, 04:10 UTC | 10m |
| 2026-05-08 | PEK → SZX | May 8, 23:00 UTC | May 8, 23:20 UTC | 20m |
| 2026-05-08 | PEK → CTU | May 8, 00:44 UTC | May 8, 01:04 UTC | 20m |
| 2026-05-06 | SZX → PEK | May 6, 10:40 UTC | May 6, 10:50 UTC | 10m |
| 2026-05-06 | SZX → PEK | May 6, 08:15 UTC | May 6, 08:30 UTC | 15m |
| 2026-05-06 | PEK → SZX | May 6, 03:20 UTC | May 6, 03:40 UTC | 20m |
| 2026-05-05 | CTU → PEK | May 5, 16:06 UTC | May 5, 16:15 UTC | 10m |
| 2026-05-05 | PEK → CTU | May 5, 01:50 UTC | May 5, 10:30 UTC | 8h 40m |
| 2026-05-04 | SZX → PEK | May 4, 02:45 UTC | May 4, 02:54 UTC | 10m |
| 2026-05-03 | PEK → SZX | May 3, 14:05 UTC | May 3, 14:25 UTC | 20m |
| 2026-05-02 | PEK → CAN | May 2, 13:15 UTC | May 2, 13:40 UTC | 25m |
| 2026-05-01 | PEK → CAN | May 1, 13:10 UTC | May 1, 13:35 UTC | 25m |
| 2026-05-01 | TSN → CAN | May 1, 02:20 UTC | May 1, 02:40 UTC | 20m |
| 2026-04-30 | KMG → PEK | Apr 30, 15:00 UTC | Apr 30, 15:20 UTC | 20m |
| 2026-04-30 | PEK → KMG | Apr 30, 07:40 UTC | Apr 30, 08:05 UTC | 25m |
| 2026-04-29 | PEK → SZX | Apr 29, 10:10 UTC | Apr 29, 10:20 UTC | 10m |
| 2026-04-28 | PEK → CAN | Apr 28, 07:25 UTC | Apr 28, 23:40 UTC | 16h 15m |
| 2026-04-27 | PEK → CAN | Apr 27, 13:10 UTC | Apr 27, 13:30 UTC | 20m |
| 2026-04-27 | ARN → PEK | Apr 27, 00:30 UTC | Apr 27, 00:45 UTC | 15m |
| 2026-04-26 | ARN → PEK | Apr 26, 17:25 UTC | Apr 26, 22:05 UTC | 4h 40m |
| 2026-04-26 | PEK → ARN | Apr 26, 06:30 UTC | Apr 26, 14:55 UTC | 8h 25m |
| 2026-04-26 | ARN → PEK | Apr 26, 00:25 UTC | Apr 26, 00:45 UTC | 20m |
| 2026-04-25 | ARN → PEK | Apr 25, 17:25 UTC | Apr 25, 22:05 UTC | 4h 40m |
| 2026-04-25 | PEK → ARN | Apr 25, 06:35 UTC | Apr 25, 15:10 UTC | 8h 35m |
| 2026-04-25 | ARN → PEK | Apr 25, 00:20 UTC | Apr 25, 00:40 UTC | 20m |
| 2026-04-24 | ARN → PEK | Apr 24, 17:20 UTC | Apr 24, 18:25 UTC | 1h 5m |
| 2026-04-24 | PEK → ARN | Apr 24, 06:25 UTC | Apr 24, 14:55 UTC | 8h 30m |
| 2026-04-24 | CPH → PEK | Apr 24, 01:00 UTC | Apr 24, 01:20 UTC | 20m |
| 2026-04-23 | CPH → PEK | Apr 23, 17:20 UTC | Apr 23, 22:35 UTC | 5h 14m |
| 2026-04-23 | PEK → CPH | Apr 23, 07:55 UTC | Apr 23, 14:55 UTC | 7h 0m |
| 2026-04-23 | PEK → CPH | Apr 23, 06:01 UTC | Apr 23, 06:10 UTC | 10m |
| 2026-04-23 | JNB → SZX | Apr 23, 00:20 UTC | Apr 23, 00:30 UTC | 10m |
| 2026-04-22 | JNB → SZX | Apr 22, 20:40 UTC | Apr 22, 20:50 UTC | 10m |
| 2026-04-22 | JNB → SZX | Apr 22, 08:30 UTC | Apr 22, 19:10 UTC | 10h 40m |
| 2026-04-21 | SZX → JNB | Apr 21, 18:25 UTC | Apr 22, 05:35 UTC | 11h 10m |
| 2026-04-21 | SZX → JNB | Apr 21, 17:01 UTC | Apr 21, 17:15 UTC | 15m |
| 2026-04-21 | SZX → JNB | Apr 21, 10:55 UTC | Apr 21, 11:10 UTC | 15m |
| 2026-04-21 | PEK → SHA | Apr 21, 03:15 UTC | Apr 21, 03:25 UTC | 10m |
| 2026-04-20 | GVA → PEK | Apr 20, 11:25 UTC | Apr 20, 17:45 UTC | 6h 21m |
| 2026-04-19 | PEK → GVA | Apr 19, 22:45 UTC | Apr 20, 05:50 UTC | 7h 5m |
| 2026-04-19 | PEK → GVA | Apr 19, 19:20 UTC | Apr 19, 19:30 UTC | 10m |
| 2026-04-19 | PEK → SHA | Apr 19, 05:45 UTC | Apr 19, 06:00 UTC | 15m |
| 2026-04-18 | CPH → PEK | Apr 18, 17:15 UTC | Apr 18, 22:25 UTC | 5h 10m |
| 2026-04-18 | PEK → CPH | Apr 18, 07:40 UTC | Apr 18, 09:20 UTC | 1h 40m |
| 2026-04-17 | CPH → PEK | Apr 17, 21:45 UTC | Apr 17, 22:30 UTC | 45m |
Specifications
| Registration | B-322Y |
| Aircraft type | AIRBUS A-350-900 (A359) |
| Mode-S code | 781B5B · 36015533 (octal) |
Looking for transponder-level data? View the Mode-S 781B5B page for country allocation, callsign history, and ADS-B signal details.
B-322Y frequently asked
What type of aircraft is B-322Y?
B-322Y is a AIRBUS A-350-900 (ICAO type code A359).
What is the Mode-S transponder code for B-322Y?
B-322Y broadcasts on Mode-S (ICAO 24-bit) address 781B5B (octal 36015533). View the transponder page.
What route does B-322Y typically fly?
B-322Y most frequently flies between PEK and SZX based on observed flights.
Where is B-322Y right now?
B-322Y is not currently being tracked; last seen 14d ago.