At some point in the trek, what appeared to be the tail section of a military jet rested ahead on a small piece of higher ground. Fallen trees and logs at a distance can look like many things, but a closer look was warranted. As seen below, it was indeed the tail section of a military jet.
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
A wheel...
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F, 51-1895 wreckage - Image by Mark Musselman |
RF-84F - Image USAF |
After initially being told that we would need to contact the Freedom of Information Act (FOIA) office, three members of the flight safety office came out to the swamp to satisfy their curiosity. After their initial excitement at seeing the older USAF insignia, they examined what could be seen of the debris field and concluded that the aircraft had impacted at a low angle generally from the east and that the crash investigation team likely took portions of the aircraft (engine, cockpit, and sensitive equipment like cameras). As Joint Base Charleston had no records of the incident, we sent our request for information to the FOIA office.
Upon returning from Christmas break, we found a letter from the FOIA office stating that they had no records of the incident in question. After a brief consultation with Fox Mulder, we were confident that there was no coverup involving the 1950s-era reconnaissance aircraft possibly encountering alien craft over Four Holes Swamp. However, we were also confident that the aircraft had not disappeared without someone in the USAF noticing (extra parking space on the runway apron; missed scheduled-maintenance appointments; extra set of keys on the sign-out board; inspectors pointing to serial number on an inventory list). Therefore, just like the movies, we went to the Internet for answers.
Unlike the movies, the detailed information we sought, including ventilation schematics for the aircraft hangers, did not immediately pop up on our computer screen. Earlier searches for military aircraft crashes in South Carolina had produced only a few high-profile crashes and mainly recent incidents. We searched for any military aircraft crashes and found a webpage showing all significant crashes from the 1940s until the present, but were overwhelmed by the volume of losses by the United States alone. We narrowed the search to simply F-84 models and once again were overwhelmed by the number of crashes, including eight flying together when ice formed on intake screens and all the engines flamed out. All of the USAF F-84 crashes occurred prior to the time frame we expected based on our local story, though F-84s flown by foreign governments continued to crash throughout the 1970s. After a rainy Saturday of searching, we found one webpage that showed numerous RF-84F aircraft crashes listed as impacting in South Carolina. Ignoring the Edisto Beach, Aiken and other non-local crash sites, we focused on the handful of crash locations listed as Shaw, AFB.
Looking back at the image showing the tail section of the aircraft wreckage, portions of the buzz number could still be seen. The buzz number was a large alphanumeric designation on the side of the aircraft to help those on the ground identify aircraft that buzzed low over their house, town, or facility. For the F-84 models, FS was the alpha- portion of the buzz number and the last three digits of the aircraft's serial number was the numeric portion of the buzz number. As the wreckage showed FS-89?, we looked at the two aircraft listed on the webpage that had 89* in their serial number. One aircraft was 51-1897 and one aircraft was 51-1895. Although the wreckage does not allow a full identification of the final number of the buzz number, it was clear that the number was not a 7, but could certainly be a 5. The RF-84F (serial #51-1895) was listed as possibly crashing in December 1956. With a specific aircraft and a more precise date for the crash, we emailed the FOIA office.
Before the end of the day, we received a call that, given the updated time frame, they had located the aircraft crash report and would be sending the releasable portions to us. They stated that the aircraft had crashed on January 7, 1957 in a dense swamp northeast of Dorchester, SC. Yep, that would be her.
Opening the manila envelope that arrived revealed photocopies of microfilm records with all names (pilot, maintenance crews, investigation officers, etc.) redacted. Reading the "Report of AF Aircraft Accident" was pretty straightforward: Dorchester, SC; 7 Jan 57; 1509 EST; Shaw, AFB, SC; flight duration 0:29; 21,000 feet; RF-84F-10RE; FltLt; British...what? We do not know the identity of the 168-lb, 71-3/4" Brit, but here is how his half hour went after taking off from TAC, 9AF, 363D TACRECONWG, 363D TACRRECONGRU, 18th TRS stationed at Shaw, AFB over 60 years ago. (Update: from my USMC roommate, 1/31/2017 - He found a webpage showing ejections from aircraft, which identifies the British pilot as Flt. Lt. John West. Update: from Grant Mishoe, 2/1/2017 - John West went on to be a RAF wing commander, flew the Canberra and died on 5/2/2008.)
http://www.ejection-history.org.uk/project/year_pages/1957.htm |
HISTORY OF FLIGHT:
At 1330 hours, 7 January 1957, FLT LT XX briefed 2NDLT XX on a formation flight, during which close and tactical formation, oblique photography, and instrument flying were to be practiced. Flight conditions were VFR and the flight was to be conducted in the local area.
Engines were started at 1425 EST. The start of FLT LT XX aircraft, RF-84F NR 51-1895, was normal, with no indication of engine malfunction or over-temperature. Formation take-off was accomplished on Runway 22 at 1440 hours, FLT LT XX leading with 97 percent power for take-off.
Level off was accomplished at 23,000 feet and power reduced to 95 percent. After approximately 10 minutes of tactical formation, FLT LT XX was maneuvering and taking oblique photographs of LT XX aircraft, and after a turn of some 60 to 90 degrees while pulling a slight "G" force (2 to 2-1/2 "G's"), FLT LT XX heard a loud explosion in his aircraft, and the aircraft started to vibrate violently. Power setting was 95 percent, altitude approximately 21,000 feet, and airspeed 340 knots.
The wingman noticed a ball of fire come from the tailpipe, immediately followed by what appeared to be fuel pouring from the underside of the fuselage and sabre drain. The aircraft itself did not catch fire.
FLT LT XX retarded the throttle and turned the fuel valve off. As the airspeed slowed down to 270 knots, the vibration smoothed out and FLT LT XX had satisfactory control of the aircraft. FLT LT XX continued to decrease the airspeed, and at 230 knots the vibration increased again and he decided to eject.
FLT LT XX blew the canopy at 7,000 feet and ejected. The lap belt released automatically and FLT LT XX manually pulled the "D" ring. He retained his P-4 helmet and oxygen mask and landed, without injury, in a large pine tree.
The aircraft continued on in a westerly direction for 4 miles and crashed in a swamp area.
(Update: 4/13/2017 from Grant Mishoe, Flt. Lt. John West's description of his ejection.)
Elsewhere, the report states that the $665,162 aircraft was destroyed primarily by an engine explosion and secondarily by being abandoned in flight. The primary cause of the engine failure "was materiel failure in the first stage of the engine compressor rotor blades," which was caused by "metal fatigue in the compressor rotor blade serrations." The engine was a Buick J65-B3, serial number B-641288.
Annotations on an area map (I-26 and I-95 are conspicuously absent) shows the pilot landing in a tree in the area of the new Volvo plant northeast of Ridgeville. The sketches below show the flight of the aircraft before impact and the resulting debris field. The flight safety team from Joint Base Charleston was correct in their assessment of the crash.
RF-84F, 51-1895 accident report sketch - USAF |
RF-84F, 51-1895 accident report sketch - USAF |
A few black-and-white/microfilmed/photocopied images were included showing various aspects of the crash site. There was the engine, which was removed from the swamp and studied as part of the investigation.
RF-84F, 51-1895 accident report image - USAF |
RF-84F, 51-1895 accident report image - USAF |
RF-84F, 51-1895 accident report image - USAF |
RF-84F, 51-1895 accident report image - USAF |
(Related news coverage at ABC News4. Corrections: 1) Audubon's Francis Beidler Forest is not part of a national forest. 2) Land manager is responsible for 18,000 acres of Francis Beidler Forest not Four Hole Swamp. Francis Beidler Forest is a portion of Four Hole Swamp. 3) The aircraft in the image is the same model, but not the aircraft that crashed.)