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 |
|---|---|---|---|---|---|
| VLZ601 | route not resolved | 21 Jun 2018, 19:2121 Jun 2018 | 21 Jun 2018, 19:51 | 38,000 ft | no position received |
| VLZ601 | route not resolved | 21 Jun 2018, 17:3721 Jun 2018 | 21 Jun 2018, 17:56 | 34,000 ft | no position received |
| VLZ590 | route not resolved | 15 Jun 2018, 17:2115 Jun 2018 | 15 Jun 2018, 17:44 | 38,100 ft | no position received |
| VLZ590 | route not resolved | 15 Jun 2018, 13:0315 Jun 2018 | 15 Jun 2018, 13:06 | 37,000 ft | no position received |
| VLZ584 | route not resolved | 30 May 2018, 21:1130 May 2018 | 30 May 2018, 21:43 | 36,075 ft | no position received |
| VLZ584 | route not resolved | 28 May 2018, 16:4328 May 2018 | 28 May 2018, 17:21 | 1,375 ft | no position received |
| VLZ549 | route not resolved | 20 May 2018, 16:5220 May 2018 | 20 May 2018, 16:58 | 38,000 ft | no position received |
| VLZ549 | route not resolved | 20 May 2018, 14:0320 May 2018 | 20 May 2018, 14:29 | 33,025 ft | no position received |
| VLZ536 | route not resolved | 1 May 2018, 09:401 May 2018 | 1 May 2018, 10:15 | 39,025 ft | no position received |
| VLZ539 | route not resolved | 13 Apr 2018, 17:0013 Apr 2018 | 13 Apr 2018, 17:19 | 32,050 ft | no position received |
| VLZ539 | route not resolved | 10 Apr 2018, 15:1910 Apr 2018 | 10 Apr 2018, 15:40 | 18,150 ft | no position received |
| VLZ517 | route not resolved | 3 Apr 2018, 13:453 Apr 2018 | 3 Apr 2018, 14:02 | 36,075 ft | no position received |
| not transmitted | route not resolved | 24 Mar 2018, 12:2624 Mar 2018 | 24 Mar 2018, 12:26 | 39,025 ft | no position received |
| VLZ472 | route not resolved | 18 Mar 2018, 12:0918 Mar 2018 | 18 Mar 2018, 12:25 | 36,100 ft | no position received |
| VLZ472 | route not resolved | 18 Mar 2018, 10:5018 Mar 2018 | 18 Mar 2018, 11:10 | 19,150 ft | no position received |
| VLZ472 | route not resolved | 15 Mar 2018, 12:4415 Mar 2018 | 15 Mar 2018, 13:03 | 37,300 ft | no position received |
| VLZ472 | route not resolved | 15 Mar 2018, 11:3015 Mar 2018 | 15 Mar 2018, 11:50 | 19,025 ft | no position received |
| VLZ521 | route not resolved | 12 Mar 2018, 14:4512 Mar 2018 | 12 Mar 2018, 15:06 | 36,000 ft | no position received |
| VLZ521 | route not resolved | 12 Mar 2018, 12:2112 Mar 2018 | 12 Mar 2018, 12:42 | 17,325 ft | no position received |
| VLZ519 | route not resolved | 11 Mar 2018, 15:5611 Mar 2018 | 11 Mar 2018, 16:16 | 24,475 ft | no position received |
| VLZ516 | route not resolved | 9 Mar 2018, 14:459 Mar 2018 | 9 Mar 2018, 15:05 | 17,125 ft | no position received |
| VLZ469 | route not resolved | 21 Feb 2018, 18:0321 Feb 2018 | 21 Feb 2018, 18:31 | 36,000 ft | no position received |
| VLZ469 | route not resolved | 18 Feb 2018, 15:2018 Feb 2018 | 18 Feb 2018, 15:47 | 19,175 ft | no position received |
| VLZ454 | route not resolved | 21 Jan 2018, 17:0721 Jan 2018 | 21 Jan 2018, 17:35 | 38,075 ft | no position received |
| VLZ454 | route not resolved | 19 Jan 2018, 18:5419 Jan 2018 | 19 Jan 2018, 19:13 | 22,850 ft | no position received |
