In-flight Conditions if Applicable
Thread Starter
In-flight Conditions if Applicable
Does anyone have a reference on the inflight conditions to be reported on contact with approach?
I'm used to visual, Visual on top, In cloud but someone told me the other day that this had all been removed (6-7 years ago apparently)... I must have been hiding under a rock.
Any takers
I'm used to visual, Visual on top, In cloud but someone told me the other day that this had all been removed (6-7 years ago apparently)... I must have been hiding under a rock.
Any takers
Yea was discussing this one the other day. Apparently changed recently from "visual/in cloud/on top" to either "visual" or not reporting anything. ATC either want to know if you're visual or not. If you're not, you don't say anything other than level and ATIS info and only report 'runway XX in sight' to director (where applicable) later on.
Join Date: Sep 2006
Location: Melbourne
Posts: 1,569
Likes: 0
Received 0 Likes
on
0 Posts
What Dragun says is pretty much true, but not to most inc the airline drivers who are meant to be at the top of the tree & sharp ar a whip leading by Example!
I don't think anyone really cares ATC themselves often say non std R/T procedures, we all do, human nature simple as that
CW
I don't think anyone really cares ATC themselves often say non std R/T procedures, we all do, human nature simple as that
CW
Onya Wally! Unfortunately, the airline pilot of today (well, their radio procs) is not a patch on yesteryear. So don't look to them for guidance.
This was the way it was BEFORE the superb ICAO RT arrived. In fact, AIP was reasonably clear on this call: you called "visual" if appropriate, which meant if you could do a Visual approach, then you said Visual, if not, keep your trap shut. I recall there was a note explaining the call. On top? Who cares? Proceed on the STAR/Radar descent until you get visual. If you never get visual, Inst Apps were probably on the ATIS so your follow the dials and land.
If at a non-radar tower, you called your inflight condition every time because that determined what the controller would give you - a visual app or a DME Arrival (for example).
Now, AIP is as clear as mud. It has the same call text as the old days, but not the explanatory text.
ATC either want to know if you're visual or not. If you're not, you don't say anything other than level and ATIS info and only report 'runway XX in sight' to director (where applicable) later on.
If at a non-radar tower, you called your inflight condition every time because that determined what the controller would give you - a visual app or a DME Arrival (for example).
Now, AIP is as clear as mud. It has the same call text as the old days, but not the explanatory text.
Thread Starter
its nice to know what people think... Anyone have any Jepp reference.
My Jepps still say level, ATIS code and "in-flight conditions" if applicable.
Any references for in-flight conditions?
My Jepps still say level, ATIS code and "in-flight conditions" if applicable.
Any references for in-flight conditions?
Sprucegoose
Join Date: Sep 2000
Location: Hughes Point, where life is great! Was also resident on page 13, but now I'm lost in Cyberspace....
Age: 59
Posts: 3,485
Likes: 0
Received 1 Like
on
1 Post
On top? Who cares?
If I wanted a weather report, I would ring the MET OFFICE!
PS: I like threads which make me go and get the books out...
Bula
That is the reference you're looking for. I think the discussion here is the interpretation of the words 'if appropriate'. There is nothing detailed for that.
ATC only want to know whether you're visual or not as it changes their separation criteria.
That is the reference you're looking for. I think the discussion here is the interpretation of the words 'if appropriate'. There is nothing detailed for that.
ATC only want to know whether you're visual or not as it changes their separation criteria.
