The massive storms that rolled through the Austin Bergstrom and San Antonio areas last Friday not only put a dent in the landscape, they put a dent in the skies too.
The Austin Bergstrom (KAUS) control tower suffered significant flood damage Friday. 6 inches of rainfall in an hour caused water to come pouring into the first floor of the tower, flooding the radar room and knocking out the power. This led to transmission outages for the tower, ground control, clearance delivery and the ATIS. Similar to the Chicago Center fire last year (though this was a much smaller section of airspace), the area normally controlled by Austin Approach was replaced by a big, gaping radar hole.
By 8:45am on Friday morning, the Austin Bergstrom airport actually closed. One runway eventually opened back up Friday afternoon, but massive delays and cancellations had already taken place. All the ILS approaches were down and Houston Center had taken over the airspace normally occupied by Austin Approach control.
A temporary, emergency tower vehicle was brought in by the FAA (it’s essentially an RV with communications and a giant window) by the end of the weekend. All arrivals and departures were restricted to 17L and 35R.
Due to the radar outage, I heard there was as much as a 4 hour delay even for planes coming into Austin Bergstrom from Dallas, and that was in VMC conditions on Sunday and Monday. Tuesday and Wednesday brought IMC conditions which only enhanced the delays.
The latest news is that Austin Approach will be opening back up, but in a satellite base in San Antonio. The Austin controllers will be using the SAT radar room and will be receiving their radar picture via satellite. The approach frequencies should be up and running today or tomorrow. The Austin Bergstrom tower is up and running and most of the ILS approaches are operational at this point.
In the meantime, expect delays going in and out of Austin. If you don’t have to get to AUS, EDC, or GTU, you’re better off delaying a day or two until Austin Approach is back up and running.
When flying a WAAS GPS approach, there are several different levels of WAAS signal that a GPS receiver can get. The most precise is an LPV signal. LPV stands for Localizer Performance with Vertical guidance. An LPV approach has the lowest minimums of all the WAAS GPS approaches, typically in the range of 200-300 feet AGL. A GPS glide path (GP) is guaranteed with an LPV approach and the minimum altitude is a decision altitude (DA).
Just like a localizer, an LPV course width get’s tighter and the CDI becomes more sensitive the closer the plane get’s to the runway. Even though the LPV approach minimums are so low and the approach is down to a DA, they still aren’t considered precision approaches by the FAA (which leads to some extra planning when selecting an airport as an alternate that only has GPS approaches, since the AIM specifies only the LNAV minimum are to be considered if an alternate airport only has GPS approaches, bringing the 800 foot ceiling requirement to bear)
An LNAV/VNAV approach is still a WAAS approach that has a GPS glidepath, but is slightly different than an LPV approach. An LNAV/VNAV final approach course does not get more sensitive the closer the plane gets to the runway. The smallest course width on an LNAV/VNAV approach is 0.3 miles either side of center. LNAV/VNAV approaches will, most of the time, have higher minimums than LPV approaches and can have minimums no lower than 250′ AGL.
The third type of WAAS approach is strictly a non-precision approach with a Minimum Descent Altitude (MDA). These are designated LP approaches, which stands for Localizer Performance. These are like old school Localizer only approaches that, similar to the lateral portion of an LPV approach, the course width tightens the closer to the runway that a pilot is. There is no glide path by definition of an LP approach, though there is a caveat.
Now, by looking at an approach plate that is a WAAS approach, but only has LP minimums listed, a pilot would assume there would be no glide path. Depending on what type of GPS unit the airplane has, that pilot could be wrong. Garmin Perspective units (Cirrus G1000), all GTN 750s and GTN 650s, All G1000 NXi units, most Garmin 430W and 530W, and all Avidyne IFD 550/540 and 440 units will display an advisory glide path on an LP approach, designated LP+V.
What does LP+V indicate? An advisory glide path is just advisory, but it is totally legal to follow down on a non-precision LP approach. The kicker is obstacle clearance is not guaranteed and the pilot needs to keep an eye on minimum altitudes at the different waypoints on the approach. The big thing I tell people is, when you arrive at the MDA and the runway is in sight, following the advisory glide path below the MDA could get you in trouble with obstacles. Don’t just hone in on your instruments when you break out of the clouds. Look out the windscreen and make sure you won’t hit anything.
If you arrive at the MDA on the advisory glide path and the runway isn’t in sight, DON’T GO BELOW THE MDA! Most autopilots won’t level off at the MDA, even if that altitude is set in the altitude pre-select, so this will involve turning off the autopilot before the MDA and manually leveling off, or engaging the altitude mode of your autopilot at the MDA.
One other type of GPS approach that you will encounter is an LNAV approach. This is a non-WAAS approach down to an MDA, but your GPS unit may still give you a +V. Most modern ones will.
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.
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.
If you’ve ever been to Nantucket Airport during the summer, you’ll understand when I say that it is a crazy place. During the summer months, especially on weekends, the airport is visited by an endless parade of airplanes ranging from the smallest GA airplanes to the biggest private jets.
One sunny Sunday afternoon I was standing in line at the front desk of the Nantucket FBO when the ramp door opened and a very grumpy and entitled man walked in. The man marched right up to the front desk and barked a fuel order at the girl working there, which she mistakenly read back wrong. After yelling at her for her wrongdoing, he announced that he had flown in to go to the restaurant and stormed off to drown his sorrows in fish and chips. Although he was a jerk, his attitude got me thinking about FBO’s and everything that the people who work at them do for us pilots.
For anyone who may not know, FBO stands for Fixed Base Operator. FBO’s can be found at airports everywhere and their business is to provide services such as fuel, hangar space, and tie downs. Bigger FBO’s can offer more services including rental cars, food, maintenance, flight instruction, etc. FBO workers have the ability to make life really good or really miserable for pilots, and, it seems to me, we pilots have the same power over them. Based on my personal experiences and the experiences of some friends who have worked at airports around the country, here are some things to think about next time you taxi onto an FBO ramp.
Landmark Aviation has the best pens
I’ve divided this article into two sections:
FBO Etiquette: What can we as pilots do to make life easier for the workers at the FBOs
FBO Pilot Perks: Ways that FBOs can help make a pilot’s life better (besides basic services like fueling)
FBO Etiquette
Be Polite
Everyone I talked to about their time working at an FBO said that simply by being friendly and polite is one of the biggest ways we can help. Most of the people that work at the FBOs love aviation and likely are working there to be around the industry in hopes of eventually being more involved. The girl working the desk at Nantucket didn’t deserve to be yelled at just for reading a tail number back wrong; don’t forget that “please” and “thank you” are still magic words.
Call Ahead
Whether you are flying to the airport, or you left your airplane at the FBO and you need them to pull it out or fuel it, calling ahead is greatly appreciated. Most FBO’s have a radio at the front desk and have their frequency listed online and in foreflight. Call ahead and tell them that you’re coming, when you’ll be arriving, and what you’ll need when you get there (gas, rental car, taxi..etc). That way they wont feel rushed and you may get what you’re looking for more expediently upon arrival.
Fuel orders
If your fuel order is difficult or confusing (example: 6.54 gallons in the right side and 4.32 in the left) you may be better off just to do it yourself at the self serve. One of the guys I talked to said that he would have pilots ask for extremely specific numbers and then stand there watching, ready to pounce when it wasn’t fueled exactly right. Its also worth noting that fuelers do make mistakes. Its highly recommended to watch and make sure that the correct truck (Jet A or 100LL) is the one pulling up to dispense your gas. Make sure you check that the fuel caps are properly installed before departing.
Look outside
A lineman motions for the pilot to stop.
Taxiing onto the ramp is not the right time to be doing your after landing and shutdown checklists. Wait until the airplane is stopped before taking your eyes off the person marshaling you to your parking spot. I’ve been told that it isn’t uncommon for a pilot to be looking inside while taxiing and it makes the linemen very nervous as they are motioning to the pilot to stop (For those unfamiliar, with lineman hand signals, here’s a helpful link).
Brakes
Unless you have talked to them and get the okay, don’t leave the parking brake on when leaving your airplane at an FBO. Often the lineman will direct you to park upfront to make loading and unloading easy, but if you’re going to stay for a long period, the airplane will need to be towed and parked out of the way. Leaving the parking brake on can make serious headaches for the people trying to organize the ramp after you leave.
Lights
Don’t blind the poor guy parking you by leaving all your landing, taxi, and recognition lights on as you’re pulling into your spot at night. Likewise, when you are ready to leave your parking space, its courteous to signal the person waiting in front of your airplane by flashing one of your lights at them so they know you are ready to be directed off of the ramp.
FBO Pilot Perks
Good parking
This one is pretty basic. I’ve heard through the grapevine that you may get parked in the boondocks as punishment for being rude to the FBO staff. However, if asked, much of the time they can pull your airplane right up front and may even let you pull a vehicle onto the ramp to load people and bags more easily.
Cheaper hotel rooms/ rental cars
Some FBO’s have special rates with hotel and rental car companies around in the area. Although it varies from place to place, you may be surprised with the amount you can save on these travel essentials. I had a flight last week where I called and was given a quote of 185 dollars for a rental car…after telling them that I was parking at the local FBO, I got the special price of 125. Check with the FBO you will be stopping at for any of their current offerings.
Fuel discounts
Sometimes the price of fuel or the minimum uptake to waive the fees can be negotiated. Sometimes, the fees may be forgotten entirely. If you are unable to take the minimum amount of fuel to waive the landing or ramp charges, tell them what you can take and you may be pleasantly surprised with the response. Its not uncommon with our Bonanza that even though the “minimum” may be 20, I can waive the fees by up-taking 10 or 12 gallons instead.
Points/ Rewards cards
Some FBO’s offer incentives to pilots for buying gas. Many of the rewards programs are free to sign up for and will pay the fuel purchaser cash based on how much fuel they buy over a specified time period. I am a member of the Avtrip program which rewards fuel purchases at Avfuel airports with points that are redeemable for money. Avtrip is just one example of an FBO fuel rewards program; if you fly regularly, it may be worth looking into whether or not there is a fuel rewards program you can take advantage of.
Crew Cars
Most FBO’s have cars designated for use by the pilots. They are extremely nice for going to get lunch or taking care of whatever short errands you may need to run around town. Most crew cars are limited to about 1-2 hours of use, but they can often be loaned out longer based on the discretion of the people working the desk. On a few occasions, I’ve had the cars loaned to me for longer, even over night, by the nice people at the FBO (They always appreciate pilots splashing a few gallons of auto gas into the cars while they are out, too).
FBOs and the services that they provide are invaluable to pilots, both commercial and private. If we as pilots are willing to work with the linemen and service reps we can make both our lives and their lives easier. Remember to be polite and don’t be afraid to ask if you need something….that’s what they’re there for!
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.
Talk about star treatment. The Lajitas Golf Resort rolled out the red carpet for the 2019 Texas Top Aviation Lajitas Fly In. I had been to Lajitas twice before; once in July when it was hot, miserable and bumpy. The second time was the week before our Fly In. Both times, everyone from the airport folks to the bus drivers to the front desk and restaurant staff were top notch. It made for a very pleasurable experience.
If you haven’t been out to Lajitas (or don’t even know where it is) and you’re a pilot (you don’t even have to play golf), you have missed a sure gem. Lajitas is positioned on the southern tip of the Big Bend area of Texas, right on the Rio Grande river. Lajitas has great lodging with several different room options from big to small, an excellent restaurant for 3 square a day (and even a bakery for sweets, coffee, and breakfast tacos in the mornings), and a 5 star golf course in Black Jack Crossing.
Why is this all relevant to us aviators? Lajitas has it’s own private airport, 89TE. Complete with a 5,500 foot asphalt runway, VFR conditions most of the year, and reasonable fuel prices, Lajitas is the pilot’s gateway to the resort and the entire Big Bend area. If you wait until the fall, a brand new, 7,000 foot concrete runway should be completed and an IFR approach should be available. An AWOS is in the works too.
The resort and airport are so far south, radar and radio coverage with Albuquerque Center is pretty poor below about 15,000 feet, and non-existent below 10,000 feet. This isn’t a big concern as any airplanes in the area should be on 122.9 and the airport manager will make contact with you, give you a weather report, and assign a runway.
Once you are on the ground, there will be a resort bus waiting to whisk you and all your friends to the resort for your getaway.
The 2019 Texas Top Aviation Lajitas Fly In was a big hit. We had 7 airplanes total: 5 Cirrus SR22s, 1 Piper Matrix, and 1 Citation M2. There were 15 attendees total, including 13 golfers. Everyone raved about the resort and the golf course. The only hiccup in the weekend was the cold front that blasted through on Friday afternoon, kicking up a lot of dust. Golfing on Saturday was windy too, but Sunday morning was absolutely perfect.
Thanks again to the folks at Lajitas for the star treatment!
Interested in participating in the next Texas Top Aviation Fly In? Contact Us or Sign Up for Our Newsletter and we will make sure you find out about the next one so you don’t miss out!
In July, a Cirrus SR22 suffered an engine failure in Houston after departing KIAH. The CAPS system was deployed and the airplane came to rest in a neighborhood on the north side of Houston. This makes CAPS save number 53 for Cirrus and no fatalities. The initial NTSB report is below.
14 CFR Part 91: General Aviation
Accident occurred Tuesday, July 07, 2015 in Houston, TX
Aircraft: CIRRUS DESIGN CORP SR22, registration: N422PB
Injuries: 2 Minor.
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 July 7, 2015, about 1137 central daylight time, a Cirrus SR-22 single-engine airplane, N422PB, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed in a residential neighborhood at Houston, Texas. The pilot and passenger sustained minor injuries, and the airplane was substantially damaged. The airplane was registered to and operated by AIRCCS, LLC; Humble, Texas, as a 14 Code of Federal Regulations Part 91 business flight. Day visual meteorological conditions (VMC) prevailed and a flight plan had not been filed. The airplane departed George Bush Intercontinental/Houston Airport (IAH), Houston, Texas, at 1133 and was destined for Austin Bergstrom International Airport (AUS), Austin, Texas.
The pilot reported that during initial climb, he noticed the engine temperatures began increasing and he reduced power in an attempt to lower the engine temperatures. When the airplane was about 900 feet above ground level (agl) the engine began detonating, and soon after there was a complete loss of engine power. With no suitable forced landing areas the pilot deployed the CAPS ballistic parachute system and the airplane impacted terrain and came to rest upright next to a residence.
An initial on-scene wreckage examination showed there was adequate fuel on-board. At the facility where the airplane had most recently been refueled, refueling unit records and a review of security camera video showed that the airplane had been refueled with aviation gasoline and not with jet fuel. Postaccident fuel quality checks of that fuel facility were satisfactory.
The wreckage was moved to a different location and will be further examined. Several avionics components containing non-volatile memory (NVM), including engine performance data, will then be removed from the wreckage for examination and an extraction of useful data is expected.
At 1053 the Automated Surface Observation System at IAH reported wind from 160 degrees at 15 knots gusting to 20 knots, visibility 10 miles, scattered clouds at 3,000 feet agl, broken clouds at 25,000 feet agl, temperature 31 degrees Celsius (C), dew point 24 degrees C, and an altimeter setting of 30.03 inches of Mercury.
