flight Aircraft
VH-UVO
AIRBUS A-320
Operated by NETWORK AVIATION PTY LTD
- Tail number
- VH-UVO
- Type
- A320
- Mode-S
- 7C6842
Not currently tracked · last seen 1d ago
- Flights observed
- 77 showing last 50
- Avg flight time
- 4h 50m
- Typical route
- PER → PER
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-28 | PER → PER | May 28, 06:15 UTC | May 28, 11:15 UTC | 5h 0m |
| 2026-05-27 | PER → PER | May 27, 22:00 UTC | May 28, 02:40 UTC | 4h 40m |
| 2026-05-27 | PER → PER | May 27, 08:40 UTC | May 27, 12:45 UTC | 4h 5m |
| 2026-05-26 | PER → PER | May 26, 21:55 UTC | May 27, 02:49 UTC | 4h 55m |
| 2026-05-25 | PER → PER | May 25, 23:35 UTC | May 26, 05:40 UTC | 6h 5m |
| 2026-05-22 | PER → PER | May 22, 06:30 UTC | May 22, 11:35 UTC | 5h 4m |
| 2026-05-21 | PER → PER | May 21, 09:50 UTC | May 22, 03:35 UTC | 17h 45m |
| 2026-05-21 | PER → PER | May 21, 03:50 UTC | May 21, 08:25 UTC | 4h 35m |
| 2026-05-20 | PER → PER | May 20, 22:10 UTC | May 21, 02:25 UTC | 4h 15m |
| 2026-05-20 | PER → PER | May 20, 06:45 UTC | May 20, 10:45 UTC | 4h 0m |
| 2026-05-20 | PER → PER | May 20, 00:25 UTC | May 20, 05:10 UTC | 4h 46m |
| 2026-05-19 | - | May 19, 10:00 UTC | May 19, 10:40 UTC | 40m |
| 2026-05-19 | - | May 19, 06:20 UTC | May 19, 06:50 UTC | 30m |
| 2026-05-18 | PER → PER | May 18, 22:15 UTC | May 19, 03:10 UTC | 4h 55m |
| 2026-05-18 | PER → PER | May 18, 06:50 UTC | May 18, 10:50 UTC | 4h 0m |
| 2026-05-17 | PER → PER | May 17, 23:45 UTC | May 18, 05:30 UTC | 5h 45m |
| 2026-05-15 | PER → PER | May 15, 05:20 UTC | May 15, 10:25 UTC | 5h 5m |
| 2026-05-14 | PER → PER | May 14, 22:15 UTC | May 15, 02:05 UTC | 3h 50m |
| 2026-05-14 | PER → PER | May 14, 06:10 UTC | May 14, 10:55 UTC | 4h 45m |
| 2026-05-13 | PER → PER | May 13, 23:40 UTC | May 14, 04:20 UTC | 4h 40m |
| 2026-05-11 | PER → PER | May 11, 06:25 UTC | May 11, 11:05 UTC | 4h 40m |
| 2026-05-10 | PER → PER | May 10, 22:40 UTC | May 11, 02:50 UTC | 4h 10m |
| 2026-05-10 | - | May 10, 09:55 UTC | May 10, 10:00 UTC | 5m |
| 2026-05-10 | - | May 10, 05:30 UTC | May 10, 09:50 UTC | 4h 20m |
| 2026-05-09 | PER → PER | May 9, 03:00 UTC | May 9, 07:40 UTC | 4h 40m |
| 2026-05-08 | PER → PER | May 8, 05:49 UTC | May 8, 09:49 UTC | 4h 0m |
| 2026-05-07 | PER → PER | May 7, 09:30 UTC | May 8, 03:19 UTC | 17h 50m |
| 2026-05-07 | PER → PER | May 7, 03:10 UTC | May 7, 07:50 UTC | 4h 40m |
| 2026-05-06 | PER → PER | May 6, 05:15 UTC | May 6, 10:10 UTC | 4h 55m |
| 2026-05-05 | PER → PER | May 5, 22:30 UTC | May 6, 02:55 UTC | 4h 25m |
| 2026-05-05 | PER → PER | May 5, 06:30 UTC | May 5, 10:45 UTC | 4h 15m |
| 2026-05-04 | PER → PER | May 4, 09:10 UTC | May 5, 02:30 UTC | 17h 21m |
| 2026-05-04 | PER → PER | May 4, 03:30 UTC | May 4, 08:05 UTC | 4h 35m |
| 2026-05-03 | PER → PER | May 3, 21:35 UTC | May 4, 01:10 UTC | 3h 35m |
| 2026-05-03 | KGI → PER | May 3, 11:20 UTC | May 3, 12:10 UTC | 50m |
| 2026-05-03 | PER → KGI | May 3, 09:25 UTC | May 3, 10:15 UTC | 50m |
| 2026-05-01 | - | May 1, 05:25 UTC | May 1, 10:15 UTC | 4h 50m |
| 2026-05-01 | - | May 1, 00:10 UTC | May 1, 04:10 UTC | 4h 0m |
| 2026-04-30 | PER → PER | Apr 30, 07:30 UTC | Apr 30, 12:20 UTC | 4h 50m |
| 2026-04-30 | PER → PER | Apr 30, 07:20 UTC | Apr 30, 07:25 UTC | 5m |
| 2026-04-29 | PER → PER | Apr 29, 22:35 UTC | Apr 30, 02:55 UTC | 4h 19m |
| 2026-04-29 | PER → PER | Apr 29, 06:05 UTC | Apr 29, 10:10 UTC | 4h 6m |
| 2026-04-28 | PER → PER | Apr 28, 22:15 UTC | Apr 29, 02:35 UTC | 4h 20m |
| 2026-04-28 | PER → PER | Apr 28, 06:40 UTC | Apr 28, 11:10 UTC | 4h 30m |
| 2026-04-27 | PER → PER | Apr 27, 21:55 UTC | Apr 28, 02:10 UTC | 4h 15m |
| 2026-04-23 | PER → PER | Apr 23, 06:30 UTC | Apr 23, 11:05 UTC | 4h 35m |
| 2026-04-23 | PER → PER | Apr 23, 00:05 UTC | Apr 23, 04:50 UTC | 4h 46m |
| 2026-04-22 | PER → PER | Apr 22, 05:40 UTC | Apr 22, 09:50 UTC | 4h 10m |
| 2026-04-21 | PER → PER | Apr 21, 22:15 UTC | Apr 22, 02:55 UTC | 4h 40m |
| 2026-04-21 | PER → PER | Apr 21, 06:35 UTC | Apr 21, 10:35 UTC | 4h 0m |
Specifications
| Registration | VH-UVO |
| Aircraft type | AIRBUS A-320 (A320) |
| Operator | NETWORK AVIATION PTY LTD |
| Mode-S code | 7C6842 · 37064102 (octal) |
Looking for transponder-level data? View the Mode-S 7C6842 page for country allocation, callsign history, and ADS-B signal details.
VH-UVO frequently asked
What type of aircraft is VH-UVO?
VH-UVO is a AIRBUS A-320 (ICAO type code A320).
Who operates VH-UVO?
VH-UVO is operated by NETWORK AVIATION PTY LTD.
What is the Mode-S transponder code for VH-UVO?
VH-UVO broadcasts on Mode-S (ICAO 24-bit) address 7C6842 (octal 37064102). View the transponder page.
What route does VH-UVO typically fly?
VH-UVO most frequently flies between PER and PER based on observed flights.
Where is VH-UVO right now?
VH-UVO is not currently being tracked; last seen 1d ago.