-->

Tuesday, April 30, 2013

2013 Annual Inspection (ii)

This year's Annual Inspection, now completed, was an unusual one. And I mean that in a good way. There was very little "emergent" work resulting from the inspection and most of the work effort was focused on items properly classifiable as "maintenance". Even the one major cost item, the inspection and resealing of the propeller (first discussed here) was not the result of a "squawk". The prop was turning just fine when removed from the airframe.

If you wonder what happens when the propeller shop is told to "IRAN & Reseal" rather than overhaul, the log entry for the propeller work is instructive:

"Propeller disassembled, cleaned and visually inspected for red dye oil leak. Replaced all seals and gaskets. Reassembled, set angles, track and balanced. Propeller filled with red dyed oil and pressure tested."

The engine, at 1749.3 hours Since Major Overhaul (SMOH), seems to be holding up very nicely. The pressure drop data is perfectly acceptable (see the chart at left for seven years of data), the filter media were free of metal particles and there were no worrisome indications found by borescope. An oil sample has been sent off for spectrometric analysis but I don't anticipate any bad news from that quarter.

I flew the airplane for a 1/2 hour local test flight last Thursday evening with the only squawk being that the landing lights (both of which were replaced) were inop. As it happens, there is an in-line connector in the wire harness that supplies power to the landing lights and it has to be unmade to remove the lower cowling. In this case, it didn't get re-made when the cowl was re-installed. That minor glitch was remedied the next day and on Friday I flew N631S down to the DC area for the first time in three weeks. Then we flew back, mostly in rain and clouds, yesterday morning. No new problems showed up so I'm ready to call it done.

The only leftover item – which is an expected issue – is the need to adjust the Shadin Miniflo-L fuel computer to correctly interpret the output of the replaced fuel flow transducer. Every transducer is tested by the manufacturer to determine the number of electrical impulses it emits per gallon of flow passing through and that "K-factor" is supplied with the sensor. For this unit, the K-factor is 19.8, meaning 19,800 pulses per gallon. Right now, the computer is reading about 10% high. To correct the condition it has to be removed from the panel and reprogrammed with the new K-factor. Naturally, this can't be accomplished in situ, as that would be far too easy. So sometime soon my friends at Three Wing Aviation Group (check out their spiffy new web site!) will make the adjustment and all will be well.

I anticipate one more post about this year's Annual wherein I'll analyze the final invoice.

Wednesday, April 10, 2013

Eternal Father, Strong to Save...

On 10 April 1963, fifty years ago today at 9:18AM EST, the Sea enveloped in her cold embrace the 129 men aboard the USS Thresher and took them away from their loved ones forever. It is important that we remember.

I remember. I was 14 at the time and in the habit of listening to Jean Shepard's program on WOR radio from New York before going off to sleep. There was a news bulletin. The Navy was reporting one of its submarines as overdue at Portsmouth Navy Yard. A search was underway. I had no understanding of abyssal deeps and vast pressures, and so I went to sleep with hope. As I'd understand in future years, my hope was unjustified.

Of course, a day or so later, the finality of the loss was made clear. She was gone and her people were gone. The convening of Boards of Inquiry was announced. It was the first loss of a nuclear powered submarine, and in fact the lead ship of a new class, so naturally much was made of the disaster. But little information was forthcoming and of course the events of November of that year drove everything else from the front pages.

I really didn't think very much about Thresher until eight years later, in the summer of 1971 when I went to work as a design engineer at the Electric Boat Division of General Dynamics Corporation. Immediately, I was plunged into the design effort to incorporate modifications known collectively as SUBSAFE on the forthcoming second overhaul of the Lafayette class of ballistic missile submarines. The work embodied in the SUBSAFE program was the direct result of the loss of Thresher.

There are two aspects to SUBSAFE. One is an intensive quality assurance regime encompassing both materials traceability and rigid process controls. The other involves improvements in systems design to ensure that the casualties that are inferred to have led to the loss of Thresher can never again have similar consequences.

Based on the painfully limited evidence, those investigating the ship's loss concluded that the precipitating casualty was the failure of a seawater pipe joint in one of the ship's machinery spaces. The crew was unable to secure the inflow of seawater from this failure. The intense spray, driven by the pressure of the sea at or near Thresher's design depth, would have penetrated electrical control panels and caused the loss of propulsion. (NB: Recently a countervailing theory has emerged which posits that the seawater piping failure is neither likely nor necessary to account for the loss of the ship. The sinking, it holds, could have followed from loss of propulsion due to an electrical casualty compounded by a failure of the ballast tank blow system.)

At the time, the design and operation of the nuclear propulsion plant was governed by a philosophy that focused on saving the reactor at any cost. So any disruption of control circuitry would cause an immediate reactor plant shutdown. But this deprived the ship of the ability to use hydrodynamic forces against the effects of the flooding casualty. Would a few more minutes of propulsion have made a difference? We'll never know.

The last hope would have been use of the ship's high pressure air banks to blow the main ballast tanks on an emergency basis. Testing later showed that the rapid flow of air through the system would have caused plummeting temperatures and formation of ice that would block the piping and prevent the air from reaching the tanks. With no way to deballast, no propulsion, and no way to secure the flooding, Thresher was doomed.

With the adoption of this scenario as "probable cause", the SUBSAFE program set out to address each stage of the cascade of casualties. The quality assurance aspects sought to ensure that all seawater piping systems could always withstand the pressures of the deep. But if that failed, hydraulic remote valve actuation systems were installed (that was the piece of the puzzle I worked on) to ensure that hull and backup seawater valves could be shut to secure flooding. And last, the Emergency Main Ballast Tank Blow system was completely redesigned to ensure that it would be effective under all circumstances.

Outside of the bounds of SUBSAFE, the design and operating philosophies of the Naval Nuclear Propulsion Program were modified to allow ships to maintain propulsion as long as possible in the event of a casualty even if damage to the reactor is a possibility.

Did SUBSAFE accomplish its mission? The evidence says that it did. From 1915 until the loss of the Thresher sixteen US Navy submarines were lost to non-combat causes. Afterward, the only such loss was that of Scorpion in 1968. That ship was not yet SUBSAFE certified.

I am proud to have been involved in a modest way in the implementation of SUBSAFE. And I hope that the surviving relatives and friends of those lost aboard Thresher 50 years ago can find solace in the fact that their loss led directly to a profound reduction in the risk of submarine operations.


Eternal Father, Strong to save,
Whose arm hath bound the restless wave,
Who bid'st the mighty Ocean deep
Its own appointed limits keep;
O hear us when we cry to thee,
for those in peril on the sea.

Tuesday, April 2, 2013

2013 Annual Inspection (i)

Yesterday was the first day of N631S's Annual Inspection availability for 2013. My friends at Three Wing Aviation Group will be doing the inspection and associated work package and this year Tony diNuzzo is the IA on the case. I've known and respected Tony for a long time now, and am looking forward to working with him.
Our last flight up from the DC area had been uneventful and I had very few "squawks" to report. The taxi light bulb had burned out a couple of months ago, and the landing light joined it about a month back, so both of those bulbs will require replacement. And the performance of the Shadin Miniflo-L fuel totalizer has been increasingly erratic, so we'll take this opportunity to replace its transducer with a spare that I acquired a year or so ago.

Beyond those tasks, the most notable work-item planned for this year is an inspection of the McCauley constant speed propeller. The prop was overhauled in conjunction with the 2005 Annual Inspection – the first year N631S spent with us – and so it now has about 1,200 hours and eight years SPOH. McCauley holds that the recommended TBO (Time Between Overhauls) is 2,000 hours or seven years, whichever first elapses.

I feel no compulsion to overhaul components at some arbitrarily selected calendar time or time-in-service, as I'm a firm believer in maintenance "on condition". N631S's Continental O-470U engine has a recommended TBO of 2,000 hours or 12 years. The latter mark has long passed and I will cheerfully let the former pass unremarked as well, so long as the engine is talking to me and saying, "I'm fine, boss...let's go fly." And it will do so through spectroscopic analyses of the oil, visual inspections of the filter media and borescope inspections of the cylinders and valves. Ah, but the propeller presents a different problem.

The propeller is a "black box". It doesn't speak to you and there is no way to know that it is sick until something Very Bad happens. Recently, blogger Ron Rapp did a post (which I endorse in its entirety) on Constant Speed Propeller Maintenance, where he describes some of the Very Bad Things that can happen to a sick propeller with terrifying suddenness. I take these things to heart and view propeller maintenance as something you neglect at your mortal peril.

That said, I don't want to "overhaul" the propeller. In the world of aviation, the word "overhaul" has a very specific (and expensive) meaning. It means that you drag out the manufacturer's overhaul manual and do everything that it says to do. But N631S's prop was overhauled back in 2005 and since then has accumulated about 60% of the hours McCauley assigns for TBO. It's just nicely broken in, from the perspective of hours in service, and I'd argue that an overhaul would be premature. My concern is directed more toward the notion that non-metallic parts wear and rubbery things deteriorate more in step with the calendar than with the Hobbs meter. So I've asked Three Wing to take the prop off and send it to New England Propeller (who did the overhaul in '05) with instructions to "IRAN and Reseal". That means, "Inspect and Repair As Needed (to serviceable condition) and renew all fluid seals". Once that is done, I'll happily run the prop for another 1,000 hours before sending it off for "Overhaul".

I stopped at Three Wing this morning and spoke with Tony. He'd done the maintenance run-up and found nothing noteworthy. The cylinder leakdown test had gone satisfactorily. Cylinder #2 was a bit weak at 59 psi (on a day where the minimum acceptable result was 46 psi). Tony will continue and I'll be visiting N631S every day for a while.

Friday, March 29, 2013

"Contact the Tower..."

The Air Traffic Control Tower (ATCT) at my more northerly "home 'drome", Sikorsky Memorial Airport (KBDR), is scheduled to close on or about the 5th of May due to the funding cut-off known as "sequestration". The closure seems to be for an indeterminate period. After Cinco de Mayo, KBDR will become a non-towered field.

The tower at KBDR is one of well over 100 "contract towers" that the FAA is standing down to save money. Arguably, some towers that are to be closed are in fact busier than some FAA-staffed towers that will remain open. But the plug can be pulled on the contractor operations with far less bureaucratic fallout than would ensue if the jobs of Federal employees were affected. The half-dozen or so controllers at KBDR, employees of Midwest Air Traffic Control Service, Inc. who I hold in high regard, will be out of work.

It has been quite interesting to attend to the comments from various parts of the aviation community as the tower closures went from rumored to probable to inevitable. Many voices have been raised (some informed, some less so) to decry a predicted reduction in "safety" with the closing of these facilities. But a substantial part of the community is adopting a "Keep Calm and Carry On" attitude. In truth, pilots have always known how to operate around non-towered fields without undue risk and I am quite confident that operations will continue without a sudden epidemic of bent aluminum.

There are, however, two issues raised by the sequestration-related tower closures that have not been widely discussed. One is short term and operational in nature, the other is long term and can change the nature of the system in which we fly.

The tower at an airport like Sikorsky Memorial has two main functions that affect me in my comings and goings. The first and most important is to "control" local traffic, both on the ground and airborne, so as to maintain safe, orderly and expeditious use of the available runways. Traffic at a fairly low-volume field like KBDR, operating under non-towered field procedures, will no doubt become somewhat less expeditious, slightly less orderly, and (I contend) just about as safe. Pilots arriving and departing VFR (i.e., under Visual Flight Rules) should hardly notice the difference. But there may be a significant impact on pilots operating IFR (under Instrument Flight Rules) as N631S and I usually do, absent the tower's other normal function.

The control tower provides a link between the departing or arriving IFR pilot and Approach Control. The tower controller delivers your IFR clearance, obtains your release and sends you on your way. On arrival, it's the tower that cancels your IFR flight plan. Now, IFR pilots will need to interface directly with the TRACON to accomplish these things.

There is no reason that any of this needs to be a big deal. I do it routinely, interacting with Potomac Consolidated TRACON when departing or arriving at KVKX in the DC area. But – the TRACON's are going to be having some sequestration effects of their own. It's reported that controllers will be getting an unpaid day off per payroll period and that translates into fewer controllers on station and higher workloads for the ones on duty. So I expect that departing KBDR on a busy Friday afternoon in the summer when convective weather is rumbling around the area could become difficult. Problems picking up clearances and long waits for release may become the norm. I hope that a few weeks will suffice for development of "work-arounds" and for all the players to adapt.

The second issue that needs some discussion concerns the length of the tower shutdown. There is, I believe, a very significant probability that for many of the closing towers – and I think KBDR is one – the closure may be permanent. Here's the problem:

The chart above (you can click on it to make it readable) depicts annual airport operations at KBDR from 1994 (the year I got my Private Pilot's license) through 2012 with a trend line extending out another five years. The data is from the FAA's Air Traffic Activity System. In 1995 the field had 114,247 operations. Last year it had 61,911, a decline of 45.8%, and the trend line suggests a further drop to about 45,000 by 2017. There is some variability in the data but the long term trend is unmistakable...traffic at KBDR is going away.

I remember a sunny Sunday afternoon in 1995, when I was flying a Cessna 172N (N6583D, I believe) rented from the old Bridgeport Air Center. I'd departed KBDR, flown around for a while just enjoying the delightful day, done a couple of touch & go's at Oxford, then returned to Bridgeport. Arriving there, I found myself one of eight airplanes in the traffic pattern, a number of them students in closed traffic exhibiting shaky pattern discipline (not that I was so great at that point). The tower controller was holding on by his fingernails – but he was hanging on. Making right traffic for Runway 29, I was asked for a left 270 for spacing. An airplane arriving after me was told, "Remain clear of the Class Delta". I soon got my turn at the runway and was grateful for it.

That's the kind of day when you need a tower. Those kinds of days don't happen any more. In 1994 there were three active flight schools at KBDR. Today there is one (plus a few independent instructors). I really don't recall the last time there were more than two airplanes in the pattern while I was flying. The bottom line is that even after the budgetary kerfuffle that led to sequestration is over, it may be very difficult to justify re-opening the tower at KBDR given current traffic levels. And many more of the towers being closed this spring are likely to be in a similar situation. As a result, the once ubiquitous Class D tower may become a rarity.

After my next arrival at KBDR, N631S is going in for this year's Annual Inspection, which will take a couple of weeks. So it's quite possible that the next time I hear New York TRACON say, "Bridgeport is at your 12 o'clock, seven miles. Radar service terminated, contact Bridgeport tower on 120.9"...it will be the last time.

Saturday, February 23, 2013

Book Review: "The Dog Stars" by Peter Heller

The post-apocalyptic novel has been with us at least since Mary Shelley published The Last Man in 1826. The basic model is familiar – the author invokes some catastrophe to kill off the vast majority of humanity and then follows the lone (or few) protagonist(s) through the effort to survive and build a new future in a hostile world.

The nature of the precipitating catastrophe is rather beside the point. Writers have called upon plague, astronomical disaster, alien invasion and thermonuclear holocaust (recently, zombies have been popular). The point is what happens afterward.

For most of the latter half of the last century, nuclear war was the preferred disaster (see Nevil Shute's On the Beach, Pat Frank's Alas, Babylon, and Walter M. Miller, Jr.'s A Canticle for Leibowitz). Of late, however, the pendulum seems to have swung back to favor pestilence. Which brings us to Peter Heller's recent work, The Dog Stars.

Fine, you say, ...but what has this got to do with aviation? Well, the connection involves one of the important supporting characters in the story. In this tale, a virulent strain of influenza has carried off almost all of the population. The protagonist, a survivor who goes by the name Hig, lives at an airfield. He has a friend, and a dog, and an airplane. That would be the Beast.

"I hand pump the 100 low lead aviation gas out of the old airport tank when the sun is not shining and I have the truck too that was making the fuel delivery. More fuel than the Beast can burn in my lifetime if I keep my sorties local, which I plan to, I have to. She's a small plane, a 1956 Cessna 182, really a beaut. Cream and blue. I'm figuring I'm dead before the Beast gives up the final ghost."

The friend is the aptly named Bangley, who is testy and a bit of an odd duck, but who has the redeeming virtue of being a crack shot and well equipped with automatic weapons and things that go boom. Hig and the Beast patrol their perimeter from the air and Bangley sees to security. Hig's other job is to go up to the hills with his dog Jasper and bring back the occasional deer or some carp (the trout being gone since the streams warmed up).

Hig's life is pretty stable, but his focus is on the things that are gone. The things of Before. He holds on tenaciously to the connections with Before.

But of course, the connections break and Hig comes adrift. He has to go off in search of new moorings. It's the Beast that enables him to do this, taking him to unexpected places where unforeseeable events turn him away from the past and toward the future. And when he has to get himself (and newly met others) out of a tight spot he achieves his goal using his own skill and the Beast's reliability and horsepower. (Incidentally, this occurs in one of the best accounts of a back-country short field takeoff that you'd ever care to read. I couldn't breathe 'til they cleared the trees!)

At the end of the tale, Hig still has a precarious existence, albeit with a couple more people to be close to. But he's shed his longing for the past and found reasons to hope for a better future. And he's still flying.

The Dog Stars would be a fine read even without the airplane. Peter Heller writes vividly and packs a great deal of meaning into few words. The reader comes to know Hig quite well and to care what happens to him. And for a pilot, the aviation related scenes are icing on the cake. The author presents them using correct terminology but never lapsing into jargon that might put off the groundling reader. And very few errors crept in during the editing process (though I did wince when an oil change involved a case of "50 straight weight Arrowshell").

We learn that the Beast wears registration N6333A which, by coincidence, is also the N-number of a '56 Skylane owned by Peter C. Heller of Denver, CO. So Hig comes by his love of flight legitimately. I recommend Mr. Heller's book to you, and I hope he and '33 Alpha enjoy many years of flying together.

Thursday, February 21, 2013

My '709 Drive

Those of you that visit here regularly will recall that early in January I was involved in an incident wherein N631S struck and slightly damaged another aircraft (described in this post). At the time I had a cordial conversation with Dean, the assigned FAA Inspector who was opening a file on the incident.

A couple of weeks later, I received a letter from the FAA, sent via Certified Mail, inviting me to participate in a re-examination of my qualifications to hold a pilot's certificate. The re-examination would focus (logically enough) on taxiing and ground operations. I had 10 days to get back to them to schedule the event.

This sort of re-examination is conducted under authority granted to the Administrator by 49 USC 44709(a), which says:
Reinspection and Reexamination — The Administrator of the Federal Aviation Administration may reinspect at any time a civil aircraft, aircraft engine, propeller, appliance, design organization, production certificate holder, air navigation facility, or air agency, or reexamine an airman holding a certificate issued under section 44703 of this title.

The re-examination is usually referred to as "a '709 ride" (from the referenced USC section). In my case, since we would only be dealing with ground operations, it would be more like a '709 drive.

I called Dean at his office at the Windsor Locks Flight Standards District Office (FSDO), located at Bradley International Airport (KBDL). After a couple of false starts related to our conflicting schedules we agreed that N631S and I would meet him today at the Hartford-Brainard airport (KHFD). We'd talk for a while, then I'd taxi around a bit while he watched. He'd be evaluating my competence based on the relevant sections of the Practical Test Standard for Private Pilots.

The morning dawned clear but quite breezy. I took a look at the winds at Brainard and was less than thrilled with what I saw:
 
KHFD 211353Z 29013G23KT 10SM CLR M02/M13 A2992 RMK AO2 SLP131 T10221128
The runway at KHFD is oriented 2 - 20, so a wind from 290 is a direct crosswind. At 13 knots gusting to 23 it was fairly sporty already and I suspected that it could easily get more intense as the day went on. I sent Dean an e-mail saying I looked forward to meeting him and commenting on the winds. Very shortly, he called me and asked if I'd like to meet instead at Bradley (KBDL). Bradley has a Runway 33 that would make the wind perfectly manageable so I accepted immediately.

N631S and I departed Sikorsky Memorial (KBDR) at about noon and had a bumpy forty minute flight up to KBDL. Bradley Approach sequenced us into Runway 33 behind a Delta MD-80. The wind was 31020G26KT, and did not present any problem.

I parked on the ramp at the FSDO and announced myself. Dean came down to collect me and escorted me to a conference room. We sat and talked about my incident and about risk-management in ground operations (a subject to which I have given considerable thought of late). He focused strongly on avoidance of runway incursions – still clearly an FAA 'hot button'. While this was going on, one of Dean's colleagues went out and ramp-checked N631S. He joined us and said the only question he had concerned the cable connecting the portable Garmin gps396 with the panel-mounted GNS-530W. It supplies both 5.0v power and flight-plan data to the portable and he wants to see the log entry supporting the installation. Of course, the airplane's logs are home in Virginia so I am on the hook to dig out the pertinent page and send it to Dean.

After about 45 minutes, Dean said, "OK, let's go out and taxi around."

We went out to N631S, started the engine, and taxied over to the Tac-Air FBO ramp. There, we went through the motions of parking. Dean indicated a few spots and said "Would you park there?" or "Could you pull straight in to that spot", or "How could we best get to that spot over there?". I said 'Yes' or 'No' or 'NO WAY!' in what seem to have been all the right places and after about 15 minutes we taxied back to the FSDO ramp. Dean said he'd send me a letter next week attesting to my competence and continued qualification to hold a Private Pilot's Certificate and I was free to go. N631S and I had a somewhat bumpy but really quick flight back to Bridgeport and it was done.

I can't say it was a pleasure, but the experience was minimally painful. Dean, the FAA Inspector, was cordial and totally professional at every turn. I know all of the jokes about the FAA but none of them applied here. I drew one of the "good guys".

Wednesday, February 6, 2013

Book Review: "A Higher Call" by Adam Makos

Charlie Brown was perfectly clear about the situation. When the young journalist, having "heard a story", sought him out for an interview, he said, "If you really want to learn the whole story, learn about Franz Stigler first...in this story, I'm just a character – Franz Stigler is the real hero."

Author Adam Makos had no choice but to seek out Franz Stigler, living in pleasant retirement in the Vancouver area, to learn what happened on 20 December 1943, in the skies near Bremen. There, the life arcs of two warrior-aviators intersected for about 10 minutes. If someone had described to their earlier selves what transpired during that brief encounter, they would each have reacted with disbelief. But as they moved on along separate paths – destined to intersect again nearly 50 years later – they knew their lives had changed forever.

On that morning over Germany, Charlie Brown was the 21 year-old pilot of a terribly damaged B-17. He was embarked on a first combat mission that had become deadly and terrifying. Franz Stigler was, at 28 years of age, an elite Luftwaffe veteran of hundreds of missions in the Bf 109. He was fighting to defend his homeland and his countrymen from the onslaught of the American bombers. Both of them had already on that day displayed heroism in battle. But when they met, there was nothing left for Charlie to do. Keeping his crew alive and his airplane aloft to that point had exhausted his resources. He could only watch and wait.

As he approached the straggling bomber, it fell to Franz Stigler to make a choice. The action required by the call of duty was clear. He should attack and destroy the wounded B-17. But perhaps there was a higher call, requiring forbearance. Perhaps honor and humanity required staying the hand of destruction. It was time to decide. Act, in answer to the call of duty...or act not, in answer to the higher call. The sum of all his experiences led to the choice that few would have predicted and few would understand. "This will be no victory for me, Franz decided. I will not have this on my conscience for the rest of my life."

How did an elite warrior, the product of a proud martial tradition, come to make this choice? This is perhaps the most fascinating question raised by the episode and the author sets out to answer it. This requires a thorough study of Franz Stigler's life, and Makos provides it. We learn where Franz came from, how his love affair with the sky originated, how his sense of honor evolved.

We're taken back to Bavaria in the late 1920's where young Franz begins to fly, under the auspices of a local glider club sponsored by his father, the elder Franz (who had been a scout pilot in the Great War) and Father Josef, a local Catholic priest who had been a fighter pilot in that war. Following in the footsteps of his elder brother August, Franz flew a simple Zögling ("Pupil") glider that was launched using a bungee cord, from the side of a hill. It was said that, "[b]ecause training was conducted solely by solo flight the aircraft had to be very easy to fly and also easy to repair." This principal was demonstrated by young Franz, who pranged the club's glider on his first flight, but soon became proficient.

Franz was urged by his devoutly Catholic mother to enter the Seminary, but Father Josef, the fighter pilot, glider club sponsor and family friend, urged him to follow his dream of flying. He took advantage of government training programs and found himself, in the late 1930's, flying Ju 52's for Lufthansa. In due course, he was transferred to the newly emerging Luftwaffe and set to work as an instructor. One of the students he found himself responsible for was his elder brother August.

While Franz continued to instruct, August went on to serve as a night fighter-bomber pilot flying Ju 88's from France against England. It was late in 1940 that Franz learned that August had been killed in an accident at night, on takeoff. The loss of his brother moved Franz to seek a transfer to fighters. There followed 18 months of preparation and training, until in the spring of 1942 Franz Stigler arrived in North Africa to serve as a fighter pilot in Jagdgeschwader 27 (JG 27).

JG 27 was a famous unit, the home of the great ace, Hans-Joachim Marseille. Franz was in good company. He was assigned to the squadron of Leutnant Gustav Rödel. His new commander quickly gave him a lesson that would have a profound influence on him:

"Every single time you go up, you'll be outnumbered. Those odds may make a man want to fight dirty to survive. But let what I'm about to say to you act as a warning. Honor is everything here. What will you do, Stigler, for instance, if you find your enemy floating in a parachute?"

"I guess I've never thought that far ahead yet," Franz said.

"If I ever see or hear of you shooting at a man in a parachute," Rödel said, "I will shoot you down myself. You follow the rules of war for you, not for your enemy. You fight by the rules to keep your humanity."

As the author recounts in some detail, Franz flew and fought under Rödel's leadership in Africa for five months. His unit was then transferred to Sicily, where he continued to fly and fight for another ten months. During this period he met Adolf "Dolfo" Galland, the famous General of the Fighters. He managed to impress Galland with his views on tactics for effective attacks on heavy bombers. This relationship would be important to Franz' future more than once in the coming years.

In mid-1943 the strategic bombing campaigns of the Allied Air Forces were beginning to have real effects on the German homeland. Fighter units, including JG 27, were transferred back to Germany to engage in homeland defense. The stage was being set for an epic confrontation.

Meanwhile, Charlie Brown and his crew were readying themselves to join the fight. By the fall of 1943 they had joined the 379th Bomb Group of the mighty 8th Air Force at RAF Kimbolton. They'd been assigned a veteran B-17F named Ye Olde Pub.

On 20 December the 379th took off for a raid on Bremen. Ye Olde Pub, with a rookie crew, was assigned the trailing position, known as "Purple Heart Corner". The slot would soon once again earn its name.

On the approach to Bremen, before reaching the point where its load of bombs would be dropped, Ye Olde Pub was hit by flak. The Number 2 engine was knocked out, and the bomber's Plexiglas nose was shattered. Charlie pressed on. Another burst of flak damaged the Number 4 engine just before the bombardier released Ye Olde Pub's deadly load. As the group turned away from the target, Ye Olde Pub with one engine out, one producing partial power, and drag increased by the damage to the nose slowed and began to fall behind the formation. Soon, a group of eight Fw 190 fighters focused their undivided attention on Ye Olde Pub.

The author's chapter describing the fight between the B-17 and the Focke-Wulf's is intense and thrilling. It describes Charlie's desperate maneuvers, the crew's efforts to fight back, and the horrific damage inflicted by the fighters. In the end, the bomber rolled into an inverted spin when the pilots, their oxygen system disabled, blacked out. The Fw 190's – either out of ammunition or certain that their job was done – moved on.

About 10,000 feet above ground, Charlie awoke. He started to try to recover the airplane from its spin, and barely succeeded in regaining level flight below 2,000 feet.

The damage and casualty reports were frightening. The tail gunner, Sgt. Hugh 'Ecky' Eckenrode, was dead. Two other crew members were badly wounded. The airplane was riddled with holes and many systems were destroyed or compromised. They were staggering toward the coast, at low altitude, on 2½ engines.

Just then, Franz Stigler was on the ground at a nearby field while the ground crew rearmed and refueled his '109. He heard an approaching aircraft and looked up in amazement as a damaged B-17 flew westbound, almost directly over the field. Franz wasted no time in taking off to give chase.

Charlie struggled to get Ye Olde Pub to climb to 2,000 feet. He passed the word that anyone who wanted to bail out had his permission. No one took him up on it. And behind them, a Bf 109 piloted by one of the Luftwaffe's best pilots was closing in.

Franz closed on the B-17's tail, knowing that he needed to get close to be sure his attack would be effective. But when he closed in, he saw the damage to the bomber's tail section. He saw that the tail-gunner's weapons were disabled. He got close enough to to see the wind-driven streams of 'Ecky' Eckenrode's blood.

Franz slid his '109 to the right and moved forward along the right side of the B-17. Through a gaping hole in the fuselage he saw crew-members, not at their stations, but huddled together and caring for the wounded.

Franz decided then, that on this day he was not going to kill these men. He pulled even with the cockpit and slid over to the bomber's left side. He pointed to the north, repeatedly and mouthed "Sweden...Sweden", in an effort to get Charlie to turn toward the nearest haven. He was certain that if the B-17 tried to cross the North Sea and reach England it would crash and all aboard would be killed. Charlie Brown had no idea what he was saying.

Finally, over the sea, Franz gave up, saluted Charlie, and peeled away to return to Germany. Only then did he consider that if anyone had seen what he had done he'd certainly be court martialed.

Ye Olde Pub staggered across the North Sea at minimum altitude. The crew jettisoned everything they could to lighten the aircraft, but the B-17 was having difficulty maintaining altitude. Soon, their height above the sea was measured in hundreds, rather than thousands of feet.

As they approached the English coast a pair of P-47 Thunderbolt fighters joined them. They exchanged hand signals (the radios were out) and raced ahead. Charlie followed. As Ye Olde Pub crossed the English coastline, Charlie searched for a farmer's field to use as a landing site of last resort. Then he saw the two P-47's ahead, circling at 1,000 feet. He turned toward them and soon saw the runway they had found for him.

Minutes later, Charlie Brown settled Ye Olde Pub onto the runway at RAF Seething, home to the 448th Bomb Group. One of his crewmen was dead; two were injured severely enough that they would probably not have survived a bailout. The airplane would not go to war again.

The intelligence officers debriefed Charlie and he told them the whole story, including the odd behavior of the Bf 109 that had escorted them off the coast. The word came down to forget that had happened. Never mention it to anyone. It was unacceptable to say that a 'Nazi' had behaved with honor and chivalry.

Franz Stigler never experienced any repercussions from the incident with the B-17. He fought on with JG 27 through the first 10 months of 1944, in Germany and Jugoslavia. Then on 26 October 1944 a B-17 gunner's .50 cal. round, having spent nearly all of its energy passing through the canopy of Franz' Bf 109, struck him in the forehead. Amazingly, he lived. Not so amazingly, he suffered symptoms of brain trauma and was grounded by the flight surgeon. Franz was, for the time being, out of the war.

After a brief stay at a R & R facility, Franz pestered his group commander, still Gustav Rödel, for something useful to do, and Rödel was able to get him a slot at the jet school near the Messerschmitt factory in Augsburg. There he took to the Me 262 like a duck to water. He was kept on as an instructor, but ran afoul of a political officer and found himself released with no new assignment. That's when he remembered 'Dolfo' Galland.

The word was around. Galland had run badly afoul of Reichsmarschall Herman Goering and been sacked as General of the Fighters. But Goering had allowed him to form a new fighter group, Jagdverband 44 (JV 44), flying Me 262's. It was said that Goering couldn't arrest the famous and popular Galland but could, perhaps, arrange for him to die in combat. Franz called Galland and asked if he could join JV 44.

Galland told Franz that he'd be glad to have him as long as he brought a jet with him. So Franz went to the factory, stole a jet (details, quite entertainingly, in the book) and reported to Galland's group.

JV 44 may have been the most amazing unit in the history of air warfare. All of the pilots were considered experten. Nearly all were there because they had somehow run afoul of the Nazi political system. All of them were committed to defending the German homeland.

None of these men were found culpable for the crimes of the Nazi regime. Many of them would later serve with great distinction in the Air Force of the Federal Republic of Germany. But in 1945, they were still the enemy, fighting on for honor in a lost cause.

And of course, the war ended. Franz struggled to survive in the economic disaster that was post-war Germany. In 1953 he emigrated to Vancouver, Canada and became successful in business. Charlie Brown went to college, rejoined the Air Force and retired in 1965, then worked for the State Department before retiring for good in the early 1970's. But 20 December 1943 always stayed with him. At the urging of friends, he tried to place a query in a newsletter distributed to veteran Luftwaffe pilots. The editor turned him down, so he appealed to Dolfo Galland...who used his influence to ensure that the query was published.

In January 1990, in Vancouver, Franz Stigler collected his mail including the Jagerblatt newsletter. Minutes later, he was calling for his wife to come and see what he'd read. And he quickly wrote a letter.

Charlie Brown and Franz Stigler soon met and became the closest of friends. They referred to each other as 'brothers', and for many years they enjoyed a close relationship based on a bond that no one else could fully understand. Franz and Charlie both "went West" in 2008, six months apart. Franz' obituary said that he was survived by his brother, Charles Brown.

In this book, Adam Makos does a good job of describing the experiences that brought Franz and Charlie to their fateful encounter near Bremen. We're left with complete understanding of what happened. But I found myself wishing that the author had addressed "the elephant in the room". What are we to make of this story? Actions have consequences – what were the consequences of Franz Stigler's actions on that day in 1943? By choosing not to attack Charlie Brown's B-17, Franz made it possible for him to return to England with his crew. Charlie flew another 27 bombing missions with that crew (plus replacements) and dropped over 50 tons of bombs on German targets. Viewed in accordance with the cold calculus of war, it seems clear that Franz failed, on that day, to do his duty, and thus put his country in jeopardy. The author does not seriously address this issue.

The book's only allusion to the moral ambiguity surrounding Stigler's actions is in a mention of 'Dolfo' Galland's reaction. Stigler had kept in touch with Galland after the war, and he reported that the old General of the Fighters had mixed feelings about his story. He regarded Franz' actions on that day in '43 as a dereliction of duty – and also the right thing to do.

It's left to the reader to ask whether "the cold calculus of war" is decisive. What about the calculus of humanity? Remember what Gustav Rödel said to Franz Stigler: You fight by the rules to keep your humanity. When the war is over, do we want to welcome back into our midst warriors whose every choice was guided solely by the cold calculus of war? Or do we want to embrace warriors who have fought bravely and well, and yet have retained their humanity and can say that their honor is intact?

Today's wars are harder. The choices, never easy, are even tougher. But I know that I want men like Franz Stigler making those choices for our side.

Monday, January 28, 2013

A Fairly Bad Week (Part 2 of 2)

As mentioned at the end of the previous post, the forecast on Friday morning foretold a large ridge of warm air arriving in the East, bringing rain but no risk of icing.
The low centered over Chicago at 12Z (left) was headed eastward with it's associated occluded front at roughly the speed of a runaway freight train. I could expect a long, hard slog against stiff headwinds for the westbound portions of my trip and anticipated that ceilings and visibilities would deteriorate some time after 00Z, making an early departure advisable. The computer was telling me to anticipate about 2:40 enroute so I planned on a 20Z departure to be in the DC area well before 23Z. The relevant Terminal Forecasts (TAF's) reflected these expectations:

TAF AMD KDCA 111844Z 1119/1218 21005KT P6SM -RA OVC028
FM112200 16006KT 3SM -RA OVC015 
FM120000 17006KT 2SM BR OVC008 
FM120600 00000KT 1/2SM FG OVC003 
FM121500 11003KT 5SM BR BKN015 OVC035=

TAF AMD KADW 1120/1223 16009KT 9000 -SHRA SCT010 OVC014 WS020/21042KT QNH3004INS
TEMPO 1121/1202 3200 -SHRA OVC009
BECMG 1205/1206 23006KT 3200 BR SCT010 BKN020 QNH3004INS
BECMG 1208/1209 27005KT 1600 BR FEW020 QNH3008INS
BECMG 1210/1211 28005KT 0800 FG FEW100 QNH3008INS
BECMG 1215/1216 30009KT 4800 BR FEW180 QNH3008INS
BECMG 1216/1217 32009KT 9999 NSW FEW180 QNH3008INS T17/1219Z T05/1211Z 
AMD 112023 LIMITED METWATCH 1201 TIL 1211=
The KDCA forecast issued just before my departure was calling for good visibility in light rain and light southerly winds under a 1500 foot overcast on arrival – no problem for the RNAV Rwy 6 approach into KVKX. Even if the conditions forecast to prevail after 00Z were to arrive early I'd be looking at two miles visibility under an 800 foot overcast – still acceptable. The weather wasn't forecast to get really bad until 06Z.

As a cross-check, I looked at the forecast prepared by the Air Force met watch for Andrews AFB. They were advertising the same light southerly winds, with a couple of miles visibility under a 1400 foot ceiling through 05Z with brief periods of 1/2 mile visibility and 900 foot ceiling. Also not too bad. One notable feature for the Andrews forecast was the "WS020/21042KT" group. That's a wind shear warning projecting wind at 2000 feet from 210 degrees at 42 knots. Not in itself a problem but worthy of note.

N631S and I were off the ground within minutes of 20Z and on our way. The clearance routed us from KBDR westward to Sparta VOR (SAX) then south to Solberg (SBJ), west again to East Texas (ETX) then south via Lancaster (LRP) and Baltimore (BAL) toward home. As expected, progress to the west was very slow with ground speeds between 85 and 95 knots (while true airspeed was about 140 knots). This implied a headwind component of about 45 to 50 knots.

About an hour into the flight I checked the weather at Washington National and didn't like what I saw:

SPECI KDCA 112116Z 22003KT 1 3/4SM -DZ BR OVC008 06/05 A3020 RMK AO2 P0000=

That 800 foot ceiling was three hours early and that suggested conditions in the DC area were deteriorating more quickly than forecast. This was not good. If the trend continued I might be unable to land at KVKX and have to divert to an alternate. My filed alternate was Manassas (KHEF), which had been legal when I filed. But Manassas was to the west, "up-weather", and if DCA was going down the tubes HEF would probably be at least as bad.

There was nothing for it but to press on and see what I'd have to deal with in the destination area. And as expected, N631S and I passed Baltimore and were heading south to the Nottingham VOR (OTT) at about 2140Z. That's about when the Potomac Approach controller asked, "Skylane 31 Sierra, what are your intentions?" At that point the weather looked grim:

SPECI KDCA 112142Z 20003KT 1SM R01/P6000FT -RA BR OVC006
07/05 A3018 RMK AO2 DZE39RAB39 P0000=

SPECI KADW 112151Z AUTO 00000KT 1SM R01L/P6000FT -DZ BR VV007
06/05 A3016 RMK AO2 DZB2145 SLP216

METAR KHEF 112155Z 17003KT 3/4SM BR OVC003 06/06 A3015=

The reports for DCA and ADW implied marginal conditions at best for VKX. The minima for the RNAV Rwy 6 approach at VKX are 680-1 (i.e., the approach requires 1 statute mile flight visibility and the Decision Height is 680 feet AGL). The METARs for DCA and ADW were not encouraging and my filed alternate (HEF) was looking none too good, even for an ILS approach.

I responded to the controller's query with: "I guess 31 Sierra's intentions are to try the RNAV 6 approach at VKX."

He replied, "A Pilatus just tried it and missed and he diverted to Easton. There's a Colombia 350 inbound for the approach. He'll get there before you; I'll keep you informed on how he makes out."

I thanked the controller and continued to motor on – slowly – toward OTT. Before too long, the controller was back. He told me, "31 Sierra, that Colombia missed at VKX and has diverted to Manassas. What do you want to do?"

I thought about it for a few seconds. First, two aircraft had missed at VKX, and the weather wasn't going to get better. I saw absolutely no point in trying to get in there. But where to go? I asked the controller, "Approach, 31 Sierra, can you say the weather at Manassas?"

He answered quickly, "300 and 3/4 in mist, wind 170 at 3."

That was doable but not great – especially if the trend was worsening. I asked, "Approach, 31 Sierra, could you say current conditions at Easton?"

The reply, after a few seconds, was, "Easton is reporting 7 miles, 1300 overcast, wind calm."

Sold! I said, "Approach, 31 Sierra would like to divert to Easton."

The immediate reply was, "November 631 Sierra is cleared to the Easton airport via radar vectors. Turn left to 050 and maintain 3,000 feet." A moment later, "31 Sierra, you can expect the ILS for Runway 4 at Easton."

I'd already descended to 3,000 feet on the way south from Baltimore, so I turned to the northeast and bid VKX farewell for the evening. As I rolled out on the 050 heading my groundspeed went from the low 90's to 173 knots. Remember that wind shear group in the Andrews TAF? A 40+ knot tailwind at 2,000 feet was going to make for a sporty ILS approach.

In what seemed like no time at all the controller said, "Skylane 31 Sierra, turn right to 080, descend and maintain 2,000 until intercepting the localizer. Cleared ILS 4 approach at Easton."

I acknowledged the approach clearance and got down to 2,000 feet as the localizer needle centered. I configured 631S for the ILS...manifold pressure 15", 10 flaps, indicated airspeed 90 or 100 knots, pitch for about 500 feet per minute descent...and watched as the glideslope indicator plunged toward the bottom of the instrument. With the tailwind, my ground speed was still 135 knots. I reduced the power further and pitched for 1,000 fpm descent and the glideslope began to creep back up.

I was still a couple dots high on the glide slope when we broke out at about 1,000 feet. There was that beautiful long runway at KESN, just where it belonged. I pitched up to slow to full flap extension speed and deployed all of the flaps and then did one of those "helicopter" descents that the 182 is so good at. We flared and touched down on the 1,000 foot touchdown zone markings. The tower asked where I was parking and I told them I needed an FBO and was unfamiliar. They advised me to turn left at the end of the runway onto Maryland Air's ramp.

I found the ramp, shut down, and walked over to the FBO – which proved to be locked up tight. So I returned to '31S and called the tower controller on the radio. Did he know of anyone that could help a poor wandering pilot on a dismal night? He said he'd call the Maryland Air after-hours number and see if they could help. Very soon he came back and told me they'd said to stand by, someone would be there soon.

In about 15 minutes, Bob from Maryland Air showed up to rescue me. He'd interrupted his Friday evening to open up the FBO and issue me a rental car for the hour-and-a-half drive home. And so I was on my way, soon to be done with a long and trying week.

My friend Sarah, who's a controller at Potomac TRACON, said in a comment to the last post that, "I was working approach that day and worked the first guy into (and right back out of) VKX. I almost got to say hi to you, but then watched you fly off my scope. Good call! That weather was no joke. Can't wait to hear how it all ended... :)"

Well, Sarah, there you have it.

Sunday, January 13, 2013

A Fairly Bad Week (Part 1 of 2)

Last week began and ended with flights that I will not cherish as warm and glowing memories of my aviation experience. And the first is going to be rather painful to discuss here.

Monday began with a disarmingly uneventful flight from the DC area up to Sikorsky Memorial Airport (KBDR) in Connecticut. The weather was clear and dry at about 0915 local time, when N631S and I landed on Runway 29 and were cleared to taxi to parking via taxiways Hotel and Alpha.

Approaching the tie-down area I took note that a rather large aircraft, a Piper Navajo, was parked in the last space of the row behind my assigned spot. That space is usually occupied by an Archer and so I thought that as I maneuvered N631S into its tie-down I'd have to be very careful to avoid the big Piper's wing.

Well, I succeeded after a fashion. As I turned 45 degrees to the right exiting the taxiway I carefully monitored the position of my wingtip relative to the Piper. Once sure that it was clear, I started to swing the nose to the left to align with the tie-down centerline. That's when I heard the sound of aluminum striking aluminum and felt '31S decelerate (from 3 or 4 mph) and yaw a bit to the right.

What I saw when I looked to the right was dismaying. I had completely disregarded the Piper's high, wide-span tailplane and my wingtip had struck and damaged the larger plane's elevator. Sick at heart, I shut down and got out to examine the extent of the damage. Pretty quickly, I had company.

Tony came out from Three Wing's maintenance hangar, looked up at the sad sight, and called the folks that own the Navajo. Meanwhile, I was calling Dan Schrager, of The Aviation Insurance Agency. He asked the basic questions and said he'd get back to me soon.

It appeared that N631S had come through the incident in pretty good shape. I couldn't see any significant damage to the wing. The Piper had been less lucky. The right elevator was clearly toast, and worse, the outer third of the horizontal stabilizer was bent down at a significant angle. It looked like I'd made a rather costly mistake.

Tony said they'd wait for the Piper's owners before separating the aircraft so I went to my office, having said I'd return if and when I was needed. That happened about two hours later when I received a call saying that the FAA was headed to the airport and had asked that I be there. So I hustled back.

The Piper Navajo that I'd damaged was in Part 135 service for an air charter operator, 'Fly the Whale'. As a "for hire" operator, they had to report the incident to the FAA and the FAA had to do an investigation. If the Piper had been a Part 91 aircraft like N631S, no FAA involvement would have been required.

While waiting, I met Andy, the CEO of 'Fly the Whale'. I apologized for the inconvenience I'd caused and he was extremely understanding and a perfect gentleman about it. He was the first, but not nearly the last, to tell me that, "Hey, things happen in life, nobody got hurt, it's OK." (No...it is not OK.)

The FAA inspector arrived, surveyed the scene, and asked if we could talk. A brief, cordial and professional interview ensued. I told him exactly what had happened. He asked a few relevant questions. I gave him my contact information for follow up and he joined the growing group saying to me, "Hey, things happen in life, nobody got hurt, it's OK." (No...it is not OK.)

And, yes, I've filed my NASA ASRS form.

I also heard from the insurance company, USAIG. Rob, the adjuster on the case, had been informed of the incident by Dan, my agent. Rob said he'd e-mail me a 'Report of Hull Loss' form to get the claim started and asked me for contact information for the shop and the other involved parties. Starting then and throughout, the service provided by Rob and USAIG has been impeccable!

The next day I returned to Three Wing, where both aircraft had been moved into the maintenance hangar. The news was better than I'd expected. N631S's right wingtip had been removed and the interior of the wing structure inspected. The shallow dimple in the leading edge was nicely between ribs and purely cosmetic. The remedy would be an application of aerodynamic filler, i.e., "Bond-O" at the next annual. N631S was, meanwhile, airworthy.

The right elevator of the Navajo would, as expected, need to be replaced along with the plastic tip of the stabilizer. But the apparent bend in the outer portion of the stabilizer that had worried us proved to be entirely elastic in nature. When the load imposed by N631S was removed the stabilizer "unsprung" back into its normal configuration. A thorough inspection revealed no consequential damage. The repairs would still be rather costly (elevators for big twins aren't cheap) but not nearly as bad as had been feared. And the time out of service for the airplane would be fairly brief.

So I felt much better. Not good...but better. You see, I had hoped to get to the time when I hang up my headset for the last time without having bent an airplane. I can no longer achieve that goal. I can't dismiss the loss of situational awareness that I had on Monday – which led to the incident – as one of those "hey, stuff happens" things. I've been committing aviation for 18 years now and have logged 1,500+ hours as Pilot-in-Command...and now I have a clear understanding of an area where I need to get better.

At least N631S was good to go for Friday. The forecast was telling me that a large ridge of warm air would be arriving in the East on Friday bringing rain but no risk of icing. I could plan for a wet IFR trip home to the DC area. Which was how I got to the second part of my Fairly Bad Week (to be covered in the next post).

Monday, December 31, 2012

Happy New Year (With a Look Back)

This is the fourth year that I've used this post title on 31 December. A year ago, I looked back on 2011 in this post, and a year earlier I reviewed 2010 in this one. The retrospective for 2009 was here.

N631S finished 2012 with 4,391.8 hours on the tach, having flown 184.5 hours in 2012. That's just a bit more than the 2011 total of 175.8 hours. I made the round trip from KVKX in Maryland to KBDR in Connecticut and back 32 times this year, two fewer than last year.

I logged 10.1 hours in actual IMC (instrument meteorological conditions) this year, compared with 2011's 10.0 hours. This year's total of 16 instrument approaches flown in actual conditions is up from last year by six. Time logged as night this year was 9.3 hours, not very different from last year's 10.2.

Once again this year, N631S has been a remarkably reliable machine. Beyond the normally expected maintenance items, the things needing repair have been rather minor:

  • During the Annual Inspection in March, one of the aft roller assemblies on the pilot's side seat had to be replaced.
  • Also at Annual, the muffler was replaced with an overhauled unit.
  • To clean up a bit of 'hangar rash', the right stabilizer and elevator plastic tips were replaced. We used the opportunity to accomplish a Service Bulletin replacing some rivets in the outboard stabilizer rib with larger ones.
  • Both magnetos were serviced, and each needed some fairly significant parts renewal.
  • The baggage door latch failed and was replaced with an overhauled assembly.
  • The left wing strut upper and lower fairings, badly cracked, had to be replaced. (The ones on the right side will get done at the next annual.)
  • And finally, two steel brackets in the upper cowling (that mate with the lower cowl at the crankshaft opening) failed due to fatigue cracking and had to be replaced.

This is the 43rd post on this blog for 2012. That compares with 70 in 2011, 100 in 2010 and 128 in 2009. This obvious decline in my productivity here is the result of two things: first, my non-aviation life has gotten somewhat busier, and second, some experiences that would have been "bloggable" in the past now feel repetitive. Perhaps that's a hazard to be expected in this sort of venue. Maybe 2013 will be more interesting, but I have mixed feelings about whether that would be a Good Thing.

In closing, I wish all who may visit here a healthy, prosperous and safe 2013.

Sunday, December 30, 2012

The Coolest Thing I Got for Christmas

Now I have to show off something that I think is really neat! Our daughter-in-law Kate is a staffer on Capitol Hill, and a while ago she got herself and son Rich onto the Capitol Dome Tour, which is a very tough ticket. If you've been in the Rotunda and looked up, you've seen where the Dome Tour goes. All...the...way...up.

A prominent feature in the dome is the Frieze of American History, which encircles the dome 58 feet above the Rotunda's floor. It's a trompe l'oeil fresco about eight feet high depicting 19 historical vignettes, the last of which is The Birth of Aviation. The frieze was begun in the 1870's by Constantino Brumidi, but the last three vignettes, including The Birth of Aviation, were finished by Allyn Cox in 1953.

So, anyway...Kate got some good pictures on the tour, including several of the frieze. And when unwrapping time arrived, I found this:

The work depicts, obviously, Orville and Wilbur in their moment of triumph. The figures at left are Octave Chanute and Samuel P. Langley (Leonardo da Vinci is out-of-frame left). Kate snapped the shutter, and Rich cropped, printed and framed the result. And I'm as thrilled as I can be.

Monday, November 19, 2012

Waiting Out the Fog

Last Monday I was concerned about whether N631S and I would be able to land at Bridgeport's Sikorsky Memorial Airport at the end of our northbound flight. Just over a week earlier the field had been extensively flooded by the surge from Hurricane Sandy. The ILS equipment and the VOR were damaged and out of service. The forecast on offer when I got up didn't look too bad but just a bit worse and the ceiling could go below the minimums for the available RNAV approaches – around 400 feet.

TAF AMD KBDR 120840Z 1209/1306 00000KT 2SM BR BKN007
       TEMPO 1209/1212 1SM BR 
       FM121400 20006KT 5SM HZ SCT015 BKN025 
       FM121600 20010G17KT P6SM SCT025 BKN100 
       FM130300 20012KT 5SM BR BKN025=
Winds calm, visibility one to two miles in mist with a broken 700 foot ceiling; forecast to improve at about my ETA to five miles in haze with scattered clouds at 1,500 and the ceiling up to 2,500 feet. Really, a good enough forecast to depart on. I checked the current conditions at KBDR just before leaving.

SPECI KBDR 121147Z 19004KT 1 3/4SM BR OVC005 11/11 A3047=
A mile and three quarters with a 500 foot ceiling. Consistent with the forecast, and good enough for the RNAV Runway 24 approach.

About 45 minutes after takeoff from KVKX I figured I'd better have a look at how conditions were developing up in Connecticut. So I checked the METAR for KBDR:


SPECI KBDR 121233Z 21006KT 3/4SM BR OVC003 12/11 A3047=
That's not so good. Both the visibility and ceiling had gone below the minimums for the RNAV approach. I hoped that this was just a passing bit of dense weather and that conditions would return to something more in line with the forecast. But hope is not a plan. I looked at the reported conditions at nearby airports so that I could start planning for a diversion. New Haven, Oxford, White Plains and Danbury were little better than Bridgeport. But Hartford-Brainard didn't look bad at all.

SPECI KHFD 121239Z 19005KT 3SM BR SCT009 11/09 A3046=
Three miles in mist, scattered clouds at 900 feet. OK, that's Plan B.

I kept watch on the situation as N631S and I motored northward. We crossed over KJFK at about 1340Z and the fog was much in evidence. The weather at Hartford continued to hold up quite nicely but the reports for Bridgeport just continued to get worse. The fact that the ILS was out-of-commission was irrelevant, as Bridgeport was below minimums even for that approach. It was small consolation, but the forecast for KBDR had finally been updated to reflect foggy reality:

TAF AMD KBDR 121347Z 1214/1312 19005KT 1/4SM FG VV002
       TEMPO 1215/1216 1/2SM FG 
       FM121600 19007KT 2SM BR BKN005
       TEMPO 1216/1217 4SM BR SCT005 
       FM121700 18010KT P6SM SCT025 BKN150 
       FM130100 17007KT 5SM BR BKN015 
       FM131000 22010G18KT 4SM -SHRA BR BKN015=
Visibility of 1/4 to 1/2 mile with vertical visibility of 200 feet for the next two hours; then improving to two miles and a 500 foot broken ceiling. The METARS for KBDR and KHFD were:

METAR KBDR 121352Z 20003KT M1/4SM FG VV001 12/12 A3047=
METAR KHFD 121353Z VRB04KT 5SM BR OVC009 12/11 A3046=
So, Hartford pretty good at 5 miles and a 900 foot overcast. Bridgeport not good at all at less than a 1/4 mile in fog with vertical visibility of 100 feet. I was handed off to the final approach sector controller and checked in with "New York Approach, Skylane 631 Sierra level 3,000, Sierra at Bridgeport, is anyone getting in over there?"

The controller answered, "Skylane 631 Sierra, Bridgeport altimeter 30.46, and no, a Pilatus just tried it and went missed. Whaddya want to do?"

In a triumph of wishful thinking over reality, I said, "Approach, 31 Sierra would like to go to BAYYS and do a couple turns in the hold, and see if things improve at Bridgeport."

"Skylane 31 Sierra, maintain 3000, cleared direct BAYYS intersection, hold as published."

BAYYS intersection is an initial approach fix for the RNAV Runway 24 approach into KBDR. I entered the hold there and pulled the power back. Perhaps in 15 or 20 minutes there would be some sign of improvement at KBDR. After a few turns around the hold, I checked with Bridgeport tower, who assured me that conditions were staying consistently bad. So I went back to New York Approach.

"Approach, Skylane 31 Sierra would like to divert to Hartford."

"31 Sierra, you're cleared to the Hartford-Brainard airport via present position to the Hartford VOR thence direct. Maintain 3,000."

I read that back and departed the hold to toward HFD. Very soon I was handed off to Bradley approach who cleared me direct to LAZRD, the IAF for the GPS Rwy 2 approach, circle to land Runway 20. Brainard Tower then kindly offered Runway 2 for landing with a few knots of tailwind and I taxied over to the ramp at Atlantic Aviation, where the nice folks provided a place to wait out the fog at Bridgeport.

I landed at Brainard Field a little after 10:00 AM local time and settled down to wait. The last timethat this happened I wound up leaving N631S at Oxford (KOXC) for a few days, as the fog at Bridgeport refused to dissipate. This time I was more fortunate. I watched the METARS issuing for KBDR and was happy to note some improvement.


SPECI KBDR 121541Z 00000KT 1SM BR OVC002 12/12 A3045=
SPECI KBDR 121550Z 00000KT 3SM BR BKN002 OVC006 13/13 A3044=
METAR KBDR 121552Z 00000KT 3SM BR BKN002 OVC006 13/13 A3044=
Over the course of a few minutes (from 1541Z to 1552Z) the visibility went from one mile to three and the sky condition from 200 overcast to 600 overcast. I promptly filed an IFR flight plan for a 1600Z departure KHFD to KBDR direct and went back out to N631S.

Brainard ground control gave me my clearance to KBDR via HFD thence direct, at 4,000 and I got underway for the 25 minute flight. By the time I was cleared to BAYYS for the RNAV Runway 24 approach, Bridgeport was reporting "better than 5,000 and 5." N631S and I touched down at 1625Z. Waiting out the fog had taken two and a half hours out of my day, but it was just another one of those things in aviation. Every now and then the old adage applies: "Time to spare? Go by air!"

Wednesday, October 31, 2012

It's Been Over a Week...

The seasons are changing, the weather is dynamic, and recently the flying has been somewhat entertaining. The last trip N631S and I made from Connecticut down to the DC area was a good example.

It's certainly the time of year when I start paying close attention to temeratures aloft. That Friday was a sort of a drizzly, rainy day so I wanted to see forecasts above freezing for my intended route.

Fortunately, the freezing levels forecast for the eastern Pennsylvania routing (a morning forecast at left, with a valid time of 19Z) looked quite good. The area where my flight path would be at 8000 feet MSL would have the freezing level between 9000 and 11000. That was good news, as I could focus on other things.

I was expecting to depart KBDR between 20Z and 21Z, and the TAF was forecasting basic conditions of six miles visibility in mist with a broken ceiling between 2500 and 3500 feet, but with periods of light showers and four mile visibility, ceiling at 1500.


TAF AMD KBDR 191858Z 1919/2018 15010KT P6SM SCT008 SCT015 BKN035
       TEMPO 1919/1921 4SM -SHRA BR BKN015 
       FM192100 15008KT 6SM BR SCT008 SCT015 BKN025 
       FM192300 17007KT 4SM BR SCT008 BKN015 
       FM200300 VRB04KT 4SM BR OVC015
       TEMPO 2006/2010 2SM BR BKN008 
       FM201000 VRB04KT 2SM BR BKN008 
       FM201300 24008KT P6SM SCT015
       FM201500 24010KT P6SM SKC=
The winds were going to be against me, quite vigorously. I was anticipating about 2:35 enroute, with an arrival at KVKX a bit after 23Z. But the forecast for nearby KDCA was quite benign...calling for good visibility and scattered clouds at 15000 feet. Clearly, it seemed, I was headed for better weather.
 
TAF AMD KDCA 192038Z 1921/2018 VRB12G20KT 4SM SHRA BR BKN035 
       FM192200 21005KT P6SM SCT150 
       FM200900 27006KT P6SM SCT200=
So I got on with the program and departed KBDR at 2034Z in the midst of a light rain shower. N631S climbed into the overcast and soon broke out into the clear at about 6000 feet. So far so good! The balance of the flight promised to be lengthy but uneventful.

About an hour later, things started to get a bit more interesting. The forecasts hadn't said anything about convective activity; indeed the outlook had used words like "slight" to describe the risk of thunderstorms. But there, up ahead as I approached Lancaster, was a rather nasty looking line of storms headed northeast and most certainly becoming a factor. Who ordered that? Not that I was terribly surprised. The strong southerly flow and warm air aloft indicated considerable advection of warm moist air, moving north and colliding with the cold air approaching from the west. Some atmospheric fireworks were to be expected.

The thunderstorm activity was clearly visible up ahead in the light of the setting sun. I asked Harrisburg approach for an early turn toward Baltimore to put a bit more space between N631S and the weather, and they accommodated with "After Lancaster, cleared direct Baltimore". I expected I'd need further deviations to the east as the line of cells moved north, but that was good for the time being.

By the time Harrisburg handed me and N631S off to Potomac Approach I was not liking the proximity of the weather outside the right cabin window at all. Frequent cloud to ground lightning was appearing about five miles west of my track. So, from the first Potomac Approach controller I requested a 15 degree deviation left, which he promptly approved. That vector pointed me toward Martin State (KMTN) and moved me away from the storm cells just west of Baltimore.

The scheme running through my mind as I was handed off to the next controller was "present heading for about 15 miles, then direct Nottingham (OTT)". I never got a chance to propose that, because the controller said, "Cessna 31 Sierra, fly a heading of 180 for now. We'll do that for 20 miles or so and then you can go direct Nottingham and then to VKX. That should be comfortable." I responded, "31 Sierra, that sure works for me." Have I mentioned that I love Air Traffic Controllers?

Looking ahead, I could see that there were cells in the vicinity of Andrews AFB, just north of KVKX, my destination. It would, I figured, take me about another twenty minutes to get down to a point abeam OTT and I hoped that the active weather would clear to the north by then.

The south heading took me offshore over Chesapeake Bay (not, however, beyond gliding distance from the shoreline). The sun had set, it was getting quite dark, and the sound and light show off to the west was pretty spectacular. So much for the forecast of "slight" chances for convective weather!

Approaching OTT, I asked for the RNAV Runway 6 instrument approach into KVKX. It looked as though the active cells had moved away from the airfield, but I saw no reason to chance that cloud "debris" from the cells would hamper a visual approach. And, the extra 15 minutes or so that it would take to fly the approach would give the weather some extra time to move away. Sort of a useful delaying vector.

The approach was uneventful. The weather had moved off to the north and the final approach and landing offered no problems. I taxied N631S around to the hangar and put the airplane to bed.

Only after closing the hangar doors did I notice that in the half-hour since the wheels had touched the runway a serious layer of fog had settled over KVKX. If I'd been thirty minutes later, I doubt I could have landed there. Timing is, as usual, everything.

Tuesday, October 30, 2012

Today at KBDR (cont'd)

Watching the weather forecasts this past weekend, it became quite clear that a Monday morning flight from the DC area to Bridgeport's Sikorsky Memorial Airport (KBDR) was a Bad Idea. Hurricane Sandy was on the way and so I resolved to travel a day early.

I believe I could have made the flight on Sunday afternoon, but it didn't seem quite right to be flying an airplane TO an airport that most people were trying to fly away FROM.

KBDR's airport elevation is 10 feet above Mean Sea Level. The National Weather Service was predicting a storm surge in excess of 10 feet on top of an astronomical high tide. You can do the math.

So I opted to leave N631S in its hangar at KVKX and to take AmTrak. I spent Monday morning getting my office secured and the afternoon and evening listening to Sandy's sound and fury outside my window while hoping that the power would stay on – which it did.

At noon today I drove over to KBDR to have a look at what Sandy had wrought...and came away very happy with the decision to leave N631S in Maryland.

That lake over on the other side of the airplane is a couple of feet deep and Runway 6-24 lies at the bottom of it. Yes, that's the glide slope transmitter for the ILS Rwy 6 approach over on the far side.
There stands the BDR VOR transmitter across the pond. Runway 6-24 runs left to right, about halfway from where I was standing to the VOR. You can see that the flooding continues off to the left, to where Runway 11-29 lies. It's under water as well. The airport is closed indefinitely.

The rumor mill is operational, of course. I've been told that there is no plan for dewatering the field because no one has any idea of how it could be done. The airport was built on marsh so there's no place to send the water. A couple of years ago heavy spring rains left a large pond between the two runways. It took many weeks for the water in that pond to subside.

Over on the other side of the field, a T-hangar collapsed during the height of the storm, taking out two airplanes – a fairly new Bonanza that was in the hangar and a nice Mooney that was tied down next to it. In addition, a number of airplanes are reported to have been partly immersed in the flooding...and that's salt water.

So on the plus side of the ledger, I can congratulate myself for leaving N631S in a safer location as Sandy passed through. On the minus side, I may have to arrange to use a much less convenient airport (likely Waterbury-Oxford, KOXC) for my travels.

Of course, I'm in better shape than the folks who have airplanes at KBDR. Even the ones that came through the storm in good shape are faced with a problem...they haven't got a runway.


UPDATE 11/1/2012: I spoke with the Operations office at KBDR this afternoon, and learned that to the amazement and gratification of all, the airport has re-opened.

Runway lights, REIL's, taxiway lights, PAPI's/VASI's, VOR and ILS all OTS. Night ops not advised.

Runway 11-29 is still under water but 6-24 is open, as are a useful array of taxiways. As the ops guy noted to me, the water "subsided amazingly fast. Tuesday we were calling it Lake Sikorsky and figured it was there for a while."

So...Yay!!!