Controller Questioning A Pilot's Technique . . .

mtsu_av8er

Well-Known Member
Curious . . . at what point is it appropriate for a local controller to cancel a landing clearance, because the pilot was waiting too long to lower the gear?
 
ZTL Training Department
  • Once cleared to land, cancel landing clearance only if unsafe ground conditions exist (runway incursion, etc.).
  • Do not cancel landing clearance because you think the pilot is too far off the localizer of too high or low -- the pilot is in charge of that decision. ATC cannot instruct a pilot to call a "missed approach" -- that's a call only the pilot can make.

FAA Order 7110.65R

3-1-10. OBSERVED ABNORMALITIES

When requested by a pilot or when you deem it necessary, inform an aircraft of any observed abnormal aircraft condition.

PHRASEOLOGY-
(Item) APPEAR/S (observed condition).

EXAMPLE-
"Landing gear appears up."
"Landing gear appears down and in place."
"Rear baggage door appears open."
2-1-6. SAFETY ALERT

Issue a safety alert to an aircraft if you are aware the aircraft is in a position/altitude which, in your judgment, places it in unsafe proximity to terrain, obstructions, or other aircraft. Once the pilot informs you action is being taken to resolve the situation, you may discontinue the issuance of further alerts. Do not assume that because someone else has responsibility for the aircraft that the unsafe situation has been observed and the safety alert issued; inform the appropriate controller.

NOTE-
1. The issuance of a safety alert is a first priority (see para 2-1-2, Duty Priority) once the controller observes and recognizes a situation of unsafe aircraft proximity to terrain, obstacles, or other aircraft. Conditions, such as workload, traffic volume, the quality/limitations of the radar system, and the available lead time to react are factors in determining whether it is reasonable for the controller to observe and recognize such situations. While a controller cannot see immediately the development of every situation where a safety alert must be issued, the controller must remain vigilant for such situations and issue a safety alert when the situation is recognized.

2. Recognition of situations of unsafe proximity may result from MSAW/E-MSAW/LAAS, automatic altitude readouts, Conflict/Mode C Intruder Alert, observations on a PAR scope, or pilot reports.

3. Once the alert is issued, it is solely the pilot's prerogative to determine what course of action, if any, will be taken.

I appreciate the controller's desire to not have his runway closed down because of debris, and, maybe s/he had the Comair Lexington accident in mind where the question was asked several times about why the controller didn't do more.

As far as cancelling a landing clearance:
3. Once the alert is issued, it is solely the pilot's prerogative to determine what course of action, if any, will be taken.
Maybe the controller felt they were helping the pilot decide his course of action. :buck:
 
This thread reminds me of the old story about a late descent clearance:

Controller: "Cross ZZZ at 10,000."
Pilot: "We're too high to comply with that restriction."
Controller: "Don't you have speedbrakes on that thing?"
Pilot: "Those are for my mistakes, not yours."
 
Uh - Minuteman, you do realize that ZTL Training Department

Is not an OFFICIAL FAA authorized source for information, but rather a VATSIM (Fly Online with VATSIM.net - Virtual Air Traffic Simulation Network providing simulated air traffic control and online flying) mock ARTCC facility?

HAH! Well, don't I suck? I didn't realize it was a VATSIM thing. I was just getting used to this whole information-at-my-fingertips thing and nobody told me I had to fact check. :crazy:

Thought I was referring to something legit, like National Air Traffic Controllers Association Local ZTL. NATCA from the local TRACON used to have an airspace familiarization page and an FAQ. It was nice, but they took it down a while back.
 
There is nothing in the 7110.65 that says the controller can or can't cancel a landing clearance if your gear isn't down. Controllers are supposed to notice and tell you "it appears" and then whatever the problem is, you gear is up, door open etc. The entire provision pertains for the proper way to provide a verbal warning. However, since there is nothing that says they can or can't cancel a landing clearance, 1-1-1 in the 7110.65 becomes the appropriate section. "Controllers are required to be familiar with the provisions of this order that pertain to their operational responsibilities and to excercise their best judgement if they encounter situations that are not covered by it."
 
Going into MGM one afternoon I called up tower "Bluestreak XXX right base gear down". There was a pause and then tower came back with "roger Bluestreak XXX cleared to land. Would you like the approach end cable up for your tail hook?"
 
It's always great when you're working UH-1's. You give 'em the "check wheels down" line and they always come back with something interesting. like "Down and welded."
 
The very reason I like the Air Force wheels down check.

Since it was mentioned, the LATEST point that Air Force guys are required to call gear down is "prior to crossing the runway threshold." But MOST will do it at the FAF (instruments), or on the Base turn (VFR), as most are taught to have the gear down prior to the "perch".
 
Well, here's the story.

I was going into KMEM the other morning, and I just happened to be in a 210 that day (had to swap an aircraft with another pilot). I am EXTREMELY comfortable in that airplane. While on with Approach, the controller asked me if I could maintain 160 KIAS to the runway, and I replied that I could give him 160 until a VERY short final, and then slow down - maybe land a little long, but that it would be no problem. So, he sequenced me in on the visual, and turned a CRJ in behind me from the downwind.

The final controller cleared me for the approach, and again asked me to maintain max forward speed if possible. No problem . . . nothing unsafe about it. With a VLO of 165, VFE of 160 for 10 degrees, 130 for 20 degrees and 115 for 30 degrees . . . piece of cake.

So, on with the tower, cleared to land, and just coming up on about a mile final, i pull the power out, gear down, and flaps 10. Just as soon as I lowered the handle, the tower controller says, "FLX305, cancel approach and landing clearance - um, cleared to land [obviously seeing that my gear was coming down]. I continued slowing, but arrested the descent, preparing for a go-around, and replied with "FLX305, confirming cleared to land?". She replied, "FLX 305, you are cleared to land".

So, I landed, made the same turn-off that I always do, and she started to explain that she noticed that my gear wasn't down, and was going to have me go around. She followed it up with the always-dreaded "I need you to call the tower supervisor . . . . advise when ready to copy".

So, after I shut down, I gave the tower supervisor a call. He started by saying that I wasn't being violated (good thing - I didn't do anything), and advised me that I had created a "moment of anxiety", and that they don;t like to see pilots that close to the runway with the gear up. He then proceeded to tell me the correct way to fly the airplane, and that I should configure the airplane a lot earlier. I thanked him for his advise, and told him that the only time that safety was compromised was when the tower controller canceled my approach and landing clearance and cleared me to land, all in the same sentence. He didn't really respond to that, and I'm sure that he didn't like it.

And, that was that!

On a side note, the next morning, myself and the other FLX pilot heading into KMEM that morning made an effort to ensure that we were slowed to 120 KIAS, flaps and gear down, and stabilized 40 miles out.

We configured the airplanes a lot earlier. ;)
 
Back
Top