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
- not in the registry
- Country of registration
Guernsey
- First contact
- 26 Aug 2016, 11:17
- Last contact
- 5 Oct 2026, 15:16
- Logged visits
- 225
The station's story
- Cumulative contact time
- 90 h
- Distinct days
- 173
- Highest captured altitude
- 47,000 ft
- Discovery rank
- #17,294 of 60,431
- Longest contact
- 2 h 44 min
Observed callsigns
VLZ (215 contacts, 2016-2026) · VLX (1 contacts, 2026)
Operator as per the registry of 12 Oct 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLZ688 | route not resolved | 11 Mar 2019, 15:4511 Mar 2019 | 11 Mar 2019, 15:57 | 34,000 ft | no position received |
| VLZ688 | route not resolved | 7 Mar 2019, 14:437 Mar 2019 | 7 Mar 2019, 15:03 | 19,000 ft | no position received |
| VLZ717 | route not resolved | 27 Feb 2019, 10:1427 Feb 2019 | 27 Feb 2019, 10:38 | 37,975 ft | no position received |
| VLZ717 | route not resolved | 26 Feb 2019, 18:0726 Feb 2019 | 26 Feb 2019, 18:31 | 24,575 ft | no position received |
| VLZ695 | route not resolved | 23 Feb 2019, 16:0723 Feb 2019 | 23 Feb 2019, 16:31 | 35,975 ft | no position received |
| VLZ716 | route not resolved | 23 Feb 2019, 14:2823 Feb 2019 | 23 Feb 2019, 14:41 | 19,000 ft | no position received |
| VLZ716 | route not resolved | 23 Feb 2019, 12:1523 Feb 2019 | 23 Feb 2019, 12:37 | 25,050 ft | no position received |
| VLZ716 | route not resolved | 22 Feb 2019, 14:4422 Feb 2019 | 22 Feb 2019, 15:03 | 37,975 ft | no position received |
| VLZ716 | route not resolved | 17 Feb 2019, 17:5017 Feb 2019 | 17 Feb 2019, 18:06 | 9,125 ft | no position received |
| VLZ695 | route not resolved | 17 Feb 2019, 16:1817 Feb 2019 | 17 Feb 2019, 16:42 | 16,725 ft | no position received |
| VLZ690 | route not resolved | 16 Feb 2019, 16:4016 Feb 2019 | 16 Feb 2019, 16:54 | 30,000 ft | no position received |
| VLZ690 | route not resolved | 10 Feb 2019, 13:5210 Feb 2019 | 10 Feb 2019, 14:14 | 38,000 ft | no position received |
| VLZ690 | route not resolved | 7 Feb 2019, 14:287 Feb 2019 | 7 Feb 2019, 14:48 | 19,025 ft | no position received |
| VLZ697 | route not resolved | 25 Jan 2019, 14:3025 Jan 2019 | 25 Jan 2019, 14:38 | 6,325 ft | no position received |
| VLZ686 | route not resolved | 7 Jan 2019, 20:517 Jan 2019 | 7 Jan 2019, 21:14 | 38,000 ft | no position received |
| VLZ687 | route not resolved | 19 Dec 2018, 15:1119 Dec 2018 | 19 Dec 2018, 15:16 | 26,075 ft | no position received |
| VLZ687 | route not resolved | 19 Dec 2018, 13:1419 Dec 2018 | 19 Dec 2018, 13:34 | 17,675 ft | no position received |
| VLZ672 | route not resolved | 4 Nov 2018, 20:454 Nov 2018 | 4 Nov 2018, 21:02 | 39,000 ft | no position received |
| not transmitted | route not resolved | 3 Nov 2018, 13:353 Nov 2018 | 3 Nov 2018, 13:36 | 38,050 ft | no position received |
| VLZ645 | route not resolved | 17 Oct 2018, 16:0417 Oct 2018 | 17 Oct 2018, 16:08 | 38,025 ft | no position received |
| VLZ645 | route not resolved | 10 Oct 2018, 13:0010 Oct 2018 | 10 Oct 2018, 13:00 | 37,000 ft | no position received |
| VLZ607 | route not resolved | 12 Jul 2018, 14:3812 Jul 2018 | 12 Jul 2018, 15:05 | 38,025 ft | no position received |
| VLZ607 | route not resolved | 12 Jul 2018, 13:2712 Jul 2018 | 12 Jul 2018, 13:40 | 18,525 ft | no position received |
| VLZ603 | route not resolved | 9 Jul 2018, 20:279 Jul 2018 | 9 Jul 2018, 20:48 | 40,100 ft | no position received |
| VLZ603 | route not resolved | 9 Jul 2018, 10:409 Jul 2018 | 9 Jul 2018, 10:53 | 35,000 ft | no position received |
