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,664 of 57,376
- 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 |
|---|---|---|---|---|---|
| TJT048 | route not resolved | 10 Feb 2017, 20:2810 Feb 2017 | 10 Feb 2017, 21:04 | 7,800 ft | no position received |
| TJT047 | route not resolved | 10 Feb 2017, 18:0610 Feb 2017 | 10 Feb 2017, 18:44 | 19,600 ft | no position received |
| TJT048 | route not resolved | 9 Feb 2017, 20:089 Feb 2017 | 9 Feb 2017, 20:52 | 5,900 ft | no position received |
| TJT047 | route not resolved | 9 Feb 2017, 18:029 Feb 2017 | 9 Feb 2017, 18:47 | 19,100 ft | no position received |
| TJT042 | route not resolved | 9 Feb 2017, 08:249 Feb 2017 | 9 Feb 2017, 08:59 | 8,500 ft | no position received |
| TJT041 | route not resolved | 9 Feb 2017, 06:209 Feb 2017 | 9 Feb 2017, 07:02 | 19,800 ft | no position received |
| TJT048 | route not resolved | 8 Feb 2017, 20:178 Feb 2017 | 8 Feb 2017, 20:54 | 7,000 ft | no position received |
| TJT047 | route not resolved | 8 Feb 2017, 18:078 Feb 2017 | 8 Feb 2017, 18:52 | 19,800 ft | no position received |
| TJT042 | route not resolved | 8 Feb 2017, 09:318 Feb 2017 | 8 Feb 2017, 10:09 | 7,600 ft | no position received |
| TJT041 | route not resolved | 8 Feb 2017, 06:248 Feb 2017 | 8 Feb 2017, 07:09 | 21,600 ft | no position received |
| TJT048 | route not resolved | 7 Feb 2017, 20:197 Feb 2017 | 7 Feb 2017, 20:56 | 8,400 ft | no position received |
| TJT047 | route not resolved | 7 Feb 2017, 18:177 Feb 2017 | 7 Feb 2017, 19:03 | 18,800 ft | no position received |
| TJT042 | route not resolved | 7 Feb 2017, 08:287 Feb 2017 | 7 Feb 2017, 09:00 | 11,200 ft | no position received |
| TJT041 | route not resolved | 7 Feb 2017, 06:257 Feb 2017 | 7 Feb 2017, 07:13 | 20,400 ft | no position received |
| TJT048 | route not resolved | 6 Feb 2017, 20:196 Feb 2017 | 6 Feb 2017, 20:52 | 7,400 ft | no position received |
| TJT047 | route not resolved | 6 Feb 2017, 18:076 Feb 2017 | 6 Feb 2017, 18:55 | 18,000 ft | no position received |
| TJT042 | route not resolved | 6 Feb 2017, 08:386 Feb 2017 | 6 Feb 2017, 09:17 | 5,300 ft | no position received |
| TJT041 | route not resolved | 6 Feb 2017, 06:386 Feb 2017 | 6 Feb 2017, 07:23 | 19,200 ft | no position received |
| TJT048 | route not resolved | 3 Feb 2017, 20:233 Feb 2017 | 3 Feb 2017, 21:00 | 8,300 ft | no position received |
| TJT047 | route not resolved | 3 Feb 2017, 18:183 Feb 2017 | 3 Feb 2017, 19:01 | 18,300 ft | no position received |
| TJT048 | route not resolved | 2 Feb 2017, 20:192 Feb 2017 | 2 Feb 2017, 20:54 | 8,700 ft | no position received |
| TJT047 | route not resolved | 2 Feb 2017, 18:092 Feb 2017 | 2 Feb 2017, 18:52 | 19,800 ft | no position received |
| TJT042 | route not resolved | 2 Feb 2017, 08:282 Feb 2017 | 2 Feb 2017, 09:05 | 8,200 ft | no position received |
| TJT041 | route not resolved | 2 Feb 2017, 06:232 Feb 2017 | 2 Feb 2017, 07:07 | 19,200 ft | no position received |
| TJT048 | route not resolved | 1 Feb 2017, 20:181 Feb 2017 | 1 Feb 2017, 20:56 | 10,500 ft | no position received |
