The FAA started their Pilot Proficiency Award Program (commonly known as FAA WINGS) in 1996. It is run by the FAA Safety Team, or the FAASTeam. The intent of the program was, and is, to “improve the nation’s accident rate by conveying safety principles and practices through training, outreach, and education” (taken from faasafety.gov). The FAA WINGS program, free of charge, encourages pilots to pursue recurrent training to enhance their overall knowledge of all the aspects of aviation.
The FAA WINGS program has evolved over the years, but with the current structure, pilot’s accomplish tasks, both knowledge and flying, for credit that adds up to the equivalent of a flight review. Pilot’s must accrue three knowledge credits and three flight credits to complete a phase, and each phase acts as a flight review.
FAA WINGS has three levels, the basic, advanced, and master level. Under each level, you accomplish different phases. The basic level is “designed for pilot’s [desiring] a higher level of proficiency than … a normal flight review” (faasafety.gov). The flying tasks in the basic phase are based on the private or commercial pilot PTS, depending on the airman’s certificate level. The knowledge courses revolve around many different areas, all of which can be viewed on the FAASafety Team’s website. Most are free, but there are some courses that have a cost associated with them. In the advanced and master phases of the FAA WINGS program, the tasks have higher standards, challenging pilots to hold themselves to those higher standards.
One unique aspect of the FAA WINGS program is the opportunity to attend a safety seminar for credit. Throughout the year, there are many different safety seminars that take place in the different FSDO areas. The FAA WINGS seminars range from a study of accidents, to GPS usage and anything in between. You can even get FAA WINGS credit for attending the Bonanza BPPP or the Cirrus CPPP programs.
As an instructor, I highly recommend to all my customers to enroll in the FAA WINGS program and use it. This keeps pilot proficiency at a high level, which in turn keeps safety at a high level as well. Plus, you get to learn a lot too!
If you’d like to enroll in the FAA WINGS program, visit faasafety.gov to create an account. Then, find a good instructor and start working on those phases!
Texas Top Aviation has added a new member to our instructing team. Stephanie Mertz was hired in March 2019 and will be specializing in G1000 & Instrument instruction.
Stephanie graduated from LeTourneau University in Longview, Texas with a degree in Aeronautical Science, earning her commercial single and multi ratings while there. She began her aviation career in Ontario, California flying a Pilatus PC-12 for charter and medical trips. While operating the PC-12, she gained valuable experience flying all over the US and Mexico.
In 2013, Stephanie moved back to East Texas with her husband where she worked as a contract pilot flying a variety of Citations as well as a Falcon 10. A few years later, she became involved in her local Ninety-Nines chapter and joined their mentorship program.
After earning her CFI, CFII, and MEI, Stephanie returned to her alma mater to pass on her flying passions to college students through flight instructing. After a year of teaching at LeTourneau, she and her husband, with their first baby in tow, moved to the Austin area. Now she is instructing with Texas Top Aviation while acting as a mentor for other women working on achieving their flying dreams.
Some of a pilot’s favorite words are heard on the ATIS: “Winds, Calm.” These words set off all sorts of happy bells and hallelujah choruses. Most pilots spend their lives fighting the winds. On those rare days when the winds are calm, great happiness ensues.
But, are calm wind landings more complicated then everyone thinks? Well, they can be if the proper planning doesn’t go into them.
Let’s think about wind. We have surface wind and we have winds aloft. Sometimes the surface winds are calm. When this happens, certain airports have preferred calm wind runways which are supposed to be used in these conditions. Winds aloft are almost never calm. 95% of the time, there is some kind of wind even 100-200 feet above the surface.
Here is the question pilot’s face when coming into an airport with calm winds: which runway do I use? Do I use the calm wind runway? Do I use the runway that is easiest to enter the pattern for? Do I use the one with the shortest taxi?
A lot of technologically advanced aircraft have a wind indicator on the PFD. This tool is often forgotten in calm surface wind conditions. On the contrary, this is probably the most important tool a pilot can have when figuring out which runway to use when the winds are reported calm.
Here’s why. That wind indicator is showing the pilot what the winds aloft are. The winds aloft should determine what runway is going to be used. If the wind indicator is depicting a south wind, then a south runway should be used. Even if it is a 5 knot wind at pattern altitude, it’ll still be a headwind coming in on final approach. If the north facing runway is used, that same 5 knot headwind can blow an airplane halfway down the runway before the ground speed drops off enough for it to land.
So, the next time you are coming into an airport and the winds are reported calm, take a look at your wind indicator on your PFD when deciding which runway to use. It’ll probably save a few go arounds!
L-3 has jumped into the ADS-B transponder game with their Lynx line of products. Aircraft owners have a myriad of options with the Lynx line, from simply becoming ADS-B compliant with the NGT-1000 ($2,100, with ADS-B out that works with the GTX 327 and GTX 330), or going all in with the NGT-9000 touch screen transponder complete with ADS-B In, a traffic screen and NEXRAD ($6,800).
The NGT 1000/2000/2500 line works with the existing transponder in the airplane (as long as it’s a Garmin GTX 327 or 330). The 2000 gives ADS-B In capability, allowing the pilot to access NEXRAD and traffic, plus has a Wifi source to broadcast all the information to an iPad. The 2500 includes all of that, plus gives the pilot MFD capability as well. An optional control panel is available if the airplane is not equipped with one of the aforementioned Garmin transponders.
The L-3 Lynx NGT-9000 is an actual transponder replacement. It is a touch screen device that has a multitude of ADS-B features that, quite frankly, are really cool on a transponder. The ADS-B traffic is displayed on the unit itself and can also be sent, via the optional Wifi connection, to an iPad on the WingXPro or SkyRadar apps. The optional L-3 NextGen Active Traffic can also be installed to receive traffic callouts (this does not include resolution advisories). Already have SkyWatch? The L-3 Lynx can use the equipment.
The L-3 Lynx NGT-9000 is also capable of displaying NEXRAD as well as METARs, TAFs, NOTAMs, and TFRs and a myriad of other weather products, all on it’s moving map. It seems that L-3 has taken the transponder and turned it into something awesome.
To read more about the L-3 Lynx line of transponders, you can visit their website.
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
The gear door and strut after the accident.
If you think about the fact that I hit the deer with the wheel, but it didn’t hit the gear door, it becomes apparent just how close the airplane was to clearing the animal completely.
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.
There was a bill introduced in Congress recently to take control of Air Traffic Control away from the FAA and give it to a private, for profit, corporation. The initial reaction of pilots is “Ahhh! User fees!” which we are all adamantly opposed to. There are a myriad of reasons why this is a bad idea (the “Flying” article makes a comparison to giving NASA to Richard Branson and Jeff Bezos) and we as pilots should be against it.
The first task I give my new instrument students before we start training is to find a view limiting device that they like. There’s the hood that everyone hates (which has been used since the beginning of instrument training,though it isn’t that uncomfortable) or foggles, which usually end up becoming very uncomfortable very quickly. The headset ends up pressing the sides of the foggles into the side of your head, leaving lumps and scars that hurt for days.
Well, there is finally another solution that combines the hood and foggles. Meet the ViBAN.
ViBAN brags that it is the most comfortable IFR view limiting device out there. I have a customer who has one and he loves it. It’s easy to put reading glasses on underneath while still blocking the view of the exterior of the plane. It doesn’t leave bruises against the side of your head, either.
If you’re looking for something different for your IFR training, give ViBAN a try.
