The story of a non-standard RF-4C Phantom Ejection

The story of a non-standard RF-4C Phantom Ejection

By Dario Leone
Jul 27 2018
Share this article

A normal F-4 ejection sequence calls for the back-seater to go out first, followed by the front-seater, but an internal fire had burned through Lieutenant Bell’s emergency canopy release line causing his canopy not to blow. Meanwhile the Phantom ejection sequence device ejected Captain Sams leaving the back-seater still in the airplane…

The following article titled Phantom Ejection and written by Charles Arrington & Robert Conely appeared in Volume II, No. 1 issue of Smoke Trails, Quarterly Journal of the F-4 Phantom II Society.

As with any item of military equipment, the ultimate test of man and machine is not always combat. Nothing could be closer to the truth for Major Mike Sams, Captain Mike Bell, and RF-4C 64-1073, than the series of events following an inflight emergency and crew ejection.

Saturday, May 15, 1982 was to be a routine day for pilot Mike Sams, then a Captain, and back-seater Mike Bell, then a Lieutenant, both with the 165TRS/123TRW Kentucky Air National Guard. On this day the two Mikes were to be part of a flight of RF-4C from their home base in Louisville to Savannah, Georgia. Recce Phantom 64-1073, their mount for the trip, had just returned from depot maintenance and sported a fresh paint job. While preparing for take-off, the crew chief Sgt. John Hourigan, joked about not scratching the paint on his newly overhauled aircraft–perhaps a harbinger of things to come.

The story of a non-standard RF-4C Phantom Ejection

During an interview for this article, Major Mike Sams talked of being airborne on that fateful day for around 45 minutes flying over the Cherokee National Forest, about 40 miles south-west of Knoxville, Tennessee when things began to happen. Events occurred as follows. A loud explosion on the left side of the Phantom brought on a fire warning light. Sams moved the left engine throttle to idle and then shutdown. Next, an explosion on the right side brought a fire warning light for that engine, with the pilot reacting by moving this engine throttle to idle. He then pulled the aircraft into a zoom climb, going from about 500 feet altitude to 1500 feet with the airplane rolling to a 45° angle. Pilot Sams was able to transmit one radio message that said it all, “Hey Jack, I think I’ve got a problem.” If this was not enough more bad things were happening. Smoke and heat entered the cockpit as all electrical systems, including the radio, failed followed by a more serious failure of the flight control systems. The KY ANG crew no longer in control of their aircraft made a quick decision to eject. Mike Sams believes that only about 10-15 seconds passed from the first trouble to initiating the ejection sequence. But this was not to be a textbook ejection. A normal F-4 ejection sequence as explained by the Major calls for the back-seater to go out first, followed by the front-seater. Unknown to Mike and Mike, an internal fire had burned through Bell’s emergency canopy release line causing his canopy not to blow. Meanwhile the Phantom ejection sequence device ejected Sams leaving the back-seater still in the airplane. With 64-1073 loosing altitude, Bell activated other seat ejection devices with no luck. Finally at 600 feet the canopy blew after he engaged a normal canopy release, the release used to raise the canopy for a normal ground egress. With the second canopy gone, the ejection sequence continued followed by another successful ejection from the stricken RF-4C.

Ejecting at a higher altitude, Mike Sams floated down under his parachute with a good vantage point to see Bell’s chute open and the burning Phantom pass by looking like a “skyrocket.” Bell landed virtually uninjured near a group of loggers that rushed to his aid. The burning airplane plowed into a tree covered ridge line, exploding into a fireball. Major Sams, knowing a collision with a tree was unavoidable, guided his parachute towards the smallest tree in sight before making contact. Later, safe on the ground, he discovered that he suffered from a separated shoulder and compression fractures of the vertebrae. Both men remained on the ground for about two hours before being picked up by an Army UH-1 helicopter dispatched from Knoxville.

More than three years after his quick exit from RF-4C 64-1073, Major Mike Sams reflected on the incident. He stated that he was off flying status for three months to recover from injuries obtained from the ejection. Sams, with over 2000 hours in the F-4, credits the excellent ejection seat training courses from the Kentucky AG Life Support people for pulling him through on that not-to-be-forgotten day and the professional work done by base personnel that maintained the ejection seat and life support equipment that saved his life. As to the ill-fated Phantom 64-1073, Major Sams mentioned that material failure on the aircraft probably was the cause for its loss.

The story of a non-standard RF-4C Phantom Ejection

In skies over rugged terrain, Mike Sams and Mike Bell met the ultimate test of man and machine and passed with flying colors, in no small measure to their skills, the instructors that prepared them for the task, and to the professionals that made sure their equipment worked when called upon.

Photo credit: TSgt. G. Dennis Plummer / U.S. Air Force


Share this article

Dario Leone

Dario Leone

Dario Leone is an aviation, defense and military writer. He is the Founder and Editor of “The Aviation Geek Club” one of the world’s most read military aviation blogs. His writing has appeared in The National Interest and other news media. He has reported from Europe and flown Super Puma and Cougar helicopters with the Swiss Air Force.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share this article


Share this article
Share this article

Always up to date! News and offers delivered directly to you!

Get the best aviation news, stories and features from The Aviation Geek Club in our newsletter, delivered straight to your inbox.

Error: Contact form not found.


Share this article
Back to top
My Agile Privacy
This website uses technical and profiling cookies. Clicking on "Accept" authorises all profiling cookies. Clicking on "Refuse" or the X will refuse all profiling cookies. By clicking on "Customise" you can select which profiling cookies to activate. We and our selected ad partners can store and/or access information on your device, such as cookies, unique identifiers, browsing data. You can always choose the specific purposes related to profiling by accessing the advertising preferences panel, and you can always withdraw your consent at any time by clicking on "Manage consent" at the bottom of the page.

List of some possible advertising permissions:

You can consult: our list of advertising partners, the Cookie Policy and the Privacy Policy.
Warning: some page functionalities could not work due to your privacy choices