JordanGrant
Well Known Member
All,
I am beginning work on a research project enroute to a Masters Degree from Air University (i.e. the US Air Force). It is very much aviation related, so I thought I would solicit input from the RV community here (since its easy and I read the boards all the time). Here is my draft research question:
"What is the best way to deconflict military aircraft performing low-level training, both from each other and from civilian aircraft?"
My research is going to focus on two areas:
1. What would a centralized low-level scheduling system look like and how can it integrate with other users of the National Airspace System?
2. If a sufficiently advanced system were used, would we still need Military Training Routes?
For the first question, I want to explore ways we can integrate general aviation SA-building systems with the military scheduling system. For example, the moving-map displays that many of us have are beginning to use datalinks to include weather, TFRs, and traffic. Could the same datalinks be used to overlay information about scheduled low-altitude military training? (i.e. indicate to pilots when to look out for high-speed military airplanes in their area)
Even if you couldn't get real-time updates from datalinks, would general aviation (i.e. you guys) use a web-based system to check for scheduled traffic in your flying area? What would it take to integrate with other commonly used tools like Weathermeister? (Dan, are you reading?)
For the second question, I want to make the argument that MTRs are no longer needed if you have a computer-based system. Presumably, the reason MTRs were established many years ago were to facilitate scheduling and deconfliction by limiting high-speed, low-altitude flight to certain corridors. If the computer can deconflict flights automatically, as well as inform the general flying public as to where the flights will take place, there is no reason to limit flights to those corridors anymore. Instead, a database can be built with no-fly areas and other restrictions, and military guys can build their routes around them. The result would be increased training effectiveness, enhanced safety, and minimized noise complaints by avoiding overflights of the same areas all the time.
If anyone has any thoughts, inputs, or especially good research sources, I would greatly appreciate your help!
I am beginning work on a research project enroute to a Masters Degree from Air University (i.e. the US Air Force). It is very much aviation related, so I thought I would solicit input from the RV community here (since its easy and I read the boards all the time). Here is my draft research question:
"What is the best way to deconflict military aircraft performing low-level training, both from each other and from civilian aircraft?"
My research is going to focus on two areas:
1. What would a centralized low-level scheduling system look like and how can it integrate with other users of the National Airspace System?
2. If a sufficiently advanced system were used, would we still need Military Training Routes?
For the first question, I want to explore ways we can integrate general aviation SA-building systems with the military scheduling system. For example, the moving-map displays that many of us have are beginning to use datalinks to include weather, TFRs, and traffic. Could the same datalinks be used to overlay information about scheduled low-altitude military training? (i.e. indicate to pilots when to look out for high-speed military airplanes in their area)
Even if you couldn't get real-time updates from datalinks, would general aviation (i.e. you guys) use a web-based system to check for scheduled traffic in your flying area? What would it take to integrate with other commonly used tools like Weathermeister? (Dan, are you reading?)
For the second question, I want to make the argument that MTRs are no longer needed if you have a computer-based system. Presumably, the reason MTRs were established many years ago were to facilitate scheduling and deconfliction by limiting high-speed, low-altitude flight to certain corridors. If the computer can deconflict flights automatically, as well as inform the general flying public as to where the flights will take place, there is no reason to limit flights to those corridors anymore. Instead, a database can be built with no-fly areas and other restrictions, and military guys can build their routes around them. The result would be increased training effectiveness, enhanced safety, and minimized noise complaints by avoiding overflights of the same areas all the time.
If anyone has any thoughts, inputs, or especially good research sources, I would greatly appreciate your help!