|

Flying the Hudson River Corridor

Ever since I moved out to the Philadelphia area, the Hudson River corridor in New York City has become one my favorite places to fly. It’s hard to overstate the beauty of the city from low over the river. Every time I have a family member or friend come to visit, I try and take them over to see the city from the air.

Each time I fly up the river I can’t believe that we are actually allowed to do so, flying below the tops of the buildings and close enough that you feel that you could reach and out touch them. The draw back to the Hudson River Corridor is that it can be busy, intimidating, and confusing. However, with some reading and preparation, the Skyline flight is easy to do and extremely rewarding.

Having the right weather is an important first step. The second step is try to arrive during ideal lighting conditions. If possible, select a smooth, calm day to make it easier to maintain a track down the correct side of the river. I always try and target arrival at the city around sunset. The view is spectacular any time of day, but having the lights from the city while the sun is just setting gives the best viewing. I’ve also flown over and done the whole flight after dark, which is always spectacular.

View of the World Trade Center

The first method of flying the river is to utilize VFR flight following. If the controllers aren’t too busy, they will provide advisories to aircraft that request the Skyline. The nice thing about doing it this way is that the controller will clear you into the NY bravo airspace and keep you above the traffic flying the Skyline in the VFR corridor below. This is the method that I have always preferred as I enjoy the added benefit of the traffic advisories and it’s nice not to worry about position reporting on the radio.

If you want to get flight following, head toward the corridor and request the Skyline route with NY Approach. (Remember to stay clear of the Bravo until you’re cleared in!) Once you’re cleared into the Bravo and approaching the corridor, they will hand you off to Newark/ LaGuardia Tower for traffic advisories over the river. I like to approach from the south and ask for a 180 over the George Washington Bridge. This allows me to fly past the city a second time before exiting the corridor over the VZ (Verrazano Bridge) and heading back toward home.

In red is the path I typically fly. I descend to 1400’ and fly toward the APPLE intersection picking up the shoreline around Staten Island and hugging it until crossing the middle of the VZ. Newark normally clears me into the Bravo at 1400’ or 1500’ to fly up the corridor.

Pros:

  • Better traffic Awareness
  • No position reports

Cons:

  • Flying slightly higher reduces the view
  • If the controllers are busy, they may deny your request for advisories  
  • Can be intimidating to talk to NY Approach/ Newark/ LaGuardia 

The other option is to fly in the VFR corridor. If you want to do it via this method there are just a few things you need to make sure you’re familiar with before you go. When in the VFR corridor you’ll need to make required position reports on a CTAF frequency. Make sure that you have the proper charts and have studied pictures of the landmarks so that you know what you’re looking for. I tend to plan on this as a backup in the event that the controllers won’t give me advisories.

Pros:

  • Doesn’t require talking to controllers/ class B clearance
  • More freedom to select altitude and routing as desired

Cons: 

  • Less traffic awareness
  • Required position reporting

All the requirements and guidelines for flying the corridor can be found on the back of the NYC TAC chart. Any pilot flying the river is required to have one of these or a NYC helicopter route chart on board. If you’re using Foreflight, look in the Documents section under FAA Fly Charts and select the NYC TAC chart in order to read the back of page.

Below you’ll find examples of the diagrams/ instructions printed on the back of the NYC TAC charts.

You can see the traffic flow requires northbound airplanes to hug the east side of the river, while the southbound traffic stays on the west side. The VFR reporting positions (listed from North to South) are: Alpine Tower, George Washington Bridge, Intrepid aircraft carrier, Goldman Sachs (clock), Statue of Liberty, VZ (Verrazano Bridge). Each position report should include aircraft type, position, direction, and altitude.

Other things to be aware of:
NYC is always a hotspot for TFR’s. There are often TFR’s for baseball games or presidential movements so make sure to check before you head that way. Additionally, there is a speed restriction in place of 140 kts, though I’m not sure why anyone sightseeing would want to go that fast anyhow.

I realize that all of the procedures and restrictions can be overwhelming, but with the proper preparation, the Hudson Skyline is one of the most incredible places in the world to operate an airplane. There are a lot of things that are easy to get excited about that don’t live up to expectation, but this isn’t one of them. I’ve never taken anyone to the river that wasn’t impressed by what they saw and that’s why I plan to keep going back.

About to cross the VZ looking north toward the city

Similar Posts

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

    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…

  • PIREP: Austin Executive Opens a Control Tower

    Austin Executive Airport opened a control tower on Friday, February 23rd 2018.  The airport is now officially Class D airspace.  The charts and A/FD are not updated yet to reflect the tower, but there is a NOTAM with the tower and ground frequency information.  The tower hours are from 6am to 10pm.  The weather frequency remains the same.

    Make sure you check those NOTAMs if you are headed to KEDC anytime soon!

    KEDC Tower Frequency:  120.3

    KEDC Ground:  119.45

    Austin Executive Airport opened a control tower on Friday, February 23rd 2018.  The airport is now officially Class D airspace.  The charts and A/FD are not updated yet to reflect the tower, but there is a NOTAM with the tower and ground frequency information.  The tower hours are from 6am to 10pm.  The weather frequency remains…

  • IM SAFE: Are You Really?

    As pilots, we are all familiar with the IM SAFE acronym that the FAA puts out.  It comes up as part of the ground training over Human Factors during private pilot ground school.  We all memorize it, spit it out for our check rides, then most of us promptly forget about it.

    When I was training for my pilot’s licenses, I was at a Part 141 school that was very standardized (LeTourneau University, who has a fabulous aviation school).  Before each flight, we had to do a self evaluation based on the weather and the IM SAFE checklist.  Based on our answers, we would then determine if the conditions were conducive to flying as well as if I was physically okay to fly.

    This was a great tool because not only do pilots have to pre-flight the airplane, they also need to pre-flight themselves.  It’s very easy to fall into one of the “Hazardous Attitudes” if there is a pressing meeting or you haven’t flown in a while and it’s a beautiful day, but maybe you aren’t physically fit to control an airplane.

    Let’s break down the IM SAFE checklist to dig a little deeper into the physically fit side of flying.

    Illness

    This one is pretty easy.  Are you sick?  If so, how sick?  If you can’t hardly talk or your body feels like it was hit by a truck, then flying probably isn’t in your best interest.

    The tricky area can become if you are only a little sick.  Maybe you have a cough or a little cold or a headache is starting to form.  You probably could go fly, but is it really a good idea?  It could be something worse, or it may be nothing.  You have to know yourself and put limits on yourself before you wake up on the day of your big meeting two states over.  Set illness personal minimums and stick to them.

    Medication

    There are a slew of drugs, both prescription and over the counter, that pilots cannot take and fly.  AOPA has a hotline to call for pilots to find out if they can fly with the medication they are taking, or what meds they can take to give them relief and still operate an aircraft.

    Another great resource is your medical examiner.  Just give him/her a call and they will be more than happy to let you know what you can and can’t take.  They’ve been educated in the area of aviation so they are very knowledgeable.

    Stress

    StressometerThis is a huge one that pilots ignore a lot.  Maybe it was a stressful day at work, maybe you are running late to the airport, your meeting got moved up, whatever.  Stress can jump on you and mess up a pilot’s thinking very quickly.  If you have a lot of other things on your mind and you aren’t able to focus just on flying, it might be a good idea to stay on the ground.

     

    Alcohol

    Out of the whole IM SAFE list, the alcohol limitations are very clearly defined.  8 hours bottle to throttle, no more than 0.04% BAC, no operating an airplane while under the influence, and no carrying passengers who are visibly intoxicated.  For your personal minimums, it’s a good idea to increase that time to 12, 18 or even 24 hours bottle to throttle.

    Fatigue

    Learning to fly while a college student led to a fair share of canceled flights due to fatigue.  I operate best on 8 hours of sleep in the past 24 hours.  I can function on 6, but anything less than 6 hours, my performance drastically drops off, sometimes to a point where I wouldn’t be safe.  I discovered this while with my flight instructor attempting to do a holding pattern and completely botching it up.

    I observed this as a CFI quite often.  If I was doing ground with a student and they were struggling, my first question would be, how much sleep did you get last night?  More often than not, if I had to ask that question, I would get an average answer of 3 to 4 hours (I even had one guy show up for a flight block on 2 hours sleep.  I sent him back to the dorm).

    Fatigue is very easily overlooked because it’s not measurable.  Needing to get a flight lesson done or needing to get somewhere when you are obviously fatigued is not a good idea.  Make sure you get a good night’s sleep before a flight and don’t be afraid to cancel if you didn’t.  Set some sleep personal minimums and make them hard and fast.

    Eating

    Don’t skip meals and fly.  Performance greatly decreases when a pilot is hungry.  At the very least, stick a couple of food bars in your flight bag to give you some nourishment.

    Also, stay hydrated, especially in the summer time.  I carry a huge bottle of water with me on all my flights because I get headaches if I don’t drink enough.  Getting dehydrated on a long flight can lead to all sorts of performance problems (over hydration is also a problem in the air, but that’s what Gatorade bottles are for, right?).

    All this to say, have some personal minimums when it comes to you and your body.  Check the plane, check the weather and check yourself.  If anything falls in the “red” area in any one of those three categories, stay on the ground and don’t press your luck.

    As pilots, we are all familiar with the IM SAFE acronym that the FAA puts out.  It comes up as part of the ground training over Human Factors during private pilot ground school.  We all memorize it, spit it out for our check rides, then most of us promptly forget about it. When I was…

  • The Avidyne Equipped Cirrus Upgrade

    A History Lesson

    11 years ago, in April of 2009, the Avidyne Corporation unveiled the much bally-hooed Release 9, or R9 as it is commonly known, as a hardware replacement for the Avidyne EX5000 Entegra system in Cirrus Aircraft. The Entegra system was way outdated by that point. Even though Avidyne was the first company to put together a glass PFD in a single engine piston airplane, the company had quickly fallen behind Garmin in keeping up with the ever changing technology landscape.

    Rewind to 2008. Cirrus had been going strong with the Avidyne Entegra since the SR20 and SR22 went to full glass in 2003 (a PFD and an MFD; prior to that, Cirrus aircraft only had an MFD with steam gauges and a Sandel Electronic HSI). Cessna, on the other hand, vaulted past the Avidyne Entegra and went straight to the Garmin G1000 in it’s aircraft, starting in 2004 with the 182 G1000 and 2005 with the 172 G1000. Beechcraft and Columbia went to the G1000 (Columbia started with the Avidyne as well) in 2005.

    Garmin’s technology in 2007 was so much better than Avidyne’s technology that Cirrus decided to switch. I’m sure there were many promises made by Avidyne to Cirrus about what Avidyne was working on (the R9), but the G1000 was out there, available, and being used in a lot of different airplanes with very good results.

    So, in 2008, Cirrus made the switch from the Avidyne Entegra to the Garmin G1000, dubbing it the Cirrus Perspective by Garmin avionics package. Avidyne finally got the R9 to market in 2009, but by that time, Piper was the only airplane manufacturer left putting factory Avidyne panels in their airplanes, and they switched to G1000 later that year.

    The R9 is a fabulous product. It’s fully integrated, has great graphics, has fully redundant displays, a QWERTY keypad (which, by the way, Garmin didn’t do for another 8 years), and a lot of other neat features. There’s a bit of a learning curve, but it’s a really good product for what it is.

    Avidyne, though, was late to the game with their technology. By the time it debuted in 2009, all the GA aircraft manufacturers had long since switched to the Garmin G1000 and weren’t looking back. That left Avidyne with the retrofit market for the many different Avidyne Entegra Cirrus aircraft out there. The only problem was, the retrofit was $80,000 ($95,000 if you wanted to throw in the DFC 100 Autopilot, which is a must have) and not many owners were up for paying that much money, then or now.

    To sum up our brief history lesson, Avidyne knew the Entegra needed to go, but couldn’t get the R9 out quickly enough to convince anyone to stick with Avidyne products. The retrofit market didn’t amount to many sales, so Avidyne doesn’t even make the R9 anymore.

    As a side note, I really, really like the Avidyne R9 and am sad that it didn’t make it into more airplanes.

    So, when the Avidyne Entegra starts to have issues, what’s an owner to do? Keep reading!

    There is Hope

    There are thousands of Cirrus aircraft out there flying with the Avidyne Entegra instrumentation, which is basically 20 year old technology (I’ve had a computer engineer tell me the programming in an Entegra is Windows 98 tech). These things are going to start having problems at some point (many already have), but what solution do owners have that is cost effective and get’s them new technology?

    Remember that little company named Garmin? Well, they have come through again. Announced this summer, the Garmin G500 TXi is now certified as a replacement in the Cirrus Avidyne Entegra equipped aircraft. This means pulling out both the PFD and MFD and replacing them with the G500 TXi on both sides. Engine data is also displayed on the G500TXi MFD, including the percent power and TIT indications, if equipped.

    Cirrus SR22 Equipped with Dual G500 TXi Screens and Dual Garmin GTN 650Xi GPS Units

    The cost for the panel? Two 10.6″ G500 TXi’s run about $16,000 apiece for the units, not including labor. $32,000 for a brand new panel isn’t terrible. Plus, the G500 TXi’s work with the DFC90 autopilot if the Cirrus is already equipped with it. If not, the Garmin GFC 500 autopilot is now approved for the Cirrus at a relatively low price of $7,000, including the servos.

    Still have the original Garmin 430s in your Cirrus? Upgraded to the Avidyne IFD 540/440 stack? Put in dual GTN 650Xi’s? Put in a GTN 750Xi? All are compatible with the G500 TXi panel.

    Want to upgrade everything? It does get kind of pricey at that point, but for just equipment, the cost for a complete panel conversion is somewhere in the area of $65,000 plus labor, still below what the R9 cost, but not cheap either. That would include 2 G500 TXi’s, 2 GTN 650Xi’s, a GFC 500 Autopilot, and all the engine monitoring equipment that the G500 TXi would need.

    Cirrus SR22 Equipped with Dual G500 TXi Screens, a GTN 750Xi, and a GTN 650Xi

    Thankfully, some new technology has finally come to the Generation 1-3 Cirrus. Oh, and by the way, your steam gauge Cirrus is fully upgradable as well.

    Want to read more? Check out Garmin’s website.

    A History Lesson 11 years ago, in April of 2009, the Avidyne Corporation unveiled the much bally-hooed Release 9, or R9 as it is commonly known, as a hardware replacement for the Avidyne EX5000 Entegra system in Cirrus Aircraft. The Entegra system was way outdated by that point. Even though Avidyne was the first company…

  • An Educational Runup

    When a pilot thinks of an engine runup in a single engine piston airplane, typically it is let’s find out if the engine is running rough or not, meaning a spark plug is fouled.  Believe it or not, there is a little more to learn from a runup than just checking the spark plugs.

    A distinct advantage to having an engine monitor that monitors all EGTs and CHTs is you get a better idea of engine health.  When switching to one magneto or the other during the runup, all the EGTs should rise, showing that the temperature of the exhaust gas is going up from each cylinder.  This occurs because when running on only one magneto and one set of spark plugs in each cylinder, the mixture takes longer to burn, so, when the exhaust valve in the cylinder opens, the burn is still on going and this hits the EGT probe, causing a temperature rise.  An indication of a magneto failure in flight would be a rise in all the cylinders EGT without a change in mixture setting.

    Now that we know what to look for when checking each magneto, what would one look for to show that there is a problem?  The basic that each student pilot is taught still applies.  The engine manufacturer puts a limit on RPM drop during the runup.  When checking one magneto or the other, watch for an excessive RPM drop.  If the RPM drops past the limit, this usually will be accompanied by engine roughness.

    Why is that?  Let’s look at the cause for the excessive RPM drop.  For this, we need to go back to our EGT indicators.  Let’s say we have a 6 cylinder engine.  When the key is turned to the right magneto, the RPM drops 250 RPM and the engine gets very rough.  Look at the EGT gauge.  The cylinders where the spark plugs are firing normally will all show a temperature.  The cylinder (or cylinders) where there is no combustion, meaning a bad plug, will show no temperature.  This is because the mixture is just sitting in the cylinder and not igniting, therefore, no exhaust gases will be pushed out so there will be no EGT indication for that cylinder.  This is also how you tell a mechanic which cylinder to check for the bad plug.

    It could also be a bad magneto.  If multiple cylinders EGT all drop, or the engine wants to quit entirely, you have a bad magneto or bad ignition harness.

    What else can you learn during the runup?  Electrical system health is key, especially in all electric airplanes (meaning no vacuum system).  It’s a very good idea to turn on all the lights and pitot heat to ensure that a rise is indicated on the ammeter.  This means the alternator is carrying the load and working properly.

    The next time you do your runup, keep an eye on your EGT to see the rise during a magneto check.

    When a pilot thinks of an engine runup in a single engine piston airplane, typically it is let’s find out if the engine is running rough or not, meaning a spark plug is fouled.  Believe it or not, there is a little more to learn from a runup than just checking the spark plugs. A…

  • Oh, Deer (Part 3)

    Read Part 1 & Part 2

    Throughout the whole event, I learned quite a few things both about flying and about myself. Here are some of the lessons which I have taken away from the accident:

    1. No flight is routine: When I took off that morning I was about as relaxed as I could have been while going to fly. I was flying an airplane that I knew well, in beautiful weather, to familiar airports and even carrying passengers which I had taken on this exact trip more than a dozen times. The accident brought into startling clarity that anything can happen at any time. I had done everything right that morning (preflight, weather briefing, planning, etc) , and none of that did anything to stop the deer from jumping out onto the runway. All we can do is ensure the items we do have control over are covered and try to be prepared to deal with anything else that arises. This ties directly into my next point:
    2. Making sure everything is correct: When you do go fly, make sure that you have all your paperwork and personal details taken care of. I can think of a few times over the course of my flying career where something wasn’t quite right with the paperwork, or perhaps I had forgotten my wallet and I was tempted to go fly anyway. “It’s 8pm on Sunday, I’m not going to get ramp checked.” Well, I can assure you that the paperwork and questionnaires which were required to be submitted to the FAA, NTSB, and Insurance companies would have uncovered any discrepancies in my logbooks, currency, or legality. It isn’t worth the risk of flying without having everything in place just in case something happens. It isn’t just a random ramp check which can get a pilot into trouble.
    3. Ask for help: The story of my collision with a deer would have had a very different outcome if it weren’t for the help that I received from countless the people on the ground. If you’re ever in a situation where you could use a hand, don’t be afraid to ask for help. If I had simply turned around and landed back at Wings, I wouldn’t even have had any idea that my landing gear was missing! The people in the control tower, the maintenance guys, the approach controllers in Philly, the emergency responders, and many more people all played their part in orchestrating a successful outcome.

      Airplane sitting on the runway after the firefighters had checked it out
      Photo credit: www.lancasteronline.com
    4. Dealing with the Paperwork: I have had dealings with the FAA before, but never for an accident. I was afraid that the investigation would be a witch hunt and I would have to defend myself while someone poured over all my planning and paperwork looking for potential errors. But, my fears were totally unfounded. Although I did have to answer many phone calls, write many reports, and fill out much paperwork, the FAA, NTSB, and Insurance companies were very patient in waiting for my responses and even complimentary in how the situation played out. I really enjoyed working with all of them and appreciated their encouragement and help.
    5. Emotional Response: After the dust had settled and the smoke had cleared, I was left standing on the side of the runway with the passengers and my boss. I offered to fly them back to Philadelphia or continue to Pittsburgh and assured our Chief Pilot that I was feeling fine and ready to fly again. Fortunately, there wasn’t a need. Over the next week or two, I noticed a change in myself. I wasn’t fine. I have never had headaches, but shortly after I landed I developed a headache that didn’t go away for days. I had trouble focusing on anything and I had trouble finding motivation to do much but sit and stare at a wall. I wasn’t sharp and I caught myself making silly mistakes in my normally routine activities. I wasn’t depressed, or sad, it was just an unwanted mental and physiological response to the stress and shock of what happened that morning in the Baron. I didn’t feel like myself for quite some time and I even found myself a little on edge whenever I lined up for takeoff on subsequent charters for while afterward. Eventually I started to feel normal again, but it was a slow process.
    6. Feather the Props: I can’t tell you what a difference it makes when those props go from wind milling to feathered. It became clear to me that feathering a prop could make a huge difference in deciding the outcome of an emergency situation.
    7. Good training and checklists usage: This one is pretty straight forward, but it’s worth mentioning. Good training and proficiency make all the difference when the odds are against you. Make sure that you use all your resources when your back is against the wall, and that includes the checklists. Under the stress of the flight I had forgotten to close the cowl flaps and would likely have landed with them open without the aid of the Emergency Procedures Checklist. This would have resulted in unnecessary damage to the airframe.
    8. No need to rush: There is no denying that I had things stacked in my favor that day. I had nice weather, extra gas, daylight hours, and even the luxury of landing at my home airport. But, regardless of all those variables, there is no need to rush into anything. Ask questions, find answers and come up with a plan. Obviously not all emergencies present the pilot with the luxury of time, but use all time and resources you have to your advantage.
    9. Polish up those procedures: The deer accident really made me want to go out and brush up on all the emergency procedures which I hadn’t performed since my last checkride. The realization that I could need any of them at any time was really hit home after I hit that deer. Additionally, make sure you know who to call if something ever does happen.
    10. Know the systems: Familiarity with the systems on the airplane makes it easier to troubleshoot and solve issues on the fly and makes it easier to spot a problem in the first place. Knowing how systems work and what their normal indications should be helps make decisions regarding when to divert and where to land easier.

    The irony isn’t lost on me that the last article that I wrote for this newsletter dealt with how to avoid making gear up landings and the high cost required to repair one. I never would have imagined when I wrote that article last fall that I would be writing one only a few months later detailing my own gear up landing.

    The bottom line is that there is nothing a person can do to prepare for every situation which might arise throughout the course of a flight, and it’s also impossible to know which emergency you may have to deal with if a situation arises. All we can do is stack odds in our favor by making sure that we address the things within our control such as aircraft maintenance, careful flight planning, checking weather, and having personal minimums set in place to keep us from flying outside of our skill sets and comfort zones.

    Additionally, ensuring that you are knowledgeable and proficient in your aircraft’s procedures will give you the best chance for success. When things start going wrong, keep calm, and ask for help. Work the problem instead of guessing or rushing into a less than desirable solution. No one wants to be caught in an emergency like a deer in a landing light!

    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.

    Read Part 1 & Part 2 Throughout the whole event, I learned quite a few things both about flying and about myself. Here are some of the lessons which I have taken away from the accident: No flight is routine: When I took off that morning I was about as relaxed as I could have…

Leave a Reply

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