F-14 TOMCAT ISSUES AND ACCIDENTS
The following is a compilation of issues with the F-14 Tomcat that have been encountered by pilots throughout its lifespan due to both mechanical and other reasons. Some are based on individual accidents and some cover epidemics in which many aircraft were lost to the issue *cough* compressor stalls *cough* If you write something pls let me know cause I want to read it :P
Water Damage- Any type of water intrusion would cause issues with the electrical systems. It was a very common thing, so much so that they would have to duct tape anywhere water might be able to enter as a precaution when they knew it would rain.
Hydraulic Fluid Leaks - The F-14 did leak hydraulic fuel fairly often. There was a joke going around that if there isn't a bucket leaking hydraulic fluid underneath the plane then you are out of hydraulic fluid.
The Staple - Cracks were occurring in the aircraft just before the tailhook attachment point. Their solution was to limit the airplane for 3 months to no more than 4 Gs before installing a 1 ft long, 1-inch wide solid steel staple to prevent the cracking. pilots must hang from the staple as a part of their pre-flight check to ensure it won't come out.
Airbags - Now and then, the airbags would rip and they would have to fix them.
Hydraulic Failures - They happened occasionally but were not any more common than they would be in any other aircraft.
AICS Programmers - They would have to start the airplane and then run the intake ramps aka would have to cycle the intake ramps otherwise they wouldn't be able to get off the ground.
Flap-Slat Lockout - If the flaps on either side of the jet didn't program at the same rate, it would cut it out and lock them up. They were then unable to move them as the lockout was a precaution to prevent asymmetry. This forced pilots to land without flaps, requiring an extra 22 knots during landing. Flap-Slap Lockout was a consistent issue throughout the Tomcat's life.
Unreliable Fire Warning Light - Sometimes the fire warning light would just barely start to flicker on and steadily become more prominent. Overall "just a bad system." You never actually know if there's a fire or not.
Wings Won’t Come Out - This happened at NAS Oceana in 1968. The airplane landed at a speed of 230 mph, so very close to the F-14’s stall speed. When the wings are stuck back, you can't hit the brakes during landing because there is no anti-skid and you would overheat them, If you pulled the stick back you would rotate, and with the wings back you have no spoilers so there is nothing to slow you down. In this particular incident, the pilot was able to take the long landing, but if this issue was encountered at sea it would require an ejection. No big explosions or fires though, it’d be a fairly calm procedure and the plane could fly into range of the ship for easy retrieval after ejection.
Low Fuel (Barricade Landing) - Bad weather at night combined with air traffic personnel being too occupied with diverting tons of airplanes, launching tankers, etc. can cause an aircraft to get low on fuel. There was a situation covered in the F-14 Tomcast episode called "F-14 Barricade" where they were unable to refuel using a tanker and were forced to do a barricade landing for their safety. They were almost forced to pull up alongside the carrier and eject. After the landing, one of the crew calculated based on the amount of fuel left that they only had about 90 seconds of flying left. This is literally the only F-14 barricade landing ever I am pretty sure (in real life Maverick's doesn't count lol). I like it because the pilot and RIO had to tell the aircrew straight up "You have to take us now" because the pilot could no longer see the tape on the fuel gage. The crew tells their story really well and it’s really funny to listen to, especially considering the fact that they had to keep sending them around because they fucked up setting up the barrier.
Hitting the Canopy (During Ejection) - Goose's story is based on a real story in which a RIO hit the canopy during ejection and broke his spine. The reason the pilot does not also hit the canopy is because the ejection sends the RIO out first and then the pilot a certain amount of time after, maybe 5-10 seconds or something like that. The ejection seats also launch them in different trajectories so the pilot and the RIO do not collide in the air, meaning they may or may not end up in the same area. The solution would be to wait for the canopy to clear before ejecting but sometimes your don’t have that luxury.
Front Landing Gear Failure During Takeoff- While launching off of the catapult of the aircraft carrier, the nose gear attached to the shuttle broke. The landing gear and shuttle proceeded to the end of the runway without the jet, hitting the end of the ship at 305 knots and damaging the front of the carrier. The jet went off the ship with far less speed than necessary (at barely 60-70 knots) and began falling into the water as it was not enough to get the Tomcat in the air. They ejected to barely 50 feet high and were in serious danger of getting run over by the aircraft carrier. In the accident covered on the Fighter Pilot Podcast FPP004 - Ejection Seats, the RIO tells the story of his survival and the tragic loss of the pilot.
Radome (Nose Cone) Detachment - An F-14 Tomcat lost its radome during a flight due to the failure of the latching mechanism. The radome crashed into the canopy, shattering te glass of the windscreen. The pilot could only see out of a 3 inch hole in the windscreen due to the cracked windshield. He couldn't hear anything due to the noise of the wind in the cockpit, so he was unsure of the state of his RIO but assumed he was unconscious because he hadn't ejected them. The pilot was able to land the plane, despite having glass in both eyes and a broken collarbone. The pilot was medevaced for eye surgery and then returned to the US.
Midair Collision - F-14A BUNo 159832 was a midair collision between two F-14 Tomcat. In this particular situation, one of the airplanes was able to divert to a nearby airport due to losing part of the right wing whereas the other crew was forced to eject. Obviously you could probably imagine a situation where both jets went down.
Landng with Damage - Tomcats are a very sturdy aircraft, often described as being a tank both due to how much fuel they were able to carry and the sheer size of the aircraft. The following video shows an aircraft landing aboard an aircraft carrier with significant damage on its right right side.
F110 Afterburner Failure - The new engines installed were great, but they initially had a problem with the afterburner. In one recorded accident, the pilot lit the afterburner, damaging the afterburner can's lining and leading to an explosion. The Navy prohibited use of the afterburner below 10,000 ft on the F-14+/B/D until the problem could get solved but it took nearly a year to remedy.
"Thump Bang" - The easiest way to incorporate any sort of accident is to call it what the Naval Aviators call a "thump bang". A "thump bang" refers to a series of events that occur when an aircraft experiences some sort of issue they described as a "thump" and then an explosion. It's kind of hard to describe what is like in the cockpit during this sort of accident as it could have happened quickly or could have been a delayed explosion, and it could have been caused by any number of reasons. If they don't know what actually happened, they'll call it a "thump bang" and can only hypothesize what occurred. The likely scenario would have been an issue with the TF30 engines.
TF30 - The "Turd in the punch bowl, " the F30s had two specific issues that were kind of intertwined.
Throwing Fan Blades - One of the largest issues with the TF30s was that they were known to throw fan blades. When the fan blades become eroded or damaged over time, they no longer compress the airflow efficiently, potentially leading to an engine stall (see Compressor Stall below). Additionally, the T30 was known for "throwing" fan blades. This is when the fan blade becomes detached and is shot out to the side into the interior of the aircraft. Not good. Pretty bad actually. They didn't initially know they were throwing fan blades until after a couple of accidents. when they started to be more common they would retrieve the aircraft from the water (if in large enough pieces and then investigate the cause.
Compressor Stall - The actual biggest issue with the F-14 Tomcat and its T30 engines is the compressor stalling. They literally happened all the time from a variety of different causes. Generally speaking, the compressor stalls were the result of disruption to the airflow into the compressor of the engine. The compressor has fan blades that require the airflow to be undisturbed for maximum efficiency. It was theorized to be the result of foreign object debris (FOD) ingestion into the engines. They check religiously for loose objects on the airplanes as a result, oftentimes having a crew member dive into the intake ducts to check for loose bolts. Additionally, compressor stalls could be caused by operating the aircraft outside of its limits, improper handling, etc.
The F-14 had a gated afterburner, meaning it had 5 “gates” inside of the afterburner and each one lit up a flame rack. There was no variable thrust, so it had to be either on or off. Each of the five racks was labeled as a zone. Zone 3 is what they were allowed to take off with. Coming in or out of afterburner with any angle or attack would cause the compressor to immediately stall. This was mostly due to poor design of the intake.
In general, approximately 30% of F-14A losses were attributed to high-altitude compressor stalls. When one engine stalls, more often than not it will induce the other engine to stall as well. There is a procedure to counteract the compressor stall, the specific protocol was to ease the amount of Gs, slow down, the T.I.T. would go crazy and you shut it down. Or in fighter pilot slang, “ease, slow cook it, shut it down.”
stormborns
tangentwithtanner
pixelskylines
2087
snowghoul
dailybridgerton
areudirty
izzy806
jacobvanloon
