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 |
|---|---|---|---|---|---|
| TJT305C | route not resolved | 4 Feb 2017, 01:304 Feb 2017 | 4 Feb 2017, 01:35 | 750 ft | no position received |
| not transmitted | route not resolved | 4 Feb 2017, 00:274 Feb 2017 | 4 Feb 2017, 00:33 | 10,250 ft | no position received |
| TJT305A | route not resolved | 3 Feb 2017, 09:133 Feb 2017 | 3 Feb 2017, 09:28 | 25,000 ft | no position received |
| TJT038 | route not resolved | 2 Feb 2017, 20:032 Feb 2017 | 2 Feb 2017, 21:09 | 27,550 ft | no position received |
| TJT037 | route not resolved | 2 Feb 2017, 17:192 Feb 2017 | 2 Feb 2017, 18:03 | 23,425 ft | no position received |
| TJT031 | route not resolved | 2 Feb 2017, 07:392 Feb 2017 | 2 Feb 2017, 08:25 | 23,000 ft | no position received |
| TJT037 | route not resolved | 1 Feb 2017, 19:151 Feb 2017 | 1 Feb 2017, 19:57 | 20,925 ft | no position received |
| TJT031 | route not resolved | 1 Feb 2017, 07:591 Feb 2017 | 1 Feb 2017, 08:45 | 21,000 ft | no position received |
| TJT037 | route not resolved | 31 Jan 2017, 19:1931 Jan 2017 | 31 Jan 2017, 20:04 | 19,725 ft | no position received |
| TJT031 | route not resolved | 31 Jan 2017, 07:4331 Jan 2017 | 31 Jan 2017, 08:31 | 23,000 ft | no position received |
| TJT037 | route not resolved | 30 Jan 2017, 18:4630 Jan 2017 | 30 Jan 2017, 19:33 | 22,000 ft | no position received |
| TJT607B | route not resolved | 20 Jan 2017, 16:5220 Jan 2017 | 20 Jan 2017, 17:20 | 23,000 ft | no position received |
| TJT607A | route not resolved | 19 Jan 2017, 10:3919 Jan 2017 | 19 Jan 2017, 11:23 | 6,050 ft | no position received |
| TJT041P | route not resolved | 19 Jan 2017, 07:2519 Jan 2017 | 19 Jan 2017, 08:04 | 24,000 ft | no position received |
| TJT25HY | LFJL > LFML | 18 Jan 2017, 18:1318 Jan 2017 | 18 Jan 2017, 19:01 | 17,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 18 Jan 2017, 09:0318 Jan 2017 | 18 Jan 2017, 09:56 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 18 Jan 2017, 06:4618 Jan 2017 | 18 Jan 2017, 07:47 | 41,000 ft | no position received |
| TJT26KZ | LFML > LFJL | 17 Jan 2017, 20:1617 Jan 2017 | 17 Jan 2017, 21:05 | 16,000 ft | no position received |
| TJT25HY | LFJL > LFML | 17 Jan 2017, 17:5217 Jan 2017 | 17 Jan 2017, 18:38 | 19,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 17 Jan 2017, 09:0417 Jan 2017 | 17 Jan 2017, 10:03 | 18,000 ft | no position received |
| TJT21HY | route not resolved | 17 Jan 2017, 06:4617 Jan 2017 | 17 Jan 2017, 07:41 | 29,400 ft | no position received |
| TJT26KZ | LFML > LFJL | 16 Jan 2017, 20:5316 Jan 2017 | 16 Jan 2017, 21:30 | 14,000 ft | no position received |
| TJT25HY | LFJL > LFML | 16 Jan 2017, 18:3816 Jan 2017 | 16 Jan 2017, 19:20 | 21,450 ft | no position received |
| TJT73JR | route not resolved | 16 Jan 2017, 11:4416 Jan 2017 | 16 Jan 2017, 11:56 | 23,000 ft | no position received |
| TJT22KZ | LFML > LFJL | 16 Jan 2017, 09:1816 Jan 2017 | 16 Jan 2017, 10:21 | 16,000 ft | no position received |
