| |

Flying Through Rain

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.

Similar Posts

  • Dry Motoring a PT6

    When it comes to turboprop engines, a hot start is a really bad thing. For you piston drivers out there thinking, “What’s the big deal, you are just starting a hot engine,” then here’s a little education for you.

    In a PT6 turboprop engine, there is a very important temperature gauge that a pilot monitors very closely during each and every start. It is called the Inter-Turbine Temperature gauge, or ITT. This temperature is a measurement of the exhaust gases between the compressor turbine and the power turbine (s). In the picture below, the probe is located where the blue and red colors meet.

    In a turboprop engine, specifically the Pratt & Whitney PT-6 in all it’s different sizes and variations, there will always be a specific temperature that the pilot will want to keep the ITT below. This article will deal specifically with a Piper Meridian.

    A Piper Meridian starts hotter than almost any other PT6 engine because of the way it’s air intake is designed. Unlike other turboprops, the Meridian has a permanently open inertial separator. This means that not all the intake air makes it to the engine during start because some of it goes out the inertial separator opening. So, coming to a Meridian from operating other turboprop engines can lead to a little bit of a surprise on the ITT temperature being higher than what a pilot is used to when starting.

    As a rule of thumb, when starting a Meridian, never let a start continue when the ITT hits 875 degrees. Based on the chart below, you are still in the safe zone at 875 and have about a 50 degree buffer before you have to start getting worried.

    On cold starts with a good battery or a GPU, 875 is typically not an issue. Most starts when cold are going to be in the high 700s or low 800s. On a cold start, if you are seeing starts in the mid to upper 800s, try starting with a GPU and see if that lowers the start temperature. If it does, then that means your battery is weak and needs to be replaced. Another tell-tale sign of a weak batter is the Ng doesn’t spool up properly (meaning it settles around 12-13%) or takes a really long time to spool up. Also, never start on the battery with less than 24 volts.

    When there are multiple flights in one day, the pilot has to take into consideration the warm engine prior to starting. If the ITT, prior to the start sequence, is above 150 degrees, it is time to do some motoring of the engine.

    What is motoring? It is simply using the starter to turn the engine, which leads to air being sucked into the engine allowing the engine to cool off prior to start. The theory is, the cooler your engine prior to start, the cooler the ITT peaks at during start.

    Here’s the steps on how to dry motor a Piper Meridian:

    • Battery on
    • Strobes on
    • Fuel Pumps and Ignition off
    • Throttle idle
    • Condition Lever feather/cutoff
    • Push the start button
    • Monitor the ITT temperature
    • Reaching 150 degrees, if less than 30 seconds have elapsed:
      • Fuel Pumps on
      • Ignition On
      • Condition Lever run
    • Reaching 150 degrees, if 30 seconds have elapsed:
      • Push Manual/Stop button to stop the start
      • Let starter rest for 30 seconds

    The starter has a 30 second limit on the Meridian, followed by a 30 second rest period. You can do the sequence twice, then, after the 3rd start, there is a 30 minute rest period. Typically, if the ITT won’t cool down to 150 after the 3rd time, there is probably something wrong.

    The most important thing a pilot can remember is never, ever push the condition lever forward if the ITT is above 150 degrees. You’ll be well on your way to avoiding hot starts that way.

  • Free iPad Webinar

    Are you thinking of buying an iPad and going to a paperless cockpit?  Have you just recently purchased an iPad and are unsure of how to use Foreflight to it’s fullest extent?  Check out this free webinar on Monday, January 19th.  Gary Reeves, a Master CFI from California, will be hosting the 90 minute seminar, which begins at 1800 Z.  He will be able to point you in the right direction for what type of iPad to purchase, how to set up your Foreflight account, and the basics of using the App.

    You can finally get rid of those paper charts, saving clutter in the cockpit.  Just make sure you bring along a charger for those extended flight in case your battery dips low!

    To sign up for this webinar, click here.  There is no cost associated with the webinar.

  • Skyvector Has a New Look

    Skyvector has changed it’s look.  The aeronautical chart website is now offering flight plan filing capability. In order to gain the ability to file flight plans, the user has to form an account first.

    Personally, I really liked how Skyvector had a simple interface before they changed.  As an instructor, a lot of times, I go to multiple airports on one flight.  It was really nice to just plug in airport IDs to check distances and heading information on Skyvector.  The new format is a little clunky as the website has made it a little more difficult to do what it did best before.

    Did the aviation community need another venue to file flight plans?  Not with Foreflight, Garmin Pilot, and WingXPro leading the way in the app market.  Skyvector was smart in not trying to develop another app to compete with the big boys.

    Will the new Skyvector last?  We’ll see.  I’m hoping they’ll go back to the way they used to be, but we’ll see. I may use it enough to come around to liking it.

  • 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.

  • Redbird Skyport Bluebonnet Fly-In at KHYI

    Bluebonnet Fly In

    Come out to Redbird Skyport at the San Marcos Municipal Airport on Saturday, May 30th for the Bluebonnet Fly-In.  Hank Gibson from Texas Top Aviation will be giving a safety presentation at 2pm in the large conference room entitled “Is The Approach Activate?  Flying Garmin Approaches.”

    Join Texas Top Aviation and Redbird Skyport as we open the summer together at the Bluebonnet Fly-In.

    To Register for the Safety Seminar, please click here.

  • Cirrus CAPS Pull in Arkansas

    Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR.  From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure.  It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure.  At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.

    As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation.  I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands.  This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.

    After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport.  Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.

    To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital.  Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.

    The initial NTSB report as well as a link to the CBS story is below.

    http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

    NTSB Identification: CEN16LA026
    14 CFR Part 91: General Aviation
    Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
    Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
    Injuries: 3 Minor, 1 Uninjured.
    This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
    On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.

    According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.

    At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.

    An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.

    The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.

    The airplane has been retained for further examination.

Leave a Reply

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