Back to the log
Aircraft
F-HMCT
Regular
The station's story
Address not received since 14 Apr 2023. The marker states the absence, it does not say why.
- Cumulative contact time
- 76 h
- Distinct days
- 205
- Highest captured altitude
- 35,025 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #261 of 57,065
- Longest contact
- 0 h 46 min
Same airframe, also seen as
- 9A-LANfrom 20 Sept 2023 to 2 Aug 2026 · 42 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FHMCT | route not resolved | 13 Nov 2016, 19:0413 Nov 2016 | 13 Nov 2016, 19:23 | 24,000 ft | no position received |
| FHMCT | route not resolved | 5 Nov 2016, 11:015 Nov 2016 | 5 Nov 2016, 11:15 | 25,000 ft | no position received |
| FHMCT | route not resolved | 18 Sept 2016, 19:0518 Sept 2016 | 18 Sept 2016, 19:26 | 26,000 ft | no position received |
| FHMCT | route not resolved | 16 Sept 2016, 19:4616 Sept 2016 | 16 Sept 2016, 20:00 | 25,550 ft | no position received |
| FHMCT | route not resolved | 13 Sept 2016, 19:4013 Sept 2016 | 13 Sept 2016, 20:00 | 26,000 ft | no position received |
| FHMCT | route not resolved | 9 Sept 2016, 20:179 Sept 2016 | 9 Sept 2016, 20:33 | 76,100 ft | no position received |
| FHMCT | route not resolved | 9 Sept 2016, 10:489 Sept 2016 | 9 Sept 2016, 11:10 | 26,000 ft | no position received |
| FHMCT | route not resolved | 9 Sept 2016, 08:279 Sept 2016 | 9 Sept 2016, 08:43 | 25,000 ft | no position received |
| FHMCT | route not resolved | 2 Sept 2016, 21:042 Sept 2016 | 2 Sept 2016, 21:15 | 26,000 ft | no position received |
| FHMCT | route not resolved | 2 Sept 2016, 18:492 Sept 2016 | 2 Sept 2016, 19:04 | 25,000 ft | no position received |
| FHMCT | route not resolved | 30 Aug 2016, 20:2930 Aug 2016 | 30 Aug 2016, 20:43 | 24,000 ft | no position received |
| FHMCT | route not resolved | 30 Aug 2016, 17:1930 Aug 2016 | 30 Aug 2016, 17:30 | 22,275 ft | no position received |
| FHMCT | route not resolved | 28 Aug 2016, 18:5628 Aug 2016 | 28 Aug 2016, 19:16 | 24,000 ft | no position received |
| FHMCT | route not resolved | 26 Aug 2016, 19:3126 Aug 2016 | 26 Aug 2016, 19:44 | 24,475 ft | no position received |
| FHMCT | route not resolved | 23 Aug 2016, 19:0723 Aug 2016 | 23 Aug 2016, 19:21 | 24,000 ft | no position received |
| FHMCT | route not resolved | 16 Aug 2016, 21:2216 Aug 2016 | 16 Aug 2016, 21:39 | 26,000 ft | no position received |
| FHMCT | route not resolved | 16 Aug 2016, 17:3916 Aug 2016 | 16 Aug 2016, 17:58 | 21,875 ft | no position received |
| FHMCT | route not resolved | 30 Jul 2016, 13:5430 Jul 2016 | 30 Jul 2016, 14:07 | 26,000 ft | no position received |
| FHMCT | route not resolved | 30 Jul 2016, 10:4930 Jul 2016 | 30 Jul 2016, 10:56 | 27,000 ft | no position received |
| FHMCT | route not resolved | 26 Jul 2016, 20:5026 Jul 2016 | 26 Jul 2016, 21:02 | 26,000 ft | no position received |
| FHMCT | route not resolved | 26 Jul 2016, 16:4026 Jul 2016 | 26 Jul 2016, 16:56 | 22,825 ft | no position received |
| FHMCT | route not resolved | 24 Jul 2016, 18:2224 Jul 2016 | 24 Jul 2016, 18:40 | 26,000 ft | no position received |
| FHMCT | route not resolved | 22 Jul 2016, 19:3522 Jul 2016 | 22 Jul 2016, 19:53 | 23,475 ft | no position received |
| FHMCT | route not resolved | 22 Jul 2016, 11:0322 Jul 2016 | 22 Jul 2016, 11:22 | 26,000 ft | no position received |
| FHMCT | route not resolved | 21 Jul 2016, 19:4321 Jul 2016 | 21 Jul 2016, 20:06 | 27,000 ft | no position received |
