Back to the log
Aircraft
F-GTKJ
Regular
- Mode S hex
- 394D49
- Type
- Beech 1900B190
- Manufacturer
- Beech
- Serial number
- UE-348
- Year built
- 199828 years old
- Operator
- Twin Jet (TJT)
- Country of registration
France- First contact
- 21 Apr 2016, 07:32
- Last contact
- 26 Jun 2026, 19:15
- Logged visits
- 2,744
The station's story
- Cumulative contact time
- 1,268 h
- Distinct days
- 1,004
- Highest captured altitude
- 36,000 ft
- 4 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,665 of 57,498
- Longest contact
- 1 h 7 min
Observed callsigns
TJT (1,960 contacts, 2016-2026) · ITI (351 contacts, 2019-2026) · POF (28 contacts, 2016-2022)
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 |
|---|---|---|---|---|---|
| TJT135B | route not resolved | 1 Mar 2019, 13:231 Mar 2019 | 1 Mar 2019, 13:27 | 18,000 ft | no position received |
| TJT25HY | LFJL > LFML | 15 Feb 2019, 16:3015 Feb 2019 | 15 Feb 2019, 17:21 | 22,975 ft | no position received |
| TJT216A | route not resolved | 13 Feb 2019, 08:5013 Feb 2019 | 13 Feb 2019, 09:09 | 22,975 ft | no position received |
| TJT042P | route not resolved | 7 Feb 2019, 21:307 Feb 2019 | 7 Feb 2019, 22:02 | 23,850 ft | no position received |
| TJT218B | route not resolved | 7 Feb 2019, 18:597 Feb 2019 | 7 Feb 2019, 19:11 | 19,225 ft | no position received |
| TJT217B | route not resolved | 6 Feb 2019, 19:066 Feb 2019 | 6 Feb 2019, 19:27 | 1,075 ft | no position received |
| TJT217A | route not resolved | 6 Feb 2019, 10:366 Feb 2019 | 6 Feb 2019, 11:07 | 18,000 ft | no position received |
| TJT031P | route not resolved | 6 Feb 2019, 08:296 Feb 2019 | 6 Feb 2019, 09:03 | 975 ft | no position received |
| TJT013P | route not resolved | 4 Feb 2019, 12:124 Feb 2019 | 4 Feb 2019, 12:45 | 18,000 ft | no position received |
| TJT25HY | LFJL > LFML | 1 Feb 2019, 16:291 Feb 2019 | 1 Feb 2019, 17:32 | 19,500 ft | no position received |
| TJT26KZ | LFML > LFJL | 31 Jan 2019, 20:1631 Jan 2019 | 31 Jan 2019, 20:51 | 18,000 ft | no position received |
| TJT25HY | LFJL > LFML | 31 Jan 2019, 17:5731 Jan 2019 | 31 Jan 2019, 18:54 | 20,425 ft | no position received |
| TJT22KZ | LFML > LFJL | 31 Jan 2019, 09:1431 Jan 2019 | 31 Jan 2019, 09:54 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 31 Jan 2019, 06:5131 Jan 2019 | 31 Jan 2019, 07:37 | 19,575 ft | no position received |
| TJT26KZ | LFML > LFJL | 30 Jan 2019, 20:1830 Jan 2019 | 30 Jan 2019, 21:05 | 16,000 ft | no position received |
| TJT25HY | LFJL > LFML | 30 Jan 2019, 17:5530 Jan 2019 | 30 Jan 2019, 18:44 | 22,425 ft | no position received |
| TJT22KZ | LFML > LFJL | 30 Jan 2019, 11:0530 Jan 2019 | 30 Jan 2019, 11:42 | 16,000 ft | no position received |
| TJT21HY | route not resolved | 30 Jan 2019, 08:2930 Jan 2019 | 30 Jan 2019, 09:23 | 22,975 ft | no position received |
| not transmitted | route not resolved | 29 Jan 2019, 20:4929 Jan 2019 | 29 Jan 2019, 20:49 | not transmitted | no position received |
| TJT25HY | LFJL > LFML | 29 Jan 2019, 18:0529 Jan 2019 | 29 Jan 2019, 18:22 | 23,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 29 Jan 2019, 09:0729 Jan 2019 | 29 Jan 2019, 09:50 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 29 Jan 2019, 06:5529 Jan 2019 | 29 Jan 2019, 07:40 | 23,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 28 Jan 2019, 22:1228 Jan 2019 | 28 Jan 2019, 23:02 | 16,000 ft | no position received |
| TJT109C | route not resolved | 19 Jan 2019, 15:1519 Jan 2019 | 19 Jan 2019, 15:22 | 21,850 ft | no position received |
| TJT109B | route not resolved | 19 Jan 2019, 12:0919 Jan 2019 | 19 Jan 2019, 12:25 | 18,000 ft | no position received |
