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 |
|---|---|---|---|---|---|
| VLJ040A | route not resolved | 30 Jan 2019, 15:5330 Jan 2019 | 30 Jan 2019, 16:11 | 32,850 ft | no position received |
| VLJ040A | route not resolved | 29 Jan 2019, 08:4129 Jan 2019 | 29 Jan 2019, 09:04 | 32,875 ft | no position received |
| VLJ047A | route not resolved | 21 Jan 2019, 18:1621 Jan 2019 | 21 Jan 2019, 18:30 | 17,950 ft | no position received |
| VLJ047A | route not resolved | 21 Jan 2019, 12:0421 Jan 2019 | 21 Jan 2019, 12:25 | 1,275 ft | no position received |
| not transmitted | route not resolved | 20 Jan 2019, 17:4820 Jan 2019 | 20 Jan 2019, 17:48 | 14,250 ft | no position received |
| VLJ003A | route not resolved | 3 Jan 2019, 18:043 Jan 2019 | 3 Jan 2019, 18:13 | 23,575 ft | no position received |
| not transmitted | route not resolved | 3 Jan 2019, 09:373 Jan 2019 | 3 Jan 2019, 09:50 | 34,975 ft | no position received |
| VLJ944G | route not resolved | 30 Dec 2018, 09:4230 Dec 2018 | 30 Dec 2018, 10:10 | 33,975 ft | no position received |
| VLJ944G | route not resolved | 29 Dec 2018, 16:0429 Dec 2018 | 29 Dec 2018, 16:36 | 34,975 ft | no position received |
| VLJ870Z | route not resolved | 22 Dec 2018, 10:4322 Dec 2018 | 22 Dec 2018, 10:55 | 17,950 ft | no position received |
| VLJ870Z | route not resolved | 21 Dec 2018, 21:4621 Dec 2018 | 21 Dec 2018, 21:57 | 34,100 ft | no position received |
| VLJ902Z | route not resolved | 5 Dec 2018, 17:065 Dec 2018 | 5 Dec 2018, 17:18 | 33,000 ft | no position received |
| VLJ902Z | route not resolved | 5 Dec 2018, 09:035 Dec 2018 | 5 Dec 2018, 09:18 | 34,950 ft | no position received |
| VLJ802M | route not resolved | 2 Dec 2018, 18:402 Dec 2018 | 2 Dec 2018, 18:53 | 35,950 ft | no position received |
| VLJ876K | route not resolved | 29 Nov 2018, 17:4129 Nov 2018 | 29 Nov 2018, 17:52 | 34,300 ft | no position received |
| not transmitted | route not resolved | 29 Nov 2018, 07:4929 Nov 2018 | 29 Nov 2018, 07:56 | 34,950 ft | no position received |
| not transmitted | route not resolved | 22 Nov 2018, 20:1822 Nov 2018 | 22 Nov 2018, 20:20 | 18,950 ft | no position received |
| VLJ821K | route not resolved | 21 Nov 2018, 18:0221 Nov 2018 | 21 Nov 2018, 18:21 | 28,200 ft | no position received |
| VLJ821K | route not resolved | 20 Nov 2018, 08:4920 Nov 2018 | 20 Nov 2018, 09:21 | 26,050 ft | no position received |
| VLJ878Z | route not resolved | 19 Nov 2018, 20:3319 Nov 2018 | 19 Nov 2018, 21:06 | 23,850 ft | no position received |
| VLJ878Z | route not resolved | 19 Nov 2018, 18:0119 Nov 2018 | 19 Nov 2018, 18:36 | 31,000 ft | no position received |
| VLJ843K | route not resolved | 18 Nov 2018, 17:2418 Nov 2018 | 18 Nov 2018, 17:34 | 29,625 ft | no position received |
| VLJ843K | route not resolved | 16 Nov 2018, 10:3916 Nov 2018 | 16 Nov 2018, 10:40 | 34,950 ft | no position received |
| VLJ845A | route not resolved | 15 Nov 2018, 11:1715 Nov 2018 | 15 Nov 2018, 11:22 | 31,975 ft | no position received |
| VLJ837Z | route not resolved | 11 Nov 2018, 11:5511 Nov 2018 | 11 Nov 2018, 12:19 | 26,000 ft | no position received |
