Blogging the FARs: Avoid the Flow of Fixed Wing Traffic

What it means — and doesn’t mean.

I was at Wickenburg Airport for a short time yesterday and was dismayed to see another helicopter pilot practicing autorotations using a left traffic pattern for the taxiway parallel to Runway 23. In Wickenburg, it’s right traffic for Runway 23, keeping the airplanes on the northwest side of the runway. There are fewer houses out that way; a left traffic pattern would have you overflying dozens of homes.

Someone else at the airport told me that the owners of the homes southeast of the runway had asked this pilot several times not to overfly their homes. They were bothered by the noise of his buzzing aircraft just 500 feet over their houses over and over again. He replied that he was supposed to “avoid the flow of fixed wing traffic.” When one of the nicest guys on the airport suggested he fly on the other side, this pilot’s response was, “Fuck you.” Whoa. Seems like someone has an attitude problem.

But is he right? Should he be doing left traffic patterns if the airplanes would be doing right patterns?

The Rules

FAR Part 91.126, “Operating on or in the vicinity of an airport in Class G airspace,” says, in part:

(a) General. Unless otherwise authorized or required, each person operating an aircraft on or in the vicinity of an airport in a Class G airspace area must comply with the requirements of this section.

(b) Direction of turns. When approaching to land at an airport without an operating control tower in Class G airspace —

(1) Each pilot of an airplane must make all turns of that airplane to the left unless the airport displays approved light signals or visual markings indicating that turns should be made to the right, in which case the pilot must make all turns to the right; and

(2) Each pilot of a helicopter or a powered parachute must avoid the flow of fixed-wing aircraft.

To some, it might appear that Part 91.126(b)(2) gives helicopter pilots permission to fly wherever they want in Class G airspace, as long as it’s not anywhere near an airplane. Maybe that’s what our attitude-challenged helicopter pilot at Wickenburg thinks. But I’d argue that it’s simply not true.

Why Avoid the Flow? Why Not Join It?

Wickeburg Airport

Wickenburg Airport, from the approach end of Runway 05.

Helicopters are advised to avoid the flow of fixed-wing traffic mostly because of the significant differences in the way they operate. Helicopters are usually slower than airplanes, they tend to operate at lower altitudes, and they don’t need a runway to land or take off. Putting airplanes and helicopters together in a traffic pattern is like mixing oil and water: they just won’t blend.

But does avoiding the flow of fixed wing traffic mean creating a completely separate traffic pattern? Sometimes, it does.

Does it mean making yourself a noisy nuisance over a residential neighborhood on the side of the airport that normally doesn’t have aircraft flying over it? I say it doesn’t.

And what if there aren’t any airplanes in the traffic pattern? I’ll argue that there’s nothing to avoid so why not use their established, community-preferred traffic pattern?

And that was the problem yesterday: the bad attitude pilot was the only aircraft in the traffic pattern for the entire time he was flying yesterday. There was no fixed-wing traffic to avoid.

There was no reason to overfly those homes.

Fly Neighborly

Although I’m not a big fan of Helicopter Association International (HAI), I do want to commend them on their attempts (although usually feeble) to share information that’s useful to the helicopter community. Among that information is “The Fly Neighborly Guide” they offer as a PDF download from their site. Here’s a blurb about the program from their site:

The Fly Neighborly Program addresses noise abatement and public acceptance objectives with programs in the following areas: 

  • Pilot and operator awareness
  • Pilot training and indoctrination
  • Flight operations planning
  • Public acceptance and safety
  • Sensitivity to the concerns of the community

The point is, lots of people hate helicopters because they’re noisy. (In reality, they’re not all that much more noisy than an airplane. But because they usually fly lower, they seem louder.) By using techniques that help us fly more quietly and avoiding noise-sensitive areas, we’ll blend in with the environmental impact of aircraft traffic much better.

What does that mean to me? Well, here are some of the things I try to do:

  • Maintain speed above 80 knots in my R44 to avoid “rotor slap.”
  • Not fly low over homes, schools, or businesses.
  • Vary the flight path I use to approach or depart the airport.
  • When flying traffic patterns, choose a pattern that does not repeatedly overfly the same noise-sensitive areas. (Yes, the other day when I was practicing autorotations at Wickenburg, I shared the same standard traffic pattern with three airplanes.)

I do need to point out here that anyone who buys a home within 3 miles of an airport should expect some level of noise. If you don’t like aircraft noise, don’t buy a home near an airport. Period.

Why I Care

Why should I care that a bad attitude pilot is thumbing his nose (and perhaps making other hand gestures) at people who complain about his inconsiderate flying?

AFD for E25

The Airport/Facilities Directory entry for Wickenburg.

Well, it’s like this. Right now, at Wickenburg, there is no published noise abatement procedure. Look in the Airport/Facilities Directory and see for yourself. (Try not to notice that the diagram is inaccurate on so many levels.) That means pilots have the freedom to make their own decisions about approaching and departing the airport. We’re not forced to follow some idiotic plan set forth by an ignorant non-flyer in response to noise complaints.

But if Mr. Bad Attitude keeps ignoring the complaints and overflying the same homes again and again, the complaints will get escalated. I’m not too worried about the town doing anything — they’re extremely ineffective when it comes to solving airport-related problems. But eventually, it’ll get up to the FAA. Enough people know it’s not me — a bright red Robinson R44 looks nothing like a little white Schweitzer 300 — so I won’t get in trouble. But the FAA might actually do something to make the complaints go away. Since Mr. Bad Attitude isn’t technically doing anything wrong, the only way to fix the problem is a noise abatement program. The FAA will push the town to make one and we’ll be stuck with it.

What’s also bad is that his continued inconsiderate behavior makes everyone in the helicopter community look bad — including me and the two other helicopter owners based in town. It could cause problems in Wickenburg or other communities for helicopter pilots and operators. It could affect businesses like mine or emergency services. (Come to think of it, one of the reasons our hospital lost its helicopter medevac base was noise complaints. So if you have a heart attack in Wickenburg, you’ll just have to wait an extra 20-30 minutes for help to come.)

And all this is why I care.

In Summary

When helicopter pilots are advised to “avoid the flow of fixed-wing traffic,” that doesn’t mean we should avoid flying in empty airplane traffic patterns. It means we should avoid flying with airplanes.

It also doesn’t mean we should use FAR 91.126(b)(2) as an excuse to become a nuisance by repeatedly overflying noise-sensitive areas.

If there’s no conflicting aircraft, common sense should prevail.

FARs Explained

The FARs in a way an intelligent person can understand them. Maybe.

I was down at Williams-Gateway Airport (IWA) in Chandler the other day. They’ve got a great pilot shop there with lots of books, charts, and real-life pilot supplies. I’d venture to say that it’s one of the best pilot shops in the Phoenix area.

(Side note here. If you’re a Phoenix area pilot looking for a destination for a quick flight, try Willie. The controllers are friendly, there’s plenty of parking, and there’s both a restaurant with excellent breakfast and a pilot shop to give you an excuse for the flight.)

Jeppesen FAR Books

Among the books on the shelves was a series by Jeppesen titled Federal Aviation Regulations Explained. Ah, I thought to myself. Could this actually be a successful attempt to explain the legalese text of the FARs?

Now I don’t really like Jeppesen as a company because of the restrictions it places on suppliers. For example, when I ran an FBO some years ago, none of my pilot supply providers were able to become Jeppesen dealers, so I could not carry Jeppesen products. (Fortunately, ASA products are just as good and I had no trouble getting them.) But I do admit that Jeppesen has products that no one else carries and that their products, in general, are good. It certainly wasn’t worth turning my nose up at Jeppesen and missing out on a good book.

There were three versions of the book, each tackling a different group of FAR parts. One fat book, mostly for private pilots, covered Part 1, 61, 91, 141 and NTSB 830. A slightly slimmer book, mostly for commercial pilots, covered Part 1, 119 and 135. Another book, mostly for mechanics (I think), covered Part 1, 21, 43, 65, 145 and 147.

imageAlthough I would have purchased the first two books mentioned here, the price tag on the first book ($35.95, I think) was a little rich for my blood — especially since I hadn’t actually read any book in the series. I decided to try the series with the volume that I needed most: the one that included coverage of Parts 119 and 135. (My helicopter charter business operates under Part 135.) The cover of the book I bought is different from the one shown here; I think (hope) I bought the latest edition, dated 2005.

Now I don’t want you to think I don’t understand the FARs I’m supposed be be operating under. I do. Mostly. Every once in a while, I stumble upon a rule that I’m not quite sure of. I usually call other pilot friends or sometimes the FAA to get an interpretation. I know enough about the FARs to operate safely and legally and stay out of trouble, although I fully admit that I make no effort to understand the rules that don’t apply to my operation (i.e., rules covering cockpit recording devices, beverage carts, autopilots, and multi-pilot operations). After all, there’s only so much information that can fit into my brain. I’d rather fill it with the information that matters.

Aviation Law 101

I jumped into the book during breakfast at Willie’s Flight Line Cafe restaurant. I basically opened to a random page, paged around until I found a topic that interested me, and started reading. I was immediately reminded of my Business Law 101/102 text book back in college — a big, black volume that stated laws, interpretations, and cases.

So, for example, Page 42 begins a discussion of FAR Part 135.79, which covers Flight Locating Requirements. This applies to my operation, since I’m required to have procedures to help rescuers find me if I make an unscheduled landing and get stuck somewhere — or crash, which I prefer not to think too much about.

First, the book provides the complete text of the paragraph and all of its sub paragraphs. This is the same information you can get in any FAR book or on the FAA’s Web site.

Next, it provides a plain English Explanation of the rule with a few examples of how it might apply.

Then it lists some Cross References to other FARs, the Aeronautical Information Manual (AIM), and Advisory Circulars.

Finally, it lists some Chief Counsel Opinions related to the rule. This is how the rule has been interpreted when challenged in court or other proceedings.

This particular example is pretty straightforward. Other parts are more complex. For those, the book also includes Preamble information and case excerpts associated with the rule. This, when combined with lengthy Chief Counsel Option excerpts, can go on for pages.

I find the case studies and opinion excerpts the most enlightening when dealing with a complex rule. They clearly explain how a pilot did (or did not) get into trouble for doing something (or not doing something) related to the rule and why the situation was (or was not) an issue. At breakfast the other day, I was completely absorbed in the Part 135 applicability regulations, which illustrated how pilots got in trouble for operating Part 135 flights when they weren’t certified for Part 135 operations. It made me very glad I had my Part 135 certificate.

A Good Addition to Any Serious Pilot’s Bookshelf

In all, I highly recommend these books to anyone who is serious about a career in aviation. Written by aviation lawyers, they are equivalent to the business law books I had to read to get my BBA years ago. They tell it like it is and help you understand the rules in a way that a simple reading of the FARs cannot. The next time I’m at Willie, I’ll pick up the first book in the series for my reference library.

You can learn more about the books on Jeppesen’s Web site.

Blogging the FARs: ELTs

What’s required…and what’s smart.

I recently got into a disagreement with another helicopter operator about the requirement for emergency locator transmitters (ELTs).

An ELT is a device that sends out a signal in the event of an unplanned landing or crash. Rescuers can use the signal to find the aircraft. Most ELTs are activated by impact, but they can also be manually turned on, either by a switch on the unit itself or a switch wired into the cockpit of the aircraft. My helicopter’s ELT has impact activation, a switch on the unit, and a switch inside the cockpit.

ELTAn ELT is a piece of equipment you hope you never need, but one you pray is working right when you do need it.

Who Needs It?

FAR Part 91.207 covers the requirement of an ELT. It starts out like this:

(a) Except as provided in paragraphs (e) and (f) of this section, no person may operate a U.S.-registered civil airplane unless–

(1) There is attached to the airplane an approved automatic type emergency locator transmitter that is in operable condition for the following operations, except that after June 21, 1995, an emergency locator transmitter that meets the requirements of TSO-C91 may not be used for new installations:

(i) Those operations governed by the supplemental air carrier and commercial operator rules of parts 121 and 125;

(ii) Charter flights governed by the domestic and flag air carrier rules of part 121 of this chapter; and

(iii) Operations governed by part 135 of this chapter; or

(2) For operations other than those specified in paragraph (a)(1) of this section, there must be attached to the airplane an approved personal type or an approved automatic type emergency locator transmitter that is in operable condition, except that after June 21, 1995, an emergency locator transmitter that meets the requirements of TSO-C91 may not be used for new installations.

This is the FAA’s way of saying that you can’t operate an airplane without an ELT attached unless the flight meets the requirements of paragraphs (e) and (f):

(e) Notwithstanding paragraph (a) of this section, a person may–

(1) Ferry a newly acquired airplane from the place where possession of it was taken to a place where the emergency locator transmitter is to be installed; and

(2) Ferry an airplane with an inoperative emergency locator transmitter from a place where repairs or replacements cannot be made to a place where they can be made.

No person other than required crewmembers may be carried aboard an airplane being ferried under paragraph (e) of this section.

(f) Paragraph (a) of this section does not apply to–

(1) Before January 1, 2004, turbojet-powered aircraft;

(2) Aircraft while engaged in scheduled flights by scheduled air carriers;

(3) Aircraft while engaged in training operations conducted entirely within a 50-nautical mile radius of the airport from which such local flight operations began;

(4) Aircraft while engaged in flight operations incident to design and testing;

(5) New aircraft while engaged in flight operations incident to their manufacture, preparation, and delivery;

(6) Aircraft while engaged in flight operations incident to the aerial application of chemicals and other substances for agricultural purposes;

(7) Aircraft certificated by the Administrator for research and development purposes;

(8) Aircraft while used for showing compliance with regulations, crew training, exhibition, air racing, or market surveys;

(9) Aircraft equipped to carry not more than one person.

(10) An aircraft during any period for which the transmitter has been temporarily removed for inspection, repair, modification, or replacement, subject to the following:

(i) No person may operate the aircraft unless the aircraft records contain an entry which includes the date of initial removal, the make, model, serial number, and reason for removing the transmitter, and a placard located in view of the pilot to show “ELT not installed.”

(ii) No person may operate the aircraft more than 90 days after the ELT is initially removed from the aircraft; and

(11) On and after January 1, 2004, aircraft with a maximum payload capacity of more than 18,000 pounds when used in air transportation.

Our argument centered around the point that this operator uses his helicopter for training, including cross-country flights in excess of 50 miles ((f)(3) above). So under the above rules, it seemed to me that he should be required to have an ELT on board. He argued that the rules applied to airplanes, not helicopters. And although the wording of the rule certainly supported his claim, I couldn’t believe that the FAA would exempt helicopters from the requirement.

So a few days later, while taking my Part 135 check ride, I asked my examiner. Actually, he asked me. And I told him about the disagreement I was having with my unnamed friend — I didn’t want to get him in trouble — and that I thought an ELT was required.

I was wrong. Helicopters are not required to have an ELT on board unless they’re doing Part 135 operations. [Note: The previous edit was made after a reader, Mark from Teterboro, confirmed that helicopters are not required to have ELTs, even for Part 135 operations. Read our discussion in the comments for this post to get the details. Thanks very much to Mark for taking the time to correct this.]

Personally, I think this is nutty. I wouldn’t dream of flying a helicopter some of the places I fly without that piece of potentially life-saving equipment on board. I don’t spend most of my flying time buzzing around a city or the suburbs where someone would notice a helicopter on the ground in their backyard or local park. I fly places where there aren’t paved roads for miles and miles. For example, on a straight-line flight from Wickenburg to Laughlin, NV, I fly over only two paved roads in a distance of 80 miles. And there ain’t many unpaved roads, houses, or even cows under me, either.

But the regs are the regs, so if my ELT broke or simply stopped functioning, I could continue to fly legally under part 91 as long as I wanted to. Would I do that? No.

The Rest of the Reg

Part 91.207 also covers requirements for mounting the ELT, testing it, and replacing its batteries. All of this maintenance stuff should be clearly logged in your Aircraft Log book, just in case someone comes along to take a peek at it — perhaps as part of a ramp check.

It’s another interesting example of how helicopter regulations differ from airplane regulations.

Blogging the FARs: Fuel Requirements

A look at FAR Part 91.151 and real life.

FAR Part 91.151: Fuel requirements for flight in VFR conditions, sets up minimum fuel requirements for flight in VFR conditions. In other words, it’s telling you, the pilot in command, how much fuel must be on board to fly legally.

Here’s the language:

(a) No person may begin a flight in an airplane under VFR conditions unless (considering wind and forecast weather conditions) there is enough fuel to fly to the first point of intended landing and, assuming normal cruising speed:€”

(1) During the day, to fly after that for at least 30 minutes; or

(2) At night, to fly after that for at least 45 minutes.

(b) No person may begin a flight in a rotorcraft under VFR conditions unless (considering wind and forecast weather conditions) there is enough fuel to fly to the first point of intended landing and, assuming normal cruising speed, to fly after that for at least 20 minutes.

What does this mean?

It’s actually pretty straightforward. It’s saying two things:

  • First, it assumes that when you do your flight plan for a flight, you should know how much fuel is required for that flight. For example, if you expect the flight to your first intended landing point (your destination) to take 30 minutes and you burn 12 gallons per hour, that means you’ll need 6 gallons to get to that destination (12÷60×30).
  • Second, it’s requiring that you load additional fuel as follows: If you’re flying an airplane during the day time, you’ll need an extra 30 minutes worth of fuel to be legal; in this example, another 6 gallons for a total of 12 gallons. An airplane at night would need 45 minutes worth of extra fuel; 9 gallons (12÷60×45) in this example for a total of 15 gallons. And a helicopter, which often has its own special rules, only needs an extra 20 minutes of fuel day or night; 4 gallons (12÷60×20) in this example for a total of 10 gallons.

The assumptions here are very important. You need to do a flight plan to know how much fuel it will take to get to your destination. A flight plan should take into consideration wind speed and other weather conditions — for example, conditions that may require rerouting around storms or low-visibility areas. This is related to FAR Part 91.103: Preflight Action, which states, in part:

Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight. This information must include—

(a) For a flight under IFR or a flight not in the vicinity of an airport, weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot in command has been advised by ATC;

By flight plan, I mean a real flight plan. Normally, that involves calculations using a whiz-wheel or handheld aviation calculator or the ever-popular Duats online service (my personal favorite). Looking at a chart and guessing doesn’t count.

What Would a Prudent Pilot Do?

Although I don’t like the phrase “a prudent pilot” — primarily because it was used on me by an FAA person who seemed to suggest that I might not be prudent — it is something to consider here. Using the example above, if you had to complete the flight as planned, would you just take the fuel required by the FARs? In other words, 12 gallons for an airplane during the day, 15 gallons for an airplane at night, or 10 gallons for a helicopter during the day?

A prudent pilot wouldn’t if he/she could safely take more. The limitations would depend on max gross weight; performance at high elevations, high temperatures, or high weight; and weight and balance. Performing weight and balance calculations and checking performance charts is part of the responsibilities of every pilot in command before a flight — that’s part of FAR Part 91.103, too. Remember, you need to “become familiar with all available information concerning that flight.” [Emphasis added.]

Why would more fuel be better?

Do I really need to ask?

More fuel means more time in flight. For me, that could mean the difference between taking an in-flight detour to follow a stream or river that’s rarely flowing or flying the boring straight route from point A to point B. Or the difference between successfully navigating around a fast-moving thunderstorm or having to land in the middle of nowhere to wait it out. Or having to pay $4.90/gallon for fuel at my destination rather than $3.47/gallon at my home base.

According to the 2006 Nall Report, 10.5% of aviation accidents in 2005 were due to poor fuel management — pilots running out of fuel or forgetting to switch fuel tanks. This is sheer stupidity by the pilots — something I call “stupid pilot tricks.” By taking on more fuel than you need, you’ll be reducing the chance of becoming one of these stupid pilots. (You can still be another kind of stupid pilot, though.)

You’ll also have one less thing to worry about in flight.

And if that ain’t prudent, I don’t know what is.

Blogging the FARs: ATC Light Signals

For the first time, it might be something I need to know.

One of the nice things about my helicopter is that it has two com radios: a standard Bendix King KY196A and the radio that’s part of my Garmin 420 GPS.

My Radio Setup

Bendix King KY196AThe Bendix King is my primary radio and it’s wired into some controls on the cyclic stick. This is a neat feature that’s standard on Robinson helicopters. I can program 9 frequencies into the radio and cycle through them all without reaching down for the radio knobs or buttons. Once I get the frequency I want on standby, I simply push a second button on the cyclic to make that frequency active. I’ve got it programmed for all the CTAF (common traffic advisory frequencies), towers, and ATIS (automatic terminal information service) recordings of the airports I visit most: Wickenburg, Prescott, Deer Valley, etc.

Garmin 420The Garmin is primarily a GPS and I very seldom use the radio. It has the ability to automatically transfer the radio frequency for the current waypoint or selected airport to the standby slot, but when I’m flying, I don’t usually mess around too much with the GPS controls beyond simple Go To and Nearest functions. I prefer having a list of frequencies I need for a flight handy and manually tuning them in. A few times, I used the GPS to look up or check a frequency, but that was usually a practice exercise to make me more proficient with the GPS’s airport directory feature. I subscribe to the data card updates and usually have current (or at least recent) data in there, so it’s pretty reliable. It’s also a lot easier than fumbling with a chart while I’m flying. (One of the drawbacks of flying a helicopter is that you only have one hand to work with while you’re flying; your right hand is pretty much glued to the cyclic.) Another cool thing about the Garmin is that when paired with a Garmin GTX 330 transponder and flying within range of Class B airspace, it can graphically display traffic, as I wrote about here.

A nice thing about having two radios is that I can monitor two frequencies at once. This is especially handy if I want to fly between, say Deer Valley and Scottsdale — a distance of about 9 miles — and want to listen to the Scottsdale ATIS while monitoring the Deer Valley tower for instructions or traffic information. In fact, I’m starting to get into the habit of using the GPS’s radio to monitor ATIS and the Bendix King for two-way communications.

Two Radios are Better than One

Of course, the best thing about having two radios is that if one of them fails, there’s another one there to use. And just recently, having two radios became a very good thing.

On a recent flight, while talking to an airport tower’s controller, I heard static in my headset about halfway through my transmission. Turns out, when the transmission turned to static, it also became garbled on the controller’s end. He couldn’t understand what I was saying. But I could hear him and everyone else just fine.

I immediately tuned in the proper frequency on the Garmin, flicked the right switches to talk on that radio, and retransmitted. No problem. So it wasn’t my push-to-talk switch. It was something in the radio.

I had the radio looked at the same day. Of course, the mechanic could not duplicate the problem. And neither could I on my way home.

Don’t you hate when that happens?

Well, the problem has reared its ugly head several times since then. I’ve had another mechanic and an avionics shop look at it. The mechanic couldn’t duplicate the problem. The avionics shop pulled the radio out for a bench test and could find nothing wrong with it. But they did find a mysterious nut (as in hardware) in the mounting bracket. Once removed, the radio appeared to seat better in the console. We thought the problem would go away. But it didn’t.

So I’m left with a radio that receives perfectly and transmits perfectly about 75% of the time along with a second radio that works fine. I’ve taken to talking on the Garmin and listening to ATIS on the Bendix King.

Unfortunately, no one seems to have a spare KY196A for me to swap temporarily with mine. Putting another radio in there and flying with it for a bit would help me confirm that the problem is the radio and not some kind of helicopter wiring problem. You see, if I put in a different radio and the problem goes away, the problem is definitely my radio. But if the problem persists with a different radio in there, the problem is in the helicopter’s wiring or something related. I tracked down a refurbished KY196A, which I can get for a whopping $2,100. The folks there have promised to take it back if the problem turns out to be in the helicopter rather than the radio. So I’ll be ordering it on Monday.

What All This Has to Do with Light Signals

As usual, I’ve turned a short topic into a long story. But it does explain why light signals are on my mind.

If my second radio also decides to stop transmitting reliably, I may be unable to communicate with a tower. That would not be a good thing if I wanted to land at a towered airport.

The AIM (Aeronautical Information Manual) has a procedure for this. (You can find it in Chapter 6, Section 4-2.) The first thing a pilot who has lost communication capabilities should do is turn his/her transponder to 7600. That sends out a signal that says, “Hey, I’m over here and my radio isn’t working.” If you’re lucky, the tower you’re trying to land out has radar capabilities and can “see” you and this signal. The tower will attempt communication and will react according the results.

In my case, I can hear the tower perfectly fine. I can even transmit a little. So the controller would probably work with that and communications would continue, although rather one-sidedly, with me getting instructions and either clicking my push to talk button or speaking briefly to acknowledge.

But if I couldn’t hear a thing — or couldn’t get the controller to understand that I could hear — the controller would take out the light signal gun and point it at me. And that’s when I’d need to know what the signals meant.

I saw one of these light signal guns close up once, on a visit to Chandler tower. It’s a handheld device that they had attached to the ceiling inside the tower. It can display/flash three different colors of light: red, green, and white. The controller points it at an aircraft having communications problems and either shines a steady light or flashes a light. The pilot is supposed to understand what the signals mean.

So what do they mean?

FAR 91.125: ATC light signals includes this useful table:

Color and type of signalMeaning with respect to aircraft on the surfaceMeaning with respect to aircraft in flight
Steady greenCleared for takeoffCleared to land.
Flashing greenCleared to taxiReturn for landing (to be followed by steady green at proper time).
Steady redStopGive way to other aircraft and continue circling.
Flashing redTaxi clear of runway in useAirport unsafe—do not land.
Flashing whiteReturn to starting point on airportNot applicable.
Alternating red and greenExercise extreme cautionExercise extreme caution.

How This Might Appear on a Check Ride

Testing you on your knowledge of this is pretty straightforward for an FAA Examiner. He’ll simply say something like “You discover that your radio doesn’t work as you approach Class Delta airspace. What do you do?”

You reply that you tune your transponder to 7600 and circle outside the airspace until you see a light signal from the tower.

The examiner then says, “Okay, so you see the tower flashing a green light at you. What do you do?”

You explain that the signal means you should “return for landing” or enter the normal traffic pattern.

“You’re cleared to land?” the sly FAA examiner asks innocently.

“No. You need to wait for a steady green before you can land,” you reply, indicating full understanding of FAR 91.125.

To really prepare for this question on a test — and for it happening in real life — it’s a good idea to review the AIM Chapter 4, Section 3-13: Traffic Control Light Signals. Chapter 4, sections 2 and 3 provide additional information for working with Air Traffic Control at an airport. And, if you’re flying IFR (which I don’t), check out Chapter 6, Section 4: Two Way Radio Communications Failure.

Of course, all this might be led up with you explaining what’s required to enter Class D airspace in the first place. But that’s another FAR to explore.

One More Thing

I just remembered that I had a “voluntary radio failure” a while back when returning to non-Towered Wickenburg Airport (E25) from an off-airport location three years ago. If you’re interested, you can read about it here.