Blogging the FARs: Pilot in Command

A definition from FAR Part 1.1.

According the FAR Part 1.1: General Definitions:

Pilot in command means the person who:

(1) Has final authority and responsibility for the operation and safety of the flight;

(2) Has been designated as pilot in command before or during the flight; and

(3) Holds the appropriate category, class, and type rating, if appropriate, for the conduct of the flight.

How this Might Appear on Your Oral Exam

This seems like pretty simple stuff, but it always appears in an oral exam in one way or another. The examiner won’t ask for the definition. Instead, he’ll ask a question that refers to the definition, something like: “Who has final authority over the aircraft?” or, more slyly, “If the tower tells you, the pilot in command, something to do and you think it’s dangerous, should you do it?” The answers to those questions are the pilot in command (that’s you, if you’re taking the check ride) and no, respectively.

FAA examiners are very sly people. If they sense any doubt in your mind, they’ll push harder to get you to give them the wrong answer. The next question might be, “Are you sure? The tower is telling you to do it. Don’t they have authority?”

Don’t fall for this! Remember that when you’re pilot in command, you are the boss of the aircraft. But you also need to remember that if you don’t follow an ATC instruction, you better have a damn good reason why you didn’t and that reason better be somehow related to safety.

This is also covered in Part 91.3: Responsibility and authority of the pilot in command:

(a) The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft.

(b) In an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule of this part to the extent required to meet that emergency.

(c) Each pilot in command who deviates from a rule under paragraph (b) of this section shall, upon the request of the Administrator, send a written report of that deviation to the Administrator.

Stating the Obvious

The Part 1 definition also suggests that you can’t be a pilot-in-command until you qualify for it. For example, an airplane pilot can’t be a pilot in command of a helicopter until he/she gets a helicopter rating. And, oddly enough, a 5000-hour helicopter pilot who has been flying all kinds of helicopters but has never had any training in a Robinson R44 could not be a pilot in command of that helicopter. Why? Because there are additional regulations (specifically, SFAR 73) covering that make and model of helicopter.

The best thing to do before flying a different aircraft is to make sure you you have the rating(s) you need to fly it. When in doubt, ask a flight instructor, the company you may be renting from, or the FAA. My advice is to always fly with a flight instructor for at least 30 minutes in any different kind aircraft you’re flying for the first time. And make sure he/she signs off in your logbook before you go solo, just in case there is a problem. You (or your next of kin) want to be able to prove that you had some training in this lawsuit-happy country we live in.

Other Stuff to Check and Remember

And don’t forget the other Part 61 rules which also apply here, including qualifications, currency, etc. And the Part 67 medical requirements.

(To me, that’s the biggest problem with the FARs; they require you to look in a half dozen places just to get the answer to a question.)

By the way, the responsibilities of the pilot in command are also covered in the AIM Chapter 5, Section 5-5-1b.

Blogging the FARs: An Introduction

The FARs for mere mortals.

As a Single Pilot Part 135 operator — in other words, a commercial pilot allowed to do on demand air taxi and charter flights; more later — I’m required to take an annual check ride with an FAA examiner. The check ride isn’t just a flight to prove I can perform the required maneuvers. It’s also an oral exam that lasts 1 to 2 hours and is designed to confirm that I know my aircraft, my operating rules, and the FARs.

About the FARs

FAR stands for Federal Aviation Regulations. Technically, the regulations are really Titles 14 and 49 of the Code of Federal Regulations, so some very few people might refer to them as 14 CFR or CFR Title 14 or some other combination of that information. Most people don’t. Most people just call them the FARs.

If you’re reading this in another country, you likely have rules and regulations like this. I don’t know what they’re called or what they contain. And if you are reading this as a pilot flying in another country, don’t depend on what you read here to correspond to your country’s rules. It might be interesting, however, to get comments that explain how something differs in your country, so don’t be shy about sharing what you know.

Blogging the FARs

Like most pilots’ I don’t know the FARs by heart. I don’t even know the ones I’m supposed to know by heart. I simply know that regulations exist and where I can look them up in the big, fat book that’s revised annually. And, of course, I do know the gist and meaning of the regulations that affect my operations on a regular basis.

In an effort to

  1. refresh my memory about the regulations I’m supposed to know,
  2. translate those regulations, which are written in FAA-dialect legalese, into a language I’m more familiar with, like plain English,
  3. provide myself with reference material for future study,
  4. provide site visitors interested in aviation with some information they might find useful, and
  5. generate a comments-based discussion about some of the FARs and why they’re important, stupid, good, bad, or whatever,

I’ve decided to write a series of blog entries that explore the various FARs.

If you’re not a pilot, you may not find this too interesting. I understand. Many pilots don’t find this too interesting, either. But they are the rules and we do need to be familiar with them. If you have any interest in aviation and how the system works to remain safe, you might find some of these posts very interesting. If so, enjoy. And ask questions in the Comments if you need clarification.

If you are a pilot, please remember that I’m not an expert. I read FAA-dialect legalese no better than the next guy and there is a chance that I might misinterpret something. If you think I got it wrong, speak up in the Comments area for the article in which the error appears. But please do back it up with some other reference so I can confirm the correction. If you have more to add about a topic — especially stories about how that topic affected you — please share your experience. We can all learn together. Personally, I learn better from stories than from boring 1000-page books written in legalese.

All of these articles will appear in the Flying category of this site. If you just care about flying and not about the other things I write about, I recommend that you subscribe to the category with an RSS reader, the live bookmarks feature of Firefox, or some other subscription method. (You can also subscribe to get new content automatically by e-mail.) That’ll filtering out my geeky computer stuff and my occasional political rants.

The FARs I’ll Cover

I’m not going to cover all of the FARs here. I’m only going to cover the ones that directly affect my operations, the ones I’m likely to be asked on my check ride. These are the same one you might be asked on a private, commercial, or Part 135 check ride. And of course, being a helicopter pilot, I won’t be dealing with any airplane-only regulations. In fact, if you’re a pilot and you read these, you’re likely to get a good picture of how airplane and helicopter operations differ. Don’t worry; I’ll make a special note if anything I write about is helicopter-specific.

Generally speaking, I’ll be covering material from FAR Parts:

  • 1 – Definitions and Abbreviations
  • 61 – Certification: Pilots, Flight Instructors, and Ground Instructors (I’ll concentrate on Pilots)
  • 67 – Medical Standards and Certification
  • 71 – Designation of Class Airspace Areas; Service Routes; and Reporting Points
  • 73 – Special Use Airspace
  • 91 – General Operating and Flight Rules
  • 119 – Certification: Air Carriers and Commercial Operators
  • 135 – Operating Requirements: Commuter and On Demand Operators
  • SFAR 73 – a Special regulation for Robinson helicopter operators

I won’t be covering them in this order. I’ll be covering them in the order I study them in. And the articles I write are likely to appear here weekly over an extended period of time, so don’t expect to read it all next week.

Some Additional References

If you’re interested in FARs, you’ll likely find some of the following reference material quite useful:

  • FARs online. You can read the current version of the FARs on the Web on the FAA’s Web site. This should be the most up-to-date version of the FARs available for free.
  • FAR/AIM 2007: Federal Aviation Regulations/Aeronautical Information Manual (FAR/AIM series)AIM or Aeronautical Information Manual. This is the plain English text that actually explains the rules and provides additional how-to information for pilots. Every U.S. certificated pilot should have and read this book. Normally, when you buy a book containing the FARs, the AIM is appended to it. So what you’re really buying is a FAR/AIM. My understanding of this document is that the text is prepared by the government and is in the public domain. A variety of publishers print books of the information and some add illustrations and supplemental text to the AIM part of the book. So you’ll find several versions of the book. I buy the ASA version shown here for financial reasons; I’m required to buy it every year and usually get an offer to get it sent to me for under $15 as soon as it’s printed (normally late in the previous year). But there are other versions out there and you can even buy the AIM as a separate book, without the FARs.
  • FARs in Plain English by Phil Croucher. This book attempts to do what I’m doing here, but for most of the FARs. I have this book and don’t really care for it, primarily because some of the rules I need are omitted and the book isn’t updated regularly. (The FARs are updated every year.) The book is also quite expensive for us poor pilots, retailing for $44.95.

Comments?

Please do share your comments about this little project. The Comment link is below. I’d also be interested in learning about other online resources, as well as opinions of the ones listed here.

A Professional Pilot?

I’m not impressed.

Yesterday, my friend Ray flew me down to Mesa, AZ, in his airplane so I could pick up my helicopter, which was down there for its big annual inspection. While we were taxiing from Ray’s hangar to Runway 23 in Wickenburg, we heard the following exchange between two pilots on Wickenburg’s frequency:

Premier 1-2-3 (not the exact call sign; Premier is a small “corporate” jet): Wickenburg, this is Premier 1-2-3. Is there anyone there?

PanAm 5 (not the exact call sign; PanAm is a flight school based at Deer Valley Airport (DVT) that does a lot of practice landings at Wickenburg): This is PanAm 5 at Wickenburg.

Premier 1-2-3: Can you tell me the winds down there?

PanAm 5: The winds are shifting around a little, but they’re mostly out of the southwest at about 5 or 6 knots.

Premier 1-2-3: Oh, great. Thanks….So that means you’re using Runway 26 down there? Is that the runway number?

PanAm 5: It’s actually Runway 23.

Premier 1-2-3: Oh, thanks. We don’t have any approach charts or anything for Wickenburg so we’re kind of flying by the seat of our pants.

Yes, he really said that.

The radio went quiet for a few moments, then another pilot called to say he was 5 miles north, inbound for landing.

Premier 1-2-3: Premier 1-2-3 is about 3 miles south. We’ll be making left traffic for Runway 23.

Pan Am 5: Actually, it’s right traffic for Runway 23 at Wickenburg.

Premier 1-2-3: Okay. Thanks. Right traffic for Runway 23.

At this point, the FBO attendant came on the radio to provide wind and unofficial altimeter setting information. (It’s a good thing the altimeter setting is unofficial, since it’s off by nearly 100 feet.) She asked if the jet wanted fuel on landing and he told her he didn’t, that he was just dropping off some passengers.

We were holding short behind a PanAm plane when the jet came in, zipping past us. He was nearing the other end of the runway where the terminal was when the FBO woman came on again to ask if he knew where to park to discharge his passengers. He told her he’d been there before, then advised everyone that he was off the runway.

Ray and I had been discussing this jet pilot’s lack of professionalism while we were waiting. Both of us knew that one of a pilot’s responsibilities for a flight, as stated in Part 91 of the Federal Aviation Regulations (FAR’s). From Section 91.103, Preflight Action: “Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight.” Surely that must include runway numbers (which are determined by magnetic course headings) and traffic pattern information. This information is available on the Sectional Chart and in the Airport/Facilities Directory, both of which are required to be on board for commercial flights. They’re also available on the Web on various airport information Web sites and on the FAA’s Web site. Heck, I’m a helicopter pilot and I’m supposed to avoid fixed wing traffic when I land at airports, yet I usually know the runway numbers and traffic pattern information just so I can get an idea of where planes might be.

This guy simply hadn’t done his homework.

The PanAm plane in front of us took off. Ray rolled onto the runway. As the PanAm plane drifted to the north of the centerline (likely because of the wind), we took off and headed south.

I’ve since given the exchange a bit more thought. What if the Jet was arriving after 4 PM, when the FBO was closed, and the traffic pattern was empty. Where would he have gotten his information. He was only 5 miles out on his first call; would he have had time to look at his chart or A/FD? Or would he have assumed Runway 26 from memory, made a left traffic pattern low over the homes on the southeast and east sides of the airport, and adjusted his approach only when he realized he was on the wrong heading — 30° off? Approaching at a heading of 260 would have put him right over the homes on Broken Arrow Road — the homes of people already complaining about noise now that the runway is 1500 feet closer to their homes. Would his action have had a long-term impact on the airport?

The point here is, all pilots are responsible for gathering information about the flight — including the airport they intend to land at. This guy acted irresponsibly and was fortunate enough to have people on the ground that could provide him with the information he needed.

But as any pilot knows, you’re not always lucky. You need to do your homework before you get on board and start the engines.

Helicopter Safe Flight Altitudes

How some people try to make up — and enforce — FAA regulations.

Yesterday, Mike and I flew out to Wenden to give helicopter rides to our friend, Celia, and her family. Wenden is a farming community primarily inhabited by Mexican farm workers. Its a tiny desert town in what must be a fertile valley. Wells pump water into irrigation canals and the entire area is surrounded by a patchwork of farm fields. This time of year, the cotton harvest is over and big square bins of cotton line one field after another. Most of the fields are already plowed and readied for their next harvest; a few are even planted.

A straight-line route between Wickenburg and Wenden takes me right over the top of an airpark called Eagle Roost. Eagle Roost was the brainchild of a man with vision. He bought a section of land — that’s a mile square — in Aguila, another Mexican farming community. He laid in a north-south runway, paved it, and sold 5-acre lots all around it. Back when I first started coming to this area about 10-12 years ago, the lots were going for $8,000 each and the place wasn’t very impressive. They’re now worth considerably more, and most lots have been built up.

Eagle Roost is the home of mostly retired people who are (or were) pilots. Like Wickenburg, half the population disappears during the hot summer months. Although the development isn’t bad, the town of Aguila has nothing much to offer. There are one or two small convenience stores, three restaurants, and a motel. Most people speak Spanish. On weekday mornings men gather in predetermined places, waiting to be picked for work crews. On Tuesdays (I think), there’s a farmers market. The place has terrible flies during cantaloupe harvest. There’s nothing much to do, so most Eagle Roost residents seem to do a lot of internal socializing, gossiping, and drinking. When they need something, they drive 25 miles east to Wickenburg or about 75 southeast to Phoenix’s west valley.

We used to have friends out there, but after a disagreement with one of them, another one told me he didn’t want to be friends with me anymore. (And no, he isn’t a third-grader.) No loss, as far as I’m concerned.

Anyway, whenever I fly from Wickenburg to points west, like Wenden, Salome, Vicksburg Junction, or Quartzsite, I usually fly right over the top of Eagle Roost. I’ve been doing it since I got my first helicopter, back in October 2000. More than five years now.

Don’t get me wrong — I don’t fly out there often. I don’t have reason to. There’s not much west of Wickenburg to fly to. As I mentioned elsewhere, Wickenburg is on the edge of nowhere. West of there is nowhere. But I definitely do it at least a few times a year. In fact, I did it a few weeks ago when I flew out to Quartzsite to research possible landing zones for a gig there.

Now in case you don’t know, helicopters fly lower than airplanes. In fact, there’s no set minimum altitude for helicopter flight. When I’m in Wickenburg, in or around town, I normally fly at 500-700 feet above the ground, but when I’m out in the desert, I sometimes fly lower. This is so for two reasons. The main reason is so I can see the stuff I’m flying over — range cattle, people off-roading out in the desert, the trickles of water in a spring-fed canyon creek. If I wanted to get from point A to point B without seeing what I was flying over, I’d fly an airplane. And that brings up the second reason I fly low: to avoid airplane traffic.

It’s a common joke among helicopter pilots. You mention that you flew at a certain higher-than-usual altitude someplace and a fellow helicopter pilot says, “Why the hell were you all the way up there? That’s where the planes are.”

We also joke about nosebleeds.

If you’ve been following along, you’ve probably guessed by now that I fly over Eagle Roost — and most other places I fly over — at less than 500 feet above the ground. I did it yesterday, on the way out to Wenden.

Now although very few of Eagle Roost’s residents are active pilots, there are a few who do actually own planes and fly them. So I treat Eagle Roost about the same as I treat Wickenburg. It’s a Class G, uncontrolled airport. Common courtesy — but not FAA regulations — dictates that you listen in on the airport frequency as you approach and depart the area and make one or more radio calls to announce your intentions and solicit responses from other pilots in the area. So, on the way west, I tuned into Eagle Roost’s frequency about six miles west of Wickenburg. I made a radio call as I passed south of Forepaugh, a historic airport that seems to have had its name wiped from aeronautical charts.

A minute or two later, I heard a call from someone at Eagle Roost departing runway 17 with a downwind departure. I had to translate that into direction. Helicopter pilots don’t have much use for runways so we don’t pay much attention to runway numbers and directions. It takes thought to decipher what the pilot had said. Since runway numbers correspond with compass directions, the pilot was taking off on the runway that pointed roughly south. Downwind was the direction parallel to the runway, but going in the opposite direction he’d taken off. That meant he was departing to the north. We were east and still pretty far out, so we were no factor. Mike and I actually discussed this thought process yesterday, comparing notes about how airplane and helicopter pilots think.

There were no more calls from Eagle Roost and no more traffic. I made a call three miles east, giving my altitude and intentions: transitioning to the west. Then I made another call when I was over the airpark. Then we were west, speeding along at a healthy 110 knots to our destination, still 25 or 30 miles west.

I circled the town of Wenden to find Celia’s street. She lives in a house between two farm fields, off Alamo Lake Road. I followed Alamo Lake Road with my eyes, saw her house, judged the wind from a flag, and decided to come in from the west. I lined up with an east-west road that ran right past her house. It was a farm road, made to give access to the fields. But it was Christmas Eve day and a Saturday, so the fields were empty. No one was using the road. I landed in a huge cloud of dust about 50 yards from her front door, where she and her family had gathered when they first heard us coming. The breeze from the east was pretty stiff, so the dust cloud swept past me when I idled down, so it didn’t actually reach where everyone was standing.

Celia Takes a Helicopter RideI gave four rides, each with three people on board. It was Celia and her daughters and their husbands and kids. Mike handled the ground crew work. I gave short rides — there’s not much in Wenden to see — and everyone really seemed to enjoy it. I gave helicopter toys to the little kids. The dust was incredible on my takeoffs and landings and my fears were confirmed when I shut down in Wickenburg later on: a little more paint had been sanded off the blades.

When we were finished, Celia invited us in for burritos. But I had another charter at noon and wanted to get back to Wickenburg. So Celia gave Mike a package of burritos and he climbed on board. Soon we were on our way back to Wickenburg.

Of course, we flew over Eagle Roost again. We’d been on the same frequency since we’d left Wickenburg and there was no one talking on the radio. Mike and I kept an eye out for planes, as we usually do, and didn’t see any. I made my first radio call about 3 miles to the west and didn’t hear a thing from anyone in the area. But when I made my second call when I was overhead, the radio suddenly came to life.

“When you fly over the airport, fly above traffic pattern altitude,” came a man’s voice.

“Zero-Mike-Lima is a helicopter,” I told the person who’d called. “Helicopters fly below traffic pattern altitude.” No lie there.

“Helicopters have to follow the rules, too,” the voice said. If there hadn’t been an edge to it before, there was now.

“I’ll have to look that one up,” I replied.

“You do that.” Now definitely nasty. “The FAA would be interested.”

“Then I’ll ask the FAA,” I replied, thinking I might send my Part 135 contact at the Scottsdale FSDO an e-mail if I couldn’t find the rule. (Some people are afraid of the FAA. I’m not. All of my dealings with the FAA have been very fair and everyone I’ve worked with at the local FSDO has been very helpful and informative. So if this guy was trying to scare me, he wasn’t succeeding.)

By this time, I was about a mile or two to the east. The man, who Mike and I figured was on the ground because he didn’t provide an N-number, didn’t say anything else.

I looked at Mike. “Is there a rule like that?” I asked him.

“I don’t think so,” he replied.

“I’ll look it up,” I repeated. I have the 2006 FAR/AIM in my hangar. And we continued east, with the episode tucked in the back of our minds.

Unfortunately, that wasn’t the end of it. I was sitting with Mike and a few other pilots at a picnic table at Wickenburg airport, waiting for my noon charter and eating burritos when my cell phone rang. I looked down and saw a familiar phone number. When I answered it, I heard the voice of the Eagle Roost idiot who said he couldn’t be my friend all those years ago.

“I have absolutely no desire to talk to you,” I said. And I snapped the phone shut.

It started ringing again almost immediately. I pushed the button that would silence it. Then again. Sheesh! Some people just don’t get it. I turned the phone off.

We talked to the pilots we were with about the “rule” we’d been told about while over Eagle Roost. Mind you, we were sitting with three other active pilots — the kind that actually fly — and none of them had ever heard of such a rule for an airport in Class G airspace, let alone a private airpark that doesn’t even appear on current GPS maps.

I turned the phone on a while later and there were three messages on it. I let Mike listen to them. Two were from potential customers. The other was from the idiot at Eagle Roost. For some reason, this guy has become the “Godfather” of the airpark and everyone goes to him with their problems. And although the original cause of the breakup of our friendship years ago was because I hadn’t “minded my business” when his buddy was sleeping around behind my friend’s back, this guy has no problem minding other people’s business. He’d called to talk to me about flying over Eagle Roost. Supposedly, the guy who’d talked to me on the radio swore that there was another plane in the pattern. He claimed I was being dangerous and I’d been belligerent. And this former friend of mine had been assigned to talk to me about it. The hell with that.

One thing was already pretty obvious: the guy was lying about the plane, probably to cover up the fact that he didn’t know what he was talking about. I have four pieces of evidence to prove it:

  1. Neither Mike nor I, experienced, active pilots who were sitting in the front seat of an aircraft with virtually unlimited forward and side visibility, did not see another aircraft, even though we were both looking.
  2. No other pilot made a radio call. And yes, I do realize that the pilot could have been operating without a radio, but then who’s being safer: me with two radio calls or him with none?
  3. If the guy on the ground was so concerned about our altitude because of other traffic, why didn’t he mention the other traffic?
  4. How did the guy on the ground know there was other traffic if he was inside listening to his radio and the phantom pilot hadn’t made a call?

My charter passengers arrived right about the time Stan had the espresso machine fired up. I did two charters while everyone else went to Stan’s for a latte. By the time I was done an hour and a half later, Stan had closed up shop and most of the other pilots had gone home. I settled up with my passengers and locked up the helicopter on the ramp. I was schedule to fly Santa to a remote ranch at dawn on Christmas morning.

Mike said that the pilots gathered at Stan’s had discussed the “rule” at length. They all agreed that there was no such rule and that I hadn’t done anything wrong.

We had some repairs to make on our airport golf cart and Mike left to get the parts. While I was waiting, I washed the chicken dust off my car and spent about 20 minutes going through the FAR/AIM for the “rule.”

I found the helicopter altitude rule I’d already committed to memory: Helicopters may operate at an altitude lower than airplane minimum requirements as long as operations do not pose a danger to persons or property on the ground. This is paraphrased, of course — I don’t have the FARs in front of me right now. But this is the rule we’re taught and we discuss it at length. Although it seems like it’s a free pass to fly wherever you want, if something does happen and you have an emergency landing and someone on the ground gets hurt, the FAA could always say that you were not operating at a safe altitude. So safety is always the primary concern when choosing a minimum altitude. For a helicopter, that means operating within the safe area of the height-velocity diagram, a document that establishes safe altitude and airspeed combinations to make a power-off landing. Of course, terrain has a lot to do with it, too. There needs to be a flat open space within range to land. Like a farm field? Or a runway at an airpark? So as far as that rule was concerned, I was operating at a safe altitude.

I also found another helicopter rule that was pounded into my head when training: helicopters are to avoid the flow of fixed wing traffic. This is the rule that keeps helicopters low. In fact, whenever I operate in a Class D airspace — that’s an airport with a control tower —-and I want to approach my landing zone or cross over the top, I’m directed to stay below the traffic pattern altitude. Even when crossing over the top — and I can’t tell you how many times I crossed over the top of Scottsdale while working on on my private helicopter rating. Just the other day, when leaving Scottsdale Airport, the tower cleared me to depart and directed me to remain below 2,000 feet — or below the traffic pattern altitude. I come and go at Prescott below the TPA and, when I was training at Grand Canyon Airport to work for Papillon, I was constantly reminded by my instructor to stay below 7,000 feet MSL — below the traffic pattern altitude. (Of course, that put me right over the treetops, which wasn’t a comfortable place to be, at first.) As a result of all this work in Class D airspace, it’s become natural for me to cross airports below the traffic pattern altitude. I never expected to be told that there was a rule to the contrary.

I looked for, but did not find, any rule stating required — or even recommended — altitudes for any kind of aircraft operating in the vicinity of a Class G airport. So what the hell was this guy talking about?

I reported my findings to Mike as he worked on the golf cart. We went home, stopping at Safeway for some wine to take to Christmas dinner at a friend’s house the next day.

Belligerent. That word bothered me. I asked Mike if I’d been belligerent on the radio. He said I hadn’t but the guy who’d talked to me had definitely been belligerent. So I asked Mike to call the idiot at Eagle Roost and tell him I wasn’t belligerent.

Mistake. The guy talked poor Mike’s ear off. And, as usual, he didn’t believe anything Mike had to say. Talk about a trap door mind. One of his neighbors had sworn something to him, and the idiot, our former friend, was willing to believe him instead of us. Radio man said that a plane had been in the pattern and I had been belligerent. Period, end of story, trap door swings shut. Poor Mike listened to the idiot far longer than I would have. I felt bad for him when he finally hung up.

Like I said, no loss.

Tomorrow, I’ll give my FAA contact a call and ask him about this “rule.” He’s a helicopter guy, so he’ll know. And if there is no rule, I’ll just pretend the whole thing never happened.

PostScript

I called my POI at the Scottsdale FSDO and talked to him. Twice. He confirmed what I suspected: there is no rule in the FARs specifying an altitude for untowered airport overflights. That applies to both airplanes and helicopters. However, he added in his best FAA voice, a “prudent pilot” would overfly above the traffic pattern altitude. He went on to provide some examples of how overflight at a lower altitude could cause problems.

So I was right but I was wrong. And so was the guy on the ground.

In my opinion, if something happens while you’re flying in Class G airspace — like a midair collision or even a near miss or a forced go-around — then one of the pilots (at least) is not being prudent. It doesn’t matter what the situtation was: if a rule wasn’t broken but someone did something dumb that caused a problem, that someone wasn’t being prudent. But if nothing happens? Then is there a question of what’s prudent? I don’t know. But I do think that if the FAA felt strongly about altitudes at Class G airports, it should amend the regulations to specify an altitude. That would turn a gray area into black and white. What good are regulations if you can’t use them to guide you in your actions?

I also spoke to a fellow helicopter pilot who lives in the area. “Do you ever fly over Eagle Roost?” I asked.

“Once in a while,” he replied.

“What altitude?”

“Usually about 400 feet.”

So I wasn’t the only one. “Do you talk on the radio?” I asked.

“No.”

He didn’t add what we both knew: The regulations do not require communication in Class G airspace. But who’s being more safe? The pilot who attempts communication or the one who just buzzes through without a peep?

What is the lesson to be learned from this? It isn’t one the FAA would like.

The lesson is that when you overfly an airport without a published radio frequency, don’t talk on the radio. Eagle Roost’s frequency does not appear on any chart and the airport is not listed in the Airport/Facilities Directory, the only two documents a pilot is required to have onboard (and I’m not even sure the A/FD is required for all pilots, although it is required for Part 135 operations). If I hadn’t responsibly made my radio calls, the guy on the ground wouldn’t have even known I was flying over. He’d have nothing to get his blood pressure up. He wouldn’t have called the idiot to harass me. None of this would have happened. Heck, you wouldn’t even be reading a blog entry about it.

Fortunately, that’s not the lesson I learned. I learned that residents at private airparks are a bunch of whiners who like to boss around anyone within radio range. They like to make up stories about possible accidents and share them with anyone who will listen and take their words as gospel truth. And some of them even like to take it beyond the radio, with harassment by phone and in person.

As for me, I won’t overfly Eagle Roost again. It just isn’t worth the headaches that go with it.

Flight Planning

A quick review of my Part 135 Flight Planning Routine

My company, Flying M Air, is an FAA Part 135 operator. What that means is that I had to go through a lot of paperwork and testing with the FAA to be allowed to take paying passengers more than 25 miles from my starting point or to land with paying passengers on board.

As a Part 135 operator, I have the FAA looking over my shoulder to make sure I do everything “by the book.” The book, in this case, is my Statement of Compliance, a 50+ page document I wrote that explains how I’ll follow the Federal Aviation Regulations (FARs) that pertain to my Part 135 operations. The FAA reviewed this document in painstaking detail and it took about three months to fine-tune it to the FAA’s satisfaction. Of course, the FAA also conducts surprise and scheduled inspections of my aircraft and my base of operations (my hangar) to make sure everything is just right. And because I’m required to be on a drug testing program, I’ve been told that I can expect a visit from the FAA’s “drug-testing police” one day in the future.

For the record, I have no problem following FAA’s requirements for my operation. They’re not asking for anything unreasonable and everything they require is in the interest of safety for me, my passengers, and my aircraft.

Anyway, one of the requirements for Part 135 operations is flight planning. And, at this point, I have it down to a science.

I start by getting the names and approximate weights of the passengers I’ll be carrying, along with our destination, expected time on the ground, and any special route requests.

Today’s a good example. My two passengers want to fly from Wickenburg to Sedona and back. They want a scenic route both ways so they can see as much of the area as possible. At Sedona, they want to take a Jeep tour at least 2 hours long. I’ll have to line that up for them so the Jeep folks meet them at Sedona Airport when we arrive. With lunch and other activities on the ground, I expect to be there 4-5 hours. I expect to depart Wickenburg at 10 AM and depart Sedona by about 4 PM. My route will take them past some of the area’s mining areas, over Prescott, near Sycamore Canyon, and past Sedona’s red rocks before landing. On departure, we’ll swing past Jerome and follow the Bradshaws down to Lake Pleasant, where I can show them some Indian ruins and the house on Sheep Mountain. A final swing around Vulture Peak and over the ranch where they’re staying will get us back to Wickenburg. Total time enroute: about an hour each way.

With this information in mind, I fire up my Web browser and visit the Duats Web site. Duats is a free flight planning service for pilots. I log in and enter my flight plan for a weather briefing that includes current conditions at airports on or near my route (Prescott and Flagstaff) as well as NOTAMs. Today I learned that we’ll have typically clear Arizona weather with the possibility of some high cirrus clouds. It’s windy right now in Flagstaff, with gusts up to 34 knots, but the wind is expected to calm a little bit as the day wears on. Still, I can expect some very light turbulence as the winds pass over the mountains we have to cross or fly around: the Weavers, the Bradshaws, and Mingus Mountain.

Duats also has a flight planning feature and I use this next. It takes the information I’ve already entered to get the weather and uses it to calculate the route and enroute time for the flight. Since I can’t put as much detail into Duats as I need to, its flight plan is much simpler than my scenic route. It says it’ll take 45 minutes to get there and 40 minutes to return. I file both of those flight plans, each with their own times (10 am and 4 pm) with the FAA. They’ll sit in the FAA’s computers until I either activate them (one at a time, of course) or they expire.

Next, I whip out my Manifest form. This is an Excel spreadsheet I designed that automatically calculates weight and balance for my helicopter. I enter all the flight plan information, as well as my starting fuel load and the names and weights of my passengers in the seats I expect to put them. For weights, I add 20 lbs. I used to add 10 lbs, but the folks who book these flights don’t seem to have a clue about weights. It’s always better to overestimate than underestimate. And since it’s nearly impossible to load an R44 out of CG, it doesn’t matter if the two passengers sit somewhere other than the seats I expect to put them in. When my passengers are light — as these two are — I usually put them both on the same side of the helicopter so they have the same basic view. I then fly so that the most interesting views are on their side. But if they both want to sit in back, that’ll work, too. Or any combination they want.

The Manifest form is also designed to be used when I don’t have access to the Internet. It creates the same flight plan that I file with the FAA. So if I have to get the weather from a telephone briefer, I can file my flight plan over the phone at the same time rather than via the Internet.

If I have access to a printer, which I usually do during flight planning, I print out my manifest form for each leg of the trip, my flight plans for each leg of the trip, and my weight and balance for each leg of the trip. If I plan to start each leg of the trip with the same amount of fuel and take the same amount of time, I only print one weight and balance sheet. No sense wasting paper. But today I printed two sheets — I plan to fill up in Sedona since my passenger load is light and fuel is currently cheaper there than in Wickenburg.

I usually give a copy of my manifest — that’s the form with the passenger names and flight plan — to Mike. He’s my backup flight following. I call Mike when I depart and arrive each leg of the trip. If I don’t call in on time and he can’t get me on my cell phone, he takes the next steps with Flight Service.

Of course, I also open my filed flight plans with the local Flight Service Station (FSS). Although I prefer to do this on the ground before I start up, the FSS prefers that pilots do this on departure. My problem is that as a helicopter, I don’t always get enough altitude to access one of the radio frequencies the FSS uses. So I sometimes can’t activate a flight plan until I’m 10 minute into my flight. I close the flight plan by phone when I land, then call Mike to let him know I’ve arrived safely.

All the paperwork that’s generated for the flight is left on my desk in my hangar. After the flight is done, I file it. The FAA likes to look at these papers when they do their base inspection, even though I’m not required to save them.

And that’s about it. As you can see, the whole routine is designed to make sure I properly plan the flight and have at least one form of flight following to make sure a search is conducted promptly if I do not arrive at my destination. It sounds like a lot of work, but I can normally do it in less than 20 minutes with my computer and an Internet connection. To do it manually would take about twice the amount of time.

So I’m flying to Sedona today. I’d better bring a book; I have a feeling I’ll be spending a lot of time at the airport there.