Thursday, September 07, 2006

Teach a Pilot to Fish ...

An increasing number of GA aircraft have some sort of traffic awareness equipment, be it installed in the panel or of the hand-held variety. As I've said in the past, this equipment can do a lot to enhance safety when used properly. Thing is, a lot of pilots don't use the equipment very effectively nor do they understand the equipment's limitations.

The idea behind traffic awareness systems is pretty simple: Warn the pilot when another aircraft is getting too close. All of the systems I know of rely on the intruder aircraft having an operable altitude-encoding transponder. Traffic warning systems come in several flavors, the first being ATC's radar. When targets begin to get too close together on a controller's screen, an alarm sounds to alert the controller. I don't know if the controller is also given some sort of visual alert, but many a time I've heard the aural alarm sounding in the background while a controller was transmitting. When I hear that alarm, I get my head on a swivel.

Traffic alerting systems for aircraft fall into four broad categories: personal collision avoidance systems (aka PCAS), Traffic Information System (TIS), Traffic Alert System (TAS), and Traffic Alert and Collision Avoidance System (TCAS). There are actually two flavors of TCAS, but I won't go into it since it's rare to find TCAS installed in smaller GA aircraft.

Personal collision avoidance detectors passively listen to transponder replies from other aircraft and, based on signal strength and the altitude encoded in the signal, warn you when an intruder aircraft is nearby. Most of these units let you set the warning envelope - the radius and altitude above and below - so you're not deluged with warnings in a busy airspace. The early versions couldn't tell you where the aircraft was exactly, just that one was near. One newer unit actually gives you the relative location of the traffic. These units are helpful, but remember that if an intruder aircraft doesn't have an operating transponder that is replying to an ATC radar sweep or some other form of transponder interrogation, a PCAS unit won't help you.

TIS depends on ground-based ATC equipment to feed it information about traffic in your area. Not all areas that have radar coverage support TIS, hence the warning you'll hear from many TIS systems: "Traffic unavailable." The Bendix-King systems actually say "TIS not available." Even if TIS is available, there can be interruptions in the uploading of traffic data. In these cases, you'll see a message that indicates a nearby target is in coast mode - it's no longer being observed for some reason. Maybe the pilot of that aircraft turned their transponder off, maybe their transponder has failed, or maybe they just went below radar coverage.

Oh, and the FAA will be phasing out TIS so enjoy it while you can. ADB-S (automatic dependent surveillance-broadcast) is the service that many think will replace TIS and provide even more features and functions. ADB-S has dramatically improved aircraft safety in Alaska, where it was introduced and tested. The skeptic in me suspects that the reason ADB-S has not become widespread is that they haven't figured out how to charge pilots subscriptions fees for this service. For those of us spending hundreds of dollars each year in GPS, terrain, and obstacle database updates, another subscription fee is just what we need.

Active TAS, like the equipment installed in Cirrus aircraft, will actually interrogate transponder-equipped aircraft. This means that you theoretically have traffic detection even when an intruder aircraft is below ATC radar coverage. A couple of years ago, I flew a Cirrus from Texas to California and was fascinated to see a tethered balloon in New Mexico actually show up on the MFD as a target. Seems this balloon is a downward looking radar unit and apparently it has its own transponder, too. I've also seen targets below the Cirrus I was flying come and go on TAS equipment. My guess is that the intruder aircraft's belly-mounted transponder antenna was being shaded.

And if an intruder aircraft has no transponder, then PCAS, TIS, TAS, or TCAS won't be of any use. This was recently illustrated by the mid-air collision of a Hawker jet and a glider at 16,000 feet near Carson City, Nevada.

My first exposure to high-flying gliders as potential collision hazards came when I was flying from the Black Rock Desert (aka Burning Man) to Reno a few years ago. Cruising at 11,500' in a Cessna and talking to Reno approach, the controller called traffic for me that was a primary target only (no transponder) at an unknown altitude. When I called the traffic in sight, ATC asked if I could estimate the glider's altitude. I said it looked to be about 12,000 feet and added that it appeared to be climbing like a stripped monkey.

One of my new pet peeves is how some pilots respond to an ATC traffic advisory.
Norcal: "Cirrus 123, traffic, 12 o'clock, 4 miles, 3000 feet, right to left, is a Diamond Star"

Cirrus: "We got him on the fish-finder"
What these pilots fail to realize is identifying a target with traffic detection equipment like TIS (Traffic Information System) or TAS (Traffic Advisory System) is not what a controller is concerned with when they issue a traffic advisory. Read Order 7110.65R Air Traffic Control and you'll see that the controller only wants to know whether or not you have the traffic in sight with your eyes. If an aircraft is operating under IFR or in class B airspace, ATC can allow you to maintain visual separation, but again, you must have the other aircraft in sight with your eyes.

A mistake pilots make when using a traffic detection system is they may be hesitant to react to a target that appears to be a threat. If your traffic detection system warns you of an aircraft that you have not been able to acquire with you eyes, then by all means climb or descend or turn to avoid that target. Except for operations in Class B airspace, ATC will provide traffic advisories on a workload permitting basis. If the controller is busy, there's a lot of aircraft to service, or if the controller is being trained by another controller, they may not warn you of traffic that is near you. Even when you are operating under IFR, you are expected to see and avoid other traffic when you have sufficient visibility to do so. So don't be afraid to take matters into your own hands, if necessary, then tell ATC what you're doing and why.

And don't forget to use your eyes, which are often more effective than the so-called "fish-finder."


Ron said...

Oh, man. I despise the phrase "fish finder". It's nearly as bad as the alternative phonetic alphabet some folks make up in an effort to be 'cool'.

Pilot-controller communications suffer enough without that kind of stuff.

Dave said...

Great tutorial John, thanks. With all of the advancements made, I was concerend about how the G1000 system almost forces a pilot to keep his eyes inside. While I'm a skeptic, I'm sure the flashing lights or little vectors can lull one to believe that all is well. Technology is great...up to a point. Thanks for the post.

Colin Summers said...

I say, "We have him on the traffic scope and we are looking." It seems, from interaction with ATC, that they appreciate this additional information. We are looking, and we have a way to track the target a little bit. So, if they are busy, they know they don't need to give us constant updates on the position of the target. They know that we can also make a course correction relative to the target's course, which we can't do without the scope or visual contact.

Obviously, we always call "Traffic in sight."

I admit that I have fumbled out "fish finder" when the words "traffic scope" won't come out. In my head, it's a fish finder because that's what I heard it called numerous times around LA when I was first flying. I've never heard someone complain about it.

Maybe I should say "We have him on Tee Eye Ess."

John said...


The regs require you to alway be "looking for traffic." Controllers I've talked to only want to hear one of two responses to a traffic call:

Traffic in sight
Negative contact

My advice is to keep your communications with ATC short, simple, and clear. You can, of course, use whatever phraseology you choose. But if you're not using one of these two phrases, I think you're just perpetuating a bad radio technique "virus."

Mike said...

When I was in SoCal airspace today on the way to John Wayne, I heard no less than 3 people say "fish finder" when responding to traffic advisories.

Every time I heard it, all I could think was "Who are you, Larry The Cable Guy?"

Sara T. said...

Chuckle! Have NOT heard "fishfinder" before on any of the SoCal frequencies!

Today heard another pilot tell ATC he "had the boggie in sight" - hope he wasn't gonna shoot him down! 8-) Haven't heard that one in awhile.

But I have to admit I've said "no joy" a couple of times for "looking for the traffic"/"dont' have the traffic in sight." This Brit affectation was more popular in ORD airspace than out here, where I've been for 2 years, yay!
Keep up the good work, we need more aviation blogs!