Back to the log
Aircraft
F-GUME
Regular
- Mode S hex
- 395184
- Type
- Beech 1900B190
- Manufacturer
- Beech
- Serial number
- UE-371
- Year built
- 199927 years old
- Operator
- Twin Jet (TJT)
- Country of registration
France- First contact
- 11 Apr 2016, 15:22
- Last contact
- 16 Jul 2026, 18:58
- Logged visits
- 2,310
The station's story
- Cumulative contact time
- 1,085 h
- Distinct days
- 948
- Highest captured altitude
- 36,000 ft
- 23 corrupted frame(s) excluded from this maximum
- Discovery rank
- #5,306 of 57,466
- Longest contact
- 1 h 17 min
Observed callsigns
TJT (1,642 contacts, 2016-2026) · ITI (335 contacts, 2019-2026) · POF (113 contacts, 2016)
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 |
|---|---|---|---|---|---|
| TJT25HY | LFJL > LFML | 15 Jun 2017, 18:0215 Jun 2017 | 15 Jun 2017, 18:53 | 22,075 ft | no position received |
| TJT32SQ | LFBO > LFJL | 15 Jun 2017, 09:5415 Jun 2017 | 15 Jun 2017, 10:04 | 17,975 ft | no position received |
| not transmitted | route not resolved | 15 Jun 2017, 06:5315 Jun 2017 | 15 Jun 2017, 06:54 | 19,000 ft | no position received |
| not transmitted | route not resolved | 14 Jun 2017, 21:1614 Jun 2017 | 14 Jun 2017, 21:17 | 17,975 ft | no position received |
| not transmitted | route not resolved | 14 Jun 2017, 18:0214 Jun 2017 | 14 Jun 2017, 18:13 | 19,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 14 Jun 2017, 09:1414 Jun 2017 | 14 Jun 2017, 09:59 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 14 Jun 2017, 06:4714 Jun 2017 | 14 Jun 2017, 07:46 | 35,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 13 Jun 2017, 20:3213 Jun 2017 | 13 Jun 2017, 21:09 | 17,950 ft | no position received |
| TJT25HY | LFJL > LFML | 13 Jun 2017, 17:5113 Jun 2017 | 13 Jun 2017, 18:46 | 22,850 ft | no position received |
| TJT22KZ | LFML > LFJL | 13 Jun 2017, 09:2213 Jun 2017 | 13 Jun 2017, 10:05 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 13 Jun 2017, 06:4513 Jun 2017 | 13 Jun 2017, 07:40 | 23,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 12 Jun 2017, 20:1312 Jun 2017 | 12 Jun 2017, 21:04 | 33,950 ft | no position received |
| TJT25HY | LFJL > LFML | 12 Jun 2017, 17:4912 Jun 2017 | 12 Jun 2017, 18:43 | 20,425 ft | no position received |
| TJT22KZ | LFML > LFJL | 12 Jun 2017, 09:1512 Jun 2017 | 12 Jun 2017, 09:51 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 12 Jun 2017, 06:4512 Jun 2017 | 12 Jun 2017, 07:41 | 22,650 ft | no position received |
| TJT26KZ | LFML > LFJL | 9 Jun 2017, 22:299 Jun 2017 | 9 Jun 2017, 23:14 | 16,600 ft | no position received |
| TJT038 | route not resolved | 8 Jun 2017, 18:548 Jun 2017 | 8 Jun 2017, 19:45 | 23,000 ft | no position received |
| TJT037 | route not resolved | 8 Jun 2017, 17:128 Jun 2017 | 8 Jun 2017, 17:58 | 21,075 ft | no position received |
| TJT031 | route not resolved | 8 Jun 2017, 07:398 Jun 2017 | 8 Jun 2017, 08:30 | 23,000 ft | no position received |
| TJT037 | route not resolved | 7 Jun 2017, 19:037 Jun 2017 | 7 Jun 2017, 19:48 | 20,475 ft | no position received |
| TJT031 | route not resolved | 7 Jun 2017, 07:337 Jun 2017 | 7 Jun 2017, 08:33 | 32,975 ft | no position received |
| TJT037 | route not resolved | 6 Jun 2017, 19:086 Jun 2017 | 6 Jun 2017, 19:54 | 21,600 ft | no position received |
| TJT031 | route not resolved | 6 Jun 2017, 07:316 Jun 2017 | 6 Jun 2017, 08:26 | 21,000 ft | no position received |
| TJT037 | route not resolved | 5 Jun 2017, 18:415 Jun 2017 | 5 Jun 2017, 19:25 | 22,750 ft | no position received |
| TJT051P | route not resolved | 2 Jun 2017, 15:332 Jun 2017 | 2 Jun 2017, 16:08 | 22,000 ft | no position received |
