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 |
|---|---|---|---|---|---|
| VLJ687Z | route not resolved | 30 Dec 2017, 16:2430 Dec 2017 | 30 Dec 2017, 16:58 | 1,275 ft | no position received |
| VLJ673Z | route not resolved | 27 Dec 2017, 15:5127 Dec 2017 | 27 Dec 2017, 16:17 | 27,725 ft | no position received |
| VLJ673Z | route not resolved | 27 Dec 2017, 12:0227 Dec 2017 | 27 Dec 2017, 12:12 | 30,800 ft | no position received |
| VLJ682Z | route not resolved | 26 Dec 2017, 16:3526 Dec 2017 | 26 Dec 2017, 16:41 | 31,975 ft | no position received |
| VLJ682Z | route not resolved | 26 Dec 2017, 10:5026 Dec 2017 | 26 Dec 2017, 11:01 | 24,025 ft | no position received |
| VLJ669Z | route not resolved | 14 Dec 2017, 13:5614 Dec 2017 | 14 Dec 2017, 14:13 | 24,000 ft | no position received |
| VLJ645Z | route not resolved | 11 Dec 2017, 17:5411 Dec 2017 | 11 Dec 2017, 18:09 | 21,975 ft | no position received |
| VLJ637Z | route not resolved | 1 Dec 2017, 20:401 Dec 2017 | 1 Dec 2017, 21:16 | 24,950 ft | no position received |
| VLJ637Z | route not resolved | 29 Nov 2017, 11:3729 Nov 2017 | 29 Nov 2017, 12:11 | 34,975 ft | no position received |
| VLJ593 | route not resolved | 26 Nov 2017, 16:1726 Nov 2017 | 26 Nov 2017, 16:42 | 35,425 ft | no position received |
| VLJ593 | route not resolved | 24 Nov 2017, 15:1824 Nov 2017 | 24 Nov 2017, 15:39 | 34,000 ft | no position received |
| VLJ603 | route not resolved | 24 Nov 2017, 08:3824 Nov 2017 | 24 Nov 2017, 08:51 | 23,975 ft | no position received |
| VLJ603 | route not resolved | 23 Nov 2017, 20:0623 Nov 2017 | 23 Nov 2017, 20:07 | 26,775 ft | no position received |
| VLJ550 | route not resolved | 22 Nov 2017, 21:4922 Nov 2017 | 22 Nov 2017, 22:06 | 25,975 ft | no position received |
| VLJ520 | route not resolved | 16 Nov 2017, 18:1516 Nov 2017 | 16 Nov 2017, 18:44 | 22,550 ft | no position received |
| VLJ601 | route not resolved | 10 Nov 2017, 16:2910 Nov 2017 | 10 Nov 2017, 16:53 | 24,900 ft | no position received |
| VLJ560 | route not resolved | 1 Nov 2017, 16:111 Nov 2017 | 1 Nov 2017, 16:46 | 29,150 ft | no position received |
| VLJ560 | route not resolved | 1 Nov 2017, 14:561 Nov 2017 | 1 Nov 2017, 15:15 | 24,975 ft | no position received |
| VLJ546 | route not resolved | 26 Oct 2017, 16:3126 Oct 2017 | 26 Oct 2017, 17:07 | 21,925 ft | no position received |
| VLJ546 | route not resolved | 25 Oct 2017, 08:2625 Oct 2017 | 25 Oct 2017, 08:53 | 27,500 ft | no position received |
| VLJ553 | route not resolved | 24 Oct 2017, 20:1124 Oct 2017 | 24 Oct 2017, 20:46 | 21,425 ft | no position received |
| VLJ553 | route not resolved | 24 Oct 2017, 10:5824 Oct 2017 | 24 Oct 2017, 11:19 | 34,975 ft | no position received |
| VLJ513L | route not resolved | 4 Oct 2017, 19:484 Oct 2017 | 4 Oct 2017, 20:24 | 21,800 ft | no position received |
| not transmitted | route not resolved | 3 Oct 2017, 09:453 Oct 2017 | 3 Oct 2017, 09:48 | 34,950 ft | no position received |
| VLJ511 | route not resolved | 30 Sept 2017, 23:5430 Sept 2017 | 1 Oct 2017, 00:13 | 35,000 ft | no position received |
