Back to the log
Aircraft
F-MAYF
Regular
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 23 Jun 2016. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
- Mode S hex
- 3AABD1This aircraft has carried several registrations: the same airframe, re-registered. Directories give it sometimes as 5529, sometimes as F-MAYF; every contact below is its own.
- Manufacturer
- Aerospatiale
- Serial number
- 5529
- Year built
- 199234 years old
- Country of registration
France- First contact
- 23 Jun 2016, 15:11
- Last contact
- 14 Jan 2026, 11:29
- Logged visits
- 18
The station's story
- Cumulative contact time
- 4 h
- Distinct days
- 14
- Highest captured altitude
- 9,325 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #13,933 of 57,390
- Longest contact
- 0 h 32 min
Observed callsigns
FMY (9 contacts, 2016-2025)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 14 Jan 2026, 11:2914 Jan 2026 | 14 Jan 2026, 11:29 | 3,750 ft | no position received |
| FMY8645 | route not resolved | 3 Apr 2025, 11:403 Apr 2025 | 3 Apr 2025, 11:56 | 5,000 ft | no position received |
| FMY8860 | route not resolved | 7 Jul 2021, 11:057 Jul 2021 | 7 Jul 2021, 11:12 | 4,650 ft | no position received |
| FMAYF | route not resolved | 29 Sept 2020, 14:0529 Sept 2020 | 29 Sept 2020, 14:17 | 4,775 ft | no position received |
| FMY8387 | route not resolved | 11 Sept 2020, 11:2411 Sept 2020 | 11 Sept 2020, 11:34 | 2,700 ft | no position received |
| not transmitted | route not resolved | 11 Sept 2020, 10:4211 Sept 2020 | 11 Sept 2020, 10:43 | 1,900 ft | no position received |
| FMAYF | route not resolved | 10 Sept 2020, 10:4010 Sept 2020 | 10 Sept 2020, 10:47 | 3,975 ft | no position received |
| FMAYF | route not resolved | 5 Aug 2020, 10:355 Aug 2020 | 5 Aug 2020, 11:00 | 5,325 ft | no position received |
| FMAYF | route not resolved | 4 Aug 2020, 11:184 Aug 2020 | 4 Aug 2020, 11:23 | 3,675 ft | no position received |
| not transmitted | route not resolved | 13 Aug 2019, 15:1513 Aug 2019 | 13 Aug 2019, 15:20 | 2,050 ft | no position received |
| FMAYF | route not resolved | 1 Aug 2019, 10:371 Aug 2019 | 1 Aug 2019, 10:43 | 3,750 ft | no position received |
| FMY8810 | route not resolved | 16 May 2017, 14:5016 May 2017 | 16 May 2017, 15:13 | 8,875 ft | no position received |
| FMY8810 | route not resolved | 16 May 2017, 10:5516 May 2017 | 16 May 2017, 11:21 | 5,225 ft | no position received |
| FMY8818 | route not resolved | 20 Feb 2017, 15:5020 Feb 2017 | 20 Feb 2017, 16:10 | 7,950 ft | no position received |
| FMY8818 | route not resolved | 20 Feb 2017, 13:0420 Feb 2017 | 20 Feb 2017, 13:37 | 5,050 ft | no position received |
| FMY8830 | route not resolved | 23 Nov 2016, 14:4923 Nov 2016 | 23 Nov 2016, 15:05 | 27,000 ft | no position received |
| FMY8830 | route not resolved | 23 Nov 2016, 11:3923 Nov 2016 | 23 Nov 2016, 12:04 | 3,850 ft | no position received |
| not transmitted | route not resolved | 23 Jun 2016, 15:1123 Jun 2016 | 23 Jun 2016, 15:12 | 8,950 ft | no position received |
Page 1 of 1 · 18 visits