Tag:

planes

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

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

History

Carmine Vito: the only U-2 pilot to fly above Moscow

by Till Daisd November 9, 2021

written by Till Daisd

“I learned later that the Soviets launched at least five fighters to intercept my flight. Two planes took off initially. The lead plane aborted takeoff ran off the runway and exploded. The wingman went through lead’s flames and then bailed out. Two more airplanes scrambled and were refueled in the air. Those airplanes got lost or collided. The pilots bailed out. A fifth plane scrambled but couldn’t find the tanker. He was lost and never found to this day,” Carmine Vito, the only U-2 pilot to fly over Moscow

The first flight of the original U-2A, which Kelly Johnson and the Lockheed Skunk Works built with total secrecy, took place in August 1955. The president and other U.S. decision-makers received crucial intelligence about Soviet military capacity during the first flights over the Soviet Union in the late 1950s. Its employment was kept a secret until Francis Gary Powers’s U-2 was shot down by a surface-to-air missile on May 1, 1960, when it was conducting a reconnaissance trip over Soviet territory.

The only U-2 pilot to fly directly over Moscow was Carmine Vito, one of the original six pilots trained to operate the high-altitude reconnaissance aircraft for the CIA. His journey, which the pilots referred to as a “hot flight,” was the third operational flight into a possibly hostile country, as explained by Eric Hehs in his article Carmine Vito: U-2 Pilot for Code One Magazine. On June 20, 1956, Carl Overstreet made the first U-2 flight of its kind. East Germany and Poland were included in the mission.

After that, on July 4, Hervy Stockman flew over Soviet territory, traveling as far north as Leningrad to photograph naval shipyards and then west to the Baltic States to photograph bases for jet bombers. Marty Knutson, Glen Dunaway, and Jake Kratt piloted the fourth, fifth, and sixth missions. All were successful.

The story of Carmine Vito, the only U-2 pilot to fly over Moscow — Early U-2 pilots had to resign their military commissions before joining the CIA as civilians, a process they referred to as “sheep dipping.”

“The Russians launched planes to intercept Overstreet on the first flight,” notes Vito. “But they couldn’t reach him.” Soviet radar also picked up Stockman’s flight. Many MiG fighters sprang into action to intercept him as well. The intercepts, like earlier flights, were unsuccessful. Soviet fighters were unable to get close to the necessary height to bring the soaring U-2 down.

When the orders to fly came, Vito’s selection for the Moscow mission was more a result of chance than of planning. Twelve hours before takeoff, headquarters would generally send an alarm message to the Wiesbaden U-2 detachment. Normally, the message arrived before 5:00 p.m. The ground staff and pilots prepared for the flight throughout those twelve hours. The aircraft, engine, and cameras underwent ground inspections by teams from Lockheed, Pratt & Whitney, and Kodak. To combat the effects of rapid decompression, pilots put on their specialized partial pressure suits and breathed pure oxygen (the bends). Before being granted the all-clear to take off, U-2 pilots had to spend at least two hours “on the hose” to expel nitrogen from their blood.

“Without a go signal from headquarters, everyone headed for the club after five that evening,” explains Vito. “On that particular weekend, the 4th of July, most everyone was celebrating. When the late go came down from headquarters, I was the only one who had had only one drink. So, even though our order of mission flights had been predetermined by drawing straws, I was selected for the mission.”

After recalling this specific U-2 mission for 46 years, Vito is unsure if he is speaking from true memories or memories of earlier descriptions. Whatever the case, he recalls the fireworks display that kept him up that night and the required steak and egg meal the next morning. “They always fed us steak and eggs before a flight,” he says. “I didn’t want steak and eggs at two in the morning, but they were on the checklist. So I had to eat.”

Vito went through Krakow, Poland, before continuing to Brest and Baranovici in Ukraine. On his trip to the Soviet capital, he continued along this east-northeasterly course while flying over Minsk.

The mission began in bad weather. “We had about 200 feet of visibility on the ground,” recalls Vito. “The sky was clear at 3,000 to 4,000 feet, but I had undercast halfway inbound.” The weather cleared as Vito followed a railroad line from Minsk to Moscow. At an altitude of more than 66,000 feet, he listened to Peter and the Wolf, a Russian musical composition with narration, transmitted from a Soviet radio station. Small mosaic fields from the collective farms passed below him. “Those fields reminded me that Russian farmers tilled the land by hand,” he says. “I couldn’t get mad at people who work that hard. I was never mad at the Soviet people themselves, just at their government.”

Vito’s mission carried him directly over Moscow and the vast array of recently constructed air defenses that encircled the city in three concentric circles at a distance of twenty, forty, and sixty miles. The metropolis was hidden by a hazy sky. “My bubble burst,” Vito recalls. “I thought, Gee I came all this way for nothing. But the filters on my camera cut through the haze. A year or so later, I learned that the resulting film picked up some remarkable detail.”

A CIA history of the U-2 claims that Vito’s flight captured photographs of the Fili airframe facility, where the Soviets were constructing their first jet bomber—known to the West as the Bison—as well as a bomber arsenal in Ramenskoye, a rocket engine plant in Khimki, and a missile plant in Kaliningrad. He turned north toward the Baltic coast from about east of Moscow before turning back south toward West Germany.

“I learned later that the Soviets launched at least five fighters to intercept my flight,” says Vito. “Two planes took off initially. The lead plane aborted takeoff ran off the runway, and exploded. The wingman went through the lead’s flames and then bailed out. Two more airplanes scrambled and were refueled in the air. Those airplanes got lost or collided. The pilots bailed out. A fifth plane scrambled but couldn’t find the tanker. He was lost and never found to this day.” Vito never received credit for five aerial victories. “After all, I never fired a shot,” he says.

On his way back to West Germany, the Canadian radar came on the air: “Lone Ranger, this is Tonto. Keep heading the way you are going. You have twenty-two minutes to touchdown.”

“I knew they were talking to me because they had the best radar around and had picked us up on previous flights,” recalls Vito. “But U-2 pilots had to observe complete silence on the radio. To this day, I wish I could have replied, ‘Ti Ee Kemosabe.’”

Vito logged over 450 hours on about 65 flights in the U-2 between 1955 and 1959. In the first U-2C at Edwards AFB, he made his final flight. In August 1960, he left the CIA’s U-2 headquarters.

Photo by Lockheed Martin

November 9, 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

Cold War

That time an RAF Tornado made an emergency landing at Tonopah AFB, home of the top-secret F-117

by Till Daisd November 7, 2021

written by Till Daisd

“The guys at Tonopah had a sense of humor after all, for the silhouette of an F-117 had been stenciled on each side of our tail fin,” Squadron Leader Wally Grout, former RAF Tornado navigator

The following article contains excerpts from Squadron Leader Wally Grout’s story titled Still Learning After All Those Years which appears in Ian Hall’s book Tornado Boys.

So there I was, just approaching my 40th birthday and all fired up to participate in my first Red Flag exercise in the States. After just four missions, my pilot and I were tasked as the lead crew for the package on 9 April 1990. I had spent my earlier years on the mighty Vulcan, having been posted from nav school as a navigator radar, and was lucky enough to be one of the first to cross over to the Tornado GR1 in January 1982. Red Flag was, at that time, a distant dream.

I was now on my second Tornado tour; I had 440 hours on type and, together with my pilot, was now to lead the planning and execution of a typically complex mission into the heart of Red Flag territory. I had come a long way.

Our mission was to penetrate the defenses and drop two inert 1,000 lb bombs into an airfield target using a loft maneuver. All Red Flag aircraft are fitted with telemetry pods and, much like Formula One racing cars, can transmit information back to the HQ so that supervisors and spectators can watch the progress of the ‘war’ on a big screen in real time.

We were airborne on time and proceeded to Caliente, our holding point for entry into the Red Flag area. Whilst orbiting, checking maps, timings, and aircraft systems we detected a fault; fuel was not feeding on the wings into the fuselage tanks. This problem was not insignificant and, although the checklist gave advice and possible solutions, the fault could lead to serious fuel imbalance and possible mission abort.

We were approximately three minutes from our push time; just sufficient to go through the initial actions from the checklist. But we had no time to see if the problem was cured.

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

We completed the pre-target checks, found the initial point, and performed the attack. Job did, bombs on target, time to recover. Once settled we did a routine op check. As we covered ‘fuel’ our heart rates increased. We had not cured the fuel transfer problem; both of us having been fully tied up with the mission, we’d not double-checked. It was now clear that we didn’t have enough usable fuel to get back to Nellis, even in a straight line.

The next few minutes seemed to last forever. From the map, Tonopah was our nearest diversion, and I gave my pilot the relevant track information. Simultaneously, we transmitted to Red Flag control that we were diverting with an emergency. In fact, with the telemetry pod ‘big brother’ probably knew already — but that call seemed to set the cat amongst the pigeons. Tonopah at that time was home to the USAF / Lockheed ‘skunk works’, a highly secret development site for the stealth bomber program. We all knew about the F-117 but, as yet, it hadn’t been officially cleared for public consumption.

You can now imagine the reaction over the radio. “Why do you need to go there? You cannot get there. What exactly is wrong with your aircraft? Why can’t you go to Indian Springs?” (a less sensitive diversion airfield). We even had our detachment commander quizzing us. All the time fuel was reducing and we were getting closer to Tonopah. Between us, we convinced all and sundry that our only alternative to Tonopah was an ejection over the desert. That shut them up, and we now got a period of relative quiet on the radio while we concentrated on getting our aircraft safely on the ground. We hadn’t really thought about what would happen after that.

After touching down we were instructed to clear the runway, stop, and shut down. We complied, made the seats safe, and raised the canopy.

What happened next is the stuff that makes Hollywood great. Several vehicles formed up in front of the aircraft, including one full of armed soldiers. Steps were brought and we climbed out. A USAF major greeted us; he confiscated the film cassettes from the HUD and the data recorder, told us that the aircraft would be looked after, and escorted us under armed guard to the operations center. Good job that I didn’t on this occasion have the 35mm camera I usually carried with me or they really would have thought we were spying! He guided us to a windowless room with blank walls and minimal furniture. We sat down, wondering what would happen next. We both felt reasonably relaxed, apart from the armed guards — after all, we had saved the aircraft and felt justified in our actions.

The major then explained our predicament. Landing at a top-secret establishment in the USA is not an everyday occurrence and we were now going to be questioned — or, as it later turned out, interrogated. Our interlocutor asked all the standard questions: name; rank; squadron; nationality; why we landed at Tonopah. And some more personal: marital status; family background; and educational qualifications. All the while, two large military personnel armed with carbines stood by the door.

Having finished with his questions the major left the room. After a few minutes, another male entered the room, dressed casually in civilian clothing. No introduction, no name given, just more questions. It was almost a repeat of those we had already answered. However, erring on the side of, ‘let’s not make waves’, we both answered them.

He left and we sat chatting about our situation while the guards remained in the doorway. It was now time for my bladder to complain; a post-flight comfort call was needed. I told the guards I needed the `john’. The response took me by surprise; a guard would have to escort me — I assume to prevent me from running amok. He duly stood a few races behind me as I took relief. I was escorted back to the room and we waited some more.

I then recall a further interrogator asking the same questions and getting the same responses. The major returned to tell us that our aircraft was now confiscated and that we would be flown back to Nellis in one of theirs. We would be told when we could have ours back, and we would be the only crew allowed to return to pick it up. He left us to puzzle why.

Soon we heard the sound of aircraft taxiing. We asked a guard if the F-117s were flying this afternoon, to which he shrugged. I said, “I suppose you have to wait until the surveillance satellites are clear before you fly the 117?” His response was standard USAF: “I do not know what you are talking about, sir.” Further questions elicited similar responses. We gave up. More aircraft noise from outside; more flying tonight? It was getting late in the afternoon.

Eventually our ‘friendly’ major returned with news that, for operational reasons, we would not be flying back to Nellis but it would be a road trip instead. We asked if the operational reason was the fact they were flying the F-117. He gave a non-committal smile.

More waiting, but then we were told that transport was available and asked to get our kit together. The next move stunned us both; we black cloth bags put over our heads. We were led out of the room and outside; we could hear the sound of jets but thought it better not to ask more questions. We were helped into the rear seats of a vehicle. As the doors closed, our guards in the front seats had a few words for us to digest. “Do not remove your blindfolds, we are live-armed.” “OK,” we said; the understatement of the year.

We drove in silence for what seemed an age. The bags had not been tied under our chins and I made a conscious effort to get a handle on the direction of travel by looking down and using the shadows; it was now getting close to sunset and I estimated that we had been traveling west for the majority of the time. When we finally stopped and the guards told us to remove our blindfolds, I turned around and could just see a tiny speck in the distance, which I assumed was an F-117 in the circuit. We were at the main gate and the aircraft must have been about fifteen miles away. What a main street to an airfield!

For our journey back to Nellis we were given brown paper ‘sacks’ of sandwiches, chocolate, and fruit juice — courtesy of the Tonopah fire department dinner lady. That was about the only friendly gesture we’d had all afternoon, and boy was the food welcome.

The welcome at Nellis was cool but not hostile. It came as rather a surprise to the RAF commander that we would be told when we could have our jet back. We hadn’t serviced the aircraft, but NATO air forces regularly exercised on each other aircraft so we assumed our ‘hosts’ had a capability. Furthermore, strange as it may seem, there was an RAF pilot on an exchange tour on the F-117 at the time. Indeed, digressing slightly, during the Iraq War an ex-Tornado pilot took an active part in operations, flying an F-117. But did we think we had got away with it?

The next day a telephone message told us to get over to the other side of Nellis field, where a USAF Beechcraft was waiting to take us to Tonopah. We were met by a very young USAF pilot; we boarded, made ourselves comfortable while the crew gave us a quick safety brief, and off we went. The pilot wanted to know why and how we had gone to Tonopah, and also asked if we needed anything doing to our aircraft.

As we approached the field the pilot informed us that we would have to be airborne in less than forty minutes after arrival. He couldn’t say why, but he let on that there would be jets out for flying. We were not allowed to see them but, as we broke into the circuit, he hinted that if we looked out of the starboard window we would get an extremely good view of two ‘invisible’ aircraft. Shame that I’d left my camera behind!

He dropped us close to our aircraft and, once again, armed guards watched us; our friendly major was on hand to see us off, repeating that we had forty minutes to get airborne. As we did an inspection we noticed that the guys at Tonopah had a sense of humor after all, for the silhouette of a stealth fighter had been stenciled on each side of our tail fin. And in the cockpit, tucked under the windscreen, was a police parking ticket for illegal parking on US military soil. We had with us a couple of squadron prints, one for operations and one for the fire department. As we gave these to our major he presented us with a print of the F-117, even though it didn’t officially exist. The last time I had the chance to look, the print was still on the walls of the crew room at Marham.

That’s not quite the end of the story. Having debriefed the engineers about our fuel problem, they did their investigation and found that the transfer valve was indeed not working. Hurrah, at least we got that bit right. However, in hindsight, that well-known exact science, we should have monitored the fuel flow more closely and, if necessary, aborted the mission. But you know how it is — leading the pack, adrenaline rush, must complete the task, and all those other excuses for not giving up. All very well in peacetime to press on — but what about real war?

Update: Mike Crutch, author of the book CVW: US Navy Carrier Air Wing Aircraft 1975-2015, brought to our attention that “a RAF Phantom FGR.2 (F-4M in the US speak) diverted there also during a RED FLAG, arriving back at Nellis with a day glo F-117 sticker and legend DON’T ASK. The diversion took place on Nov. 9, 1989, and the aircraft was Phantom FGR.2 serial XV476 (coded ‘S’ with No.56 Squadron, based at RAF Wattisham, UK but was part of a mix of airframes from UK and RAF Germany units as crews changed during RED FLAG). The zap was applied to the port engine intake.” Unfortunately, we couldn’t find any photo of this aircraft with the F-117 Zap.

Photo by Crown Copyright via Ian Hall, U.S. Air Force, and Mike Freer – Touchdown-aviation via Wikipedia

November 7, 2021 0 comment

Cold War

An SR-71 had an inflight emergency during a secret mission over the Golan Heights during the Yom Kippur war

by Till Daisd November 6, 2021

written by Till Daisd

“We had no viable emergency airfields, and I did not want to be a no-notice, no–flight plan, single-engine emergency arrival at David Ben-Gurion Airport in Tel Aviv, especially since the Israeli government had not been informed in advance about the mission,” Jim Wilson, SR-71 pilot

The Lockheed SR-71 Blackbird Mach 3 strategic reconnaissance aircraft was the fastest and highest-flying operational aircraft in the world for about 24 years throughout its career. It could survey 100,000 square miles of the Earth’s surface per hour from 80,000 feet. In the unlikely event that an enemy attempted to bring it down with a missile, the Blackbird just had to speed up and outrun it.

Notably, some SR-71 operational sorties had a higher priority than others. There were several means of ensuring they would be flown successfully. The lowest level of mission priority had a spare SR-71 ready and waiting in case the primary aircraft malfunctioned. The next priority level had a spare crew in the cockpit of a second SR-71 waiting for codewords that the primary aircraft had malfunctioned and that they were to launch ASAP. The highest level of priority had a spare SR-71 flying the same route directly behind the primary aircraft by about 30 minutes.

Once the primary aircraft was a “go,” the spare aircraft returned to base.

The development of the iconic SR-71 Blackbird: how the world's fastest plane was conceived

If a completely new mission was tasked and had a level of difficulty that required in-depth mission planning, it could possibly take the crews several days to get all the details worked out with the mission planners. These were generally high-priority missions that arose from a crisis somewhere in the world.

SR-71 pilot Jim Wilson gives the following account of one mission during the Yom Kippur War, which can be found in Col. Richard H. Graham’s book Flying the SR-71 Blackbird:

“On October 6, 1973, the armies of Egypt and Syria opened an offensive against Israel on two fronts, launching a coordinated series of air, armored, and artillery attacks across the Suez Canal into the Sinai and on the Golan Heights. The preemptive strike came as a result of a failure to resolve territorial disputes arising from the Arab-Israeli War of 1967.

“These disputes involved the return of the Sinai to Egypt and return of the Golan Heights to Syria. UN Resolution 242 and Egyptian president Sadat’s peace initiative failed to bring peace. Sadat wanted to sign an agreement with Israel, provided the Israelis returned all the occupied territories, but Israelis refused to withdraw to the pre-1967 armistice lines. Since no diplomatic progress was being made toward peace, Sadat was convinced that to change things and gain legitimacy at home, he must initiate a war with limited objectives.

“Along the Suez Canal, eighty thousand well-equipped members of the Egyptian army who had crossed the Suez on rapidly constructed pontoon bridges attacked fewer than five hundred Israeli defenders. In the Golan Heights, approximately 180 Israeli tanks faced an onslaught of 1,400 Syrian tanks. Initial Israeli military losses were significant, and assistance was requested from the United States.

“National reconnaissance satellites did not have the capability that needed to sufficiently assess the situation. The 9th SRW at Beale AFB, California, was alerted to prepare to fly SR-71 missions from Beale AFB over the area of conflict and recover at RAF Base Mildenhall, England, a mission within the design capability of the aircraft, although a long and logistically difficult mission never before accomplished in operational environment.

“Within the first few days of the conflict, the supporting Arab nations initiated an oil embargo, making oil a weapon of war and contributing to a decision by the British government to deny approval to use Mildenhall as a recovery base. Plan B was rapidly drawn up to fly SR-71 out of Griffiss AFB, New York, through the area of conflict, and recover back at Griffiss. These never-before-accomplished twelve thousand—mile missions would require five air-to-air refuelings, the deployment of sixteen KC-135Q supporting tankers with special JP-7 fuel to Spain, and a specialized maintenance intelligence and operational support planning staff to Griffiss. The 9th SRW was well prepared, and in utmost secrecy, the forces were mobilized and deployed. The first mission was successfully completed on October 13.

“I was a fairly young pilot in the squadron at the time, with only one operational tour and about 120 hours of SR-71 time under my belt. On October 20, I was assigned to fly a backup SR-71 from Beale to Griffiss in an alert posture, prepared to fly follow-on missions. We flew successful missions on October 25 and November 2, where I served as a backup pilot. My turn as primary came up on November 11. The excitement level was high, as I certainly wanted to be part of the Force and the wing’s success in completing the mission as tasked.

“Takeoff was at 2 a.m. on a brisk and clear autumn night with about fifteen inches of snow already on the ground. It was peacefully calm — until I lit each of the thirty-four-thousand-pound thrust afterburners. The first 450 mites had to be flown subsonic at 0.9 Mach since we had to clear the commercial aircraft flight tracks out of Boston and New York to Europe before we could safely conduct air refueling operations. Radio-silent electronic rendezvous with three tankers 250 miles out over the North Atlantic at 3 a.m. went well, as did the seventy-thousand-pound (10,600-gallon) fuel offload.

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

“You don’t know the true meaning of dark until you’ve been in a situation like this. We likened it to refueling in an inkwell. After completing a few post-refueling checks, I lit the afterburners and started my acceleration to a leisurely Mach 3 cruise across the Atlantic. The airplane performed flawlessly, thanks to the extra-special effort by maintenance guys. About two thousand miles across the Atlantic on an easterly heading, I watched with excitement as the sun peeked over the horizon and came up right in my face in about a minute and a half—a nice vantage point for viewing this daily event.

“The second refueling was conducted in daylight, a couple of hundred miles north of the Azores. This was another seventy-thousand-pound offload, thirty-five thousand pounds from each of the two tankers, while the airborne spare tanker was not needed. I started my second acceleration and headed for the Strait of Gibraltar. Cruising through the center of the narrow strait at eighty thousand feet with clear weather one hundred miles on both sides provided quite a spectacular view.

“As we proceeded down the Mediterranean toward the Middle East, the weather grew gradually worse as forecasted. The third air refueling south of Crete, although in poor weather, went as scheduled. After packing in a full load of eighty thousand pounds of JP-7 fuel, I lit the afterburners and started the acceleration toward the target area.

“At 0.98 Mach, just prior to going supersonic, maximum fuel flow full afterburner, a red engine-oil-quantity-low light illuminated steady on my emergency warning annunciator panel. I stared at it in almost disbelief, while scanning engine instruments, oil pressure, rpm, exhaust gas temperature, and nozzle position for other indications of trouble. Although there were no confirming indications of problems, I couldn’t just ignore the situation and continue on into the target area with the possibility of an engine failure at supersonic speed over the Sinai. We had no viable emergency airfields, and I did not want to be a no-notice, no–flight plan, single-engine emergency arrival at David Ben-Gurion Airport in Tel Aviv, especially since the Israeli government had not been informed in advance about the missions and they were in a battle for their own survival. I took the engines out of the afterburner to access the situation and think about the best course of action.

Read the story of the SR-71 crew that landed their Blackbird in zero visibility

“To my pleasant surprise, a few seconds after coming out of afterburner, the red emergency warning light went out. I was by now fairly well convinced that it was a false momentary indication, but it had cost me 2,500 pounds of critically needed fuel. My tankers were now eighty miles behind me heading further away. Getting rejoined to top off with fuel would present a new set of problems. I decided to light the burners and press on. Except for a five-second flash during acceleration, I never saw the light again.

“My flight track went down the Suez Canal past Cairo before making a left turn at Mach 3.15 to the north across the battle lines in the Sinai. I continued on a northerly course across the Dead Sea and over the center of the Golan Heights with the panoramic and point cameras providing imagery of hundreds of targets on both sides of the aircraft. Approaching the Lebanon border, I made a sweeping right turn over Syria and then back into the Sinai on a parallel flight path for maximum coverage. The airplane was running well, and I pushed it up a bit to Mach 3.2 before exiting the area near Port Said.

“Once out over the Mediterranean, I started a descent to twenty-five thousand feet for my fourth refueling. As fate would have it, not only I was low on fuel because of my previous oil warning problem, but also a thunderstorm had moved in over the scheduled air refueling contact point. My reconnaissance systems officer (RSO), using electronic azimuth and distance measure equipment, got me to within less than a mile behind my tanker, but the visibility was so poor that I couldn’t see the tanker. We continued twenty miles down the track in lousy weather with only one-half mile and one thousand feet separation before a small break in the clouds permitted hookup. When we made contact and started transferring fuel, I had less than fifteen minutes of fuel remaining and was seventy-five miles from the closest straight-in emergency landing runway on Crete. Needless to say, I was very thankful to tanker buddies, RSO, and good equipment for that rendezvous. It gives new meaning to finding a gas station when you really need one.

The story of the SR-71 Blackbird that slid on JP7 fuel residue while taxing into Kadena Hangar

“We completed a fifth seventy-thousand-pound air refueling near the Azores before the leisurely Mach 3 flight across the mid-Atlantic with a landing at Seymour Johnson AFB, North Carolina. We were met by 9th SRW download crews who had the photo and electronic intelligence equipment downloaded and on a dedicated AF courier flight to Washington, D.C., and the National Photographic Interpretation Center in twenty minutes. The flight covered 12,181 miles in ten hours, forty-nine minutes, and included six hours, forty-one minutes of supersonic time, and five air refuelings. After landing, I remember wondering what Charles Lindbergh would have thought about the advancement of aviation technology in less than fifty years. The 9th SRW was tasked to fly nine missions of this type and completed them all successfully.”

Photo by Lockheed Martin, NASA and U.S. Air Force

November 6, 2021 0 comment

Cold War

The Lightning interceptor that suffered a reheat fire at supersonic speed but landed safely

by Till Daisd November 5, 2021

written by Till Daisd

“I scramble down it to see what the fuss is all about. Moving to the rear of the Lightning, the cause of everyone’s concern becomes apparent; highly inflammable hydraulic fluid is pouring from the vicinity of the hole in the fuselage and running down inside over the hot jet pipe. I suddenly realize that, now that my part in the drama is over, my hands are beginning to shake.” Sqn Ldr Clive Rowley, former RAF Lightning Driver

The following article titled The ‘Hole in the Wall’ and written by Sqn Ldr Clive Rowley MBE RAF Ret’d appeared in Issue 5 – English Electric Lightning of Aviation Classic.

On my lounge wall at home is a strange-looking object, which could, at first glance, be taken for a piece of modern sculpture of dubious artistic merit. On closer inspection, a brass plaque explains the jagged hole in the center of the metal panel: ‘THE HOLE, Reheat Fire damage to Lightning F2A XN789 on 11th May 1976’. This strange wall decoration has a special place in my heart and my home, as it reminds me of a day when I was very lucky to keep up my record of having the same number of landings as take-offs and that all pilots need luck as well as skill. This is the story.

It is 11 May 1976 – I’m taxying out towards the runway in Lightning F2A, XN789, tail letter J (the personal aircraft of Sqn Ldr John Spencer, 19 Squadron’s OC B Flight), and taxying rather fast as we always do. No ‘fast walking pace’ for us, as taught at the flying training schools, we don’t have the fuel to waste taxying slowly. Even in the F2A with its large ventral tank and 10,300lb of fuel, we still suffer from the Lightning’s well-known shortage of ‘go juice’. I’m burning only slightly less fuel per minute on the ground than in the cruise at 36,000ft and I’d rather be burning it up there. I’ve been flying Lightnings with 19 Squadron at RAF Gütersloh in Germany for just over two years. I have over 500 hours flying on type, although I’m still only 25 years old and still considered a junior pilot on my squadron.

Pre-take-off checks

As I taxy out, I complete the pre-take-off checks from memory. These are now second nature. Trim: Set for take-off. Airbrakes: In and locked. Anti-ice/rain dispersal: Off. Autopilot: Set up. Fuel: Transfer switches on, ventral tank feeding. Flaps: Up and indicating up. Instruments and electrical system indications: Checked. Pitot heater: On. Warning panels: All warnings out. Battery master switch: Checked on. Oxygen: Check contents, pressure, and flow. Hood: Close the cockpit canopy fully and double-check that the handle is fully down with the electric switch in the handle fully recessed, check that the shoot bolts that lock the canopy down are in the locked position and that the canopy seal is inflated. (In the past there have been several incidents with the canopy being sucked off just as the aircraft reaches lift-off speed on the take-off roll due to the pilot not having locked the canopy fully; this is now virtually a ‘hanging offense’ so extra care is taken over it). Seat harness, leg restraint lines, and dinghy line: Connected. Hydraulics: Check controls for full free movement, warnings out, pressures good.

Finally, ejection seat safety pins are all stowed. The seat is now live and ready to fire when the handle is pulled. It’s a slightly strange thing to be sitting on an explosive seat, but it’s something that you get used to and are happy to accept as this could be your lifesaver if and when staying with the aircraft no longer has any merit!

The incredible story of the Lightning interceptor that suffered a reheat fire at supersonic speed. And landed safely. — Lightning F2A XN-789

I call on the radio for permission for our formation of two Lightnings to take off; adding “canopies locked” as without that confirmation the air traffic controller will not let us go. Having received clearance, I taxi onto the runway, line up pointing down the center of the left-hand half, and bring the aircraft to a halt, the nose dipping as the nose-wheel leg compresses when I apply the brakes. My wingman for this sortie, Flt. Lt. Phil Owen, the 19 Squadron Qualified Flying Instructor, lines his aircraft up alongside me on the right-hand half of the runway. He looks across at me and gives me a ‘thumbs up’.

I give him the ‘wind up’ signal, rotating my gloved index finger. I parallel the two throttles and then advance them both smoothly forward to wind the two mighty Rolls-Royce Avon jet engines behind me up to 92 percent RPM. This is the most power that the brakes can hold, any more and the wheels will start to slide even with the brakes fully on. I can hear an increased roar behind me to accompany the engine indications on the gauges. A quick check around the cockpit shows that all is well and I look across at Phil. He gives me another ‘thumbs up’ – he’s ready. I tap the front of my flying helmet on the ‘forehead’ twice and then give a pronounced nod of my head to indicate brakes release.

Take-off

We both release the brakes simultaneously, the acceleration is immediate and, as we start to roll down the runway in formation, we move the throttles forward to maximum ‘cold’ (unheated) power, and check that the engine indications are normal. I nod again and we both push the throttles through the ‘gate’ to select reheat. A double ‘thump’ from behind me and a kick in the back tell me both reheats have lit and I glance in to check the indications – jet pipe nozzle positions and jet pipe temperature. I bring the power back a bit from full reheat to give my Number Two something to play with. On my right, Phil is doing all that I am doing and trying to stay in formation with me; others will be watching and reputations are at stake! All this has taken mere seconds but we are already accelerating through 150 knots so I start to raise the nose-wheel and at 180 knots pull back on the control column to lift-off from the runway.

As soon as I’m safely airborne, its brakes on to stop the wheels rotating (there is a lot of energy in wheels doing 190mph) and select undercarriage up even though we’re only feet above the ground. The aircraft is accelerating rapidly and because the nose-wheel retracts forwards into the airflow, it will stick down if the speed reaches 250 knots before it is locked up. As a single aircraft, there is the option, albeit an untidy one, of pitching the aircraft into a steeper climb to keep the speed down while the undercarriage locks up, but this isn’t something you can do during a formation take-off, with a wingman trying to keep station. Rapid and apparently quite ‘punchy’ undercarriage retractions immediately after liftoff are therefore the ‘norm’ for Lightning pilots.

Once the undercarriage is locked up, I nod my head again and we both cancel the reheats and continue to accelerate fairly rapidly in ‘cold’ power to the climbing speed of 450 knots. I roll gently into a right turn onto the northerly climb-out heading and, as I roll out of the turn, I wave Phil away and he breaks out in a ‘punchy’ manner to position his aircraft in tactical ‘battle’ formation about a mile to my right and line-abreast with me. The speed is now at 450 knots and we’re climbing rapidly through 2000ft with an 18 degrees nose-up attitude. This is a fairly steep climb, but if I were climbing at full power, in reheat, as we sometimes do, I would need a 30-degree nose-up attitude and close attention to the speed to prevent the aircraft from going supersonic in the climb!

We switch to the departure frequency on the radio and continue the climb, transitioning to a climbing speed of M0.9 as we pass 16,000ft. About 31⁄2 minutes after take-off (not that I’m counting) and 28 miles from the airfield, we level off at 36,000ft, cruising at M0.9 now talking with the German Ground Control Intercept (GCI) controller, who will organize and provide control for the supersonic intercepts we are going to practice.

Going supersonic

We split up under his control with Phil going off to the north to act as the target for the first intercept (he will run in at 40,000ft and at M1.1) and I am held at the southern end of the supersonic corridor. When the controller has organized sufficient range between us, we both turn in onto reciprocal headings as directed by him; our tracks will have about 10 miles lateral separation between them.

To the north, I know Phil will be engaging reheat on his engines to climb and accelerate to the target parameters, then he’ll throttle back to minimum reheat to hold the speed; the F2A will not quite hold supersonic flight in ‘cold’ (unheated) power so cannot actually ‘supercruise’ like the earlier marks of Lightning could. In my aircraft, I engage the reheats and accelerate through the transonic regime. There is a second or two of the very light buffet, the so-called ‘cobblestone’ effect at about M0.97, which could easily be mistaken for some clear air turbulence. The Machmeter winds up through M1.0 – the only indication that I am supersonic – there is no noise, no vibration, no fuss; this is what the Lightning is designed to do.

At M1.04, the altimeter height suddenly winds up by 1800ft, and indications on the other pressure instruments also jump as the pressure errors disappear when the shock wave moves back past the static vents. I’ve been supersonic on very many occasions now and there is really no thrill to it anymore. At six miles high you are not even aware, visually, that you are accelerating towards 1000mph and beyond. That said, I’m quite proud of my ‘Ten Ton Club’ membership although, now every Concorde passenger qualifies, it’s somewhat less exclusive!

Accelerating through M1.25 at 38,000ft with both engines in full reheat, I notice a slight pulsing in the power and, looking in at the engine instruments, I see that the Top Temperature Control on the No.2 (top) engine is intermittently trimming back the RPM. I throttle back to an intermediate reheat setting and, as I do so, the No.2 reheat self-cancels. I re-select reheat on the No.2 and it lights normally, we are accelerating again, perhaps it was just a ‘glitch’.

Thirty seconds later, I get an audio alarm which immediately draws my eyes to the warning panel. The Reheat Fire 2 warning is illuminated! This is just like being in the simulator except I’m not; this is for real and it isn’t good. A reheat fire warning might be spurious, but if it is real, the outcome may involve earning a Martin-Baker tie and landing by parachute rather than as planned. Many Lightnings have been lost over the years to fires.

Emergency drills

I immediately and rapidly carry out the reheat fire drill, instinctive actions drummed into me during the regular simulator training I’ve received. I throttle the No.2 engine back to idle, operate the catch on the throttle, and bring the throttle fully rearwards, closing the high-pressure fuel cock for that engine and shutting it down. I also turn off the low-pressure fuel cock and the fuel pumps and select the air-to-air refuel switch to refuel to stop fuel transferring through pipes that may be damaged.

There is no fire extinguisher for the reheat zones of the Lightning so that’s all that can be done for now. I declare a ‘Mayday’ on the GCI frequency, hoping I sound a lot calmer than I feel, and about 10 seconds later the warning light goes out. Perhaps it was a false alarm, or perhaps the fire is so bad it’s burned through the firewire! I really don’t fancy ejecting at supersonic speed and at such a high altitude, so I now start working hard to slow down and go down, in case of ejection becomes necessary.

That time a lone RAF Lightning intercepted a horde of 80 Soviet strategic bombers

The ideal ejection parameters we are told are 10,000ft and 250 knots, although, personally, I’ve always felt that 10,000ft is a long way to come down in a parachute, the harness of which may be pinching certain sensitive parts of one’s anatomy. I am now heading towards the pre-meditated ejection area, the Dummersee Lake, and its surrounding marshland, about 30 miles north of Gütersloh. If I have to eject, the aircraft will hopefully cause no harm to anything or anyone on the ground in this unpopulated area.

Meanwhile, Phil Owen in the target aircraft has got GCI to vector him onto me very slickly and he joins into close formation to give my aircraft a visual inspection. From the port side, he can see nothing amiss, perhaps it was just a spurious warning. He moves to the starboard side and finds something. “Oh yes, you’ve definitely had a fire!” he says on the radio, sounding really quite enthusiastic about his discovery. I’m glad he is pleased!

He describes what he can see; a large jagged hole about a foot in diameter on the top of the rear fuselage beneath the base of the fin. Even more worrying, he also reports what he says looks like smoke or fluid venting from the hole, and he asks me to check that I have completed the drill and turned off the fuel to the No.2 engine. I double-check and confirm that I have.

The reheat fire drill requires the pilot to hold off for a minimum of five minutes before commencing recovery. This requirement is as a result of experience gained with reheat fires earlier in the Lightning’s life and is intended to give confidence in the integrity of the tailplane control rods at the rear of the aircraft, which could easily be damaged by a fire and which might then fail, leading to loss of pitch control. By the time that I have – waited five minutes from the initial fire warning, my usable fuel (in the left wing) is getting quite low. I do not want to transfer fuel from the other tanks as I don’t know whether the fuel transfer pipes have been damaged. So I request permission to commence my recovery with the Gütersloh Air Traffic Controller we are now talking to.

His immediate response is, “From your Squadron Commander you are to remain in the ejection area for another two minutes”. I point out that my fuel is now low, I have already completed the five-minute hold-off and I’d really like to recover now. After a brief pause, during which my future is presumably being discussed on the ground, I am allowed to commence recovery. I complete a slow speed handling check on the way back to Gütersloh, slowing down to 175 knots in the landing configuration with undercarriage down, flaps down, and airbrakes out, to ascertain that I still have control at the approach speed.

‘Mayday’ recovery

I land from a straight-in visual approach, my ‘Mayday’ status ensuring I have priority over all other traffic. I fly a relatively shallow approach, a glide path angle of about 21⁄2 degrees converting to two degrees for the last part just before landing, coming down at 175 knots with that high nose-up attitude the Lightning’s 60-degree swept wings demand on the approach. Phil stays with me all the way home flying a loose formation position, keeping out of my way but keeping an eye on me, which is quite comforting; he overshoots on my right as I am about to land.

The landing is quite normal, albeit on one engine, which is no big deal in the Lightning as there is plenty of power from just one engine even without reheat. I touchdown at about 160 knots, with a slight check back on the control column to arrest the rate of descent, and then, as the nose wheel comes down onto the runway, I close the throttle to idle and reach for the brake chute handle. As it is the No.1 engine that is still running and that provides the hydraulic power to open the brake parachute doors, the chute works normally, and stopping is no drama at all. I have 600lb of usable fuel remaining, not a lot, as I pull off the runway at the far end and shut down, immediately being surrounded by fire trucks, tractors, and assorted senior officers.

Thinking that the panic is now over, I carefully confirm that everything is switched off and made safe in the cockpit. While doing this, I suddenly notice the ‘Boss’, Wg Cdr Bob Barcilon (OC 19 Squadron), frantically signaling from the ground beside the cockpit for me to get out. The firemen have positioned one of their ladders against the cockpit so, without further delay, I scramble down it to see what the fuss is all about. Moving to the rear of the aircraft, the cause of everyone’s concern becomes apparent; highly inflammable hydraulic fluid is pouring from the vicinity of the hole in the fuselage and running down inside over the hot jet pipe. The firemen are poised with hoses ready lest it all catches fire and quite bizarrely, not to say bravely, the OC Engineering Wing (a Wing Commander) is standing on the top of an ‘A’ frame ladder in his shirt sleeves with his hand in the hole, attempting to stem the flow of hydraulic fluid with what looks like a large handkerchief! I suddenly realize that, now that my part in the drama is over, my hands are beginning to shake.

The sequel

At the end of what had been a rather exciting day and once I had completed all the various paperwork that an incident of this nature generates, I went to the Officers’ Mess bar and was enjoying a well-deserved beer or two. The squadron’s Junior Engineering Officer came looking for me to explain what had happened.

For some reason, the No.2 (top) engine had lost about 25 percent of each of the four exhaust cone support fairing shrouds at the rear of the engine, and two pieces of the fairing, one quite large, had lodged in the reheat burner ring. It seemed that these lodged pieces of metal had sufficiently disturbed the reheat flame distribution to cause excessive heating and failure of the jet pipe skin. Once that had happened, burning through the aluminum alloy structure and fuselage skin was inevitable. Effectively the No.2 reheat had burned out through the side of the aircraft.

Considerable damage had been caused to the rear fuselage on the starboard side and the rudder-powered flying control unit had been damaged by the heat and was leaking fluid from the No.1 control system. In Lightning, the flying controls were entirely hydraulically powered with no manual backup. If both hydraulic systems failed, the controls went solid.

With the No.2 engine shut down and with it, the No.2 hydraulic system, the flying controls were being supported only by the No.1 system. This was losing fluid at such a rate that had I stayed airborne for much longer, I would have had a complete flying controls failure and been forced to eject, possibly at a late stage on the approach. The engineers actually calculated that I probably had only two minutes left before the controls would have failed completely. I had been very lucky indeed!

When I went back to my room later that evening there was a piece of Lightning propped against my door, a panel with a jagged hole in the middle, obviously beyond repair and looking like it had been damaged by ‘flak’. Stuck to it was a note from OC Eng Wing that simply said, “A Souvenir?!”

Photo by Royal Air Force, MilborneOne, Arpingstone, and Mike Freer – Touchdown-aviation and frankskarl via Wikipedia

November 5, 2021 0 comment

History

Red Tail legacy over Alabama from past to future

by Till Daisd October 31, 2021

written by Till Daisd

Together, Peace, Lopez, and Lang took to the air. Once the fighter pilots adjusted to the P-51’s rather sluggish pace, the flying was smooth

On Thursday, September 7, 2018, keen-eyed spectators inspecting the skies may have spotted a special tribute to the history, present, and future of the Tuskegee Airmen legacy that was created in Alabama more than 77 years ago.

The members of the 100th Fighter Squadron Red Tails at Dannelly Field are aware of their past and the importance of the red paint on the tails of their jets, as stated by Staff Sgt. Jared Rand of the 187th Fighter Wing Public Affairs in the article Tuskegee Airmen Legacy Soars Over Alabama. It pays tribute to the original Red Tails, the heroic World War II Tuskegee Airmen of the 332nd Fighter Group (and 100th Fighter Squadron). These Airmen, who were among the first African-Americans to serve in the military, decorated the tails of their P-51 Mustang fighter planes in order to distinguish friendly from hostile aircraft amid the chaos of combat.

On September 8, the Red Tails Over Montgomery Air Show was scheduled, and when U.S. Air Force (USAF) Maj. Rich “Sheriff” Peace, a fighter pilot with the Red Tails, learned that a Red Tail P-51 Mustang and an F-22 Raptor from the 301st Fighter Squadron would be flying in for the show, and an idea started to take shape. The Tuskegee Airmen were also the ancestors of the 301st.

Past, present, and future of Red Tail legacy over Alabama

“We realized we had an opportunity to do something historic”, Peace said later. “That was to take three Tuskegee aircraft, with three black pilots, and do a flight over Tuskegee.”

A compelling image to motivate the following generation of Airmen would be on full display, showcasing the past, present, and future of the Red Tail legacy.

A different formation flight was authorized following coordination, phone calls, and assistance from leadership all the way up to the MAJCOM level. Over Moton Field in Tuskegee, where the Tuskegee Airmen trained, and Dannelly Field, where the 100th currently flies, the three aircraft would fly in formation. F-16 would be piloted by Peace. The P-51 would be flown by Commemorative Air Force pilot Brad Lang. And the F-22 would be flown by USAF Maj. Paul “Loco” Lopez, the team leader and pilot for the ACC F-22 Demonstration Team.

“We all stand on the shoulders of giants,” Lopez said before the flight. “If you look around here in Montgomery, you can see how the Air Force values preserving our legacy and honoring our heritage. For me, it’s very humbling to know that a lot of people went through great sacrifices so we can all be here.”

Lang, Lopez, and Peace all went to the air. Once the fighter pilots got used to the P-51’s rather slow speed, the flight was smooth.

“I had seen (the P-51) in air shows, but being right next to it, it’s just so beautiful and majestic,” Peace said after the flight. “Seeing it flying over Moton Field was pretty awesome.”

The jets made a variety of formations and photo opportunities before returning to Montgomery. Although the flight was over, the impact it made on the pilots and probably others who heard their narrative will be felt for a long time.

“The legacy flight was to honor the memory of the Tuskegee Airmen and to bring visibility and light to the sacrifices they made then, what we’re doing now, and how they paved the way forward to the future,” Peace remarked afterward. “To see what their work and sacrifice led to today was a pretty amazing thing. I was honored and proud to be part of it.”

Photo by Staff Sgt. Clayton Cupit / U.S. Air Force

October 31, 2021 0 comment

Newer Posts

Older Posts