Your suggestion would require a motion-device/macro/program apart from the polygon definition. The stearing could eather be done by some kind of joystick or by external data (such as a networklink). Either way recalculation will have to be done. Now its done external trough a network link.

The kmz for 3D plane movement, i made, works just fine, for now. Speed and frequency depend on data delivered by others on a once every 15 seconds level. So the model rather jumps than moves. Still I consider a 3D image in some instances better than icons and images.
I wonder if you had a look at the 3D model yet.

Lets get the heads (and planes) up a bit earlier.
try out a single plane, using Airforce One

Something I'ld like (for my pilotsview) is a <LookFrom> tag rather than the <LookAt> tag for situations where the coordinates of the point of view are known, but those of the point one is looking at are unknown.