Grumman OV-1 Mohawk - reconnaissance & attack aircraft

The first prototype flew on April 14, 1959. Entered production in October 1959. By 1970 a total of 265 were built.

Dave Olney, e-mail, 20.02.2023

Jack �Beetle� Bailey CDR, USNR

Jack,
I remember when you joined the 73d SAC at Vung Tau. I was serving as one of the Maintenance Officers along with Maj Hank Hall and CPT Roger Norris. Basically, I had flight line responsibilities along with Tech Supply and Maintenance Test Flights. You were a newly minted WO-1 and got assigned to the Maintenance Platoon. I recall a funny incident: One of our senior captains had about 3,000 hours in the Mohawk. One night he was taxiing out and did a reverse check and the left engine quit (I believe that was the one). He restarted it and performed another reverse check with same result. He taxied back into the parking ramp. I was out flying a mission that night and you were on duty. You noticed the aircraft taxiing back in and went to check with the pilot who described the problem. As I recall, from my later conversation with the pilot, you told him the engine was quitting because of monsoon moisture and that it would clear up as the engine warmed up. Amazingly, he bought your explanation and flew the mission. When he returned from his mission, he reversed props on landing and the same engine quit. I was on duty and noticed him taxiing in with a dead engine. When he shut down, I climbed up and asked him if the engine had quit before he flew the mission and he told me it had during reverse checks. I asked him why he took the aircraft and he said, and I quote, "Warrant Officer Bailey said it was a temporary problem caused by moisture and as the engine warmed up the problem would go away." I was stunned. First because the engine was quitting because of a likely fuel control problem...a real red flag that he should have recognized and taken the backup aircraft. With the fuel control issue, the engine very well could have failed during take-off... not a good thing. Secondly, I noted your advice to him was completely off the mark. Not good... and I believe I said something to you about that. Thirdly, when he told me his story, I looked at him in total amazement because I knew he had over 3,000 hours in the Mohawk. What amazed me was he did not know much of anything about the aircraft systems.... I believe I made a sarcastic comment to that effect something like "...and you have over 3,000 hours in this aircraft!" Then I explained what the problem was and pointed out that he should have rejected the aircraft...instead of buying your explanation :). I think he was a bit chagrined, and I hoped he would take some time to learn the systems at my suggestion. I am not sure he ever did. I made a practice of becoming familiar with all of the systems on any aircraft I flew...especially the Hawk. It was a great aircraft, but it would kill you if you didn't know what you were doing or didn't know the systems...especially the critical go-no-go symptoms. In his case, the aircraft was clearly telling him..."I have a significant problem", But he didn't know enough to recognize what it was saying to him. I am happy to say that you went on to a successful career in aviation and turned out ok. But that little incident stuck in my mind for many reasons but the most important one: Really know the aircraft you are flying and its systems. Take the time to study everything you can so you know how to understand when the aircraft is talking to you. It was a good lesson for all of us and one reason we all came home.


RECONNAISSANCE & ATTACK AIRCRAFT	Virtual Aircraft Museum / USA / Grumman