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 |
|---|---|---|---|---|---|
| VLJ415Z | route not resolved | 10 Jun 2018, 01:5510 Jun 2018 | 10 Jun 2018, 02:16 | 29,975 ft | no position received |
| VLJ415Z | route not resolved | 10 Jun 2018, 00:4610 Jun 2018 | 10 Jun 2018, 01:16 | 9,000 ft | no position received |
| VLJ388K | route not resolved | 7 Jun 2018, 19:547 Jun 2018 | 7 Jun 2018, 20:12 | 37,400 ft | no position received |
| VLJ388K | route not resolved | 7 Jun 2018, 16:227 Jun 2018 | 7 Jun 2018, 16:57 | 35,025 ft | no position received |
| VLJ395P | route not resolved | 7 Jun 2018, 13:157 Jun 2018 | 7 Jun 2018, 13:49 | 24,775 ft | no position received |
| VLJ395P | route not resolved | 6 Jun 2018, 20:436 Jun 2018 | 6 Jun 2018, 21:11 | 1,325 ft | no position received |
| VLJ326M | route not resolved | 26 May 2018, 19:1226 May 2018 | 26 May 2018, 19:34 | 25,400 ft | no position received |
| VLJ326M | route not resolved | 26 May 2018, 09:2026 May 2018 | 26 May 2018, 09:44 | 29,225 ft | no position received |
| VLJ339M | route not resolved | 25 May 2018, 18:1525 May 2018 | 25 May 2018, 18:41 | 22,700 ft | no position received |
| VLJ339M | route not resolved | 25 May 2018, 15:5125 May 2018 | 25 May 2018, 16:12 | 15,525 ft | no position received |
| VLJ339M | route not resolved | 24 May 2018, 18:3524 May 2018 | 24 May 2018, 19:05 | 1,300 ft | no position received |
| VLJ350Z | route not resolved | 24 May 2018, 14:3624 May 2018 | 24 May 2018, 15:01 | 26,200 ft | no position received |
| VLJ350Z | route not resolved | 24 May 2018, 09:4124 May 2018 | 24 May 2018, 10:06 | 1,225 ft | no position received |
| VLJ349Z | route not resolved | 23 May 2018, 12:2823 May 2018 | 23 May 2018, 12:51 | 31,700 ft | no position received |
| VLJ349Z | route not resolved | 22 May 2018, 11:0122 May 2018 | 22 May 2018, 11:40 | 33,025 ft | no position received |
| VLJ352Z | route not resolved | 21 May 2018, 16:5221 May 2018 | 21 May 2018, 17:20 | 36,375 ft | no position received |
| VLJ352Z | route not resolved | 21 May 2018, 11:1421 May 2018 | 21 May 2018, 11:53 | 34,975 ft | no position received |
| VLJ245M | route not resolved | 21 May 2018, 08:3521 May 2018 | 21 May 2018, 09:08 | 23,700 ft | no position received |
| VLJ245M | route not resolved | 20 May 2018, 15:3420 May 2018 | 20 May 2018, 15:59 | 36,975 ft | no position received |
| VLJ319Z | route not resolved | 13 May 2018, 20:1113 May 2018 | 13 May 2018, 20:25 | 30,375 ft | no position received |
| VLJ277Z | route not resolved | 13 May 2018, 12:4113 May 2018 | 13 May 2018, 13:05 | 34,975 ft | no position received |
| VLJ320Z | route not resolved | 12 May 2018, 11:4212 May 2018 | 12 May 2018, 12:06 | 24,025 ft | no position received |
| VLJ124G | route not resolved | 11 May 2018, 18:3311 May 2018 | 11 May 2018, 19:01 | 35,900 ft | no position received |
| VLJ124G | route not resolved | 11 May 2018, 16:0511 May 2018 | 11 May 2018, 16:11 | 33,975 ft | no position received |
| VLJ320Z | route not resolved | 10 May 2018, 10:0610 May 2018 | 10 May 2018, 10:32 | 32,975 ft | no position received |
