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
- 19 Nov 2026, 21:05
- Logged visits
- 2,344
The station's story
- Cumulative contact time
- 1,102 h
- Distinct days
- 967
- Highest captured altitude
- 36,000 ft
- 23 corrupted frame(s) excluded from this maximum
- Discovery rank
- #5,342 of 60,729
- Longest contact
- 1 h 17 min
Observed callsigns
TJT (1,655 contacts, 2016-2026) · ITI (351 contacts, 2019-2026) · POF (118 contacts, 2016-2026)
Operator as per the registry of 16 Nov 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| TJT22KZ | LFML > LFJL | 21 Feb 2019, 10:1021 Feb 2019 | 21 Feb 2019, 10:42 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 21 Feb 2019, 06:4721 Feb 2019 | 21 Feb 2019, 07:35 | 23,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 20 Feb 2019, 20:2220 Feb 2019 | 20 Feb 2019, 20:56 | 18,000 ft | no position received |
| TJT25HY | LFJL > LFML | 20 Feb 2019, 17:5320 Feb 2019 | 20 Feb 2019, 18:37 | 22,975 ft | no position received |
| TJT22KZ | LFML > LFJL | 20 Feb 2019, 09:1820 Feb 2019 | 20 Feb 2019, 09:49 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 20 Feb 2019, 06:4820 Feb 2019 | 20 Feb 2019, 07:33 | 23,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 19 Feb 2019, 09:2019 Feb 2019 | 19 Feb 2019, 09:48 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 19 Feb 2019, 06:4519 Feb 2019 | 19 Feb 2019, 07:33 | 21,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 18 Feb 2019, 09:1618 Feb 2019 | 18 Feb 2019, 09:44 | 17,700 ft | no position received |
| TJT21HY | route not resolved | 18 Feb 2019, 06:5018 Feb 2019 | 18 Feb 2019, 07:30 | 21,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 15 Feb 2019, 19:2315 Feb 2019 | 15 Feb 2019, 19:58 | 17,875 ft | no position received |
| TJT25HY | LFJL > LFML | 8 Feb 2019, 16:308 Feb 2019 | 8 Feb 2019, 17:18 | 23,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 7 Feb 2019, 20:237 Feb 2019 | 7 Feb 2019, 21:05 | 17,975 ft | no position received |
| TJT25HY | LFJL > LFML | 7 Feb 2019, 17:507 Feb 2019 | 7 Feb 2019, 18:39 | 23,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 7 Feb 2019, 09:167 Feb 2019 | 7 Feb 2019, 09:51 | 17,975 ft | no position received |
| TJT21HY | route not resolved | 7 Feb 2019, 06:507 Feb 2019 | 7 Feb 2019, 07:45 | 22,975 ft | no position received |
| TJT26KZ | LFML > LFJL | 6 Feb 2019, 20:126 Feb 2019 | 6 Feb 2019, 20:50 | 17,975 ft | no position received |
| TJT25HY | LFJL > LFML | 6 Feb 2019, 17:526 Feb 2019 | 6 Feb 2019, 18:45 | 18,075 ft | no position received |
| TJT22KZ | LFML > LFJL | 6 Feb 2019, 09:116 Feb 2019 | 6 Feb 2019, 09:52 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 6 Feb 2019, 06:446 Feb 2019 | 6 Feb 2019, 07:35 | 21,825 ft | no position received |
| TJT26KZ | LFML > LFJL | 5 Feb 2019, 20:205 Feb 2019 | 5 Feb 2019, 21:10 | 19,975 ft | no position received |
| TJT25HY | LFJL > LFML | 25 Jan 2019, 16:3625 Jan 2019 | 25 Jan 2019, 17:08 | 23,000 ft | no position received |
| not transmitted | route not resolved | 24 Jan 2019, 18:0224 Jan 2019 | 24 Jan 2019, 18:12 | 19,000 ft | no position received |
| TJT36SQ | LFBO > LFJL | 23 Jan 2019, 21:2423 Jan 2019 | 23 Jan 2019, 21:25 | 18,000 ft | no position received |
| TJT36SQ | LFBO > LFJL | 22 Jan 2019, 21:2622 Jan 2019 | 22 Jan 2019, 21:26 | 22,000 ft | no position received |
