Monday, May 31, 2010

Piling on the Pres

Starting out writing this, I’m commuting home from a four day trip, both sides un-commutable. Yesterday started relatively early, with a 6:30 AM van ride to the airport in Newberg, New York, near West Point US Army Officer Academy, where President Obama spoke Saturday before we arrived. There were no signs left from the Secret Service personnel, of whom the van driver said had been staying in the hotel all week, and I had a good and needed rest for our long day of Sunday flying.

With a friendly Co-Pilot and Flight Attendant, we made our way through almost eight hours of flying, which entailed six flights and twelve hours to perform it in. Newberg-Philadelphia-Louisville-Philadelphia-Washington-Rochester-Washington was on the agenda, but a low pressure weather system and the forecast east winds and relatively low cloud ceiling in Philly promised to slow us down. My First Officer had plans to meet his wife in Milwaukee, to spend the night there before heading to Charlotte the next morning. With the delays in Philadelphia we were expecting, it was questionable whether he could catch the last flights from Washington to Philadelphia. He commutes from Green Bay, Wisconsin, and is a fellow brother in Christ. We had a good conversation about some of the particulars of Protestant Christian theology, and enjoyed flying together.

Our first two flights arrived in Philly and “Loua-Vule” on time. Now we just had to go through Philadelphia one more time, and we wouldn’t expect any delays in and out of Washington. In Philadelphia, when the winds are from the east, the airport runway layout can’t accept the same amount of departure and arrival traffic as it would normally. This can create major ATC delays, especially for traffic inbound to Philadelphia. Our scheduled departure time out of Louisville was 11:35 AM, and Louisville clearance delivery had given us a ‘wheels up’ takeoff time of 1:01 PM. We had time to hang out some, eat lunch, and talk about our commuting plans. I couldn’t make it home even if we arrived in DC on time, our Flight Attendant, a new one but a good one (she had flown for a regional based in Atlanta previously) could still make her commute flight even if we were a couple hours late, and my Co-Pilot was scheming and trying to figure out a plan to catch his last flight available in record time. It seemed we would arrive in DC at about 7:30 PM, and that’s when the last flight to Milwaukee was.

We pushed back without three missing passengers in Louisville, in order to meet the 1:00 PM takeoff time. Just then, ATC surprised us with a new delay, a 2:05 PM takeoff time. No! We had a couple options: taxi out and hope for a shortened delay, or wait to see if our three missing passengers would make it back to the gate. We could board them on our plane, taxi out, and still make the new 2:05 PM takeoff slot. In the interest of providing good customer service (this is a customer service business, despite what some of my Co-Pilot’s seem to feel), we started our engines and taxied the thirty yards back to the gate to board our three lost passengers. In actuality, we lost one passenger, who had said ‘enough’ and got off our jet to travel another day, and we put on four, for a gain of three and a ‘full boat’ back to Philly. The ‘circus music’ had started playing, because whenever a plane returns to the gate, one-third of our pax ask the Flight Attendant the litany of ‘will I still make my connection?’ type questions, and they were doing it now. Dealing with those issues is the Gate Agent’s job, and it’s a tough one in this situation. They generally make an announcement in the cabin (I asked her to this time) that ‘NOW is the time to leave the flight if you want to, that this aircraft will leave the gate again and not come back.’

We got our new passengers on board and just as we were closing up, ATC notified us that the ground delay program had been canceled, along with our 2:05 PM takeoff delay. We were released to Philly, and in quick order we taxied and took off. As we broke ground I wondered if that passenger we lost saw us climbing out into the blue Louisville sky.

Fast forward four days later: I’m commuting again back to work, trying to go through Chicago.  Before my first of two flights to get me to Washington, Chicago had a ground stop issued by ATC for “VIP movement” (President Obama). My Sioux Falls-Chicago flight was now delayed till 7:15 PM instead of 6:30 PM, and with a scheduled 45 minute connection to Washington on a normal day, I knew I'd be running for it. And I literally was, after seeing on the departure monitor that my flight was delayed by five minutes, and that many others were as well. "Can't you do something, Mr. Obama, without displeasing someone?"

I caught my breath in my window seat and our Airbus taxied out for Washington National.  Leaving Chicago, I’m transfixed by what I see. We’ve turned to the east just after breaking ground in smooth air, and the vast, expansive grid of greater Chicago spreads out in the window in that appealing orange halogen color the street lights have. Miles and miles of it are broken up occasionally by the stray winding expressway with white and red lit drivers making their way to where they’re going. The famous Chicago skyline is now ahead and to the right, with the (former) Sears Tower and the Hancock Tower framing the ends of it. Oddly, downtown and Lake Michigan seems to be backlight tonight. After closer observation and some scuddy clouds clear out of the way, it can plainly be seen that a full moon is out tonight, shining it’s white, reflected light on the calm, black surface of Lake Michigan. It casts a white, milky beam across the water, seemingly all the way to Indiana and the Notre Dame ‘capital’ at South Bend.

I am reminded that scenes like this one, which I first enjoyed while flying standby as a passenger on American Airlines as a kid, really make an impact on me. I really enjoy the beauty the skies can have, I guess you could say my eyes behold it. With the distractions and stresses of life, it’s can be easy to overlook the beautiful things, whether it’s in the sky or in your personal or family life. As the sky goes, maybe I’ve been doing some overlooking lately. But it is now thunderstorm season, and I know there will be plenty to appreciate soon! (And to be wary of)

Speaking of which, it’s a convenient time to transition back to the previous trip's Louisville departure to Philadelphia. Soon we’re climbing to our cruising altitude of 29,000 feet (“Flight Level two niner zero”). In blue sky and sunshine, my First Officer turns on the radar, and increases the range to 80 miles, then 160 miles. The tilt is low and the gain is turned up, but the screen barely shows any green returns, and that’s probably from the ground. The white, wispy clouds ahead, with a few curved, more solid looking bumps bulging slightly above them, indicate that we’ll probably have to do some deviating from our course line ahead, in spite of the clean radar returns.

We’re just not close enough to it yet; when we get within about 40-60 miles some good returns start showing up, the worst color they show is yellow. The view out the windscreen compels us to ask ATC for deviations, even if the radar was blank. The cumulonimbus tops are only two to three thousand feet above us, it looks like, but in reality they are probably four to six thousand feet higher. The tops look relatively flat, for thunderstorms, but looks can be deceptive. I see a bolt out into the burning blue sky out of one of them in front of us, confirming that these puppies can still bite. By this time I’ve been trying to ask center for a heading of 15, now 20 degrees left to avoid this buildup in front of us. The center controller I’ve been trying to check in with has been busy handling other airline traffic, and now we’re 15 miles closer to this storm than when we started calling. Another 30 seconds to a minute of this and my FO and I agree that we’re turning left, no matter what.

We could make it through it OK, but it would be constant moderate turbulence at the least, possibly severe occasionally, with icing in the tops of the cumulus formations, and a chance of lightning and wind shear with the turbulence. Not good for the pax or the Flight Attendant, and definitely not good customer service. The controller finally responds and serves us with an approval to “deviate left as required, direct Gordonsville (GVE) when able”.

Overall, it’s a good primer for the now-here thunderstorm season. A broad layer of wispy clouds stretches from left to right. As my Co-Pilot has the autopilot finish the turn to make our first of several heading deviations for buildups, we confer with each other, and agree that our course to the left, mostly in the clear, is better than to the right of the cumulonimbus. On the radar, another yellow spot, the biggest one, is now plainly seen; if we had deviated to the right we would have less room to deal with this cell than if we had turned left. Looking out the window, this largest storm cloud is mostly obscured by this thin layer of clouds previously mentioned. If we were a thousand feet lower, this situation would meet the classic definition of an embedded thunderstorm; the wispy clouds leftover from previous buildups wouldn‘t let us visually see the danger ahead! We later fly through some of these wispy areas, they are generally fairly smooth, with occasional light chop and nothing else.

We made it through the rest fairly unscathed day after arriving in Philadelphia.  Philly to Washington to Rochester to Washington went off without a hitch, minus our standard wait for ramp agents to park our jet in DC, both times.  However, we didn't make up enough time to improve my FO's chances of going to Milwaukee.

With my FO a little dejected, I was walking with him to the crew room when he spied the departure monitor board, and saw that he might have one last chance to make it to Milwaukee, via an American Eagle flight from Washington to Chicago, then the last United Express flight of the night to Milwaukee. He would be running for it, but we both thought he just might make it. He ran off to the gate, just like I would in the future tonight, but I don’t know if he made it or not. If President Obama didn’t get in his way, he was probably fine! I took his flight bag back to the crew room and then myself to Chipotle for a good, needed dose of burrito. I made it home the next morning, starting this post on the way.
 
I'm giving our President Obama a little bit of a hard time.  But I'm just poking fun at everyone else who seems to be.  Lately he's been taking flak from all sides, not just Republicans.  I think his current troubles are more politically partisan based and stem from a lack of PR control rather than lack of performance.  It's true that far left liberals haven't gotten what they've wanted from Obama, but neither have right wing conservatives.  Is not preventing the Deepwater Horizon oil disaster and spill, and performing an inadaquate leak stoppage and cleanup, really his fault?  No, the Deepwater Horizon disaster is not Obama's 'Katrina'. 
 
Excuse me for getting too political, perhaps.  I just feel that we should have a minimum amount of respect for our political leaders, no matter how much we disagree with them.  We should pray for them, it's in the Bible too: "I urge, then, first of all, that requests, prayers, intercession and thanksgiving be made for everyone— for kings and all those in authority, that we may live peaceful and quiet lives in all godliness and holiness. This is good, and pleases God our Savior, who wants all men to be saved and to come to a knowledge of the truth." (I Timothy 2:1-4).
 
And the Bible teaches that we should pay our appropriate taxes to the government: : "Render, therefore, unto Caesar the things which are Caesar's; and unto God, the things that are God's" are Jesus' words from Matthew 22:21.
 
That's it for now.  Thanks for reading my blog.

Thursday, May 20, 2010

Wet laptops & reflective thoughts

(This post was originally started about nine days ago)


I just finished a five day sequence and am flying home on United in economy plus, fighting the urge to take a nap. I’m pleased because my new laptop isn’t dead after all. Last night in Syracuse, New York, I was trying to finish my schedule bid for June, talking to my Mother on the phone (Mother’s day you know) when I accidentally splashed water on this keyboard I’m typing on. Doh!

I dried it off immediately with towels but there were droplets in between the keys. Not thinking, and especially not googling, I dried the keyboard further using the hotel hair drier and my breath to blow the droplets away from the keyboard.

It worked, for a while. Soon the number 8 key starting ghosting and repeating, and after a lengthy, second hair drying, the 0 key did too, and many keys didn’t work at all. Panicked and anxious, I finished my schedule bid on the hotel computer, worried that I had ruined my laptop by blowing the water drops into the keys and driving moisture into the keyboard using the hair dryer.

After bidding, ‘google’ said in one entry to never use a hair dryer to dry off your keyboard, as it will drive moisture further into it, and the heat and static can cause electrical problems with a laptop as well. But there were many other sites which mistakenly, in my opinion, suggested using a hair drier. The advice I now trust after a liquid spill on a laptop is not to use a hair drier, but to turn your laptop off immediately, dry it off with towels, turn it upside down to let liquid drain, and put it in the sun or warm, dry air for a while, remove the battery, and leave it off for 24 hours. I removed the battery, let it air dry overnight, then put it out in the sun during all five of our flights today (with it off, lest you‘re thinking about that NW crew). The air is pretty dry in an airliner, and the sunlight coming through the flight deck windows can bring in a fair amount of warmth. That combination draws the moisture out of a laptop fairly well, because after finishing scheduled day of six hours of flying, it works again, and every key is fine.

We had a ‘nice’ 4:45 AM show time at the airport, so considering I had this secondary problem to contend with, in addition to the one of getting a good amount and good quality of rest, I slept for five hours relatively soundly. Giving your worries up to God in prayer does help, and I did the best I could doing that before lights out last night.

I am tired with a capital T at the end of this five day sequence of flying. Today we flew from Syracuse to Philadelphia to Detroit to Washington to Norfolk to Washington, and were on duty for nine hours and fifty minutes, from 4:45 AM till 2:35 PM. This was the fourth early showtime I’ve had this sequence, and the second one at 4:45 AM in a row. And the best part of it is it’s all legal per the FAA’s rest rules and our labor contract. But is it safe?  It could be even safter.

I don't want to scare you, but this is the reality that many flight crews face.  However, it's much easier on pilots than in the early air-mail and airline days, when airplanes were unreliable, the navigation technology and avionics were crude, weather forecasting was more like weather guessing, the working rules were scarce, and the accident record was reflected in all these shortcomings.  It is relatively safe, in that there are two pilots (better than one), our aircraft is highly automated (hand flying five legs would be exhausting), and our work is highly standardized and routine.  The US does have the safest transportation system in the world.

On another note, I haven’t posted for a while, and don’t have a concise and readily available reason as to why. I have a couple ideas I’m working on, and a new phone which will enable me to do better and more frequent twitter (I’m “crossky” on twitter) updates, with pictures, on the fly, so to speak (literally). Technology and social networking, a’la ‘community’ is a subject I’ve been pondering. Because of social networking, the way we have community with each other in this era is changing, and sometimes I wonder if it’s for the better or not. I’m still trying to correlate it to flying somehow, but it will come.

Community with God, and better community with each other, is one of the main reasons the Son of God came to earth in human form. I’m not the best at fostering and keeping community with others in a loving Christian manner (as Christ teaches), but I kind of think that concern has been on my heart and mind lately. There are other signs I’ve seen that God is still working in my life, and when I get to a quiet place to reflect on that, it feels good. God is good, all the time! All the time, God is good! Thanks again for reading the blog.

Sunday, April 18, 2010

Gut Check

He is risen, He is risen indeed! I say it to others and others say it to me. In my past life, in the next few days and weeks after Easter I typically would slowly revert to living like I did before, only feeling the literal meaning of Jesus’ resurrection every so often, instead of every glorious day. I wish we could celebrate our Lord’s resurrection every week. Wait a minute, we do: Sunday is the day of the Lord, the risen Lord. Christians (except for Seventh Day Adventists) observe the Sabbath day as Sunday instead of Saturday, honoring the fact that Jesus rose from the dead on a Sunday morning, after the Jewish Sabbath (Friday night to Saturday night). Realizing that I’m still human helps me to understand how rediscovering ‘the joy of my salvation’ keeps it fresh in my heart.

Luke, a gentile (non-Jewish person) and physician, and close friend of the apostle Paul, wrote the gospel of Luke and the sequel to it, the book of Acts, during A.D. 61-64. Acts picks up where the gospels left off, and documents the rapid growth and events of the early Christian church after the resurrected Jesus Christ, in bodily and glorified form, appeared to many disciples and followers.

What occurs in the book of Acts is exactly what one would expect from resurrection witnesses empowered with a conviction of the mind and the presence of the Holy Spirit (which Jesus promised them). The apostles act boldly, teaching, preaching, performing miracles, and endure much persecution, suffering, and dying for God‘s glory. The church grows rapidly as a result.

Here are just a few events in the book of Acts: the outpouring of the Holy Spirit comes at Pentecost; the gospel is preached to the Jews and the Gentiles; the church grows rapidly in spite of resistance and persecution of it; Saul (a zealous Jew who persecutes Christians) is met by a blinding Jesus on the road to Damascus, believes, and is renamed Paul; and Paul and others go on missionary journeys as far as Greece and Rome.

Acts is certainly a book of action, and a perfect sequel to the gospels. It’s an historical ‘gut-check’: it’s stories and history are evidence for an affirmative answer to the question ‘did Jesus really rise from the dead?‘ Instinctively, it makes sense. The followers of ‘The Way’ wouldn’t have been willing to endure the persecution and suffering they did if the resurrection wasn’t true.

Christians pronounce that Jesus is risen: we say it and believe it, but do we keep it hidden? Do we act like we really believe it so others can see our faith? The stories in Acts can be used as evidence of the new church’s knowledge of the truth, resulting in the bolstering of one’s faith in Jesus.

I’m reading through Acts this month, and am behind the reading schedule in my Bible. So often it seems things don’t happen on my schedule, they happen on God’s schedule. But that’s the way it should be. After a week of good vacation and getting the taxes done, I’m having an enjoyable three day trip in sunny weather. It’s the third morning in Jacksonville, North Carolina, and I’ll be flying OAJ-CLT-LEX-CLT-DCA today (Charlotte, Lexington, and Washington).

We had an overnight in Lexington the first night of this trip. I liked it there, it was lushly green, with absolutely beautiful tree lined, hilly horse farms and meadows, complete with painted wooden fences. The folks are friendly there with true southern hospitality, and I had a good jog over to the nearby ‘UK’ (University of Kentucky).

However, in spite of the niceness of Lexington, I can’t go there without thinking of the tragedy of Comair 5191, on August 27, 2006.

The Delta Connection flight to Atlanta attempted to takeoff on 3,500 foot long runway 26, instead of 7,003 foot long runway 22. Forty-nine out of fifty souls on board died after the jet struck a fence and trees while struggling to get airborne beyond the short runway.

They attempted takeoff on the wrong runway because the Captain steered the jet onto it by mistake. The taxiway route to the runway offered the crew an opportunity to take a left turn at two locations. The first left turn was onto the ill fated short runway, the second left turn, a little further down the taxiway, was onto the correct runway.

It can be argued that there were many contributing factors for this accident. The control tower controller didn’t watch their takeoff attempt, information about the airport wasn’t supplied appropriately to the crew, the layout of the taxiways and runways could potentially trick pilots into using the wrong runway, the Captain didn’t get good rest the night before, and the crew engaged in non-essential conversation while the plane was taxiing. However, in spite of all these factors, in the end it was the pilots responsibility to make sure they were taking off on a runway that had adequate length.

What prevented either pilot from noticing they were on the wrong runway? Apparently, they didn’t check that the magnetic direction the plane indicated while on the runway was the same direction of their intended runway for takeoff (260 degrees instead of 220 degrees).  More fundamentally and less technically, apparently they didn't do a gut check: they didn’t ask internally or to the other pilot ‘does this feel right, is everything OK?’  Professionals in all fields of work perform ‘gut-checks’ routinely. ’ Experience is the best teacher’, and it teaches them to safeguard their work just by being aware and sensing when something is amiss and out of the ordinary. Gut checks are vitally important when operating at less than full mental capacity, as when fatigued, distracted, or both.

The paradox is that at the very time when it’s most critical to maintain a good situational awareness, when fatigued or distracted, is the very time when it’s most difficult to do so. I know this from experience.

The two most humbling mistakes (and they were very humbling) I’ve made in my airline career have occurred while I was taxiing the plane on the ground, and I believe they happened in part because I didn’t perform a gut-check. I wasn’t able to because I was tired and fatigued, rushed, and too distracted in non-essential (to the flight) conversation with my Co-Pilot on the ground. In the industry this is known as ‘violating sterile cockpit’, and it is big on the FAA’s hit list. Airline pilots are to observe a sterile cockpit - no conversation that doesn’t pertain to the safe operation of the flight - anytime the plane is moving on the ground or anytime below 10,000 feet in flight.

Applying this line of thought to this accident, I believe that short term fatigue and distraction from violating sterile cockpit helped to prevent this crew from taxiing to the correct runway, and to prevent them from aborting the takeoff before it was too late.

I examined the cockpit voice recording transcript briefly, and the crew (mainly the First Officer) did ‘violate sterile cockpit‘, but not to a gross extent, in my opinion. However, lack of focus is possible when distracted by emotion or thought about a non-essential conversation, even if its a short one. I have seen this occur to me numerous times, and I believe it is one of the main considerations for the sterile cockpit rule. What I mean is that’s how I think the mechanism works: while a mistake can occur during the moment sterile cockpit is violated, it can also occur afterwards. Non-essential conversation can induce a type of lingering distraction to pilots during a period of flight operations that is critical to the safety of flight.

I mentioned fatigue as another characteristic which reduces the ability to maintain situational awareness. Unfortunately, the Captain of the accident flight didn’t get good rest the night before, due to his wife and two infants spending the night in the hotel with him. He complained on the CVR about his lack of sleep to his Co-Pilot. I was fatigued when I had both of my problems aforementioned on the ground, the first after a short night of sleep after commuting in to my base for an early showtime, and the second after a long duty day full of schedule changes. When fatigued, one simply doesn’t have the ability to perform to the same level as when not. Slowing down the pace at which one completes tasks and adhering to SOP’s (standard operating procedures) are two ways to counteract the effects of fatigue.

This accident, like other airline accidents and incidents recently, exhibit symptoms of a lack of flight discipline, which stems from a lack of professionalism. Frankly, others I've talked to are like me, we never expected Comair, a regional airline whose pilots always had a reputation for being true professionals, to have an accident like this.  If Comair could have this accident, any regional airline could.  This problem of a lack of professionalism is endemic in our industry, and it seems to be difficult to get across to all pilots the insidiousness of it. The negative reaction seen at times involves an impulse to blame airline management for poor schedules and reduced pay, instead of examining their own personal standards of professionalism and flight discipline. Poor schedules and reduced pay are problems the pilot unions continue to battle to win improvements on, but these issues are no excuse to absolve pilots from their duty and responsibility to safely transport the flying public with the highest standards possible.

OK, short rant over. In review, fatigue and distraction both reduce pilots ability to ‘trap errors’ and perform a gut-check. Performing a gut-check is good thing to do in aviation or any industry:

- be in tune to your instincts, trust them, and follow them

- when fatigued and/or distracted, the ability to perform a gut-check is diminished

- when fatigued and distracted is the time when SOP’s are the most important to follow to the letter. Adhering to a checklist, callout, or procedure when fatigued and/or distracted makes it more likely than otherwise that a critical item won’t be missed.

I got a little academic, but this is the way I see it, and I make no apologies for it. The opportunity to learn and lessen the likelihood of more tragedy and loss of life makes it worthwhile. Thanks again for reading my blog.

PS: In case you're curious, I continue to battle against fatigue and distraction I encounter on the flight deck.  After I've made mistakes of the type which in the past I would point to others and say quietly "I could never do something that silly", I operate more conservatively and with better flight discipline than I ever have as a pilot.  I still learn new things about the airplane and how to better perform my job, and I hope I always will.

Friday, April 2, 2010

Good Friday sense

It’s day five of flying for me, tonight will be night number six away from home. I’m spending the day in a Hampton Inn in Greenville, SC, where everything is green, or greening up in the early spring. Tonight I’ll fly from GSP to Charlotte, only about a twenty minute flight maximum, then deadhead back to DC for the night. I miss my wife and girls, and will be home tomorrow afternoon, for a week of vacation and four days extra scheduled off, away from the skies. So, two days before our Easter holiday, it’s a good Friday, in fact it is THE Good Friday, and I’ll be writing about that subject in a paragraph or two.


The first couple of days of this trip we endured a lot of turbulence in the clouds, immersed and enveloped ‘inside the lampshade‘, in white and gray. Climbing and descending to find a smoother altitude for our ‘peeps’ didn’t help much, so we usually just slowed down the plane and endured it. My Co-Pilots and I had to fight gusty crosswinds on takeoff and landing. We airline pilots generally like the challenge of a crosswind, passengers generally don’t. Not seeing the blue sky or sun for entire flights is strange at times. It still intrigues me to navigate using only our instruments on the flight display screens in front of us, then pop out of ragged clouds and mist with the runway right in front of us, canted at an angle, due to our ‘crab angle’ into the wind.

On the second day we were flying north over western New York, destination Toronto, Ontario, Canada, when we seemed to reach the end of the endless clouds. It started clearing over Buffalo, New York, as center had us descend to 10,000 feet. I got out my camera because I knew Niagara Falls was coming up, and it looked as if we would get a chance to photograph it. This is from two miles above the ground with a zoomed lens, but it’s still very impressive.

I think it’s only fitting that I quote Jesus’ from John 7:37 (ESV) here: “Whoever believes in me, as the Scripture has said, ‘Out of his heart will flow rivers of living water.’” Wow, what a river of living water, indeed. I will see it up close in person, someday.

Below is a picture of the river and lakes of the Niagara Falls region, this was taken while we were headed south, from Toronto back to Philadelphia. In the foreground is Lake Ontario, in the background is Lake Erie. That little puff of white is the mist rising from the Canadian, Horseshoe falls side. The river is the Niagara river, and it flows from south to north, background to foreground, from Lake Erie towards Lake Ontario. Unless you’re geography limited, like I was about this area until a few years ago, it doesn’t make sense without an explanation. Here's a google map of the same area.  It’s still tricky for me to make sense of it, of a river that flows from south to north, and not only that but a humongous waterfall over seemingly flat country. But with a little knowledge and explanation, it does make sense. Rivers all over the earth flow from a higher elevation to a lower elevation.

It can be hard to make sense of Jesus’ sacrifice of his life on the cross too. With a little knowledge and explanation it begins to make sense too. God loves you! God loves us, every one of us, and He wants to have relationship with us, now and for eternity. Our sin (which is turning away from God by our thoughts, words, actions, and deeds) separates us from God, because God is Holy and perfect, and cannot and will not tolerate sin in his presence. As a matter of fact, God will destroy whatever is sinful in his pure presence. But God made a way, from the beginning, to ‘fix’ our imperfectedness and restore our relationship with him. Jesus. He said in John 16:13 “there is no greater love than to lay down one’s life for one’s friends.”

Many skeptics of Christianity accept that a man named Jesus Christ of Nazareth was crucified on a cross, but they draw the line there. But without Jesus’ resurrection from the dead, his crucifixion doesn’t make sense at all. The resurrection is absolutely essential to Christianity. But don’t just take my word for it, feel free to check out these three links, by others much smarter than me about the subject: No Christianity with the Resurrection, Christianity is Resurrection, and Resurrection essential to Christianity.

Without Jesus rising from the dead:

-His death on the cross was in vain, and unable to defeat sin; in other words the pain and suffering of crucifixion, ‘bearing the guilt for the sins of many’, was unable to overcome death.


-He was just a man, and not God.


-He was a liar, and so were his disciples. All the times in four gospels where Jesus promised that ‘whosoever believes in me shall not die, but have everlasting life’ make him and the gospel writers out to be liars.


-God has permitted all true Christians out to be liars as well. I can’t, don’t, and won’t believe that the nature of God is like that, the Bible says otherwise in plenty of places.

The proof that Jesus’ perfect sacrifice was sufficient enough to make us sinners right with God (“by grace through faith” - Ephesians 2:8) is in the fact of his resurrection itself, and gives all believers confidence that at some point after we die in this life we will have resurrected bodies and eternal life, just as our Savior promised multiple times in the gospels, and as the New Testament authors espoused on.

Perhaps the most memorable New Testament passage regarding the essentialness of the doctrine of the resurrection was by the apostle Paul, in I Corinthians 15:12-19 (Amplified): "12But now if Christ (the Messiah) is preached as raised from the dead, how is it that some of you say that there is no resurrection of the dead?  13But if there is no resurrection of the dead, then Christ has not risen; 14And if Christ has not risen, then our preaching is in vain [it amounts to nothing] and your faith is devoid of truth and is fruitless (without effect, empty, imaginary, and unfounded).  15We are even discovered to be misrepresenting God, for we testified of Him that He raised Christ, Whom He did not raise in case it is true that the dead are not raised.  16For if the dead are not raised, then Christ has not been raised; 17And if Christ has not been raised, your faith is mere delusion [futile, fruitless], and you are still in your sins [under the control and penalty of sin]; 18And further, those who have died in [spiritual fellowship and union with] Christ have perished (are lost)! 19If we who are [abiding] in Christ have hope only in this life and that is all, then we are of all people most miserable and to be pitied."
 
Wow, what a statement and declaration of truth by Paul.  If we have no resurrection from the dead then Jesus doesn't either, and we are to be pitied by others, and we are, because they don't believe it (the resurrection).  But we brothers and sisters in Christ know otherwise, for we have experienced the prescence of Christ in our lives, and the peace, joy, fellowship, love, and purpose that comes along with it. 
 
Hallelujah, for He is risen!  He is risen indeed!

Happy Easter everyone, whether you observe and believe the resurrection of our Lord or not.  Thanks for reading my blog.

Tuesday, March 23, 2010

Geese!

It's Tuesday, mid morning on day three of my current trip, in Milwaukee, Wisconsin.  Under a white but clear sky the sun is getting rid of the dew on the grass and surfaces.  From my hotel window I can see the airport only a quarter mile away, and a jet on final.  It's going to be a great day, it seems.

Our first day had us flying six legs on a Sunday, in and out of New York LaGaurdia and Philadelphia, mostly.  We arrived in New York on the second flight of the day, then saw it again after stopping in Philly once.  After seeing Philly twice we were to make our way up to Allentown, Pennsylvania for the night.  Allentown is pretty close to Philly so it would be a busy, short flight.

On our third flight, LGA-PHL, we had a jumpseating pilot up front.  He was a Captain for a large regional airline which has a good prescence at LaGaurdia, but not ours.  He seemed like a sharp fellow, and proved it before the flight was over.  Our First Officer was flying the plane with the autopilot engaged in the Philadelphia terminal area, and I was handling the radios and checklists while we were getting vectors for the visual approach to runway 35 (landing towards the north).  Philly sometimes gives us delay vectors for 35 because they have to coordinate the proper spacing for the landing runways.  Runway 35 and runway '27 right' physically cross each other, like a street intersection, so it's critical that we have safe spacing when they are landing jets on both of these runways.  After zig zagging per ATC's instructions for a few minutes it looked as if we would be cleared for the visual approach at any second.  We could easily see Philadelphia International through the afternoon haze, in a very pleasant appearing sky, about ten miles away.  We were about 2,000 feet above the ground, pointed toward the airport, when a voice shouted, loudly, GEESE!!  It was our jumpseater, looking out for us.  The fact that I nor my FO hadn't seen them didn't bother me, I was glad that 'Dan' our jumpseating pilot in the extra seat, did.

Upon all of us looking up, there they were, at our altitude, almost right in front of us.  Actually, they were from our center position in front of us off to our right.  It was two large flocks of big honkers, Canadian Geese, the kind that brought down US Airways 1549.  Just as my brain thought that we needed to disconnect the autopilot and manuever to avoid these birds, and I may need to ask my FO to do just that, he did.  "Blink blink blink blink" (a poor imitation) the sound came as he disconnected the autopilot and smoothly but quickly banked the plane to the left to avoid the flock, and the birds nearest to our flight path banked away from us as well.  We had other options if the birds had been right in front of us, on both sides, but thankfully they weren't, and we didn't have to consider them.  If that had been the case, whomever was flying the plane could have disconnected the autopilot and started a sudden climb or dive to avoid the birds. 

But that would have been a tall order, at the range we can identify birds in our way, there just isn't enough time to be that clever, it's a matter of three to five seconds before they're there and past you, it happens quickly.  We aren't given specific training or advise on how to avoid flocks of big, aiplane damaging birds, besides the simple but sage advice of "see and avoid". 

I reported a large flock of geese at our altitude about two miles behind us to approach control, right after they cleared us for the viusual approach to runway 35, shortly after our encounter with them.  They appreciated it, and had already been busy advising other aircraft on final approach for runway 27 right of other flocks of geese in the final approach path for that runway.  It was a certain afternoon of risk for a large bird strike at Philly.

After ten years of airline flying, this was the second closest I've come to a large bird strike incident, and the largest flock I've seen up close.  The closest were 'six flashes above out heads at night',  while descending into a prarie airport.  See my original posting here for that one.

I hear these beautiful birds outside my open window now, landing in the courtyard of the hotel here.  I like these honkers, like watching them fly and hang out; they are certainly majestic and beautiful.  And dangerous.  I have three more days of flying and avoiding flocks of birds, before this bird writing this heads 'north', to migrate back home.

Friday, March 19, 2010

Post-PC ramblings on love

(I wrote the first part of this about a week ago, but am just getting around to finishing it now)

I’ve just enjoyed, or 'loved' two days off at home, or two half days and one full day at home, or, best expressed, forty-eight straight hours at home. I had a PC (proficiency check or check ride) again in Charlotte, with a relatively good time slot of four PM to ten PM, plus a debrief. Spending another night in Charlotte meant my first day off from flying or training duty was actually a travel day (still a working day) I get paid for, to travel back to my domicile of Washington, DC. Instead of going home through Washington, I got up early on just a few hours sleep and jump-seated to the Twin Cities of Minnesota and then home, to big slushy snowflakes falling at the airport, but a cold rain falling on the other side of Sioux Falls, South Dakota, the city I commute out of. The seasonal change to spring is almost upon us, and the first day of spring is one week from now, excellent.

About my PC: it went fairly well, after I spent most of a long overnight in Charlotte preparing for it the day before. There’s always so much to study for, and as usual, at some point I felt like I studied a few of the wrong things I hope to study earlier and smarter next time.  I even made a simple sixth month studying checklist after this one: if I study such and such each month I won’t have to cram as much for it next time. But I made no serious mistakes, no retraining was done, and best of all, I didn’t crash! With simulated engine failures on takeoff and realistic wind shear encounters, it’s a possibility. Also, It’s considered a good sign if the Instructor is nitpicking your technique, which he was, honestly.

I don't love PC's, but I don't loathe them either.  It’s always good to have a review of our jet’s systems and procedures, backed up by a demonstration of my capability to actually fly and perform those procedures in the simulator. We know what’s going to happen, pretty much, the instructor is mainly the facilitator of that during the flying portion, and the quizzer during the oral portion.

The ‘box’ (the simulator) has a delay, a lag, however, between the time you apply the controls till when the ‘airplane’ reacts. This is due to the time it takes for the host computer to realize you want a greater bank angle or lower pitch attitude, for example, and then to calculate the change and transmit the response to the simulator itself. The advice to overcome this tendency is to make a control change and wait a moment longer for it to happen than you would in the airplane. But it takes discipline to not over control the simulator, it does for me at least. I remind myself to wait and not over control, and to breathe, as strange as it may sound. Breathing well helps you to think, not surprisingly.

And when I have two days off at home, like I do every time I have three days off while commuting on two of them, two subjects enter my mind: I must make the best use of my precious time at home, and I ponder why I’m doing this: why do I continue to sacrifice time with my wife and girls, and time at home?

Besides my religious and spiritual motivation which helps me to justify being away, and upon which I've expressed at length before, there are a couple other prime reasons I've neglected to mention. I need a job to pay the bills and the mortgage, and support my family with, that's the simple one.

The other one, and I'm surprised that I've never come outright and wrote it here, is that I love flying. I Love flying! I've always been fascinated by airplanes, long before I was a pilot, since I was a boy on our driveway, craning my neck to watch Cessna's and 727's pass across the sky.

Here are just a few things I attach the L-word to in flying: punching through an overcast layer of clouds into the burning blue sky, and surfing them for a moment while still enveloped; dodging puffy stray cumulus clouds, using these giant punchy cauliflower growths as pylons in the spring and summer; the challenge of hand flying a final approach, still mystified at the runway enlarging at us in a 700 foot per minute descent and at a speed of two and three-quarters a mile per minute; takeoffs are fun but landings are better, a tailor made return to terra firma satisfies my passengers and myself, sometimes I say “lucky again” out loud to avoid grandstanding (and to keep the "luck" going).

I wouldn’t exactly say “I love being a Captain” and having all the responsibilities and leadership role that comes with it, but ‘its good to be the king’, as Mel Brooks says. Some of you youngsters might have to Google that to get the reference. I would much rather be a Captain than the First Officer, but I'd rather be in a secure sport at a major airline than at a regional.  I’m always my favorite Captain: I get to run the show the way I want to, within reason and our SOP’s, of course.

It bears worth writing again that the hardest part of this job is dealing, in a healthy way, with the emotional and physical toll due to not being home. Again, I’m blessed and lucky to be doing something for a living that I love to do. Not everyone gets that opportunity. Too many pilots lose sight of their love for flying, they let the demands of the job overshadow their passion for it.

Life is meant to be lived in balance, it is demanding when getting the most out of it, whether you’re a free spirit or a devoted religious person. My personal experience has been that a life lived “in Christ” brings balance, peace, and an eternal perspective that re-orients one’s eyes and heart anew. Want to be in better balance on the see-saw of life? Put Jesus on the other end!

This is some of what I’ve learned, and keep re-learning, with Jesus Christ in my life: God loves me, not because of anything I’ve done or will do, He just does. God’s will for me is to know him, and to make him known, and to glorify him, whether I‘m flying planes or fixing drains.

He wants to be lived out in me! May I be so presumptuous to say exactly this? Yes, the following Bible passages quote Jesus implicating it to be so in John 14:23 (his home with us), John 15:4-5 (the vine and the branches), and John 17:21-23 (Jesus prays for his disciples).  Galatians 2:20 is one of my favorite verses in the New Testament.  Galatians was written by the apostle Paul, whom Jesus, in glorified form, met and temporarily blinded him on the road to Damascus, while Paul was named Saul, a zealous Jew, and actively persecuting Christians.  Paul teaches clearly in this verse that Jesus lives in us: Galatians 2:20 (ESV): "I have been crucified with Christ.  It is no longer I who live, but Christ who lives in me.  And the life I now live in the flesh I live by faith in the Son of God, who loved me and gave himself for me."

Love is an interesting thing, it asks you to do things you might not want to do otherwise. Love asks you to sacrifice. My wife and I have sacrificed a lot for each other, and will continue to do so, out of love for each other and to enable me to do what I love. “God so loved the world that he gave His only begotten Son, that whoever believes in Him should not perish but have everlasting life” - John 3:16. The proof of the love God has for all of us is in Jesus Christ, my friends.

Thanks for reading my blog, and God bless you today.

Saturday, February 27, 2010

Toronto, pronto

This image of the weather map for the northeastern US last night essentially shows the conditions we experienced yesterday, while trying to fly seven legs.  Bands of snow rotating counter-clockwise around a low pressure center between Boston and New York City made it interesting for the second day in a row for everyone in this area. 

My FO and I agreed both that the safety of flying seven flights and seven hours in a day is questionable, and it definitely isn't doable on a day like this.  DC to PIT to Philly to Toronto to Philly to Allentown to Philly to Binghamton was our itinerary.  Regardless, off we went.

Very gusty winds got my attention taking off on the short runway from DC.  Our CRJ juked and jived in the gusts as I turned away from the Pentagon to follow the Potomac river to the northwest, climbing out steeply while wondering how long the constant turbulence would last.  It wasn't long; we cruised over to Pittsburgh at 20,000 feet above the clouds, enjoying the sunshine with the familiar blue backdrop.

In about a mile of visibility because of snow falling, I landed on an all white runway, one with a thin snow cover, highlighted by wavily shaped snow drifts.  After deploying the thrust reversers to full, I applied the wheelbrakes smoothly but surely, increasing the pressure as I stowed our thrust reversers below 80 knots indicated airspeed.  The 'braking action' was there, somewhat more than barely, you could say.  The anti-skid was now cycling constantly, but we were slowing down, slowly, on this 11,500 foot runway in Pittsburgh.  The control tower told us other pilots had reported the braking action as fair, but I though it was closer to poor, and my FO told them so.  Braking action is subjective, and in my opinion this same braking action in DC on the 6,870 foot runway there would definitely been called 'poor'.  I used about 6,000 feet of runway in landing and slowing down.  After waiting for and watching an efficient bulldozer driven snow scooper plow our ramp area, we parked and boarded up quickly for Philadelphia.

Out EDCT (pronounced 'edict') time (Expect Departure Clearance Time) for PHL was 12:15 PM, but on our taxi out we learned they had extended it to 1:15 PM.  Our Dispatcher hadn't sent us an ACARS message to 'hold our push' for some reason.  We taxied to a spot on a taxiway between the snow drifts, and I elected to shut down the engines to conserve fuel.  We actually didn't have much left before we would burn down to our takeoff fuel, and then we would have to either reduce our takeoff fuel by decreasing our holding fuel or go back to the gate to get more gas.  We had an hour to wait as it turned out; they decreased our takeoff delay a little.  I briefed the pax, and after a short wait we started up and got deiced quickly by PIT's excellent deice crew.  Their setup looks like this, using enclosed control cabs on the end of booms connected to ground structures, instead of trucks.




After lining our chariot up on the centerline of this runway (yep, it really is one, see the runway edge lights?), I gave the reins to my FO, who did a great job of keeping us straight on the takeoff roll.  We knew this due to the increasing frequency 'thump thump thump thump' sound the nosewheel tires made in rolling over the runway centerline lights.  Ah, the neat, challenging, and sometimes a little perplexing things you get to see as an airline pilot.  When some visual clues are lost it forces you to use what clues you have left.


In the clear again cruising over to Philadelphia, valleys of smooth and fluffy clouds below us hid the reality of a serious winter storm giving it's best blows on the ground.  Much of the time when the weather gets rotten in winter, with high, gusty winds and snow, the wind blows straight down the runway, and that's what it was doing on the ground in Pittsburgh and Philadelphia.  When a pilot has to deal with a low visibility approach with snow, reduced braking action on the runway, and then a healthy crosswind on top of it, that tends to up the ante and the heartrate.  The weather report for Philadelphia was considerably better than the delays imposed on us indicated earlier.  The snow was gone, the runways were dry, and they even offered us a short runway, after clearing us for a visual approach to the long 27 Right.  'No thanks'.   

Gold star time!  By the time we parked at the gate in Philly, we were about an hour behind schedule.  Cause I'm a team player (and because I packed my lunch), I offered to our Flight Attendant that I would say goodbye to the passengers and clean the cabin for her.  She'd already asked for a food run in Philly, and she took me up on this time saving offer too.  I'd never actually done this before, and I'll try to make it a habit when I can.  (Passengers, at the regionals don't get our cabins cleaned by cleaners like at the majors; our flight attendants (and pilots sometimes) do it ourselves.) 

PHL-YYZ, our third out of seven flights was next.  Toronto's ATIS was interesting.  Toronto was only landing on one of it's five runways, and wasn't using the runways which faced into the wind at all. For my FO, the pilot flying, it was going to be a 10-15 knot crosswind landing on a snow covered runway with fair or worse braking action, in falling light snow. What more can you ask for?  How about not having to divert to our alternate airport.  After just passing Buffalo, NY, we heard Toronto Center (ATC) give a holding clearance to two aircraft in front of us.  Holding at a fix name 'Linng' southeast of Toronto, soon became our fate as well.  We had a lot on our plate to think about, in quick order.

Here's the rundown: After conferring with out dispatcher with messages sent and recieved using our ACARS unit in the flight deck, our bingo fuel was 3,200 lbs.  Entering the hold we had 4,200 lbs, and each engine was burning about 1,000 lbs per hour of jet fuel.  Pilot mental math converts that to 30 minutes holding time.  If we weren't released from the holding pattern to continue to YYZ before we our fuel remaining reached 3,200 lbs, we were diverting to Buffalo.  And the weather at Buffalo, called up on ACARS, sucked, frankly.  Any pilot would agree that 1/2 mile visibility in moderate snowfall, freezing fog, and a healthy crosswind is not the best weather to have at your alternate airport that you could very possibly divert to. 

Toronto ATC never offered a clear reason why we were holding, I think the one runway they were landing planes on was full of traffic.  My FO offered that we should consider other options than Buffalo, and we did call up weather from other suitable airports.  None were as close as Buffalo, and if we were to divert, I preferred to land in the US, at an airport which was served by the airline we fly for, to make handling our pasengers of various nationalities easier.  Elmira and Syracuse were bad, and too far away by this time, because of our fuel.  Hamilton, in Canada, was ok, and Erie, PA, was not too great, but doable, fuel wise.  Fortunately, with the next hour's weather report, at 4 PM, Buffalo reported much improved weather, two miles visibility in light snow with better winds.

By this time we had been holding for about fifteen minutes, had a solid plan to divert to Buffalo if we bingoed on our fuel, and were hoping Toronto would open the additional runway soon.  Two other airliners holding in front of us were having fuel issues too.  One gave up and proceeded to their alternate.  Our fuel situation by now: together with the two engines we were using 2,000 lbs an hour, or 200 lbs each tenth of an hour, or 200 lbs every six minutes.  We now had 3,600 lbs, or twelve minutes left.  I asked Toronto how long till the runway is open, notifying them also that we have ten minutes of fuel left before diverting.  'Oh about fifteen minutes they say' in a polite canadian accent came the reply. 

I had briefed the passengers three times, the first being routine, the second being a little concerned and sharing the possibilityof diverting, and the third with the likelyhood of diverting.  I don't like diverting, but I'll do it if I have to.  Tick, tock, tick, tock.  "___  ____ you are now cleared out of the hold, fly heading 180 after Linng"", he told us.  They were clearing us out of the hold with a turn to the south, before having us continue on the arrival northbound.  Good news.  We had about 3,500 lbs, about nine minutes more of holding fuel left.  It looked like the other airliner bugging our had worked in our favor. 

On approach the changing weather had gotten a bit better, the cloud ceiling was higher, about 3,500 feet above the ground, and the crosswind was about half of what it had been before, about seven knots now. 

The control tower reported that the braking action reported by pilots was fair on the runway, and poor on the runway turnoff.  But like I experienced in Pittsburgh, my FO rated it as poor, and told the tower so.  We took the slippery turnoff about two-thirds down the 11,200 foot runway, and taxied in slowly on one inch of fresh snow.  Then we saw and appreciated this:

This behemoth, seen through the falling snow, is the new largest airliner in the world, the Airbus A380.  Those are two passenger decks you see, the entire length of the fuselage.  It flys all the way from Dubai, UAE to Toronto, a world away in culture, geography, religion, government, and weather.

"Hast thou seen the white whale?" Captain Ahab asks.  Well, I have now.  As an aside, I just finished reading, for the first time, Moby-Dick.  It was hard,  took me six months.  It's about much more than an egomaniacal Captain seeking vengeance on a whale.  I could wax on about it, but I can't do it justice.  Maybe just a little.  I highly recommend it. 

I will say a couple things.  I identify with Starbuck, the first mate of Captain Ahab, a man of true Christian faith, and one with his head on straight; he tries valiantly to talk Ahab out of attacking Moby-Dick.  A little background on the white whale: Ishmael, the narrator of Moby-Dick, teaches us that all sperm whales are dangerous, but Moby-Dick is a giant who has a fearsome, evil reputation for killing whalers.  Ahab is demented, hell bent on killing Moby-Dick, because of his vengeful pride (Moby-Dick took off half of one of his legs previously), but moreso because he's wrapped up in the 'white whale' his personal bias against the existence of evil and 'fate', (i.e. the unfairness and unapolagetic circumstances of life) in the world.  In demented and megalomanical character, he believes he will rid the world of the problem of evil if he kills the white whale.  It ordinarily sounds strange and implausible for a human to leap to this level of egoism, but in the backdrop of such a grand and mystifying vocation as hunting on the world's oceans (with sailboats and hand thrown harpoons and lances) these huge, majestic, and spiritually associated (by humans) whales, the subject matter and symbolism is easily pulled off by author Herman Mellville, over 150 years ago.  It is an epic and timeless book.


In this picture you can see how big the 'white whale' is compared to the 737 next to it.  We taxiied in and with typical canadian efficiency we boarded up a new batch of passengers for Philadelphia.  I had a message on my phone from crew scheduling, but because I don't get minutes in Canada and it's pretty expensive if I do make a call, I didn't check it.  It was good news (for us), however; we found out after landing in Philly that our Allentown, PA round trip and our Binghampton, NY overnight had been canceled.  We were overnighting in Philly after flying four of seven legs. 

I haven't written too much on spiritual stuff lately, but God is still calling me, and I'm still answering.  Even when I don't answer, he still calls.  What a commitment God has made to all humans through the work of his son, Jesus Christ!  The problem Ahab had with Moby-Dick and evil has been solved by Jesus.  We can fret and philosophize over it, but we're better off examining the life and nature of God's son, who died on the cross for all of our sins, and, well, evil.  The answers to the questions of life and the true life, personal relationship with God, are  found in Jesus. 

What is your white whale?  What is your frustration in life, that has got you in a bind, a bias, against God?  What has been unfair to you in life that has influenced you to think God doesn't care?  God does care.  BTW I'm just assuming these things, my dear reader, I know that not everyone has a grudge against God.  I have had a grudge againtst God before, myself, a few times.  I likely will again in the future, but that won't invalidate my faith.  Recently I flew with a good guy with a poor attitude.  He appeared to have a Christian, but cynical, faith.  His cynicism extended to his personal life and our airline.  To you, my friend, and others, I submit one of my favorite and simple verses: the word of Jesus from Matthew 11:28-30: "Come to me, all who labor and are heavy laden, and I will give you rest.  Take my yoke upon you, and learn from me, for I am gentle and lowly in heart, and you will find rest for your souls.  For my yoke is easy, and my burden is light." 

Until next time, thanks for reading my blog.