Back to the log
Aircraft
F-HBZA
Regular
The station's story
- Cumulative contact time
- 173 h
- Distinct days
- 304
- Highest captured altitude
- 39,975 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #21,386 of 57,065
- Longest contact
- 1 h 20 min
Same airframe, also seen as
- G-IBZAfrom 21 Jun 2016 to 6 Jan 2017 · 31 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.
Observed callsigns
VLJ (423 contacts, 2017-2023) · ARL (11 contacts, 2026)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ54GZ | route not resolved | 3 Jul 2019, 10:143 Jul 2019 | 3 Jul 2019, 10:37 | 33,250 ft | no position received |
| VLJ01AZ | route not resolved | 1 Jul 2019, 17:421 Jul 2019 | 1 Jul 2019, 18:19 | 24,825 ft | no position received |
| VLJ01AZ | route not resolved | 1 Jul 2019, 10:131 Jul 2019 | 1 Jul 2019, 10:36 | 34,975 ft | no position received |
| VLJ02AZ | route not resolved | 30 Jun 2019, 17:5430 Jun 2019 | 30 Jun 2019, 18:23 | 26,200 ft | no position received |
| VLJ02AZ | route not resolved | 30 Jun 2019, 16:3530 Jun 2019 | 30 Jun 2019, 17:05 | 37,000 ft | no position received |
| VLJ02AZ | route not resolved | 30 Jun 2019, 12:0930 Jun 2019 | 30 Jun 2019, 12:41 | 33,975 ft | no position received |
| VLJ11GZ | route not resolved | 29 Jun 2019, 11:4429 Jun 2019 | 29 Jun 2019, 12:01 | 21,400 ft | no position received |
| VLJ52EK | route not resolved | 28 Jun 2019, 17:4828 Jun 2019 | 28 Jun 2019, 18:25 | 26,000 ft | no position received |
| VLJ52EK | route not resolved | 28 Jun 2019, 16:2928 Jun 2019 | 28 Jun 2019, 16:45 | 14,850 ft | no position received |
| VLJ50GZ | route not resolved | 28 Jun 2019, 11:4028 Jun 2019 | 28 Jun 2019, 12:11 | 26,075 ft | no position received |
| VLJ50GZ | route not resolved | 28 Jun 2019, 09:0828 Jun 2019 | 28 Jun 2019, 09:34 | 33,000 ft | no position received |
| VLJ32GZ | route not resolved | 25 Jun 2019, 22:3625 Jun 2019 | 25 Jun 2019, 23:12 | 22,325 ft | no position received |
| VLJ32GZ | route not resolved | 25 Jun 2019, 21:2425 Jun 2019 | 25 Jun 2019, 21:52 | 1,125 ft | no position received |
| VLJ16GZ | route not resolved | 24 Jun 2019, 15:5024 Jun 2019 | 24 Jun 2019, 16:30 | 33,975 ft | no position received |
| VLJ16GZ | route not resolved | 24 Jun 2019, 12:5424 Jun 2019 | 24 Jun 2019, 13:18 | 1,225 ft | no position received |
| VLJ12GZ | route not resolved | 21 Jun 2019, 13:1421 Jun 2019 | 21 Jun 2019, 13:25 | 19,975 ft | no position received |
| VLJ15BM | route not resolved | 8 Mar 2019, 17:058 Mar 2019 | 8 Mar 2019, 17:34 | 30,750 ft | no position received |
| VLJ85BM | route not resolved | 6 Mar 2019, 11:216 Mar 2019 | 6 Mar 2019, 11:43 | 29,650 ft | no position received |
| VLJ86BM | route not resolved | 4 Mar 2019, 15:014 Mar 2019 | 4 Mar 2019, 15:17 | 36,975 ft | no position received |
| VLJ69BG | route not resolved | 3 Mar 2019, 18:183 Mar 2019 | 3 Mar 2019, 18:39 | 33,725 ft | no position received |
| VLJ69BG | route not resolved | 28 Feb 2019, 14:3828 Feb 2019 | 28 Feb 2019, 14:56 | 34,950 ft | no position received |
| VLJ58BZ | route not resolved | 24 Feb 2019, 13:4524 Feb 2019 | 24 Feb 2019, 14:01 | 17,950 ft | no position received |
| VLJ36BZ | route not resolved | 23 Feb 2019, 15:2723 Feb 2019 | 23 Feb 2019, 15:37 | 3,950 ft | no position received |
| VLJ81AM | route not resolved | 17 Feb 2019, 00:0517 Feb 2019 | 17 Feb 2019, 00:26 | 29,225 ft | no position received |
| VLJ81AM | route not resolved | 16 Feb 2019, 13:4816 Feb 2019 | 16 Feb 2019, 14:06 | 34,075 ft | no position received |
