Documenting Air Force History- page 2 | A&S Interview | Air & Space Magazine
(Nick Spark)

Documenting Air Force History

Ray Puffer asks, "Can anyone dispute that I had the most interesting job in the entire Air Force?"

Air & Space Magazine | Subscribe

(Continued from page 1)

And yes, it was all a great help in later life.  Even a modest flying ability gets you over the first and highest hurdle in talking with Air Force pilots and airmen—speaking the language with a natural accent.  Understanding basic aerodynamics and airmanship—being a genuine “airplane man”—made my Air Force work much more meaningful.

A & S: You say that researching and recording each of the 364 flight-related deaths over the years was a real privilege.

Puffer: After I had been working at Edwards for a few months, one of the base chaplains came by with a query.  The Memorial Chapel had a memorial plaque that had (I think it was) 64 spaces for bronze memorials, and 52 of them were filled.  The chaplains were worried—had they missed anybody?  I started researching, and the more I investigated the larger the number of flight-related deaths grew.  It took several years before I was satisfied that the list was complete.  The chaplains had, of course, been thinking of the more famous and spectacular mishaps, whereas many, many more had died in less-heralded circumstances.   During World War II, Edwards (then Muroc) had been a training base for fighter pilots and for bomber squadrons being deployed to the South Pacific.  Too many 21-year-old second lieutenants died in their P-38s, and the B-24 crews died in groups of ten or eleven.  Working with the few accident records that had survived, with coroners and sheriff department reports, and with newspaper accounts, the picture gradually built up.  There were lots and lots of forgotten accidents, and it came to be a mission to me.  Sometimes all I could do for those guys was to finalize the right spelling of their names, or to nail down an accurate middle initial.  The final tally was 363 men and one woman (a student at the Test Pilot School).  Eventually I incorporated it all into an accident roster and into a Master Chronology, an official record of major events that have taken place at Muroc/Edwards (download the list as a Word document here).  Early on, some of the old-timers working here had said that once, during WWII, three smoke pyres from separate crashes were seen at the same time.  They turned out to be right.  Two of those pilots had died and the third had successfully bailed out.

Later on I found the site of the third crash by accident.  I was out in the boonies looking over an ancient dump site and thought that one of the hummocks nearby looked almost like an impact crater.  “Let’s see…if an aircraft impacted here, it would have pushed up the soil there, and so the debris splash must be over here…”   And sure enough, I found aircraft remnants including the distinctive nose cap of a P-38 gondola.  One of the aforementioned old timers remembered having seen a ’38 go down on that heading, at about that location, so I was satisfied.  Can anyone dispute that I had the most interesting job in the entire Air Force?

Yes, every so often we would have contact with family members.   Often it happens years after an event when the relative becomes curious about the circumstances of the death.  Major Ray Popson’s sister once phoned me for information about her brother’s accident.  We corresponded for a while and she was delighted to find that the History Office at Edwards was located on Popson Avenue.  By the time of Maj.  Popson’s fatal flight in the swing-wing experimental craft, the X-5’s propensity for dangerous spins was known to the test pilots.  Nevertheless, Popson successfully continued with a stall test series, knowing the hazards.  Needless to say, the sister was delighted to learn of his bravery and dedication.   On another occasion,  Captain Joseph McConnell‘s daughter wrote.  She was nine years old when the Korean War ace died while testing an advanced version of the F-86H in January 1953.  As she put it, she felt she was finally able to come to grips with what happened to Joe and she wanted to know exactly what went wrong that day.  She visited the office and we explained how a broken elevator linkage crippled his plane, and that he elected to try to save it by flying back to the base using his elevator trim for longitudinal control.  We gave her some photos she had never seen and, at her request, one of the historians took her out to McConnell’s impact site some miles north of the base.  Seeing the crater and some shards of metal allowed her to bring it to closure.

A & S: How does the role of Air Force historian allow him to document less-than-flattering moments in history?  Did this ever prove to be awkward?

Puffer: When I was first approached by a friend about joining the Air Force History Program, I was not too enthusiastic about the idea.  As I said: “Wow!  Imagine spending a career writing squeaky-clean, sanitary, success stories for your commander’s signature!  No thanks.”  He replied “No, you’ve got the wrong idea.  We have a Public Affairs office that does that.  Your job will be to tell the truth, warts and all.”  He proved to be right.  It turned out that, to do his job, the Air Force historian has carte blanche access to every piece of paper, and to every mind, in the Air Force.   In fact, denying the historian any information he requested would be a serious breach of AF regulations.  When I asked about the “black” programs, his reply was that the Air Force had black historians too.  He turned out to be completely right.  (In fact, some time later I had an enlisted historian who got assigned to Nellis AFB.  Do you think that guy would tell his old Sea Daddy about anything going on there?  Hah!)

Occasionally someone must be reminded of the regulation but, by and large,  the historian never has any problems getting the material he needs. Once in a great while we hear: “You can’t write about that!” and a second remark is like unto the first: “Who told you about that?”  But cooperation is by far the norm.  At one base, a retiring commander wanted me to know about a politically sensitive incident that had taken  place in testing a missile.  He wouldn’t say a word about it, but he called my attention to his safe and then left the room.

No, as I would always brief the new officers: “We aren’t in the business of destroying careers, but we aren’t patsies either.”  If you cannot learn something one way, there is always another way to explore.

A & S: What interesting aviation failures did you work on (aircraft or components)?

Puffer: It is hard to think of any, because nearly all were successful in one way or another.  Designing is so advanced these days, and the engineering so meticulous, that out-and-out failures are much rarer than back in the Golden Age of flight testing.  Mishaps happen, of course, but usually something can be learned even then.  Very soon after I started to work at Edwards, the X-31 crashed just across Hwy 58 from the base.  The nearly-tailless jet was returning to base from the next-to-the-last sortie in its test series when the pilot suddenly uttered an expletive and ejected (safely).  The problem turned out to be an iced-up pitot tube that caused the plane’s computer to think that it was flying slower than it was, whereupon the pilot discovered he could no longer control it.  We have film of the bird pancaking into the ground just before an 18-wheeler passes in the foreground.  Probably there’s a truck driver out there whose buddies still don’t believe his story.

The Dark Star, a stealthy saucer-shaped autonomous UAV, was an intriguing bird.  It suddenly went out of control during liftoff on its first flight, impacted alongside the runway and immediately created what wags called the Dark Spot.  That turned out to be a software error, not foreseen but certainly easily corrected.

A & S: Were there some projects you dug into with gusto, and others you dreaded?

Puffer: You bet.  I was always much more interested in hardware and engineering than the planning and funding aspects of a program.  Researching and writing up the administrative parts of a project, as important as those things are, was always a chore.  Fortunately Dr. Jim Young, the current Chief Historian at the Flight Test Center, was always expert on resources and the decision-making processes.  I’m still much more interested in how new technology works and what it accomplishes.  There’s nothing more fascinating than finding out just how an aircraft or a missile does what it does, and why.

A & S: Did you ever work directly with pilots, and do any memories stand out?

Comment on this Story

comments powered by Disqus