|
fly alaskaA Close Call |
by Jay Kelley First published in the on-line AOPA magazine in their "Never Again" feature copyright 2002 AOPA Even though this incident occurred almost 30 years ago, the lesson learned is as important now as it was then. Had I been flying a faster aircraft, I might not be here today. With 1800 hours total time, I had been hired for my first charter flying job by an air taxi company in Fairbanks, Alaska and had been flying for them for several months. Single engine IFR was still legal under FARs part 135 in the mid 70's. My mission for the day was to fly three round trips between Fairbanks and Bettles. I would be transporting three Cessna 207 loads of construction workers who were finished for the season and were really glad to be heading for home. Bettles is well north of the Arctic Circle in the southern foothills of the Brooks Range about 200 miles northwest of Fairbanks. The weather was IFR, but with a gradually rising ceiling throughout the day. It was mid-autumn and getting dark early. My first two round trips were uneventful solid IFR flights on NDB amber airways with an ADF approach each time into Bettles. There was no icing or turbulence. The approaches, to well above minimums, were normal and relatively easy. On my third and final trip of the day, it had gotten dark. I shot the ADF approach, landed in Bettles and picked up the last five men. I filed an IFR flight plan for our return to Fairbanks and we took off. Fairbanks was by then reporting 4000 overcast and 30 miles (actual visibility was probably more than 100 miles) with winds light and variable. We climbed to the assigned altitude of 7000 feet and headed for Fairbanks in the dark through solid stratus clouds. It had been a long day, and I was tired but still alert and looking forward to being done. After flying almost everyday for months including winter blizzards and obscurations, I had become somewhat complacent about important details of each flight. I was flying on instruments and not really paying much attention to our location over the ground. I couldn't see the ground at night in the clouds anyway, and besides I knew that at any given time we were a certain number of minutes from Fairbanks. The route, a straight line from Bettles to Fairbanks, passes over several ridgelines and small mountain ranges, but at 7000 feet there was ample terrain clearance. About 20 minutes or so out of Fairbanks, we were cleared to descend to 4000 feet. We broke out of the clouds right at 4000 feet and there at what appeared to be about 15 to 20 miles in the distance, were the lights of Fairbanks and the Fairbanks Airport. I was a little surprised to be so close in, but thought no more of it. I informed approach control that we had the field in sight and they cleared us to descend at pilot's discretion for a visual approach. I began a gentle cruising descent with the idea of arriving at the final approach altitude just a few miles out from the airport. I turned on the landing light, my usual practice when approaching Fairbanks from any direction at any time of the day. (The Alaskan pipeline was under construction at the time, and there was a lot of traffic in and out of the Fairbanks Airport. We all used our landing lights when coming and going from the airport.) The lights of the city and the airport did not seem to be getting closer as quickly as I expected them to, but I dismissed this thought and continued my cruising descent. Suddenly, with the lights of the city still visible straight ahead of me, there were trees dead ahead being illuminated by the landing lights. I pulled up sharply and cleared the ridge top I had almost flown into. The guy in the co-pilot's seat looked at me and said, "I'm glad you did that." Needless to say, I had not been expecting to fly into the ground with the lights of the city still showing in my windshield and my altimeter reading 2700 feet, but it had almost happened anyway. Had I been flying a faster airplane, I might not have had enough time to react and pull up. There were a number of factors at work leading me into that ridge top. I was fatigued. I was complacent from months of flying with almost no time off. But the optical illusion of the situation is probably the most significant factor. This illusion has two aspects to it, the first being the apparent closeness of the bright lights of the airport and the city. I later realized that my original estimate of 15 to 20 miles out was way-off wrong, and that we were probably 40 or more miles from the airport when we descended out of the overcast. I have since noticed that distant lights on a night with really good visibility appear to be closer than they really are. There is a second and more insidious illusion. As the pilot descends toward
the airport, the lights appear to remain at the same angle and in the same spot on the windshield. This visual
reference, without the benefit of other visual cues, gives the pilot the false sense that there is nothing to run
into between the aircraft and the lights. This dangerous illusion can be illustrated with a simple diagram: It is important, when making a visual approach at night in good visibility, to know of any terrain still in front of you which is higher than the lights you're descending toward, especially when the only lights you can see, are the ones you're heading for. This kind of near disaster is less likely to happen in populated areas where there are lights on the ground along your route, but still possible. In my near disaster, the landing lights saved us. It is important to monitor the rate of descent and to correlate it with altitude and distance remaining to the airport. It is important to be especially vigilant when tired. Flying professionally day in and day out doesn't relieve a pilot of the responsibility to be on top of the situation at all times. Complacency can spoil your whole day. I almost learned this lesson the hard way. JOIN |