Gage FSS, Oklahoma

Gage FSS photos are requested

The following remarks regarding Gage FSS personnel were submitted by a very grateful pilot.

“My hats off to the FSS specialists at the Gage Ok facility in cira. 1982. I was in a military T-41 (similar to C-172 with no pitot heat) IFR flight from Lajunta, CO to Barksdale AFB in Bossier City, LA. I was in the clouds at 8000 ft and began picking up rime-ice very rapidly. Long story short, the pitot system froze thereby losing the airspeed indicator, as well as my windscreen icing over. I declared an emergency with en route center and they gave me a heading to nearby Gage OK (KGAG) that had an NDB approach.

I was by myself and had a pad of NOS approach plates and was trying to maintain flight and find the Gage NDB plate. A brief look at the plate and turbulence caused the approach plate book to close and fall on the floor. I thought the NDB beacon was on the airfield and after descending to MDA did not see the field and called missed approach and started a turn back. At that time the FSS told me they were DFing my VHF radio transmission and showed me still 3 miles from the runway.

I immediately turned back on final approach heading and continued on to find the runway and land. I taxied up to the FSS building and they came out to meet me. They (and I) couldn’t believe the amount of ice on the wings, and stabilizers as well as the propeller spinner which had a 9″ cone of ice shaped just like the spinner. Leading edges had 4″ of ice; they began taking pictures as they hadn’t seen an aircraft land with that much ice!
I most definitely had God as my copilot, and Gage FSS personnel as my guardian angles! Thanks to the many dedicated specialists….”

Los Angeles Mayor Sends Letter to New York, 1926

April 17, 1926
The mayor of Los Angeles sent an oversized letter to the mayor of New York City proudly stating it would cross the country in just 30 hours. This was only possible without the new lighted airway system. Once the new lighted airway was in place, that same letter that used to take 83 hours took just 33 hours to get from New York to San Francisco.

Flight Service History 1920-1998

By John Schamel

This page contains a brief history of the FAA Flight Service Station, written by John Schamel, a Flight Service Specialist.

The evolution of Flight Service from the aviation support facilities of 1920 to the present Automated Flight Service Station mirrors the remarkable growth of aviation during this century. In fact, today’s modern Air Traffic Service (ATS) has its origins in those original stations. The following is a brief account of that evolution.

First Radio Station
Click to view enlargement

The United States military entered the aviation arena during World War I, an episode in history that was instrumental in demonstrating the versatility of the newly invented airplane. During the war, a variety of tasks for military aircraft were tried, one being a venture with the U.S. Post Office. In May 1918, the first air mail route was established between New York and Washington, D.C., with other short routes in the eastern states following. The Army turned the operation over to the Post Office in August 1918, transferring all the equipment and personnel. As Air Mail routes slowly expanded, work was started on the transcontinental route. This ambitious plan called for a 2,612-mile route from New York to San Francisco, complete with the 17 primary landing fields having an Air Mail Radio Station (AMRS). The transcontinental route opened on August 20, 1920. All 17 AMRS were operational by the end of 1921. The AMRS specialist made local weather observations, obtained other weather information by radio, and often made their own forecasts. They also assisted in loading and unloading mail, servicing the airplane, and maintaining their own equipment, often building their own radios.

Mail Plane
Transcontinental route from New York to San Francisco, opened August 20, 1920

The passage of the Air Commerce Act on May 20, 1926 brought a variety of aviation-related tasks under the control of the Department of Commerce. The Transcontinental Airway System was transferred from the Post Office to the Bureau of Lighthouses. 

Salt Lake City Air Mail Radio Station, March 1925

A new organization within the Bureau – the Airways Division – took over in June of Air Commerce.jpg (76952 bytes)1927. By this time there were 45 radio operators working at the renamed Airway Radio Stations (ARS).

Radio Operator

Early specialists were primarily former maritime radio operators. They were well experienced in building, maintaining, and operating radios for long periods with little or no assistance. These radios used point-to-point telegraphy using Morse Code — known as CW (Continuous Wave) — to communicate with other ground stations. CW was used for air RadioTelegraph_small.jpg (2090 bytes)ground communication until voice radios were developed.

Early Radio Operator

CW was not phased out of the air traffic system until 1948. Weather and aeronautical information was passed along the routes from one station to the next. The standard Morse Code gave way to shorthand methods as radio traffic increased. First Phillips Code was used, which was later replaced with “Q” calls. Many of the “Q” calls are still used in the computerized systems of today.

Radio-telegraph 1925.
The radio-telegraph position in a 1925 Airway Radio Station, featuring both 
hand and semi-automatic sending keys

Standardized air-ground voice radios became available in the early 1930s as more aircraft became radio equipped. Teletype was introduced to the ARS in 1928. One circuit was available for all traffic, which included message traffic for other government agencies. A second circuit was added later, allowing weather information to be separate from flight information and administrative messages.

Burley Radio, Idaho 1930’s.
In the early 30’s, the technician took care of teletype and radio equipment at stations 
like this in Burley, Idaho

The station keeper’s duties remained pretty much the same. Service wasn’t limited to just mail planes, though. Any pilot stopping at or calling the ARS could get weather information or make a position report. Search and Rescue duties were added to look for overdue aircraft. Specialists still did their own technical maintenance on radios and teletypes, and often maintained the airport’s lighting aids.

Pilots of the era came to rely on the dedication and professionalism of the station keepers, the pilots’ only contact with the air traffic system. This reliance would continue, even with the addition of airport control towers in the 1930’s. Tower controllers were specialized in that airport environment. The ARS controllers still provided the majority of services to pilots nationwide.

The continued growth of aviation lead to the Civil Aeronautics Act in June 1938, creating the Civil Aeronautics Authority (CAA). The CAA took over many of the functions from the Department of Commerce and the ARS became the Airway Communication Station (ACS). Skilled technicians were assigned for maintenance of the electronic equipment in the system. The basis of the Airway Facilities System was formed in the years before World War II

Airway Technician.
Airways maintenance technician, “Dusty” Rhodes takes a break alongside his sector truck in the late ’30s.  Unlike their modern counterparts, the airway station keepers of 40 years ago were required to wear distinctive uniforms on the job

With the U.S. entry in this war, the military became the main customer of the ACS. Women joined the controller ranks, with some facilities staffed by only women controllers.

The end of World War II marked the return of commercial aviation. ACS controllers provided services to private pilots, airline pilots, and military pilots. New and improved radio navigation aids helped speed the growth of flying across the nation.

Haines FSS, Alaska.
Chief Albert (Whitey) Machin (left) and Carl Shute (right) at work in the Haines Flight Service Station, 1945/1946.

The rapid growth of postwar aviation lead, in part, to the Federal Aviation Act in 1958, merging the CAA and other organizations to create the Federal Aviation Agency (FAA). The name Flight Service Station (FSS) was unveiled in March 1960.

Flight Service controllers continued to provide a variety of services to pilots throughout the nation, however, they were limited to simply reading weather reports and forecasts verbatim.

Buffalo Radio, New York.
U.S. Airways Radio Station, Department of Commerce Radio Station WWAB was located in Buffalo, NY.  The Station held the call letters of WWAB until 1961

An agreement was reached in 1961 between the FAA and NWS. Flight Service controllers were trained as Pilot Weather Briefers and could summarize and interpret weather charts and reports. Pilot weather briefings could be obtained by phone or air-ground radio from any FSS. Improvements in weather services, aimed at reducing weather-related accidents, gave more tools for the FSS controller to use. Flight planning services continued to grow. The FSS became “general aviation’s operations office.”

The Federal Aviation Administration came under the Department of Transportation in 1967. The FSS system continued to grow slowly compared to the rest of the air traffic system. Because of a series of fatal accidents in the 1950s and early 1960s, emphasis was placed on upgrading radio, radar and computer equipment in en route centers and towers. Flight Service continued to work with the teletype systems originally built in the 1930’s.

Washington Flight Service after recent modernization in 1969

Considering recommendations from the Civil Aeronautics Board and National Transportation Safety Board, a new program was initiated in 1972. Its aim was to reduce weather-related general aviation accidents. It started on the West Coast at four stations – Los Angeles, Oakland, Portland, and Seattle. It was known as EWAS — En Route Weather Advisory Service. Specially trained and dedicated controllers provide pertinent, current weather information to airborne aircraft. After a very successful test period, it was implemented nationwide with only a minor name change — En Route Flight Advisory Service (EFAS).

Wichita Falls FSS, Texas. 1970

Flight Service also led the way in another important area in 1972. In June the National Association of Air Traffic Specialists (NAATS) became recognized as the first national air traffic labor union. The NAATS/FAA contract was the first nationwide collective bargaining agreement in the FAA’s history.

During the 1970’s the Flight Service Automation System (FSAS) was conceived. Increasing traffic loads demanded a more efficient way of doing business. Two automation systems were field-tested. MAPS (Meteorological and Aeronautical Presentation System) was installed in the “new” Washington Flight Service at Leesburg, VA. Two other stations were closed and consolidated into the Leesburg facility shortly after it opened. These were the first in a long series of automation consolidations. AWANS (Aviation Weather and Notices System) was installed in the Indianapolis and Atlanta Flight Service Stations. Other stations experienced upgrading of teletype equipment. A CRT-based system — Leased Service A System (LSAS) and later Leased A and B System (LABS) – replaced the familiar yellow paper and forest green mechanical equipment of the teletype system in most stations.

FSS Improvement.
A faster, more accurate flight planning program was tested in the early ’70s at the FAA’s National Aviation Facilities Experimental Center (NAFEC) in New Jersey

The best features of both MAPS and AWANS were blended together to form the “Model One” FSS system. The first Automated Flight Service Station (AFSS) was commissioned at Bridgeport, CT on March 3, 1984. 60 more AFSS’s followed over the next few years. Changing technology and funding modified the original plan that called for three various systems to be phased in separately. By the late 1980s, though, it was obvious the original plan was not feasible. A new system, the Operational And Supportability Implementation System (OASIS) is the blueprint for FSS into the 21st Century.

From a high of almost 400 Flight Service Stations in 1973, the system has shrunk to less than 100. Most are the AFSS ‘super stations’. On September 30, 1997, the non-automated stations at New Bern and Hickory, NC were closed. Those facility closings marked the end of the FSS Consolidation and Modernization Program that had been started in the 1970s.

McAlester AFSS, Oklahoma.  1998.
McAlester Automated Flight Service Station, Oklahoma, 1998

This quotation, from an article marking the 50th Anniversary of Flight Service, is just as appropriate today as it was then:

“Their day-to-day work is not as dramatic as it once was, nor as widely appreciated by the public, since they do not direct or regulate air traffic.”

“But nevertheless they are the persons most pilots rely on for flight planning data, for guidance over unfamiliar terrain, for steady reassurance when they get into trouble. The men and women who staff the stations haven’t lost any of the dedication of those early pioneer station keepers who helped bring aviation out of its infancy.”

About the author …

John joined the FAA in 1984 and has been an Academy instructor since 1991. He taught primarily in the Flight Service Initial Qualification and En Route Flight Advisory Service programs. He has also taught in the International and the Air Traffic Basics training programs at the FAA Academy.

History has been an interest and hobby since childhood, when he lived near many Revolutionary War and Great Rebellion battlefields and sites. His hobby became a part time job for a while as a wing historian for the U.S. Air Force Reserve.

John’s first major historical project for the FAA was to help mark the 75th Anniversary of Flight Service in 1995.

Huron, South Dakota 1991-2001

A personal history of Huron FSS written and submitted by Jim Anez, Huron Flight Service Station

I went from the manager’s position at Pierre FSS to Huron AFSS as Plans and Procedures specialist (PPS). I was one of 3 staff specialist (the others being Training and Quality Assurance) who established many of the procedures as the facility became fully automated. In 1994 I went back to the controller work force because I was 3 years short of time required to be eligible for retirement at age 50. When I did this the other specialists indicated they wanted me to be the union Facility Rep so I joined NAATS and was elected as facrep. When my term as NAATS rep was up, and I had my “good time” in, management asked if I would consider moving back into a staff job. I agreed without thinking that the job title was now “Support Specialist”, it was the only staff position, and it encompassed the duties of the PPS, Training and Quality Assurance (QA). It worked out well, I liked the work, and one of my proudest moments was in 2000 when the facility received a perfect score on a full facility evaluation. I retired in November 2001 and moved to Washington State.The Huron AFSS flight plan area in 1991 was all of South Dakota except for the Aberdeen, Pierre, Rapid City and Watertown airports. By 1994 the facilities at other airports were closed and Huron was responsible for the all airports in the state.

AIRCRAFT LOST, CONFUSED, IN DISTRESS OR WORSE?

This guy was REALLY lost
I came into work one evening at 2200. During shift turnover I noted that we had a Cessna 150 on a VFR flight plan due shortly at Custer, SD in the southern Black Hills. Not much later the pilot called on the Rapid City VOR to advise he was on the ground Custer and we closed his flight plan. The other specialist and I had a short discussion about the call because we weren’t really aware that we could talk to aircraft on the ground at Custer… but he’d called us, so we decided it was just “one of those things”.

Then we got a call from the pilot’s wife. She advised that she was at Custer and wondered about her husband’s ETA. We advised that he’d just landed. She said that she had been at the airport for a while and for sure no one had landed.

Before we had time to digest that the pilot called on the radio to say there was no one around and he was supposed to meet his wife. We told him she’d called and was at the airport. He assured us there wasn’t a soul around and it’s now past sunset and getting dark. We still couldn’t understand how he was talking to us from the ground in Custer, but since he was we asked him to give us his bearing off the Rapid City VOR. When we laid this out on the chart the line ran directly over the Custer airport and there were no other airports anywhere near that bearing.

Since it was obvious he wasn’t at Custer, but had landed on a paved runway that wasn’t charted, we were stumped. We asked him to look through the buildings and see if he could find anything to identify where he was. He found some boxes with a name and address on them. We somehow got a phone number for that person, in Nebraska, but that she knew nothing about airports in South Dakota and couldn’t even understand why a package with their name on it would be in the Black Hills. Meanwhile the pilot reported that he could see a north-south highway with a fair amount of traffic to the east below him. This sounded like US93 and confirmed that he was on the east side of the Black Hills somewhere – but didn’t help much.

Fortunately it was a pleasant summer night so we didn’t have to worry about the pilot’s well-being but he was concerned about the aircraft battery. We arranged for him to call every 30 minutes while we tried to puzzle out his location. I called the sheriff’s office to see if they knew of any paved private airstrips in the general area on the east side of the Hills west of highway US93. They advised there was a quarry in that area but there were no landing strips, especially paved ones.

The next time the pilot called we asked if there were any tractors or trucks around, thinking that if it was the quarry there should be some equipment. “Oh yeah,” he says “there are all kinds of trucks”. So we asked him to get a license plate number, which we then passed on to the sheriff’s office and they called the owner.

It turned out that there was a 500’ paved runway for radio control aircraft at the quarry site and that’s where our pilot had landed. We asked the sheriff if they would go out and rescue the guy, and that was the last I heard about the event.

I wasn’t there for this one, just heard about it and presume it’s true
A specialist was working with a pilot who was uncertain of his position. He was fairly close, but for some reason they weren’t having any luck with NAVAIDS. The specialist asked the pilot if he saw any railroads, highways, lakes or rivers. Yeah, he said he saw a road and he was following it. The specialist asked did the pilot see any signs. Yeah, he saw a sign. The specialist asked if he could tell what it said. Sure, the pilot says, the signs say “Do Not Litter!”

Navigation problem or pilot problem
A student pilot enroute from Sioux Falls to Huron (Sioux Falls is about 80 miles SE of Huron) became overdue. This was pretty much the middle of our flight plan area so we started checking airports and calling for him on all frequencies. He finally answered on the Flight Watch frequency and I think we concluded he was about 100NM WSW of Huron. Using our directional finder (DF) and pilotage we got him headed in the right direction and he finally landed. In discussing the situation it sounded like his directional gyro wasn’t working right but we couldn’t understand how he could be so far off course, and so far away and not know he was lost.

So, because it seemed like he had a hard time holding a heading we suggested that he should watch for the interstate highways to make sure he didn’t miss Sioux Falls. I-90 runs E-W through Sioux Falls and I-29 runs N-S through Sioux Falls. So we told him to turn south if he crossed the N-S interstate and turn east if he encountered an E-W interstate.

Again he came up overdue so we started looking for him and found that he had landed at Yankton, SD – 40 miles SW of Sioux Falls and 45 miles south of the interstate!

Off planned route
I was working a pilot briefing position one afternoon and took a call from a pilot in Mobridge who was planning a flight to Billings. There was poor flying weather forecast south of his route but based on his planned departure time it looked like he should get to Billings well before the weather moved across his route of flight.

It so happened that I had rotated to the radio position by the time he called to activate his flight plan so I talked to him again when he departed. A short time after the activation he called again to advise that he’d returned to Mobridge because a door had popped open. His final call, not too much later, was to advise he was again airborne and reactivated his flight plan.

As the afternoon became evening we received a notification from Great Falls AFSS that the aircraft hadn’t arrived in Billings. The flight became overdue and search and rescue procedures were implemented. Eventually the aircraft wreckage was located on the east slopes of the Big Horn Mountains in northern Wyoming which was well south of the planned route. The aircraft had gotten into an area of restricted visibility after dark and flown directly into the mountain. Investigators were at a loss to understand why he was so far south but radar data was retrieved and it appeared that the pilot had intentionally flown west southwest after departure possibly to do some sightseeing.

Pierre, South Dakota 1989-1991

A personal history written and submitted by Jim Anez, Pierre Flight Service Station

In the spring of 1989 I moved from the supervisor’s position at Watertown to the manager’s position at Pierre FSS.

The Pierre flight plan area was approximately the central third of South Dakota. After the Huron AFSS was opened this area shrank greatly.

PEOPLE AND THINGS

Trust me
Most of the specialists at Pierre FSS had been there for quite a while when I got there. They knew their jobs and, in most ways, did them well, so I didn’t have any big issues to deal with. Automation was starting to take place and prior to my arrival, computer monitors had begun to replace teletype and paper.
The facility layout limited the options for placement of the monitors, but I felt that there were some obvious improvements that could be made. I didn’t want to come across as the “new guy changing everything” so, during a facility meeting, I asked for ideas. It seemed to me that anything would be an improvement, and that employee buy-in was more important that a perfect solution.

After a few weeks of getting no suggestions, I proposed that we make the changes I had in mind. The response was lukewarm and I got the idea that specialists weren’t crazy about changes but they didn’t want to argue.

When completed the changes were well accepted. One of the specialists even told me he had thought of the same thing even before I came to the facility. I asked him why he hadn’t suggested the change when I asked for input. He told me that the previous manager had often asked for input and then either ignored it or belittled the suggestion, so the guys just quit participating. They didn’t believe I was serious about wanting their input to make working conditions better.

After that we had a very good working relationship and were able to make some positive changes and improvements.

Congressional inquiry
Not long after I got to PIR I was informed there was an inquiry from one of the state’s Congressmen about my selection as Facility Manager. One of the specialists in the facility had bid on the position and apparently a local pilot thought he should have been selected and complained to the Congressman. This specialist and I always had a really good relationship and, in fact, when I left the facility he became manager.

After I’d been there about a year I was visiting with a local pilot and he told me he’d filed the complaint but that after seeing how things were going he needed to apologize. I let him know that I was in no way affected and he need not worry about it.

Watertown FSS, South Dakota 1985-1989

A personal history written and submitted by Jim Anez, Watertown Flight Service Station

I was selected as the Area Supervisor at Watertown FSS in the fall of 1985 but because of staffing, couldn’t leave Huron immediately. I traveled to Watertown one day each week during the last 3 months of the year. We didn’t actually move from Huron until after Christmas in 1985. The Huron Facility Manager was also the manager of the Aberdeen and Watertown FSS facilities, so in many respects I had the autonomy of a manager without the title. I had 5 to 7 specialists during the time in Watertown but worked some shifts to cover leave and illness. I and a couple specialists from Watertown took turns for almost a year traveling to Aberdeen on weekends to cover shifts so the supervisor and specialist there could get one or two days off.

The Watertown flight plan area was in the northeast corner of South Dakota and a few airports in western Minnesota.

WEATHER ISSUES

This gal did good
I was working a Saturday day shift. It was an unseasonably warm and sunny but a windy spring day with winds gusting into the mid-30 knot range. A lady called from a Cherokee asking for an airport advisory and advised that she’s on a student cross-country. There was no traffic, but I remember being mildly surprised that a student would be doing a cross-country with the kind of winds we were getting.

She landed uneventfully and taxied to the FSS ramp. When she came in she was in tears and was trying to tell me that she had gotten lost, was overdue on her flight plan and just didn’t know what she was going to do.

She wasn’t on a flight plan to Watertown so I presumed she must really be lost, but when I asked for details it turned out that Watertown was the first leg of three and her flight plan destination was the next location where she planned to land. So, she really wasn’t overdue… she was running late and all we needed to do was adjust her ETA at the flight plan destination. That made her feel a little better.

The next issue was that she said she’d gotten lost. When I asked her about this I learned that when she realized she didn’t know where she was she’d spotted a small town, descended enough so she could read the name on the towns water tower. Then she climbed back to altitude, got her chart and plotted a new course for Watertown. I told her I could not think of any better way to do it than that and she should be proud.

So, she left, much happier than she arrived.

But as I watched her on her takeoff roll she just didn’t seem to be able to accelerate and she aborted the takeoff. She taxied back to the end of the runway and tried again with no better results. This time she taxied back to the ramp, and when she came into the Flight Service she said the plane just wouldn’t develop any power and called her flight instructor.

A couple of hours later her flight instructor and husband flew into Watertown in another aircraft. She flew home with the instructor, and her husband flew their plane home.

A couple of weeks later, on a much nicer day she flew in again. I asked her what had happened and she said they weren’t exactly sure, but thought it had something to do with the fuel. They were burning auto gas and thought it was a cold temperature blend, and because it was such a warm day the fuel wasn’t burning properly. She said her husband got the plane home, but it hadn’t run well until he got closer to home and temperatures dropped into the 50s.

PEOPLE AND THINGS

The Vice President
For some reason Watertown got a lot of attention during the primary races leading up to the elections in 1988. We had 3 different presidential candidates visit, but the one I remember was George Bush. He was vice president at that time so had Secret Service protection. About 10 days before the visit the Secret Service came out and did a facility study. Then a few days before the visit a team came in and installed all kinds of radio and telephone equipment. Because the facility manager was in Huron I had worked in the main facility office. We had another office that really wasn’t used for anything (I think it technically belonged to Airway Facilities). The phone company installed a bank of phones in the spare office for the press and my office was designated as the “safe room” in case they needed to get the vice president inside.

The morning of the visit they brought in a bomb sniffing dog and went through the entire facility. They also physically looked through every drawer and filing cabinet in my office, then kicked me out. At one point some law enforcement guy asked the dog handler if he could pet the dog. The dog handler, an Air Force sergeant, said, “Sure, if you don’t mind losing the hand.”

After Bush got back from wherever he’d gone while in Watertown, he made a little speech out on the ramp to a group of 50 or so people right outside our operations room widow. It was cold, probably between 0 and 10 above with a stiff breeze, and the thing that impressed me, more than anything else, was the secret service detail standing in front of the group in their light weight overcoats, totally motionless except for their heads turning as they scanned the crowd. It could have been 72º and sunny out there for all the discomfort they showed.

After Bush’s plane took off all the extra equipment was gone in about 2 hours!

Money means different things to different people
Watertown FSS was a “temporary” part-time facility operating from 0600-2200 (in this case “temporary” had gone on for about 12 years). One evening I was working when the commuter airline agent come to our end of the building and told me that there were a couple of guys in the terminal waiting room. They were there to pick up a passenger from the last flight of the evening but the passenger has missed his flight and was going to charter a plane to fly him to Watertown. She was ready to close the terminal and wondered if they could come to the FSS area to wait. No problem.

While visiting with the guys waiting for the aircraft I learned that the reason the passenger missed his airline connection was because he was in the bar drinking and missed hearing the flight call! About 10 minutes before closing time the charter flight called in. I gave him an airport advisory and told him that although I’d be discontinuing FSS operations before he arrived I’d wait for his arrival since his passenger’s friends were waiting in the FSS, and it was cold outside.

The aircraft arrived and the passenger was a loud boisterous “big city” type of guy. He thanked me profusely for waiting. He wanted to give me a “tip” for my trouble and tried to hand me a $5.00 bill. I told him I couldn’t take it but thanked him. He insisted I take it and I insisted that I couldn’t. His friends finally told him they should just go as I’d been nice enough to stick around and they were holding me up. As they were gathering his stuff I noted that he’d just left the five dollar bill lying on the counter. I went over and picked it up to give it back to him and realized that it was a $50.00 bill!!!!!!!

I gave it back to him and after he left I asked the pilot if he’d seen that the guy wanted to give me a $50…. he said “Yeah, he gave me $100.00 when we got out of the plane.”

The Wild West (South Dakota style)
When I got to Watertown there was a female there in training. She’d had a pretty sheltered life – she’d grown up in a big city in Ohio and attended private girls’ schools – high school and college. One Easter she brought hard boiled eggs to work and revealed that she’d never eaten an egg until she was in college. Apparently, her folks never made her eat anything she didn’t want and it wasn’t until she was “dared” to eat one in college that she found out she liked them.

She’d worked in Washington, DC for a newspaper, and then following the controller strike in 1981 was hired by the FAA and sent to Chicago Center. She washed out of the ARTCC option and was offered the FSS in Watertown, SD which she accepted. The first car she ever owned was the one she bought when she had to move to South Dakota. She lived in an apartment above a sewing shop in the main business district, which was about as urban as possible in Watertown, but this was the farthest west she’d ever been and it was definitely the least civilized place she could imagine.

So, the irony of what happened to her is unbelievable. She always parked her car off the alley behind the L shaped building where she lived. One morning she heard a commotion in the alley and she casually glanced out her window to see what the noise was. In her alley there two cowboys on horseback with a buffalo trapped between her car and the building. The cowboys were trying to get the buffalo lassoed so they could pull it out of the space, but in the meantime this buffalo process was crushing the side of her car.

It seems that the buffalo had escaped from a ranch a few miles from town and somehow found its way to a place where it could destroy the car of the one person who thought she lived in the Wild West.

Careful What You Ask For
There was a family of ground squirrels who had their burrow just outside the Flight Service and we could watch the babies playing in the grass right outside our window. It seemed like everyone thought they were pretty cute and enjoyed watching them.

One morning when I came to work I noticed one of the adults, obviously dead, right at one of the entrances to his burrow. A few minutes later the day shift specialist came in and, having seen what I’d seen, was very distraught. She was going to talk to the airport manager. I figured they’d need to dispose of the dead rodent, which was a good idea.

Later that morning one of the airport workers came in and I learned the rest of the story. It seems the specialist, who was so disturbed by the dead squirrel, had actually precipitated the situation. Apparently, she had complained to airport management about the squirrels and wanted the airport to get rid of them. As a result of her complaint, airport management put out some poison and that did get rid of the squirrels.

I talked with the specialist later and asked her what she thought would happen when she asked that they “get rid” of the squirrels. She said she thought the airport would bring in animal control, trap the squirrels and have them relocated to a new home.

Deer in a Hole
The airport authority was building an underground power vault right outside the FSS and had excavated a large hole, probably 15 feet square and eight or ten feet deep.

One day we saw a couple of deer trotting down the street. Deer were very common and even though the airport was entirely fenced with an 8-foot fence topped with barb wire, they sometimes got onto the field. Some people thought there was a small band of deer that had been on the airport when the fence was built and still lived inside the fence.

On this particular day, construction workers from one of the aircraft hangers saw the deer and started chasing them. One of the deer took off but the other came off the road, got between the FSS and the airport fence, and became panic stricken. He couldn’t get over the fence and kept throwing himself into it trying to get through. The violence with which he threw himself against the fence was amazing. He broke off one of his antlers and was bleeding from the head and one leg. There was only about four feet of space between the fence and the FSS plate glass windows so we had a great view but were concerned that if he started throwing himself into the windows we might have a wounded and terrified deer inside our office. We watched closely and cautiously as the deer gradually worked his way back the way he’d come.

When he finally cleared the corner of the building and could see an escape route he was off like a shot – for about four feet – then he hit the hole. Now he was really trapped. He tried frantically to jump or claw his way out of the hole but it was just too deep and he finally collapsed at the bottom of the hole. He would struggle to his feet periodically and weakly try to get out of the hole but it was apparent that he was too tired and the hole was too deep.

We called the State Game, Fish and Parks office (GF&P) and explained the situation. When a guy from GF&P showed up he walked around the hole and assessed the situation then came into the FSS and calmly sat down for a cup of coffee. He said he didn’t think there would be any problem getting the deer out of the hole – we just needed to wait a bit.

After about 45 minutes the GF&P guy quietly walked around the hole to the “fence” side and then with a sharp clap of his hands and a shout he startled the deer into jumping straight up 10 feet. The deer was out of the hole that easy and took off at a hard run down the street where he’d originally come from.

His Heart Wasn’t in It
One of the specialists named Chuck had worked at Watertown for a long time. He knew the job well and did a good job, but never did more than he absolutely had to, and he was just waiting for retirement. Chuck’s real love was music, poetry and cooking. He was planning on moving to Iowa when he retired and had married a woman there. He was gradually moving all his stuff to her house and pretty much just “camping out” at his home in Watertown. Then their house in Iowa burned down. Chuck lost virtually everything – but the only thing he was distraught about losing in the fire was his trumpet that he’d owned since he was in High School!

Huron, South Dakota 1979-1985

A personal history written and submitted by Jim Anez, Huron Flight Service

Jamestown was on the verge of being downgraded from a Level II to a Level I facility and we had more specialists than there was work for, so I asked for a transfer. My choices were Great Falls, MT or Huron, SD, and we decided on Huron. We moved at the beginning of August two weeks after our son was born. The transfer was scheduled for early in July, but the FAA was good enough to delay the move until after the baby came. It wasn’t much fun staying in a hotel for 30 days with 7 and 9-year old’s, and a newborn, but we managed. In about 1983 I got a Flight Watch position and, in the fall of 1985, I was selected as supervisor at Watertown, SD.

The Huron flight plan area was all of southeast South Dakota, a portion of southwestern Minnesota and a bit of extreme northwest Iowa. Most of our workload was generated from Sioux Falls but Huron, Mitchell and Yankton FSS’s were busy at times.

WEATHER ISSUES

Snowed In
The only time I was ever stranded at the airport was in Huron. South Dakota is known for harsh winters and everyone has their stories so this is one of mine.

I was scheduled to go to work at 0800 on a Saturday morning. The weather was pretty bad that morning and there was a blizzard warning so when I left home I knew full well that there was a chance I could be stuck once I got to the airport.

When I got to work there were four of us there – the midnight shift who was going home, the 0600 specialist, and the Flight Watch specialist who had come in at 0600. There were also four guys from the NWS, two who were coming on and two who were going off shift.

The airport manager came in and said that he was going to make one more trip out to the highway with the snow blower and then was going to quit plowing, so anyone who wanted to leave the airport had to go and anyone who stayed should plan on being there until the storm was over. Don and I were both EFAS rated, so one of us had to stay and since I’d brought extra food, anticipating the situation, I agreed to stay and Don insisted that he’d stay too. The guy coming off the mid and the other 0600 shift guy went home.

It was fairly busy because the largest/busiest airport in our flight plan area was Sioux Falls and since they were not being significantly affected by the storm, it was business as usual for them. About 11 PM we dug one of the cots out of the storeroom that were kept specifically for this type of situations. We set it up in the back room and I slept until around 0300 or so and then Don took his turn to get 3-4 hours of sleep.

The airport manager had been hanging out mostly in the terminal building through the storm and on Sunday he offered to make sandwiches in the airport restaurant and bring them over. He had to use the snow blower to cross the 100 yards or so of the ramp and deliver us the sandwiches.

By late afternoon the storm seemed to be abating but the winds were still very strong. I personally think it quit snowing a couple of hours before the weather observer recorded snow ending but it was blowing so bad that it was impossible to tell the difference between snow and blowing snow.

Finally, around 2100 the facility manager with the help of a friend in a big 4×4, managed to get out to the airport with a relief specialist, and then he gave us a ride home. Driving through town there were drifts at the intersections that were 20-25 feet high with just a single lane cut through for vehicle traffic. I found a drift across my driveway that was 9 or 10 feet high and it was Tuesday before I was able to get to the airport to get my car.

ACCIDENTS AND INCIDENTS

Deposition
My next-door neighbors in Huron were an elderly couple, Elmer and Stella, who were in their 90s. They had a son who was a railroad engineer and a pilot. I’d met him, by chance, when he flew into Jamestown several weeks before we moved to Huron – months before we ended up moving in next door to his parents.

Elmer and Stella had a grandson, Dan, who worked for the National Weather Service and in 1980 he and his family moved to Huron from Florida. Besides working in the same place – the NWS shared the building with the FSS – Dan had kids about the same age as our kids and when he’d come over to mow his grandparent’s lawn we’d generally have a beer and visit.

In August of 1982 Dan and his dad departed Huron headed to Oshkosh, WI to attend the annual EAA fly-in. I was working on the In-Flight position the morning they departed.

A short time after they departed, Mark, who was on the Broadcast position (adjacent to In-Flight), took a phone call and then asked me to see if I could contact Dan’s aircraft on the radio – there was a message for them. I called and when they responded I told them we had a message for them and handed the microphone to Mark. Mark told them that the airport manager thought their aircraft might have been struck by lightning during the early morning hours when a line of thunderstorms had moved across the airport. There was a chunk of concrete missing at a tie-down where their aircraft had been parked.

Dan’s dad responded, saying that they had just gotten through the line of storms and didn’t want to turn back. They would stop enroute and have the aircraft checked out. I learned much later that they did stop in Brookings, SD and no damage was found during the inspection.

Dan and his dad flew on to Oshkosh, spending the remainder of that day and all of the next there. That evening they flew to DeKalb, IL, picked up Dan’s sister and headed home to Huron. Sometime around midnight, over Iowa, they crashed and everyone was killed.

About 2 years later I was notified that I would have to give a deposition in the case. Dan’s widow was suing the FAA, Piper aircraft, and the FBO who rented the aircraft. I was being deposed simply because I’d called the aircraft so Mark could relay the message! In reality it was a fishing expedition and the lawyer was trying to find someone to pay up. After about four very intense hours with the lawyers I realized they weren’t interested in what I had done; they were just trying to find a loophole in our procedures that would result in the FAA being found at fault.

The FAA was released from the lawsuit a couple of weeks after my deposition. I never learned if anyone got any money out of it because Dan’s mother and grandparents hadn’t been part of the lawsuit and his widow had moved back to Florida.

Uneasy Night
I had worked an 0800-1600-day shift during which, for some reason, I never rotated away from the Pilot Briefing position. The next day I was scheduled to work 0600-1400 but took the day off to go to Sioux Falls for something but I then came back on shift at midnight. The specialist I relieved gave me a routine pre-duty briefing and departed.

After doing administrative duties, like traffic count, etc., I was straightening up the desks and noticed a Weather Service accident report. Looking at it I noted it was for a fatal accident that occurred the evening after my day shift and realized that the aircraft identification was one that I had been given for 3 or 4 of the weather briefings that I had done that day. The trouble was that I couldn’t remember any specifics of the briefings – about all I could recall was that they’d all been for different destinations.

When I went to check the briefing logs for the day I found that everything had been put into a locked file – standard procedure following an accident – so there was no way I could know if I had talked to the pilot and whether the briefing had in any way been contributing. It made for a long night as I wondered about my part in the event.

Finally, when the 0600-shift arrived I found out that I had indeed briefed the pilot and the conditions – scattered snow showers along the route with localized IFR conditions – were exactly what the pilot encountered and apparently what caused the accident. The tapes had confirmed that the pilot was given an accurate route forecast and decided to proceed anyway with tragic results.

Thanksgiving
I believe the saddest Thanksgiving I ever spent was while working at Huron.

It had been an unusually nice day with clear skies and relatively warm temperatures, but pilot briefing was difficult because a cold front was dropping south though North Dakota with low clouds, wind, snow and cold temperatures. We’d been watching the deteriorating conditions all day as they steadily moved south, but for some reason the forecasts for southern North Dakota and all of South Dakota continued to call for nice weather. Only after the weather deteriorated at an airport following frontal passage would we see an amended forecast reflecting what was coming. Consequently, we were giving briefings using the forecast material but warning pilots that we anticipated the forecasts were wrong – we called this “trending” and was, in my opinion, the reason Flight Service weather briefers were there.

In the late afternoon we got a call from the sheriff’s office letting us know that an aircraft had crashed near a small town about 40 miles northeast of Huron and asking if we had any overdue or missing aircraft – we didn’t – and after checking the logs, we found nothing that would likely have been in that area. When we asked for more information about the aircraft we were told that the weather wasn’t very good (the front had passed) and the wreckage was burning. Because it was fully engulfed and the fire was so hot, they couldn’t read the aircraft identification or even tell what color it had been.

Then we started getting phone calls.

The regional TV stations had gotten the story and put it on the air. We were swamped with calls from distraught people who had friends or family flying and were concerned that they might be the victims in the accident. In a few cases we were able to advise that we’d talked to the pilot or aircraft and allay their fear but in most cases, we weren’t able to tell them anything helpful.

Eventually we got a call from the scene and again they couldn’t tell us anything for certain about the aircraft except that it was a high wing, probably a Cessna, and there were 5 victims. They said it appeared to be 2 adults and 3 children but they weren’t even sure about that.

Finally, we got a call from a guy near Watertown who had loaned or rented his plane to a guy so he could fly his family to Mitchell for a Thanksgiving family gathering. He was concerned because the weather had gone bad and the plane wasn’t back yet. He said the family consisted of husband, wife and three kids under the age of ten. He hadn’t heard any of the news stories so wasn’t aware there had been an accident.

I don’t recall ever learning what the official probable cause was but have always thought that it was probably weather related because the crash site was about ten miles into the area of deteriorating weather. We discovered that the pilot had checked the weather with the Watertown FSS before departing early that morning. He’d been told that all forecasts indicated the weather through all of eastern South Dakota should be excellent VFR for the entire day. There was no indication that the pilot had rechecked weather before departing for the return flight on Thursday afternoon so he was probably caught by surprised when he encountered the low ceilings and snow.

PEOPLE AND THINGS

Who?
Each year Huron, SD hosts the South Dakota State Fair during the week prior to Labor Day, and in 1979 this was the last full week of August. I had reported to Huron from Jamestown, ND at the beginning of August and was working my first midnight shift alone during the middle of that week.

During the pre-duty shift briefing I was told that “Bill Janklow was sleeping in his plane on the ramp right outside the FSS door and if anyone needs to reach him he’d like us to wake him”. Of course, my response was something like “Who the heck is Bill Janklow”? And the answer was “He’s the governor of South Dakota”. Yeah, right… the governor is sleeping in an airplane. I figured this was some kind of initiation prank they pull on new guys. I was assured it was no joke. Janklow had flown his own plane over to the fair but the Pierre, SD weather had gone below minimums due to fog, and there were no hotel rooms to be found in Huron.

I didn’t realize a couple of things. First off – South Dakota is a small state and it’s amazing who you rub shoulders with. Secondly – Fred Janklow, Bill’s brother, had been a specialist at Huron FSS and so most of the specialists were somewhat acquainted with the Janklow family.

So anyway, I decided to operate on the premise that the governor might be out on the ramp, but if no one called it wouldn’t matter.

Someone called saying he was Janklow’s son and he was supposed to drive to Huron and pick his dad up, but only a few miles east of the Pierre it was crystal clear. He wondered if it might clear off so Bill would fly home and they’d have driven over for nothing. The forecast supported the clearing trend so they decided to go home.

Now I believed that the governor was sleeping in his plane, but I’m counting on the weather improving at Pierre. If it didn’t improve I’m going to have to explain why I agreed with a teenage kid who didn’t want to drive 200 miles at 3am.

It all worked out. The Pierre weather cleared off and about 0500 the governor came in, used the restroom, checked weather, filed a flight plan and headed home.

So, that’s how I met the governor.

Conflict
The early 80’s saw a lot of changes in Flight Service as the first hints of consolidation started to appear. One of the early changes was direct phone lines installed at some airports and they could blur some of the established facility boundaries. One such case was a phone line in Mobridge, SD that rang into Huron FSS, even though Mobridge was in the Pierre FSS flight plan area. This really annoyed Pierre FSS personnel and consequently any time we got a flight plan cancellation at Mobridge we followed prescribed procedures exactly and forwarded the information to Pierre.

On one occasion I was on duty as CIC (Controller In Charge) when the facility manager and both supervisors were gone somewhere. We forwarded a flight plan cancellation for an arrival in Mobridge and moments later I received an interphone call from Pierre. The caller was the facility manager calling to complain about us “stealing” their traffic. I told him I believed we had handled the situation correctly and that he had no reason to complain. A few minutes later the admin line at the supervisor’s desk rang and when I answered it was the manager from Pierre. We had essentially the same conversation. Then a few minutes later the secretary came out of the office to say that the manager from Pierre was calling for our manager and did I want to talk to him. So, for the third time I went through what we did and how it was procedurally correct and he was welcome to call again the next day if he wanted to talk to our manager.

He did call the next day and whatever the conversation was it ended the problem. The people in Pierre were still not happy, but we never had any further complaints. Ironically, I would replace this manager in Pierre when he retired 6 or 7 years later.

Pilots and owners
There was a guy in Huron who owned a C310 but wasn’t a pilot. We never talked to him – I’m not sure he ever visited the Flight Service. Nearly every day he would work on the aircraft and two or three times a week he would pull it out of his hanger and start it up and run it a while and then push it back in the hanger. It never flew. Never did figure that out.

Another character was a lawyer who retired in his 70s and decided to fulfill a lifelong dream. He bought a Piper Cherokee and got his pilot license. He was a very nice guy but always a bit of a concern as a pilot. Often times we would see him in his leather jacket and white silk scarf taxi over to the terminal building to go in to have coffee. One day he came into the facility and said he was going to see how high he could get his plane. After takeoff he called overhead at 3,000 feet (field elevation was 1290). Then he reported 4,000 feet sounding pretty calm. Then he reported 5,000 feet sounding a little excited. Then when he reported 6’000 feet with a tremor in his voice and said, “That’s high enough, I’m coming down”

There was a doctor in Mitchell, SD who flew frequently. Apparently, he had another practice (or some kind of business) in northwestern Nebraska. I understood that he had been an instrument rated pilot but that ticket had been pulled and he was strictly VFR during the times I dealt with him.

One day he departed Mitchell and when we asked for a pilot report on cloud bases he gave us bases and tops of the overcast layer!

He would often call ahead when returning to Mitchell and ask us to relay messages. On one occasion he asked us to call the hospital and advise them of his ETA. When I called the hospital, his nurse told me that if this call is about Mrs. So-and-So he shouldn’t worry because she’d already had her baby. I passed this info and his response was, “How’d she do that?”

The final straw for our message relaying service was the afternoon when he asked us to call his home, give his wife the ETA and tell her they were going out to eat at a steakhouse. His wife asked us to tell him they were going out to have pizza. When we told him that he said we should call her back and tell her it was steak night not pizza night. We never relayed messages after that unless they were medically related.

We had a pilot who flew in regularly. I don’t know anything about him except that he seemed to be a competent pilot and he stuttered. When he would call in for an advisory it was agonizing because we knew who he was, and generally what he was trying to say long before he could get the words out. We always wanted to finish his sentences for him just to clear the air.

One day, on Flight Watch, I received a call from an aircraft with a pilot report. When I asked for his position I couldn’t understand what he was saying. After three tries I finally asked him if he could give me the identifier for the location and he responded with H – O – N. He was over HURON! To this day I can’t imagine how he was pronouncing it in such a way that I couldn’t understand him!

Jamestown, North Dakota FSS Stories, 1978-1979

A personal history written and submitted by Jim Anez, Jamestown Flight Service

Miles City was a Level 1 facility with a traffic count that justified Level 2 status. There had been a freeze on upgrading facilities so I, like those before me, decided to move on. During 1977, I submitted a few bids to Level 2 facilities and in the late fall I was notified that I’d been selected for a position at Jamestown with a transfer date in January 1978.

I arrived in Jamestown in mid-January to find temperatures stuck around 20º below and it stayed that until near the end of February. It had snowed a lot in November or December and although it never really snowed much the rest of the winter, it never thawed either. There were huge piles of snow all around the airport and during orientation and training I had to take a lot of airport information on faith because I never saw some of the airport until spring.

The Jamestown FSS flight plan area consisted all of southeast North Dakota and included Fargo where most of our workload was generated. In early 1979, Fargo was transferred to the Grand Forks FSS flight plan area and overnight we had very little to do. I couldn’t imagine staying in Jamestown with the low activity level so asked for a transfer a few months later.

WEATHER ISSUES

Don’t ever talk to the “media”
As weather observers we maintained a “basic weather watch” which meant that we didn’t stare outside all day long, but maintained an awareness of what was happening outside between scheduled observation times.

One night I was listening to a local radio station and sometime a little after 3:00 AM the radio guy says he just got a call from the airport and it’s snowing. I glanced outside and sure enough it was snowing ever so lightly. In fact, it was so light it didn’t affect the ceiling or visibility enough to require a special observation so I didn’t really do anything.

But as the hour wore on it bugged me and finally I called the radio station to let them know that whoever called in about the snow was correct… but it wasn’t me unless I was doing stuff in my sleep.

When the announcer came back on the air he corrected his earlier report and said the call must have come from a regular at an all-night diner because he’d gotten a call from the airport where the guy said he’d been sleeping!

Thank God it was 4:00 in the morning!

Helicopter damage
The Air Force ran some kind of dispersal exercise one summer. Jamestown is 150 miles southwest of Grand Forks Air Force Base and was one of the designated dispersal fields so they brought a tanker of jet fuel and a helicopter to our airport. They also brought a lot of people and I heard they “took over” an entire motel in town. The joke was that if they ever have to actually activate the plan it better not be on a weekend during basketball season, because there probably wouldn’t be any rooms. Anyway, for the two or three nights of the exercise we had a couple of Air Police hanging out at the Flight Service “guarding” the helicopter. Mostly they just played cards and sometimes we visited a little.

The night I worked during the exercise we had a nasty line of thunderstorms moving eastward across the state. During the evening shift my co-worker had called the Air Force base ops to alert them to the weather so they could see about getting the helo in a hanger or otherwise protect it. He was told that they couldn’t get hanger space and since they didn’t like to fly at night they’d take their chances. No action was taken and the guards just played cards all night.

The storms moved through on my shift and the worst cells passed south of us so there was no problem.

About 6:30 AM I got a call from an officer at the airbase wanting to know how badly their “…helicopter had been damaged…” during the night. Apparently, the message that got delivered was more of a report of what had happened rather than a warning about what could happen.

Winter weather
Winter weather can be brutal in the Dakotas. I never got snowed in at Jamestown but one night when it was snowing and blowing, I was tested.

The instrument shelter with thermometers was 30 or 40 feet from the building and on this particular night a snowdrift formed between the facility and the instrument shelter. The first observation after midnight I dug a path through the drift with a snow shovel and got my readings, but by the next hour the drift was more than knee high. Maintenance kept a snow blower in their shop so I fired it up and “blew” a path through the drift to get my temperatures.

The next hour the path I’d cut was filled in and the drift was nearly waist high, so I fired up the snow blower again. And so, it went all night; every hour I’d start up the snow blower and cut a path to the instrument shelter. By the time things started letting up the drift was more than four feet high.

The buried runway lights
Relationships on airports could be tricky at times and they were a little different at each place I worked. In Jamestown, for some reason, it seemed they were sometimes a little testy. The airport manager also ran the FBO (Fixed Base Operation) and he really didn’t care much about his airport obligations when he had other business to attend to. One evening during the winter of 1978-79 the snow had been blowing and drifting quite a bit and the Northwest Airlines station manager came in to ask that I call the airport manager and advise him that their afternoon flight had reported that about half of the runway lights were buried in the snow.

The aircraft had given me the same report and I’d already passed the information to the manager but he’d taken no action. So, thinking that the airline request might carry some weight I called the guy again. He pretty much told me he’d looked at them and they were fine. The response of the Northwest manager was that unless the lights were cleared they would cancel their flight that night and so I called the airport manager again. He told me it was his airport and he would give us condition reports.

Within 30 minutes I got a call from a member of the airport board asking what was going on. Apparently, the Northwest agent had called the board member. I reported the sequence of events up to that point and perhaps 30 minutes after that the airport manager called me on the radio advising that he would be on the runway clearing the lights. He was quite obscene and every time he moved the pickup to a new set of lights he called on the radio and told me what a son-of-a-bitch I was.

A couple of months later the city hired a full-time airport manager and the relationship among airport tenants improved considerably.

The rain storm
One night I was going into work at midnight but because my wife and daughter were gone somewhere I needed to drop my son off at a co-worker’s home for the night. Because of the extra stop I planned on leaving home a little early. As we left the house about 10:45 that night it was just starting to rain lightly.
By the time I’d driven across town it was pouring and as I started up the hill to the guy’s house the water was running down the sides if the street almost to the level of the curbs. I ran Kevin into the house and got him settled and went back to my car. The rain hadn’t let up a bit.

I got to the airport around 11:30pm, the intensity of the rain hadn’t decreased, and the specialist on duty was swamped. One of the ironies we encountered was that when adverse weather was occurring and we needed to take special observations or be particularly vigilant we’d get a rash of calls (mostly from people who were just curious) to ask what was going on. Since he was so busy I offered to get his weather observation started and, although we normally wouldn’t measure the precipitation until the observation at 1:00 AM I decided to see how much rain we’d gotten. I was stunned when I measured the water in the rain gauge and found that we’d had nearly 2¾ inches in just about exactly one hour.

While the on-duty specialist finished the observation, I called the forecast office and reported the quantity of rain and a few minutes later they issued a flash flood warning. There was some flooding – I know the railroad underpass in town was completely full of water and some creeks overflowed but don’t think there was a lot of property damage.

The rain quit shortly after midnight and when I checked the rain gauge for the 1:00 AM observation there was only one or two tenths to add to the measurement I’d taken prior to midnight.

Fake weather observations
This story is about a situation in Jamestown, but has roots back to about 1976 when I was in Miles City and first I’ll need to explain the equipment we used.

We had two teletype circuits in the facility, one for the transmission and receipt of weather and the other for flight movement and administrative messages. To send a message we typed it on one of the teletypes which simultaneously generated a paper tape with holes punched in it. Each character on the keyboard was represented by a different combination of holes punched in the tape. This tape was then placed in a Transmitting Device (TD) and when our station’s signal was received the TD would automatically start and read the tape as it was pulled through the device and would send it out the circuit.

These systems ran at 100 words per minute and the weather teletype ran almost constantly. After we took a weather observation we had to “cut” a tape and have it in the TD by 59 minutes after the hour. There were about 10 stations on each circuit and they were always polled in sequence. At the top of the hour the 10 weather reports for our circuit would be printed. Following this the weather for the state would be printed and then each surrounding state and states further away were printed. At 20 minutes and 40 minutes into the hour the TDs on the circuit would be scanned in case there were any changes in the weather. After all the current weather was received the rest of the hour we would receive forecasts, winds aloft or other weather information.

One night when I went into work at Miles City the specialist I was relieving pointed out an anomaly on the weather report for Jamestown. Instead of a weather report there was a flight movement message. I suggested that observer must have put the wrong tape in the TD by mistake. The guy I was relieving laughed and showed me that the hour before the very same flight movement message had been sent. The only explanation was that the specialist in Jamestown had put the same tape in the TD both times.

Weeks later I happened to be talking with a specialist in Minot FSS and mentioned what we’d seen coming out of Jamestown. The guy in Minot said, “Yeah, that was my brother.”

When I transferred to Jamestown I met the guy and it was obvious what he was doing – when he was working at night he’d fill out the weather reports for the full shift and would cut one tape which he’d put in the TD each hour in time for the transmit signal. This only worked because we did not encode the observation time on each report.

Not long after I got to Jamestown the format for weather reports changed and the time of the observation was now required at the beginning of each report. We all figured that would solve the problem of what the guy was doing because each report had to have a unique, and appropriate, time. Surprisingly this didn’t deter him as he would type all the reports at the beginning of his shift and then put them in the TD in order. I’m not sure what happened to the guy, I know management and the weather service were aware of what he was doing, but I wasn’t in Jamestown long enough to know whether he ever changed his ways or not.

AIRCRAFT LOST, CONFUSED, IN DISTRESS OR WHAT?

Oops
Northwest Airlines was flying B727s through Jamestown when I started working there. There were two runways, 12-30 and 04-22 (which is basically shaped as an X) but only runway 12-30 was constructed to handle the weight of a B727. Also, the only taxiway that the aircraft could use was from the intersection of the two runways to the ramp. Our standard policy was to broadcast a reminder for the pilots to not turn off the runway but to taxi back down the runway to the intersection then to the ramp.

A few months after I got to Jamestown Northwest had a strike and didn’t operate for most of the summer. It was late fall when they finally started up again and I was working when the first aircraft arrived. After such a long absence I forgot about the warning transmission and thought of it just as the aircraft started to turn onto the taxiway at the end of the runway. Before I could even make a call, the pilot was on the radio saying, “I shouldn’t be here should I?”

The airport manager had also seen what happened and called immediately to advise that, because the ground was frozen hard, there was no problem and the airliner could safely use the parallel taxiway. Whew!

ACCIDENTS AND INCIDENTS

Fire
A mail plane came through Jamestown every night enroute from Fargo, ND to Bismarck, ND and return during the midnight shift. They used Beach 18 aircraft that had seen better days. Their radios were so bad that when you heard some kind of scratchy squelch break at about the right time of night we just automatically gave them an airport advisory.

One night the plane had taxied away from the ramp, copied their clearance and was doing a run-up at the runway/taxiway junction when I glanced out the window to see the entire right wing on fire. I grabbed the mike and called the aircraft with the message.

The pilot’s response was, “Aw, not again”! He then revved up the engine, blew the fire out, and took off.

Mail Plane crash
During the first summer I was in Jamestown we lost a mail plane. I wasn’t working that night so don’t know the precise details of the event but by all accounts, the contacts with the flight were all perfectly routine. The aircraft was the same type as described in the previous story but with a different pilot. Some of the circumstances were eerily similar to what had happened in Miles City. The pilot was on his last leg of the night, departing Jamestown for his home base in Fargo. The flight was cleared to Fargo and after departure the controller didn’t expect to talk to the pilot until he arrived at Fargo. The flight was assigned a cruise clearance at or below an altitude where he would be in radar coverage. Consequently, the aircraft wasn’t missed until he failed to make contact at his destination.

Once again, I know a few things that were reported about the accident but have no idea what the actual findings of the investigation uncovered. The aircraft flew into some abandoned farm buildings about 8 or 9 miles east of the airport and, although it caused a power outage, the wreckage wasn’t located until after the aircraft was determined to be overdue. We were told the aircraft engines seemed to be operating and at normal power settings so it was a mystery why the pilot was flying so low.

You Just Never Know
I came on duty one night at midnight and in the shift turnover I was advised that the evening shift specialist had briefed a pilot and activated an “assumed departure” flight plan for a pilot flying from Wahpeton (located on the Minnesota state line in southeast North Dakota) to Bismarck (about 100 miles west of Jamestown). The weather in Jamestown (and to the west of us) was great – clear with unrestricted visibility but there was widespread IFR over the east edge of the both Dakotas and all of Minnesota due to low stratus cloud layer. I was told that the pilot was going to confirm his departure time and give me a pilot report when he passed south of Jamestown.

The first radio contact I had after taking over the shift was an aircraft eastbound to Minneapolis. I advise that VFR flight was not recommended due the IFR conditions being report to the east. I advised the eastbound pilot that I expected a pilot report about conditions to the south of Fargo and he elected to land a Jamestown and wait for the report.

I believe there were 4 guys who came into the facility. Shortly after they arrived I received the call from the westbound pilot. He verified his departure time and reported that ceilings around Wahpeton were well below 1000’, told me where the west edge of the clouds were and said he wouldn’t recommend anyone trying to fly VFR in that area. I gave the pilot the latest Bismarck weather and went back to my other duties. The group of guys from the eastbound aircraft, after hearing that report, asked to use a phone, called a cab and left for a hotel a short time later.

A couple of hours later I got a teletype message from Minot FSS requesting flight plan information regarding the westbound aircraft because he hadn’t cancelled his flight plan at Bismarck. This was somewhat routine – pilots often forgot to cancel and we just needed to locate the aircraft. The situation was somewhat complicated because the tower at Bismarck was closed at that time of the morning and as there was no one on the field. Minot FSS had to request that law enforcement personnel check the airport.

An hour later I received a further request for information on the aircraft which was now considered overdue. I still wasn’t particularly concerned because I envisioned the difficulties they were having getting someone to conduct an airport search and there was a good chance the plane was in a hanger. We got into the beginning stages of search and rescue several times every year and usually found the aircraft within an hour or two. Never-the-less at this point procedures required that I start calling other airports along the aircraft route of flight to see if the aircraft might have landed somewhere other than the destination. This put me in the position of having to call sheriffs in each county along the route of flight from where I’d talked to the aircraft to the boundary of our flight plan area. These are small, rural counties and I was literally calling these guys at home waking them up. Most of them weren’t too happy with the 3 AM calls and only one was at all cordial. He even offered to check an airport in the next county because it was relatively close to him.

All of my airport checks came back negative and although the aircraft couldn’t be found at Bismarck I figured it was there somewhere – probably in a hanger. At any rate the Civil Air Patrol (CAP) was alerted and about 7:30 I got a call from them asking about my radio contact with the pilot – what he said, how he sounded, was he fatigued, etc. The officer I spoke to said they would be launching shortly to begin the search.

On the drive home 30 minutes later, the radio news was reporting on the overdue aircraft and said the CAP had been out searching “since first light” for the aircraft.

That evening on the news the Bismarck TV station had a report on the aircraft accident. The CAP had flown the reciprocal of the guy’s route and found the aircraft wreckage almost immediately. The TV station even had video from the scene of the accident. In the pictures they showed tire tracks in the prairie grass (from the landing gear) on the side of a gently sloping hill. Then the camera panned following the tracks in the grass to wreckage against a pile rocks at the top of the hill.

Sometime later, visiting with an FAA investigator I was shown the pilot’s sectional chart with his route from Wahpeton to Bismarck drawn in pencil with a circle around the topographic feature of the hill he landed/crashed on. He knew this was the highest terrain along his route but apparently after leaving Wahpeton with the low ceilings he’d never climbed to any significant altitude and literally flew into the ground as the rising terrain came up to meet him.

The passenger was killed in the accident but the pilot survived and I heard that he stated that he didn’t know what happened. I was told that in his statement he said he looked over to say something to his passenger and the next thing he knew they were rolling along on the ground.

Miles City, Montana (MLS FSS) 1975-1978

A personal history written and submitted by Jim Anez, Miles City Flight Service Station

I started with the FAA at the Miles City Flight Service Station (FSS) on June 30, 1975. The facility was starting a staff rebuilding phase and one new hire was at the Academy in Oklahoma City when I arrived. In July we got another guy, and then another in August and two more in September. My first month and a half were spent at the facility doing whatever the specialists and manager could teach us to do. We got pretty good at transmitting flight plans on the teletype but we had no idea what we were doing. We only knew the format to be followed and if it was wrong we’d get an error message, get teased, and have to do it again. Two of us went to the Academy in September; the guy who started in August went in October and so on. As soon as a new guy became productive one of the “old timers” would transfer. A year later, by the summer of 1976, the entire staff (except for one guy and the facility manager) had started in 1975. By the summer of 1977, due to more transfers, there were only four specialists, all of us having started in 1975. That was a hard summer, with few vacations and a lot of overtime, but it was very rewarding because all of us had started at the same time, we had nearly identical training, and we all got along well.

The Miles City FSS flight plan area was approximately the eastern quarter of Montana from the Canadian border to the Wyoming border, about 40,000 square miles. Billings, Lewistown and Great Falls had the flight plan areas to the west, Minot, Dickinson and Rapid City had the flight plan areas to the east and Sheridan had the area to the south in Wyoming.

I liked Miles City. It was a good place to work and not a bad place to live (at least for a kid from a similar Montana city). Because of our large area of responsibility and distances between airports our work load was almost evenly divided between radio and pilot briefing and it was never dull.

WEATHER ISSUES

Conflicting Needs
When I arrived at Miles City in the summer of 1975 there were two special projects operating from the airport. One crew in a Lear jet was doing high altitude infrared photography and they needed absolutely clear sky. The other operation involved weather modification and the study of developing of thunderstorms. They wanted clouds. The two groups were in the flight service every day checking weather and somebody was always unhappy when they left.

High altitude photography
One day during July the Learjet guys got a clear day and were going to fly. As I mentioned it had to be absolutely clear – even thin cirrus affected the infrared so they waited and watched much more than they flew.

They asked if any of us wanted to go along and, because I was the new guy and not at all productive, I was allowed to go. There was a huge camera mounted on the floor of the cabin and only two seats in the cabin. They flew north-south tracks over the area between the Missouri River and the Yellowstone River in eastern Montana, and had to be at a very precise altitude, as I recall, 40,500 feet. From 40,000 feet eastern Montana in July looked just like the WAC charts that we used.

They flew for about an hour and made 3 round trips during that time. When they finished the south end of the third run the pilot almost literally dove to get down without overshooting Miles City. The aircraft was in such a steep descent it was all I could do to avoid sliding out from under the seatbelt.
At the end of the week I drove back to my home in Havre, MT. Interestingly it took me three hours to drive to Glasgow, the distance the Lear had flown six times in one hour!

Weather Modification
What we called weather modification was really the data gathering and study phase of a program that ultimately hoped to lead to some kind of weather modification program.

The operation involved three aircraft, a B26, a Beech Queen Air and a Piper Navajo. The aircraft had all kinds of instrumentation and they would simultaneously fly (at different altitudes) into clouds that were developing into thunderstorms to sample conditions. Support personnel on the ground included a meteorologist and a bunch of scientists. They had an early generation Doppler radar system and a large array of rain gauges spread over several thousand square miles in southeast Montana. Data from the aircraft, radar and the precipitation readings from the rain gauges were collected and studied.

Every day their meteorologist would come into the flight service, study all the charts and weather data, and give his crews a briefing on whether there was likely to be convective development that day. In 1975 he would categorize the likelihood of storms as “yes”, “no” or “maybe” and the flight crews would plan their day accordingly.

During the summer of 1976 the meteorologist no longer had the “maybe” option. He had to say “yes” or “no” and had to predict “when”. It was amazing how close he could come to the precise time that we would begin to see the convective development – usually with 15 minutes of the time he would predict.

One day as storm development began all three flight crews rushed in to file flight plans. They all wanted to depart at the same time and go to the northeast, but Miles City was an “uncontrolled” airport so normally each aircraft had to wait for departure clearance until the controller at Salt Lake Center was talking with the previous departure.

In this case the controller gave me clearances for all 3 at the same time. The B26 was to depart runway 04 and climb on course to the northeast, the Queen Air was to depart runway 12 and turn left on course to the northeast and, finally, the Navajo was to depart runway 22 and fly southwest to cross the VOR heading southwest at or below 5000’ then climb southwest of the VOR so as to cross the VOR northeast bound at or above 9000’. I didn’t know it at the time but the reason for this was that there was traffic crossing the VOR from northwest to southeast at 7000.’

I must have read the clearance to the Navajo five times before the pilot read it back correctly. That was fortunate because by then everyone in the FSS, including the facility manager, was standing next to me listening when the pilot finally read it back correctly.

A while after all of the aircraft had departed I got a call from the controller in Salt Lake City asking me to read back the clearance I’d given the Navajo. I did and it was what he’d given me. He then asked if the pilot had read it back correctly and I assured him that he had and that three other people could verify that (we didn’t have recorders). He then instructed us to have the pilot call Salt Lake City when he got back to the airport.

I learned later that the Navajo had crossed the VOR at 5000’ heading southwest, then turned around and reported over the VOR at 7000’ heading northeast. Within a minute the transient aircraft reported over the VOR at 7000’ heading southeast. Both aircraft were in the clouds and they were on different frequencies so they didn’t know about each other and no one knows how close they might have been to each other. (Radar coverage over that part of Montana began at around 10,000 feet).

I was off duty when the aircraft returned so don’t know exactly what happened but there were new pilots flying the Navajo the following week.

[I have often wondered why the controller didn’t have the Navajo depart runway 30 with an altitude restriction and turn right after departure. But it is what is is.]

Flying the mail in winter
A company based in Denver flew mail from Wolf Point to Billings with a stop in Miles City every night.

The pilot, in Wolf Point, would check weather and file flight plans with us early in the evening then arrive about 2200 enroute to Billings. He would return to Wolf Point stopping in Miles City between 0200 and 0300 each morning. The Aero Commander 500 aircraft they flew were used hard and, by most accounts, weren’t in the best of shape.

One cold winter night, with temperatures around -15 and a little wind, I got a call from Salt Lake Center that an Aero Commander 690 had lost an engine and would be landing at Miles City. They did not declare an emergency and landed uneventfully. Shortly after they landed one of the pilots came into the FSS and introduced himself. He was the owner of the company that had the mail contract and asked if I would let his pilot know that they would need a ride to Billings when he stopped with the mail.

Soon after that an older guy came into the FSS. His face was beet red and he was really huffing and puffing from having been out in the cold. It turned out that he was the chief mechanic for the company and had opened the engine covers to try and figure out what had happened to the engine on the AC90.

When the mail pilot called from Wolf Point to check weather and file flight plans, I advised him that he’d have two riders from Miles City to Billings and who they were. His response was that it was good because he was flying a plane with no heater and maybe if they had to fly in it they’d do something about fixing the plane.

I let the owner know that I’d relayed the message and that they should be bundled up because the AC50 didn’t have a heater. His response was to send his mechanic back out to remove the heater core from the disabled AC90, and when the AC50 arrived they installed the heater in it.

The next week when I talked to the pilot of the mail plane, the events of the previous week came up and I commented that at least he got a working heater for his troubles. He said, “Not true, the SOB removed it when they got to Billings, I’m still flying without heat!”

Weather Observation hazards
In addition to assessing sky condition and visibility we had to obtain temperature readings for each weather observation. This involved a trip to the instrument shelter and a 2 to 5 minute stay to allow the “wet bulb” thermometer to be read accurately.

I’d started working shifts alone in November so obviously the weather wasn’t the greatest. One dark evening when the temperature was in the low 30’s and it was raining sideways because of the wind, I stood in the doorway for a moment and the thought crossed my mind that I could fake the temperatures this one time and no one would ever know. Then it occurred to me that less than six months earlier I’d been delivering Coca Cola and often worked in weather like this all day long – I could certainly go outside for five minutes. I never again hesitated to do what had to be done to take accurate weather observations.

There were cautionary tales about the dangers of lightning, etc., and we heard about the guys at Miles City who found rattlesnakes warming themselves on the sidewalk between the building and the instrument shelter. While I was there we never had any snakes but one day the specialist had to report the temperature as “missing,” and in remarks he had recorded “skunk under instrument shelter.”

One night, as I was leaning into the shelter to read the temperatures, I heard someone behind me and then someone put a hand on my shoulders. I spun around to find the biggest, friendliest Chocolate Lab you’d ever care to meet staring at me with that “watch doing” look in his eyes.

Gut Feeling (Sometimes things just happen the way they’re supposed to)
Miles City was an airport where a lot of general aviation pilots stopped for fuel and weather briefings so we had a fairly regular stream of walk in weather briefings. This particular day the weather in eastern Montana was broken to overcast ceilings between 4000 and 6000 feet and very strong winds with a lot of turbulence being reported.

I had just talked with a Canadian pilot flying a Piper Comanche heading southeast to central South Dakota. I’d advised him to expect ceilings to drop to around 3000 feet in northwest South Dakota and that those conditions should prevail all the way to his next stop. The guy seemed very competent and I didn’t think that those conditions should be any problem for him.

A short time later another pilot came in. He was with his wife and 2 daughters and they were in a Cessna 182 heading essentially the same direction. This guy seemed uncertain and somewhat concerned about the conditions. The more I talked with him the more I tried to discourage him continuing that afternoon. He’d talk with his wife a bit then we’d look at additional reports and then they’d talk some more. He made a couple of phone calls and eventually asked about getting a cab – he said they’d decided to take a bus to Billings and get a commercial flight to where he was heading.

I told him that I was getting off duty soon and I could give them a ride if they wanted to wait. He was fine with that and I gave them a ride into town when I got off work.

On the way into town I learned that he was from Missoula. He asked if I knew any of the guys in Missoula and I mentioned that I was acquainted with a guy who worked in the Tower. He asked if I liked Flight Service and I said I did because I really felt like we helped pilots and enjoyed the personal contact. I said something like, “We don’t often get into life and death situations but I feel like it’s a really valuable service.” His response was that I should consider that I saved the life of 4 people that day because he was convinced that if he’d continue his flight they wouldn’t have made it. He said the turbulence had been so bad from the Rockies east that he was beat, and if he’d continued into the marginal conditions I’d described, the consequences wouldn’t have been good.

Visibility too good?
I was on the radio one day when an aircraft called for an Airport Advisory stating that he was 10 north of the airport. Out of habit I glanced at the DF and it indicated a bearing of about 360º. Moments later I received a call from another aircraft, who also said he was 10 north and inbound to land; and again the DF showed about 360º. I gave the advisory and traffic and alerted both planes that I was showing them both on the same bearing. They both responded that they were looking, but neither saw the other.

A bit later the second aircraft landed with still no sign of the first aircraft. I called him and he reported that he thought he was about 10 north (still?).

Later when the first aircraft finally landed the pilot came into the FSS. He apologized for the confusion and explained that he was from Ohio and back there when you could see something you had to be within about 10 miles. He said he must have been 20+ miles out when he saw the Yellowstone River and just wasn’t used to it being so clear that you could see things that far away.

The Wild West
I had the opportunity one day to visit a ranch somewhere out in the Powder River basin southeast of Miles City. I don’t really know where it was – I just know it was a long way from anywhere. As we drove up to the ranch house I noted that there was a Piper Cub and a Cessna 182 parked near one of the out buildings so I thought I’d have something in common with the rancher.

The rancher asked me what I did a couple of times and it became obvious that he didn’t know what a Flight Service Station was. I told him that when he flew into Miles City I was one of the guys he talked to on the radio, and his response to that was even more of a surprise to me. He said he didn’t like using the radio and he’d never think of flying into a big airport like Miles City! He just used his planes to keep tabs on his cattle.

I wondered at the time how many other ranchers had aircraft that we knew nothing about and likely weren’t even properly registered. Several months later I had my question partially answered.

The Air Force Rescue Coordination Center was just started to use satellites to detect and locate transmission from Emergency Locating Transmitters (ELTs) in those days. ELTs are designed to automatically trigger when an aircraft is involved in an accident but in my experience, probably 90 percent of the signals were inadvertently triggered by hard landings or other non-emergencies. When the Air Force got an ELT signal they would calculate a rough location and they would contact the nearest FSS. We would then contact airports near the location and attempt to try to eliminate the possibility that the signal was inadvertently triggered from an aircraft on the airport.

On one day, after my ranch visit, I got a call from the Air Force RCC saying they were receiving an ELT from the vicinity of Baker, MT (about 80 miles east of Miles City). I contacted the Baker Airport and they advised the signal wasn’t from an aircraft on their field, and in fact, they couldn’t hear any ELT signal on the ground.

We always figured the satellite locations were somewhat inaccurate, but there were no other airports anywhere near Baker so we were stumped. Recalling my experience with the rancher and the suspicion that there were aircraft on ranches that we knew nothing about, I called one of the local pilots in Miles City who sold insurance and seemed to know every rancher in southeast Montana. I asked him how many aircraft he thought might be on ranches east and south of Miles City that weren’t “on the books”. His estimate was there might be as many as 50 but he said not to worry because if they ever had ELTs installed they would have been removed or the batteries were dead.

Dickinson FSS finally located the aircraft with the active ELT. It was coming from an aircraft that was in a steel Quonset building on a ranch near Bowman, North Dakota (about 40 miles east of Baker). The officer at the Air Force RCC speculated that the shape of the building focused the signal towards the west causing the satellite to “locate” it in the Baker area.

If It Ain’t Broke
There was a spray pilot who lived in a small community about 60 miles northwest of Miles City. He had a strip at his farm place but would sometimes fly out of Miles City, and during the summer we talked with him several times every day. One morning when I went to work at 8am I was advised that I should expect someone from State Fish and Game to come out during the morning to pick up a dead dear that was on the side of the runway. It seems the spray pilot hit the deer while taking off.

I expected that meant we’d had an accident and started looking for a wrecked airplane but couldn’t see anything. The specialist said it wasn’t that bad and the pilot had just jumped out of the plane, dragged to carcass off the runway and continued on his way to the spray job.

The pilot had a Twin Comanche that he flew for personal use and during the winter he would travel throughout California and the southwest US. More than once I saw flight plans with arrival times that wouldn’t get him home until after dark. I knew his strip wasn’t lighted and often wondered how that worked.

Finally an opportunity presented itself and I asked him about what happened when he got home after dark. He said he had an “approach” and went on to explain. There was a yard light at the school in the town and he had a yard light at his house and there was a small hill between the field where he landed and his house. He said he lined up the two lights, crossed the school light at a precise altitude at a specific speed and rate of descent. As soon as his yard light disappeared behind the hill he flared and cut the throttle. He then just let the plane roll straight ahead until it came to a stop at the base of his little hill.

Since the guy was in his 70’s I figured it must have worked pretty good for him for a long time and never again worried about what happened after dark.

AIRCRAFT LOST, CONFUSED, IN DISTRESS OR WHAT?

This was before GPS and the majority of the pilots were not IFR rated. Radar coverage over most of our area began around 10,000 feet and navigation aids were a long way apart. The area is sparsely populated and the there aren’t a lot of unique topographic features. The end result of all this was that it was not uncommon to have aircraft become lost (or at least unsure of their position). It was normal for each of us to have 2 or 3 orientations a month assisting pilots in determining their position using the Direction Finder and other orientation procedures. There were also a number of pilots who would have us do practice orientations on a regular basis as well.

He wasn’t lost (but didn’t know where he was)
One night an aircraft called, enroute from Billings to Glendive, with a position report. Cities and larger towns in that part of Montana were mostly established along the Yellowstone River, which runs from southwest to northeast. The pilot reported north of Miles City but on my DF he was west. Suspecting he was north of Forsyth (the next town to the southwest) I asked him to confirm his position. He was insistent on where he thought he was saying he could see Terry (the next town northeast of Miles City) ahead. A while later he reported north of Terry, but now my DF showed him north of Miles City. I figured he was one set of towns off and told him what I saw on my DF, but he again insisted that he was north of Terry and could see Glendive ahead. I asked him for a fuel status and he had 3 hours left so I figured that even if he was 50 miles behind of where he thought he was he wasn’t going to run out of fuel and would eventually figure it out.

Sure enough the next call he advised that now he was “really” north of Terry and had the lights of the “real” Glendive ahead.

Who turned this guy loose?
The biggest city in the northern portion of our Flight Plan area was Glasgow, and the Glasgow Air Force Base was located about 20 miles north-northeast of Glasgow. Glasgow AFB had been established about 1957 as a fighter-interceptor base, and in 1961, B-52 bombers and KC-135 tankers began to operate from the base. It was deactivated about 1968 and then reactivated in 1971. By 1977 it was  deactivated again and the tower had been shut down, the runway closed, and the only personnel stationed there were caretakers who were closing the place down. One day I got a call from a Piper Comanche with student pilot on a long cross country. He was low on fuel and uncertain of his position. We tried to get him to tune the Glasgow VOR, but he didn’t seem to know how to use his VOR receiver and the information he was giving us didn’t make any sense, so we tried pilotage. There aren’t a lot of unique or significant landmarks across the prairies and wheat field of the area, so that was problematic. He did say he’d seen some white domes, that led us to believe he’d sighted the air force base or a radar station, but he hadn’t seen any runways near them. He couldn’t tell us how long ago it had been or what headings he’d been flying since then. We asked him to squawk emergency but he couldn’t confirm that his transponder was even turned on. We called Salt Lake ARTCC and asked if they had any primary or secondary targets in the area and advised they might be squawking emergency. The controller had only 3 primary targets, none identified, and none were on headings even close to our Comanche.

About that time the guy quit talking to us and we began to shift to a SAR mode thinking he must have run out of fuel and crashed. But we had no real idea of where we would even start the search.

A short time later (it seemed like a “long time” then) we received a call from the FBO in Glasgow who had gotten a call from a pilot who said he had nearly run out of fuel, had landed at Glasgow AFB, and wondered if the FBO could bring him some fuel. I believe our facility manager finally reached him and we figured out that he had turned around without telling us (that’s why none of the radar tracks matched our aircraft) and landed at the air base.

The next day I received a call from an Air Force Major. He said his CO had told him to call and make sure we knew that the base and runway were closed at Glasgow AFB. I assured him we were aware of that and asked if this was a result the Comanche that had landed there the previous day. I was thinking that perhaps they didn’t realize it was an emergency landing. He was astounded and said he had no idea a plane had landed there, he had just been directed to call us and had no idea what had prompted the order.

Not lost but scared and scary
One summer evening shortly before sunset a Cessna 140 pilot came in. He was enroute from Billings, MT to his farm near Bowman, ND. He asked about weather conditions eastbound which were really not a problem, I was estimating 5,000 overcast and visibility was good. He asked if I would be able to use the DF to give him a heading outbound from Miles City to Baker. He had no navigational equipment on the aircraft and his plan was to take the outbound heading that I gave him until he got past the higher terrain east of Miles City. He figured he would be able to see the airport beacon from Baker by then. Once he got to Baker he would be able to see the beacon from Bowman and get home. Even with the good ceilings and visibility I knew it would be dark soon. He wouldn’t file a flight plan and with the overcast, there wouldn’t be any moonlight so I tried to talk him into staying. I even offered to let him use the cot we kept for emergencies and sleep at the FSS. He declined saying that he had to get home. He said he’d been working in the field when his wife left for Billings and realized that she didn’t have all the documents she needed so he jumped in the plane and flew to Billings. Now he needed to get home because there was no one there to milk the cows.

He took off just at sunset, and using the DF I got him headed east. Just when I thought he was on the way, he called to advise that all his lighting had gone out and he was returning to Miles City. I didn’t hear from him again and he wouldn’t answer up on the radio, so after a bit I went outside and observed an aircraft with lights over the field turning towards the east. I called him on the radio again and he said he’d gotten the breaker back in and everything was fine. I suggested again that he might want to stay overnight, but he said no and asked for the outbound heading again.

After he’d been gone a while, and I presumed he was well on his way, I suddenly got a panic call from him saying, “I’m in the clouds, what should I do?” I can honestly say that in 26 years with the FAA this was the one and only time I ever heard pure panic in the voice of a pilot. Anyway, I told him to just concentrate on keeping wings level and throttle back so the plane will settle out of the clouds on its own. A minute later he called to say he was out of the clouds, so I asked his altitude. He was at 7,000 feet (which confirmed my estimated 5000 foot ceiling)!!!! He thanked me, said he would stay at 5500 feet and said goodnight.

This whole thing really bothered me so after a while, when I figured he should have been in Bowman, I called Dickenson FSS to see if they’d heard from him. To my surprise the specialist said he had and, in fact, the guy was sitting in the Dickenson FSS waiting for someone to drive up from Bowman to take him home. It seems that the Bowman airport beacon was out of service (since this was a Local Notam I had no knowledge of the outage). When the pilot got to Baker and couldn’t see the Bowman beacon so he’d turned northeast and had flown to the Dickinson beacon.

I don’t think this guy was ever lost
One day I got a call from Billings FSS. They had a Cessna 421 overdue on a VFR flight plan from somewhere in North Dakota or Minnesota. I hadn’t talked with the aircraft, but a short time later I received a teletype message from a FSS in Canada advising that the C421 had gotten lost and landed in Moose Jaw, Saskatchewan. I let them know that the aircraft was on a flight plan to Billings and called Billings with the information I had.

When I came in the next morning the specialist who had been on the midnight shift advised me that the same C421 had filed a flight plan from Moose Jaw to Glasgow, MT and requested customs. When the aircraft didn’t arrive or cancel his flight plan the specialist tried to call him on the radio and managed to establish contact. He was lost again and declared an emergency. While in the process of trying to locate the aircraft the pilot saw an airport, which turned out to be Malta, MT (about 100 miles west of Glasgow) and decided to land there. Since the aircraft was inbound from Canada, it needed to clear customs, and there was no customs service available in Malta. The specialist told the pilot to stay with the aircraft until someone from a law enforcement agency could meet him. I don’t know the details, or who made the decision, but a State Patrol trooper went to the airport only to find the aircraft parked and no people anywhere.

We subsequently learned that the pilot was from Minnesota; he owned several aircraft but only had a student license that had been issued in the 1950’s. Investigators also determined that the pilot had rented a car and a U-Haul trailer that night in Malta.

I never heard any more about the pilot, but in the early 1980’s I happened to be driving through Malta (my home town is about 90 miles west of Malta) and I stopped at the airport. The C421 was still parked on the ramp and there were chains wrapped round the props!

More disoriented aircraft
One morning just a little before 8:00am, when I was just getting off a midnight shift, an aircraft requested orientation assistance. The specialist who’d come in at 6:00AM took the call so I could complete the shift turnover to the oncoming specialist.

He’d no more than determined the aircraft location when another aircraft called with the same problem. The 0800-1600 specialist, who had just relieved me, took that aircraft while the first specialist finished up with his paperwork documenting the first orientation.

In the meantime I had taken the 8:00 AM weather observation and was about to leave as the second specialist completed that orientation and started doing the paperwork. Before I could leave the room a third aircraft called asking for assistance, and because I was the only one not busy I took him. He said he was on top of the overcast but had encountered a wall of cloud and needed to know where he was. I determined that he was directly over Forsyth, MT (west of Miles City) and he elected to turn back to Billings.

A few days later I talked to the pilot and learned that he’d been there for a while circling as he listened to us work the first two aircraft, “… just waiting his turn.”

Calling “Any Facility”
During a midnight shift I heard a military aircraft, probably a B52, calling “any facility.” I could tell he was a long way off, we got those calls frequently requesting altimeter settings, so I figured a facility closer to his position would respond. I then noted that the aircraft was calling on the UHF emergency frequency and no one else was hearing him so I responded. The pilot was declaring an emergency due to engine problems, advised that he needed clearance for an emergency descent and gave me his position. It turned out he was in northwest South Dakota very near a point where the airspace of Denver Center (ZDV), Salt Lake Center (ZLC) and Minneapolis Center (ZMP) meet.

Salt Lake Center was the only control facility with which I had direct contact so I called them. The controller advised that he saw the emergency squawk code, but the aircraft wasn’t in his airspace. I relayed the aircraft message and again got a “it’s not my airspace so it’s not my problem” type of response. I suggested he try to coordinate with whoever owned the airspace and then called the aircraft.

The pilot advised that they had started their descent heading for Ellsworth Air Force Base in Rapid City, SD, so I should just let center know to get any traffic out of the way.

I called the controller back, passed that message and this time got a little more reaction. He said he’d call Denver. A few minutes later he advised that Denver center had talked to the aircraft and they were now with Ellsworth approach control.

DF Approach
The DF (Direction Finder) was a wonderful tool. In addition to giving us the ability to get a line of bearing from the airport to use for cross fixes, we had the ability to guide the pilots on “last resort” (very) non-precision approaches. I personally only know of one time this was done for real, but it worked exactly like it was supposed to.

There were three pilots who owned an aircraft in Colstrip, MT and periodically they would fly up to Miles City and ask for practice DF approaches. One of them told me that they were not instrument rated but it was good practice for them to come up to Miles City, where the airspace wasn’t too busy, and have us give them approaches while they took turns flying with a hood.

One Saturday or Sunday they called in and asked if I had time to do some approaches. The weather was good except there was a very strong cross wind to the final approach course.

Well the first pilot flew his approach and everything was working pretty well until he was lined up on final. The heading I gave him failed to compensate enough for the crosswind and when he finally broke off on the approach he wasn’t even close to the runway, in fact he was barely over the airport.

The second pilot flew his approach and I gave him a heading to fly that I figured would work with the wind. He was close enough to the runway that he would have been able to land in a real emergency, but I thought I could do better.

By the time the third pilot turned on final I thought I had the necessary correction figured and sure enough he was coming straight in to the runway. I was feeling pretty proud of myself when all of a sudden he started to drift big time. He was too close to the airport to make any corrections so I terminated the approach and they landed. I couldn’t imagine what had happened; I was sure I’d given him enough correction and there hadn’t been any significant change in wind since the two previous approaches.

They came into the FSS after they landed to debrief and I apologized but said I had no idea why the last approach went so bad at the last minute. They laughed telling me that it was the pilot – he’d “lost the picture” and the safety pilot had to take the aircraft to complete the landing.

ACCIDENTS AND INCIDENTS

The Mail Mess
The contract carrier who brought the mail to the airport each evening, and picked it up each morning, developed a pretty good relationship with the regular pilots on the mail plane. Apparently they’d developed a procedure by which the carrier would place the mail bags on the ramp and the pilot would shut down his left engine as he taxied in and straddle the bags as he rolled to a stop. One night a relief pilot was on the trip and didn’t get the engine shut down soon enough so the prop was still windmilling as he rolled up on the mail bags. One of the props hooked the mail bags, tore them open and threw mail everywhere. People were running all over the place collecting bags and bits of mail for the next hour!!

Carb ice – Really?
Working one evening in the winter I had a call from an inbound Cessna. I gave him an airport advisory and continued with other duties. After what should have been enough time for him to land, the other specialist and I realized he’d never reported clear of the runway. It was too dark to see anything on the field, and we were expecting a call from the scheduled commuter flight soon, so we were a little bit concerned.

Just then the Cessna called and asked if we could reach the FBO and have them bring some de-ice fluid out to the runway as he had some carb ice and the engine had quite on the runway.

We made a call and the FBO line service kid drove out to the runway. He wasn’t there very long and then came back to the ramp. He stopped at the FSS to advise that he would be going back out with a tug… the Cessna engine had quit because the plane was out of fuel.

Good planning (not)
It was a nice summer day, a little busy with 3 or 4 aircraft constantly in the pattern, when a Twin Comanche with a Canadian registry called and asked for a DF steer to the airport. He was on a VFR flight plan inbound from Great Falls (northwest of Miles City) but the DF showed that he was southwest of Miles City. Apparently, when he saw the Yellowstone River, he knew he’d missed the airport and was flying up the river to find us.

Winds were from the southeast favoring runway 12, but not very strong. The way the traffic was working out I figured the Twin Comanche could probably enter the downwind leg for runway 12 about midfield and land runway12, but he asked if he could land straight in on runway 04. I again alerted him to the traffic and suggested he might be able to make a right base to runway 12 if the other traffic would cooperate, but it was an uncontrolled airport, so it was his decision.

He elected the right base option and landed on runway 12 uneventfully but I learned later from the fueler that there was probably less than 5 gallons of gas remaining when the aircraft landed. That was undoubtedly the reason he didn’t want to fly the standard left hand pattern. What baffled me was why hadn’t he fueled in Great Falls when he stopped to clear customs.

The Mail Plane Accident
Kris, the pilot who flew the AC50 mail plane was also the airport manager in Wolf Point. As a result, I became fairly well acquainted with him. At some point Kris bid on the mail contract in competition with the company that he was flying for, and as a consequence he was fired. The new pilot who was brought in was a nice enough guy, but I never really got to know him.

During the winter of 1977 I’d gone to Havre for a long weekend. As I left Havre, heading back to Miles City, I heard a news report on the radio that a mail plane had crashed north of Miles City. The name of the pilot had not been released, and knowing that Kris occasionally filled in on the mail flight, I was concerned he might have been flying.

As I traveled east I eventually got within range of the radio station from Wolf Point. They were reporting the story and giving the name of the pilot. It wasn’t Kris, it was the new guy.

That afternoon when I got to Miles City I received a call from my brother, who, at the time, was a reporter for the Great Falls Tribune. He wanted details about the accident and the name of the pilot. I told him that, even if knew anything, I couldn’t give out information but regardless, I’d been in Havre and had just gotten back to Miles City. I couldn’t even remember the pilot’s name so I told him to call the radio station in Wolf Point because they were putting the name out.

The next day I saw the story in the Tribune and they’d spelled the pilot’s name incorrectly! Later when I talked to my brother he said he’d called the radio station and gotten the correct name, but when the Associated Press released the story they had a different spelling so the editors decided to go with the version in the AP release!

PEOPLE AND THINGS

The summer aide
During the 1970’s the FAA had a program to hire high school kids during the summer to help out at the facilities. I think it may have been titled “stay in school” or something. The first two summers I worked at Miles City FSS we had a high school girl who helped with filing, etc. She graduated, and for the third summer, upper management advised that anyone hired had to be a minority, and being female didn’t count. Native Americans were about the only minority in southeast Montana. Our summer aid in 1977 was a high school dropout, about 16 years old, who was half Japanese and half Native American.

His transportation, when he started, was a small motorcycle or scooter but as soon as he had a couple of pay checks he bought a car. I don’t recall seeing that first car, but I was told that the FSS specialist who first saw it called the dealership and told them they’d better give the kid his money back or give him a better car, or they’d never see anyone from the FAA in their showroom again. So he got a “better” car. This one I saw… the windshield was cracked, it had a coat hanger for a radio antenna, the tires were not quite bald, and there was always a large puddle of oil wherever it was parked.

I know at least one of the specialists talked to the kid about the oil leak and I believe they had something scheduled with the dealer to look into that. Then one Monday the kid was late for work and it turned out he’d had to walk to the airport. His story was that he’d been driving the car and all of a sudden the heat gauge shot up, the engine went “klunk,” and it quit running.

It turned out that although they had talked with him about the oil leak, no one thought to tell him he needed to replace the oil that was leaking. He’d driven the car until all the oil was gone and the engine seized. He didn’t really have money to fix the car so he got his motorcycle back and started driving it to work every day.

A week or two later we were talking at work and he mentioned that he and his friend had been in his car listening to the radio. That seemed odd and I asked if he’d gotten it fixed. He said, “No, it still won’t run, but it’s only 6 blocks from our apartment so we walk down to where the car is and listen to the radio at night.”

The sheep herder
One day, as I recall, it was a weekend afternoon during the first spring I was in Miles City, a guy walked into the FSS. I was working with Steve Martinez, one of the best specialists I ever knew, and Steve kind of took the lead in talking with this guy. The three things I remember about him were that his clothes were filthy, he smelled horrible, and he was irate.

He demanded that we tell him the name of the pilot of one of the spray planes that operated from the field. He didn’t know what plane it was and wasn’t even sure what color it was, but he wanted to know who the pilot was because the plane kept flying low over his sheep camp and scaring his girlfriend.

It was difficult to keep from laughing because this guy was so dirty and smelly we couldn’t imagine that he could have a girlfriend, or if he did, what she would be like. The problem was that the guy was scary mad and when we finally got him out of the facility, he said he was going to sit there in his pickup until he saw the plane, then he was going to kill the pilot.

We’d noticed that he had something shoved down his pant leg that was long and stiff, and as he walked across the parking lot we could tell it was long enough that he couldn’t fully bend his leg. Thinking that it could easily be a rifle or shot gun, and given the threats he made, we decided to call the sheriff’s office. In a few minutes a deputy pulled up and started talking with the guy. It turned out that he had a tire iron in his pant leg, and we observed the deputy handcuffed the guy, but we never heard any more about it.

Midnight visitors
The airport at Miles City is about two miles north of the city (about 3 miles driving distance) on the bench above the Yellowstone River, and at night the Flight Service was the only lighted building on the airport. Consequently, we got the occasional odd visitor.

One night I had four teenagers walk in the airport ramp entrance. There wasn’t any aviation activity so I was somewhat startled. It seems they’d been out driving around on a gravel road on the other side of the airport when they ran their car in a ditch, or it broke or something. They saw the lights across the airport (about a mile) and walked across the airport to call for help.

Another night, in the dead winter, with temperatures near ten below and a steady wind, I heard a rapping at the employee entrance door. Intrigued, because the door wasn’t locked, and anyone having business there would have just walked in, I went to see what was up. My midnight caller turned out to be a truck driver – wearing nothing but a long sleeve shirt and a quilted vest. He said his truck had broken down a couple of miles up the road and he was walking into town! He just wanted to warm up a bit before continuing into town. I couldn’t believe that he wasn’t frozen. I got him to accept a cup of coffee and offered to call a cab. He thanked me for the coffee, declined the cab, and after warming up for about 15 minutes, he left to walk the rest of the way into town.

They’re watching me
Miles City was a small town, and aside from a small VA hospital, there weren’t many federal government employees in town. During orientation the facility manager pointed this out and told us that as a result, many people would just see us as the government, and we needed to keep that in mind in our interactions in the community.

One of those interactions was with an older lady that would call every month or two. She’d apparently been doing this for some time because after I first talked to her, the other guys all knew about her, it was kind of a “rite of passage” to have to deal with her. She was looking for help because “they” were watching her and tapping her phone. She was unclear about who “they” were but when we suggested that she call local police, the sheriff or the FBI she’d tell us that she couldn’t because they were all in on it.

She eventually quit calling. We always wondered if “they” got her.

The story behind the story
One really hot summer Saturday afternoon a C310 from Glasgow landed and parked right in front of the Flight Service Station. The plane belonged to 3 brothers who had businesses in Glasgow. I didn’t know that much about them but believe one had a beer distributorship, one was a grocer, and the third had a furniture store. We talked to them now and then but they didn’t fly all that often and I’d never met them. As they got out of the plane one of them got a small suitcase or briefcase out of the baggage compartment and another pulled out a case of beer.

They came into the facility and we talked about the expected weather for the rest of the afternoon, and they said they wanted to leave the plane where it was parked. That was no problem and they left to hop in a car that had pulled up in the parking lot. After they got out the door I noticed that they’d forgotten the beer so ran out and told them. They responded, “What beer?”

Since we had only four specialists all that summer, the beer was easily divided, but I couldn’t imagine why they’d do that. We just didn’t deal with them that much and when we did it was all very business-like with no sense of familiarity or friendship. It was nearly 10 years before I got an answer.

In 1987 or 1988 I was in Watertown, SD FSS as the area supervisor and was looking through old documents in the files when I found a report of a successful aircraft orientation/save accomplished by a Watertown specialist. It involved a C310 enroute to Glasgow, MT, that had gotten caught in an area of rapidly developing thunderstorms and became disoriented. The specialist determined the location of the aircraft and assisted them in finding a suitable airport to land. I cross checked the tail number and it matched up with the businesses in Glasgow!

The Crew Car
Miles City is located in farming and ranching country. One of the implement dealerships left a courtesy car at the airport and we kept the keys in the FSS. Our instructions were that it was primarily for farmers and ranchers who flew in for parts, but we could let it out to anyone who asked use it.

It was a well-used, 10-15-year-old Dodge that ran OK but had transmission problems and sometimes brake problems. I recall one pilot bringing it back and reporting that the car had nearly killed him. The transmission was slipping and he said he was crossing the railroad tracks when it happened. A train was coming and he was barely able to lug it out of the way!

One day in late August the keys disappeared. It had been used a lot (it was harvest season) and no one knew for sure exactly when the keys disappeared, so we figured someone had forgotten to return them but had no idea who it might have been.

Winter set in and the car was literally buried under a giant snow drift, made worse by the snow berm the plows had pushed up against the car. Then one day in February, someone found the keys while cleaning out a drawer. We called the dealership and told them we’d found the keys, thinking they’d be happy to know we found the car and that it would again be usable when the snow melted. Temperatures were well below zero and it didn’t seem like there’d be any immediate need to dig it out or to get it running.

About an hour later we were surprised to see 3 guys show up with shovels, and watched as they began digging the car out of the snow drift. As we watched we speculated on whether they planned on towing it away or what they had in mind. Since it hadn’t been moved for close to 6 months we figured it was pretty much dead.

Once they had the snow mostly cleared off one of the guys came in, got the keys, climbed in the car, and to our amazement, the car started on the first try. They finished digging through the drifts while the car warmed up and drove it away. And they never brought it back.

Harry
Harry was a retired Air Force Colonel who flew for the FBO in Miles City and also was the contract pilot for a C421 owned by a trucking company in Miles City. The first few times I encountered him I thought he hated me. He’d come into the flight service, refuse any help, and look at weather printouts and charts on his own, and then fill out his own flight plan. Finally one of the “old timer” specialists, who he talked and listened to, clued me in that it was just that I was a new guy and would have to earn Harry’s trust.

Harry lived across the street from our Airway Facilities manager, George. One day I was with another specialist, Rick, and we had to stop by George’s house so Rick could pay his daughter for babysitting. After that was taken care of George, Rick and I were sitting on the front steps drinking a beer when Harry came home. He invited us over for “a drink” that turned into a long evening on his patio in the back yard.

As the evening wore on one of George’s kids came over and took George home. Then Rick laid down on the picnic table and went to sleep. Harry and I continued drinking and telling stories – his about the Air Force, mine about the Navy.

After that night Harry treated me like the other “old timers” and we had a great relationship.

There was a VA hospital in Miles City and from time to time the Miles City FBO would fly patients to other hospitals. On one occasion, Harry was taking a patient to Salt Lake City, and while he was filing his flight plan, he invited one of us to ride along. Somehow I was able to go. The patient had some kind of infection in a leg and Harry said he’d already had a couple of operations and it was likely they would have to amputate the leg. The guy was, under no circumstances supposed to get on his feet.

When we arrived in SLC the ambulance that was supposed to meet us wasn’t there and Harry told me to stay with the plane and patient while he went to see what was going on. Well, I had to pee like a racehorse and it seemed like it took forever before Harry got back. I presumed he had, among other things, taken the time to relieve himself before returning to the plane.

When he finally got back he was disgusted that the ambulance hadn’t even been dispatched and he said we needed to get the patient up so he could use the rest room. We walked him into the FBO so he could take care of business and by the time that was done the ambulance had arrived. I immediately made a bee line to the rest room and surprisingly Harry was right behind me… he also had put the patient ahead of his own needs!

At Christmas time, the first year I was in Miles City, we all received a fifth of whiskey. I was told that it “just showed up” and no one really knew where it came from. I thought maybe the manager bought it and didn’t want it to be public knowledge. During November of 1976, my second year at MLS, I overheard Harry questioning the facility manager about how many specialists were working at Miles City. A few weeks later a case of whiskey was found on the doorstep with the same number of bottles as specialists. It turned out that the trucking company that Harry flew for had him drop the stuff off on our doorstep each year. In 1977 when one of our specialists (who didn’t drink) was being transferred he gave me four bottles of whiskey that had never been opened!

The aviation community is pretty small
One winter day I was off duty and running errands in Miles City. The weather was weird – there was no wind in town but the sky was obscured by blowing snow and ice crystals. Since I had nothing better to do I decided to drive up to the airport and see what was going on. Miles City is located on the Yellowstone River and the airport is on the bench about 300 or 400 feet above the town. As soon as I got to the top of the hill I encountered very strong winds and near blizzard conditions due to blowing snow.

As I drove onto the airport I noted the Frontier Airlines commuter, a DH6 Twin Otter, taxing in to the ramp from the runway. When I walked into the facility I saw the plane was turned around and was taxiing back towards the runway. It turned out that the movement surfaces were so icy and the wind was so strong that the plane couldn’t steer and kept turning into the wind. They finally brought a fire truck out and tied onto the nose gear so they could get to the ramp.

There were a handful of light aircraft that had gotten caught by this storm and I think it took a couple of days before they were able to leave. One night during this period I was eating out at one of the local restaurants and overheard the people at the next table talking about their bad luck getting stuck in the storm. One made the comment, “I can’t believe we have to spend another night in Miles City.”

30 years later, after I’d retired from the FAA, I was working as a dispatcher for a charter company in Wenatchee, WA. One day I was talking with one of our mechanics (who was also a pilot) about experiences while working in Flight Service and I related the above story. It turned out that he was one of the pilots stuck in Miles City that week and remembered making that comment at the restaurant!

A lot can happen if 6 weeks
In the late spring of 1978 I was given a temporary promotion to fill in as acting manager for about 45 days, from the time one manager departed until the new manager arrived. I was surprised, as I had less than two years of experience, but appreciated the confidence they had in me. It was spring going into summer, a fairly busy time, and it sure seems like a lot of stuff happened.

I’m a star
The population of Miles City was around 9,000 people but we had a local TV station operated by an old guy, Dave, and his wife. They would hire young people trying to break into broadcasting and pay them next to nothing to handle the camera duties. I was told it was the smallest NBC market in the country. They only had one camera and would use it in the studio for news and local programming, and then when network programs were airing they would take the camera out to record things.

I’d first met Dave during the spring of 1976, with less than a year experience in Miles City. I was alone one evening when someone walked in the back door and went straight into the maintenance work area. I went back to see who it was and found this guy removing one of the oscilloscopes from the equipment rack. He told me who he was and that the manager of Airway Facilities let him borrow equipment to tune the transmitter for the TV station! I figured it must be true, who could make that up? It was true!

While I was acting manager they called and asked to do a program on the FSS. I cleared it with the Regional Office, and one day Dave arrives with his camera and camera man. After some shots around the facility and a short discussion they started to interview me on camera. While we were talking the commuter (Frontier Airlines) called inbound. As soon as the call came in Dave jerked the microphone away from me and tried to catch the airport advisory being given by the in-flight specialist. Dave then began interviewing the specialist who was explaining where the aircraft was and what an airport advisory was. While they were talking the aircraft called again so I grabbed the side mic to answer them and, immediately, the TV mic was back in my face.

Dave then asked where the aircraft would land and I advised they intended to land on runway 12 (the approach end of the runway is the furthest place on the field from the FSS) which was straight away to the west-northwest but about a mile away. Dave tells his cameraman to move the tripod closer to the window so they can get a shot of the aircraft landing.

In the finished program, at this point the picture went all bumpety-bump as the camera was moved, then focused on the horizon to the northwest. If you know what to look for you could just see a speck as the aircraft landed, and then as it taxied, it turns into an airplane.

The good news (for me) was that apparently no one watched the program. At least no one ever mentioned that they saw (or laughed) at me when I was on TV.

There’s nothing you can tell me
A couple of times I ran into specialists who had an especially high opinion of themselves. One such guy was assigned to Miles City in 1977. He went through training in Oklahoma City and returned to the facility for final check out and sign off during the period when I was acting manager.

In those days it was virtually a requirement that prospective employees had some background in aviation. They usually got a month or longer facility orientation prior to receiving a class date at the academy, and the training at the academy generally produced a specialist who was “ready to go” as soon as they returned to the facility. There was a legality that new specialists take weather observations under supervision for 2 weeks before they were eligible to be “signed off” and work alone. Whether we had an exceptional group, or were just lucky, all of the guys I worked with were signed off at the 2-week milestone.

Roy had been an Air Force controller and a tower chief and the FAA was a second career for him. During the orientation and post academy training he always had presented the attitude that our facility was small potatoes compared with what he’d done and there was nothing we could tell him that he didn’t already know.

He was very proficient and capable and as soon as the two-week weather observation probation had elapsed, I sign him off to work alone. The slot in the schedule that he went into meant that he’d be working his first shift alone from 4:00 PM to Midnight on a Friday. And it just so happened it was “Bucking Horse Sale” weekend.

One of Miles City’s claims to fame is the annual Bucking Horse Sale in the spring of each year. It’s essentially a big time rodeo where rodeo producers come to evaluate and buy bucking horses for the rodeos they will produce during the year. It’s also a huge party.

One of my co-workers, Rick, and I had spent the day at the rodeo and returned to my house about 6:00 PM to get cleaned up with the intention of doing some bar hopping. We figured that as long as we were near a phone we should see how the new guy was doing. Rick made the call and what I heard was sort of like, “How’s it going?…really?…uh ha… geeze…damn… oh geeze…OK.” CLICK… “Jim, put a shirt on we have to go to the airport NOW!”

When we got to the airport we found him overwhelmed. There was an aircraft who was unsure of his position and requesting assistance, 2 aircraft overdue into our airports, a message from another facility requesting information on an aircraft that was overdue on a flight from our area, and a good number of aircraft in the airport area. Both phones were on hold with pilots waiting to file flight plans, several flight plans that needed to be filed, and 2 pilots were at the counter waiting for service.

I can’t recall ever hearing of anyone having that much happen at once and getting that far into a hole. With Rick and me helping it took a little over an hour to get everything back to normal.

The guy never had an “attitude” the rest of the time he was at Miles City and, in fact, went on to be one of the better instructors at the FAA academy.

I want to quit
A couple of weeks after Roy signed off another new specialist named Bob, who returned from the academy and did his 2 weeks taking weather observations, I signed his card. He was also retired Air Force and had been a tower chief. He was a really nice guy and while he knew his stuff he never assumed he knew everything. His first week working shifts alone was uneventful and I wasn’t aware of any problems.

Then one evening he called me at home and asked if he could stop by. When he came to the door he told me he wanted to resign and handed me a completed government form. I’d never seen the form before but I guess it was the form that you used to resign. I begged off saying that as the acting manager I had no idea what to do with something like this and asked if he would consider waiting until the new manager got to town in a little over a week.

He was agreeable to that and we never did talk about it at work.

When the new manager arrived I had a few things to talk about – as the next story will illustrate – so I arranged a meeting as soon as he got to town. We met in the lounge at the motel where he was staying and over a couple drinks I filled him in on people and events. He said he’d talk to Bob at the first opportunity. Bob, in the meantime, had changed his mind so by the time they had their meeting, there was nothing to talk about. I still had no idea what had happened.

Several months later Bob and I were working together and he told me that when he first started he was scared to death that something would happen when he was on shift alone and he wouldn’t know what to do. I asked him why, after being a tower chief, he would feel that way, and he said that even as a tower chief there was always an officer on duty who was responsible for tower operation and decision making. He said it took a few weeks before he realized how much he knew and felt confident. While he didn’t say it, I believe that asking him to wait before resigning had been exactly the right thing to do.

How much is enough?
A specialist had started a few months before I became acting manager. He was Hispanic and had been a controller at Denver Center but decided he’d rather work in Flight Service. He was a little “different” and on one occasion he told me the reason he left the center was because they wouldn’t let him sleep on the midnight shift. Interestingly, I ended up training with him and on the midnight shift and even in that position he seemed to have a hard time staying awake.

So anyway, as acting manager, I came to work one morning and learned that he had gone to Denver on his days off and had called a Miles FSS specialist during the midnight shift to let him know that he wouldn’t make it in for his 4:00PM shift that evening. It seems he had ridden his Harley to Denver (a little over 500 miles) and had developed a boil on his rear end that needed to be lanced. He assured the specialist that he’d be there the next day for his 2:00 PM shift. I juggled staffing to cover his shift.

The next morning I came in and learned that he’d called again and, while he had the boil lanced, his butt hurt too bad to ride his bike so he wouldn’t be in for his shift. He assured the specialist that he’d be in the next day for the 8:00 AM shift. I didn’t need to adjust the schedule but the evening specialist had to work alone and I was starting to get a little upset.

The next morning I came in and learned that he’d called and said that it still hurt too bad to ride, but he’d be in for his 6:00 AM shift the next day. I was starting to get really steamed. He’d gotten to the point that he didn’t have any sick leave or vacation time left – in fact he’d used advanced sick leave to the point that he couldn’t earn enough to catch up in the calendar year. I found a management handbook and started looking at options.

Sure enough the next morning I came in to find that he hadn’t shown up for his 6:00 AM shift. He had called to say that he’d overslept and since he couldn’t get to Miles City in time he’d just ride up during the day and work his midnight shift.

Not knowing what procedures to follow or what options I had, I called the Regional Office for guidance. Initially it was suggested that I make him Absent Without Leave (AWOL). Then the guy at the RO had a thought and said, “Isn’t he the Hispanic guy? We’d better just call this Administrative Leave.” This of course meant that he was given the time off without being charged for any of it.

A few weeks later, when the new manager arrived, he had a talk with the specialist. I don’t know what was said but the guy’s performance improved noticeably and there were never any attendance problems the rest of the time I worked at Miles City.