Back to the log
Aircraft
2-BANK
Regularcountry captured 17 times
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 26 Aug 2016. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
- Mode S hex
- 43EB4AThis aircraft has carried several registrations: the same airframe, re-registered. Directories give it sometimes as 2-MATO, sometimes as 2-BANK; every contact below is its own.
- Manufacturer
- Bombardier
- Serial number
- 5114
- Year built
- 199234 years old
- Operator
- Volare Aviation
- Country of registration
Guernsey- First contact
- 26 Aug 2016, 11:17
- Last contact
- 8 Aug 2026, 12:18
- Logged visits
- 215
The station's story
- Cumulative contact time
- 86 h
- Distinct days
- 165
- Highest captured altitude
- 47,000 ft
- Discovery rank
- #17,225 of 57,229
- Longest contact
- 2 h 44 min
Observed callsigns
VLZ (206 contacts, 2016-2026)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLZ294B | route not resolved | 10 Jun 2017, 10:5810 Jun 2017 | 10 Jun 2017, 11:24 | 38,975 ft | no position received |
| VLZ171 | route not resolved | 27 May 2017, 16:5627 May 2017 | 27 May 2017, 17:31 | 40,050 ft | no position received |
| VLZ253 | route not resolved | 7 May 2017, 13:397 May 2017 | 7 May 2017, 14:10 | 35,975 ft | no position received |
| VLZ253 | route not resolved | 7 May 2017, 10:517 May 2017 | 7 May 2017, 11:16 | 33,000 ft | no position received |
| VLZ150 | route not resolved | 31 Mar 2017, 13:2531 Mar 2017 | 31 Mar 2017, 13:45 | 27,000 ft | no position received |
| VLZ151 | route not resolved | 16 Mar 2017, 15:3416 Mar 2017 | 16 Mar 2017, 15:58 | 33,950 ft | no position received |
| VLZ151 | route not resolved | 12 Mar 2017, 13:4612 Mar 2017 | 12 Mar 2017, 14:13 | 4,350 ft | no position received |
| 2MATQ | route not resolved | 6 Feb 2017, 12:376 Feb 2017 | 6 Feb 2017, 12:51 | 35,000 ft | no position received |
| VLZ113 | route not resolved | 4 Nov 2016, 18:504 Nov 2016 | 4 Nov 2016, 19:19 | 24,400 ft | no position received |
| VLZ113 | route not resolved | 4 Nov 2016, 06:344 Nov 2016 | 4 Nov 2016, 06:53 | 34,950 ft | no position received |
| VLZ114 | route not resolved | 2 Nov 2016, 12:392 Nov 2016 | 2 Nov 2016, 13:05 | 21,850 ft | no position received |
| VLZ075 | route not resolved | 9 Sept 2016, 12:599 Sept 2016 | 9 Sept 2016, 13:23 | 37,950 ft | no position received |
| VLZ075 | route not resolved | 3 Sept 2016, 12:403 Sept 2016 | 3 Sept 2016, 13:10 | 37,000 ft | no position received |
| VLZ072 | route not resolved | 28 Aug 2016, 16:1228 Aug 2016 | 28 Aug 2016, 16:39 | 38,000 ft | no position received |
| VLZ072 | route not resolved | 26 Aug 2016, 11:1726 Aug 2016 | 26 Aug 2016, 11:45 | 30,350 ft | no position received |
