VATUSA 24 hour time lapse (6/16/2017)

[Daniel Hawton]

Ever wonder what 24 hours of flights in VATUSA looks like?  I did.

Using data collected by AirStats, I applied some math and created a time lapse of VATSIM traffic from 6/16/2017 0000Z until 6/16/2017 2359Z (6/15 8:00pm US Eastern - 6/16 7:59pm US Eastern).  See 24 hours of traffic in 3 minutes.  It involved 2038 flights and 129,700 position reports (and about double that of mathematically calculated estimated positions).

Only flights that had flight plans, were on the within 500 feet AGL and 3nm of the departure and arrival airports for those phases and remained connected to VATSIM the entire time were logged.  Only aircraft with a speed of 30 knots or more are shown.  Position reports are speed based, <100 knots, every 10 minutes, 100-250 knots every 5 minutes, 250+ knots every 2 minutes.  Positions are calculated for every minute.

VATUSA Timelapse: https://youtu.be/H_VJMFyBNvA  Data obtained from: https://www.airstats.net

Hope you enjoy it.

[Toby Rice]

Very cool!

[Don Desfosse]

Very cool, thanks for doing it and for sharing it!

[Meg Bruck]

Nice!

[Camden Bruno]

Awesome!

[Jonathan Voss]

Nice. Too bad you didn't let it run another 4 hours and catch the entire Fort Houston Live event!

[Josh Glottmann]

Awesome!

[Daniel Hawton]

Nice. Too bad you didn't let it run another 4 hours and catch the entire Fort Houston Live event!

I do take requests airstats is logging data 24x7x365 and I wrote it to be useful for any time period.

[Evan Reiter]

Yes, very cool!

If you decide to do one again, it might be interesting to include a clock showing the Zulu (or ET) time throughout the video. To the extent practical, showing which controllers are online would also be kind of interesting.

Pairing this with some of the major events we run (e.g., Cross The Pond) would be really neat, too.

[Daniel Hawton]

Yes, very cool!

If you decide to do one again, it might be interesting to include a clock showing the Zulu (or ET) time throughout the video. To the extent practical, showing which controllers are online would also be kind of interesting.

Pairing this with some of the major events we run (e.g., Cross The Pond) would be really neat, too.

I thought about that including ATC, but I don't track ATC due to the number of boundaries I would have to collect to make it usable and that they are constantly changing.  It's a significant investment of time that I don't really have. The clock has been added, the VATUSA and VATSIM time lapse videos were proof of concepts mostly, the next will have a clock

[Josh Glottmann]

Do you need the request beforehand?

[Daniel Hawton]

Nope.  It would be great to have it within 24 hours of the event, if after, or earlier than as after the flight has been logged for 24 hours the positions are archived to AWS... it makes data retrieval in bulk a little more difficult but not impossible.

[Matthew Kosmoski]

Nice. Too bad you didn't let it run another 4 hours and catch the entire Fort Houston Live event!

I do take requests airstats is logging data 24x7x365 and I wrote it to be useful for any time period.

We'd love it if you could do a timelapse of the ZHU/ZFW Live event +/- a few hours!

[Daniel Hawton]

Nice. Too bad you didn't let it run another 4 hours and catch the entire Fort Houston Live event!

I do take requests airstats is logging data 24x7x365 and I wrote it to be useful for any time period.

We'd love it if you could do a timelapse of the ZHU/ZFW Live event +/- a few hours!

It will be published tonight.

Sneak peak:

[Jonathan Voss]

Nice. Too bad you didn't let it run another 4 hours and catch the entire Fort Houston Live event!

I do take requests airstats is logging data 24x7x365 and I wrote it to be useful for any time period.

We'd love it if you could do a timelapse of the ZHU/ZFW Live event +/- a few hours!

It will be published tonight.

Sneak peak:

Much appreciated, thanks Daniel! I'm looking forward to the results.