New Houston Airspace Procedures

That Pesky Rudder

ByHank Gibson July 20, 2015July 27, 2015

Whenever I get in an airplane with a pilot for recurrent training, I can assure myself that I will mention rudder usage more than once during the flight.  If it is in a tailwheel (or if the pilot is doing tailwheel training), I’m going to mention the rudder a lot.  How do I know this?  Because basic rudder skills are actually one of the most difficult things to master in flying.

Let’s start simple.  What does the rudder do?  The dictionary definition is it controls the movement about the vertical axis of the airplane.  If you stick a pole down through the CG of the airplane and rotate the airplane around that pole, this is the vertical axis.  Looking at it another way, the rudder moves the airplane’s nose left and right.  Keep this in mind as we move on.

Every pilot thinks about the rudder during the takeoff roll.  Because of the torque effect, the pilot must add right rudder during the takeoff roll to stay on the runway centerline.  Depending on the airplane’s horsepower, more rudder pressure is needed in higher powered airplanes.  The problem usually shows up once the airplane gets in the air.

In the worst situation, after takeoff, the pilot will set both feet on the floor and completely disregard the rudder.  Torque effect and now P-factor are continuing to cause the airplane to yaw left, causing the need for right rudder.  With his feet on the floor, though, the pilot is allowing the airplane to yaw.  It’s not terribly noticeable for him in the front seat, but the back seat passengers (especially in a six seat or larger airplane) are certainly feeling it.

One particular problem spot on the climb is the climbing left turn.  In a climbing left turn, training says to add left rudder since it is a left turn (see below for the reasoning).  But, since the airplane is climbing and therefore experiencing left yawing tendencies due to the aforementioned effects, the pilot needs to continue pressing the right rudder, though the pressure won’t be as much as in a straight climb.  Watch the ball the next time you make a climbing left hand turn and it’ll make a believer out of you.

I find only a handful of pilots are this egregious.  Most pilots have rudder problems in turns and in turbulence.  We’ll tackle turns first.  As we all learned when we first started flying, due to adverse yaw, a pilot must add rudder in the turn’s direction.  Again, this isn’t usually where the problem shows up.  During the rollout is the problem area.

Let’s take a turn to the left.  The pilot rolls in, adding left rudder, arrives at his heading, then begins to roll out with the ailerons.  Left adverse yaw is now being experienced and right rudder is needed to smoothly transition back to level flight.  Need some visual assistance?  Watch the nose the next time you make a turn. If you are working the rudder properly, the nose will pivot on one point in the horizon.  If you aren’t using the rudder properly, the nose will draw a U shape on the horizon.  Try making some turns without rudder, see what it looks like, then use the rudder properly.  You’ll notice a big difference.

Finally, let’s talk turbulence.  As we all know, turbulence in the hot summer afternoon is quite pronounced. When the airplane experiences a bump, it usually doesn’t bounce straight up in the air.  There is usually some kind of rolling motion involved.  As the pilot corrects this rolling motion by moving the ailerons, adverse yaw is experienced (just like rolling into and out of a turn that we talked about above), so rudder is needed.  There isn’t a need to stomp on the rudder or you’ll cause the airplane to severely yaw in the other direction, but rudder pressure is needed.

Final approach is where this gets most pilots.  By controlling the nose and not allowing it to move around on final by using the rudder, this will make your approaches a little more stabilized leading to a more successful landing.

Feeling lost when it comes to the rudder?  Ask your instructor the next time you go fly to do some rudder exercises.  Most instructors don’t emphasize these basic stick and rudder skills which leaves pilots lacking as they move on in their aviation lives.  So make it a point to do some basic rudder work the next time you fly with your instructor.

PopSocket iPad Yoke Mount

ByHank Gibson October 24, 2017October 29, 2017

I was recently clued in to a really cool (and very cost efficient) iPad yoke mount.

It’s called a PopSocket and you won’t find it on any aviation website (I have to credit Joe Casey of Casey Aviation with this nifty find).

It’s very simple.  You take the mount (see right) and stick it to your yoke.  Then you pick one of a ton of designs from PopSocket and stick it to the back of your iPad (you can even create your own design!  B2 Bomber anyone?).

It’s low profile, doesn’t get in the way of anything, and is easily removable.  The PopSocket mounts are $10 apiece (depending on the size of your iPad, you may want to get 2).  The PopSocket is $10, so at the most, you’ll be in $40 plus tax and shipping.  Most mounts on Sporty’s are upwards of $50 and require a lot of installation, are big and bulky, and usually require lots of juggling to get the iPad in and out of the mount.

Give the PopSocket a try.

Spring Cirrus Austin, TX Get Together (CATGT)

ByHank Gibson April 5, 2017April 13, 2017

The South Central Cirrus Owner’s and Pilot’s Association (COPA) Region is hosting it’s second Fly In dinner at the Austin Executive Airport (KEDC) on Friday, October 8th, dubbed the Spring Cirrus Austin, TX Get Together.  The event is from 5:30-9pm.

Like the first CATGT in October, there will be dinner ($25 per person), drinks, and several presentations.  Jack Long and Josh Marvil will speak about their trip around the world in a PC-12.  Ed McCombs and Eric Opiela will give a safety presentation about automation and task saturation.

Plus, best of all, Cirrus is bringing a real live flying SF50 Vision Jet, plus a brand new SR22 G6 with the Garmin Perspective NXi panel.

Fly in or drive to EDC.  The dinner will be in the Henrickson Jet Center’s main hangar.  You will need to RSVP so event organizers can get a proper head count.  The link to RSVP is here.

Register for the CATGT before the slots are all filled up!

Oh, Deer (Part 1)

ByAndrew Robinson March 7, 2017April 5, 2017

As far as I knew when I woke up, October 26, 2016 would be an ordinary day for me. It was a Wednesday, and I was scheduled to fly our Company’s BE58 Baron on a charter from Wings Field (KLOM), a non-towered airport just north of Philadelphia, to Pittsburgh International Airport (KPIT) and spend the day there waiting for my 3 passengers to finish up their meetings. The plan was to fly them back to Wings that evening and then make the short hop back to home base at Lancaster, PA. (KLNS).

It was a flight that I had done countless times, and I was comfortable with the airports, the passengers, and the airplane. Everything went smoothly that morning and my short flight from Lancaster to Wings was uneventful. I even made it there in time to spill coffee all down the front of my pants before my passengers arrived. The weather was clear, calm and beautiful as we loaded into the Baron and the sun was just starting to come up as I taxied toward runway 24 for departure. I was departing VFR and had an IFR plan on file which I intended to pick up with Harrisburg Approach once we were airborne. According to my calculations, I was on schedule to be drinking my coffee at the Pittsburgh FBO right around 8:30.

At 7:05, I advanced the throttles for departure. A few moments later, I received a very unpleasant surprise. I was quickly approaching rotation speed when 2 deer ran onto the runway directly in front of the aircraft. It was still dark enough that I was relying on my landing/ taxi lights to illuminate the runway for take-off.  As a result, I was unable to see the animals before it was too late. I don’t remember making a conscious decision to pull back on the yoke, but it was that or plow directly into them at about 85 knots. I pulled up as quickly as I could and the airplane rotated immediately.  A fraction of a second later I heard and felt a sickening THUD.

There was no doubt that I had hit one of them, but, somewhat unbelievably, the airplane was climbing as though nothing had happened. I put the nose down to get the airspeed back up and began to try and piece together what damage the airplane had sustained. Based on the noise and the feeling of the impact, my suspicion was that I had hit the deer with the left main landing gear. A review of the instrumentation showed no abnormalities and the airplane was behaving normally, so I didn’t suspect any damage to the airframe/ flight controls. I couldn’t see anything out the windows that looked unusual, and somewhat unbelievably I still had 3 green lights.

After gaining a safe amount of speed and altitude, I turned around and told the passengers that we had hit a deer. It was obvious that we had hit something and I was sure that they wanted to know what was going on. Then, I checked all my indications again and satisfied with what I was seeing, tried to bring up the landing gear. No dice. When I pulled the gear lever to the up position, the master “GEAR UP” warning light came on and I got a horn. There was never any change in the 3-green indication and the gear motor never came to life at all.

At this point it was obvious that, minimally I was going to have to divert to Lancaster and have the maintenance guys look at the airplane to see if anything was broken. I figured that they would either give me the green light to continue or I would just jump into one of our PC12s and complete the trip while they worked on the Baron.

The landing gear’s refusal to come up was my first indication that there was substantial damage. I set course for Lancaster and called our Chief Pilot. After explaining the situation to him, we agreed that KLNS was the best option and that he would let the maintenance guys know that I was coming.

The logic was that proceeding to Lancaster would allow a visual check of the landing gear by maintenance people as well as the tower and result in the safest outcome if an emergency landing were required. Lancaster would likely have better services available in terms of emergency responders and, not to mention, I was fairly certain that there was a dead deer on the only runway at Wings that I didn’t feel like hitting for a second time. In addition, the relatively long runway at Lancaster combined with light traffic at that time of day made it the ideal option to divert to.

I again turned around to brief the passengers. I told them that we were going to have to make precautionary landing before continuing to our intended destination and that I would be performing a few low passes for the tower.

Due to the drag from the landing gear, the flight to Lancaster seemed to take forever. The long cruise home, however, gave me time to try and reach someone on the ground at Wings in hope of having the runway inspected and cleaned off before other traffic tried to use it. After several attempts to raise anyone on the Unicom/ CTAF frequency, I called Philadelphia Approach for help instead. Philly answered right away and I explained to them what had happened. I requested that they call over to Wings on the phone or send someone out to check the runway. They told me that they would get it done and asked if there was any other way that they could assist me. I told them I was headed to Lancaster and that I appreciated their offer, but didn’t require any further assistance. I then switched over to Lancaster Tower and let them know that I was about 15-20 minutes out, but I would need to perform a couple of passes to have them check my gear. The tower cleared me for a low approach over runway 26.

I arrived at LNS at about 7:30. I performed my first low pass by the tower, not really expecting anything to appear out of place. I figured I had bent something or damaged the squat switch, but not much more. I climbed to pattern altitude and awaited the good word. Shortly after the fly-by, Tower reported that the left main gear didn’t appear to be down and locked. They suggested that I make another pass. The airport maintenance personnel chimed in, reporting the same. We had just started discussing whether cranking the gear a little by hand might help when Philly approach called the Lancaster tower on the phone.

Philly informed Lancaster that someone had inspected the runway at Wings and found the left main strut and wheel in the grass. I quickly concluded that cranking the gear down probably wouldn’t help!

To Be Continued…

(Read Part 2 Here)

Andrew Robinson is an airline pilot for Piedmont Airlines.  He is a former 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania.  He instructs in Beechcraft Bonanzas.

Cirrus SR20 Partnership Forming at KHYI

ByHank Gibson May 24, 2015May 24, 2015

Ever wanted to be a Cirrus owner, but the economics of being a single owner just don’t make sense for you? If you’re in the San Marcos/New Braunfels/Austin area, you now have a chance to join a Cirrus SR20 partnership at the San Marcos Municipal airport, KHYI.

The Cirrus SR20 partnership group is looking for 2-4 more members to buy in to a 2006 or 2007 Cirrus SR20 GTS.  The plane will be kept at KHYI and the group already has a hangar for it.

For more information, please contact Texas Top Aviation at info@txtopaviation.com.

The Do’s and Don’ts of Drones

ByAndrew Robinson June 7, 2016June 14, 2016

I’m surprised how often I’ve been asked about drones by concerned passengers as they load up for a charter flight. Most commonly I’m asked how many drones I’ve seen while I’m flying, or how many drones I’ve hit/ almost hit. Sadly, the media has made this drone crisis into something that it isn’t. I’ve never seen a drone while I was operating a full scale aircraft, and I’ve certainly never been put into a situation where I felt that a drone was a threat to my safety or the safety of the flight. In fact, I only personally know one pilot who has reportedly seen one around an airport and that was an isolated incident (and a non-event).

The reality is that while Unmanned Aerial Vehicles can be a real danger to full scale aircraft, incidents aren’t actually all that common and detailed information is often lacking or missing altogether. It is likely that some of the reported drone incidents were actually a case of a pilot confusing a loose balloon or a bird for a drone. This, combined with the media’s sensationalizing of every “close” encounter nationwide has led the public to believe that the problem is much bigger than it actually is.

In actuality, when the AMA (Academy of Model Aeronautics, the USA’s governing body for model aircraft) analyzed the data from the FAA’s 764 recorded Drone sightings, only 27 of them (3.5%) were actually recorded as “near misses” or “near collisions.” Additionally, only 10 of the records (1.3%) indicate that pilot was required to take evasive action.

The records also include reports of drone sightings at altitudes which would be impossible for civilian models to attain (19,000-24,000′). Finally, some of the sightings took place in areas which are specifically set aside for model aircraft and drones to operate.   In those cases, the person flying the drone when it was reported was actually doing so in a safe and legal manner in an area designated for that specific purpose. If you’re interested, the whole article is available here and has a lot of great information.

As pilots, it is important that we do our part in helping reduce the risk of drone strikes. The biggest thing that we can do to help is to report any activity that we see so that it can be investigated and hopefully the drone operator can be found and dealt with. Try to get as much detail as possible about the incident, such as the size, color, location, direction and altitude of any sighted UAVs and report it to the closest tower or controlling agency.

Recently, the people in Washington have come up with a bunch of new rules to regulate the operation of model aircraft. As of this year, every unmanned aerial vehicle between 0.5 and 55 lbs must be registered with the FAA and have an FAA issued registration number located on the model itself. The logic here is that if someone crashes a drone where it shouldn’t have been operated, the officials will be able to identify the owner of the model and take action.

Model manufacturers and vendors have also agreed to start providing information about a program called “Know Before You Fly” (KBYF) in the packaging of the drones.  This program seeks to help educate new hobbyists to the rules and responsibilities associated with model aviation. For more information on KBYF, here is a link to their website.

In the end, the sad reality is that it’s a combination of many factors: new technology making models cheaper and easier to fly, GPS navigation and automation, the media blowing the incidents out of proportion, and inexperienced and foolish operators which have caused the growing concern and required the FAA’s action. I think that it is important to understand that thousands of people have been flying radio controlled models for many years responsibly and this has never been a problem. The AMA has rules (which are the same ones now adopted by the FAA) regarding flying location, altitudes, speeds, and more which have kept both the modelers on the ground and the pilots in the air safe until now. Its a classic case of a few foolish individuals who have caused all modelers to be cast in a bad light.

There is no reason to fly in fear, though. A pilot should always be watching for hazards as he or she is flying, regardless of the variety. In fact, according to the FAA’s website, there were 142,000 wild life STRIKES with civil aircraft in the USA between 1990 and 2013. That seems like a much bigger concern to me than the 764 reported drone SIGHTINGS. As with any new technology, drones are suffering from growing pains. As the rules fall into place and new operators become better experienced, hopefully we will hear about fewer incidents on the evening news. Anyway, I’ll stop “droning” on. Fly safe.

Andrew Robinson is a 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania.  He flies Pilatus PC-12s and instructs in Beechcraft Bonanzas.