Positive Rate
Pre-Flight
- Joined
- Mar 2, 2013
- Messages
- 72
- Display Name
Display name:
Vr
Using Flight Simulation for Procedures & Skills Orientation
As some of you already know, I'll be using flight simulation software during what I'm calling the "Pre-Training" phase, which will be over the next eight (8) months until I start my actual flight training sometime at the end of this year, or very early next year.
What I am not trying to accomplish with this thread:
- Become a pilot overnight
- Learn about the kinethetics of flying real airplanes from a desktop sim
- Develop the physical acuity necessary to know what a real airplane feels like from a sim
- Develop a physical understanding of the flight dynamics of real airplanes from the sim
- Nail down all the aspects of real flying from a desktop windows based sim
What I am trying to accomplish with this thread:
- Orientation to procedural knowledge necessary for VFR & IFR operations
- Develop procedural knowledge relative to departure, approach and en route navigation
- Develop procedural knowledge of avionics & instruments relative to the use of navaids
- Develop good procedural habits and fundamental procedural memory patterns
- Develop ATC radio communication skills while simulating in-flight procedures in Class B airspace
- Develop knowledge of specific aircraft speed & rate related performance factors
- Orientation to flight planning using Pen & Paper, GNS 530/430 WAAS and the G1000
My questions will always be related to Procedures: What, When, Why, Where, How and Who. I will never ask a question about how something should "feel." I won't get the kinesthetic aspect of flying from a desktop simulator, nor is that what I am seeking.
How I will approach the forum:
I will try my best to never ask questions that I cannot first find answers to on my own by reading a book or publication. Or, I might already have an answer, but I might have additional questions that the author did not address, or did not make clear enough for me in particular.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question #1:
Why the navaid split pea soup?
I understand that some navaids were developed before I was born. Heck, some of it even goes back before Abraham Lincoln, was born. In fact, there might even be some navaids out there that pre-date both the Egyptian Pyramids and even the Mayan Ruins. Having said that, why has there been no successful attempt at simply unifying navaids under a singular technological code or method of operations?
In other words, there are VORs for example that have morphed over time into VORTACs, VORs that have eventually become VOR/DME. That seems a bit different than the LNAV to VNAV relationship, or the LPV to PV relationship where there was a true extension of technology leading to a new type of navaid - but even so, RNAV is just another form of LORAN (slightly confusing, no doubt for some).
The VFR chart doesn't even show the presence of LORAN-C. Still, LORAN-C is output in several different ways through different in-cockpit instruments. NDB, which is still very much in use based on what I've read, is output through the ADF which is not a navaid itself, but an instrument installed in the cockpit panel. Not to mention the fact that all of this and more, requires that multiple instruments be installed in the cockpit to be of any use to anyone at all - which also means, a different set of procedures for their individual usage (increased pilot workloads).
At some point, being a non-pilot, I am forced to stop and ask myself, why the split pea soup of navaids. When you look at the U.S. based navaids, its like a smorgasbord of flavors out there. Was it the fact that one technology came along and supplanted the other? Or, did multiple technologies get merged together to form a hybrid in some cases? Did the government just get lazy and decided not to advance the technology by integrating components into a singular, unified Navaid concept?
Today, you have aircraft in the U.S. being forced to fly circuitous routes just to get from point "A" to point "B," where the distance between both points is often times significantly less than the total lateral distance flown, all because of the way the navaids are laid out across the country and because of the way they function.
I think I understand the issue, I just want to hear it from other licensed pilots.
I've often wondered how you guys know which one's to use and under what circumstances do you favor one over the other, or do you use them all at the same time in some sort of Navigation Symphony in the sky?
If I had my way, I would at the very least organize and categorize navaids in the following way:
- Departure Navaids
- En Route Navaids
- Approach Navaids
- Landing Navaids
I can hear someone saying, "Why. Why on earth would you do such a crazy thing?"
Well, heck - I don't know. I'm obviously not yet a pilot. However, what I do know is that my brain loves to organize things. Maybe one of you will point me to a book or publication that explains how these navaids are already organized in such a fashion, or better.
I know that navaids are different because of their function - they each do different things - I get that. It just seems a bit weird to me that pilots are flying around the skies with a multitude of different equipment requirements just to handle the split pea soup that is today's navaid labyrinth.
I'm not out to single handily change it. I'm not railing against it. I will have to learn how to use it. I'm just sitting here wondering why it has taken so long before anyone bothered to integrate this stuff in far more logical manner than it is today.
Maybe this is what RNP/PBN is all about, but the current equipment requirements for RNP would sideline the vast majority of GA aircraft being flown today.
Do you guys ever foresee the navaid split pea soup becoming a nice, smooth, tasty vanilla shake some day?
Cheers.