This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

Saturday, March 13, 2010

Rush to Comply


Ok, before I begin I must admit that JFK is not common ground for me…I pass through every now and then, more often as a last minute divert from LGA or EWR than a planned destination. I possess a mental short list of airports that I avoid for one reason or another and JFK makes the list for a number of reasons. I was flying a “turn” this day…one leg out, one leg back, home at night. Not a bad deal if, like me, you savor the company of your wife and kids and are lucky and or wise enough to live where you are based. Our arrival, landing and taxi-in were unusually routine for New York. Beautiful winter day. No delays. Landed 31R. Short and simple taxi clearance to an open gate…arrived about 20 minutes early. Uneventful…just the way I like it. Getting the heck outa Dodge wouldn’t be so easy.

The 100+ knot headwind that yielded our early arrival would be a thorn in our side on the way home, so we made every effort to get underway on-time if not a little early. In spite of what the Captain may tell you when running late, it’s quite difficult to make up any measurable time en-route. That extra speed at altitude on a flight like this would cost the company at least another 1000lbs of fuel and would result in about 5 minutes saved…not a great return on investment. The best way to hedge our bet against the headwind was to get off the gate early and hope for a short taxi.

I can’t speak for the ramp crew, but for whatever reason they didn’t start paying any visible attention to us until about 20 minutes before departure. This would not suffice for our fully loaded flight home. We would leave the gate a little late. Strike one.

We finally requested push clearance about 10 minutes past departure, but the flight at the next gate beat us to the punch. We would have to wait for him to push, start and taxi out from behind us before we could move. Strike two…and here comes the fun part.

With pencil in hand, I requested taxi clearance from ever-patient JFK ground (yes, I’m being facetious). We got off to a good start with a clearance to taxi via Tengo and Alpha. “Follow the jet ahead to runway 22R” he told us. Great. Follow him…we can do that. We were turning onto Alpha when we got our first amendment. “Hold short Victor” he said, “I have a runway change for you. Standby.” So we pulled up and held short of taxiway Victor, hoping for something simple. Our new instructions were to taxi to runway 31L via Bravo. I read this back before looking at my chart and realizing that we could go left or right on Bravo and reach runway 31L. In hind sight, turning left seems more logical, but I still didn’t know for sure and needed clarification. But this is JFK ground and getting a word in is often more difficult than it sounds. So we sat there, not know which way to turn, until we were in someone’s way, got noticed by ground control and were finally asked what we were doing. Questions like “what are you doing,” “where are you going,“ and “say your altitude” are not favorites of any flight crew as they usually infer an error on your part. To add to my discomfort, the tone in the controller’s voice was not one of a nurturing parent, but one of a weathered schoolmarm. We were indignantly instructed to turn left and contact clearance for a re-route. Strike three.

We received a new full-route clearance comprised of numerous navigational points and airways with which I was not familiar. Jet this, victor that, intersections and VORs…it wasn’t pretty. I’m sure my read-back sounded something like a student pilot's first attempt at an IFR clearance, but I muddled through it with a bit of assistance and managed to get it all down on paper. Getting the new route into the FMS wasn’t any easier. Each fix and airway along our route had to be verified on a map before being entered in to the FMS. Just locating an unfamiliar fix in this part of the country is a chore. An airway map of the northeast looks a little like a plate of spaghetti. Everything is compressed and jumbled together, so finding unfamiliar points is a time consuming task...and the pressure of the clock was beginning to have its toll as we approached the departure runway. We pulled out of line to give ourselves some extra time, verified the new route and successfully entered it into the FMS. We then contacted dispatch to verify legal compliance and viability of our new clearance and left New York on our way home. Crawled into bed a little late that night.

Time seems to compress when you are feeling rushed, but the key to a safe flight is not allowing yourself to be pushed into what is know as a “rush to comply.” Pilots are proud beings...and an inability to comply with a clearance in what is perceived as a timely manner is an attack on that pride. We must resist the temptation to rush. There has never been an accident or incident that was not made up of many links in a chain. Allowing yourself to be rushed may be the quickest ways to add links to your flights chain of events. Breaking any one link could very possibly prevent a tragedy. On a good day, only checklists are completed between the gate and the runway. On this day, we had much more to do, but we took each step as it came and completed it in a safe and timely manner.

Forgive me while I paraphrase…A pilot lives in a world of perfection, or not at all. Not sure who said it, but I like it.

Sunday, March 7, 2010

Cat III approach


Just prior to a late night departure for a short, 30 minute flight to our scheduled layover, the weather at our destination was good but not great. It's usually the visibility, not the ceiling, that is the limiting factor with respect to legally beginning an approach. At our destination that night, the visibility was 2 1/2 statue miles and forecasted to stay that way. It was my leg and I, the first officer and a guy who doesn't like to give up a landing for any reason, am not allowed to land the airplane if the visibility is less than a mile. I've never been crazy about this rule, but its intent is to put the aircraft in the hands of the most experienced pilot while flying in the most challenging conditions.

Our flight that night progressed normally, climbing through a thin, stratiform cloud layer that streamed through the landing lights like soft white ribbon revealing a beautiful star filled sky and full moon above. The air was stable and smooth...I could hear the flight attendants beginning their duties as we retracted the last of the flaps and slats. In less than 10 minutes we were cruising at 23,000 ft, completing cruise checklist items, planning our descent and retrieving destination weather. The automated weather system reported visibility of 2 1/2 miles, conditions that were confirmed by the approach controller at first contact. Ten miles later and a mere 20 miles to the airport, the conditions began to change. 20 miles may seem like a lot, but we were still clipping along at 250 kts and would quickly gobble up 20 miles.

With 20 miles to touchdown, we were informed that the visibility on runway 17R, our intended runway, had just fallen to one mile and the visibility on runway 17L was now at 1/2. We had some quick decisions to make. We were set up for an approach to runway 17R. If the weather remained unchanged we could safely and legally continue and I could execute the approach and land, but the lowest visibility to legally fly the approach was 3/4 of a mile. Runway 17L on the other hand, was equipped with a special approach that would allow us to land with a visibility of 600 RVR. (Runway Visual Range). Since the visibility was so different on two runways in such close proximity, we decided to change to runway 17L and fly what is known as a CAT III, autoland approach. This approach is flown all the way through touchdown and to a complete stop on the runway by the autopilot and takes special consideration and planning. Given our distance to the runway, we elected to go-around and give ourselves some extra time to set up the approach.

By the time the controller vectored us around for the approach to runway 17L, the weather on both runways was reported to be 1/4 and falling. Of course, since the vis was below one mile, I had to relinquish control of the jet and my precious landing to the Captain. As we continued the approach and intercepted the glide slope, we each began our required call outs and completed the landing checklist. At 500 ft, I reported "on speed, sink 700" and noticed that the cloud tops were still glowing in the moonlight in my peripheral vision. My call outs continued at 300 ft. as I heard the tower controller announce 17L visibility at 600 RVR..."300" "200"...still above the cloud tops..."100"...finally in the clouds...at 50 feet I reported "minimums" just as the Captain stated "landing" and the autopilot continued the approach as the aircraft announced "50" "40" "30" "20" "10" followed by the best autoland I've ever witnessed. Very nice.

We crawled to the gate that night. The visibility was so poor that we couldn't see the terminal from the center line on the ramp. The ground crew had to walk out to the aircraft to guide us onto the lead in line. It's been a strange winter this year. Low visibility approaches like this one are rare in the U.S. In the last 10 years I have only flown 6 approaches that required an autopilot flown approach and landing. 3 of those were in February 2010.

First Post

I have been encouraged by friends and followers on twitter (www.twitter.com/AAFO4Ever) and YouTube (www.youtube.com/contrail777) to start a blog...so here it goes. My posts may wander a bit at first until I find my voice in this forum, but will always center on my thoughts and experiences as a pilot for a major US airline. Thanks for reading along.