Tuesday, December 20, 2011

Lost

According to this article on AirTrafficManagement.net, as well as others, the Federal Aviation Administration is getting serious about decommisioning as many VHF Omni-Range (VOR) stations as possible, leaving behind a skeleton system in case of GPS failure. This is a testament to the success of the GPS and WAAS programs, which have demonstrated their utility and reliability over, what, millions of flight hours?

I'm an old-fashioned guy: yes, I own a sextant, but the last time I tried to take a sight I had to knock on my neighbor's door and ask when he had moved to Montana (and that was so long ago that he has since moved to Utah). But I don't use the sextant in flight, and in fact with the rise of tablet apps (I've been using both Skycharts and FltPlan.com), I don't use paper anymore, either. I have a current sectional chart for my local flying area, and current Low/Enroute IFR charts, but when those expire I will probably switch to WAC charts for "emergency" back up. I use a yoke-mounted VFR GPS for navigation, which merely supplements the VOR/DME for IFR flight, of course (our club can't afford a panel mount GPS right now).

One other thing: I miss keeping a paper navigation log, but have found a nice hack: make a pdf of the navigation log from whatever source you like, and open it in uPad, another app. This allows me to write on the nav log, noting clearance, OOOI times (Out-Off-On-In), time-of-station-passage, times when I switched tanks, and the like.

Do you have trouble remembering the ATIS code? I form the letter in American Sign Language; that little bit of multi-modal memory manipulation seems to do the trick. Some pilots "write" the ATIS code on the yoke with a finger. Same idea. As for the ATIS content, I set the altimeter, so there's no need to write that down, and then pull up the approach to the runway in use, so there is no need to write that down, either.

But back to the VORs. I still use them!, even when flying VFR. I know I'm not supposed to, but I hearken back to this advice from Bowditch's American Practical Navigator, available online from Wikisource:


[Navigation] includes the routine use of several different navigational techniques, both as operational checks and to maintain skills which might be needed in an emergency. Any single navigational system constitutes a single point of failure, which must be backed up with another source to ensure the safety of the vessel.

So I still tune VORs.

Many years ago, when airliners had VOR and DME (no groundspeed) and ADF, I was a passenger on a United flight to San Diego, dutifully listening to Channel 9 (United puts ATC on its entertainment system). The whole way from Chicago the Morse letter 'W' could be heard in the background. What was 'W'? Checking the charts when I got home, I saw that 'W' was a powerful marine beacon located at Point Loma, near Lindbergh Field. Somebody up front wanted to have a needle pointing to San Diego for the whole trip...

Alas, marine beacons have disappeared from aeronautical charts. The most interesting area was Long Island Sound, where all of the beacons were on the same frequency but transmitted on a schedule. Thus, you could triangulate with a single receiver: one line of position from beacon #1, the next minute a LOP from beacon #2, the next from #3, and there you were!

Here you see an old (1989) Sectional Chart Legend, showing the beacon in question and how to use it. The "H+00 & ev6m" for Point Loma beacon (identifier W) indicated that it broadcast for the first minute of the hour, then every 6 minutes. So, if your watch was accurate, and the time was H+06, you knew that you were listening to Point Loma. There were other beacons along the coast, with broadcast schedules "H+01", "H+02", etc.

Some people used these.

Some people still tune VORs.

Some people still tune ADFs.

Some people take comfort in seeing the the appropriate constellation ahead.

Not just me.

BUT, the question is whether this is worth the expense of maintaining all of
those stations. (I'm not suggesting that we decomission the North Star!)

Probably not.

Labels: , , ,

Thursday, September 1, 2011

Finally...

I got my medical yesterday morning (second class, since the FAA is being generous this season), but didn't use it until last night: I needed night currency (when I was a Sport pilot, night currency was moot, since Sport pilots are limited to Day VFR). This was real night currency, none of this full-Moon-on-a-snowy-evening stuff. Last night had no Moon and there was a lot of smoke around, even though the visibility stayed above 10SM the whole time.

The winds were all over the place so it was hard to fly a square pattern, but I managed good touchdowns. After two stop-and-go landings I switched to touch-and-goes, knowing that my final landing would be the third full stop.

When the tower closed I switched to left traffic and the wind was pushing me toward those unlit hills to the East. Since I was only "staying in the pattern" I had not rigged my handheld GPS with its terrain display. I don't need a terrain display, but having seen it (and verified its performance against some known threats) I know that my procedures plus the terrain display is more comfortable than procedures alone.

Fatigue set in after about an hour and I landed. I enjoyed the airport silence while I tied the airplane down. I drove home, listening to jazz. Just what an evening should be.

Finally.

Labels: , ,

Tuesday, August 9, 2011

Stick and Rudder

[revised 9 August]

The F'n A A has been sitting on my application for a Special Issuance medical certificate for 53 days, so I'm restricted to Light Sport privileges (basically 2 seats, Day VFR, maximum weight 600kg). This is lots of fun, and it raises some interesting questions about flight training.

The Ercoupes I've been flying are intriguing airplanes. As I understand it, Fred Weick designed it to be safe, inexpensive, and fun. Most 'Coupes have aileron-rudder interconnects, eliminating the need for rudder pedals.

I used to think this was a travesty, and it makes me feel good about my skills to note that I'm better coordinated.

But now I'm beginning to think that the 'Coupe might be an ideal training airplane for the 21st century. One reason for this is the rise of the Light Sport category, which demands airplanes that are safe, inexpensive, and fun. There are some impressive LSA airplanes that look like fun: the ideal vehicle for, say, a skinny retired couple to explore the country. But these are expensive. Right now you can buy a flyable Ercoupe for $25,000, and maybe come February in a tough economy you will be able to find one for less. They need some TLC, but this can be fun, and costs a lot less than the $100,000+ new planes.

And, although I have mixed feelings about FAA certification (there is no reason for me to spend 7 summer weeks without a medical certificate), the Ercoupe is a CAA-certified airplane; the newer LSA airplanes are not certified at all, but are built to industry standards. Certification involves oversight by someone without a dog in the fight. I have seen corners cut in aviation.

But what about the flying part of the Ercoupe? I cannot look at you with a straight face and tell you that it is a stick-and-rudder airplane: it doesn't have rudder pedals! I've written before (and will again) about the importance of basic flying skill at all levels of aviation, especially slow flight and stalls. The 'Coupe won't stall!

By contrast, an Airbus 320 has little use for rudder pedals, and won't stall.

So what can one learn about flying? Well, try this: the other day I was out in an Ercoupe when the weather turned threatening and the wind picked up. As I approached the airport the wind sock showed light winds, but groundspeed on the upwind leg was low. I anticipated a fast downwind and wind shear on final. It felt early to turn base, but in fact I was high with a pretty good crab angle. Bump bump bump and now I was low with a pretty good crab angle, the other way. I touched down on the centerline in the crab, and the 'Coupe did its thing and we tracked straight until the runway exit.

Flying that pattern required a large number of transferable skills, skills that apply in every airplane from a single-seat glider to a 777. It did not require every single flying skill, but no maneuver does.

What about navigation? The Ercoupes I've seen have navigation equipment varying from a magnetic compass to a abasic IFR panel. The IFR panel is heavy, which is a problem: to quote Burt Rutan: before you install something in your airplane, hold it at arm's length and let go. If it falls to the ground it is too heavy. But a high-quality handheld GPS is neither heavy nor expensive. You may not use it to file IFR, but you can certainly use it to learn modern navigation. The right IFR GPS (or iPad app) can give a student NexRad radar, EGPWS, and airborne access to METARs and TAFs. There's no autopilot so it won't be tha hands-off flying that the Airbus driver enjoys, but there's still a lot of transferable skill to be learned.


The Ercoupe has wonderful visibility, making it easy (and fun!) to watch for traffic. That's a good habit.

So while the Ercoupe cannot make a complete pilot, no one airplane can, either. A wise instructor could produce a skilled professional pilot by supplementing the Ercoupe with a desktop Flight Training Device for learning instrument scan, and a light twin for learning to use the rudder. Both are important preparations for a flying career.

What do you think?

Labels: , ,

Sunday, June 19, 2011

Space Weather

It was March 13, 1989, in Utica, NY. My apartment was rather spare but it had a nice view North across the Mohawk Valley. There was plenty of privacy - the nearest prying eyes would have been 15 miles away - so I often left the shades up to sleep.

That night I had to close the shades. My bedroom was fully lit, but not with a steady glow. The greenish light danced and leapt around the room; it might have kept me up all night. Looking out the window revealed the most intense aurora borealis I have ever seen.

I had it lucky. The province of Québec lost all electrical power that night. The solar storm that caused the aurora also disabled the power grid.

That was my introduction to space weather, the study of the bands of charged particles that surround the Earth (the ionosphere), which are just as intricate and fascinating as the atmosphere. Its nature wasn't really understood until 1958 when the Explorer satellites made in situ observations. Prior to that, we knew that something caused the auroras at the poles. Admiral Byrd in his book Alone talked about measuring the aurora australis by triangulating. He spent the austral winter alone in a cabin (where he nearly died from CO poisoning), making observations, which were later compared with observations made at Little America, his Antarctic base.

A recent article in the New York Times was surprisingly shallow, except in making pilots look bad. To quote from the article:

"...a space weather forecaster we know at the National Oceanic and Atmospheric Administration often tells a story of a conversation he had with a pilot:

"Pilot: 'What do you do for a living?'

"Forecaster: 'I forecast space weather.'

"Pilot: 'Really? What’s that?'”



So, why should pilots care about space weather? Start with the South Atlantic Anomaly (SAA, a permanent feature). NASA pays close attention to the SAA, to the point that it is prominently displayed on the screens at Mission Control. For reasons that I do not quite understand, the Van Allen radiation belts are lower in this region, exposing orbiting spacecraft (and their occupants) to more radiation. This disrupts communications; actually, it disrupts anything electrical. (What I don't understand is, given the Earth's rotation, why this does not occur at every longitude.)

Wish as we might, most of us aren't astronauts. But every time you press DIRECT on a GPS you are a rocket scientist. Well, maybe not you, but there are bunch of rocket scientists in the picture.

The problem is that the GPS signals have to go through the ionosphere, which slows them down. Remember that GPS receivers calculate a pseudorange to each satellite, putting you on a gigantic sphere, and the intersection of four of these spheres defines your position in space. Then, using the WGS-84 model of the Earth (or one of its refinements), the receiver calculates your latitude and longitude.

The GPS position calculation assumes that the signals travel at the speed of light, and, knowing the position of the satellites from the ephemeris, determines which sphere your on. Originally, the system used two ionospheric corrections each day, but that was too crude. Here's the space weather: ionospheric storms that can really slow the GPS signal can last as little as fifteen minutes! So a twice-daily correction didn't cut it.

If your receiver can use two frequencies it can estimate the ionospheric delay, but older civil receivers only had access to one frequency. (Many of these are still in use.) So, again we were out of luck.

A lot of smart people put a lot of work into figuring out how to monitor this and other effects on the GPS "Signal In Space", and the final result is WAAS, the Wide Area Augmentation System. WAAS monitors the GPS signals at many locations, calculates corrections, and broadcasts them from a geosynchronous satellite. Most new GPS receivers are WAAS capable, and this leads to unbelievable accuracy and reliability.

We are approaching the peak of the sunspot cycle, although the Sun has been uncharacteristically quiet the past couple of years. More sunspots means more interactions with the ionosphere and more chances for a massive GPS outage.

Check out Spaceweather.com if you'd like to learn more.

Labels: , ,

Wednesday, August 11, 2010

Through A Glass, Lightly


I have to admit to being a little disingenuous with my last post discussing the perils of the glass cockpit, because even as I wrote it I knew that I was planning to buy a new portable GPS to replace my beyond-aging Trimble Flightmate, whose database expired in 1995. The Flightmate worked fine as a GPS: its position, track, and groundspeed estimates were as good as any of the more more modern units, even without WAAS. But Trimble no longer supports the unit, so no database update is available. There is no moving map, although I still say that I don't need a moving map. And, worst of all, the older chip uses a lot more power than a modern chip, so battery life is poor, and the Trimble had a really clunky power cord that was always in the way.

In my mind, the position sensor is irrelevant: what we do now is database navigation, not GPS navigation. Pilots need to think about the flight as a whole, not as the next fix, and the habit of thinking a flight through will carry over into more advanced flying.


So yesterday's UPS brought me a new Garmin Aera 500 and an excuse to go flying. Knowing the perils of head-down time, I invited an advanced student to ride along, as well as my son.

The unit just blew me away, in the good sense. The yoke clip fits intuitively, with no restriction on the controls. There is only one cord, which is built in to the yoke clip (nobody has mentioned this, and I think it's a terrific idea), so the cockpit no longer resembles the floor of an Italian restaurant at the end of a long night of dropped spaghetti.

I found it easy to program, and it has all of the approach intersections, although not the full procedures (more on this later). Its terrain warning module stays in the background until there's a problem, when a window pops up with red and yellow warnings and Xs to mark where you will hit. While there are some problems with this, of which I've been aware for a long time; see my essay in RISKS 19.56, I am convinced that it still leaves us better off than we were before.

Part of my prepurchase debate with myself was the following: the cost of these units approaches the cost of used panel-mount IFR GPS, with which I could file IFR; the aera is definitely not for IFR. But an informal poll of the members of my flying club led to the conclusion that we are a VFR club. Only two other members are instrument-rated, and neither of them is current. So the improved navigation is something that I want, not the club.

The thing is, you can still use the aera to monitor an instrument approach. It doesn't do all the things that an IFR unit would do, nor is it legal even if it did. The aera will put the final approach waypoint and the missed approach point into the flight plan, but the Aeronautical Information Manual is very clear that we can only fly IFR approaches retrieved from the database. Still, if you insert the transition waypoints into the flight plan and get yourself on a segment before "loading" the approach, the fixes are all there.

I see a lot of training value in this. A student under VFR can load the approach (using almost the same keystrokes as in the panel mount Garmins) and practice, say, an area arrival. The instructor can ask the student to make the same calls (for example, "Approach Active" when 2NM from the FAWP). The student has to recognize the step-down fixes and read the chart to fly the appropriate altitude. It may not count as an RNAV approach, but the student gets the experience and will be much closer to the Escoffier standard of instrument proficiency when he or she moves up.

I think you can teach someone almost all of the ins-and-outs of a modern glass panel with the unit. I tcompares well with the various IFR GPS units I've used, and even the UNS-1 I flew in a King Air. In some ways its terrain display is more intuitive than the one in the King Air, which didn't do anything except squeek "terrain" at awkward moments unless you chose that page on the MFD.

In my case, teaching at a school with no glass cockpits and no panel mount GPSs in the trainers, this may be the only way I have to get a student to learn something about 21st century navigation.

With the Trimble, I could only teach 20th century navigation.

Labels: , , ,

Thursday, May 27, 2010

NextGen, GPS-style


No, not the FAA's NextGen, but the GPS system. A Delta IV rocket took the first of the "Block IIf" satellites into orbit today, after several aborts (including one atT-minus-6 seconds) and delays. The new satellite will transmit on the L5 frequency. This satellite is a completely different design from SVN49, and one hopes that there was more testing. According to the US Air Force, it will take 3 - 4 months before the satellite is marked "healthy."

There are more than enough birds on orbit, but as I mentioned last week they do have a finite lifetime.

Labels:

Friday, May 21, 2010

SVN49 and Old Possum's Book of Practical Cats


I've been trying to piece together the story of SVN49. What's SVN49? Is it one of those unpronounceable high-altitude fixes that Center uses to steer you around uncharted military airspace (those of you who fly in the flight levels in the west know what I mean)? Or an oceanic fix? A proposed regulation? SVN49 won't affect me in my Cherokee Six or glider, right?

Wrong. SVN49 is a GPS satellite. Everyone in the world uses GPS, if not for navigation then for timing, so everyone should be worried.

Why haven't you heard of SVN49? A GPS satellite is like a cat. T. S. Eliot wrote



The Naming of Cats is a difficult matter,
It isn't just one of your holiday games;
You may think at first I'm as mad as a hatter
When I tell you, a cat must have THREE DIFFERENT NAMES.


We can counter with



The Naming of Sats is a difficult matter,
It just isn't one of those rocket nerd games;
You may think that these geeks are as mad as a hatter
When they claim a sat must have THREE DIFFERENT NAMES.


Obviously one of the names is SVN49; SVN stands for space vehicle number. The second name is NAVSTAR 63; NAVSTAR was the original name of the GPS program. And the final name, the one that belongs to "no other sat," is PRN01.

PRN01 should ring a bell; you've probably seen NOTAMs like

!GPS 12/064 GPS NAV PRN 25 OTS WEF 0912181500

Aviation GPS receivers usually refer to satellites by their PRN. PRN stands for Pseudo-Random Noise, and is one of the engineering marvels of the GPS system. The original GPS system had all of the satellites communicating simultaneously on two frequencies, called L1 (1575.42 MHz) and L2 (1227.60 MHz). You've heard the mess that results when two airplanes transmit on the same frequency: lots of noise followed by someone saying "Blocked." But that's the standard GPS communications environment.

The receiver gets the navigation data from one satellite at a time using CDMA (Code Division Multiple Access), which is also called spread spectrum encoding. Many cellphones use the same technique to allow simultaneous conversations on the same frequency. The technique was invented by, and patented by, the actress Hedy Lamarr during World War II. Her patent expired before the advent of GPS, so while her estate gets no royalties her name is revered in GPS circles. PRN01 refers to the specific binary code assigned to good old NAVSTAR 63.

SVN25, or PRN25, is out of service for a very good reason: it was launched in 1992, and has given its all for the cause. Much like the LGU VOR, which has been off the air for years and years, the satellite lives on in the NOTAM telling us not to use it. RIP. SVN49, however, is still begging at the door to be let in. It has been assigned PRN01, so we can tell its signals from all other signals, but its status is ominously unhealthy, so your receiver ignores it.

We all know that the FAA NOTAM system is a mess, but that's not the only NOTAM system involved. The US Coast Guard Navigation Center publishes NANU's. NANU sounds like something that Robin Williams said on Mork and Mindy, but in fact it is quite serious. NANU stands for Notice Advisory to Navstar (you remember Navstar, right?) Users, and this is where DUATS and Flight Service get their GPS NOTAMs. Here's the deal on SVN49:

!NOTICE ADVISORY TO NAVSTAR USERS (NANU) 2010068 NANU TYPE: GENERAL
*** GENERAL MESSAGE TO ALL GPS USERS ***
THE 50TH SPACE WING IN COOPERATION WITH THE GLOBAL POSITIONING SYSTEMS WING, WILL BE TESTING SVN49 (PRN01) SIGNAL CHARACTERIZATION OVER THE NEXT 6 MONTHS. SVN49 (PRN01) WILL REMAIN UNHEALTHY UNTIL FURTHER NOTICE, AND THE BROADCAST NAVIGATION MESSAGE WILL REMAIN IS-GPS-200 COMPLIANT. USERS CHOOSING TO TRACK AN UNHEALTHY SVN49 (PRN01) SHOULD CONTACT GPSOC (MILITARY) OR NAVCEN (CIVIL) IMMEDIATELY FOR ANY ISSUES THAT MAY BE ATTRIBUTED TO THESE ACTIVITIES.


How SVN49 got to be unhealthy for 15 months is a cautionary tale about engineering. The first thing to keep in mind about engineering is that at some point you have to freeze the design and start building: that's version 1. But even while you build version 1, you think of improvements, which eventually make their way into version 2. Etc.

One of the improvements to GPS is the addition of a third frequency, L5 (1176.45 MHz). This will give users improved correction for transmission errors, but the choice of this frequency is controversial.

In any event you have to test, so Lockheed-Martin engineers took a spare L5 transmitter and bolted it to a spare power bus on SVN49. Nobody has explained why a satellite has a spare bus, which is a lot more complex than having a spare USB port on your computer, but that is the case.

Now this was not a willy-nilly fly-by-night operation: I have no doubt that LMCO engineers did all of the requisite analysis, and that the proper drawings and other documentation were made. (It's very important to document every little detail of a satellite; imagine your embarrassment when the thing gets to orbit and doesn't work and you don't really know what you did when you built it.)

But despite this due diligence, the L5 signal interferes with the L1 and L2 signals, and the navigational data from the satellite is, so far, unusable.

Now there's more than one way to skin a cat, and lots of people are putting lots of work into figuring out how to make SVN49 useful. For the moment, though, it's still begging at the door, waiting to be let in. Let's hope that soon it will be PRNg.

Labels: , , ,

Sunday, December 20, 2009

Testing Yourself

The doctor gave me a definitive diagnosis: it's Rheumatoid Arthritis. He said that it looked to him like my body would respond well to treatment, and he was right: every week I am a little stronger, and with rare exceptions I don't need to take anything for pain.

The recovery has an eery nick-of-time precision. And it's a good thing, too. First came the snow; I was strong enough to handle it, barely. It felt good to be outside working.

Friday night, my wife and I were watching a DVRed episode of Law and Order, one with an exquisitely complex plot. She had a glass of wine, but I was settling for the contact high, having given up alcohol because I am taking too many drugs that are hard on the liver. This was an easy decision, especially for a moderate drinker, about as easy as "no more winter IFR over the Cascades in singles." But that's another story.

An odd background noise caught my attention. Not a helicopter, not a truck, maybe something from the rail yard? No. A neighbor doing something? No, not at 11pm.

I went down to the basement. Is it the water softener? No. The noise was coming from the furnace.

I got some tools and started poking around, and pretty quickly decided that it was the exhaust blower fan. I fooled around with it, but the disassembly was more than I felt like tackling at 1am, and, besides, I didn't have any spare parts, so what was the point? We shut the whole thing down. We shut the furnace down. The night's predicted low was 20F.

But we have a backup or two. This is one of my big lessons to my flying students (I had to get to flying somehow, right?). I remembered the time I was shooting the GPS approach into Jackson Hole, WY [KJAC], night IMC. At that time, the GPS approach was an overlay for the VOR/DME approach, and I had written in the company training manual that in such cases, workload permitting, the pilot should set up both. Which I had. When the RAIM failure came, all I had to do was punch one button tand keep flying.

My wife and I got down to work lighting the fireplaces and the wood stove. I had turned off the gas to the gas fireplace, and went down to the garage to turn it back on. When I came back, she had stacked some half-split logs on the back porch. "I'm not too good at splitting these," she said.

They were way too big for either the fireplace or the wood stove. So I went out to split some logs. Being a good Yankee, I kept saying, "Best thing about a wood fiyah is that it wahms you twice!" Which it did. While I was outside I made note of a broken gutter, which I fixed this afternoon. If I recover much more I might put on a new roof or something.

The furnace guy came out in the morning and confirmed my blower fan diagnosis. He disassembled it, and found three broken impeller blades. We tried to run it with the missing blades, but the wheel was too imbalanced. Kind of like United 232, but way less deadly.

"We don't carry this part," he said, "We'll have to order it." So I went out to split some more logs. Not bad, considering that 6 weeks ago I couldn't erase the blackboard.

But we had some luck; he found a blower fan, and came back to install it. The furnace is running nicely, everyone is warm, and the bill is in the mail.

Still, it would have been nicer to fix it by pushing one button...

Labels: , , ,

Thursday, July 16, 2009

Practicing What I Preach

It's time for the annual family trip to my sister-in-law's farm in South Dakota. It's 700 nautical miles, and we take the Club's Cherokee Six, which trues about 140 knots. The Six is not the most comfortable airplane I have flown, but it can take the four of us and full fuel with capacity to spare. Full fuel is 84 gallons, which is well over 5 hours' worth, but nobody's bladder can make it that long.

So do I practice what I preach?

  • Current charts? Kind of: I couldn't find all of the sectionals I needed at the local pilot shops, so I used a WAC chart for part of the flight, supplemented by current instrument enroute charts. WAC charts don't show airspace. I had current approach plates for any airport we were remotely likely to use.

  • Weight and balance? Yes. I made the family wait on the ramp while I figured this. "Can we load yet?"

  • Checklists? Yes. I had my daughter read them to me.

  • Flight plans filed and opened? Yes. By the way, I like the DUATS email notification when the flight plan is transmitted to FSS.

  • Flight following? Sort of. The Idaho portion of the trip is below radar coverage, so none was avaiable. I called Casper approach 30 miles out, so got some coverage then. But then we left Casper naked. I monitored Center frequencies, but that was mostly for entertainment. For example:

    Aircraft: Center, your transmissions are getting pretty weak!
    ZLC: I have multiple transmitters, and the other plane is hundreds of miles away. How's this one?
    Aircraft: Loud and clear. [stage whisper] Sorry!

    Or another:

    ZDV: United 123, there's an F-16 going to pass on your left, he's got 100 knots on you." In other words, the F-16 was 100 knots faster.

    Oh, they're shooting F-16s out of Ellsworth AFB! I called Center and got flight following.

  • Navigation logs? Yup, I had navigation logs (one form the AOPA Internet Flight Planner, and one from DUATS.



  • But I used my handheld GPS (old, no moving map) for the whole trip. This got me thinking: what would I have done if the visibility had been, say, 6 miles? There would be no comfort in spotting the Black Hills 50 NM ahead, and pilotage across Wyoming is a real test of map interpretation skills. Those "rivers" on the left are often dry, although this year's extra rain has made the riparian area green and thus more visible form the air than I can ever remember. There are few roads, fewer cities, and even fewer public-use airports.

    So I know the answer: navigation in 6 miles visibility is just too hard. I would file IFR, even though the trip would be longer.



    The municipal airport where we landed has a few hangars with ag planes and one open hangar with a recently-restored Super Cub. You can see the city from the field but it's actually a good walk. I wandered around for a while looking for cell phone coverage, finding none ("More bars in more places?????"), but closed our flight plan using the phone in the pilot's lounge. The lounge consists of a table and chair, a phone, and a bathroom. It smells of uncured concrete. The bathroom light is on a timer; twist it to get 10 minutes of light, which should be more than enough, right? There are a few aviation magazines on the table. You've got to love it.

    Labels: , ,

    Wednesday, February 11, 2009

    Something Old, Something New,...

    This week brought an unusual opportunity for me and a couple of my students. The flight school's 172 was due for its annual, and a different 172 appeared on our ramp. They had brought it over from a different location (they have three locations) to cover.

    And different it was, a 1975 model with the full 40 degrees of flaps that are manually controlled without any detents.

    "How do I get 10 degrees of flaps?" each asked. That was easy to answer. "Just count, One one hundred two one hundred three." They looked at me funny, but it worked every time.

    They also got to see that one cannot judge an airplane by its paint alone. We should have learned this from the Yarmouth Castle disaster. All that new paint made the ship look great, but helped fuel the devastating fire. This airplane flies quite nicely behind a solid mid-time engine, but the paint is about a 4 on a scale of 10.

    Better yet, they got to play with an IFR capable GPS. As one might expect, the database was grossly out-of-date, so we could not use it to fly IFR, but they were able to see that one can load a route into the GPS and watch it guide them along the route. They also got to see the track display (notice in the picture that the desired track is not straight up, so we were flying to the right). And, I got to give myself an indirect refresher on loading an approach from the database. My last logged RNAV approach was a year ago, and although I could not log this one I still got to experience it; better yet, I did this by talking Dan and Dennis through pulling the approach out of the database, putting it into the flight plan, and following the route. This was a lot for them to chew on, and all I could do was introduce some of the concepts. The airplane will go back to its real base tonight, and "our" 172 has no GPS. Nor is it likely to get one soon.

    It was interesting to work with them, because they do not have years of habits to unlearn. The big deal with GPS isn't the ability to know your position. The big deal is the database, and the unit's ability to sequence along a route. I told them both by common sense and the Aeronautical Information Manual, that they needed to load a complete route before launching, In the past, a lot of pilots had scoffed, saying "I've been flying IFR for years and never needed to load a whole route, so why should I do it now?"


    The winter scenery was an added bonus. The reservoir near our practice area is still covered with ice. The ice gets rough as the winter goes on, with lots of leads and pressure ridges. But today there was a dusting of snow in the morning, just an inch or two, making the surface smooth and uniform. The scattered clouds above us made shadows that danced along the snow. The air was smooth, making it easy to feel the more pronounced stall buffet. I had them try to climb with full flaps, and of course it wouldn't, an important lesson.

    They found their way back to the airport using the GPS, and did good landings in this new (to them) machine.Both had struggled and worked hard to master the new environment, but in an enjoyable way. What more can an instructor ask for?

    Labels: , ,

    Friday, September 26, 2008

    GPS & RAIM

    It's common sense: make sure that your navigation equipment works before you fly. There are a few cases where this doesn't matter, like when you are flying locally using pilotage alone, but certainly if you are going to be flying at night, in the clouds, or over large bodies of water you want to know that the black boxes are telling you the right thing.

    This is an old lesson. World War I ace and head of Eastern Air Lines Eddie Rickenbacker learned it the hard way, in 1942. This story comes from Seven Came Through, published by Doubleday in 1943.

    It was the height of World War II, and Rickenbacker was on a secret mission to inspect all air combat groups. After a fact-finding tour of the European theatre, he headed to Hawai'i to begin inspection of the Pacific. His first destination was "1800 miles southwest" of Hawai'i; it was still wartime when the book was published, and Rickenbacker was a little coy about the destination. My best guess for the destination is Howland Island, which is famous because another prominent aviatrix, Amelia Earhart, never made it there, either.

    The Army Air Corps assigned a B-17 and a crew to the flight, and they left Hickam Field in Honolulu on October 21, 1942. The departure didn't go well; a brake problem on the right main caused a groundloop.

    Nobody was hurt, so the Army dug up another airplane and they launched again, crossing the ocean using dead reckoning and an octant. An octant works like a sextant, but uses one-eighth of a circle rather than one-sixth. The problem with dead reckoning over the ocean is that you can't determine drift or groundspeed, so you depend on the accuracy of the winds aloft forecast. We all know how that goes. But the octant and navigator were there for backup.

    The octant had been loose on the navigation table aft of the cockpit during the groundloop, and had fallen. Damage from the fall made it inaccurate. With no way to find the destination island (whose direction finding equipment wasn't working), the B-17 eventually ditched. All eight made it into the rafts, but one crewmember died before they were rescued. Twenty one days later.




    Only a few luddites use celestial navigation in airplanes anymore. I've tried, but every time I go up the hill and take sights I end up knocking on my neighbor's door and asking when did you move to Montana? Where is the lesson for us?

    In the USA, the Federal Aviation Regulations (14CFR) require regular checks of pitot-static (14CFR91.411) and VOR navigation systems (14CFR91.171). The magnetic compass should be checked with each annual inspection. We all know people who don't do the checks, and I can't tell you with a straight face that skipping a VOR check will make you spend 21 days in a raft.

    Besides, I hear people say, nobody uses that stuff anyway. Now it's GPS, GPS, and when that fails GPS. How do you check the GPS?

    First, let's get this out of the way: GPS can fail. Satellites have broken down. The military test jamming equipment. Incorrect almanacs have probably been uploaded. Ionospheric storms hit with shocking regularity and little or no warning. Antenna connections break. Voltage spikes fry avionics. Batteries leak in handhelds. The system is guaranteed to be 99.999% ("five nines") reliable, but there are 100,000 North Atlantic crossings every year, so statistically one of them will have GPS failure.




    What do we do about GPS failure?

    The big expensive answer is WAAS, which I will leave to a future blog entry.

    The simplest answer is that we cross check against other systems, usually pilotage and VOR/DME. (When I flew turboprops I carried WAC charts, partially for sightseeing and partially "just in case.")

    The newest answer is you are required to check GPS integrity before every flight using RNAV (DPs, STARs, Q- and T-routes). This is called a RAIM check (Receiver Autonomous Integrity Monitoring). It requires at least five satellites (and barometric altimeter input). See this post for an explanation.

    The requirement has always been there, but it was scattered through a lot of supplemental documents like TSOs and operating manuals. Now the FAA has clarified the requirement, in a new issue of Advisory Circular 90-100. They have even given you a website to help you do it. If worse comes to worse, you can get the information from Flight Service.

    Even if it's not required for your operation, it sounds like a good idea.




    Modesty aside, I feel strongly enough about the study of the art of navigation that I wrote a book: Understanding Mathematics for Aircraft Navigation. Some people say that it contains more than pilots need to know. I've already said how I feel about that...

    Labels: , , , , , ,

    Wednesday, June 4, 2008

    Old-fashioned IFR

    Here it is, a nice IFR panel from the 1990s.  Two VORs (ignore them; I was being radar vectored when the picture was taken), ADF, DME.  No database, MFD, HSI, RMI, GPS, RNP, WAAS, SAAAR, or even useful autopilot.  The only problem is that this wasn't 1990, it was 2008.  Yesterday, in fact.

    I said that I was reluctant to file IFR in this airplane, not because it was unsafe or even unwise, but because there are so many services in the current IFR system that it cannot use.  I was forced to file a circuitous route.  I wasn't sure of the legality of the route, since the nearest navaid to our departure airport was more than 50 miles away, so I would be starting well outside of its service volume.  There is an intersection close to the direct route, but I had no easy way to go direct.

    Actually, I could have found the intersection using a sequence of cross fixes; been there, done that.  It's pretty simple when you have a VOR beside the desired course.  You draw the "direct" line on the map, then measure the DME distance where this line crosses various radials from the VOR to your left.  If you are 33 DME along the radial when the course is 35 DME, then you are to the left, so you adjust your heading to the right and try again in a couple of miles.  You can back this up with a handheld GPS, but mine is so old that it still has gears and belts, so the intersection wasn't in the database.  I could have defined the intersection as the crossing point of two radials, or by radial/DME, but I was not willing to file this way. 

    Like I said, I have done this, in IMC, but with a good autopilot to hold heading.  It's just too much work.

    So, I filed for the VOR way out of my way to the left.  We started up and taxied to the one spot on the ramp with cell phone reception, and I called Lockheed-Martin's Clearance Delivery line (888-766-8267).  The call got dropped the first time, but the second time I spoke to a person who told me that I was "cleared as filed."   There was no void time.  I asked again to make sure.  There was no void time.  We really were in the middle of nowhere.

    Right away we were IMC.  It took a while to contact center, who immediately gave us a radar vector direct to our destination, so all I had to do was hold heading and altitude for the rest of the afternoon.  As we moved east we were in and out of the tops, but it was smooth and there was no ice.  As usual, there was a King Air passing overhead (there's always a King Air passing overhead when I fly). Center cleared them to 8000 (we were at 7000), but we never saw them, and they were unloaded and tied down by the time we landed.

    So what was the problem?  Our real destination, where fuel was a dollar a gallon cheaper, only has a GPS approach, so we had to go to the "big" airport (radar coverage, but not Class C) where there is a long taxi and expensive fuel.  So, again, the lack of modern avionics wasn't unsafe; it was inconvenient and inefficient.  

    Still, it beats scud running.

    Labels: , ,

    Sunday, June 1, 2008

    Instrument Departures

    The IFR world is always changing, and change comes faster and faster.  

    In the old days, there were two main sources of instrument charts in the USA, the government (under a continually changing variety of names) and  Jeppesen, a commercial provider.  I still use Jeppesen charts for most of my flying, but now government charts, which are public domain, are widely available on the internet, through sites like AOPA, FltPlan.com, Airnav, and probably others. For this trip, I have downloaded government charts for the airports I am likely to use, although I am unlikely to fly IFR.

    Let me say it out loud: I am unlikely to fly IFR because the airplane does not have an IFR GPS.  Yes, I can and may fly IFR, but the lack of a GPS makes it much more difficult, and it reduces the options.

    This was reinforced while catching up on my chart revisions.  (Actually, I was getting ahead, since some of the charts are not valid until Thursday, but I determined that none of them will affect my flying between now and then.)  One of the advantages of the Jeppesen charts is that they tell you why the chart has changed.   Lately, there have been a lot of changes to departure procedures.

    Departure procedures are strange to begin with.  Generally, they are optional.    They are not optional when Air Traffic Control (ATC) includes the departure procedure in a clearance, which they will do if they need it for separation.  This tells me that when a departure procedure changes, ATC would like to use the new one in order to move more airplanes more efficiently.  Why change a procedure that has worked for 20 years unless you want to actually use the new procedure?  (It used to be that the exact statement about departure procedure being pilot's choice was only published in the controller's handbook, not in any publication for pilots, but now it is in the FAA's Instrument Procedures Handbook, FAA-H-8261, available online.)

    Look first at Driggs, Idaho.  (Unless you have a Jeppesen subscription you'll have to wait until Thursday to look, because charts are not available online until they become effective.)  The chart had a minor change this time around, but in looking it over I noticed that there is no non-GPS departure.  There are no ground-based navaids at Driggs, which is in a narrow U-shaped valley, so the only alternative to a GPS-based departure is to pick a smart heading, climb steeply,  and hope that the winds aloft forecast is correct.  There is no radar coverage, so nobody looks over your shoulder.  No thank you.

    The Cherokee Six we're in this week has DME but no GPS. Suppose that we decide to stop for lunch at Driggs on the way home (the restaurant there is excellent), and find that we need to depart IFR. No can do! This alone wouldn't keep us from stopping, but it still makes me pause.

    Next, look at Pocatello, Idaho, which has a new departure procedure, even though the old one had worked well keeping airplanes out of the rocks for at least 15 years.  The new procedure involves a "departure gate" at SICOY; in other words, every departure ends up about 13 miles west of the airport, even for an easterly flight.  Also, you need DME (or some equivalent) to identify SICOY, so many KPIH-based airplanes cannot fly the procedure.  You can see SICOY on the VOR 3 chart at right.


    I think a lot of Pocatello-based pilots will react to the change by saying "ATC seldom clears us via the departure procedure." But this is may be about to change.  Pocatello is generally below radar coverage, so ATC keeps airplanes apart procedurally.  The old departure procedure used the same airspace as the ILS missed approach, which meant that no airplane could depart while another was on the approach.  Now, ATC can send the departure to SICOY and be sure that the missed approach area is clear.  In other words, it will be easier to get out of Pocatello, as long as you have DME.

    If you keep or rent an airplane in Pocatello, you have to ask whether departure delays will cost enough to justify an avionics upgrade.

    Labels: , , , , ,

    Monday, April 21, 2008

    So many electrons, so little time


    A local turboprop operator called me because they were short a pilot.  Their trip to the coast fit my schedule, so I took it.  Get paid to fly a nice airplane to a nice destination with a nice guy?  Sure.

    Their airplane has a mixed avionics suite that includes steam gauges all around, an older IFR GPS, but a modern KMD-850 Multi Function Display (MFD) that includes terrain, traffic, weather, and moving map functions.  I have flown this kind of MFD before, and I have to admit that it took me a few flights with it before I became comfortable with it. 

    [The photo here is from _Night_Flyer's_ flickr collection, and I believe that it is legal.]

    I was a little surprised at how little their pilot knew about the system.  Remember, I just got handed my lunch by the Garmin G1000 system a few weeks ago, so I am pretty sympathetic.  All of these avionics systems have little goodies and quirks, and we have all read over and over again how important it is get to know the avionics before you fly.  The thing is, something like a G1000 hits you upside the head to warn you that it is different, while little incremental changes (add a function here, a few months later add a function there) that leave so much unchanged make it easier not to see that something more is needed.  I think that this pilot had been lulled by the familiarity of everything else in the cockpit.


    Here's a picture of another airplane of the same type, but with EFIS.  The EFIS is obviously different, so it's obvious you need to learn how to use it.  This particular airplane doesn't have an MFD, though.

    So what can the MFD do?  My favorite function is the terrain function, although it must be used with caution.  Its position depends on GPS position (not some internal position, as my friend thought), and any error in GPS position leads to an error in the display.  It is also subject to abuse.  I wrote an article for comp.risks about this in 1998 which you can probably find by searching for EGPWS; I also wrote a letter to the editor of Aviation Week that appeared around the same time.

    Despite the problems, I appreciate having a terrain display during departure and arrival, and it has been my routine to put the MFD into terrain mode before takeoff and during the descent.  

    The radar in this airplane is nice, too.  In radar mode, one of the soft buttons on the right says "VIEW", and pressing it gives you a vertical profile in one direction.  If there is a thunderstorm, you can see just how far above you or below you it goes.  We used this during one of those "Are we going to be above that?" cockpit discussions.  He had never seen it before.

    You can also use the radar to show traffic.  This takes a little knob twisting and button pushing, but most weather radars can do it.  You need to put the gain up as high as it will go (in this unit, the weather mode has automatic gain, so you have to go into map mode), and set the range to 20 miles or less.  You need to play with the tilt a little, too.  But try it when Center calls traffic 12 o'clock, 1000' above, opposite direction.  You'll see a smudge that gets closer with each sweep of the antenna.

    Traffic mode will show you a little icon of a nearby airplane with its relative altitude and derived track.  Switching back and forth between this and the radar will convince you that the radar really saw the traffic.  Since the traffic functions depends on the secondary reply to ATC's radar, you really have two radars showing the same thing, which is quite comforting.

    To me, the moving map mode is the least useful.  Some units allow you to superimpose the moving map onto the radar picture, like below, but the MFD we were flying that day with won't do it because the airplane's GPS isn't sophisticated enough.  (The picture was taken a few months ago in the bumps, as you can see.   There are multiple course lines because I was using the FMS offset function to go between the cells.) 







    The map is nice to show the passengers just how far away New York is, or to give a more intelligent answer than "White Pigeon" to the "What town is that?" question, but the useful moving map is on the GPS.  The MFD just duplicates the GPS map, anyway, so it provides no new information.  Plus, it's easy to make the map so cluttered that it is useless, by displaying every VOR, NDB, intersection, airport, MOA, restricted area, alert area, class D, class C, class B, and airway.  

    I like Jackson Pollack's paintings, but not in the cockpit.





    Labels: , , , ,