On 6/15/2026 at 10:55 AM, kevinfirth said:

I saw this list of questions in another thread, so thought this would be a great starter for 10...

Is it voice based or button? VoxATC will support both - in fact you can use either input method at any time during a flight.
Will you support both IFR and VFR from launch or only one of those? VoxATC will control both IFR AND VFR traffic regardless of what type of flight you the user is making - (although some advanced aspects of VFR flight are still being actively improved.)
Will you support the entire world or just US? VoxATC covers the entire world and has the capability to use different regionalised standards.
Is it built around simbrief or works independently? VoxATC can work with independent flightplans (.pln) or import simbrief flightplans.
Are you relying on AFCAD data for taxiways or your own solution? VoxATC reads (indexes) all scenery active in your simulator and uses them.
Is some sort of multiplayer planned? Or is it player only? Player only at first, although multiplayer has been discussed in the context of two remote pilots being able to share the same ATC/AI while in shared cockpit. If it comes it will be added later.

What sort of features could we expect from the very first release?

• IFR and VFR support, including:

  • intelligent taxiing so you don't end up face to face with AI aircraft

  • intelligent sequencing on approach

  • holding patterns and stacks at busy airports

  • flight/radar service for VFR

  • easily customisable .xml profiles for airports to specify accurate communications, holding points and VRP's

• integration with the freeware AIG package - providing a huge amount of realistic traffic based on AIG flightplans

• in-sim panel interface - html based so is visually customisable to your liking through CSS

  • interface can also be displayed on a networked device like a tablet, enabling you to use a touch interface

I have been searching for a "thread" you mentioned with the supplied questions but have not yet located it.

Do you have a link to that topic with the VOXatc pre product release questions?

5 hours ago, vonmar said:

I have been searching for a "thread" you mentioned with the supplied questions but have not yet located it.

Do you have a link to that topic with the VOXatc pre product release questions?

It was a thread about a different product. I didn't want to hijack a discussion about someone else's product so started this one.

WOW: @kevinfirth Your "Free Support here" for a product "to come" and your professional way of communicating is something to mention here!
Your support is superior! Thanks for spending so much of your spare time to answer, follow up and also "warn" so kindly and gentle....never seen before.

Let others take your way of work as an Example! I´ll do!

And no.....I am not involved in any way to Kevins work or VOXATC ;-)

Been a long time coming - (and don't criticise my Fenix setup!)

A few mins showing an exceptionally busy EGGP Liverpool and a rw27 departure. Note how VoxATC manages and interleaves the arrivals and departures while handling ground requests at the same time. Watch for the Beluga! That's injected by VoxATC, on its way to Hawarden nearby...

I mentioned the runway selection tool for advanced users before...

Here's an example of it in action! https://ibb.co/4gF2FT0Y

This is a complex set of rules for EHAM Schipol, which we all are aware has a lot of runways used in different ways.

Fly to/from EHAM using only basic logic will often result in ATC instructing you to take-off from or land on an inappropriate or unrealistic runway.

This powerful app allows creation of an unlimited number of rules to minimise problems like this. Some will come with VoxATC already. You can amend the default provided rules, or create your own. Share them with us and we'll distribute them as updates for ALL users..

As you can see from the image, this rule set does the following:

• Allocates normal runways in use for daytime periods with normal northerly or southerly wind directions

• Provide an easterly and westerly crosswind limit for which these runways can still be in use

• Allocates an additional arrivals or departures runway for specified peak operations times

• For exceptional windspeed/direction combinations switches to 09/27 for crosswind restricted operations

• Restricts runways in use during the night

• Restricts runways in use to CAT II-III equipped in low visibility conditions

• Restricts light jets/props to 04/22, during daytime normal visibility ops

Does anyone have a preferred airport with some really tough approach or departure restrictions you'd like me to demo?

Here's a short video of EHAM with live weather, and VoxATC reading the runways in use in the ATIS, based on the rules above: https://youtu.be/SWh5AKQ5I9M

The live METAR in use is EHAM 220955Z 06010KT 360V120 9999 FEW036 22/16 Q1027 NOSIG

VoxATC correctly allocates runways in use based on current time (day/off peak) and wind speed/direction (northerly, light wind) to arrivals on 06 and departures from 36C 😁

Edited Monday at 10:37 AM3 days by kevinfirth

Hi Kevin,

The advanced tool looks great! Nice job on EHAM. There's probably some additional EHAM configs to add as I notice 36C is not listed for arrivals but in real rwy ops that can happen.I will try and find the info when that rwy is used.

Some questions came to mind about how I would use the tool..

A question... can the table accept dates at all? Reason for asking is when runways are out of commission due to maintenance, I wonder if the table can be programmed to avoid certain runways on certain days (range of days)?? Of course, user can enter that exception on that specific day in the list and then revert the list back afterwards but wonder if that came up in discussions? I assume to prevent a runway from being used at all, its a question of clicking the "-" sign in the selected runways column and selecting that specific rwy for removal? I also assume the times are UTC, not local in the list?? (Note: from this Sep through end of Oct, EHAM will be doing maintenance on 4 of their runways and each time a runway will be shut for at least 1 week period).


Also for other rwy ops, the other thing may be to consider incorporating is not just aircraft class but true aircraft type.
I am thinking about Frankfurt Main ops and the northwest runway (25R/07L) that prevents specific aircraft types from using this specific runway e.g. 74x, MD-11, A380. I believe this is based primarily on the ICAO aircraft category code i.e. Cat F aircraft are the exception. I mention this because back when I was using P3D, I was also using a user-developed app named ATCAPI if you remember that one (?) that allowed you to configure AI runway usage based on aircraft types. This would be a nice to have feature- not a must.

And when multiple rwys are in operation (lets say at EHAM with 1 DEP, and 2 ARR rwys) how does the app/tool schedule the appropriate weighting of aircraft between them? Is this pre-programmed to a given percentage or could this also be user controlled.

Anyway, I am glad that this type of customisation by users will be possible. Loving the info flow on this forthcoming app! 👍

18 minutes ago, 787flyer said:

There's probably some additional EHAM configs to add as I notice 36C is not listed for arrivals but in real rwy ops that can happen.I will try and find the info when that rwy is used.

So I did a little bit of digging and from what I was able to find out, on April 18 2026 at EHAM the following rwy ops combination was in operation, I assume to some northwesterly winds.

Landing: 36C, 27

Takeoff: 36L

This info courtesy of the Dutch Plane Spotters website: https://www.dutchplanespotters.nl/

Note 36C can alternate very quickly between landings and take-offs based on winds and peak operating periods

27 minutes ago, 787flyer said:

Hi Kevin,

The advanced tool looks great! Nice job on EHAM. There's probably some additional EHAM configs to add as I notice 36C is not listed for arrivals but in real rwy ops that can happen.I will try and find the info when that rwy is used.

Some questions came to mind about how I would use the tool..

A question... can the table accept dates at all? Reason for asking is when runways are out of commission due to maintenance, I wonder if the table can be programmed to avoid certain runways on certain days (range of days)?? Of course, user can enter that exception on that specific day in the list and then revert the list back afterwards but wonder if that came up in discussions? I assume to prevent a runway from being used at all, its a question of clicking the "-" sign in the selected runways column and selecting that specific rwy for removal? I also assume the times are UTC, not local in the list?? (Note: from this Sep through end of Oct, EHAM will be doing maintenance on 4 of their runways and each time a runway will be shut for at least 1 week period).


Also for other rwy ops, the other thing may be to consider incorporating is not just aircraft class but true aircraft type.
I am thinking about Frankfurt Main ops and the northwest runway (25R/07L) that prevents specific aircraft types from using this specific runway e.g. 74x, MD-11, A380. I believe this is based primarily on the ICAO aircraft category code i.e. Cat F aircraft are the exception. I mention this because back when I was using P3D, I was also using a user-developed app named ATCAPI if you remember that one (?) that allowed you to configure AI runway usage based on aircraft types. This would be a nice to have feature- not a must.

And when multiple rwys are in operation (lets say at EHAM with 1 DEP, and 2 ARR rwys) how does the app/tool schedule the appropriate weighting of aircraft between them? Is this pre-programmed to a given percentage or could this also be user controlled.

Anyway, I am glad that this type of customisation by users will be possible. Loving the info flow on this forthcoming app! 👍

There will always be some additional edge cases that can be added. This was something I knocked up in a couple of hours research so I am not trying to say in any way that it covers every possible eventuality! But, it does cover some of the major ones and demonstrates how capable VoxATC can be.

The rules don't as yet accept dates. I've already suggested that days of the week should be added, because as I was creating this it was apparent that the additional arrival and departure runways are only available on the weekday peak times, for example.

The tool is fairly self explanatory - just a couple of programming bugs to be worked out - so yes, "+" and "-" signs add and delete runways.

Maintenance plans for runways aren't supported at this point.

Aircraft type is already covered, allowable selections include superheavy, heavy, medium, and light jets, medium and light props. I used those to restrict 04/22 useage to those aircraft types.

Not entirely confident I could answer the algorithmic question on multiple runway use. I'll come back to you on that. I think it's going to heavily depend on what AI is approaching from where and how it gets sequenced by VoxATC. That's some of the hardest part of creating an ATC app and I'll be honest, in that I cannot explain that to you easily here. 😆

You can of course take any airport profile and customise it to your specific needs at any point. It would be just a file switch and backup.

13 minutes ago, 787flyer said:

So I did a little bit of digging and from what I was able to find out, on April 18 2026 at EHAM the following rwy ops combination was in operation, I assume to some northwesterly winds.

Landing: 36C, 27

Takeoff: 36L

This info courtesy of the Dutch Plane Spotters website: https://www.dutchplanespotters.nl/

Note 36C can alternate very quickly between landings and take-offs based on winds and peak operating periods

Do you by any chance know what the metar was at that time please? That historic data is only available for paid subscriptions :-(

With some reference data it would be possible to more closely calculate the crosswind limits and fine-tune rules to get closer to them.

Edited Monday at 03:03 PM3 days by kevinfirth

It's worth noting that this profile I did for EHAM is NOT intended to be a 100% faithful reconstruction of real world ops. It is intended to demonstrate the kind of capacity VoxATC will have and develop further.

It is possible to get a lot closer to real world ops, but that will inevitably involve getting more data, and setting up and testing much more finely tuned rules based on real world crosswind limits for individual aircraft types. This demo was never intended to go that deep, it would require a lot more research time and effort than I had available this morning I'm afraid!

Factoid To do this is I asked Claude to compile a database of runways and useage patterns based on published rules and available actual data. It did a pretty good job, but on the first pass Claude got confused between departures and arrivals and started mixing runways up 🙄 It actually produced a look up table for windspeed/direction. But, while AI is great at a lot of things, its results needed fine tuning and checking!

Omg my body and wallet is ready! Looks amazing.

2 hours ago, 787flyer said:

And when multiple rwys are in operation (lets say at EHAM with 1 DEP, and 2 ARR rwys) how does the app/tool schedule the appropriate weighting of aircraft between them? Is this pre-programmed to a given percentage or could this also be user controlled.

1. As the traffic is generated it is assigned to the runway that satisfies the selection criteria and has the least traffic ahead.

2. Same happens when the user arrives / departs

1 hour ago, kevinfirth said:

Do you by any chance know what the metar was at that time please? That historic data is only available for paid subscriptions :-(

With some reference data it would be possible to more closely calculate the crosswind

Found this info for that date/time if it helps. As suspected NW winds.


: 18:25 (6:25 PM) Local Time:
METAR EHAM 181625Z 28007KT 250V310 CAVOK 26/16 Q1016 NOSIG

1. 18:55 (6:55 PM) Local Time:
   METAR EHAM 181655Z 31007KT 290V010 CAVOK 26/16 Q1016 TEMPO -SHRA FEW070CB [1]

On 6/19/2026 at 11:17 AM, mpo910 said:

WOW: @kevinfirth Your "Free Support here" for a product "to come" and your professional way of communicating is something to mention here!
Your support is superior! Thanks for spending so much of your spare time to answer, follow up and also "warn" so kindly and gentle....never seen before.

Thank you for your feedback. It's always motivating to know that I'm not communicating to a dark void! 😁

5 minutes ago, 787flyer said:

Found this info for that date/time if it helps. As suspected NW winds.
: 18:25 (6:25 PM) Local Time:
METAR EHAM 181625Z 28007KT 250V310 CAVOK 26/16 Q1016 NOSIG

1. 18:55 (6:55 PM) Local Time:
   METAR EHAM 181655Z 31007KT 290V010 CAVOK 26/16 Q1016 TEMPO -SHRA FEW070CB [1]

Interesting - those conditions are relatively calm, bit of fluctuating wind direction, good visibility, but nothing that would significantly affect flight operations at 7kts? My Claude research on which that ruleset is based included this....so its not surprising vox didnt include rw27. Wonder if there was some special case that the controllers used 27 for? Do we have any data on what/how many a/c landed using 27?

Strong crosswind (>15kt component) from SW/NW

09/27 brought into use