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,441
- 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 |
|---|---|---|---|---|---|
| VLJ35AZ | route not resolved | 30 Sept 2019, 08:5930 Sept 2019 | 30 Sept 2019, 09:18 | 31,500 ft | no position received |
| VLJ33AS | route not resolved | 29 Sept 2019, 17:5229 Sept 2019 | 29 Sept 2019, 18:25 | 28,250 ft | no position received |
| VLJ33AS | route not resolved | 29 Sept 2019, 12:1629 Sept 2019 | 29 Sept 2019, 12:36 | 32,050 ft | no position received |
| VLJ25AK | route not resolved | 10 Aug 2019, 10:2910 Aug 2019 | 10 Aug 2019, 11:05 | 30,975 ft | no position received |
| VLJ26AK | route not resolved | 9 Aug 2019, 22:139 Aug 2019 | 9 Aug 2019, 22:35 | 17,500 ft | no position received |
| VLJ26AK | route not resolved | 9 Aug 2019, 19:239 Aug 2019 | 9 Aug 2019, 19:49 | 36,975 ft | no position received |
| VLJ19AZ | route not resolved | 1 Aug 2019, 15:261 Aug 2019 | 1 Aug 2019, 16:01 | 32,025 ft | no position received |
| VLJ19AZ | route not resolved | 1 Aug 2019, 12:201 Aug 2019 | 1 Aug 2019, 12:42 | 29,550 ft | no position received |
| VLJ18AZ | route not resolved | 27 Jul 2019, 13:1227 Jul 2019 | 27 Jul 2019, 13:34 | 27,350 ft | no position received |
| VLJ18AP | route not resolved | 26 Jul 2019, 20:1826 Jul 2019 | 26 Jul 2019, 20:42 | 33,525 ft | no position received |
| VLJ16AZ | route not resolved | 26 Jul 2019, 16:3126 Jul 2019 | 26 Jul 2019, 17:00 | 33,975 ft | no position received |
| VLJ16AZ | route not resolved | 26 Jul 2019, 13:4626 Jul 2019 | 26 Jul 2019, 14:08 | 34,025 ft | no position received |
| VLJ02AG | route not resolved | 24 Jul 2019, 19:5424 Jul 2019 | 24 Jul 2019, 20:21 | 19,250 ft | no position received |
| VLJ02AG | route not resolved | 24 Jul 2019, 09:3724 Jul 2019 | 24 Jul 2019, 09:51 | 7,125 ft | no position received |
| VLJ02AG | route not resolved | 23 Jul 2019, 16:4323 Jul 2019 | 23 Jul 2019, 17:14 | 1,250 ft | no position received |
| VLJ02AG | route not resolved | 22 Jul 2019, 19:1122 Jul 2019 | 22 Jul 2019, 19:25 | 9,725 ft | no position received |
| VLJ10AZ | route not resolved | 22 Jul 2019, 14:4722 Jul 2019 | 22 Jul 2019, 15:13 | 29,025 ft | no position received |
| VLJ10AZ | route not resolved | 21 Jul 2019, 12:0321 Jul 2019 | 21 Jul 2019, 12:19 | 27,575 ft | no position received |
| VLJ09GZ | route not resolved | 12 Jul 2019, 16:0212 Jul 2019 | 12 Jul 2019, 16:43 | 25,900 ft | no position received |
| VLJ09GZ | route not resolved | 10 Jul 2019, 11:2910 Jul 2019 | 10 Jul 2019, 12:04 | 31,000 ft | no position received |
| VLJ17GZ | route not resolved | 5 Jul 2019, 15:335 Jul 2019 | 5 Jul 2019, 16:10 | 31,975 ft | no position received |
| VLJ17GZ | route not resolved | 4 Jul 2019, 20:174 Jul 2019 | 4 Jul 2019, 20:46 | 23,250 ft | no position received |
| VLJ83EZ | route not resolved | 3 Jul 2019, 21:283 Jul 2019 | 3 Jul 2019, 21:59 | 26,550 ft | no position received |
| VLJ83EZ | route not resolved | 3 Jul 2019, 18:063 Jul 2019 | 3 Jul 2019, 18:33 | 37,000 ft | no position received |
| VLJ54GZ | route not resolved | 3 Jul 2019, 12:473 Jul 2019 | 3 Jul 2019, 13:13 | 28,900 ft | no position received |
