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 |
|---|---|---|---|---|---|
| VLJ495 | route not resolved | 25 Sept 2017, 12:1825 Sept 2017 | 25 Sept 2017, 13:02 | 87,100 ft | no position received |
| VLJ487L | route not resolved | 21 Sept 2017, 11:3521 Sept 2017 | 21 Sept 2017, 12:13 | 33,975 ft | no position received |
| VLJ487 | route not resolved | 20 Sept 2017, 13:3920 Sept 2017 | 20 Sept 2017, 14:02 | 27,025 ft | no position received |
| VLJ377P | route not resolved | 13 Sept 2017, 15:5113 Sept 2017 | 13 Sept 2017, 16:27 | 26,075 ft | no position received |
| VLJ377N | route not resolved | 13 Sept 2017, 12:1313 Sept 2017 | 13 Sept 2017, 12:35 | 34,975 ft | no position received |
| VLJ450L | route not resolved | 8 Sept 2017, 19:118 Sept 2017 | 8 Sept 2017, 19:44 | 26,375 ft | no position received |
| VLJ450 | route not resolved | 8 Sept 2017, 09:348 Sept 2017 | 8 Sept 2017, 09:45 | 23,475 ft | no position received |
| VLJ459 | route not resolved | 7 Sept 2017, 15:227 Sept 2017 | 7 Sept 2017, 16:43 | 18,550 ft | no position received |
| VLJ272P | route not resolved | 7 Jun 2017, 06:297 Jun 2017 | 7 Jun 2017, 06:48 | 25,975 ft | no position received |
| VLJ272N | route not resolved | 6 Jun 2017, 22:176 Jun 2017 | 6 Jun 2017, 22:19 | 15,175 ft | no position received |
| VLJ172M | route not resolved | 26 Apr 2017, 19:5926 Apr 2017 | 26 Apr 2017, 20:36 | 22,775 ft | no position received |
| VLJ172L | route not resolved | 26 Apr 2017, 07:5826 Apr 2017 | 26 Apr 2017, 08:33 | 27,725 ft | no position received |
| VLJ134M | route not resolved | 12 Apr 2017, 08:1912 Apr 2017 | 12 Apr 2017, 08:55 | 21,025 ft | no position received |
| VLJ079M | route not resolved | 11 Apr 2017, 10:1511 Apr 2017 | 11 Apr 2017, 10:33 | 34,975 ft | no position received |
| VLJ126M | route not resolved | 8 Apr 2017, 15:468 Apr 2017 | 8 Apr 2017, 16:14 | 21,975 ft | no position received |
| VLJ126L | route not resolved | 8 Apr 2017, 14:188 Apr 2017 | 8 Apr 2017, 14:57 | 4,800 ft | no position received |
| VLJ125N | route not resolved | 6 Apr 2017, 18:216 Apr 2017 | 6 Apr 2017, 19:02 | 34,000 ft | no position received |
| VLJ125L | route not resolved | 6 Apr 2017, 06:556 Apr 2017 | 6 Apr 2017, 07:14 | 25,900 ft | no position received |
| VLJ124M | route not resolved | 30 Mar 2017, 20:4330 Mar 2017 | 30 Mar 2017, 21:16 | 29,250 ft | no position received |
| VLJ124L | route not resolved | 30 Mar 2017, 18:0630 Mar 2017 | 30 Mar 2017, 18:29 | 34,975 ft | no position received |
| VLJ138P | route not resolved | 29 Mar 2017, 14:3229 Mar 2017 | 29 Mar 2017, 15:00 | 24,750 ft | no position received |
| VLJ138N | route not resolved | 29 Mar 2017, 08:4629 Mar 2017 | 29 Mar 2017, 09:21 | 1,000 ft | no position received |
| VLJ138M | route not resolved | 28 Mar 2017, 14:2628 Mar 2017 | 28 Mar 2017, 14:58 | 35,000 ft | no position received |
| VLJ131P | route not resolved | 28 Mar 2017, 13:1528 Mar 2017 | 28 Mar 2017, 13:48 | 1,075 ft | no position received |
| VLJ103N | route not resolved | 23 Mar 2017, 14:4423 Mar 2017 | 23 Mar 2017, 15:16 | 20,675 ft | no position received |
