Showing posts with label Air Force. Show all posts
Showing posts with label Air Force. Show all posts

1/27/14

Radar Love

Radio Detection And Ranging, known more affectionately as "Radar," appears to be going the way of dinosaurs and Dodos; replaced by a system of satellites that would deign to look down on the ever changing, challenging and, to me, charming world of aviation. Me and my radar always looked up to that world though. I guess we always will. 

Call it progress, like the days when low frequency radio ranges (LFR) were being replaced by a network of VHF omnidirectional ranges. Sure; the VORs were far more precise but still a long leap of faith for airmen. Or how about the first pilots to descend their planes into thick clouds and/or rain squalls while watching a couple little instruments on the console; ending up relieved and amazed, just 200 feet above the surface, with the runway in sight. They all must have experienced the trepidation of change; as I would over the advent of "NextGen." Fickle though it was, I did love my radar. We worked a lot of planes together, moved millions of people and even saved some lives. We kept each other company during those long, tail-end hours of every mid-shift; when my frequencies were silent and radar's eye saw nothing but empty sky. There were a few brief separations but, as we know, the lack of something we love and rely on serves to intensify our desire for it. I know this to be true and have the gray hairs to prove it. 

I remember the first radar PVD (plan view display) I ever laid my nineteen year old eyes on.  It was inside a Ground Controlled Approach (GCA) radar trailer at the Air Force's Air Traffic Control School. Up till then, I'd never even heard of radar. Learning how to work airplanes from inside a GCA , using a relatively tiny PVD was tough enough when I had no idea what I was looking at. Even so; I felt a stirring of love at first sight. There was an allure to the ceaseless sweep of energy around the scope, the itty-bitty blips it revealed and the glow of the compass rose. Even the little back-lighted knobs used to adjust the display were pure magic to me. They were warm to the touch; like a woman's nipple. Maybe it was just the heat from all those circuits and such behind the radar display but they made me hot.

Unlike the fixed radar antenna you might see spinning at your local airport; GCA units were designed to be moved - sometimes frequently. They have wheels; which means they can be rolled onto an airplane or across the landscape, to end up along the runway of some far away airport. Whether it's a war zone or just another time zone; GCA units make it possible for military controllers to take their old friend Radar along whenever they have to travel.

GCA trailers can also be installed semi-permanently on a large turntable and rotated whenever the wind dictates a change in landing direction. Whether rolled or spun, the unit must be re-aligned whenever it is moved. At my Base, radar reflectors, which looked similar to satellite dishes, were mounted at each end of the runway. Whenever the unit was turned around, the display had to be re-calibrated to align perfectly with the reflector. Chances are the GCA might have shifted a little during the turn but that reflector was always in the same place. They were permanent echos, at a known range and azimuth. Alignment could be tricky but if you didn't do it correctly; the next precision radar approach you conducted could end up heading for the base housing area or worse. The Airman's Club, with all its cold beer, was out there somewhere.

Arriving at Big Time Tower in the early Seventies, I had never seen an ASR-7 display. My first impression? It was huge; like looking at today's flat screen TVs compared to that little portable you once kept on the kitchen counter. And to deepen my love affair with radar; it had been adorned with some dazzling accessories like digital data-blocks that displayed, among other things, each aircraft's callsign, altitude and ground speed. Everything was all wired into a large antenna that spun continuously atop its tower between the runways. Altogether, it did a fine job of helping us guide our traffic into, out of and through Big Time's airspace. Well . . . most of the time anyway. As I said; radar could be fickle.

Those radar scopes needed a relatively dark room. Light, even a modest amount, would bleach out the display; making it nearly impossible to see what was happening. If you came into the TRACON and saw all the lights on; it was either very late at night, when the janitor did his cleaning, or the radar had failed. If the room was quiet, you could assume the former. Assume the latter if there was a lot of noise and commotion. No, the controllers wouldn't be the ones causing all the stir. It would be the shift management. One Supervisor might be talking to a departure sector at the center. "Do you see Lear five eight alfa, ten east of Big Time, leaving seven thousand?" The answer; "Yeah, he's radar. Climb him to twelve and switch him." Another Supe would be pumping one of the radar technicians for answers about what went wrong and how long it would take to fix. Above it all, the Area Manager would be terminating one discussion with the Regional Office and starting another with the Command Center. But how about the controllers? What happened during those first few minutes after the radar quit?

Along each side of the radar room; controllers would sit at their now opaque radar scopes, intensely focused on finding a way out of the Hell that comes with sudden blindness. Just moments before; departure controllers would have been sorting out airplanes that burst off the airport like a fountain display, vectoring them toward their route of flight and handing them off to the enroute facility.

Now the departures, stalled on ramps and taxiways, were stopped indefinitely. This was not the time to be in the tower working Ground Control. At times like this; you were liable to hear the dark side of a few otherwise affable and professional pilots who suddenly found themselves stranded; up a creek without a prognosis.

Approach controllers would have been tweaking their long lines of airplanes; merging, slowing and spacing whatever they had between the outer fixes and the outer marker. Most of their traffic would be in-trail and at the same altitude. Now, the flow of additional traffic from arrival fixes was stopped. Holding patterns were filling up. With a blind eye, approach controllers scrambled to gain some kind of "non-radar" separation between the planes already on vectors to the final approach course. That meant diverging courses, altitude changes for some or, if fortune smiled, visual separation. Anything to keep the planes apart.

Everyone was concentrating - trying to recall what the radar picture looked like in their sector just before it blinked out. At times like this; good flight strip management paid big dividends for controllers. It meant they could still tell who was following who, what altitudes the planes were cleared to, the last assigned speed restriction and maybe even the last assigned headings. Next to radio communications, our flight progress strips were the only other clue as to what was going on just before the radar died.

Some controllers were meticulous about their strip marking and could recover from radar loss fairly quickly. Some tried their best but would get so busy they'd forget to keep their strips updated. Like me; they relied heavily on their habits and past practices to fill in the blanks. For others; strips were merely a distraction that diverted their attention away from the traffic. They were the ones voted most likely to shake, sweat and swear when the radar stopped spinning. Even if the radar was running, problems could arise when it came time to relieve one of those guys. But if the radar was out? Inherit the sector and, for better or worse, you also inherit the outgoing controller's flight progress strips.

My first unexpected radar failure occurred while I was working an arrival sector, in the middle of a moderately flurry of inbounds. My display flickered a few times then, just as radar's eye swept past the 'seven o'clock' position, it went dark. Everyone in the room gasped and studied their strips; hoping it was simply a 'blink' rather than an extended outage. I had seven or eight planes on vectors at the time but there were more coming. Fear, hope and despair kicked in immediately but there was no time to deal with it. I gave my traffic the bad news, advised them that radar contact had been lost then called my adjacent center sector to break the news. They'd have to hold whatever was headed my way. I climbed or descended some of my planes to get a little altitude separation then reached above the console to grab a copy of Big Time's non-radar "cheat sheet." This included a set of maps showing non-radar (pilot navigation) routes from our outer fixes to the approach in use, timed approach procedures, some unpublished holding patterns where we could hide a few airplanes till the dust settled and other information we couldn't remember due to its infrequent need. Everyone on the frequency got a new clearance limit, along with some detailed holding instructions, while we sorted this thing out. I may also have pooped myself but, through the miracle of selective memory, I prefer to forget certain things.

I felt as blind as the radar. With those 'first time' jitters rattling my self-confidence; I began to recall some radar failure horror stories the old timers used to tell around the camp fire - just to frighten us new campers. There was the one about the DC-9 in a holding pattern somewhere, who's pilot took a descent clearance intended for another flight. The plane ended up spiraling down through three or four holding altitudes occupied by other aircraft - in instrument conditions the whole way. Nobody else in the pattern saw or said a thing. The controller only realized there was a problem when the DC-9 reported reaching the altitude intended for another aircraft. Unfortunately, that aircraft was not supposed to be a DC-9. The descent clearance was supposed to be for a DC-8; which was still holding 1000 feet above the altitude now occupied by a death-defying DC-9 driver. Apparently there's some truth to the "Big Sky Theory."

The other popular "scary story" involved a controller running timed approaches from a holding pattern at the outer marker. A light twin engine aircraft had been cleared for the approach and was now on the tower frequency. The next flight to be cleared was an air carrier. Somehow, as if by magic, the air carrier landed ahead of the light twin and without a scratch. I didn't know whether these stories were factual or simply ATC folklore but they haunted me just the same. Left groping for my traffic picture; I kept hoping the radar would come back for me. I loved my radar and was truly sorry for the times I'd cursed its infrequent foibles.

Radar returned in about 45 minutes but we controllers learned long ago to not jump right back into a 'business as usual' operation. Traffic was resumed tentatively; as though we expected radar's recrudescence to be temporary - a sucker play. Our confidence in the system had to be regained before we could get back into the furious radar operation we used to move so much traffic with.

Most controllers have been through an unexpected radar failure at least once in their career. Like sex; they probably remember that first time. But unlike sex; they hope it never happens again. It's just one of those things you do not want to repeat simply for a chance to improve your score.

"We've got a thing that's called radar love.
We've got a line in the sky, radar love."
Golden Earring - 1973
© NLA Factor, 2014


12/5/13

The Persistence Of Memory

Those who've been following this Blog understand it's mostly about memories. In the beginning, I was afraid I'd forget the many things that happened before I could capture them in print. You know, before too much time passed. I now understand those memories are persistent, palpable and perpetual. They're always here with me. I can even feel them. Salvador Dali illustrated it pretty well in his masterpiece "The Persistence of Memory." With apologies to Salvador, I flew an airplane into his painting because, to me, the memories of air traffic have a persistence all their own.

Time, on the other hand, is of no real significance. It comes and goes; preceding each passing second and concurrently vanishing; leaving us with a "now" that is just too short to measure. Thankfully, it does leave those persistent memories of ours behind; scattered across the panorama of our lives.   

As to my life, it seems I spent most of it diligently winding clocks and watches, setting alarms or trying to correct the time if it was running fast or slow. According to the clock; I usually ended up being too early or too late anyway. It took a while but I finally figured out that I shouldn't even bother trying to set, sway, speed or slow the hands of time. The Universe calibrated my clock, then synchronized it to my life - and life isn't measured by hours and minutes. It's measured by events and those events always happen precisely when they're supposed to; which could be described as "right on time." I may never have believed my entire life happened on schedule - but it did. Take the early Seventies for example . . .

Life was moving at the speed of continental drift since my departure from military service. My application for an ATC position, eagerly and optimistically submitted, had apparently vanished into some minor FAA functionary's file drawer. I found an odd assortment of menial jobs to keep me busy. If you're interested, they're described somewhere in the back end of this blog. The work kept me afloat financially but my spirit was being swamped by waves of anxiety. I knew it was crazy but whenever my travels took me past the local airport, I'd glare at the control tower,  mutter a few expletives and shake my head. Frustration brought me to a point where I was seriously considering the idea of going back into the Air Force - just so I could work airplanes again. Looking back on life, I have to love that and every other mistake I almost made.

Living high on the extravagances that a minimum wage income allows, I moved into an affordable efficiency apartment on the north side of town. Although the classified ad called it an "efficiency," I referred to it as the "deficiency." There were so many deficiencies that I lost count half way through the list of health violations. Small, slightly smelly and unnecessarily outdated; it was the kind of apartment where police might one day discover 200 cats and a desiccated corpse. It was affordable though - as long as I stuck to my diet of deviled ham and bananas. I worked onward but could never quite reach my future.

Years passed. In the long run, the FAA did make me a job offer. Ironically, I had to think twice about accepting. By then, I'd worked myself into a pretty well paying and enjoyable job. I even had a better apartment! Going with the Feds would mean an initial (and substantial) decrease in pay. There was also a requisite relocation in the deal. The move would put me in an expensive metropolitan area that I couldn't possibly afford on a GS-7's salary. The offer was a "take it or leave it" deal though. I had one week to respond. That wasn't much time but it didn't really matter. My decision was preordained, so naturally I had to accept. There was simply no choice because, by the end of my Air Force career, air traffic control had become a vital organ that I couldn't live for long without.

I remember the subsequent months being a blur. The only time that mattered was my training time. Then, in nothing but an eight month instant, I found myself checked out through all tower positions and working on my radar certifications. Two years from that first foot in the door, I was fully certified at Big Time. Now that wasn't so hard, was it? Looking back, I'd say no. But back then? Looking ahead was intimidating.

It wasn't long before my first round of mids as a journeyman was scheduled. Trainees were always sent to the tower on mid shifts. But now, as a full performance controller, I could pull TRACON duty. Driving in to work, I knew what I would find when I got there. After all, I'd been home all evening, watching the lightning and listening to the din of heavy rain on the roof. I knew the crew on duty was dealing with a mess and that there'd be plenty left for me and my teammates to clean up when we arrived.

Mids, for me, usually began with a touch of circadian sleep disorder. Failing in my attempt to nap that afternoon, I would arrive at work a little out of sorts, off-balance and unshaven. By 10:45, traffic would normally be light and most of the radar sectors combined at two or three positions. Not tonight though. Walking into the TRACON I saw a Supervisor tearing strips off the printer and running them to the sectors. There were five still open and all were busy. Three of the evening shift guys would be held over for a couple hours to help us put a lid on the madness.

My mid shift teammate relieved both departure sectors and combined them into one. I was told to relieve the Final controller and let her go home. Airplanes that had been delayed at their departure points, some of them thousands of miles from Big Time, were only now beginning to show up at our arrival fixes. It was exciting. The approach controllers talked non-stop and their lines of planes stretched more than 40 miles from the airport. Radar vectors were flying in every direction. At least the bad weather had moved out and the field was VFR for the first time since that morning. After a brief consultation with the tower, I tried cutting some downwind traffic in tight on visual approaches. The first two worked nicely so I told the approach guys to start tightening up the arrival sequence. Everything was going well. The departure backlog was gone by 1:00 AM. Our holdovers from the evening shift left at 2:00 but the persistence of air traffic continued till after 3:00. The mid-shift Supervisor sat silently at his desk; counting strips, calculating the delays and catching up on log entries. In the ensuing years, there would be many more such mid shifts.

In sharp contrast with the FAA; I remember mid shifts in the Air Force being abnormally quiet. Still in the early stages of learning how impossible it was for me to sleep during the day; I'd lumber up the tower steps with my mid shift teammate, moving like a reanimated cadaver. Where I was stationed; most of the military air traffic was down for the night before 11:00 PM, so we'd be greeted by a bored looking NCOIC (Non-Commissioned Officer In Charge) who'd dutifully mutter his way through a review of the tower's daily log. I would dutifully nod with feigned interest in what he was saying. He and his evening shift crew would then rush down the steps as though the fire alarm had just sounded. In a moment, my partner Vince and I would be left in the complete silence of an empty tower cab, overlooking an empty runway. It was on such a night that a most incredible thing happened. My memory of it hangs on like the melted clock on Dali's tree limb.

By 3:00 AM, each of us had pretty well covered what we knew of the latest Squadron gossip and were settling into our chairs, feet up on the console, for a little quiet time (sleep). A light appeared across the airfield, just above the the horizon. It was moving slowly in a northerly direction; almost parallel to the runway and definitely inside our Control Zone. Certain it was a plane without a working transmitter; we simultaneously hailed it on both UHF and VHF emergency frequencies while signaling "Cleared to land" with the tower's light gun. As the craft continued north, we could see there were actually several lights glimmering; like the windows of an airliner's fuselage. But unlike the lights of an aircraft, these were indistinct; almost ethereal. They glowed like pale blue neon.

Curious about any sound this thing might be making, Vince dashed down the first flight of steps and out onto the catwalk. I called the radar unit. Did they see a target just Northeast of the field and moving North? I expected a wise-ass comment about flying saucers in the traffic pattern and I wasn't disappointed. Of course, the radar guys saw nothing on their scopes. After listening to the requisite dose of sarcasm and good-natured ridicule; I was told to leave them the hell alone and go back to sleep. Vince returned to report the night outside was as quiet as a crypt. None of the jet or propeller noise we were used to hearing. Nothing. The strange lights soon vanished over the northern horizon.

Me and Vince had an odd feeling about what had just happened. I picked up a phone and dialed the Watch Desk at our local Center. I was afraid that telling this story to anyone else was a mistake but decided it was worth the risk for a chance to have it corroborated.  The Supervisor, clearly much older and vastly more experienced than me, listened to my story. I could tell he was writing things down and figured he was making notes for a future discussion with our Squadron Commander. I'd be in trouble for sure. But no. He said my description of the object, its low altitude, slow speed and direction of flight matched reports some of his controllers had received from pilots flying across the region. Several people claimed to have spotted it but no one ever saw a radar image.

I remember watching the sunrise that morning, making a fresh pot of coffee for the day shift crew and talking to Vince about what we should do. The Air Force had a reporting program in place at the time. Named "Project Blue Book," it was a way of officially documenting what may have been a UFO sighting. Vince and I concluded there would be no report and no further mention of the incident to anyone; especially the incoming day shift guys. Along with the wry ribbing, we'd likely be labeled as lunatics by the Squadron brass; thus hobbling our chances of ever seeing another promotion. It was decided that what we saw that night must surely have been a weather balloon or another of those spontaneous outbreaks of swamp gas. We just left the tower, lingered over breakfast then moved on to the first open bar we could find. By the third round of beers, we were ready to admit what we'd really seen - but only to each other.

Another mid shift sticks in my memory - one clear and very cold night in the 1970s. A Center controller's urgent sounding voice came across the handoff line. "Hey Big Time, you talking to that guy twenty east of MALYN squawking 4543 at eleven thousand?" It was nearly 5:00 AM and for the last hour or so I'd only been talking to myself.  I saw the target he referred to though, so I pushed the handoff line button and responded. The center controller said he'd been working the plane, a Piper Navajo, for the last 45 minutes but had recently lost radio contact. It was also way off it's planned route, now about 70 miles off course and headed toward some very unfriendly terrain. After checking with the other sectors, it was clear the pilot wasn't talking to anyone at the Center. The controller was now calling all towers and approach controls along the aircraft's flight path. It seemed no one was talking to the Navajo, which was still holding its last assigned altitude of eleven thousand feet. The situation would change but as we know; change isn't always a good thing.

I called the tower and, between us, we transmitted on every frequency we had. No joy. The plane flew on and soon left my radar coverage. It wasn't till nearly 7:00 AM that the Center sector called and told me the plane eventually began losing altitude then vanished from his radar screen. Wreckage was never found and we were left with our theories about what happened. The most plausible one was that the pilot had dozed off - his plane eventually running out of fuel. With luck, he died in his sleep. This incident lodged itself in my memory like a fishhook and became a shot of adrenalin whenever I felt myself getting sleepy on mid-shifts or long drives.

I have so many many memories; some good and others, well, not so good. They don't go away though. They accumulate over a long career and, like my old record collection, become disorganized and eventually take up a lot of space. I've put some of them away in storage but still retrieve them now and then for my own enjoyment. In a way, memories are a lot like my old records. They can both be played over and over again. Someone or something just needs to push the right buttons. Case in point; I recently discovered one of my old teammates from the Big Time days, on a social media site. That pushed some long unused buttons and the memories started playing immediately. Like me; this guy was brutally insane in those days. We shared secrets and experienced many control room tantrums, terrors and temptations together. The memories of them persist, even after all this time.

Time passes. I don't even care where it goes. It takes nothing of mine when it leaves but it leaves me with plenty. Those persistent memories; they stay like my skin color. I don't know exactly where each one is at the moment but, like my old Big Time buddy, I'll eventually find them again. 

© NLA Factor, 2013

9/8/13

Viewing Life Through A Skylight

I recently drove to a little town, several state lines away from home, for a distant cousin's wedding. Apparently I just wasn't clever enough to figure a way out of it. So, after seven or eight hours on the road, I was unpacking the car in a part of the country I hadn't seen in decades. Returning to that area and surveying the familiar southern countryside was somehow comforting. It still seemed to fit me as well as my old Air Force fatigue jacket. 

And speaking of fatigue - I was exhausted from driving all day. The road left me smelling a little like fast food fryer grease and a lot like a high school locker room. I opened the door to my hotel room, dropped the bags on a chair then stretched out across the bed; putting myself to sleep by recalling some of the many memories made nearby - over 45 years ago. They were still fresh as snowflakes and nearly as numerous. Early the next morning, one of them joined me for coffee.

I was sitting on a bench outside the hotel lobby, chatting with another guest, when a sudden, thunderous blast literally stopped our conversation mid-sentence. It was a familiar sound to me, almost like what you'd get by putting a couple bowling balls in the dryer to tumble a while. I listened; smiling inside at something I had not heard in decades. Back then, I wouldn't have paid much attention to it but on this warm, sunny morning, it was like hearing a song that was number one on the charts when I enlisted. It was a blast from my past.

Looking up when I heard an airplane was a reflex acquired through the years but there was nothing to see beyond a hazy morning sky. Still, the unmistakable sound persisted. My fellow early riser looked puzzled. Not me though. I recognized the sound as that of a jet fighter's afterburners - ripping through the serene morning air and echoing off every building between me and the airport. I could even feel the bench vibrating.

I wondered what the rest of this small, southern town though of the noise. There was no military base here - only a civil airport that hosted a dozen or so commercial flights each day. Still, a fighter jet had clearly come calling.

The noise evoked memories of the first time I watched a flight of F-100 "Super Sabers" taking off. It was at an Air Force Base about 75 miles from here. Flame from their after burners was immediately visible. Then, about a second later, the sound reached us in the tower and rattled the windows. It was deafening - even from behind all that glass. The jets rolled forward, slowly at first but rapidly gaining speed as those Pratt & Whitney engines inhaled the cool morning air and exhaled pure fire and thrust. Pilots referred to F-100s by their nickname; "Huns." The planes were also known, less fondly, as "lead sleds." This term was a wry reference to their engine-out glide ratio which, according to them, was slightly better than an anvil, dropped from 28,000 feet. 
In those days there was very little wear on my Air Force uniform and just one stripe on the sleeves. I'd only had the uniform since checking into basic training a few months earlier. Now, fresh out of tech school, I was beginning my career as an Air Force air traffic controller. It was incredible! Assigned to the tower, I worked with several other new recruits and a few senior enlisted men. Some of them had already been to Vietnam at least once. Their professional wisdom, wardship and war stories quickly made me realize this was no ordinary career field I'd gotten into. It was a career that would catapult me across several decades and land me here in this sultry southern town.

As I climbed the tower steps toward my first day in an Air Force air traffic control facility, my pulse rate climbed along with me. It wasn't so much from the exercise but from the increasing weight of insecurity and anxiety over what awaited me. There were three airmen working the control positions and one sergeant watching everything from the center of the cab. His name was Dunton and he seemed to have an angry expression on his face. I soon learned that was the way he always looked. It was rumored to be the after-effect of something that happened while he was stationed at Da Nang but Dunton never talked about it.

I scanned my new world. Below me, the ramp was crowded with jet fighters, transient cargo planes and a handful of helicopters. There were several planes in the traffic pattern and a couple more waiting to go. The atmosphere was nothing like I expected. Tech school left me believing controllers heard one voice at a time and made their uninterrupted response. The reality I had just climbed into was a cacophony of overlapping voices. Everyone worked with hand-held microphones rather than headsets. Each control position had its own speakers; one for each frequency they used. Even calls from the radar unit blared from speakers mounted in the consoles.

Across the airfield, an F-4's left wing dipped slightly just before touching down. It rolled about two thousand feet down the runway then lifted off again. Two of the 'Huns' began taxiing into takeoff position as another pilot called the tower from somewhere in the traffic pattern, I had no idea what was going on but, like other 'first time' experiences, it was memorable. Everyone in the cab was looking in different directions and talking. I stood in the back and took it all in. It seemed no one knew I was there; not even the angry looking sergeant. I was 'there' though and would be there for nearly 35 years.

I recognized Jimmy; one of the guys from my barracks. He was working the Ground Control position. Jimmy turned, gave me a smile of recognition and was about to say something when a flight of four on the ramp called ready to taxi. He turned and looked at me, held his mic out and said; "Do you want to give 'em taxi instructions?" I stared at his outstretched hand like it was a rattlesnake. Talk to a real airplane? I could already feel the rush of panic setting in. This was not tech school and these were not other students posing as pilots. They were real pilots seated in real airplanes and they were waiting for instructions. My throat was closing up. Talk? I couldn't even swallow. In an instant, everything they'd taught me back at Keesler was gone. I took the microphone, along with a very deep breath, and stammered through my first transmission. Dunton looked down at the floor and slowly shook his head. Jimmy grinned as the four jets began moving off the ramp in tandem.   

Moments later, I learned another lesson about ATC that no one ever mentioned in Tech School. Controllers will witness things they may never be able to forget. 

Standing to my left, the Local controller was responding to a call from a flight of F-100s. The tone and tempo of his voice changed abruptly. Moments earlier, they had checked in on a long 'initial' (explained below). They appeared as specks in the sky, some 10 miles from the runway and were instructed to "Report break." A few seconds later I heard one of them exclaim that his engine had just flamed out. Far too low to attempt an air start, the flight leader told his wing man to eject. The reply was that he thought he could glide his plane straight to the runway. "Negative! Eject, eject!" The flight leader's voice smacked of urgency. Both jets were clearly visible now. One was much lower than the other and was descending fairly rapidly. Every eye in the tower was fixed on it. I had no idea what would happen next but noticed Sergeant Dunton lunge toward a red phone on the console. He looked like he'd just bitten his tongue. I saw the plane's cockpit canopy tumble off into the sky, followed by an ejection seat. By the time its parachute deployed, the F-100 had disappeared below a distant treeline. No smoke, no fire; just a plume of dust about two miles from the runway. Above it all, a parachute settled slowly toward the ground; its cargo swinging gracefully below. Everything happened within a minute. 


An HH-43 Huskie helicopter, callsign "Pedro One," was soon airborne and heading toward the crash scene. I listened as the flight leader directed "Pedro" to the spot where his wing man had come down. Maybe 15 minutes later, the 'copter called for clearance to the base hospital. I watched it dart across the airfield; knowing they had the luckless pilot on board. It wasn't until the following day that we learned he'd died from injuries incurred during the ejection. 

Learning I had seen the last moments of this guy's life had a profound effect on me. I couldn't erase the voice that said he could make it to the runway. I couldn't forget the sight of his parachute against the powder blue sky. I was a kid in a grownup's world and had never been exposed to sudden tragedy. There would be more in the ensuing years but the first one made an indelible mark on my memory.

Looking around, I realized I'd spent 18 years knowing nothing of what was going on in the world around me. Even worse was that, at 19, I still didn't. It was as though I'd been viewing life through a small skylight - a sliver of reality where things moved across my narrow field of vision on their way to unseen and completely unimagined horizons. Who knows? An airplane might even have flown by. If so, I'm sure it was going somewhere. But me? I'd been going nowhere. My life, to date, had been self-centered, cloistered and meaningless. So much was happening in the world that I might never have experienced. That was changing though. 

Lost in the good old daze, I hadn't even noticed the guy I'd been talking to was gone. So was the sound of those afterburners; just as 'gone' as those long gone, guileless days of my life. 


"Three-Sixty Overhead" approaches are mainly used by the military. The aircraft makes its "initial ' approach to the runway, at least five miles out, remaining at traffic pattern altitude until over the threshold. At that point, the plane "breaks" left or right, beginning a 360 degree descending turn toward the runway. 


  © NLA Factor, 2013

7/12/13

To Square One And Back

High school left me with very little education and a whole lot of bad memories. When the time came, I hurried through my graduation ceremony then ran off to find the most menial and low paying job a substandard grade average might qualify me for. I got lucky! The job I landed not only met my servility standards and apparent desire for a pitiable pay scale; it was also pretty disgusting work. So this was it; square one of my working life. 

Something happened though. After a few months I began to realize that "disgusting" wasn't as satisfying as it's reputed to be. Quite the opposite. Thus, the arrival of my Pre-induction Notice from the Draft Board actually came as a welcome relief. With my usual low expectations in tow, I traipsed off in search of the nearest Air Force Recruiter.

Volunteer day at Barber's College? Nope.
A few months later, on a sweltering Spring afternoon, I stepped off a bus at Lackland Air Force Base in San Antonio, Texas. I couldn't know at the time but Basic Training would be the prelude to my rebirth from callow youth to air traffic controller.

Within the first 24 hours, we were required to memorize our eight-digit service number. If you don't know; this is the military's "personal identification number." It gets stamped into every GI's dog tags, so that anyone could figure out who we were - just in case we were unable to say. But memorizing numbers was no easy task for a guy who'd eventually have to quickly memorize a traffic pattern sized dose of tactical callsigns and aircraft  registration numbers.

Everybody got the haircut. Then, after the issuing of uniforms, we all began sweating our way through the ensuing weeks of verbal abuse, physical training, close order drill, shooting at things and other stuff contrived to make us appear almost military. But we were still just kids; only now with guns and no hair.

Somewhere along the way, we were all asked to pick from a list of jobs we'd like to spend the next four years doing. I wondered which one required the least amount of skill - like, for example, shaving the heads of basic trainees. I studied the list methodically, as though I actually understood what I was looking at, while never really correlating my eventual choice with a post-military career or its earning  potential. As I saw it, being asked to choose a job was like asking me to choose which color of bus I'd like to drive over a cliff. It simply didn't matter. I just knew the end result would be the same - a long fall onto the rocks. Bewildered, I finally settled on ATC, although I had no inkling as to what the job entailed. It didn't sound too disgusting though. In fact, it sounded interesting.

After selecting the career we hoped to get and after working through a series of aptitude tests and interviews; someone would make a decision on our fate. There were no guarantees. Assignments were based mainly on the needs of the Air Force.

Basic training plodded along. Then, in the final few days before leaving Lackland, our big moment came. All graduating Airmen were marched into an auditorium, where a sergeant stood holding a clipboard full of papers. As names were called, someone in the crowd would yell "Here!" and the sergeant barked out their next duty assignment. His papers were arranged alphabetically, so I had time to appreciate the queasiness in my stomach. I watched him flip through them, one by one, never looking up. Finally, in his very military, staccato voice; "Factor! Air Traffic Control - Keesler Air Force Base, Biloxi, Mississippi!"

The sense of elation I felt at that moment was misguided and premature. There'd be trouble ahead, and plenty of it. Nonetheless, here I was; about to begin my Air Traffic Control technical training. Here I was; about to land on square one again.

Biloxi in those days was a sad looking town; worn away by years of Gulf hurricanes and off duty GIs. Not originally from the deep South, I didn't know what to make of it. I was now in a place where black folks stepped off the sidewalk to let me pass - neither of us ever making eye contact. It was a place where nearly every bar in town was on the Base's list of off-limits establishments. Everyone carried that list because off-limits establishments were the only bright spots in a Biloxi night. The beaches were the only bright spots during daylight hours; when you could appreciate how dreary the town looked. Littered with broken glass and the aluminum pull tabs from countless beer cans, you either wore flip-flops on your feet or you wore bandages. The only other places to be were in the barracks or attending class. But that was no fun.

When I arrived in Biloxi, our involvement in the Vietnam War was on the upswing. The Air Force needed lots of air traffic controllers. In response, Keesler ran the ATC school in three shifts. Mine was the 6:00 PM till midnight shift. At the appointed time, my class would meet up in front of our barracks and march across the airfield to a converted hanger that housed the classrooms. There were several courses; each one lasting about a week and acquainting us with certain aspects of the job. As I recall, the first block was titled "Weather." From there, we went through instructional blocks on aircraft recognition and flight characteristics, Federal Air Regulations, Airport Traffic Control, Mobile radar units (known as GCA Units) and Approach Control. I may have forgotten some but it's been a lot of years since then.
GCA Units at ATC School, Keesler AFB
One day, sometime around my fourth week of class, the trouble caught up with me. I was called into the lead instructor's office. My grades were a perfect reflection of my off duty activities, which never included studying. That's because one of my barracks buddies had a car and that car was our means of touring the off-limits bars after class. We had to be careful though. Bed check occurred around 1:30 AM. So, after some guy with a flashlight came around and peeked into our rooms, we all tiptoed out of the barracks, met up at the car and headed for town. I should have noticed my ATC career disappearing in the rear view mirror of that big Chevy Impala but was always too caught up in the excitement of what might happen next.

The lead instructor was a chubby, red faced Tech Sergeant who didn't look much older than I was. He could turn a phrase though; describing a sad mental picture of my future. It was a bleak picture that included failure and peremptory reassignment to one of the Air Force's more servile and, very likely, disgusting jobs. There, I'd serve out the remainder of my enlistment with no hope of promotion. In other words; back to square one again.

I had indeed driven the bus over a cliff. Or maybe I was the second steer in line at a slaughterhouse and suddenly realized I was about to become dead meat. I gulped, groveled and grew penitent. I pleaded and promised. For an 18 year old kid with low self-esteem, very little sense of responsibility and no vision for the future, the threat of a long fall from a short career was just what I needed. Staring, once again, into the face of failure was a strong motivator. I went back to my barracks and began studying for the next test; knowing I wouldn't be seeing much more of my drinking buddies and even less of those buxom Biloxi barflies. I wouldn't be seeing much more of those nauseating, daily hangovers either.

Graduation from ATC school brought more anxiety.Where to next? Vietnam? I wondered; would they send a controller with no actual ATC experience to Vietnam? Then I realized that most of the people over there, the ones pulling triggers and dropping bombs, had no prior experience either.

Marched into another auditorium with another hard-assed sergeant holding a clipboard, I was about to get an answer. Wherever I ended up; I would arrive there as a new kid, with only a superficial understanding of what air traffic control was all about. I knew I'd be working in a real control tower though, with a crew of real controllers. Everyone would watch me carefully, train me candidly and eventually evaluate my fitness for the work. On the day I picked ATC off the Air Force jobs list, I had no idea what I was getting into - but things were a little different now. Now, at least I was smart enough to know how little I knew. I had also passed the ATC course; a fact that boosted my self-confidence level from zero-sum up to some. This would be another beginning for me; another step back to square one and another step in my long adventure.

I've since made a lot of trips to square one and back. By now, I know the way without some guy with a clipboard shouting orders. Just don't ask me for directions. Eventually, we all find our own way.

© NLA Factor, 2013

3/5/12

Reflections In A Fun House Mirror

This is how they look to us ~ but what did they really look like? 
This is all we have to go on . . .
Criticism. Its astonishing, but most people I've known didn't like criticism. It seems those who did only abided it as long as they weren't on the receiving end. As controllers, we got used to it. We had to. It was just one of those professions where, somehow, everyone else knew of better ways to do it than we did. They could take an inconceivably complex system of rules, technology, techniques, human factors and other intangibles, then oversimplify it all the way down to one short phrase like "You could have done it better." Translation: "You should have done it my way." 


Sometimes the critics would try to mollify their appraisals and proclamations by calling it "constructive criticism" or something more trendy like "feedback." Whatever. As long as it was purely verbal, you could either let it get under your skin or roll off your back. But what if it was a written critique? And what if that written critique was widely read by people who never actually had first hand knowledge of the performance in question? If that written critique was all they had to go on; is it possible they'd be looking at a virtual "fun house mirror" that might have intentionally or inadvertently distorted some critical realities? Did they know or even care to know what we really looked like? Once upon a time . . . 

There was no irony like being chewed out by a First Lieutenant who knew even less about air traffic control than me; a naif of an Airman Third Class who, just months ago, graduated from Tech School, smelling like the bottled beers of Biloxi. I felt like a guy who'd finally memorized the first four letters of the alphabet ~ being yelled at by some jerk who could only make it from A to B. But John, our baby-faced Flight Facilities Officer was putting his heart into it.

Listening to John, you'd have thought he actually separated airplanes for a living, rather than the papers in his file cabinet, which he could barely separate alphabetically. Well...he had some higher ranking officers to impress. Across the room sat two Colonels in flight suits, holding pens and clipboards. As they made their way through the list of grievances they'd accumulated that morning, John nodded in solemn acknowledgment of our alleged errors and oversights ~ glancing grimly at me and a few other guys from the tower and radar unit. I thought he was probably attempting to look like the Captain he wished he'd been promoted to by now. In reality, he just looked like a Lieutenant with a migraine ~ a condition also known as "controllers."

Bob, our fearless FAA Air Traffic Representative (ATREP), sat next to John but his gaze seemed to be fixed on something outside the window. As the two Colonels droned on about their morning's experiences in our traffic pattern, there was a sudden thud of afterburners lighting up at the runway. Their sound rattled windows in the small, stuffy, mausoleum of a Flight Facilities Office where we controllers sat sweating ~ eyes glazed over like sad corpses. The noise jolted me. I glanced at old Bob and guessed he was recalling the sound of Viscounts and Super Constellations running up on the long forgotten taxiways of his propeller powered controller days. He hadn't worked airplanes in at least a decade but was, nonetheless, our resident windbag ~ or "expert" if you'd prefer. Bob had seen these kinds of meetings many times before. He knew how to tune them out and could afford to do so. In my callow mind though, I'd been envisioning my eventual court martial, reduction in grade and transfer to the base Supply Squadron. Well at least my agile imagination was able to escape this dreary gathering, even though the rest of me couldn't. I sat, listening to the afterburners rumbling across the airfield, then fading away in the distance. Life flew on without us.

So, who were these two malcontent Colonels? Looking back, I'd have to say they were envoys from my future.

They were pilots. There was an entire squadron of them. I think they were based at Scott Air Force Base in Illinois. From there, they'd fly off to visit all the stateside Air Force Bases. Every once in a while, their flight plans would bring them to our little slice of Paradise, where they would spend a couple airborne hours evaluating our level of service, proficiency and adherence to regulations.


Referred to among the ranks as a "Service Eval," we controllers weren't supposed to know when they were coming. From their standpoint, the whole process was more effective if it was a covert and candid peek at the way we operated. To maintain anonymity as long as possible, their flight plans were filed using the aircraft tail number rather than a tactical callsign. The inbound was called in to the tower by our Base Operations as something like "Air Force 70561, a T-33." We got a lot of T-33 traffic, so when an inbound was called on one, we'd always check "the list."

The list was a sheet of paper taped to the back of our base regulations manual. On it, we recorded the tail numbers of every known Service Eval aircraft to have ever visited the place. It was our secret and whenever an unlisted T-33 was revealed to be a Service Eval, we added the aircraft's tail number to "the list." Even though Service Evals were rarely a surprise, knowing they were coming never reversed any one controller's bad day or deterred us from making enough stupid mistakes to prompt a meeting.

Service Eval missions were always flown in T-33s. That way, the front seat could fly the airplane while the back seat handled radios and made copious notes. They'd usually start the evaluation by working the radar unit for a while; requesting at least one precision and one surveillance approach; perhaps even a no-gyro. Their trick was to intentionally deviate off the final approach course or glide slope ~ just to measure the controller's corrective reflexes. Maybe they'd pretend to lose their radios (NORDO) to see how quickly the controller picked up on it.

Once they had sufficiently exercised the radar guys, they'd switch over to our tower frequency. From their subsonic perch in the traffic pattern, they grilled us on phraseology, procedures, base regulations and anything else they figured might throw us off our game. They might even ask for a DF steer or two. The whole thing made me nervous. After all, this was the U.S. military ~ the same guys who, less than a year ago, had yanked me out of my comfortable civilian life. We were even at war! This added up to some serious shit for a twenty year old. I stammered and stuttered like Porky Pig whenever I had to handle these guys.

F-100 Super Sabre Cockpit
Of course the entire exercise was about quality control. The Service Eval was a necessary tool, albeit somewhat intimidating and sometimes nerve-racking. Most of the aircraft we worked were high performance, single seat fighters like the F-100. Compared with today's Air Force inventory, these airplanes were temperamental antiques equipped with the relatively primitive flight controls and avionics of the day. To fly one of these things, especially solo and in instrument conditions, had to be difficult enough. The pilots who flew them didn't need the added challenge of dealing with a clumsy or incompetent air traffic control facility. But then, what pilot does?

Generally, we did a pretty good job but knew the Service Eval pilots would probably find something to squawk about anyway. It was their job. I suspect they had their agenda, just like the folks who evaluated us during my FAA years. The Agency used several different approaches to quality control checks. Some were done by facility personnel while others were done by other offices. Most were insulting but a few were purely insufferable.

There was the "Tape Talk" program. This was an internal check which would have fallen into the "insulting" category. Here you had a specialist from the Training Department making tape recordings of controllers while they worked a particular tower or TRACON position. The recordings, which included all radio and landline communications, were made remotely and, more importantly, in secret. Controllers never knew they were being taped for an evaluation until well after the fact. First, someone from the Training Department would listen to the tape, noting specific deviations and providing applicable references to local and/or national directives. When that step was complete, everything would be sent to the controller's Supervisor, who would schedule a one-on-one review. Forms verifying this review would be signed by both parties, returned to the Training Department then filed away for future reference.

This kind of review was not well received by controllers or their Supervisors. There was a note of hypocrisy tacked to the idea of being critiqued by a Training Specialist who had already lost much credibility simply by taking a staff job. Adding to the insult was the possibility this particular staffer may not have been the most able or procedurally correct controller himself before landing that office job. I was shocked to learn that some controllers bid on staff jobs because they just couldn't deal with working traffic anymore. Even more shocking? They often got the job. Anyway, there sat the Training Specialist ~ passing judgment on his peers, making entries in their training records and occasionally grinding axes over former coworkers. Does hypocrisy smell worse than criticism? You betcha.

Another means of internal analysis was known as an Over-the-shoulder (OTS). Only mildly annoying, the process required a supervisor to plug in with his or her controller and monitor the sector for an hour or so. Since the OTS was performed by a Supervisor, it was about as credible as that particular Supervisor was. Equity was another problem here. Objectivity in this kind of evaluation was often influenced by interpersonal relations. If a particular Supervisor and controller were good friends or that controller was highly regarded by others, some deficiencies might be overlooked. Conversely, if a Supervisor and controller did not work or play well together, the OTS could be merciless. As always though, forms would be completed and notations made in the controller's official Training Record.

We also had what was known to us controllers as a "spy-in-the-sky" kind of evaluation. Generally insufferable, these were performed by someone from the Air Traffic Evaluations Branch, riding in the jump seat of an air carrier. On a typical cross-country flight, they could monitor several facilities and literally dozens of controllers ~ collecting data all the way. At Big Time, we never knew what hit us until the letter arrived from our Regional Office. In it were specific dates, times, control frequencies and alleged infractions. This, of course, triggered a mandatory internal investigation, follow-up and a written response to The Region, addressing each of the evaluator's assertions.

Whether we agreed with them or not, our air traffic service, like any other service, needed an occasional appraisal. No doubt it was necessary for the FAA to take quality control measures. We all knew there were weak links and signs of complacency in our facility. Sometimes we could rectify them ourselves but sometimes the issues called for added emphasis by way of outside intervention. The Air Traffic Evaluations Branch, or "Evaluations," as we referred to them, was there to provide such intervention. An FAA Headquarters organization; their primary mission was to perform periodic assessments of air traffic facilities ~ much like the old Air Force "Service Evals" did. But they had one additional tool that could look much deeper into a facility's internal workings and it wasn't always with an unbiased eye. This was known as a full facility evaluation.

By far, the most deprecating of them all, this variation on the evaluation called for sending five or six specialists in to examine all aspects of a facility's operation. They'd arrive like ants at a picnic, crawling into everything and looking for anything they could chew on.  Working from a lengthy checklist, team members scrutinized all things operational and administrative. Some monitored controllers working tower and TRACON positions while others picked through local directives, training programs and record keeping.  The general appearance of the facility was noted and critiqued. One-on-one interviews would be conducted with controllers, supervisors, union representatives and administrative staff. They'd even interview non-FAA entities on the airport, such as airline representatives and airport management. We thought we looked good. Not a hair out of place. But that was just the way we saw ourselves.

Briefings would be given to the facility's office staff each morning, updating them on what problems the evaluators had found so far. There was also a final "out briefing" when the evaluation was complete. During these briefings, Management might hear some things they didn't agree with. While it was okay to poke and probe a little, it was never a good idea to dispute their appraisals too strongly. That could be as risky as dumping bullets into a blender. It might get noisy and, even worse, someone's career might be mortally wounded. How's that you ask? When these guys got back to their own office they'd write a lengthy final report, with copies sent up the chain to our Regional Office and Washington Headquarters. By the time that happened, it would be way too late for us in the field to influence the situation.

That report was the image FAA's hierarchy saw. What they didn't see were the hundreds of airplanes flowing safely in and out of Big Time each day. They didn't see the controllers and Supervisors making it all work. They didn't deal with the equipment problems, workforce and user complaints. They didn't have to expend scant staff resources or piss on each other whenever someone in the Regional Office yelled "Fire!" A full facility evaluation, not unlike the other ways of assessing air traffic control, was often stained by preconceptions, bias and subjectivity. Truths could be shaped, stretched or twisted and new "truths" could be forged out of nothing. Big Time would eventually be boiled down by bureaucrats ~ reduced to several thousand words on a couple dozen sheets of paper. That's what the big wigs sipping coffee in their corner offices saw. It's all they had to go on. They couldn't tell what we really looked like.

The Final Report - on a short, fat family?
There might be better ways to evaluate an air traffic facility's performance but, at the time, these were the best tools we had. Irritating but essential, exaggerated, underrated, nerve racking but necessary. The alternative would be a free-wheeling ATC system where problems and deficiencies would only be brought to light by system users, whistle blowers or the National Transportation Safety Board. Oh, the news media might attempt to make an erudite observation now and then but the picture they'd portray wouldn't be much more accurate than the one above.

Which is the accurate image?
Even an aberration can contain some measure of truth but I'll always wonder . . . If it was somehow possible to inhibit the distortions, agenda-driven bias, preconceptions and misconceptions normally brought to our facility evaluations; what would we have really looked like? I guess we, as the ones being looked at, didn't ever know for sure. We had our own ideas about how we thought we looked ~ how we hoped we looked and how others wanted us to look. In the final analysis though, I guess we ended up looking like what other people elsewhere read about us. It's all they had to go on and, unless they worked at Big Time, they might have been looking at a distorted image. So . . . what did we really look like? Is there any way to know? It starts by trusting your gut feeling.

There are a few likely indicators that a facility's reflected image wasn't a pretty one. If you're interested and not too busy working traffic, you might notice them. Is the Manager unexpectedly "selected" to participate in a special project at The Region or Headquarters ~ then subsequently replaced? Does he or she abruptly announce their retirement? Perhaps one or two of the staff Managers are offered a "career enhancing detail" somewhere else and you never see them again? Don't be too concerned. It's just life in the fun house. 

© NLA Factor, 2012

1/31/12

Airway Facilities & Abilities

Sometimes I dream in VFR ~ only to awake amid rapidly deteriorating conditions. Why am I always surprised? Pilots and controllers know full well that clouds can conceal some pretty nasty twists, so we should also recognize that even the most ideal flight conditions might take an unexpected turn against us. In perfect VFR weather though, we're not always as mentally prepared for problems. Favorable conditions, complacency and high expectations are powerful drugs. They could make me so high that unforeseen troubles and the subsequent emotional plunges would result in harder landings and longer recovery times. When those nasty twists occurred at work, I was always thankful for those who could step up and somehow clear the air. If the twist involved one of the many tools of our trade, I was thankful for the technicians of our Airway Facilities staff.


Late 1970s, early November. It was one of those days when the idea of going to work really energized me. From the first morning cup of coffee to that last post-shift bottle of beer, life was going to be good. When I met up with my carpool buddies, I could see they were equally anxious to strap on their headsets. As we sputtered onto the main highway in Carl's slightly out-of-tune Beetle, everyone bubbled enthusiastically about the great weather. Winds were light, so the airport would most likely be running on our optimum runway and airspace configuration. Visual approaches would rule the day and there'd probably be very few departure restrictions. In other words; it looked like we were in for a high volume, happy to be here, whipped cream kind of shift. We knew it was going to be smooth, sweet and a hell of a lot of fun!

When Carl's VW finally skidded to a stop in the facility parking lot, everyone clambered out and peered over at the airfield. As expected, things were looking good. Aroused by the possibilities, we started our brisk walk into work. Carl was so excited that he didn't even notice the Beetle's right front tire was going flat. Neither did the rest of us. We wouldn't discover that till shift's end, when it would be referred to as the last straw.

Arriving at the facility's secure entrance, someone swiped their badge, punched a code into the keypad and the four of us hurried, in tandem, toward the sign-in log. Unlike most evening shifts, I was actually hoping for a tower assignment. Conditions were perfect for watching airplanes and Big Time's lofty tower cab was the place to do it. I really needed some tower proficiency time anyway, and a "CAFB" day like this was the best way to get it. I just needed to convince Pete to send me up. That wasn't going to happen.

Entering the TRACON we immediately noticed something different about it. But what? There was still the usual cacophony of control instructions, the hollering back and forth between sectors and, of course, the cigarette smoke. Actually, there was a bit more smoke than normal. It was so thick, in fact, that I couldn't tell whether it was coming from the ashtrays, the equipment or both. Still, there was something missing from the continual din of our musty, timeworn radar room. I noticed an abnormally large group of people standing at our Flight Data position. That's when I realized what was different. The incessant chatter, usually emanating from our Flight Strip printers (FSPs), was missing. 

There were three printers mounted at the Data position. One printed the arrival and overflight strips, one printed departure strips and the third machine was a spare.  Under normal circumstances, the arrival and departure printers ran nearly non-stop. Sounding like a chorus of teleprinters, they banged out new and amended information controllers would need on traffic entering or exiting their airspace. 
Sample departure strip from a little aerodrome in Texas.
Strips would be slid into plastic holders and disbursed to the appropriate radar sector. This particular afternoon though, in the smoky chaos of the pre-evening rush radar room, they sat like cinder blocks ~ stone still and silent. There was, however, another ominous noise coming from the Data position. It would be the sound of those deteriorating conditions I mentioned earlier.


What met our ears sounded less like an ATC facility and more like a call center in the basement of some desperate and acutely confused telemarketing company. I heard one controller muttering; "Yeah . . . yeah . . . uh huh. What was the airway after Falmouth?" As he spoke, he was writing on a flight strip. Two other controllers stood at the data console; each one scribbling frantically on blank strips. A couple of Airway Facilities technicians wearing worried faces brushed quickly past me. They were pushing a cart piled high with parts and tools. That was the moment when I realized this was not going to be a "whipped cream kind of shift." It was going to be some kind of nightmare. Imagine your Sunday paper not showing up on the doorstep. Maybe a wheel fell off the kid's bike? Who knows. So the phone rings. You pick up the receiver and a guy says; "This is The Gazette calling with your Sunday edition. Are you ready to copy?" You scramble for a pen and several large pads of paper. That kind of nightmare.

For some reason, the whole scene made me think of my old Air Force roommate William.

The old AFCS patch
I lived in the barracks during much of my Air Force time. It was a building that controllers, radio and radar technicians, plus many of the other enlisted troops who had jobs in the Communications Squadron called their home. The place was more like a college dormitory where everyone wore uniforms for half the day. The rest of the time was usually spent in civilian clothes, planning and executing forays to any of the many bars and clubs that thrived outside the base perimeter.

 William, my first roommate, was a freckled redhead from central Pennsylvania. A radar technician ~ he was one of the guys who, armed with a selection of scewdrivers and diagnostic tools, kept our aging GCA unit operational. The two of us shared a bathroom, ate at the same table in the chow hall and trekked across the base together when it was time for work. I'd often find voluminous technical manuals strewn around our room; each opened to a schematic of one of the many systems he maintained. William studied a lot and I admired him for it. After all; two or three chapters in just one of his books were thicker than the entire Air Traffic Control manual I kept, mostly unread, under my bunk. He and the other guys in his shop were all that stood between us controllers and the huge pain in the ass of a radar failure.

Ground Controlled Approach (GCA) Unit
There were several technicians in my squadron. Their areas of expertise covered radios, radar, telephone equipment and nearly everything else a controller needed to get through the day. Some of the techs even maintained our VOR and TACAN sites. We had no idea what they did between equipment outages and didn't really care. As long as someone showed up when something broke, we were happy . . . very happy.

Although the pilots in our Base's fighter wing flew the most advanced aircraft in the Air Force's inventory, our ATC equipment was fragile, antiquated and capricious. Somehow though, our techs kept everything running fairly well. They saved our asses nearly every day and, for that, we regarded them as peers and partners in the mission.  Still, during those after-hours forays into inebriation, we'd rib them mercilessly and they'd do the same to us. The truth was that every Air Force controller I knew had the highest regard for those guys. We'd lie for them, trade countless rounds of drinks in the local gin mills and, when they transferred out, we'd lament their departure. Years later, I would discover a kind of caste system in the FAA that placed Airway Facilities (AF) personnel a few notches beneath the "Air Traffic elite." It seemed AF existed solely to support us and, in the opinions of many, that could only be done from below.

Standing in that late afternoon TRACON, with three inoperative strip printers, I could hear frenetic muttering coming from the Flight Data position as controllers hand-copied flight plans, subsequent amendments, GENOTs and other data from the Center. Information on departing flights would then be relayed to the tower, by phone, where another controller had to make a copy for Clearance Delivery, Ground and Local Control.

I could also hear an undercurrent of dissatisfaction and mild contempt coming from controllers seated at the approach sectors, like "What the hell is the point in having a spare printer if those idiots can't keep it working?!!" They were writing their own arrival strips by using information from the alpha-numeric data on their radar displays. This was a time-consuming and annoying distraction that only intensified as the evening rush of inbounds began creeping toward the outer fixes and the airplanes needed more and more attention. Although we had Handoff positions, where someone could sit next to the radar controller and write strips, they were rarely staffed. Today was no exception. There was a lot of angst and anger in the air, and it was all being directed at the Airway Facilities technicians who just couldn't seem to get those printers running.

Those damned printers, among the most plain and plebeian pieces of equipment in our inventory, were major labor-saving devices. As with most things, we took them for granted until something went wrong. Then we wondered why such a basic device couldn't either be fixed quickly or replaced. In this case though, replacing any of them wouldn't have helped. None of the three devices were working and we were far beyond the quick fix time frame.

More problems emerged. The extra manpower needed to make calls and write strips was wreaking havoc with the break schedule. Guys were working well beyond the desired two hour limit on their sectors and people were getting testy. Arrival restrictions had been imposed on all surrounding facilities and departure delays were beginning to mount. Phones kept ringing at the Watch desk but no one was there to answer. The TRACON Supervisor kept glaring at those technicians ~ expressing his frustration in any way he could without interrupting their work. Outside, the sun was setting on what should have been a perfect day for working airplanes.

By now, a Data Systems Specialist had joined the group huddled around the inert printers. He was talking to his counterpart at the Center. Apparently the issue was not a mechanical malfunction after all. It took an hour or two of disassembling and diagnosing but someone finally determined that Big Time's printers were actually in fine working order. They were simply not receiving data from the Center's host computer (from which all our flight data originated). It would later be discovered that someone using a backhoe, many miles from the airport, had inadvertently ripped up the cable that connected Big Time's FSPs with the Center. Repairs would take more hours than we had left on our shift.

The two AF techs vanished but the mayhem continued. We kept making calls, writing strips and working airplanes. A few controllers were asked to stick around for a couple hours of overtime. I felt bad for those AF guys. They had been the focus of much derision for several hours but took no exception to it. Understanding they could do nothing more to help, they packed up quietly and went back to their office. Nobody apologized to them and no one thanked them for their trouble ~ myself included. By the time they left, I was too busy arguing with a Center controller about the spacing between two arrivals.

The shift finally ended. Walking out of the facility, I felt sluggish, like I was wading through quicksand. A mild breeze wafted the smell of jet exhaust across our path as we four carpoolers trudged toward the parking lot. Feeling pretty deflated by events of the last eight hours, nobody had much to say. All we wanted to do by now was have a few beers and head home to bed. As we neared the lot, it looked like the right front wheel of Carl's Volkswagen had rolled into a pothole. When we realized the tire was flat, we were relieved to learn that Carl had a spare. He popped the trunk lid, only to discover the spare was also deflated. Feeling fairly flattened ourselves, we were almost too tired to figure this thing out.

Although sympathetic to our plight, none of the other guys in the lot were headed in our direction. They were   also as anxious as we were to get home. In less than five minutes, we were all alone in that lot, glaring at the useless tire in the same way we had glared at those AF techs earlier in the day. Then we started glaring at Carl. There was a difference though. Unlike our AF guys, this was a situation that Carl could have prevented from happening.  He muttered something about "the last straw," then started walking back to the tower. There, he was able to borrow one of the mid-shift guy's car keys. We grabbed the VW's spare tire, threw it into the trunk of a blue Ford sedan and sped away from the airport.

It was oppressively quiet in that Ford until we got to Carl's place. Climbing out of the car, I reminded the others it was my turn to drive tomorrow ~ making a mental note to check my spare tire.

Here's the epilogue. As a Supervisor dealing with an equipment problem, I'd sometimes have to go looking for the AF guys if they didn't answer their desk phone. The search eventually took me to one of the facility's equipment rooms. Along with radio and telephone switching equipment, they kept tools, spare parts and a lot of broken things in there. It looked like a shop that repaired pocket watches, refrigerators and old television sets by interchanging the parts. 


A wiring diagram for the Great Pyramid?
Of course there were also the ubiquitous stacks of technical manuals; one or two of which were usually opened to a page of schematics. To my brain, they might as well have been hieroglyphics. Either was equally undecipherable. I could neither walk like an Egyptian or talk like a technician but was glad to know someone actually understood the stuff. While us controllers got through the day largely on our quick wits and aggressive decision making ~ these guys had to study constantly, work unerringly and go off for weeks of additional training whenever new equipment came on line. And they did it to support us. You just had to love 'em.


I should add a few lines about how we in Air Traffic could place the AF staff squarely in the middle of our own internal issues. Anyone in air traffic supervision knew that all equipment required periodic checks and preventive maintenance (PM). If such checks were not performed within prescribed time intervals, the particular piece of equipment would lose its certification. That meant we couldn't use it again until it was re-certified. For example, a tech might arrive at the Watch Desk one morning and ask us to release an ILS system for three hours of PMs. It would be up to shift management to approve it or not.  Sometimes existing conditions (weather, traffic volume, etc.) made approval unwise or impossible. Sometimes though, a technician's request was denied solely because that Supervisor and/or that team felt they needed every security blanket they could keep in their clutches ~ thus foisting approval and associated impacts onto another team. I believe the popular euphemism might be "Kicking the can down the road?"


Eventually though, AF would have to take that system down or be in violation of maintenance timetables. They weren't about to let that happen. If a situation ever got to that point, Air Traffic would lose their right to refuse. Think of it this way. You miss that 36,000 mile service mentioned in your car's owner's manual, simply because you didn't feel like turning the car over to some mechanic for a day. The "Check Engine" light eventually comes on and your car immediately shuts down ~ no matter where you are or where you're going. Even worse; it won't start again until you get that servicing done. The rules made PMs a kind of technical time bomb that would eventually go off if not disarmed in time.

© NLA Factor, 2012