EAA Airventure at Osh Kosh always draws great innovators every year, leading the aviation consumer to discover something new and different. Flying cars have always been a dream for the everyday pilot. Why not fly to work? Why not park the plane in the parking lot? Why not drive from the runway onto the freeway? All excellent questions!
Well, Samson Motorworks is trying to make those dreams a reality. Samson’s Switchblade flying car is in the (hopefully) finally stages of development this summer. The company expects to be able to conduct test flights early next year, then begin selling the experimental kit.
The Samson Switchblade will be in the Experimental category, but Samson has a builder assist program that only adds $20,000 to the final cost of the kit. The total price of the kit, which comes 49% completed and only takes 3 weeks to complete with the builder assist program, comes in at $140,000. That includes the engine, avionics (it’s equipped with Dynon’s 7″ Skyview glass panel display, a Dynon radio and transponder, a Dynon intercom, a Dynon AOA, an iPad mini, and an ADS-B GPS), and the builder assist program. Similar to a Cirrus, it is also equipped with a Ballistic Parachute Recovery system.
The Samson Switchblade has several different engine options, including a supercharged, liquid cooled, V-4 similar to a Corvette engine that will produce 190 HP. Max cruise in the air should be around 170 knots. The Switchblade will hold 30 gallons of mogas, burn 9 GPH in the air, and get 35 mpg on the ground. The gross weight will be 1,750 pounds.
How does the car to plane transition happen? Samson has developed a fly by wire system to retract the rudder down while the car is in drive mode. The wings use a mechanical linkage to fold up into the belly.
There are several different packages for the Samson Switchblade: the Snowbird, the Aurora, and the Trek options. Details can be found on Samson’s website.
I, for one, will be keeping an eye on the freeways next summer to keep an eye out for cars sprouting wings. No more traffic jams!
A new app came out last year that fits a need for many owners. Coflyt, available on the Apple App Store for $14/month for up to two airplanes, helps immensely with staying organized. Those questions of, “When is my oil change due?” or “Has the plane had it’s IFR inspections?” are easily answered by checking the app instead of having to dig through maintenance logs.
Not only does Coflyt help keep track of maintenance, but it also houses squawk lists that owner’s can send to maintenance shops as well as keeping track of Airworthiness Directives. If the pilot remembers at the end of flights to put the amount in, it even shows how much fuel is remaining in the airplane.
For flying clubs and partnerships, it provides easy scheduling without having to share calendars. Payments can also be taken and flights tracked. No more paper flight sheets after flights to track down.
As a pilot, it helps immensely to be organized. For $14 a month ($36/month for partnerships or flying clubs), that’s a small price to pay.
Figuring out the pattern altitude at an airport should be pretty simple, right? But, in this day of helpful technology, most pilots actually get it wrong. How can you always get it right? Well, it just takes about an extra 15 seconds. Here’s how.
John Wayne Airport Traffic Patterns
As outlined in the Aeronautical Information Manual, section 4-3-3, “traffic pattern altitudes for propeller-driven aircraft generally extend from 600 feet to as high as 1,500 feet above the ground.” Further, in the Pilot’s Handbook of Aeronautical Knowledge on page 13-10, it states: “1,000 AGL is recommended pattern altitude unless established otherwise.”
Okay, so for piston driver’s, we’ve got it narrowed down to 1,000 AGL (Above Ground Level for those who don’t like acronyms). But wait! There’s that very important phrase at the end of the last quote: “unless established otherwise.” That means not all airports have traffic pattern altitudes of 1,000 AGL, or else they wouldn’t put that line in there!
How do you find out what the TPA (Traffic Pattern Altitude) is for a certain airport if it’s not 1,000 AGL? Great question! Your first guess is probably to look on Foreflight. Though this is a good start, it is not the full answer.
Let’s use an example. Look up KAQO, the Llano Airport on Foreflight. At the top of the page, the airport elevation is stated as 1,101′ MSL and the pattern altitude is stated as 1,902′ MSL. From what we just learned, 1,902′ MSL is not 1,000 AGL, so is 1,902′ MSL otherwise established?
On the Airports page with KAQO pulled up, tap the A/FD tab, second to last on the left. Scroll down to Llano Muni. Read the whole entry. Does it state in the entry that pattern altitude is different than 1,000 AGL? It sure doesn’t. So, because it is not otherwise established, pattern altitude at KAQO is 2,102′ MSL not 1,902′ MSL.
Where did Foreflight get that? I have no idea. Too often, though, pilots look at the Foreflight pattern altitude and don’t actually check the Airport Facilities Directory (A/FD). Then, they get the pattern altitude wrong.
What does it look like when pattern altitude is otherwise established? Look up KSGR, Sugar Land Regional, on your Foreflight app. Foreflight states the elevation as 82′ MSL and the Pattern Altitude as 1,000′ MSL. Is this correct? Well, tap that A/FD button again and let’s find out.
On the second line of the A/FD entry, it says TPA-See Remarks. Down in the remarks section, we find the following:
TPA-1000 (918) single engine piston acft, TPA-1500 (1418) for twin and turbojet acft, TPA-500 (418) for helicopters within 2NM.
Foreflight got it right this time for single engine pistons, but if you are in a twin, the pattern altitude is different. What’s the lesson here? Always check the A/FD and don’t always go by what Foreflight says. The A/FD is always right and usually has a little more detail to help set you straight.
One last thing. Both the AIM and the Pilot’s Handbook of Aeronautical Knowledge, when talking about pattern altitude, state, “When operating at an airport, traffic pattern altitudes should be maintained unless otherwise required by the applicable distance from cloud criteria in…section 91.155.” 91.155 defines basic VFR weather minimums. So, to fully interpret what the AIM is saying, we have to take into account the type of airspace we are in to determine if we can safely and legally operate at pattern altitude at a particular airport.
For example, let’s say we are at KCVB, the Castroville Airport. Pattern altitude there is 1,602 feet, which is 829 AGL. CVB is Class G airspace up to 700 AGL, then Class E above that. Let’s say there is a 700 AGL broken cloud layer. Pattern altitude is 829 AGL, so you won’t be able to get up that high with a broken ceiling. What altitude can you do pattern work at to stay legal?
Class G VFR weather minimums during the day below 1,200 AGL is 1 SM visibility and clear of clouds. So, legally, you could fly at 699 AGL (which at CVB would be 1,472 MSL) while in the pattern and be legal. Safe? Maybe, but probably not if you are skimming the base of the clouds. Is 1300 MSL a safer pattern altitude in this example? Well, that is 527 AGL, so probably not, since towers tend to stick up that high sometimes.
Let’s go back to KSGR and put a 1,000 AGL overcast ceiling there. SGR is Class D airspace and we already determined pattern altitude there was 1,000 MSL for piston singles. VFR visibility and cloud clearance requirements in Class D airspace are 1,000 feet above clouds, 500 feet below clouds, and 2,000 feet horizontally from the clouds with 3 SM visibility. In order to stay 500 feet below the clouds, you would be flying a 582 MSL pattern. Safe? Probably not, though it is legal.
To summarize, don’t take Foreflight’s word for pattern altitude. Cross reference the A/FD (it only takes 15 seconds at the most) to verify. If it’s cloudy, it’s really best to stay on the ground, but if you want to find out your legal pattern altitude with a cloud deck, cross reference 91.155. I don’t recommend flying below pattern altitude because it is there for a reason.
This is the second part in a series on drones and Unmammed Aerial Systems (UAS). To read Part 1, Drones: A Brief History, please click here.
I’m surprised how often I’ve been asked about drones by concerned passengers as they load up for a charter flight. Most commonly I’m asked how many drones I’ve seen while I’m flying, or how many drones I’ve hit/ almost hit. Sadly, the media has made this drone crisis into something that it isn’t. I’ve never seen a drone while I was operating a full scale aircraft, and I’ve certainly never been put into a situation where I felt that a drone was a threat to my safety or the safety of the flight. In fact, I only personally know one pilot who has reportedly seen one around an airport and that was an isolated incident (and a non-event).
The reality is that while Unmanned Aerial Vehicles can be a real danger to full scale aircraft, incidents aren’t actually all that common and detailed information is often lacking or missing altogether. It is likely that some of the reported drone incidents were actually a case of a pilot confusing a loose balloon or a bird for a drone. This, combined with the media’s sensationalizing of every “close” encounter nationwide has led the public to believe that the problem is much bigger than it actually is.
In actuality, when the AMA (Academy of Model Aeronautics, the USA’s governing body for model aircraft) analyzed the data from the FAA’s 764 recorded Drone sightings, only 27 of them (3.5%) were actually recorded as “near misses” or “near collisions.” Additionally, only 10 of the records (1.3%) indicate that pilot was required to take evasive action.
The records also include reports of drone sightings at altitudes which would be impossible for civilian models to attain (19,000-24,000′). Finally, some of the sightings took place in areas which are specifically set aside for model aircraft and drones to operate. In those cases, the person flying the drone when it was reported was actually doing so in a safe and legal manner in an area designated for that specific purpose. If you’re interested, the whole article is available here and has a lot of great information.
As pilots, it is important that we do our part in helping reduce the risk of drone strikes. The biggest thing that we can do to help is to report any activity that we see so that it can be investigated and hopefully the drone operator can be found and dealt with. Try to get as much detail as possible about the incident, such as the size, color, location, direction and altitude of any sighted UAVs and report it to the closest tower or controlling agency.
Recently, the people in Washington have come up with a bunch of new rules to regulate the operation of model aircraft. As of this year, every unmanned aerial vehicle between 0.5 and 55 lbs must be registered with the FAA and have an FAA issued registration number located on the model itself. The logic here is that if someone crashes a drone where it shouldn’t have been operated, the officials will be able to identify the owner of the model and take action.
Model manufacturers and vendors have also agreed to start providing information about a program called “Know Before You Fly” (KBYF) in the packaging of the drones. This program seeks to help educate new hobbyists to the rules and responsibilities associated with model aviation. For more information on KBYF, here is a link to their website.
In the end, the sad reality is that it’s a combination of many factors: new technology making models cheaper and easier to fly, GPS navigation and automation, the media blowing the incidents out of proportion, and inexperienced and foolish operators which have caused the growing concern and required the FAA’s action. I think that it is important to understand that thousands of people have been flying radio controlled models for many years responsibly and this has never been a problem. The AMA has rules (which are the same ones now adopted by the FAA) regarding flying location, altitudes, speeds, and more which have kept both the modelers on the ground and the pilots in the air safe until now. Its a classic case of a few foolish individuals who have caused all modelers to be cast in a bad light.
There is no reason to fly in fear, though. A pilot should always be watching for hazards as he or she is flying, regardless of the variety. In fact, according to the FAA’s website, there were 142,000 wild life STRIKES with civil aircraft in the USA between 1990 and 2013. That seems like a much bigger concern to me than the 764 reported drone SIGHTINGS. As with any new technology, drones are suffering from growing pains. As the rules fall into place and new operators become better experienced, hopefully we will hear about fewer incidents on the evening news. Anyway, I’ll stop “droning” on. Fly safe.
Andrew Robinson is a 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania. He flies Pilatus PC-12s and instructs in Beechcraft Bonanzas.
We spend time training for them, but real-world emergencies are rare enough that it’s easy to get complacent. They don’t always happen to “other pilots,” though, and preparation can make a big difference when things don’t go as planned:
• What if you lose 500 rpm during takeoff, but the engine is running smoothly?
• What if the ammeter drops to zero during a flight in IMC?
• What if your left aileron develops a strong vibration in flight?
Our new seminar is full of expert tips on handling those “up here, but wishing you were down there” scenarios. We focus on how to keep abnormal situations from becoming full-blown emergencies, offer advice on keeping critical problems under control, and give our best advice on off-airport landings.
Find an AOPA Emergency Seminar near you!
Monday January 11, 2016-The Woodlands Waterway, 7pm-9pm
1601 Lake Robbins Drive, The Woodlands, TX 77380
Tuesday January 12, 2016-Wyndham Houston West, 7pm-9pm
14703 Park Row Blvd., Houston, TX 77079
Wednesday January 13, 2016, Holiday Inn San Antonio Airport, 7pm-9pm
77 NE Loop 410, San Antonio, TX 78216
Thursday January 14, 2016, Omni Austin Hotel at Southwark, 7pm-9pm
When a pilot first glances at the title of this article, the first thought that probably goes through that pilot’s head is, well that’s easy.
And it is, if you are flying a high wing Cessna. On other airplanes, there are a few tricks to checking the stall warning horn. If you get them wrong, you’re liable to get a bill from your maintenance shop for an hour of labor for a problem they couldn’t duplicate.
Cirrus SR22
Let’s start with the Cirrus. On the pre-FIKI Cirrus aircraft, there was a small little hole in the wing that contained a diaphragm. That diaphragm sensed a change in airflow at a certain angle of attack just below the critical angle of attack and set off the stall warning horn. Unfortunately, the only way to check that is to suck on the hole during pre-flight.
I don’t. I verify the hole is clear and that’s about it.
On the FIKI Cirrus aircraft, there is actually a stall warning vane. It looks like a high wing Cessna vane, but if you turn the batteries on and try and get it to come on during your light and pitot heat check, nada.
Here’s the trick, and the checklist doesn’t do a good job of describing this.
Turn on the Avionics Master
Turn on the speaker
Put the flaps to full
Then move the stall warning vane and you’ll hear the horn
The speaker and the Avionics Master are so you can actually hear the horn (if you had the headset on while you were doing this, the speaker would be unnecessary). The flaps have to be full because the pitch attitude for the critical angle of attack is lower with the flaps down, so the horn goes off when at a different angle. You then don’t have to use as much force to push the vane.
Piper PA46
The early -310P Malibus are pretty simple and straight forward. Move the vane, get the horn.
In the -350P, you can’t get the horn to come on by moving the vane. So, Piper put a stall test button that’s hidden underneath the upper left side of the instrument panel. Push that to test the horn. On the G1000 PA46, it is located directly above the PFD. On the Avidyne, it’s below and to the left of the pilot’s yoke.
Testing the stall warning horn is a very important part of pre-flight. A pilot needs to know if the aircraft is close to a stall. The advent of Angle of Attack indicators in small, GA aircraft, have added a greater awareness to the angle of attack during all phases of flight to avoid those stall spins.
If the stall warning horn goes off or the AOA shows yellow, lower that nose immediately.
We have all seen the little first aid kits that a pilot can get to carry in an airplane. It usually has some bandaids, maybe some gauze, and some antibiotic ointment. Very helpful in the even that your paper VFR chart cuts your finger when you are unrolling it.
What happens if you crash in a harsh environment and you have some actual injuries to take care of?
Enter the Guardian Seven Trauma G7-Alpha Trauma and Egress Kit. It literally is a First Aid Kit on steroids.
Guardian Seven Trauma has put together a kit that contains just about anything you need to take care of an injury from an airplane crash. Plus, the kit only weighs less than 2 pounds. It easily mounts in an aircraft and can be opened with only one hand.
