The Do’s and Don’ts of Drones

This is the second part in a series on drones and Unmammed Aerial Systems (UAS). To read Part 1, Drones: A Brief History, please click here.

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.

Birds and Airplanes

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.

Similar Posts

  • 2022 Texas Top Aviation Fly In is in the Books!

    Thank you to everyone who made the 2022 Texas Top Aviation Fly In at the Hilton Santa Fe Buffalo Thunder Resort a success!

    We had 22 attendees and 12 airplanes make it out to beautiful Santa Fe, New Mexico for the week.

    After 2 days of very competitive golf, Chris Travland was our 2022 Texas Top Aviation Fly In Golf Tournament Champion.

    While you are out in Santa Fe on your next trip, go check out the Rancho de Chimaya restaurant. It was excellent and a true New Mexican experience.

    Mark your calendars for the 2023 Texas Top Aviation Dallas Fly In at the Westin Stonebriar Resort in Frisco, TX. McKinney National Airport (KTKI) will be our host airport. The event will be April 12th-April 14th, 2023. Hope to see you all there!

  • Hold Anywhere

    The latest Garmin software version on the Garmin G1000 and Cirrus Perspective by Garmin has a really neat feature.  It gives the pilot the ability to create a hold at any fix, VOR, NDB, or even airport.  If the point is in the GPS database, a hold can be created over it.

    How does it work?  Here are the steps.

    Let’s say ATC tells you to hold over an intersection on a Victor Airway that you are already on.  Since you are tracking the airway already, the airway should be in your flight plan complete with all the waypoints on it.

    Bring up your flight plan and highlight the waypoint to hold at.  Press the menu key.  Using the big knob, scroll down to highlight the hold at waypoint option at the bottom of the bottom of the menu.  Press enter.

    garmin-holding-pattern

    Now you can build the hold.  You select what the inbound or outbound course will be.  Select a timed hold or a distance hold.  Then select left or right hand turns.  You can even input your expect further clearance time.  Press enter and now you have a hold as a waypoint in your flight plan.  Assuming you have a WAAS unit, the autopilot will fly the hold for you.

    If you are ever told to “Hold Present Position,” Garmin has you covered.  Simply press menu on the flight plan page, scroll down to Hold Present Position, then follow the prompts on the screen to build a hold at your present position.

  • Oh, Deer (Part 1)

    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!

    This was found in the grass by the runway at Wings Field

    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.

  • Maintaining TKS Panels

    Columbia TKS Panels

    When cleaning airplanes, the majority of people don’t know how to properly maintain their TKS panels.  TKS panels provide wing leading edge, horizontal stabilizer leading edge, and, in the case of FIKI airplanes, vertical stabilizer leading edge de-icing protection.  For those not familiar with them, they are metal strips that have thousands of holes drilled into them where the TKS fluid seeps out. They have become quite prevalent on Cirrus aircraft, the Cessna TTx, and Mooney aircraft manufactured in the last decade or so.  The system is also known as a weeping wing system.

    Being on the leading edges, these panels pick up bugs very easily.  For the uninitiated, it would make sense to just use normal airplane cleaner to spray the panels and scrub the bugs.  Don’t!

    Using anything that contains Methyl Ethyl Ketone (MEK) as that can harm the TKS bladders behind the panels.  Any aircraft cleaner containing wax could cause the pores to clog, preventing the TKS fluid from properly seeping onto the wing.

    What’s the best thing to do?  Soap and water with a soft cloth is a good start (again, make sure it doesn’t have wax in it.  Dish soap would be suitable).  No hose available?  Just simply turn the TKS system on, let it run till you start to see fluid drip off the wings onto the ground, and use the fluid to clean the panels.

    A soft cloth would work fine, but, if the panels are really buggy, take a green scouring pad to do some scrubbing.  Just make sure the scrubbing motion is up and down with the grain, not side to side.  You can find the green scouring sponges on the dishwashing aisle in the grocery store.  Just leave one in the hangar for when you need it.

  • Flight Watch to be Discontinued

    The FAA has decided to discontinue the dedicated En Route Flight Advisory (EFAS or Flight Watch) frequency 122.0.  The effective date will be September 24th, but Flight Service will continue to monitor the frequency for an additional six months to direct pilots to Flight Service Station frequencies.

    EFAS services will still be provided by Flight Service, though, on the published Flight Service Station frequencies (and 122.2).

    To me, this makes some sense.  In the past, if I accidentally contacted Flight Service on one of their frequencies to issue a pilot report or get a weather update, they would send me over to Flight Watch on 122.0.  More than likely, the Flight Watch operator was sitting right next to the Flight Service operator, but I had to flip frequencies.  This will help alleviate some confusion for pilots.

    The deactivation of Flight Watch had been coming for years since the advent of Foreflight and other iPad and tablet apps giving pilots much easier access to weather, both in flight and on the ground.  With Nexrad and Stratus, there isn’t much need for Flight Watch anymore (though you still can’t file a PIREP over the XM Weather!).

    For more information, check out AOPA’s website.

  • AOPA Rusty Pilot Seminar in San Marcos

    “AOPA Rusty Pilot presented by AOPA Ambassador Pat Brown at Tempus Training Solutions”
    Topic: A Rusty Pilots Seminar
    On Saturday, July 16, 2016 at 09:00 Central Daylight Time
    Location:
    Tempus Training Solutions
    2080 Airport Dr.

    San Marcos, TX 78666

    Select Number:
    EA2769634

    Description:

    Life may have gotten in the way, but the dream of flight can be yours again. Returning to the skies is not as difficult as most rusty pilot think. We’re inviting you back in the cockpit and will help you get there. Come and participate in a FREE Rusty Pilot program with fellow lapsed pilots. We will help you understand what’s changed in aviation since you’ve last took the controls and brush up on your aviation knowledge. The Rusty Pilot program is developed by AOPA in partnership with local flight training providers in order to create the best environment for getting you back in the air and a part of the general aviation community.

    It is easier than most people think:

    • No FAA checkride or test
    • Medical may not be required

    As a Bonus, by attending, you get two to three hours of free ground instruction towards your flight review!

    Register Now!

    https://ww2.eventrebels.com/er/Registration/StepRegInfo.jsp?ActivityID=16910&StepNumber=1

    To view further details and registration information for this seminar, click here.

Leave a Reply

Your email address will not be published. Required fields are marked *