Back to the log
Aircraft
VH-VQN
Common
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 8 Oct 2022. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
The station's story
- Cumulative contact time
- 19 h
- Distinct days
- 18
- Highest captured altitude
- 43,000 ft
- Discovery rank
- #46,855 of 57,389
- Longest contact
- 2 h 42 min
- Contacts on this Mode S address
- 34 contacts on the address, 22 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- VP-CJYfrom 8 Jul 2021 to 8 Jul 2021 · 1 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VHVQN | route not resolved | 20 Jan 2026, 10:4920 Jan 2026 | 20 Jan 2026, 12:26 | 39,975 ft | 2,012 |
| VHVQN | route not resolved | 17 Jan 2026, 08:0717 Jan 2026 | 17 Jan 2026, 08:52 | not transmitted | 3,148 |
| VHVQN | route not resolved | 14 Jan 2026, 14:5214 Jan 2026 | 14 Jan 2026, 15:33 | 40,000 ft | 1,380 |
| VHVQN | route not resolved | 7 Jan 2026, 08:167 Jan 2026 | 7 Jan 2026, 08:47 | not transmitted | 2,626 |
| not transmitted | route not resolved | 14 Jan 2025, 11:4714 Jan 2025 | 14 Jan 2025, 13:58 | 40,000 ft | 1,554 |
| not transmitted | route not resolved | 9 Jan 2025, 16:489 Jan 2025 | 9 Jan 2025, 17:26 | not transmitted | no position received |
| not transmitted | route not resolved | 8 Jan 2025, 15:308 Jan 2025 | 8 Jan 2025, 18:13 | not transmitted | no position received |
| not transmitted | route not resolved | 7 Jan 2025, 20:087 Jan 2025 | 7 Jan 2025, 21:15 | not transmitted | 2,760 |
| not transmitted | route not resolved | 6 Jan 2025, 10:036 Jan 2025 | 6 Jan 2025, 10:35 | 35,150 ft | 1,382 |
| not transmitted | route not resolved | 5 Jan 2025, 14:045 Jan 2025 | 5 Jan 2025, 14:48 | not transmitted | 3,362 |
| VHVQN | route not resolved | 2 Jun 2024, 15:382 Jun 2024 | 2 Jun 2024, 16:05 | 43,000 ft | 824 |
| VHVQN | route not resolved | 26 May 2024, 14:2126 May 2024 | 26 May 2024, 14:47 | 28,300 ft | 752 |
| VHVQN | route not resolved | 14 Jan 2024, 15:0314 Jan 2024 | 14 Jan 2024, 16:06 | 39,325 ft | 1,704 |
| VHVQN | route not resolved | 13 Jan 2024, 19:2313 Jan 2024 | 13 Jan 2024, 19:56 | not transmitted | 1,307 |
| VHVQN | route not resolved | 13 Jan 2024, 16:5313 Jan 2024 | 13 Jan 2024, 17:08 | 21,000 ft | 621 |
| VHVQN | route not resolved | 12 Jan 2024, 20:1112 Jan 2024 | 12 Jan 2024, 20:55 | not transmitted | 3,798 |
| VHVQN | route not resolved | 12 Jan 2024, 17:1912 Jan 2024 | 12 Jan 2024, 17:55 | 35,975 ft | 2,430 |
| VHVQN | route not resolved | 11 Jan 2024, 11:0211 Jan 2024 | 11 Jan 2024, 11:45 | not transmitted | 3,436 |
| VHVQN | route not resolved | 10 Jan 2024, 15:3110 Jan 2024 | 10 Jan 2024, 17:26 | 34,000 ft | 3,966 |
| VHVQN | route not resolved | 10 Jan 2024, 13:0010 Jan 2024 | 10 Jan 2024, 13:27 | 24,000 ft | 1,392 |
| VHVQN | route not resolved | 11 May 2023, 11:5011 May 2023 | 11 May 2023, 12:06 | 34,650 ft | 730 |
| VHVQN | route not resolved | 11 May 2023, 09:3611 May 2023 | 11 May 2023, 09:53 | 27,325 ft | 1,384 |
Page 1 of 1 · 22 visits
