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 for the approach I received the following call
(callsign) request heading
It caught me off guard, and it took a while but I eventually interpreted it as "say heading" and gave him my current heading. He didn't complain, but I'm still not sure if that's what he wanted.
A bit later I got a similar call
(callsign) request QNE
However, I was unfamiliar with that Q-code (as a private pilot 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 sure the guy was German, so it might be a German military thing, or a NATO thing, or just a simple mistake on his side?
"Request " is very common in Europe but it's usually the pilot who will use it to talk to ATC, as in "Request taxi" or "Request to enter your airspace".
I've never heard this phrase being used by a controller in Belgium, France and The Netherlands (where I've flown the most so far). Seems very odd to me.
In civil aviation the ICAO standard phraseology should be used. This phraseology is described in ICAO document 9432. The standard ICAO phraseology is to use the word report in the first case. According to the definitions it means: "Pass me the following information ..."
[callsign] report heading
The second phrase is even stranger. QNE is the standard pressure altimetry setting of 1013.25 Hectopascal (29.92 inches of mercury in the US). When an altimeter is set to standard pressure, the normal way of reporting the altitude is in Flight Levels. So in this case the standard phraseology should have been
[callsign] report Flight Level.
heading. He didn't complain, but I'm still not sure if that's what he wanted. A bit later I got a similar call (callsign) request QNE However, I was unfamiliar with that Q-code (as a private pilot 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
with the remedial training option the FAA may offer, but what did he mean by "counseling session"? The controller implied it would be handled by phone. I'm not freaking yet, just concerned. I told everything..., and while I eventually found the proper frequency (I'd planned to request flight following) I had crossed over the outer ring. When I contacted Approach, the Approach Controller explained I was in Bravo, and to turn West and exit. I did say, "Am I not ABOVE Bravo airspace?" He said "No, you're in it" and to fly West and exit. From that moment, I followed approach control's directions to a T
I'm a student pursuing a US Private Pilot License, and recently scheduled my checkride. I've been training in a 1981 Piper Warrior (PA-28-161), but if its annual goes sour I may have to take my..., they're pretty similar anyway—they're even both the same ATC type (P28A)—but they aren't the same model. Here's the catch: Form 8710, the "Airman Certificate and/or Rating Application", asks specifically for [II.A.2.] Total time in this make/model and/or approved FFS or FTD (Hrs.) Furthermore, according to the IACRA FAQ ("I'm a Designated Examiner. I noticed a mistake when reviewing the IACRA
to switch to ground frequency with this clearance (assume I just landed)? N12345, right on E, cross 27 R, contact ground .9 Should I call ground (or switch frequency, so I no longer hear the tower) before or after crossing 27 R? My by-the-book assumption would be immediately, as there's no "then" or "after crossing" or similar, but somehow that feels wrong. I suppose normally it doesn't really matter, but in the case of someone (which includes me, everyone makes mistakes) doing something wrong, where would they call me as I'm about to cross 27 R? The reason I ask is that I saw exactly
and that's why I don't hear reply, however on approach side much bigger distances are heard in my area) Thank you I did verify that indeed the aircraft that I don't hear read back from receives... 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 and speed adjustments). I tend to notice this with bigger birds (777,747,340), however smaller regional jets almost always promptly read back. Questions: Is there an alternative way of ATC
"report a 3 mile base" meant "report a 3 mile final and fly a straight in approach." I'm not sure if he was on the frequency when it happened or if the tower controller called him after the fact... with the runway on final and get a feeling for how the winds were blowing since the ATIS reported them as being variable in direction. That said, what I ended up doing was making a wide base, except..., I established contact with the tower and was told to "enter left base, runway 7, report 3 miles out." I interpreted the "report 3 miles out" as to give the tower a call when I was 3 miles away from
My instructor made "request right closed traffic..." call before practicing series of landings. Just wondering, what is the difference with "stay in the pattern..." request and which one and when I have to use? Thanks.
In As the Pro Flies, John R. Hoyt writes (pages 41-42): Suppose we have to land in high, gusty winds. That's what happened to Pilot Z, who once landed his plane during such conditions with his flaps down. After the wheels were on the runway he relaxed, never realizing that a plane is not landed until the switches are cut. Because he still had airspeed and because full flaps lowered the take-off speed, a small gust of wind was all that he needed to begin flying again. The additional lift was enough to raise him 10 feet from the runway, and at that point he ran out of gust
. This "mushing" went on for what seemed ages before I eventually applied power and pushed the nose down to gain airspeed again. We tried it again after that and the same thing happened. I had an instructor with me who has thousands of hours in a C172 and he had never experienced something like this before. The odd thing is that this only happened during that flight. During later flights this didn't occur...When I took delivery of a new Cessna 182T last year, I did a test flight for certification purposes. During the test flight we had to perform a power off stall but that didn't go as planned
I was watching an episode of MythBusters where they were trying to break glass windows and cups using a sonic boom generated by a F/A-18 Hornet, flown by the Blue Angels. In summary, they were... curious about what a sonic boom is to begin with, here's a wikipedia article. **Just to clarify, for those who have seen the episode. A window is broken during the 200ft pass but they say that it only... the boom straight at the house, still no windows were shattered. ** But I've wondered, ever since, if they were unsuccessful because the plane was simply too small. What if the sonic boom had been