I've noticed that client reading wrong v/s for landing. I've landed very hard yesterday, but client detected only -150 ft/min vertical speed. I use two more programs to log flight data - FSAcars as main pirep program for our VA and Flight Keeper for testing purposes as we plan to switch from FSAcars to FSFK. Both detected -600 ft/min vertical speed, which is more close to true.
konny, ur method is accurate, i that also happens with me, but when u hit so hard, most likely u will bounce up, and the client will recognize only the last "bounce". im thinking his plane might of come back off the ground then came back down at 150 ft/min
i have had a couple hard landing like that, it would bounce back up off the ground, but yet it would say a low ft/min number.
you might only see the last bounce as the landing V/S, but acutally the aircraft damage is a sum of all bounces when landing...I already added this feature some months ago Probably it would be a good idea that at the end you see the avarage V/S and not only the last bounce...
yes, I think the sum is best. Imagine you would use the avarage vs and have a hard landing. you would only have to do some minor bounces in order to decrease the damage...that doesn't make much sense
My last flight landed so hard my co-pilot broke both his legs and the stewardess bounced off the ceiling and soaked my navigator with a Jack and Coke she was bring to me. I guess next time I will turn the seat belt sign on.
it look like flynet client detecting nose (last) wheel touchdown speed - I've landed recently with -19 ft/min vertical speed according Flynet, when Flight Keeper and FSacars has detected 212 ft/min, no bounces.
Kimis, as Claudio (DaKurt) said, they are all detected, only the last is displayed, but the previous "landings" are added up to determine the "wear" on the aircraft for maintenance purposes.
Probably it would be a good idea that at the end you see the avarage V/S and not only the last bounce...
