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 |
|---|---|---|---|---|---|
| VLJ148Z | route not resolved | 26 Feb 2018, 06:4926 Feb 2018 | 26 Feb 2018, 07:04 | 1,400 ft | no position received |
| VLJ129K | route not resolved | 25 Feb 2018, 10:0525 Feb 2018 | 25 Feb 2018, 10:13 | 34,000 ft | no position received |
| VLJ129K | route not resolved | 25 Feb 2018, 08:5425 Feb 2018 | 25 Feb 2018, 09:00 | 5,650 ft | no position received |
| VLJ134Z | route not resolved | 20 Feb 2018, 15:1720 Feb 2018 | 20 Feb 2018, 15:48 | 23,975 ft | no position received |
| VLJ134Z | route not resolved | 19 Feb 2018, 08:5919 Feb 2018 | 19 Feb 2018, 09:29 | 1,250 ft | no position received |
| VLJ113Z | route not resolved | 14 Feb 2018, 12:5614 Feb 2018 | 14 Feb 2018, 13:33 | 29,225 ft | no position received |
| VLJ113Z | route not resolved | 14 Feb 2018, 07:1814 Feb 2018 | 14 Feb 2018, 07:30 | 24,000 ft | no position received |
| VLJ122Z | route not resolved | 13 Feb 2018, 17:4913 Feb 2018 | 13 Feb 2018, 18:11 | 27,325 ft | no position received |
| VLJ099K | route not resolved | 9 Feb 2018, 22:269 Feb 2018 | 9 Feb 2018, 22:45 | 24,000 ft | no position received |
| VLJ099K | route not resolved | 9 Feb 2018, 19:399 Feb 2018 | 9 Feb 2018, 20:13 | 1,375 ft | no position received |
| VLJ083K | route not resolved | 7 Feb 2018, 18:257 Feb 2018 | 7 Feb 2018, 18:51 | 28,675 ft | no position received |
| VLJ083K | route not resolved | 7 Feb 2018, 09:237 Feb 2018 | 7 Feb 2018, 09:44 | 34,950 ft | no position received |
| VLJ088Z | route not resolved | 1 Feb 2018, 18:001 Feb 2018 | 1 Feb 2018, 18:22 | 29,425 ft | no position received |
| VLJ088Z | route not resolved | 1 Feb 2018, 09:471 Feb 2018 | 1 Feb 2018, 10:06 | 35,000 ft | no position received |
| VLJ062Z | route not resolved | 29 Jan 2018, 17:4029 Jan 2018 | 29 Jan 2018, 18:12 | 37,975 ft | no position received |
| VLJ062Z | route not resolved | 27 Jan 2018, 23:4127 Jan 2018 | 28 Jan 2018, 00:18 | 38,975 ft | no position received |
| VLJ077Z | route not resolved | 26 Jan 2018, 19:2126 Jan 2018 | 26 Jan 2018, 20:27 | 17,975 ft | no position received |
| VLJ065M | route not resolved | 26 Jan 2018, 13:2026 Jan 2018 | 26 Jan 2018, 13:33 | 25,000 ft | no position received |
| VLJ063Z | route not resolved | 25 Jan 2018, 08:0625 Jan 2018 | 25 Jan 2018, 08:24 | 11,975 ft | no position received |
| VLJ061Z | route not resolved | 23 Jan 2018, 23:0223 Jan 2018 | 23 Jan 2018, 23:30 | 24,975 ft | no position received |
| VLJ061Z | route not resolved | 23 Jan 2018, 21:3923 Jan 2018 | 23 Jan 2018, 21:58 | 13,325 ft | no position received |
| VLJ052Z | route not resolved | 20 Jan 2018, 15:3320 Jan 2018 | 20 Jan 2018, 16:08 | 25,825 ft | no position received |
| VLJ687Z | route not resolved | 2 Jan 2018, 15:332 Jan 2018 | 2 Jan 2018, 15:52 | 21,975 ft | no position received |
| VLJ605Z | route not resolved | 2 Jan 2018, 13:052 Jan 2018 | 2 Jan 2018, 13:20 | 9,225 ft | no position received |
| VLJ687Z | route not resolved | 30 Dec 2017, 17:3730 Dec 2017 | 30 Dec 2017, 18:26 | 23,750 ft | no position received |
