Not sure about FSX but in P3D where I am usually, th4e Avidyne is giving bogous ETE values as seen in the picture

 

 

and here is another error in the opposite time vector

 

 

 

 

At 200 knots, it does not take 2+ hours to cover 152 NMs

 

al

Yep that's right, here in FSX it do have the same issue...but is so strange because in some waypoints the ETE times are correct and match to the times given in the Garmin GNS...that's quite more strange, it should be a global issue with all the Avidyne and not just in some waypoints!, at least, that's what I've noticed after 74 hours of flying it and with a long range flight of 1,575.00 nm!, they should fix it in the upcoming SP1...(I hope so...there are tons of issues that needs to be fixed!!!!)