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