Tag:

military

F-4 Vs F-8: the first “All-Weather Interceptor” vs the “Last of the Gunfighters”

by Till Daisd December 24, 2021

*“The F-4s got off to a horrid start when running into F-8s. Their reputation was dog-s**t,” Jerry B. “Devil” Houston, former F-8 driver*

One of the most versatile fighters ever constructed was the McDonnell two-place, twinjet, all-weather F-4 Phantom II, which could reach high speeds of over twice the speed of sound. It served in the first line of more Western air forces than any other jet. The F-4 became the fastest, highest-flying, and longest-range fighter in the U.S. Navy only 31 months after its maiden flight. It first flew on May 27, 1958, and entered service in 1961.

In contrast to the F-4’s “all-weather interceptor” role, many of the Phantom’s early cruises were as paired squadrons with F-8 units, which were considered “day fighter” (or, in the F-8 pilots’ opinion, “fighter”) units, as explained by Peter E. Davies in his book Gray Ghosts, U.S. Navy and Marine Corps F-4 Phantoms. When the F-4 started to outnumber the Crusader and F-8 drivers began switching to the Phantom, the antagonism between the two communities grew more intense. Before making the switch, Jerry B. “Devil” Houston, who flew Crusaders with VF-11, summed up the situation as follows:

“The F-8 stole your heart from the get-go with its beauty and, for its time, power (God, an afterburner!), but it quickly earned an ensign-killer reputation, rightly or wrongly. In the long run, that reputation contributed greatly to fighter pilot development in the Navy: only the top ten percent of pilot graduates were even considered for the F-8 pipeline—the créme de la créme. And as luck would have it a damn solid base of mid-level stick-and-throttle talent groomed the hungry youngsters into frothing-at-the-mouth tacticians. Without experiencing it, anyone would be hard-pressed to understand the aura that surrounded that early F-8 Crusader community. An ensign in F-8s took no crap from a Lieutenant Commander who flew anything else. Period.

“Among that small, but growing privileged group, anyone in the first few squadrons knew damn near exactly where they stood in the overall tactics ladder. Killing, capability meant everything: King of the Mountain, in spades. Gunnery, tactics, gunnery, tactics, just enough intercept training to get you into the sky with another victim. F-8s didn’t bomb then—hell, the plane didn’t even have hardpoints on the wings. In other words, everything funneled the best pilots and the best airplanes through a narrow training spout, and out popped the world’s best fighter pilots. They all ate, breathed, thought, and dreamed about fighting airplanes. All the time.

“The F-4, on the other hand, was an ugly, two-seated, gas-hog monster that hit the Fleet with a bunch of F3H Demon interceptor pilots. Consequently, the F-4s got off to a horrid start when running into F-8s. Their reputation was dog-s**t, and the ex-Demon drivers didn’t have a clue about changing it. So they practiced intercepts, avoided tactics, and groomed follow-on clods in their own image. All the while that lovely top ten percent advantage kept aircrew infusing the Crusader community with superior talent, which rapidly molded into long-clawed killers. The rich got richer—and even richer. Better people, better training, frightful competition. Crusader pilots didn’t have to brag; they owned the sky. So it remained, until finally, an F-8 jock got into an F-4, screaming and dragging his heels all the way. The rest is history.”

F-4 Vs F-8: the rivalry between the first

F-8 pilots and tactics, which were initially transferred from their squadrons to the Phantom, undoubtedly sped up the development of F-4 ACM training. In 1971, Jerry Houston referred to his VF-51 as a “double-barreled Crusader squadron with an extra set of eyeballs in each plane” as the unit transitioned from the F-8J to the F-4B. However, the need for ACM was recognized far earlier than then, and it certainly predated the late 1960s initiatives that gave rise to the Top Gun ACM training project.

Photo by U.S. Navy

December 24, 2021 0 comment

Cold War

The Egyptian MiG-15 pilot that perfectly ditched his stricken aircraft in Lake Bardawil

by Till Daisd December 20, 2021

written by Till Daisd

Abd el-Rahman Muharram, the pilot of the stricken MiG-15, flew exceptionally well and his subsequent ditching in the shallow waters of Lake Bardawil was a remarkable piece of airmanship

These intriguing pictures from 1956’s Suez War feature the first Egyptian Air Force (EAF) MiG-15 lost in combat. On October 31, 1956, an Israel Air Force (IAF) Mystére piloted by Capt. Yakov Nevo damaged its right wing, which was being flown by pilot Abd El-Rahman Muharram. Muharram was compelled to ditch his aircraft at Lake Bardawil, where the Israelis discovered it.

Nevo recalls: ‘A short burst from 600 yards missed, a second one from 400 yards missed, the third burst lasted until I got as close as 200 yards.’

The Story of the Egyptian MiG-15 Pilot that Perfectly Ditched his Stricken Aircraft in Lake Bardawil

The Egyptian fighter was hit in its starboard wing. As told by Tom Cooper and David Nicolle in their book Arab MiGs, Volume 1, the official Israeli account adds no further detail about the combat, unlike an extravagant later version that spoke of the Mystére pilot “flying alongside his helpless victim, so close that he could see the Egyptian’s head”.

Some unofficial versions suggest that the Israelis attacked the Egyptians “out of the sun”, while others maintain that, having been joined by two Israeli aircraft, which were out of ammunition, it was the Israelis who were bounced by Muharram and another MiG. All at least agree that the pilot of the stricken MiG-15 flew exceptionally well and that his subsequent ditching in the shallow waters of Lake Bardawil was a remarkable piece of airmanship.

The EAF pilot in question was Abd El-Rahman Muharram. Having graduated in 1955, he was among the youngest pilots in his squadron. He was close friends with Pl Off Fuad Kamal, who told Muharram’s story:

‘Abd al-Rahman Muharram escaped from the Israelis after being hit in the wing by going down to extremely low altitude, flying at “zero feet,” and making abrupt maneuvers. Before ditching in Lake Bardawil, there were no enemy aircraft close to him and the story that an Israeli flew alongside and could see the MiG pilot’s face is nonsense.’

After safely ditching in the lake and then escaping back across the Suez Canal, Abd al-Rahman Muharram remained in the EAF and rose to high rank. Much later the Israelis found the ditched MiG, salvaged the aircraft, and brought it to Israel for testing. Its photographs appear in most accounts of the 1956 War. The plane eventually ended up as a trophy in front of Hatzor AB.

Photo by Israeli Air Force

December 20, 2021 0 comment

Cold War

SR-71 crew’s encounter with Soviet MiG-31 over Barents Sea

by Till Daisd December 15, 2021

written by Till Daisd

“I assumed the Soviet MiG-31 fighter pilot would like nothing better than an opportunity to fire his missiles at an SR-71 Blackbird. Certainly, the SR-71 Blackbird would be a prized target,” Ed Yeilding, former SR-71 pilot

Major Mikhail Myagkiy, a retired Soviet MiG-31 pilot, participated in several attempts to intercept SR-71 Blackbirds during Peacetime Aerial Reconnaissance Operations Program (PAROP) missions to the Barents Sea area.

According to his logbook, Myagkiy has conducted 14 successful SR-71 intercepts:

21 August 1984

14 March 1985

18 March 1985

15 April 1985

17 July 1985

19 December 1985

20 January 1986

31 January 1986

21 February 1986

28 February 1986

1 April 1986

6 October 1986

23 December 1986

8 January 1987

SR-71 Aircrew remembers a Memorable Encounter with a Soviet MiG-31 Interceptor over the Barents Sea

Two of these intercepts were carried out by Ed Yeilding aboard an SR-71. Yeilding discusses the intercept from October 6, 1986, in Lockheed Blackbird: Beyond the Secret Missions (Revised Edition), written by Paul F. Crickmore.

As Yeilding recalls one of his “Barents missions was especially memorable because we had an encounter with a Soviet MiG-31. Because most details of Blackbird flights were classified at that time, I made no notes about the encounter, so I cannot verify the date of the encounter. I am certain that RSO Curt Osterheld was with me at the time. Curt and I had only two tours together at Mildenhall, so the encounter was between 25 Aug 1986 and 8 Oct 1986, or between 14 Apr 1987 and 7 May 1987. (I don’t remember why that second tour was only three weeks.) I think the encounter might have been the last flight of our first tour. My flight records show we had a 4.1-hour mission with Blackbird tail ‘980 on 6 Oct 1986.

“On that memorable MiG-31 encounter mission, I was glad to be flying with Curt, an outstanding RSO admired by all, and, by the way, one of the most popular Habus. There we were, 71,000ft, starting our Mach 3.0 reconnaissance track, heading east just outside the territorial waters of Russia’s Murmansk area coastline. I knew Curt was very busy in the rear cockpit with his many duties monitoring and managing cameras, sensors, and navigation. I kept a constant crosscheck of the many indicators and controls in the front cockpit, watching carefully for potential system failures, and maintaining stable airspeed and the most efficient altitude for our weight.

“After Curt and I completed our first pass flying south-east parallel to the Russian border, gathering imagery and electronic intelligence, our mission track turned us left about 90° and northwards, directly away from Russia over the Barents Sea. After the turn and perhaps another minute in that northerly direction, we turned 180°, and flew directly towards and perpendicular to the Russian coast.

“Our altitude then was probably about 75,000ft. At that altitude, we could see the horizon 335 miles away and see the slight, but noticeable, curvature of the earth. The view was grand. Ahead were miles off the Barents Sea and snow-covered Russia beyond. In the distance far ahead, at perhaps 100 miles, I could see a long, bright white Russian contrail flying directly toward us, but at a much lower altitude. I knew it must be a Soviet fighter, probably a MiG-31, then the newest Soviet supersonic interceptor. I raised my periscope and saw that we too were leaving a long contrail. I knew the fighter could see our contrail as easily as I could see his. Since we were flying a routine reconnaissance track that the Soviets had seen many times, I knew the fighter knew exactly where we would start our 90° right turn to parallel the coast in a westerly direction.

“I imagined the Soviet fighter pilot was much like me, with a love of aviation and trying hard to be one of the very best. I also assumed he had orders to fire his missiles if I was late with my turn and slipped over Soviet territorial waters to within 12nm of Soviet land, and I assumed the pilot would like nothing better than an opportunity to fire his missiles at an SR-71 Blackbird. Just three years prior, on 1 September 1983, a Soviet fighter shot down a Korean Air Lines 747 that accidentally crossed into Russian airspace north of Japan, killing all 269 aboard. Certainly, the SR-71 Blackbird would be a prized target.

“I believed the Soviet fighter would not fire his missiles as long as we stayed on our usual track, but I also knew he or his ground controllers could mistake our position as being closer than we actually were. In the 1980s, we were not too concerned about missiles as long as we maintained our high altitude and high speed. From my previous years of flying intercepts in the F-4 fighter, I knew the newer MiG-31 would still have difficulty maneuvering to the required launch envelope even if he knew our exact flight path. Also, in the high altitude thin air, we believed that missile maneuverability, range, and proximity fuses were not adequate to bring down the Mach 3 Blackbird. For radar-guided missiles, our low radar reflectivity further decreased the missile ‘probability of kill’, and we had a jamming capability for further assurance. I knew our contrail could help him visually put his piper on us for a heat-seeking missile lock-on’. We had no defenses like flares against heat-seeking missiles, but again, we believed that the missile ‘probability of kill’ was very low due to our high speed and altitude. I was determined to fly the track as planned and get the pictures.

“Flying straight toward each other in our supersonic jets, I was reminded of two gallant medieval knights galloping full speed toward each other, only I did not have a weapon. For survival, Curt and I depended on accurate navigation to keep us just outside Soviet territorial waters to prevent a launch, and we depended on our superior speed and altitude in case missiles were launched.

“The fighter’s contrail was holding constant altitude and was heading straight toward us, but far below, perhaps altitude 40,000ft I guessed. I imagined he might be accelerating for a possible steep climb toward our altitude. I watched our distance indicator count down to our turn point, decreasing a mile every two seconds. As always, I was prepared, if necessary, to start the turn manually with the autopilot roll wheel or with the flight control stick, but at our turn point, the autopilot automatically initiated our 90° turn to the right.

“Our 90° turn toward the west was programmed for 32° of the bank. In the turn, I kept a close watch on my instrument panel as always, ready to handle any malfunction. During my instrument crosscheck, I turned my head frequently to watch the fighter’s contrail and saw that he was in a very steep climbing turn toward us. Perhaps a minute into my turn, while turning my pressure suit helmet with my hands so that I could see behind, I saw the grey metal of the fighter, low at my left 7:30 position, at the top of his steeply climbing contrail. We were still in our right 32° banked turn, but I could see him, barely larger than a dot. I could not discern any identifying features like twin tails or distinctive shapes. From my F-4 experience with intercepts and visual acuity, my best guess is that 8 miles were his closest approach. He appeared to run out of airspeed at the top of his contrail, at maybe 65,000ft or about 10,000ft below us. I saw his nose drop below the horizon and fall away. Curt and I stayed on course and got the pictures.

“During my three years of flying overseas reconnaissance missions, I frequently saw contrails far below of potentially hostile fighters, but that day, above the Arctic Circle over the Barents Sea, was the only time I saw a Soviet fighter get close enough that I could actually see metal, though barely larger than a dot and only because our routine track was predictable. Back at Mildenhall, during our debriefing, our intelligence officer told us, with near certainty, that the interceptor was a MiG-31, the premier Soviet supersonic interceptor at that time.”

In the back seat with Ed on Oct. 6, 1986, intercepted was Maj Curt Osterheld. He recalls:

Remembering Gil Bertelson, the SR-71 driver that saw three sunrises on one particular Blackbird mission

“Ed’s description of operations in the Barents Sea is perfect. We knew that the mission was strategically critical in keeping an eye on the Soviet ballistic missile submarine fleet. But we were also aware that if something went wrong with the airplane, the crew did not have many options. Given that we were operating under the rules of the Peacetime Aerial Reconnaissance Programme (PARPRO), our path was predictable, and the Soviets used us for ‘training’… both for the surface-to-air missiles and fighter intercepts. I do have a very clear memory of turning westbound away from Novaya Zemlya (a.k.a. Banana Island). Looking out the right window and with the help of the mirrors, I could see we were pulling a fat contrail at 75,000ft. Looking down I could see a pair of circular contrails, which, I assumed, were Soviet fighters setting up for a ‘practice’ intercept. We believed that the only chance an interceptor (MiG-31) would have at a decent shot was a ‘beak-to-beak’ pass. I believed like Ed, the velocity of closure and geometry of the required maneuver gave a very low PK (Probability of Kill) to this shot.”

Photo by U.S. Air Force and Dmitriy Pichugin via Wikimedia Commons

Lockheed Blackbird: Beyond the Secret Missions (Revised Edition) is published by Osprey Publishing and is available to order here.

December 15, 2021 0 comment

Cold War

The U.S. Navy F-4B made an emergency landing aboard the USS Ranger after Vietnamese AAA destroyed its radome

by Till Daisd November 30, 2021

written by Till Daisd

Due to the damage, the F-4B was later broken up for spare parts at Subic Bay, Philippines

The main image of this article shows a U.S. Navy McDonnell F-4B Phantom II (BuNo 150643) of Fighter Squadron VF-142 Ghostriders. From May 5, 1964, to Feb. 1, 1965, VF-142 was part of Attack Carrier Air Wing 14 (CVW-14) on the USS Constellation (CVA-64).

CVW-14 flew the first strikes of the Vietnam War. During a photo reconnaissance mission to the Thanh Hoa Bridge, the F-4B 150643 of the fighter cover (call sign “Dakota 207”, piloted by Fred Ferrazzano) was struck by a 57 mm shell at an altitude of 150 m. This impact destroyed the nose cone, with some parts being ingested by both J-79 engines. Additionally, it was later discovered that the force of the impact had twisted the main spar.

The pilot was able to recover aboard the USS Ranger (CVA-61). Due to the damage, the plane was later broken up for spare parts at Subic Bay, Philippines. Note that the aircraft is carrying an AIM-9B Sidewinder missile.

Noteworthy, 26 years after this incident, another VF-142 aircraft, this time a Grumman F-14B Tomcat (BuNo 161433) aboard the aircraft carrier USS Dwight D. Eisenhower (CVN-69), had to make an emergency landing when the nose cone came off because of a latching mechanism failure at a height of 8,200 m over the Persian Gulf.

During the departure, the radome came in contact with the canopy, broke out the forward glass, and shattered the windscreen. The pilot suffered a broken right collarbone and glass in both eyes but managed to bring the jet back to the ship for a perfect two-wire landing.

With all the forward glass so badly damaged, the only way to see forward was through a three-inch hole in the left windscreen. The pilot was LCDR Joe Edwards, and the RIO was LCDR Scott Grundmeier. LCDR Edwards was medevac’d to Bahrain for eye surgery, then home to the US.

That time a VF-142 F-14 Tomcat with missing radome made an emergency landing aboard USS Eisenhower

For their remarkable achievement, both crew members received Distinguished Flying Crosses.

Photo by Commander Fred Ferrazzano / U.S. Navy and U.S. Navy via HOME OF M.A.T.S.

November 30, 2021 0 comment

Cold War

A crewless RAF Tornado flew away after the Navigator ejected himself and his pilot from their serviceable aircraft

by Till Daisd November 23, 2021

written by Till Daisd

We may only imagine the front-seater’s feelings as, from his parachute, he watched his Tornado disappear over the horizon

The following article contains excerpts from Group Captain Ian Hall’s story titled Blind and Deaf which appears in Ian Hall’s book Tornado Boys.

Over the years, there have been all sorts of odd instances of aircraft being left without the optimum number of crewmembers. I recall a Phantom navigator ejecting, believing his aircraft to have some kind of terminal unserviceability, only for the fault to rectify itself and for the pilot to return to base solo. Early in the Harrier’s life in Germany, a pilot suffered a catastrophic power loss following a compressor stall.

Try as he might, he was unable to clear it, so was left with no option but to eject. As he floated down in his parachute, you may imagine his surprise when he saw his Harrier merrily accelerating away. Presumably, the rocket efflux from the ejection seat had restored order to the airflow through the engine intake. As soon as he’d returned to earth, our sharp cookie phoned base from a nearby farmhouse to inform them that an unmanned aircraft was now powering its way around Germany.

As you would imagine, this caused consternation; would it crash onto a city? So much so that the authorities considered launching a QRA Lightning to shoot it down. But, given that it was impossible to predict exactly where it would land after being shot down, this option was discarded. Eventually, the wretched aircraft ran out of fuel and crashed happily without any catastrophic consequences. The staff recommendation after this? If pilots have time, they should shut down the engine before ejecting.

That time a crewless RAF Tornado flew away after the Navigator ejected himself and his pilot from their serviceable aircraft

The Tornado wasn’t exempt from similarly unfortunate events, and a notable occurrence derived from one of the aircraft’s foibles. Not for nothing was it known as the ‘electric jet’, and one of its primary systems was the CSAS — the control stability augmentation system. This was designed to make an airframe that was somewhat unstable into a flyable machine. But when the CSAS failed it was a real handful.

Early in the Tornado’s career crews became aware of occasional unexplained control inputs, and after a while and a bit of data analysis, these perturbations pinned down to the CSAS reacting to transmissions from radio masts. So much that low-flying charts began to sprout avoidance circles around the worst of these — known as HIRTAs — high-intensity radio transmission areas.

A chap on my squadron had previously fallen victim to this, in combination with another of the jet’s peculiarities — its command ejection system. The Tornado has a system whereby, in just such an eventuality (it was designed primarily with combat damage in mind) the nav may eject both crewmembers. But pilots are a conservative bunch and enabling this system had not, at that time, been standard, practice.

Naturally, that event prompted much head-scratching, and its aftermath caused a change in procedure, with the command ejection system subsequently being enabled as a matter of routine. But the law of unintended consequences was never more apparent than in my friend’s accident. One fine day he was trundling happily down through Germany at a low level when he became aware of a USAF A-10 Thunderbolt crossing his nose at fairly short range. Short enough to cause him to take evasive action. His trusty back-seater, surprised by this violent maneuver, glanced out of the window. Spying a large transmission mast nearby he assumed that the CSAS was being interfered with and that the jet was out of control. Whereupon he decided that the only way was out, and without further ado, he pulled his yellow and black handle.

That time a RAF Tornado made an emergency landing at F-117's top-secret Tonopah Air Force Base

It now is the standard operating procedure, his command ejection lever had been selected to ‘both’ — so his pilot followed him out in short order. We may only imagine the front-seater’s feelings as, from his parachute, he watched his perfectly serviceable Tornado disappearing over the horizon. Whether or not the A-10 pilot claimed a kill, we may only surmise. But the lesson from that accident was obvious; technology is a marvelous thing, but crewmembers still needed to talk to each other.

Photo by Kate Yates, BAe Heritage Centre and Mike Freer – Touchdown-aviation via Wikipedia

November 23, 2021 0 comment

Cold War

When Cuban-flown Angolan MiG-23 “accidentally” fired two missiles at a BAe 125 carrying the president of Botswana

by Till Daisd November 19, 2021

written by Till Daisd

For unknown reasons, the Angolan MiG-23 fired a missile, which blew the starboard engine clean off the BAe 125. A second missile hit the same engine after it had already left the aircraft

In exchange for South Africa withdrawing from the First Angolan Civil War and agreeing to hold UN-supervised elections for a new government in South-West Africa (SWA), Cuba and the Soviet Union agreed to a gradual withdrawal from the conflict in the middle of 1988. Then, the latter would gain independence and become Namibia. With this agreement, South Africa stopped directly supporting UNITA (União Nacional para an Independência Total de Angola), the country’s second-largest political party and the last major military opposition group, which was heavily supported by the United States, China, and South Africa.

FAPLA (Força Armadas Populares de Libertaceio de Angola, the Angolan military) and UNITA continued to fight when Cuba, the Soviet Union, and South Africa withdrew from Angola. To the surprise of many observers, the combined withdrawal did not spell the end for either organization. UNITA was able to continue operating because it had the continued support of the United States through Zaire and was well-protected by extensive minefields that South Africa had placed during its withdrawal. Additionally, MiG-23s from FAPA-DAA (Força Aérea Popular de Angola—Defesa Anti-Aviones, Angola People’s Air Force and Air Defence Force) kept up their vigorous patrols over the skies over southern Angola, attempting to intercept some of the several transport aircraft transporting supplies for insurgents.

Similar events occurred on August 6, 1988, when a MiG-23 intercepted a Botswana Air Wing BAe 125-800 over Angola, carrying the president of Botswana and eight other passengers at 35,000 feet (10,668 meters). The business jet’s starboard engine was completely destroyed by a missile fired by the Angolan interceptor for an unidentified reason. Once the missile departed the aircraft, a second one struck the same engine. At Kuito, Angola, the pilot regained control and executed an emergency landing. The Luanda government expressed regret for the error and covered the costs of the harm done.

In their book African MiGs Volume 2 Madagascar to Zimbabwe, Tom Cooper, Peter Weinert, Fabian Hin, and Mark Lepko received the following description of the events from Arthur Ricketts, the co-pilot of the Botswanan BAe 125-800 that the Angolan MiG-23 flown from Cuba intercepted and damaged:

“On 7 August 1988, Botswana. Defense Force Air Wing BAe 125-800 (serial ranger OK-1) was tasked to fly His Excellency J. K Quett Masire, President of Botswana, and eight other government officials from Gaborone to Luanda. The aircraft was crewed by Col Albert Scheffers, CO of the Air Wing, and me, Arthur Ricketts, employed as a transport and training captain with British Aerospace. Col Scheffers had completed his type conversion in the UK and I was continuing his line training in Botswana. I had been employed on the test program of the 125 series of aircraft for the previous eight years.

“The aircraft was cruising at FL 350 [10,668m] and had just passed a position report to Luanda after crossing over Kuito Bie. Without warning, the starboard engine of the aircraft was hit by what was later discovered to be an AA-2 Atoll missile fired from a MiG-21 of the Angolan Air Force. A second missile fired was assumed to have hit the engine after it departed the airframe. When hit, the aircraft was on autopilot. This tripped out with the impact of the missile and the aircraft pitched violently upwards, a shower of turbine and fan blades being seen by myself before I instinctively took control of the aircraft manually, rolling it off the top of a stall.

That time a Cuban-flown Angolan MiG-23 accidentally fired two missiles at a BAe 125 business jet carrying the president of Botswana — British Aerospace C-29A (BAe-125-800FI)

“At the point of impact Col Scheffers was rendered incapacitated by the instantaneous application of approximately 33g (calculated by the BAe stress engineers later on, based on damage to the fuselage frames), which threw him hard against the port cockpit wall, and he played no further part in the recovery of the aircraft. Also at this time the engineer traveling with us was thrown into the cockpit from the cabin. The aircraft sustained damage to the pressure cabin that resulted in an explosive decompression. At least one window was shattered by shrapnel from the engine, approximately a ton and a half of fuel was lost from the damaged starboard wing tanks, all radio navigation systems failed, and the cabin oxygen masks failed to deploy automatically.

“My first instinct was to regain control of the aircraft by rolling it away from the vertical and establishing a stable descent, which I achieved by the time we reached FL 280 [8,534m]. Initially, we were descending at about 6,000ft [1,829m] a minute, which gave me almost six minutes to sort everything out before arriving very hard in Africa! In that six minutes, I managed to transmit two Mayday calls, one to Luanda, which was apparently not received or understood, and the other on HF radio which was picked up and acted upon by Santa Maria in the Azores.

“I had substantial previous experience of flying in Africa and assessed that there was probably an airstrip of sorts at Kuito Bie, some 25 miles [40km] behind the point at which we were hit. During the descent, I had assessed the aircraft systems remaining and had made the decision to leave selecting flaps and landing gear until shortly before landing, not expecting them to work. However, when the engine departed the airframe, the quick-release couplings on the hydraulic pump, starter/ generator, and alternator did their job and I was able to have the use of flaps, undercarriage, and brakes, certainly necessary as the damage demanded a landing speed of approximately 150-160kt.

“Several passengers received injuries in addition to the crew, and these were attended to at the hospital in Kuito Bie, before we were eventually uplifted by a Gulfstream III (registration D2-ECB), to Luanda. President Masire was injured by a fan blade that penetrated the cabin and then his seatback. He was subsequently flown to England by the RAF for treatment.

“The captain’s name on the flight to Luanda was Pereira, and he kindly allowed me to fly the aircraft from the co-pilot’s seat. I was repatriated to Botswana by Beech King Air 200 (registration D2-ESO) via Luena Air Base in Angola, where I saw various MiG-17s and MiG-21s, but no MiG-23s as I remember. The base was a shambles, with hangars flattened and aircraft upside down all over that very large area. But, that — as they say — is yet another story!

“The aircraft that intercepted us was said to us to have been a MiG-21. It should have fired two AA-2 Atoll missiles. The information I have about that plane and the missiles is current as of the time when this happened. I can’t recollect the source but have never seen anything different quoted.

“This is the first and only account that has been written … As you can imagine, this was a ‘hot potato’ at the time, which is why I never commented on various reports of the incident. The only other account I am aware of is the record of an interview I gave to Air International News at the NBAA [National Business Aviation Association] show in Dallas, in 1989…

“I was subsequently awarded the Diploma of Outstanding Airmanship, in 1989, by the Fédération Aéronautique Internationale, an honor which is awarded only once a year.”

With regards to the same incident, Teniente-Colonel Eduardo Gonzalez (DAAFAR, Defensa Anti-Aérea Y Fuerza Aérea Revolucionaria, Cuban Revolutionary Air and Air Defense Force, ret.) provided the following commentary:

“During Operation Second Congress, in 1985, I personally intercepted (with GCI support), twice a month and in broad daylight, a huge Douglas DC-10 from Mozambique, flying over Mavinga and bound for Luanda. We were very pissed off because that airway was closed for all commercial traffic – or at least we asked a number of times for it to be closed to the ATC authorities in Luanda since it was a combat zone. Documents on this matter were signed but to no avail.

“I do not want to act as a ‘prophet of the past’ now, but at those times I was sure an incident involving a civilian airliner would happen sooner or later because violations of the war zone occurred almost on a daily basis. Remember that only two years earlier, the Soviets had shot down the South Korean Boeing 747, and only three years later — i.e. in the same year the interception of that BAe 125 occurred —an US cruiser shot down an Iranian Airbus. A responsible aircrew will never accept a flight plan that overfills a combat zone. I was terrified that if a passenger aircraft would enter that zone at night, my pilots and I could not establish a visual ID.

“We [Cubans], as the `world’s black sheep’, could not afford such a mistake. That’s why I instructed my pilots already in 1985 that before launching their missiles at any such target in daylight, they always had to establish a visual ID. Thus, I feel it must be told to Mr. Ricketts that it was a gross mistake for them to fly across a location known by every ‘newspaper in the universe as a war zone. Even more so with a VIP on board.

“The aircraft in question first came under fire from an Angolan SAM site near Cuito Cuanavale. They were in full readiness and attempted to identify the ‘bogie’. There was no ‘friendly’ answer and a ‘clear to fire’ order was issued. They fired four missiles but all missed: they were out of tune with the fire-control radar… Meanwhile, the information was forwarded to Menongue AB, and a Cuban pilot, Capt Albert Olivares Horta, scrambled in MiG-23ML C-479. He accelerated to Mach 1.9 to catch the intruder but never established a visual ID of the BAe 125 before opening fire… Horta fired two missiles. The first was an R-24T from the left-wing station no. 3. This scored a hit, and that was when Horta sighted his target for the first time. He then fired an R-24R from the right-wing station no. 4. To the luck of the crew and passengers in the targeted aircraft, this missile went astray…

“The name of the doctor who took care of all the injured was Ransin Cruz Mendez… I was not in Angola at the time, otherwise, I would keep hammering those cabrones [‘bastards’ in Cuban slang] to insist on visual ID before launching…

“C-479 was later lost due to engine-related problems. 1st Lt Eladio Avila ejected safely.”

Photo by U.S. Air Force and Torsten Maiwald via Wikipedia

November 19, 2021 0 comment

Cold War

Ex-C-5 pilot recounts the “Cockpit Cat Fight” between two female navigators on their first FRED mission

by Till Daisd November 16, 2021

written by Till Daisd

“Sandy, the pretty one, and Penny, the interesting one, hunched over the scope on the navigators’ station behind the pilot. Their voices rose in volume and their tone turned argumentative and aggressive,” Jay Lacklen, former C-5 pilot

Jay Lacklen is a former C-5 pilot with 12,500 flying hours and the author of two books, Flying the Line: An Air Force Pilot’s Journey and Flying the Line: An Air Force Pilot’s Journey Volume Two: Military Airlift Command. He’s working on the last book of the trilogy.

Women Enter The Cockpit, 1982

A significant change in Air Force culture began for me in 1982 when women entered the cockpit, in this case, as C-5 navigators. It began curiously for me.

On an early mission in my C-5 career as a copilot, two female navigators showed up on the flight. I’m not sure why we had two, but it caused problems on the segment coming out of Dhahran, Saudi Arabia, en route to Frankfurt, Germany.

I know this was early in my C-5 experience because we still had the band weather radar that wasn’t worth a damn. It showed dim spokes on its fished-out screen as it scanned the sky ahead and showed returns as ghostly, imprecise shadows with no color gradations to show intensity.

At this time, navigators were losing their mission. Inertial Navigation Systems (INS) had severely encroached on the navigator’s space on the crew and would soon eliminate them as Flight Management Systems (FMS) provided almost all the information navigators had previously provided to the pilots.

But in the early 1980s, navigators controlled the weather radar and processed information from the triple (INS) setup. This trek across the northern portion of the Saudi peninsula, of all the hundred times I made it, had the worst weather I ever saw over this terrain. Thunderstorms were everywhere, some visible, some not when we flew into a cloud deck. This is when near-fisticuffs broke out between the two female navigators.

Sandy and Penny, both first lieutenants, seemed to be getting along well up to this point, but interpreting the K-band returns under pressure progressively led to a raging argument about which way we should turn the aircraft to avoid storm cells.

Sandy, the pretty one, and Penny, the interesting one, hunched over the scope on the navigators’ station behind the pilot. Their voices rose in volume and their tone turned argumentative and aggressive.

We pilots grew frustrated with the argument; we just needed someone to tell us which way to turn. We were flying blind as the argument behind us grew in intensity. Being of equal rank and crew qualification, neither seemed to be in charge. Finally, one of the women stalked to the back to check her forms to see who held the earliest date of rank between them. That finally settled who would call the shots. I can’t remember which one it was, but we finally got information in a timely manner. Not an auspicious introduction to women in the cockpit as a catfight erupts on my first mission with the fairer sex.

Another indicator that things had changed in the crew force happened as we checked into our rooms at the Rhein-Main hotel. Sandy and I shared the same bathroom that joined our two rooms, early shades of a unisex privy. True, each of us could lock the other’s entry door, but doing so, noisily, announced that any of the various performances were about to begin. After a long flight, one of those would probably be one neither would want to share with the other but would have to.

Unfortunately, while we were diligent in locking the door in such situations to avoid a potentially unfortunate face-to-face in the bathroom, were less diligent about unlocking the other’s door when we left. This could prove catastrophic in the middle of the night when you arose in dire need of relief only to find your bathroom door locked. You could pound on the door or get semi-dressed and go out into the hallway to the other’s room entry do and knock on that, dancing in the hallway trying to hold it (and don’t for your key!).

The true catastrophe arrived when the other person had locked your bathroom door and left their room. Now you were truly screwed and would have to use the public bathroom in the lobby or find a housekeeper to enter their room and unlock your door.

And then, lascivious possibilities would arise in the mind. Such as, instead of locking the bathroom door, one of us would open it and step through instead—a rare possibility, I admit, but who knows what fantasy might lurk in Sandy’s libido? Since she was married, that limited the possibility even further, and she did not. But I had a string of such “limited possibilities” that actually happened to me previously with Air Force wives, so who knows?

The incredible story of the C-5 crew that performed three night air refuelings during a storm

And, besides, Penny was the more interesting of the two, so if I got to choose, I’d have selected her. But as with 99% of such fantasies, none of these happened except in my mind. Just as well.

Photo by Senior Airman Zachary Cacicia and Brett Snow / U.S. Air Force

November 16, 2021 0 comment

Cold War

A wife had her wedding ring flown at Mach 3

by Till Daisd November 10, 2021

written by Till Daisd

“Suddenly the wife began sliding her wedding ring off and handed it to me. She said, ‘I would love to have my ring flown at Mach 3,’” Richard H. Graham, SR-71 pilot

The following story appears in Col. Richard H. Graham’s book Flying the SR-71 Blackbird.

At a Wife’s Insistence

Sometimes visitors would ask if we would take a personal trinket of theirs on a Mach 3 flight. Some of the items I’ve taken up with me are coins, dollar bills, American flags, unit patches, and pilot wings.

Once at Det 1, a husband and wife were watching Don and me suit up for a mission. After all the pressure-suit checks were done, I casually asked if there was anything they would like me to take up for them. They looked at each other with a blank stare for a second or two, when suddenly the wife began sliding her wedding ring off and handed it to me. She said, “I would love to have my ring flown at Mach 3.”

I sensed the husband was uneasy with this. He emphatically said, “No!” as he reached out to get the ring back from me. Not wanting a family argument in PSD [physiological support division], I handed it to him and said, “It’s probably best anyway; it looks expensive and could get lost or damaged.”

I thought that was the end of it. She took the ring from him and proceeded to hand it back to me! This time I was smart enough to know not to reach out for the ring. She looked him square in the eyes and said, “My ring is going to fly at Mach 3!” She handed me the ring again, and this time hubby backed off. He knew she was getting serious, and this wasn’t the time or place for a family feud. I wrapped her wedding ring in a protective cloth and zipped it in one of my pressure-suit pockets. I’m not a good judge of diamond ring quality, but it was an impressive stone. The mission went well and the Mach 3 ring was returned to its happy owner!

Photo by U.S. Air Force photo by Tech. Sgt. Michael Haggerty

November 10, 2021 0 comment

Cold War

B-52D Diamond Lil tail gunner explains how he scored the last confirmed kill by a tail gunner in wartime

by Till Daisd November 10, 2021

written by Till Daisd

“I fired at the bandit until it ballooned to 3 times in intensity then suddenly disappeared from my radar scope at approximately 1,200 yards, 6:30 low. I expended 800 rounds in 3 bursts,” Airman 1st Class Albert Moore, B-52D Diamond Lil tail gunner

The B-52 Stratofortress close to the north gate would have a great Christmas Eve tale to tell if the landmarks at the U.S. Air Force Academy could speak.

That day in 1972, the crew of the B-52D, tail number 55-083, took off from Utapao Royal Thai Naval Airfield, as explained in the article Records detail MiG kill by ‘Diamond Lil’ tail gunner. Their mission was to bomb the North Vietnamese railroad yards at Thai Nguyen as part of Operation Linebacker II, which took place Dec. 18–29, 1972.

However, unlike present-day bombing missions, Diamond Lil’s crew faced enemy airpower. A North Vietnamese MiG-21 raced to intercept the B-52, callsign Ruby 3, and her crew. The Buff’s tail gunner, Airman 1st Class Albert Moore, noticed the MiG’s approach.

“I observed a target in my radar scope 8:30 o’clock, low at 8 miles,” he wrote six days later in his statement of claim for enemy aircraft destroyed. “I immediately notified the crew, and the bogie started closing rapidly. It stabilized at 4,000 yards at 6:30 o’clock. I called the pilot for evasive action and the EWO (electronic warfare officer) for chaff and flares.

“When the target got to 2,000 yards, I notified the crew that I was firing. I fired at the bandit until it ballooned to 3 times in intensity, then suddenly disappeared from my radar scope at approximately 1,200 yards, 6:30 low. I expended 800 rounds in 3 bursts.”

Here's how B-52 tail gunners made of the BUFF a MiG killer

Tech. Sgt. Clarence Chute, another gunner, verified the kill in his report.

“I went visual and saw the bandit on fire and falling away,” wrote Sergeant Chute, who was a gunner in Ruby 2. “Several pieces of the aircraft exploded, and the fire-ball disappeared in the undercast at my 6:30 position.”

The kill of Airman Moore is the last confirmed kill by a tail gunner employing machine guns in wartime, and one of only two confirmed kills by a B-52D during the Vietnam War.

Following the MiG kill, Airman Moore said, “On the way home, I wasn’t sure whether I should be happy or sad. You know, there was a guy in that MIG. I’m sure he would have wanted to fly home too. But it was a case of him or my crew. I’m glad it turned out the way it did. Yes, I’d go again. Do I want another MIG? No, but given the same set of circumstances, yes, I’d go for another one.” Moore died in 2009 at age 55.

Linebacker II brought the North Vietnamese government back to the negotiating table after earlier talks had broken down. A month after the campaign, North Vietnam and the United States signed a ceasefire agreement.

Diamond Lil kept on flying even after the Vietnam War had ended. Overall, it logged more than 15,000 flight hours and participated in over 200 combat missions between its commissioning in 1957 and its decommissioning in 1983. It came to the Academy shortly after it was decommissioned.

Photo by U.S. Air Force photo/Staff Sgt. Don Branum

November 10, 2021 0 comment

Cold War

Ex RAF Jaguar pilot recounts being shot down by an RAF Phantom interceptor

by Till Daisd November 9, 2021

written by Till Daisd

“Giving up on the medics, we decided it was time for the bar and he offered me a lift home. Only on the way back to Brüggen did I find out what had happened. The Phantom I had seen fly over the farmer’s field had shot me down!” Group Captain Steve Griggs, former RAF Jaguar pilot

The following article contains excerpts from Group Captain Steve Griggs’s story titled With Friends Like These which appears in Ian Hall’s book Jaguar Boys.

Bang! The aircraft was yawing violently to the right, and not responding to the controls; I heard the canopy shattering. I hear Paddy’s voice from the other aircraft yelling “Eject! Eject!” Thought process — he must know what is going on because I certainly don’t! Result — I eject.

There was a violent explosion, my head was driven down to the breastplate of my lifejacket, I had a vision of the floor of the cockpit dropping away, a snatch of a parachute opening, wrenching pain in my right hand (fool, let go of the seat handle!), then a moment of blissful quiet before the ground below began approaching rapidly. Now, what did the physical training instructors tell us about parachute rolls on landing? Can’t remember in time and — thump, I land completely out of control in a field — and it hurts. Look up and think, momentarily, that I might be in heaven (I was a young, bachelor flight lieutenant at the time) as a blonde vision of loveliness dressed in tight-fitting jodhpurs ran over to me, followed her father (blast!).

“It must be your birthday,” Gerd Molleken (ex-cavalry officer) said. Still distracted by the vision of Germanic loveliness peering (fondly?) at me, I somewhat confusingly replied, “no, that’s not until September”, which seemed to perplex them both.

Former RAF Jaguar pilot tells the story of when he was shot down by a RAF Phantom interceptor

I was being helped to my feet and gathering my parachute and various bits together when alone Phantom flew overhead, very low down.

“Did you see what happened?” I asked the farmer.
He did not, and neither did I know what had happened, except that I thought that it was odd for the F-4 to be alone — they normally flew as pairs. Could I have had mid-air with his mate? They were questions for later since a bottle of brandy had now been produced and hospitality offered (not my daughter, unfortunately). Pausing only to make a quick phone call to Brüggen to relay the news (apparently disturbing the station commander during the annual formal inspection lunch) we attacked the bottle. Remember, this was in the years before compulsory ‘medicals’ following accidents; i.e. I would have compromised the blood test. Still, morale, welfare and not offending the farmer were much higher priorities in my mind at the time — as well as his daughter.

The farmer seemed quite unperturbed by the whole event. Little did I know that he was quite used to having aircraft crash into his fields. A Harrier had ended up there a few years earlier, and his cash register was already ringing up the latest invoice for compensation. Several glasses of brandy later (not sure if they went onto the bill), the sound of a chopper was heard, and a lift back to Brüggen given the courtesy of the German air force. I was rushed to the medical center for a quick check-up, to be met by Paddy and other members of 14 Squadron (I was in Staneval Weapons at Brüggen and was flying with 14 Squadron that day) with bottles of beer stuffed in their pockets. I was waved off for a rather wobbly ride to Wegberg Hospital for X-rays, etc; at that point, there was still no news of what had occurred. Even Paddy was in the dark; he had just happened to look back at me in time to see the aircraft explode and had had the presence of mind to immediately call for me to eject.

Wegberg Hospital was worse than useless. Having arrived in casualty covered in mud and with a cut chin, there was not a soul in sight, even though they had been told to expect me. Finally, I found someone who told me to go down the corridor and book in for an X-ray. That over, I sat around seemingly for ages waiting to see a doctor. I was getting bored and feeling in need of another beer, when, on cue, I walked Flight Lieutenant Brian Newby (I had been flying his ‘named’ aircraft Jaguar GR1 XX963). Giving up on the medics, we decided it was time for the bar, and he offered me a lift home. Only on the way back to Brüggen did I find out what had happened. The Phantom I had seen fly over the farmer’s field had shot me down!

So how did it happen? There I was minding my own business at 1,350ft, returning to Brüggen after a forward air controller training sortie as number two to Paddy Mullen, when the radar unit we were using warned of conflicting traffic ahead. The RWR lit up, which was not an unusual event in the corridor routing aircraft to and from the training areas to Brüggen and Wildenrath. Aircraft went out at 750ft and back at 1,350ft for deconfliction. The F-4s from Wildenrath often ‘painted’ aircraft to ensure their separation. What was unusual this time was that the CWI-band vector moved from front to rear. “Might not be a Phantom then,” I thought, “I could be picking up the Hawk surface-to-air missile site to the north – although that would be a fair distance away.” In the meantime, I saw a German F-104 pass down the starboard side — more of him later.

Hours before this the hooter had sounded at RAF Wildenrath (the Phantom FGR2 base) in the early hours of the morning for a station exercise. Aircraft and crews had been generated, and the aircraft loaded with live weapons in accordance with the normal policy for exercising quick-reaction forces in NATO. Once the required number of live-armed aircraft had been achieved, the aircraft was then de-armed prepared for training sorties loaded with acquisition rounds (inert missiles with real, heat-seeking heads). Crews were then to stand by to fly missions as directed by the SOC for training. For the purpose of such exercises, other RAF Germany aircraft were generally regarded as hostile targets, with fighter controllers scrambling the F-4s to intercept targets for training.

One crew, who shall remain nameless, was scrambled for such a mission in Phantom FGR2 XV422. They took off from RAF Wildenrath to mount a combat patrol under the control of the SOC. At approximately 1247 hrs, they were vectored onto a pair of Jaguars and told to engage the ‘hostile’ aircraft. Following standard procedures for a simulated attack, the Phantom closed on the Jaguars, and, when in an ideal position to complete what until that moment had been a typically routine engagement, the pilot pulled the missile release trigger. This should only have produced a witness mark on the radar film to record the intercept. Instead, as the pilot said later, the growl from the missile seeker transferred to his other ear (now indicating the missile on the other wing), and the first missile was launched.

Dumbfounded he watched, powerless to influence the outcome, (the Sidewinder being a fire-and-forget weapon) as the missile exhaust trail headed off towards my aircraft. He was not even on the same radio frequency as me, and we in turn had not been made aware that we were to be intercepted for training. The AIM-9G missile hit my aircraft, with my complete tail section behind the wing breaking away and the front part of the aircraft (with me still inside) entering a flat spin.

I cannot begin to imagine what was going through the poor guys’ minds on their way back to Wildenrath; it is a bit difficult to explain away returning to base after a training flight with one missile fewer than when you started out! Indeed on the way back, I understand that they had some difficulty in convincing agencies of the reality of the event. At least they had the reassuring knowledge they had seen me eject safely.

Since I was well, with only a slight cut to the chin and not even back pain (I will be able to play golf the next day — albeit with a sore head), I decided to celebrate my lucky escape in the traditional way by putting on a barrel of beer in the mess. Since I did not know the F-4 crew, I invited them to attend to show that there were no hard feelings. To their credit, they entered into the lion’s den and came along, apologizing. It was later that evening that the Brüggen station commander discovered they were in the bar with me, and pointed out that this would not look good for the subsequent board of inquiry — since we could be accused of collaborating. Indeed the ‘party’ was subsequently misreported in the press as us ‘celebrating’ the loss of one of Her Majesty’s aircraft, a fact I tried to correct by a letter to The Telegraph.

At any rate, we split from the mess, with members of 14 Squadron taking the F-4 crew away for beers at the married quarters, and me being royally entertained by the combined efforts of members of 17, 20, and 31 Squadrons elsewhere on the patch.

Obviously, the accident was the result of a monumental cock-up. The board of inquiry found the crew of the Phantom to be negligent, but were they solely to blame? Having read the accident report, and spoken to those involved, the crew seemed to me to be the last link in an unbroken chain that was destined to result in an accident.

The crew had been called out late and had missed the start of the exercise. They were briefed hurriedly and were the last to be allocated an aircraft, which was live-armed. A simulated bomb incident forced them to evacuate the aircraft shelter and they were allocated another, which was also still armed with live weapons. The navigator noted that this aircraft had no red tape over the master armament switch, which would have denoted that the aircraft was live-armed. Halfway through a pee-break (flying and NBC kit hindering a speedy execution of this maneuver), they were scrambled by the SOC, which was also on exercise. The accident train was underway.

The report of the board of inquiry revealed that all of the safeguards provided for in the command and station operating and engineering orders relating to the carriage of live missiles were either ineffective or had not been complied with. The circuit breaker for the firing circuit was found not to be an effective device, even though it had been pulled to render the system inactive. The SOC fighter controller had not made a ‘check switches safe’ call because he had not been informed that the aircraft was carrying live weapons. Indeed, the operations officer at RAF Wildenrath had not passed the information to the SOC because he was not aware of it himself.

Despite these factors and the absence of the vital tape on the master arm switch, the crew was deemed by the board of inquiry to be negligent and (eventually) faced a court-martial which resulted in their being found guilty of negligence. The severe reprimand was given by the court, which was the lightest punishment possible, suggested that the court acknowledged that the crew was not solely to blame. The organization behind them was seen to be at fault, and following a comprehensive review, numerous changes were made to procedures.

The accident may seem unbelievable but vividly illustrates how pressure on individuals, combined with poor organization and inadequate orders, can lead to mistakes being made.

Photo by Rob Schleiffert from Holland via Wikipedia, MSgt. Don Sutherland / U.S. Air Force, Pinterest, Crown Copyright and Todd Pormealeau via sepecat.info

November 9, 2021 0 comment

Newer Posts

Older Posts