He’s very sneaky, creeping unexpectedly and attacking after the propeller begins to turn.
He’s very cunning, veiling his intentions until, BOOM, he attacks.
Beware of the Lunch Monster!
Whenever I am doing a full day of training (which is usually how transition training courses are planned out, in full day sessions), I always plan a lunch stop. My metabolism has the speed of a rocket ship, so I get hungry and need some sustenance in the middle of the day. I have a running list of airports to stop at that have good lunch spots at them or nearby, so my customers and I usually end up at one of those airports.
Almost without fail, if a customer is having an excellent flying morning, nailing all the procedures, picking up all the techniques, and overall, flying pretty well, then eats lunch, the afternoon doesn’t go quite as well. Doing some of the same things we did that morning, but the customer’s performance isn’t quite as good. Most of the time, it’s just a brain lockup or landings aren’t quite as squeaky as they were in the morning.
Part of it is fatigue after flying for 2-3 hours in the morning. The other part is what I call the Lunch Monster. Eating a big lunch can sap away brain power and cause a person to lose energy around 2-3pm, leading to an afternoon lull (or the Lunch Monster attacking!).
Diet contributes to energy levels too. “Eating a lunch that is too big is the most common reason for feeling sleepy in the afternoon,” says Rebecca Solomon a nutritionist at Mount Sinai Hospital in Manhattan. “All your energy goes into digesting the enormous meal.”
The goal is to keep the body’s Cortical and Cortisone levels even since they’re the hormones released by the body in reaction to stress–they produce the fight or flight response. Their levels are elevated when you have sugar, caffeine and processed food, so you feel awake and energetic. But a few hours later, when those levels drop, you’re sluggish.
Solomon recommends eating a meal that’s balanced with healthy fats (from olive oil or avocados, for instance) with protein and healthy carbohydrates (whole wheat bread or pasta). The portion will vary for people of different sizes, but a general rule is you should be hungry about four hours after the meal.
Another healthy eating habit: Consume small portions of foods throughout the day, including almonds, carrots and hummus and fruit. Enjoy lunch around 1:30 or 2 p.m., just before the time you normally feel fatigued.
Now, most of the stops on my list of restaurants don’t fit the bill of healthy fats and healthy carbohydrates (plenty of protein, though, especially the BBQ joints). For those days, bringing along a snack like almonds or dried fruit is a great idea to munch on mid-afternoon. Trimming down the amount eaten at lunch helps a lot too.
So, the next time you have a long day of flying or training, beware the lunch monster and prep some good snacks when your flight instructor says you’re stopping for BBQ!
Let’s say you’re flying in the mountains of Colorado on a cloudy day. There’s a solid layer from the surface all the way up to 14,000 feet. You’re inbound to Eagle (KEGE) on the RNAV (GPS) D approach. There are mountains next to you and below you, but you aren’t concerned since you can see them all. The base of the last reported overcast layer was 3,000 feet, so you know you’ll break out before the MDA and land no problem.
At 11,100 over AWACC, you clearly see the top of the mountain below you. You are comfortably above it. You already have the runway in sight as well. You pop out of the clouds on the approach at 9,700 feet, spot the airport and follow the tower’s instructions to circle north of the runway for a left base for runway 7.
How could you see the mountains inside the clouds? You have Synthetic Vision installed on your glass panel, that’s how.
Aspen Synthetic Vision
Synthetic Vision, which has actually been around since the ’70s when NASA and the US Military first developed it, was first FAA certified for the Gulfstream PlaneView flight deck in 2009. Garmin, Avidyne, and Aspen are the main general aviation manufacturers of synthetic vision these days. All Garmin PFDs are now equipped with Synthetic Vision while Aspen gives you the option to upgrade to Synthetic Vision when you get one of their PFDs installed. Avidyne gives you Synthetic Vision in their R9 upgrade for the Cirrus.
What is Synthetic Vision? Basically, it’s a 3-D picture on the primary flight display showing terrain, obstacles, traffic, and runways. It greatly enhances situation awareness in areas of terrain or high obstacles during IFR conditions or at night.
The goal behind the development of Synthetic Vision was to decrease the amount of controlled flight into terrain (CFIT) accidents. A CFIT accident consists of a perfectly airworthy airplane flown by a pilot (or autopilot) unintentionally into terrain. These accidents can happen in low visibility conditions or at night, but the reason is mainly due to the pilot losing track of his position in relation to obstacles or terrain (or water as was the case with JFK Jr.).
With Synthetic Vision, the goal is to enhance pilot knowledge of what is around the airplane at all times. When you’re at altitude, the terrain below you looks flat. When you start descending down amongst the rocks, the hills or mountains start to rise up on your screen. For those used to the coloration with the 2-D terrain feature on a GPS unit, it translates very easily to the terrain coloration on a Synthetic Vision equipped PFD. Terrain that is between 100 and 500 feet below the aircraft is shown as yellow, while terrain closer than 100 feet is depicted as red.
Garmin Synthetic Vision
One neat feature on Garmin units is the Highway in the Sky. When a pilot puts a course or a flight plan in the GPS, the PFD displays magenta boxes at the altitude selected displaying the route. It’s handy when hand flying to just “fly through the boxes.” They also display descent angles on approaches.
Synthetic Vision is still optional on Garmin and Aspen units, but I highly recommend springing for it. It will give you a higher level of safety and keep you out of the rocks.
Let’s say you’re flying in the mountains of Colorado on a cloudy day. There’s a solid layer from the surface all the way up to 14,000 feet. You’re inbound to Eagle (KEGE) on the RNAV (GPS) D approach. There are mountains next to you and below you, but you aren’t concerned since you can see…
Type Clubs Lead By Example with Standard Operating Practices
This article appeared in the May 2019 edition of EAA’s Sport Aviation Magazine. It is used with permission. For other articles by Charlie Precourt, please visit EAA.org and join for a full subscription.
Imagine a year when there are no fatal accidents in general aviation. Does that seem impossible? The airlines achieved that many years ago, and so can we if we focus on the right things in our safety pro- grams. In fact, the overall trend in GA accident rates over the last few years is very encouraging. AOPA’s Air Safety Institute published its annual GA Accident Scorecard recently (see www.EAA.org/ extras), revealing fatal accidents from 2008 to 2017 are down more than 30 percent. Nevertheless, there were 185 fatal accidents in 2017, so we still have a long way to go. But, there are many developments in safety programs across GA that can keep the trend going.
One such development that I’ve advocated through a couple of type clubs is establishing standard operating practices (SOP). When I flew for both the U.S. Air Force and NASA, we had what we called standard operating procedures. They were the law for our flying. That is, we had to follow them procedurally because the folks that paid our salaries said so. The objective was to ensure we all used the same playbook, minimizing the risk that one of us might develop a bad in-flight habit that increased risk to the organization.
One way to think about SOPs is to recognize the difference between procedure and technique. For example, you have to follow the manufacturer’s pilot’s operating handbook (procedure)where it says to lower the landing gear before landing. If you don’t, you are in for a bad day. However, it does not tell you exactly when to lower the gear; that’s left to technique.
In the middle, between procedure and technique, is a best practice. In this example, lowering the gear just before the final approach fix is a “standard practice.” It is the generally accepted “best” place to lower the gear. In GA, however, aircraft owners don’t generally answer to a boss, so I prefer the term practices instead of procedures.
However, whether or not someone is paying us to fly, following best practices just makes sense. If you have a good set of practices, they enable you to do things the same way every time, leaving lots of brain cells to manage the unusual, the things that might go wrong. The safest approach to accomplishing a flight task is one that leverages consistency. On the other hand, if you are inconsistent, doing flight tasks differently each time, you’ll always be struggling to keep up. So, in my involvement with the safety committees for both the Malibu Mirage Owners and Pilots Association and the Citation Jet Pilots Association, there has been broad acceptance of recently developed standard operating practices.
The good news in this development is that a culture of safety is growing broadly across most sectors of GA through these type club initiatives. Perhaps more importantly, there is much to learn from each other about the effectiveness of these various initiatives. EAA has seen a four-year drop of 47 percent in fatal accidents among homebuilts! So, there must be something right going on there — a major focus on appropriate transition training before flying a new homebuilt (as a standard operating practice) is paying off.
So, what is covered in the SOPs these type clubs have developed? The following outlines the kinds of standard practices other type clubs have set up and represent SOPs you could establish for yourself regardless of the type of aircraft you fly. You just have to fill in the blanks for your particular type and commit to sticking to them in your flying. These are notional and are practices (not mandatory procedures). They don’t tell you how to fly your aircraft; they give you things to think about when you do. If you take a bit of time to set your own SOPs and then stick with them, you’ll be a far safer pilot. Here are some ideas:
Duty Day
Set the maximum number of hours of flight time during a calendar day and rest hours off between flying days. One example is a maximum of eight hours in the air and a minimum of 10 hours off until flying again.
Cargo
Establish best practices for what you will carry as cargo. One example is no lithium batteries in the baggage compartment.
Flight Planning and Preparation
What are your limitations for the types of flight you’ll take on? Consider SOPs such as designating a suitable alternate airport for all flights. Another might be for first flights after significant maintenance, such as no flight at night or in IMC until a day-VMC functional check flight has been done.
Runway Field Length Guidelines
Establish an appropriate minimum field length for your aircraft and commit to not going into shorter fields. Consider sea level operations and high-altitude airports as well.
Surface Operations
What should be your maximum wind conditions for taxi, takeoff, or landing? Maximum acceptable crosswinds on landing? Set them in your SOP and stick to them.
En Route
Consider establishing practices like no non-operationally necessary conversation below 10,000 feet MSL, during any segment of an approach procedure, or during the last 1,000 feet before leveloff during climb or descent. Also consider declaring “minimum fuel” when the fuel state becomes less than fuel to destination plus 45 minutes at current burn, even if flying day VFR.
Approach and Landing
Consider establishing personal minimums in your SOPs for things like visual approaches. Perhaps use a 1,500-foot ceiling and 3 miles’ visibility for day and 5 miles for night, even though these exceed the FAA’s requirements.
Pilot Limitations, Training, & Currency
FAR Part 91 rules allow us to fly with pretty marginal levels of currency. Consider setting your own SOP to something more appropriate for the kind of aircraft you fly and the kind of flying you do in it. For example, consider these ideas as SOPs:
If you have less than 100 hours of time-in-type or have not flown at least 15 hours as pilot in command in the last 90 days, use a minimum planned fuel reserve of one hour.
Also, if flying IFR in this situation, use a minimum visibility for takeoff of 1 mile.
On instrument approaches, increase the published minimums by one- half mile visibility and add 200 feet to the decision altitude or minimum descent altitude.
Perform landings at a weight that allows a full stop in 60 percent of available runway length.
Consider an SOP that establishes you will fly with a CFI on a refresher flight before flying as pilot in command if you have not logged at least an hour of flight time and one takeoff and landing in an aircraft of the same type within the preceding 45 days.
Maneuver Standards
Wherever there are “techniques” associated with things like takeoffs and climbs, cruise, use of autopilot, power settings, and approaches and landings, you can write down your preferred technique as your own SOP. Describe each maneuver in enough detail (speeds, altitudes, power settings, configurations, etc.) to define a routine you will use each time. This ensures you fly consistently each flight and leverage the power of the standard operating practice, that is, to give you the bandwidth you need should you encounter an unexpected event or an emergency.
SOPs are among the exciting concepts underway to make safety programs work for us. Hats off to type clubs like MMOPA and CJP and many others that are taking the initiative. But even if you’re not in this kind of group, you can still set up your own SOPs. Let’s all look forward to our first year in GA without a fatal accident — and let’s make it soon! Fly safe!
Charlie Precourt is a former NASA chief astronaut, space shuttle commander, and Air Force test pilot. He built a VariEze, owns a Piper JetPROP, and is a member of the EAA board of directors.
Type Clubs Lead By Example with Standard Operating Practices This article appeared in the May 2019 edition of EAA’s Sport Aviation Magazine. It is used with permission. For other articles by Charlie Precourt, please visit EAA.org and join for a full subscription. Imagine a year when there are no fatal accidents in general aviation. Does…
Texas Top Aviation is proud to announce that Hank Gibson has completed the training to become an American Bonanza Society Instructor, or ABS Instructor. He is now qualified to give instruction in Beech Aircraft.
As an ABS Instructor, Hank brings over 2800 hours of flying experience in a variety of aircraft to the cockpit of Beechcraft. Along with his ABS Instructor Designation, Hank is also a Cirrus Standardized Instructor Pilot (CSIP) and a Cessna FITS Accepted Instructor in both Cessna high and low wing piston aircraft (CFAI+). Hank is proud to add the ABS Instructor designation to his list of qualifications.
The process of becoming an ABS Instructor is quite comprehensive. The coursework consists of 20 powerpoint lessons covering anything and everything related to flying Debonairs, Bonanzas, Travel Airs, and Barons. The ABS Instructor course is quite in depth and detailed, giving the graduate a full understanding of the Beechcraft piston line of aircraft. To find out more about ABS Instructors, see the ABS website.
Hank is now giving initial and recurrent training in Beech Debonairs and Bonanzas. Please visit the Texas Top Aviation Bonanza Training page for more information on Bonanza and Debonair initial and recurrent training. Interested in Bonanza or Debonair training with a qualified ABS Instructor? Contact Texas Top Aviation today!
Texas Top Aviation is proud to announce that Hank Gibson has completed the training to become an American Bonanza Society Instructor, or ABS Instructor. He is now qualified to give instruction in Beech Aircraft. As an ABS Instructor, Hank brings over 2800 hours of flying experience in a variety of aircraft to the cockpit of…
Earlier this month, Cirrus announced the new Cirrus G6 SR20 and SR22. To the naked eye, they look like incredible airplanes. There is new lighting and the updated Cirrus Perspective+ avionics in both models, plus the SR20 is now a Lycoming powered airplane.
The Perspective+ in the Cirrus G6 is based on Garmin’s G1000 NXi platform. The keypad is updated to a QWERTY keypad, allowing for quicker inputting of data since our fingers are already used to the setup. A home button was added to the center stack to get back to the map page without having to hold down the CLR key. The bug knobs were moved down to the autopilot, while the display of the GFC 700 was altered slightly to match the Vision Jet setup.
The Perspective+ also boasts a 10-fold increase in processor speed, allowing the system to move quicker than the standard Perspective. The ability to wirelessly update databases has also been included.
The exterior of the Cirrus G6 SR22 and SR20 models has changed as well. Cirrus has added the Spectra wing tip lighting system to the Cirrus G6. It incorporates an entire light panel that runs the length of the wing tip. The LED dual strobe setup helps with aircraft visibility and ramp appeal.
The SR20 engine has been changed to the Lycoming IO-390, 215 HP engine. The Continental IO-360-ES 6 cylinder engine comes out of the SR20 and the 4 cylinder Lycoming goes in. 2 less cylinders will help with useful load and the extra 15 HP will help with takeoff and climb performance.
The new Cirrus G6 is available for order and delivery immediately. To read all the details and specs on the Cirrus G6, you can check out Cirrus’ website.
Earlier this month, Cirrus announced the new Cirrus G6 SR20 and SR22. To the naked eye, they look like incredible airplanes. There is new lighting and the updated Cirrus Perspective+ avionics in both models, plus the SR20 is now a Lycoming powered airplane. The Perspective+ in the Cirrus G6 is based on Garmin’s G1000 NXi…
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 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:
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.
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
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.
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.
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.
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.
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.
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.
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…
Almost all IFR pilots are familiar with visual approaches and what the requirements are in order to fly a visual approach. As a refresher, the Instrument Procedures Handbook defines a Visual Approach as “an ATC authorization for an aircraft on an IFR flight plan to proceed visually to the airport of intended landing; it is not an [Instrument Approach Procedure]” (page 4-56).
For ATC to issue a Visual Approach, the pilot must have the airport or the traffic to follow in sight. Once the pilot reports the airport or the traffic in sight, ATC can clear the aircraft for a visual approach.
A limiting factor for a visual approach is ATC’s Minimum Vectoring Altitude. “This altitude, based on terrain and obstruction clearance, provides controllers with minimum altitudes to vector aircraft in and around a particular location” (Instrument Procedures Handbook page 1-42). ATC has to restrict aircraft to these MVAs, which can sometimes be quite high due to terrain or obstacles in the vicinity of the airport.
Every pilot has been in a situation with a high MVA that ATC can’t get them below, but it’s solidly MVFR or VFR at the destination airport. The MVA keeps the pilot in the clouds, so a visual approach isn’t possible since the pilot can’t see the airport or the traffic to follow. This can lead to extra time to go out and fly an approach.
Enter a Contact Approach. A Contact Approach is different then a Visual Approach. “The main differences between a visual approach and a contact approach are: a pilot must request a contact approach, while a visual approach may be assigned by ATC or requested by the pilot; and a contact approach may be approved with 1sm visibility if the flight can remain clear of clouds, while a visual approach requires the pilot to have the airport in sight, or a preceding aircraft to be followed, and the ceiling must be at least 1,000 feet AGL with at least 3sm visibility” [Instrument Procedures Handbook page 4-57].
Here’s the simplified explanation: A pilot does not have to have the airport in sight to request a contact approach. All that is required is for the airport to be reporting at least 1sm visibility and for the pilot to remain clear of clouds.
When would this be helpful for an IFR pilot? Good question. Here’s a scenario.
Pilot Smalls is about 20 minutes from his destination, which is an uncontrolled airport with only one approach to runway 17. He is approaching from the south and the initial approach fix for the approach to 17 is about 15 miles north of the airport. The airport is under Center control. When he has arrived at this destination in the past, Center usually could only vector him down to 4,000 AGL. He is very familiar with this airport and the surrounding area as he comes to this destination at least 2-3 times a month for business.
Pilot Smalls listens to the AWOS, which is reporting a 2500 foot scattered layer and 10 miles visibility. He knows it is right traffic for 17 since there is a 2,000 foot antenna on the east side of the field. There is some hilly terrain around, but all the terrain is well below pattern altitude and doesn’t cause a safety issue.
Looking out at the clouds, Pilot Smalls observes that the cloud layer is scattered to broken, but more scattered on the west side of the airport, with several large openings that he can see the ground through. Center asks for his approach request and Pilot Smalls requests a visual approach. Center gives him a descent to 4,000 AGL, their MVA for the area. They tell him to report the airport in sight for the visual approach.
At 4,000 AGL, Pilot Smalls is going through the scattered layer of clouds, but can see the ground in between the clouds and deems he has room to maneuver safely between the clouds and stay clear of them. He can’t see the airport, so a visual approach seems unlikely. He can’t cancel IFR because then he would have to keep the VFR cloud clearance and visibility requirements in Class E airspace (1,000 feet above, 500 below and 2sm horizontally), which isn’t possible in this case.
5 miles from the airport, ATC states, “N12345, I’m going to have to send you out for the approach since you don’t have the airport in sight.” Pilot Smalls then requests a Contact Approach. ATC clears him for the Contact Approach to his destination, so Pilot Smalls descends through a break in the clouds, remaining clear of clouds, until he gets below the base of the ceiling. He maneuvers onto the right downwind, lands and cancels IFR.
Contact approaches can be useful at controlled and uncontrolled airports. The first time you request one, do so with a higher ceiling and some room to maneuver to keep your safety margins. After you’ve done a few, you can determine what your personal minimums are for a Contact Approach.
I would not recommend doing a Contact Approach at an airport you are unfamiliar with. It’s vital to know what obstacles are around since on a Contact Approach, the pilot is now responsible for traffic avoidance and terrain avoidance, whereas on a visual approach, ATC resumes that responsibility.
Almost all IFR pilots are familiar with visual approaches and what the requirements are in order to fly a visual approach. As a refresher, the Instrument Procedures Handbook defines a Visual Approach as “an ATC authorization for an aircraft on an IFR flight plan to proceed visually to the airport of intended landing; it is…