That time the USAF intercepted a pilotless Soviet fighter

Ian D'Costa
Updated onOct 19, 2023 5:32 AM PDT
3 minute read
soviet fighter jet intercepted

soviet fighter jet intercepted

SUMMARY

As it turns out, the Soviet fighter had originated from Bagicz Airbase on what was supposed to be a regular training mission.

On the morning of July 4, 1989, alarm bells blared at Soesterberg Air Base in the Netherlands, home of the US Air Force's 32d Tactical Fighter Squadron. Within minutes, a pair of armed F-15 Eagles, manned by Capts. J.D. Martin and Bill "Turf" Murphy, were launched on a scramble order. Their mission was to intercept what appeared to be a lone fighter making a beeline from Soviet-controlled airspace into Western Europe. Though the Cold War's end was seemingly not too far away, tensions still ran high between the two sides of the Iron Curtain, and any incursion by an unidentified aircraft would need to be responded to swiftly.

F-15Cs of the 32d Tactical Fighter Squadron (US Air Force)

As JD and Turf were vectored in on the aircraft, now identified as a Soviet MiG-23 Flogger supersonic fighter, ground controllers notified them that all attempts to contact the inbound jet had failed and the intentions of its pilot were unknown and potentially hostile.

When they got close the the Flogger, the two Eagles were primed and ready to shoot down their silent bogey if it didn't respond and carried on its flight path. But when the two F-15 pilots closed in on the aircraft to positively identify it, they noticed that the pylons underneath the Flogger — used to mount missiles and bombs — were empty.

By then, the Flogger was firmly in Dutch airspace, casually flying onward at around 400 mph at an altitude of 39,000 ft.

What JD and Turf saw next would shock them — the Flogger's canopy had been blown off and there was no pilot to be found inside the cockpit. In essence, the Soviet fighter was flying itself, likely through its autopilot system.

A Soviet Air Force MiG-23 Flogger, similar to the one which flew pilotless across Europe (US Air Force)

After contacting ground control with this new development, the two Eagle pilots were given approval to shoot down the wayward MiG over the North Sea, lest it suddenly crash into a populated area. Unaware of how long the pilotless MiG had been flying, and battling poor weather which could have sent debris shooting down the MiG into nearby towns, JD and Turf opted to let the jet run out of fuel and crash into the English Channel.

Instead, the aircraft motored along into Belgium, finally arcing into a farm when the last of its fuel reserves were depleted. Tragically, the MiG struck a farmhouse, killing a 19-year-old. Authorities raced to the site of the crash to begin their investigation into what happened, while the two F-15s returned to base. French Air Force Mirage fighters were also armed and ready to scramble should the MiG have strayed into French airspace.

The crash site of the MiG-23 in Belgium (Public Domain)

Details of what led to the loss of the Flogger began to emerge.

As it turns out, the Soviet fighter had originated from Bagicz Airbase — a short distance away from Kolobrzeg, Poland — on what was supposed to be a regular training mission. The pilot, Col. Nikolai Skuridin, ejected less than a minute into his flight during takeoff when instruments in the cockpit notified him that he had drastically lost engine power. At an altitude of around 500 ft, it would be dangerous and almost certainly fatal if Skuridin stayed with his stricken fighter, trying to recover it with its only engine dead. The colonel bailed out with a sense of urgency, assuming the end was near.

But as he drifted back down to Earth, instead of seeing his fighter plummet to its demise, it righted itself and resumed climbing, its engine apparently revived.

The ensuing debacle proved to be thoroughly embarrassing for the Soviet Union, which was forced to offer restitution to Belgium and the family of the deceased teenager. By the end of the MiG's flight, it had flown over 625 miles by itself until it ran out of fuel and crashed.

NEWSLETTER SIGNUP

Sign up for We Are The Mighty's newsletter and receive the mighty updates!

By signing up you agree to our We Are The Mighty's Terms of Use and We Are The Mighty's Privacy Policy.

SHARE