Back to the log
Aircraft
F-HAPE
Regular
- Mode S hex
- 3981E4
- Type
- Beech 1900B190
- Manufacturer
- Beech
- Serial number
- UE-367
- Year built
- 199927 years old
- Operator
- Twin Jet (TJT)
- Country of registration
France- First contact
- 11 Apr 2016, 11:12
- Last contact
- 22 Sept 2026, 19:11
- Logged visits
- 2,407
The station's story
- Cumulative contact time
- 964 h
- Distinct days
- 992
- Highest captured altitude
- 36,000 ft
- 37 corrupted frame(s) excluded from this maximum
- Discovery rank
- #5,211 of 60,212
- Longest contact
- 1 h 38 min
Observed callsigns
TJT (1,106 contacts, 2016-2026) · POF (727 contacts, 2018-2022) · ITI (277 contacts, 2019-2026)
Operator as per the registry of 28 Sept 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| TJT32SQ | LFBO > LFJL | 11 May 2017, 09:5311 May 2017 | 11 May 2017, 10:02 | 18,000 ft | no position received |
| not transmitted | route not resolved | 11 May 2017, 07:0211 May 2017 | 11 May 2017, 07:02 | 19,000 ft | no position received |
| TJT36SQ | LFBO > LFJL | 10 May 2017, 21:1510 May 2017 | 10 May 2017, 21:25 | 16,550 ft | no position received |
| TJT35LX | LFJL > LFBO | 10 May 2017, 18:2910 May 2017 | 10 May 2017, 18:30 | 19,000 ft | no position received |
| TJT32SQ | LFBO > LFJL | 10 May 2017, 09:5710 May 2017 | 10 May 2017, 10:07 | 18,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 9 May 2017, 20:119 May 2017 | 9 May 2017, 20:59 | 35,000 ft | no position received |
| TJT25HY | LFJL > LFML | 9 May 2017, 17:499 May 2017 | 9 May 2017, 18:34 | 20,950 ft | no position received |
| TJT22KZ | LFML > LFJL | 9 May 2017, 09:129 May 2017 | 9 May 2017, 10:01 | 16,000 ft | no position received |
| TJT21HY | route not resolved | 9 May 2017, 06:479 May 2017 | 9 May 2017, 07:32 | 22,975 ft | no position received |
| TJT26KZ | LFML > LFJL | 5 May 2017, 19:245 May 2017 | 5 May 2017, 20:09 | 18,000 ft | no position received |
| TJT041P | route not resolved | 27 Apr 2017, 13:4227 Apr 2017 | 27 Apr 2017, 14:03 | 23,975 ft | no position received |
| TJT001A | route not resolved | 12 Apr 2017, 16:5012 Apr 2017 | 12 Apr 2017, 17:00 | 20,000 ft | no position received |
| not transmitted | route not resolved | 5 Mar 2017, 20:015 Mar 2017 | 5 Mar 2017, 20:16 | 35,825 ft | no position received |
| TJT336A | route not resolved | 5 Mar 2017, 11:185 Mar 2017 | 5 Mar 2017, 11:27 | 23,000 ft | no position received |
| TJT056P | route not resolved | 17 Feb 2017, 16:3717 Feb 2017 | 17 Feb 2017, 16:45 | 20,000 ft | no position received |
| TJT031 | route not resolved | 14 Feb 2017, 07:3814 Feb 2017 | 14 Feb 2017, 08:26 | 23,000 ft | no position received |
| TJT037 | route not resolved | 13 Feb 2017, 18:4613 Feb 2017 | 13 Feb 2017, 19:33 | 24,000 ft | no position received |
| TJT038 | route not resolved | 9 Feb 2017, 19:019 Feb 2017 | 9 Feb 2017, 19:47 | 23,000 ft | no position received |
| TJT037 | route not resolved | 9 Feb 2017, 17:079 Feb 2017 | 9 Feb 2017, 17:55 | 19,600 ft | no position received |
| TJT031 | route not resolved | 9 Feb 2017, 07:479 Feb 2017 | 9 Feb 2017, 08:36 | 23,000 ft | no position received |
| TJT037 | route not resolved | 8 Feb 2017, 19:148 Feb 2017 | 8 Feb 2017, 20:01 | 5,450 ft | no position received |
| TJT031 | route not resolved | 8 Feb 2017, 07:478 Feb 2017 | 8 Feb 2017, 08:29 | 20,975 ft | no position received |
| TJT031 | route not resolved | 7 Feb 2017, 19:157 Feb 2017 | 7 Feb 2017, 20:04 | 34,000 ft | no position received |
| TJT031 | route not resolved | 7 Feb 2017, 07:367 Feb 2017 | 7 Feb 2017, 08:25 | 23,000 ft | no position received |
| TJT037 | route not resolved | 6 Feb 2017, 18:406 Feb 2017 | 6 Feb 2017, 19:28 | 18,000 ft | no position received |
