MMOPA announced the location for the 2022 MMOPA Convention. The 2022 Convention will be in Tucson, Arizona and will take place September 29th-October 2nd, 2022. The JW Marriott Starr Pass will be the host resort.
Thursday, September 29th will kick off the convention with a safety event for pilots and companions, lunch with exhibitors, and the return of the charity golf tournament.
Friday, September 30th and Saturday, October 1st will be when all the classes and seminars that make the MMOPA convention great are held. The Friday dinner will be at an aviation themed spot in Tucson while the annual auction and black tie affair will be Saturday night.
Stay tuned to the event details page on the MMOPA website to see when registration is opened.
In my 3,000+ hours of flight training, I have developed some tips and tricks to help people fly better. With teaching landings, I have 3 specific tips that will make smoother landings every time, guaranteed.
A Good Pattern
A wise flight instructor whom I would love to give credit to (but don’t know who it is!) once said that a good landing starts off with a good traffic pattern. So true! A good landing all begins with the setup. This is true for a VFR rectangular traffic pattern or an IFR instrument approach. Flying the proper speeds and being at the proper AGL altitudes helps immensely in making a good landing. Being at 600 feet AGL on a 1/2 mile final (or the alternative of 60 feet off the ground on a mile final!) makes it hard to make a good landing.
Proper Use & Understanding of Pitch and Power
Once flaps are used in the pattern, the plane is now on the back side of the power curve (or in the region of reverse command). Power is now being used to control the plane’s rate of descent while pitch is being used to control airspeed. The key is, both pitch and power work together, so if the pilot changes the power, he’ll also need to change the pitch and vice versa.
The common mistake I see here is when the airplane gets low on final, the pilot tends to (quite naturally) pitch up. All this does is bleed off airspeed and cause the airplane to sink faster. The proper input would be to add power, then adjust the pitch for airspeed.
Look Down the Runway
Now that we have gotten to the point of the round-out and touchdown, it’s the most important part. The best thing the pilot can do to make the best landing possible, is to look at the trees at the end of the runway. When I worked with college students, I told them to find the owl in the trees at the end of the runway.
The tendency is to stare at the pavement (or concrete) the whole way down to the landing. When a pilot’s eyes are fixated on the ground, this destroys his depth perception and causes a level off too low to the runway, resulting in a 3 point landing and/or a bounce.
By looking at the trees at the end of the runway, this gives the pilot much better depth perception and allows him to properly judge where to level off the airplane.
The question now is when should the pilot start looking at the trees? My recommendation is crossing the threshold of the runway. For some, it works better to start looking at the trees when turning final. Others, right before the level off. Regardless, find that owl!
The Garmin G1000/Perspective combined with the Garmin GFC 700 Autopilot can be a great tool in descent planning. When you want to end up at pattern altitude a certain distance from the airport or you get a clearance to cross a fix at a certain altitude, Garmin VNV is a great tool. Here’s how to use it.
VFR Garmin VNV Use
Let’s say you want to end up at pattern altitude 3nm from your destination, but you don’t want to descend down into the bumps before you have to. Here’s how to set it up:
Go to the Flight Plan page on the MFD
Press the ATK OFST soft key on the bottom of the MFD. It stands for Along Track Offset, which, in laymen’s terms, means you are setting a point along your track a certain distance from your destination. In this case, it will be 3nm
Input the distance using either the keypad or the small FMS knob and press enter
Select the altitude you want to be at (in this case pattern altitude) and press enter
You will see a point 3nm before you destination appear on your magenta line and a Top Of Descent (TOD) appear where you need to start your descent
1 minute before the Top Of Descent, an indicator will appear next to your altimeter
To have the GFC 700 Autopilot fly the descent for you, you have to do two things
Set the Altitude bug for the desired altitude
Press VNV on the autopilot
All you have to do now is manage power
IFR Garmin VNV Use
Let’s say you are told to cross a fix at a specific altitude. Here’s how to use Garmin VNV to plan it out.
Go to the Flight Plan page on the MFD
Turn the cursor on and highlight the altitude blank next to the fix in the flight plan
Input the desired altitude
You will see a Top Of Descent (TOD) point appear along your course where you need to start your descent
1 minute before the Top Of Descent, an indicator will appear next to your altimeter
To have the GFC 700 Autopilot fly the descent for you, you have to do two things
Mooney announced last week the redesign of their current Ovation and Acclaim models. The biggest change that Mooney pilots will love is the addition of a pilot’s door, allowing the pilot to enter on the left side instead of having to crawl over the passenger seat.
Other upgrades include a keypad for easier data entry on the G1000 and an all in one, digital standby instrument that includes attitude, airspeed, and altitude.
This raises the question, will Piper and Beechcraft follow suit?
Density Altitude: Pressure Altitude corrected for non-standard temperature.
That’s the book definition of density altitude. The problem is, that definition leaves a lot of general aviation pilots scratching their heads. What really is density altitude?
All airplane engines rely on air and fuel mixing together, then that mixture is ignited to create combustion. Normally aspirated piston engine airplanes get their best performance at sea level, where the air is nice and thick, allowing plenty of air molecules to get sucked in the engine intake. As a normally-aspirated airplane climbs, the ambient air pressure drops with an increase in altitude (the air gets thinner, less dense), thereby reducing airplane takeoff, climb, and landing performance. There just isn’t as much air at higher altitudes, to put it simply.
Turbo charged piston engines assist with this air density problem. A turbo charger boosts the air coming into the engine and fools the engine into thinking it is at sea level pressure all the time. The higher the altitude, the faster the turbo charger spins, spinning the compressor faster, which compresses more air to continue to give the engine sea level pressure air. This gets faster cruise speeds the higher you go.
Both normally aspirated & turbo charged engines do experience longer takeoff rolls and reduced climb rates at higher airport elevations & higher altitudes.
How does this all relate to density altitude?
When the outside air temperature rises, the air becomes thinner, less dense. This means that when an airport elevation is 1,000 feet, but the density altitude is reported as 3,000 feet, the airplane engine thinks it is at 3,000 feet. It won’t accelerate as fast. The airplane’s climb rate will also be reduced. That means that the normal climb pitch attitude a pilot is used to seeing won’t be accurate at higher density altitudes. It will lead to slower indicated airspeeds, slow enough to potentially lead to a stall if a pilot isn’t paying attention.
Where does this get dangerous? High elevation airports. Whenever the OAT creeps above 85 or 90 at an airport that is higher elevation (I would classify higher elevation as 2,500 feet or higher), the corresponding density altitude sky rockets. If a pilot isn’t paying attention to airspeed or angle of attack (if the airplane is equipped with an AOA), a stall can come very quickly on climb out.
What to take home from this? Monitor your climb speed and angle of attack, especially right after takeoff, when you hear density altitude on the ATIS or AWOS.
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.
For the most part, flying through rain is a non-event. If the NexRad or Radar is showing light green or dark green, usually there aren’t that many bumps and your plane just gets a wash. Sometimes the visibility drops down a little bit making us IFR pilots have to transition to our instruments.
It get’s a little more exciting when the precipitation on your screen turns to yellow. This means there is a lot more precipitation echoes either in the clouds or coming out of the clouds, meaning harder rain. I usually tend to stay away from yellow unless it’s absolutely necessary to go through it.
I had a situation a few weeks ago where I deemed it necessary to fly through some yellow NexRad returns. I was flying a G1000 Columbia into Monroe, Louisiana, KMLU. The winds were mostly light, but slightly favoring runway 04, which was the runway in use. As I got closer, a decent size rain shower with mostly yellow returns was sitting over the final approach fix for runway 04 and slowly tracking to the northeast.
I didn’t particularly want to spend the entire approach getting beat on with rain, so I decided to fly the RNAV 14 approach at MLU and circle to land on runway 04. The rain hadn’t quite reached the airport yet, so I decided that circling to 04 should be no problem.
I started the RNAV 14 at the FLESH IAF. Since I was approaching from the west, I did not need to do the procedure turn, so I joined the Final Approach Course (FAC) after crossing FLESH.
In the meantime, that rain shower was inching closer to the FAC for the RNAV 14. I wasn’t concerned about my safety if I flew through some of it and I didn’t have passengers on board who would get nervous, so I elected to continue. I wasn’t seeing any lightning coming out of the clouds, so it appeared to only be moderate rain.
Just before I got to JIVEY, the FAF, I entered the clouds and the rain. About 20 seconds later, my altimeter and airspeed started bouncing around a lot. Now, based on all I’ve said so far, what would cause that, and what would you do?
(Jeopardy theme song playing while contestants ponder questions)
The answers? Due to the moderate precipitation, water had gotten into my static port and caused the unusual readings on my altimeter and airspeed indicators on the G1000.
I had experienced this before, so I knew what to do. I reached down and turned the static source from primary to alternate, which starts taking static pressure from inside the cabin in the Columbia. Instantly, everything went normal.
The other time I had experienced this was also in a Columbia, so I’m under the impression that the way the Columbia static ports are designed, they are a little bit more susceptible to water creeping into them than other airplanes.
Moral of the story? If your pitot/static instruments start jumping around, the first thing you do is turn your alternate static source on.
