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,441
- 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 | 20 Jul 2017, 20:0620 Jul 2017 | 20 Jul 2017, 20:21 | 25,000 ft | no position received |
| FHMCT | route not resolved | 16 Jul 2017, 19:1016 Jul 2017 | 16 Jul 2017, 19:29 | 24,000 ft | no position received |
| FHMCT | route not resolved | 9 Jul 2017, 19:599 Jul 2017 | 9 Jul 2017, 20:13 | 25,000 ft | no position received |
| FHMCT | route not resolved | 11 Jun 2017, 18:5311 Jun 2017 | 11 Jun 2017, 19:15 | 26,000 ft | no position received |
| FHMCT | route not resolved | 3 Jun 2017, 10:363 Jun 2017 | 3 Jun 2017, 10:52 | 25,000 ft | no position received |
| FHMCT | route not resolved | 8 May 2017, 19:298 May 2017 | 8 May 2017, 19:46 | 18,000 ft | no position received |
| FHMCT | route not resolved | 29 Apr 2017, 10:3229 Apr 2017 | 29 Apr 2017, 10:48 | 25,000 ft | no position received |
| FHMCT | route not resolved | 9 Apr 2017, 13:159 Apr 2017 | 9 Apr 2017, 13:37 | 18,000 ft | no position received |
| FHMCT | route not resolved | 9 Apr 2017, 11:579 Apr 2017 | 9 Apr 2017, 12:18 | 3,625 ft | no position received |
| FHMCT | route not resolved | 1 Apr 2017, 12:241 Apr 2017 | 1 Apr 2017, 12:48 | 24,000 ft | no position received |
| FHMCT | route not resolved | 1 Apr 2017, 11:001 Apr 2017 | 1 Apr 2017, 11:31 | 4,200 ft | no position received |
| FHMCT | route not resolved | 28 Mar 2017, 21:2228 Mar 2017 | 28 Mar 2017, 21:34 | 26,000 ft | no position received |
| FHMCT | route not resolved | 24 Mar 2017, 19:1124 Mar 2017 | 24 Mar 2017, 19:22 | 21,575 ft | no position received |
| FHMCT | route not resolved | 12 Mar 2017, 18:1112 Mar 2017 | 12 Mar 2017, 18:32 | 26,000 ft | no position received |
| FHMCT | route not resolved | 4 Mar 2017, 10:274 Mar 2017 | 4 Mar 2017, 10:42 | 25,000 ft | no position received |
| FHMCT | route not resolved | 12 Feb 2017, 13:3512 Feb 2017 | 12 Feb 2017, 14:03 | 24,000 ft | no position received |
| FHMCT | route not resolved | 12 Feb 2017, 11:5212 Feb 2017 | 12 Feb 2017, 12:27 | 3,175 ft | no position received |
| FHMCT | route not resolved | 4 Feb 2017, 11:494 Feb 2017 | 4 Feb 2017, 12:26 | 19,000 ft | no position received |
| FHMCT | route not resolved | 4 Feb 2017, 10:364 Feb 2017 | 4 Feb 2017, 10:54 | 4,700 ft | no position received |
| FHMCT | route not resolved | 8 Jan 2017, 15:058 Jan 2017 | 8 Jan 2017, 15:28 | 19,000 ft | no position received |
| FHMCT | route not resolved | 8 Jan 2017, 13:368 Jan 2017 | 8 Jan 2017, 14:23 | 4,225 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2016, 14:0727 Dec 2016 | 27 Dec 2016, 14:41 | 18,000 ft | no position received |
| FHMCT | route not resolved | 27 Dec 2016, 12:4427 Dec 2016 | 27 Dec 2016, 13:18 | 3,575 ft | no position received |
| FHMCT | route not resolved | 6 Dec 2016, 20:326 Dec 2016 | 6 Dec 2016, 20:43 | 22,000 ft | no position received |
| FHMCT | route not resolved | 2 Dec 2016, 19:292 Dec 2016 | 2 Dec 2016, 19:46 | 24,800 ft | no position received |
