HAC stands for Helicopter Aircraft Commander.  In the Navy, the HAC is responsible for the overall conduct of the mission.  Since the main character, Josh Haman, is a helicopter pilot and I qualified as HAC in several models of the H-2 and H-3, I thought in this part of my website I’d share some of my recollections about flying those helicopters.  As time goes on, I plan to add new material that is probably not in books on flying or about those helicopters you’d buy and it’ll give you more insight into the world that Josh Haman lives.

My Navy logbooks show that I have about almost nineteen hundred hours of rotary wing flight time in a variety of Navy helicopters.  About a hundred of the total is divided between the TH-57A and the UH-1D that I flew as a Student Naval Aviator in the Training Command on my way to getting my wings.  The rest is split between about nine hundred in the H-2 series and eight hundred hours in H-3s.  This doesn’t include the other three thousand plus pilot-in-command hours in a variety of fixed wing aircraft.

My Navy flight time includes lots of night, over water operations; flights over different types of terrain as well as flying in all sorts of ugly weather as a co-pilot and as a HAC. Looking back through the two books, it is just a blur of hand written entries of the:

  • Official Navy three digit number/letter flight purpose codes that describes the official purpose of the flight;
  • Total flight time and how much was in night and instrument conditions;
  • Number and type of approaches and landings; and
  • Last name of the other guy sitting next to you in the cockpit.

That’s it. In the front of every Navy log book, there are four pages of different flight purpose codes and instructions on how to assign them to a particular flight.  One – 4R8 the flight purpose code for a night instrument rescue of personal in or out of a hostile fire area – does nothing to convey what happens in the cockpit much less in the back during a combat rescue.  There’s no place for notes or brief narrative of what happened in one’s official Navy log book.  All the details are supposedly kept in separate reports, none of which I kept because they were often classified or buried in messages containing statistics, maintenance information, parts orders, etc.

The information, including the flight purpose code, fills the pages in three colors of ink – black or dark blue for daytime sorties; red for night frights, err flights; and green for combat missions.  This data is great for generating statistics but doesn’t begin to describe my experiences.  Nor can the raw numbers relate to the many hours I spent scaring the hell out of myself and crew learning how to descend to a stable, steady hover forty feet at night above water that you can’t see and knowing that if one of the engines burps or you have any significant mechanical problem, you are going to get wet and maybe drown.

And yes, the Navy still records flight time in log books.  My son who got his Navy wings in 2002 has a log book that has the same dark blue cover and gold ink that fades over time.  It looks just like mine, even with the embossed plastic strip with your last name, first initial and Social Security number stuck to the spine.

So what will follow in this section are some of my many memories of flying these machines, jogged by what is in my log books and by flipping back through the NATOPS (Naval Air Training and Operations Procedures Standardization) manuals that were issued to me that I kept over the years.  The comments that follow are mine and mine alone.  If you want me to answer specific questions about any of these helicopters, please e-mail and I’ll add stuff to this section or cover it in the blog