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
- 16 Oct 2026, 18:57
- Logged visits
- 2,810
The station's story
- Cumulative contact time
- 1,287 h
- Distinct days
- 1,030
- Highest captured altitude
- 36,000 ft
- 4 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,703 of 60,447
- Longest contact
- 1 h 7 min
Observed callsigns
TJT (2,017 contacts, 2016-2026) · ITI (359 contacts, 2019-2026) · POF (28 contacts, 2016-2022)
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 |
|---|---|---|---|---|---|
| TJT032 | route not resolved | 19 Oct 2016, 07:5419 Oct 2016 | 19 Oct 2016, 08:40 | 23,000 ft | no position received |
| not transmitted | route not resolved | 19 Oct 2016, 07:4519 Oct 2016 | 19 Oct 2016, 07:49 | 23,000 ft | no position received |
| TJT037 | route not resolved | 18 Oct 2016, 19:1018 Oct 2016 | 18 Oct 2016, 19:58 | 22,100 ft | no position received |
| TJT032 | route not resolved | 18 Oct 2016, 07:3518 Oct 2016 | 18 Oct 2016, 08:30 | 23,000 ft | no position received |
| TJT037 | route not resolved | 17 Oct 2016, 18:4517 Oct 2016 | 17 Oct 2016, 19:28 | 20,500 ft | no position received |
| TJT367B | route not resolved | 17 Oct 2016, 00:3117 Oct 2016 | 17 Oct 2016, 01:07 | 17,600 ft | no position received |
| TJT367A | route not resolved | 16 Oct 2016, 09:3016 Oct 2016 | 16 Oct 2016, 10:17 | 23,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 14 Oct 2016, 19:2614 Oct 2016 | 14 Oct 2016, 20:06 | 18,000 ft | no position received |
| TJT041P | route not resolved | 6 Oct 2016, 13:206 Oct 2016 | 6 Oct 2016, 13:36 | 17,000 ft | no position received |
| TJT042 | route not resolved | 6 Oct 2016, 08:256 Oct 2016 | 6 Oct 2016, 09:05 | 5,950 ft | no position received |
| TJT041 | route not resolved | 6 Oct 2016, 06:136 Oct 2016 | 6 Oct 2016, 07:04 | 23,725 ft | no position received |
| TJT048 | route not resolved | 5 Oct 2016, 20:095 Oct 2016 | 5 Oct 2016, 20:44 | 8,525 ft | no position received |
| TJT047 | route not resolved | 5 Oct 2016, 18:025 Oct 2016 | 5 Oct 2016, 18:49 | 17,375 ft | no position received |
| TJT042 | route not resolved | 5 Oct 2016, 08:195 Oct 2016 | 5 Oct 2016, 08:56 | 5,425 ft | no position received |
| TJT041 | route not resolved | 5 Oct 2016, 06:165 Oct 2016 | 5 Oct 2016, 07:03 | 18,775 ft | no position received |
| TJT048 | route not resolved | 4 Oct 2016, 20:004 Oct 2016 | 4 Oct 2016, 20:38 | 4,850 ft | no position received |
| TJT047 | route not resolved | 4 Oct 2016, 17:564 Oct 2016 | 4 Oct 2016, 18:45 | 18,600 ft | no position received |
| TJT042 | route not resolved | 4 Oct 2016, 08:274 Oct 2016 | 4 Oct 2016, 09:07 | 5,725 ft | no position received |
| TJT041 | route not resolved | 4 Oct 2016, 06:244 Oct 2016 | 4 Oct 2016, 07:09 | 18,150 ft | no position received |
| TJT048 | route not resolved | 3 Oct 2016, 20:113 Oct 2016 | 3 Oct 2016, 20:52 | 5,175 ft | no position received |
| TJT047 | route not resolved | 3 Oct 2016, 18:103 Oct 2016 | 3 Oct 2016, 18:59 | 20,025 ft | no position received |
| TJT048 | route not resolved | 30 Sept 2016, 20:1030 Sept 2016 | 30 Sept 2016, 20:48 | 8,175 ft | no position received |
| TJT047 | route not resolved | 30 Sept 2016, 18:0530 Sept 2016 | 30 Sept 2016, 18:52 | 19,600 ft | no position received |
| TJT048 | route not resolved | 29 Sept 2016, 20:2129 Sept 2016 | 29 Sept 2016, 21:02 | 7,700 ft | no position received |
| TJT047 | route not resolved | 29 Sept 2016, 18:2529 Sept 2016 | 29 Sept 2016, 19:10 | 17,625 ft | no position received |
