Hi,
After more than 3h flying, just before to descent, I noticed there was something unusual with Simfly Live data …
the system was like i didn’t take off yet, 0NM done, 1900 remaining.
Alt at 0, and about taxiing speed …
I tied to restart Simfly Client (1.3.1), and then went back to the broswer to find this message :
Seems like the client froze at the departure and stopped to get/sent the data.
I assume that LIVE DATA window was receiving and showing data after take off. It happened once to me, but as I have the habit of having client window up in a second monitor, I got the anomaly right away and didn’t close and reopen the client, I just clicked on the icon beneath “broadcasting” and reconnected. but the important thing is to monitor frequently the client, especially after take off.. I assume that also your position on the map didn’t change. didn’t you check your position on the map if it was moving?
Hi … @Karim-CTO-SimFly
Same problem again today …
active mission was saying “0.00NM, 53 minutes …”
So i tried to click on the circular red arrow below “broadcasting” … then flight was aborted.
I lost 4PAX for the touch & win . How can we deal with that ?
Hi Benoit0211,
We are currently investigating this situation, and it seems to be an isolated case on your side.
I will update you as soon as possible. If it happens again in the meantime, please send me the client log.
Thank you, and I’ll let you know as soon as I have more information.
thank you @Karim-CTO-SimFly
As I made a support ticket formally BTW, I replied to “info@simfly.io” with the logs attached
for today case : (time in GMT+2)
2026-06-09T19:02:09.134Z [INF] [FS2024] [FS2024] Could not extract ICAO from livery ‘FenixA320 CFM WF’, leaving ICAO blank
2026-06-09T19:02:12.423Z [INF] [FS2024] [FS2024] connection state changed Closed
2026-06-09T19:02:12.423Z [INF] [connection] [connection] Broadcasting → Disconnected
2026-06-09T19:02:17.477Z [INF] [FS2024] [FS2024] Simconnect interface opened
2026-06-09T19:02:17.477Z [INF] [FS2024] [FS2024] connection state changed Opened
2026-06-09T19:02:17.478Z [INF] [connection] [connection] Disconnected → Broadcasting
2026-06-09T19:02:18.177Z [INF] [FS2024] [FS2024] Could not extract ICAO from livery ‘FenixA320 CFM WF’, leaving ICAO blank
2026-06-09T20:21:24.500Z [INF] [Prepare3d] [Prepare3d] connection state changed Closed
2026-06-09T20:21:24.501Z [INF] [connection] [connection] Broadcasting → Disconnected
2026-06-09T20:21:24.557Z [INF] [FS2020] [FS2020] connection state changed Closed
2026-06-09T20:21:24.620Z [INF] [FS2024] [FS2024] connection state changed Closed
2026-06-09T20:21:24.792Z [INF] [XPlane] [XPlane] connection state changed Closed
2026-06-09T20:21:24.795Z [INF] [XPlane] [XPlane] Stoping server
2026-06-09T20:21:24.797Z [INF] [websocket] [websocket] Stoping server
2026-06-09T20:21:24.797Z [INF] [api] [api] active api key cleared
2026-06-09T20:21:29.660Z [INF] [XPlane] [XPlane] Binding to : 31001
2026-06-09T20:21:29.695Z [INF] [FS2024] [FS2024] Simconnect interface opened
2026-06-09T20:21:29.695Z [INF] [FS2024] [FS2024] connection state changed Opened
2026-06-09T20:21:29.695Z [INF] [connection] [connection] Disconnected → ConnectedToSim
2026-06-09T20:21:30.678Z [INF] [FS2024] [FS2024] Could not extract ICAO from livery ‘FenixA320 CFM WF’, leaving ICAO blank
2026-06-09T20:21:31.412Z [INF] [websocket] [websocket] Binding to : http://localhost:32500/
2026-06-09T20:21:31.516Z [INF] [api] [api] active api key prefix = 4091…
2026-06-09T20:21:31.663Z [INF] [connection] [connection] ConnectedToSim → Broadcasting
2026-06-09T20:21:31.695Z [INF] [FS2024] [FS2024] connection state changed Closed
2026-06-09T20:21:31.695Z [INF] [connection] [connection] Broadcasting → Disconnected
2026-06-09T20:21:36.752Z [INF] [FS2024] [FS2024] Simconnect interface opened
2026-06-09T20:21:36.752Z [INF] [FS2024] [FS2024] connection state changed Opened
2026-06-09T20:21:36.753Z [INF] [connection] [connection] Disconnected → Broadcasting
2026-06-09T20:21:37.658Z [INF] [FS2024] [FS2024] Could not extract ICAO from livery ‘FenixA320 CFM WF’, leaving ICAO blank
These are the two flights where you received that penalty from the tutor.
As you can see from the “Log Penalty” and by clicking on the mini-map “Click to view details”, the client received those data directly from your flight simulator.
The movement detected appears to be anomalous, as if the aircraft was moved instantly, for example by opening the simulator menu or through a sudden repositioning.
I wanted to give you this additional information so you can also check on your side when it happens and verify if you have anything installed that could potentially create a conflict.
In the meantime, we are still carefully investigating the whole situation.
https://simfly.io/missions/log/019e9e2c-cecf-7827-b1e6-88461c8fec26
https://simfly.io/missions/log/019ead6d-1840-70a6-be54-f28f55035bcb
Perfect, thank you. This is very useful.
I’ll update you as soon as I have more news.
AS I said, it was like the client freeze around the time of my take off, or whatever happened, so it stopped to sent my position, for 3h last time, 50 minutes today … but during that time, I flew.
So When I refreshed the client, last time by closing it and reopening, this time by using the red ciruclar arrows button, the system thought I traveled 1000NM in a second …
but if you look time used, and where the flight ended, it’s clear .
on 06/06 : 3h flight from LPSJ to EDDC, (noticed when start to descend …)
today, 50min SVMC to KFLL :
From me, everything was done correctly, started the flight in simfly correctly without error message before staring the engines, then taxing, take off.. flying …
the only mistake is that I didn’t found out the issue earlier like at beginning of the flight
And whatever, for today i was screwed for the 4 Pax fee of the T&W… 
Ok, now we have more information about this. Again, it seems to be an isolated case, and I’m not saying that you are doing anything wrong. I’ll update you as soon as I have more details, including regarding the PAX spent on the T&W event
This topic was automatically closed after 30 days. New replies are no longer allowed.
