Back to the log
Aircraft
F-GTVC
Regular
- Mode S hex
- 394EA2
- Type
- Beech 1900B190
- Manufacturer
- Beech
- Serial number
- UE-349
- Year built
- 199828 years old
- Operator
- Twin Jet (TJT)
- Country of registration
France- First contact
- 27 May 2016, 20:25
- Last contact
- 20 Jun 2026, 16:40
- Logged visits
- 2,904
The station's story
- Cumulative contact time
- 1,244 h
- Distinct days
- 983
- Highest captured altitude
- 36,000 ft
- 39 corrupted frame(s) excluded from this maximum
- Discovery rank
- #12,130 of 57,441
- Longest contact
- 1 h 18 min
Observed callsigns
TJT (2,261 contacts, 2016-2026) · ITI (226 contacts, 2019-2026) · HOP (69 contacts, 2017-2018)
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 |
|---|---|---|---|---|---|
| TJT25HY | LFJL > LFML | 28 Feb 2017, 17:4628 Feb 2017 | 28 Feb 2017, 18:48 | 21,325 ft | no position received |
| TJT22KZ | LFML > LFJL | 28 Feb 2017, 09:2028 Feb 2017 | 28 Feb 2017, 10:00 | 17,025 ft | no position received |
| TJT21HY | route not resolved | 28 Feb 2017, 06:4728 Feb 2017 | 28 Feb 2017, 07:51 | 19,925 ft | no position received |
| TJT26KZ | LFML > LFJL | 27 Feb 2017, 20:1627 Feb 2017 | 27 Feb 2017, 20:55 | 18,000 ft | no position received |
| TJT25HY | LFJL > LFML | 27 Feb 2017, 17:5027 Feb 2017 | 27 Feb 2017, 18:50 | 20,850 ft | no position received |
| TJT76QD | route not resolved | 27 Feb 2017, 16:2927 Feb 2017 | 27 Feb 2017, 16:38 | 21,925 ft | no position received |
| TJT22KZ | LFML > LFJL | 27 Feb 2017, 09:1627 Feb 2017 | 27 Feb 2017, 09:58 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 27 Feb 2017, 06:4627 Feb 2017 | 27 Feb 2017, 07:48 | 20,975 ft | no position received |
| TJT26KZ | LFML > LFJL | 24 Feb 2017, 19:2824 Feb 2017 | 24 Feb 2017, 20:24 | 16,000 ft | no position received |
| TJT340A | route not resolved | 19 Feb 2017, 13:0119 Feb 2017 | 19 Feb 2017, 13:12 | 23,000 ft | no position received |
| TJT052P | route not resolved | 17 Feb 2017, 21:4017 Feb 2017 | 17 Feb 2017, 21:44 | 14,300 ft | no position received |
| TJT641B | route not resolved | 17 Feb 2017, 19:4517 Feb 2017 | 17 Feb 2017, 20:26 | 8,900 ft | no position received |
| TJT641A | route not resolved | 15 Feb 2017, 08:3315 Feb 2017 | 15 Feb 2017, 09:23 | 22,000 ft | no position received |
| TJT021P | route not resolved | 7 Feb 2017, 07:367 Feb 2017 | 7 Feb 2017, 07:49 | 19,100 ft | no position received |
| not transmitted | route not resolved | 3 Feb 2017, 09:343 Feb 2017 | 3 Feb 2017, 09:37 | 18,825 ft | no position received |
| TJT041P | route not resolved | 2 Feb 2017, 20:452 Feb 2017 | 2 Feb 2017, 21:20 | 10,575 ft | no position received |
| TJT620B | route not resolved | 2 Feb 2017, 18:152 Feb 2017 | 2 Feb 2017, 18:59 | 20,450 ft | no position received |
| TJT310B | route not resolved | 1 Feb 2017, 23:481 Feb 2017 | 2 Feb 2017, 00:05 | 22,000 ft | no position received |
| TJT310A | route not resolved | 1 Feb 2017, 10:361 Feb 2017 | 1 Feb 2017, 10:56 | 37,000 ft | no position received |
| TJT022P | route not resolved | 31 Jan 2017, 21:1931 Jan 2017 | 31 Jan 2017, 21:31 | 22,000 ft | no position received |
| TJT620A | route not resolved | 31 Jan 2017, 19:3531 Jan 2017 | 31 Jan 2017, 20:10 | 7,725 ft | no position received |
| TJT21P | route not resolved | 31 Jan 2017, 16:0731 Jan 2017 | 31 Jan 2017, 17:02 | 21,850 ft | no position received |
| TJT051P | route not resolved | 13 Jan 2017, 14:3113 Jan 2017 | 13 Jan 2017, 15:24 | 22,975 ft | no position received |
| TJT22KZ | LFML > LFJL | 12 Jan 2017, 09:2312 Jan 2017 | 12 Jan 2017, 10:00 | 14,000 ft | no position received |
| TJT21HY | route not resolved | 12 Jan 2017, 06:4512 Jan 2017 | 12 Jan 2017, 07:30 | 23,000 ft | no position received |
