Back to the log
Aircraft
100
Common
- Mode S hex
- 3AABFF
- Manufacturer
- Socata
- Serial number
- 100
- Year built
- 199531 years old
- Country of registration
France- First contact
- 12 Apr 2016, 17:50
- Last contact
- 25 Sept 2026, 17:52
- Logged visits
- 438
The station's story
- Cumulative contact time
- 139 h
- Distinct days
- 289
- Highest captured altitude
- 33,975 ft
- Discovery rank
- #5,732 of 60,209
- Longest contact
- 1 h 3 min
- Contacts on this Mode S address
- 453 contacts on the address, 438 under this registration: the address has carried several identities over time.
Observed callsigns
FMY (413 contacts, 2016-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 |
|---|---|---|---|---|---|
| FMY8038 | route not resolved | 28 Feb 2017, 17:0828 Feb 2017 | 28 Feb 2017, 17:31 | 24,800 ft | no position received |
| FMY8038 | route not resolved | 28 Feb 2017, 13:5328 Feb 2017 | 28 Feb 2017, 14:01 | 25,000 ft | no position received |
| FMY8038 | route not resolved | 21 Feb 2017, 13:4821 Feb 2017 | 21 Feb 2017, 14:08 | 18,000 ft | no position received |
| FMY8038 | route not resolved | 21 Feb 2017, 11:3421 Feb 2017 | 21 Feb 2017, 11:48 | 4,725 ft | no position received |
| FMY8038 | route not resolved | 20 Feb 2017, 14:0720 Feb 2017 | 20 Feb 2017, 14:26 | 18,000 ft | no position received |
| FMY8038 | route not resolved | 20 Feb 2017, 11:2420 Feb 2017 | 20 Feb 2017, 11:42 | 4,700 ft | no position received |
| FMY8054 | route not resolved | 8 Feb 2017, 17:448 Feb 2017 | 8 Feb 2017, 18:16 | 28,000 ft | no position received |
| FMY8054 | route not resolved | 8 Feb 2017, 10:138 Feb 2017 | 8 Feb 2017, 10:25 | 22,975 ft | no position received |
| FMY8046 | route not resolved | 2 Feb 2017, 19:142 Feb 2017 | 2 Feb 2017, 19:16 | 24,000 ft | no position received |
| FMY8046 | route not resolved | 30 Jan 2017, 17:0930 Jan 2017 | 30 Jan 2017, 17:20 | 25,000 ft | no position received |
| FMY8046 | route not resolved | 30 Jan 2017, 14:0730 Jan 2017 | 30 Jan 2017, 14:15 | 18,000 ft | no position received |
| FMY8046 | route not resolved | 30 Jan 2017, 12:1430 Jan 2017 | 30 Jan 2017, 12:24 | 15,650 ft | no position received |
| FMY8034 | route not resolved | 25 Jan 2017, 15:2425 Jan 2017 | 25 Jan 2017, 15:43 | 22,000 ft | no position received |
| FMY8039 | route not resolved | 25 Jan 2017, 13:3325 Jan 2017 | 25 Jan 2017, 13:55 | 23,250 ft | no position received |
| FMY8036 | route not resolved | 14 Dec 2016, 17:5614 Dec 2016 | 14 Dec 2016, 18:31 | 28,000 ft | no position received |
| FMY8036 | route not resolved | 14 Dec 2016, 15:3714 Dec 2016 | 14 Dec 2016, 15:56 | 25,000 ft | no position received |
| FMY8034 | route not resolved | 7 Dec 2016, 16:567 Dec 2016 | 7 Dec 2016, 17:10 | 18,000 ft | no position received |
| FMY8034 | route not resolved | 7 Dec 2016, 08:507 Dec 2016 | 7 Dec 2016, 08:56 | 11,250 ft | no position received |
| FMY8049 | route not resolved | 23 Nov 2016, 15:2823 Nov 2016 | 23 Nov 2016, 15:59 | 28,000 ft | no position received |
| FMY8036 | route not resolved | 23 Nov 2016, 10:5523 Nov 2016 | 23 Nov 2016, 11:11 | 16,050 ft | no position received |
| FMY8036 | route not resolved | 22 Nov 2016, 18:1822 Nov 2016 | 22 Nov 2016, 18:34 | 22,000 ft | no position received |
| FMY8043 | route not resolved | 21 Nov 2016, 13:5521 Nov 2016 | 21 Nov 2016, 14:25 | 28,000 ft | no position received |
| FMY8034 | route not resolved | 21 Nov 2016, 09:4821 Nov 2016 | 21 Nov 2016, 10:18 | 12,850 ft | no position received |
| FMY8054 | route not resolved | 16 Nov 2016, 10:1216 Nov 2016 | 16 Nov 2016, 10:48 | 26,000 ft | no position received |
| FMY8054 | route not resolved | 15 Nov 2016, 11:0015 Nov 2016 | 15 Nov 2016, 11:15 | 25,000 ft | no position received |
