Instrument Approach into Uncontrolled Field - TP ??? MikeD

Malko

ughhh
Staff member
So today I am up safety piloting for fellow JC member, Dazzler and a situation/question came up.

About a mile or two from the FAF we are handed off from the approach controller to the CTAF. We make a couple of position reports and continue in (3 planes in the area). About 4 miles out (inside the FAF) I hear a plane on announce entering the downwind and keep on the lookout but do not see it yet. At 3 miles, I make another CTAF call (we are straight in). This is immediately followed by earlier plane making their base call and I see the plane turning base inside of us. If we were landing, we would have had to go around, because there is no way the plane would have been off of the rw in time for us to land.

Questions:

Is there a point when a plane should not turn base inside of a straight inbound a/c?

Also, is there a hard and fast definition for short final? I called short final at one point and some individual came on the CTAF stating "short final is closer than that". It was as if he was trying to scold me.
tongue.gif
to him I say.
 
Quick question:

1. Did you make position reports to the lowest common denominator? That is, call out distances in miles as opposed to using fix names or such, or anything else that a VFR pilot in the pattern might not be familiar with?

That's the first thing that needs to be done when shooting approaches at airports with a CTAF, since most VFR pilots aren't familiar with fix names, but will be able to relate to distances (or at least should be able to if they have any SA......not something to bet on).

As you well know, straight-in has priority over a pattern aircraft. Reference 14 CFR 91.113(g). Here:

[ QUOTE ]

(g) Landing. Aircraft, while on final approach to land or while
landing, have the right-of-way over other aircraft in flight or
operating on the surface, except that they shall not take advantage of
this rule to force an aircraft off the runway surface which has already
landed and is attempting to make way for an aircraft on final approach.
When two or more aircraft are approaching an airport for the purpose of
landing, the aircraft at the lower altitude has the right-of-way, but it
shall not take advantage of this rule to cut in front of another which
is on final approach to land or to overtake that aircraft.

[/ QUOTE ]

In the pattern, the straight-in is already established on final, lower and configured, and has less maneuvering ability or place to go than someone in the pattern. In the military pattern (overhead), for me to be able to roll off downwind, I must be able to know that I can safely maneuver and land ahead of the straight-in, and either have him in sight, or have SA on his location. If I don't see the straight-in or there's not enough room to maneuver, then it's up to me to remain at pattern altitude, turn back to upwind over the runway and carry straight through, or break out of the pattern (or make a 360 if it's not a problem....ie- no one else in the pattern).

No set definition for short final, I consider it to be 1-2 miles from the runway.

Comments like his on CTAF qualify for the MikeD, limited-time only, deluxe ass-kicking on the tarmac, complete with re-education in the error of their ways, the definition of the chain of command, and re-schooling in the concepts of clear/concise/correct radio comm, to include non-extraneous BS on freq........all free of charge.
 
[ QUOTE ]
Quick question:

1. Did you make position reports to the lowest common denominator? That is, call out distances in miles as opposed to using fix names or such, or anything else that a VFR pilot in the pattern might not be familiar with?

[/ QUOTE ]

Yes, we did. FAF was 5.7 SE. Call was made "Airlake traffic, Arrow 8265s 5.7 miles SE, inbound on the ils30, Airlake."

Same call was made at 3 miles, and then the traffic turned base after that call. I believe I called short final 2 miles out and then the "base" aircraft went missed before even reaching the threshold. And thats when smarty pants got on the CTAF.

[ QUOTE ]
Comments like his on CTAF qualify for the MikeD, limited-time only, deluxe ass-kicking on the tarmac, complete with re-education in the error of their ways, the definition of the chain of command, and re-schooling in the concepts of clear/concise/correct radio comm, to include non-extraneous BS on freq........all free of charge.

[/ QUOTE ]

That's exactly what I was thinking. It is so funny that when this was playing out and smarty pants got on the CTAF to spout his knowledge, I thought, "MikeD would kick his @#$".

So when do I get my JC-Air America Wings.
grin.gif
 
I see a problem with the interpretation of said FAR....While it does say that a plane on final approach has right of way, it also says the lower aircraft approaching an aiport has right of way.

Frequently an aircraft on an "intermediate segment" will be above pattern altitude, let's say 1,000 - 2,000' AGL. Is this level-non configured aircraft on Final Approach? IMO no. Is a configured aircraft still outside the FAF on final approach? IMO no, but it's a grey area.

So getting back to the original case, a plane on downwind at 1000AGL and an aircraft approaching at some intermediate altitude outside the FAF, I'd say aircraft at lower altitude has right of way, why? He's at a lower altitude and the other aircraft is not on final approach.

If the other aircraft is within the FAF yet still above the other aircraft I find that the FAR conflicts, one aircraft is lower (should have right-of way), the other is on final approach (should have right of way).

Bottom line, keep your eyes and ears open cause nobody's thinking about this stuff during an ILS. Nobody says the FARs are perfect.
 
[ QUOTE ]

Comments like his on CTAF qualify for the MikeD, limited-time only, deluxe ass-kicking on the tarmac, complete with re-education in the error of their ways, the definition of the chain of command, and re-schooling in the concepts of clear/concise/correct radio comm, to include non-extraneous BS on freq........all free of charge.

[/ QUOTE ]

See, you need to come out here and work with me at Tune, MikeD . . .trying to set these hillbillies straight is full-time work!!
 
[ QUOTE ]
I see a problem with the interpretation of said FAR....While it does say that a plane on final approach has right of way, it also says the lower aircraft approaching an aiport has right of way.

[/ QUOTE ]

Yes, but as I read the bold portion of the FAR, the lower aircraft cannot take advantage.

[ QUOTE ]
As you well know, straight-in has priority over a pattern aircraft. Reference 14 CFR 91.113(g). Here:


[ QUOTE ]
(g) Landing. Aircraft, while on final approach to land or while
landing, have the right-of-way over other aircraft in flight or
operating on the surface, except that they shall not take advantage of
this rule to force an aircraft off the runway surface which has already
landed and is attempting to make way for an aircraft on final approach.
When two or more aircraft are approaching an airport for the purpose of
landing, the aircraft at the lower altitude has the right-of-way, but it
shall not take advantage of this rule to cut in front of another which
is on final approach to land
or to overtake that aircraft.


[/ QUOTE ]

Clear as Mud......
 
I don't know man...around here if you called short final at 2 miles, and I was on base? I would be on the ground and off the runway before you started your final flap extension. In most small aircraft, turns to final at an uncontrolled field are going to happen within 3/4 of a mile. There is a big difference between the speed that Mike's jet is traveling and the final approach speed of your Arrow. In my opinion the guy was not in the wrong, but probably should have made a direct call to you to tell you he was going to try to land in front of you.
 
Just another thought...

While you should also announce your distance, it's also a good idea to announce altitude. Some uncontrolled fields have precision appoaches, and you could be as low as 200' AGL. If I hear an airplane is 200' AGL and .5 mile out it gives me better idea of where to look.
 
[ QUOTE ]
Just another thought...

While you should also announce your distance, it's also a good idea to announce altitude.

[/ QUOTE ]

good point

[ QUOTE ]
Some uncontrolled fields have precision appoaches,

[/ QUOTE ]

Yep and we were on the ILS approach into the field.
 
[ QUOTE ]
I would be on the ground and off the runway before you started your final flap extension.

[/ QUOTE ]

Oh some hot shot huh ! You must be good.
sarcasm.gif


[ QUOTE ]
There is a big difference between the speed that Mike's jet is traveling and the final approach speed of your Arrow.

[/ QUOTE ]

True, I'll give you that. There is also a difference in speed between the Arrow we were flying and the Katana (small version) that turned base in front of us. If they (student/cfi) could have gotten down and off at one of the fist couple of taxiways, great. Other wise they may have had to roll to the end and would have been on the rw when we got close to land. I know as a student pilot, I would not have felt comfortable trying to get down and off knowing someone would have been right behind me.

[ QUOTE ]
In my opinion the guy was not in the wrong,

[/ QUOTE ]

No problem there, but if something were to happen, then we go to the FARS and as I am interpreting them, he was in the wrong. How can they enforce soemthing that is clear as mud and open to so much different intrepatation?
banghead.gif
 
How's this for a rule of thumb: An aircraft that is in the traffic pattern has the right of way over an aircraft that is not in the traffic pattern. You are 4 miles out and know that there is another airplane already in the pattern. Sorry, I think you're the one who needs to make the adjustment.
 
The guy in the traffic pattern could show some courtesy as well. I know that I'll extend the downwind a bit to help out guys doing IFR training. Up here the ag pilots just make up their own patterns and use any runway at all and none of them have radios and then on top of that they are always cutting people off as well.
 
I like the idea of calling out altitude as well as distance when flying an instrument approach, for the benefit of those in the pattern, and I will employ this technique in the future.

As for the definition of short final, this is completely open for interpretation. Sure, if you're flying a small plane in the pattern and you consider a normal final to be 1 mile or so, then if you turn base early for a short approach, giving a final of half a mile say, then you would consider that a short final.

However, an aircraft that has been on approach 10 miles out - typical on an ILS approach - may well consider 2 miles out to be short final.

Bottom line is a good lookout for traffic coupled with common sense is what is needed when mixing IFR and VFR traffic at busy untowered airports, and kudos to JEP for providing that for me yesterday!
 
When I took my instrument ride (who was with the same guy that lilrtk took all his with out of Lapeer) the examiner said the thing that he didn't like, but was acceptable, was the way I did my callouts on my non-precision approach. When I was making the VOR-A approach into Lapeer I made my callouts on the CTAF as the fixes, flew my approach and did my circle to land. Obviously my callouts changed once I got to the point of entering the pattern because I wasn't going to be doing a straight in. When we got down he said that it was technically correct in the way I made the callouts, telling people over the CTAF what fixes I were at. The reasoning behind it is that if you're actually in instrument conditions and doing an approach down to mins. in the clouds, there are not going to be any VFR aircraft around to worry about running into. In that case, the only people that will be flying will be other people on instrument flight plans that will either be about to depart, or will be on some other segment of the approach. In that case, you don't want to call out "3 miles from the left downwind," you want to tell them when you're crossing fixes.

The issue that he had, and he said that he wanted to just let me know this and not bust my balls about it because what I did wasn't wrong, was that when you're doing a simulated approach in VFR conditions you need to make callouts that the VFR traffic (which you would expect on a clear day) would understand.

The point that I guess I'm trying to drive home is that you have to expect different things out of different kinds of pilots. Flying on a CAVU day and call short final as 2 miles to an uncontrolled airport with an ILS approach? The VFR only pilots are going to think your nuts! Now to me, 2 miles on an ILS approach IS a short final. You're getting pretty low at that point, you've probably already put yourself in a pretty good configuration for landing and you are trying to maintain a stabalized approach so you can make a good landing. But again, you've got to play to your audience to make sure that they don't run into you. With that, 2 miles to VFR traffic is not a short final.

You win some you loose some at a point, the real deal is that someone has got to keep their eyes outside the cockpit to watch for these guys that don't have a clue what they're doing.
 
Personally, I think it boils down to simple courtesy. Do your best to accomodate each other's objective around the airport, whether that's extending your downwind for close traffic on an instrument approach or slowing down a tad on a straight-in approach for traffic already established on downwind/base. It's a judgement call.
 
[ QUOTE ]
How's this for a rule of thumb: An aircraft that is in the traffic pattern has the right of way over an aircraft that is not in the traffic pattern. You are 4 miles out and know that there is another airplane already in the pattern. Sorry, I think you're the one who needs to make the adjustment.

[/ QUOTE ]

Is that written any place? Again, good common sense and judgement is the key, and like the reg says, no taking advantage. If a guy is in the pattern on crosswind or has just turned downwind, and I'm 4-5 mile final, I wouldn't think I would have to give right of way due to me being established on final. But I'd also communicate with the guy and we'd work it out one way or the other......

.....unless his comm sucked, then I'd have to kick his ass........either way the right of way goes.
 
[ QUOTE ]
The reasoning behind it is that if you're actually in instrument conditions and doing an approach down to mins. in the clouds, there are not going to be any VFR aircraft around to worry about running into. In that case, the only people that will be flying will be other people on instrument flight plans that will either be about to depart, or will be on some other segment of the approach. In that case, you don't want to call out "3 miles from the left downwind," you want to tell them when you're crossing fixes.

[/ QUOTE ]

I always call mileage from the field, even in solid IMC. That way you get into a habit of using the same type of position announcements and feel comfortable making them in VMC or IMC.
 
[ QUOTE ]
I always call mileage from the field, even in solid IMC. That way you get into a habit of using the same type of position announcements and feel comfortable making them in VMC or IMC.

[/ QUOTE ]

See I disagree with that because if there are other traffic in the clouds with you they're going to scrambling to figure out what the heck you are. Use known reporting points and fixes and don't make up your own.
 
Back
Top