January 1, 1999
By John S. Yodice
A 10,000-hour corporate pilot was grounded by the FAA on an emergency basis because of a single air traffic control incident. That's a pretty extreme action. Let's try to put it in perspective. In the scheme of things, the revocation of an FAA pilot certificate on an emergency basis is the most drastic enforcement sanction that the FAA can impose upon a pilot. For one thing, revocation means that the pilot must apply for and requalify for the certificates if he or she wants them back. For another, the FAA will probably not accept such an application for a year, and maybe not even as soon as that. For still another, revocation on an emergency basis means that the certificates are revoked immediately, with no stay of the revocation pending review of the case by the National Transportation Safety Board - in other words, an immediate grounding. Last, it is very unusual that the FAA would take such drastic action based on a single incident.
Here is what happened:The pilot was flying a twin-engine Cessna 310 into the Alexandria (Louisiana) International Airport. The airport is in Class D airspace, requiring the establishment of two-way radio communication with the control tower prior to entering the airspace. At the time, there was other traffic in the Alexandria airport area.
As the twin Cessna approached the airport, the pilot contacted the Alexandria tower, announcing that he was five miles southeast, inbound for landing. He later announced that he was entering left downwind for Runway 14. He was told to continue and to report a left base for Runway 14. Later, because of other traffic in the pattern, the twin Cessna was instructed by the tower to continue its downwind leg and to follow a single-engine Cessna. The tower advised that the other airplane would be landing ahead of the 310. The pilot of the twin Cessna, looking all the while, advised the tower that he was unable to visually locate the traffic. The tower then instructed the 310 pilot to continue on the downwind and said that the tower would call his base leg. He was then told twice to extend downwind, and twice he complied; when the pilot estimated that he was seven miles from the airport, and he could see no conflicting traffic, however, he advised the tower that he was turning base.
An extract of the ATC communications gives more flavor to the story:
Twin Cessna: "[Twin Cessna] is entering left downwind for Runway 14."
Tower: "Twin Cessna [N number] roger, Runway 14 is in use, altimeter 29.82, wind 180 at 20, continue, and report a left base for Runway 14."
Tower: "[Twin Cessna] you're number three, correction, yeah, number three to follow a Cessna on a left downwind for Runway 14."
Twin Cessna: "We're about to turn base for Runway 14."
Tower: "[Twin Cessna] roger, continue on your downwind, you're number three to follow a Cessna also on a left downwind Runway 14."
Twin Cessna: "I don't see a Cessna on a left downwind, I see one on a right crosswind."
Tower: "Yes sir, Cessna, I have the Cessna in sight on a left downwind. I'll call your base for you."
Twin Cessna: "You're going to put me in behind an airplane that's on a crosswind?"
Tower: "Negative, sir. You have a Cessna in your 12 o'clock on a left downwind."
Twin Cessna: "Roger, no joy."
Twin Cessna: "Another point-out on the Cessna on downwind, [tower]. Has he turned base yet?"
Tower: "[Twin Cessna], he's on a left base now about three miles out."
Twin Cessna: "No joy."
Tower: "Roger, continue on your downwind."
Twin Cessna: "[Twin Cessna] is turning left base."
Tower: "[Twin Cessna], you have the Cessna in sight you're following?"
Twin Cessna: "I sure don't."
Tower: "OK. I didn't tell you to turn base, continue on your downwind."
Twin Cessna: "Hey, you're not determining when I can turn base, son; I do that. Now where's the traffic?"
Tower: "Traffic should be in your vicinity."
Twin Cessna: "OK, do you see the plane?"
Tower: "Yes sir, I sure do."
Twin Cessna: "Is he on base or final?"
Tower: "He's on base to final."
Twin Cessna: "OK, that's what we're asking."
Tower: "He's on base, he's on final now."
Twin Cessna: "Roger that."
The pilot proceeded onto final and landed, without a clearance to land, in front of the single-engine Cessna that had been cleared to land.
After landing, the twin Cessna requested permission to execute a 360-degree turn on the taxiway. He wanted to get a look at the traffic behind him. The tower denied the request and instructed the aircraft to taxi straight ahead. The twin Cessna made the turn anyway.
On these facts, the FAA issued an emergency order revoking the pilot's airline transport pilot and flight instructor certificates - immediately grounding him. The FAA alleged that the pilot had violated FAR sections 91.111(a), creating a collision hazard with another aircraft; 91.123(b), failing to comply with ATC clearances and instructions; 91.129(i), operating in Class D airspace before establishing communications; and 91.13(a), operating carelessly or recklessly.
The pilot was not at all happy about the handling of his flight by ATC, much less the FAA's reaction to the incident. He appealed the FAA order to the National Transportation Safety Board. He argued that the tower, a VFR tower, was improperly providing separation services by directing him to continue downwind when he could not locate the other aircraft and by advising him when it would be safe to turn base. He also complained that ATC could have done a better job helping him locate the other aircraft.
Both the administrative law judge and the full Board rejected these arguments and sustained the revocations. The Board said: "Even if it were true that ATC would ordinarily not issue VFR traffic specific instructions as to how to fly the airport pattern, such instructions here, clearly intended to reduce the collision potential that a premature turn to base by respondent's aircraft could (and ultimately did) create, were, at the very least, appropriate. To the extent that the respondent found ATC's assistance in this connection unwelcome, he could have radioed his intent to exit the pattern, [radioed] for re-entry when he had all traffic converging on the airport in sight, or he could have sought permission to land ahead of the aircraft that had already been cleared to land, an option that would have possibly prompted ATC to reevaluate the relative positions of all aircraft within the airport environment and issue appropriate changes, if it believed them warranted.
"What the respondent was not free to do was ignore or defy ATC's instructions in favor of his own assessment that his aircraft should be accorded landing priority over one he could not find, but whose safety he should have appreciated could be seriously compromised if he did not allow ATC, which had both aircraft in sight, to manage the situation in accordance with its informed appraisal of how best to ensure safe operations within the controlled airspace it is charged with regulating. [The] respondent's decision to land contrary to instruction and ahead of an aircraft he did not yet see was both reckless and demonstrative of a noncompliant attitude inimical to air safety."
The FAA and the Board considered the pilot's actions to be so bad that they refused to waive the sanction even though the pilot had filed a NASA Aviation Safety Reporting system form. "An ASRP waiver is not available for deliberate, willful FAR violations, and [the] respondent's conduct was anything but inadvertent," said the NTSB.
FAA Information and Services,
Safety and Education,
In my house, every Friday night is “Movie Night.” While the movies are rarely educational (I don’t think I learned anything from the Lego Movie), we look forward to the weekly opportunity to spend time together. Why not use the same concept for your Flying Club (with the addition of education, of course)?
The Aircraft Spotlight feature looks at an airplane type and evaluates it across six areas of particular interest to flying clubs and their members: Operating Cost, Maintenance, Insurability, Training, Cross-Country, and Fun Factor.
The AOPA Internet Flight Planner (AIFP) 2.0, powered by Jeppesen, is now available in beta for all AOPA members to test. The beta period is open through early 2015.
VOLUNTEER AT AN AOPA FLY-IN NEAR YOU!
SHARE YOUR PASSION. VOLUNTEER AT AN AOPA FLY-IN. CLICK TO LEARN MORE >>>
VOLUNTEER LOCALLY AT AOPA FLY-IN! CLICK TO LEARN MORE >>>
BE A PART OF THE FLY-IN VOLUNTEER CREW! CLICK TO LEARN MORE >>>