Primary target: An aircraft not reporting mode-C, the only thing the controller has is the return on the radar.
When a controller reports a primary target as traffic to other aircraft, the controller does not have the altitude of the target. Given this, I conclude that ATC radar does not have the altitude (angle-up) to the target, and only provides azimuth.
So then without the altitude, how does the radar-system know where to put the target laterally on the screen?
Example, a radar picks up a target that is 10 miles from the station. If the target is 0 AGL, the proper position would be 10 miles out. However, if the target is at 15,000ft, the proper position would be 9.5 miles out.
Since the difference is so small, does the radar just put the target at 10 miles, and the FAA separation guidelines factor in the discrepancy?
In primary radar displays usually just the azimuth and range are plotted. So an aircraft at 15.000 ft 9.5 NM away will be plotted on 10 NM distance, just like an aircraft at 0 ft 10NM away. Usually the secondary radar is collocated with the primary so secondary targets can be displayed using the same projection (disregarding the altitude).
If you now apply horizontal separation based on this projection, you will never bust the separation minima. It is a conservative way of providing separation, but when there is no altitude information it is the best possible way.
Note that this does not only apply to primary targets, but also to Mode-A only targets
, the controller does not have the altitude of the target. Given this, I conclude that ATC radar does not have the altitude (angle-up) to the target, and only provides azimuth. So then without the altitude, how does the radar-system know where to put the target laterally on the screen? Example, a radar picks up a target that is 10 miles from the station. If the target is 0 AGL, the proper position would be 10 miles out. However, if the target is at 15,000ft, the proper position would be 9.5 miles out. Since the difference is so small, does the radar just put the target at 10 miles, and the FAA separation
Are airspace violations (e.g. entry to class B without clearance) based on primary radar and/or Mode C transponder, or something else? I read that Mode C altitude is based on pressure altitude, i.e., set to 29.92" ... but presumably that's adjusted at the ATC facility based on the current pressure before being used for altitude enforcement. This begs the question, what would stop one (hypothetically), just winding back the altimeter pressure reading to appear to be at a lower altitude? So to summarize: How are airspace violations detected: What data input is used? If Mode C reading
Based on the reading I've been doing of FAA's Next Generation Air Traffic Control (NextGen) plans, I've been wondering if and how radar systems will continue to be used for ATC as NextGen rolls out? Questions include: Is it correct to assert that radar coverage will effectively become a less precise, backup only, data feed? I am suggesting this because my understanding (which could easily be incorrect) is that ADS-B will mandated for most (everyone?) and so aircraft will be actively reporting their precise position without the need for a radar track. Will existing radar coverage eventually
out in the question for some reason mostly it is "big" aircraft that gets this preferential treatment, but I am not 100% sure why. ...I enjoy tracking air traffic at my local KORD. I listen on LiveATC and use my private virtual radar setup to get "real-time" traffic info. I understand which instructions need to be read back by the pilots per this question however on more than one occasion I don't hear read back on critical vector info on departure, despite the visual confirmation of instruction (pilot making proper vector
As we all know from our instrument training, the MOCA is: MINIMUM OBSTRUCTION CLEARANCE ALTITUDE (MOCA)- The lowest published altitude in effect between radio fixes on VOR airways, off-airway routes, or route segments which meets obstacle clearance requirements for the entire route segment and which assures acceptable navigational signal coverage only within 25 statute (22 nautical) miles..., segment, or route between the radio fixes defining the airway, segment, or route. (Both quotes taken straight from the Pilot/Controller Glossary) The only difference in language is the bit about 22
to another airport that is within 25 nautical miles from the airport where the student pilot normally receives training The student must be endorsed with something along the lines of: I certify that (First name, MI, Last name) has received the required training of section 61.93(b)(1). I have determined that he/she is proficient to practice solo takeoffs and landings at (airport name... the 25nm part except in title). The situation it is used in most commonly is the towered-field TO/LDG practice. There is a towered field about 10 miles north of our airport where we all go to practice
the field, ie, when my GPS indicated I was 3 miles from the field. Now, it was the most windy day I had flown solo in so far (15kt gusts) so I wanted to make sure I had ample time to line up... and told him about it because I was told to "report 3 miles out", not "report 3 mile base." I completely understand that I made my base leg too wide and that caused me to deviate from an ATC instruction...Here's the scenario: I was a student pilot on inbound for landing at my home airport on my final solo cross country flight I needed before doing a checkride. At roughly 8 miles out to the north west
The G1000 has a feature where it can put up a winds aloft arrow/speed in the PFD. I've been sort of wondering how exactly this is determined. My guess is that the aircraft (or the G1000) knows your airspeed via the pitot/static system and heading via the fluxgate/mag compass. Then, it uses your GPS position to figure out where you should be every X seconds given the airspeed and heading. Any difference must be attributable to winds aloft. Does this make sense?
case, and average case for each location, altitude, and date in the future. I have searched and searched Google to no avail. Where can this wind data be found, and how can it be used in a commercial product? For those of you who don't know what the Boeing winds are, I found this description of their software product on am informal message board (not related to Boeing): PC WindTemp... navigation, or any other type of actual flight operations. PROGRAM FEATURES A seasonal and monthly database with global coverage from 1000 millibars (364 feet pressure altitude) to 10
in Europe you pretty much need to know QNH, QFE, QDM and QTE) and only later found out it means "pressure altitude". Q-codes suck. Anyway I said "Say again" and he came back and asked how many were on board (which I incorrectly assumed at that point was what QNE meant), again, using "request". Anyway, I've never heard a controller say "request" before, is it just army version of "say"? I'm pretty...I recently had the opportunity to fly a PAR approach into Büchel Airbase in Germany. It was a ton of fun and I'll definitely try it again when I get the chance. However, as we were getting set up