I’m using SimFly client alongside another tracker (FsHub/LRM) and I’ve noticed some regular differences in the landing rate displayed for the same flights.
Out of curiosity, what method does SimFly.io use to calculate the landing rate? Is it an instantaneous value at the moment of touchdown, an average over a short time window, or something else? I was also wondering which X-Plane dataref is used, as some return an instantaneous value while others return a smoothed one — which could explain discrepancies between tools.
The reason I’m asking is that the landing rate has a direct impact on PAX gains, so understanding how it’s calculated would help me better interpret my results and know which value to trust.
in my case, I don’t focus much on the differences between the many clients I have on. I rather see if other pilots lands the same airplane in similar runways the way I do. Within simfly. I check if the wind measured is also the same in the logs.
Anyway I see that the internal sim landing rate in MSFS is pretty much close to Simfly, same as Volanta. I don’t know if Xplane has one. I don’t relay much on FSHUB (LRM), OnAir, FSEconomy, or any other landing monitor tool. Also take note that mainly the total score is but will be more relevant in XP and PAX given instead of the landing score. It’s better to worry about on how to “fix” lights , flaps usage during flight instead only in the landing.
but if you are interested on what can cause differences between landing rate read out, take a look at next answer.
Different landing rates in flight simulators (like MSFS 2020/2024, X-Plane) for seemingly similar landings are caused by a combination of software polling inconsistencies, aircraft weight, atmospheric conditions, and the specific methodology of third-party tracking tools.
Here are the primary reasons for these discrepancies:
Landing rate tracking tools do not usually measure the exact instant the tires touch the ground. Instead, they use a polling interval (checking simulation data every few milliseconds).
The Issue: The simulator might register the landing at -100 fpm in one frame, but in the next frame, the plane settles, causing the tracker to record -250 fpm.
Result: A “buttered” landing can often show a higher, firmer, or lower rate depending on when the app takes its data snapshot.
2. Variable Aircraft Weight and Balance
The landing rate is highly dependent on the aircraft’s current weight.
Weight Sensitivity: An aircraft nearing its maximum landing weight requires a firmer touchdown (higher landing rate) to ensure positive ground contact, while a light aircraft can land much more softly.
Momentum: Higher weight means higher momentum, which often results in a higher FPM (feet per minute) reading if the flare is not perfect.
3. Atmospheric Conditions (Wind and Turbulence)
Simulators often introduce variable wind gusts, which make consistent landing rates difficult.
Wind/Gusts: A sudden drop in wind during the flare can cause the aircraft to settle faster, leading to a higher landing rate.
Real-world vs. Sim: While real-world winds are often steady with a directional feel, simulator winds can sometimes feel unnaturally turbulent, causing inconsistency.
4. Approach Speed and Power Settings
Insufficient Power: If power is reduced too early, the aircraft loses too much speed and stalls earlier than expected, causing a “harder” (higher FPM) landing.
Speed Management: Maintaining the correct, consistent approach speed (roughly 5 times your ground speed in FPM) is crucial for a consistent, moderate rate.
5. Third-Party Monitoring Tools Differences
Different Algorithms: Different monitoring tools (e.g., FSUIPC-based tools, Volanta, internal landing checkers) may calculate the touchdown moment or interpret FPM vs. G-force differently.
“Hard Landing” Definition: Different Virtual Airlines (VAs) or tools have different thresholds for what they consider “firm” or “hard”.
6. Runway Slope and Surface
Sloped Runways: If the runway has a significant incline or decline, the vertical speed, when referenced to sea level rather than the surface of the runway, will differ, leading to misleading landing rate readings.
7. Simulation Frame Rate (Sim Rate)
Sim Rate Speed: Using a higher frame multiplier (speeding up the simulation) causes the physics engine to skip frames, which can lead to erratic landing data.
First of all, I want to make it absolutely clear that this is not a criticism at all — SimFly.io is a great platform and I really enjoy flying on it. I’m simply trying to understand how things work so I can improve as a pilot.
I fly on X-Plane 12 and, during my flights, I genuinely feel like my landings are fairly smooth. I work hard on my technique and I’m always trying to get better, so I was a bit puzzled when I noticed higher landing rate values than I expected.
That’s what led me to ask about the calculation method — purely out of curiosity and a desire to understand, not to challenge the system.
I’d also like to mention something that might be relevant: since X-Plane 12.4, I’ve been getting lighting and flaps warnings during my flights that I never had before on version 12.3. I follow checklists very carefully and nothing has changed on my end, so it seems like something may have shifted in how XP12.4 reports certain states. This could potentially affect how some data is captured by the tracker as well — but I’m not sure, hence the question.
Thanks again for your time and for detailled response.
everything could be, even a new release of software, 12.4.0 full release has been available since feb 2026. For what I can see from your logs for example, last flight (Airbus A320-NEO) you only had Flaps penalty and approach speed. Lights were ok. the previous although had taxi lights and flaps, with the same Airbus A320-NEO. So it could depend on how the simconnect client and Xplane send info to simfly client. Not realy sure if it is the new Xplane release, because you encountered the same penalty also on Sep 8, 2025 with the same A320-NEO when I suppose version 12.4 wasn’t available.
but it could really be a sim software (XPLANE) malfunction, because I can see from other users (MSFS2020 and MSFS2024) with the same model they don’t get those penalties. But I also see this Xplane user that had 99 points flying with the same model A320-NEO (can’t be sure of the release if the newest or not , but he gained 99 as you can see here SimFly | Fly and Earn . I don’t fly liners but with the majority of planes I use, don’t really stick to check list, I just found out how not to get penalties with lights. For example. while on parking area, I turn on, all lights except for LANDING and STROBE. then I move and taxi (Flaps ON) to on runway line up. I full stop with parking brake. then I turn OFF TAXI lights and TURN ON Landing and Strobe. run for take off. Above 500ft before arriving to 1000ft, FLAPS OFF and GEAR UP.
when landing, regarding lights, as soon as I full stop on the runway, before making a U turn, I turn OFF landing and Strobe, and turn ON TAXI lights. (obviously also FLAPS UP) then I do my taxi while still on runway before entering taxi way with TAXI lights ON and LANDING and STROBE OFF. to me 99% I get 100 points. (take note that there are some models, GA and Liners that have issue on lights behavior and TRANSPONDER) Transponder though should be fixed with some liners model that had problems.
Still, I’m wondering if the Toliss A320neo isn’t sending the correct data through SimConnect/X-Plane to SimFly sometimes. Even when I’m 100% sure I did everything by the book (flaps, speeds, lights on/off at the right times, transponder, etc.), I randomly get hit with “Flaps” or “Approach speed” penalties with no obvious reason. And like you mentioned, people flying the same type on MSFS don’t seem to have this issue at all, so it really feels like something specific to X-Plane + Toliss + SimFly interaction.
I try to fly it more or less like a real airline pilot would — follow the flows and callouts as best I can, especially in critical phases (takeoff, approach, landing). That said, the points I’m losing right now aren’t too punishing in the overall ranking, so I’m not stressing too much about it yet.
I focus a lot on the landing because it’s the PAX sheath that depends on it at the end. Thank you for all the tips and info. I would turn off the lights and tuck in the flaps when stationary on the track before the taxi-off to see.
well for the approach speed I suppose you can check it “live” when you are landing and see if the IAS is above 200, but can’t remember at which altitude is requested to be below.
During Final Approach (Airline Ops): While the general speed limit below 10,000 feet is 250 knots, standard procedure for many airliners involves decelerating to 200 knots (or less) during the intermediate approach phase, typically around 5,000–8,000 ft, often reaching 180–200 kts around 5 miles from the runway.
ps it says “Airline Ops”, so lets consider Simfly “our” Airline Ops that can require these rules.
