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 |
|---|---|---|---|---|---|
| VLJ851M | route not resolved | 14 Aug 2022, 16:1014 Aug 2022 | 14 Aug 2022, 16:40 | 23,300 ft | no position received |
| VLJ321J | route not resolved | 13 Aug 2022, 17:2513 Aug 2022 | 13 Aug 2022, 17:46 | 30,275 ft | no position received |
| VLJ891A | route not resolved | 12 Aug 2022, 15:4112 Aug 2022 | 12 Aug 2022, 16:19 | 24,950 ft | no position received |
| VLJ891A | route not resolved | 12 Aug 2022, 09:2812 Aug 2022 | 12 Aug 2022, 10:07 | 34,975 ft | no position received |
| VLJ321J | route not resolved | 10 Aug 2022, 15:4010 Aug 2022 | 10 Aug 2022, 16:13 | 35,975 ft | no position received |
| VLJ321J | route not resolved | 10 Aug 2022, 12:5410 Aug 2022 | 10 Aug 2022, 13:16 | 32,975 ft | no position received |
| VLJ874Y | route not resolved | 23 Jun 2022, 15:4523 Jun 2022 | 23 Jun 2022, 15:56 | 27,025 ft | no position received |
| VLJ374T | route not resolved | 1 May 2022, 20:521 May 2022 | 1 May 2022, 21:19 | 28,475 ft | no position received |
| VLJ374T | route not resolved | 30 Apr 2022, 08:0230 Apr 2022 | 30 Apr 2022, 08:19 | 30,600 ft | no position received |
| VLJ345M | route not resolved | 2 Apr 2022, 22:432 Apr 2022 | 2 Apr 2022, 22:57 | 34,000 ft | no position received |
| VLJ345M | route not resolved | 2 Apr 2022, 09:562 Apr 2022 | 2 Apr 2022, 10:17 | 32,725 ft | no position received |
| VLJ403Y | route not resolved | 1 Apr 2022, 18:351 Apr 2022 | 1 Apr 2022, 19:00 | 25,150 ft | no position received |
| VLJ410F | route not resolved | 14 Mar 2022, 18:5814 Mar 2022 | 14 Mar 2022, 19:16 | 17,975 ft | no position received |
| VLJ878A | route not resolved | 6 Mar 2022, 11:396 Mar 2022 | 6 Mar 2022, 11:59 | 18,000 ft | no position received |
| VLJ878A | route not resolved | 6 Mar 2022, 10:036 Mar 2022 | 6 Mar 2022, 10:09 | 4,425 ft | no position received |
| VLJ226M | route not resolved | 5 Mar 2022, 14:115 Mar 2022 | 5 Mar 2022, 14:33 | 17,975 ft | no position received |
| VLJ226M | route not resolved | 5 Mar 2022, 12:405 Mar 2022 | 5 Mar 2022, 12:47 | 4,375 ft | no position received |
| VLJ597X | route not resolved | 19 Feb 2022, 17:3419 Feb 2022 | 19 Feb 2022, 17:46 | 17,950 ft | no position received |
| not transmitted | route not resolved | 19 Feb 2022, 16:2219 Feb 2022 | 19 Feb 2022, 16:26 | 6,450 ft | no position received |
| VLJ608 | route not resolved | 19 Feb 2022, 08:5119 Feb 2022 | 19 Feb 2022, 09:04 | 17,950 ft | no position received |
| VLJ608A | route not resolved | 19 Feb 2022, 07:4319 Feb 2022 | 19 Feb 2022, 08:01 | 1,300 ft | no position received |
| VLJ833T | route not resolved | 6 Feb 2022, 17:586 Feb 2022 | 6 Feb 2022, 18:05 | 24,025 ft | no position received |
| VLJ809V | route not resolved | 25 Jan 2022, 18:0325 Jan 2022 | 25 Jan 2022, 18:26 | 21,975 ft | no position received |
| VLJ809V | route not resolved | 25 Jan 2022, 16:4425 Jan 2022 | 25 Jan 2022, 16:53 | 3,825 ft | no position received |
| VLJ658M | route not resolved | 16 Jul 2021, 14:2216 Jul 2021 | 16 Jul 2021, 14:51 | 27,175 ft | no position received |
