You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.214.0.0/16 has been blocked by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 16:45, 10 January 2025. Your current IP address is 44.214.4.121.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
This IP address range has been globally blocked.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

This block affects editing on all Wikimedia wikis.
The IP address or range 44.214.0.0/16 has been globally blocked by ‪AntiCompositeNumber‬ for the following reason(s):

Open proxy/Webhost: Visit the FAQ if you are affected

This block will expire on 13:57, 18 February 2025. Your current IP address is 44.214.4.121.

Even while globally blocked, you will usually still be able to edit pages on Meta-Wiki.

If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

Other useful links: Global blocks · Help:I have been blocked

You can view and copy the source of this page:

((Short description|US Navy camera pod for the F-14 (1981–2006)))
((More citations needed|date=January 2021))
((Use dmy dates|date=October 2017))
[[File:F-14 TARPS.jpg|thumb|F-14 with a TARPS pod mounted]]
[[File:Logo tarps.png|thumb]]

The '''Tactical Airborne Reconnaissance Pod System''' ('''TARPS''') was a large and sophisticated camera pod carried by the [[Grumman F-14 Tomcat]].((#tag: ref|The pod was originally developed for use by the [[LTV A-7 Corsair II|A-7 Corsair]]<ref>((cite book |last= Spick|first= Mick|date= 1988|title= Modern Fighting Aircraft Volume 8 - F-14|location= New York|publisher= Arco Publishing Ltd|page= 45|isbn=0-668-06406-4))</ref>|group="N")) It contains three camera bays with different type cameras which are pointed down at passing terrain. It was originally designed to provide an interim [[aerial reconnaissance]] capability until a dedicated [[McDonnell Douglas F/A-18 Hornet|F/A-18 Hornet]] reconnaissance version could be fielded. TARPS was pressed into service upon arrival in the fleet in 1981, and remained in use up to the end of Tomcat service in 2006.

==TARPS pod and Tomcat interoperability==
[[File:TARPS drawing.jpg|thumb|left|TARPS drawing.]]
[[File:Crew moves TARPS pod on USS George Washington.jpg|thumb|left|At ((convert|17|ft|m)) and weighing 1,850 lb (840 kg), the TARPS is the largest device hung on a Tomcat.]]

The pod itself is ((convert|17|ft|m)) long, and weighs ((convert|1850|lb|abbr=on)). and is carried on the starboard side of the tunnel between the engine nacelles. The F-14A and F-14B Tomcats had to be specially modified to carry the TARPS pod which involved routing of control wiring from the rear cockpit and environmental control system (ECS) connections to the pod. Standard allowance was at least three TARPS aircraft per designated squadron (only one per [[carrier air wing|airwing]]). All F-14Ds were modified to be TARPS capable, which allowed greater flexibility in scheduling aircraft and conducting maintenance. A control panel is fitted to the rear cockpit and the RIO has total control over pod operation except for a pilot controlled button that can activate cameras as selected by the RIO (but seldom used).

==Camera bays==
[[File:A crewman looks at TARPS imagery aboard USS George Washington.jpg|thumb|TARPS intelligence specialist uses a [[light table]] to analyze film from KS-87 camera.]]
[[File:Crew inspecting TARPS digital camera.jpg|thumb|left|TARPS personnel attending to forward camera bay]]

Each of the camera bays was designed to carry different cameras for specific tasks on reconnaissance missions. The forward bay held a 150&nbsp;mm (6") focal length serial frame camera (KS-87) on a two position rotating mount which could direct the camera's view straight down or be moved to a 45° angle for a forward oblique view.  The second bay or middle bay of the TARPS pod originally held the 230&nbsp;mm (9") [[focal length]] KA-99 [[panoramic camera]] which rotated from horizon to horizon and could be used for side oblique photography. Each image in the wide field of view position produced a 91&nbsp;cm (36") negative. The KA-99 could carry up to ((convert|2000|ft|m)) of film that could be exhausted if not managed carefully by the RIO. The third camera bay held an infrared line scanner camera used for night missions or daylight mission traces. All TARPS cameras were monitored by a device called a CIPDU in the tail cone section of the pod that provided camera status to maintenance personnel and during flight provided aircraft position data onto the camera imagery for intel analysis. An electrical umbilical cord connected the pod to the control panel that was positioned on the left side of the rear cockpit. A hose from the ECS from the F-14 cooled/heated the internals of the pod in flight and kept the appropriate humidity levels constant. In 1987 VF-111 was the first squadron to deploy with a KS-153 camera system in bay two.  The KS-153 used a 610&nbsp;mm (24") lens and was used for stand-off photography in the Persian Gulf. During Operation Desert Shield the KS-153 was used to monitor the no fly zones in Iraq.

[[File:TARPS pod on skid.jpg|thumb|left|TARPS pod mounted on a skid with TARPS personnel]]
Tomcat TARPS squadrons were staffed with Navy photographer's mates and Avionics Technicians that maintained the cameras and worked with the carrier to process the imagery. TARPS squadrons also included an extra Intelligence officer and Intelligence Specialists to help plan TARPS missions and exploit the imagery afterwards. The TARPS shop maintained the cameras and removed or loaded the pod when and if needed. Wet [[film processing]] was conducted in a processing room connected to the ship's Intelligence Center (CVIC) where the Intelligence Specialists has a dedicated space with a [[light table]] for analyzing the hundreds of feet of film and exploiting the data.

==TARPS missions==
The TARPS pod provided capability for the Tomcat to conduct a variety of reconnaissance tasking including:
* mapping (the Tomcat software was also upgraded to assist with this demanding and painstaking mission)
* pre and post strike bomb damage assessment
* standoff oblique photography
* maritime ship surveillance

==Upgrades==
[[File:F-14 from VF-102 with TARPS.jpg|thumb|right|[[VF-102]] F-14 Tomcat seen carrying a combat TARPS loadout including ECA and ALQ-167]]

Although TARPS was originally planned to be an interim solution, combat experience with VF-32 over Lebanon in 1983 resulted in upgrades to the TARPS camera suite and to the aircraft survivability. Since the KA-99 camera was designed for low-medium altitude missions, the Tomcats were forced to fly as low as ((convert|10000|ft|m)) over active AAA and SAM sites in the Bekaa Valley, again by VF-32, resulting in 6th Fleet requesting higher altitude cameras such as had been available in the dedicated reconnaissance platforms such as the RA-5C, RF-8 and RF-4. As a result, the first set of four KA-93 910&nbsp;mm (36") focal length Long Range Optic (LOROP) cameras were shipped to NAS Oceana in the spring of 1984 for deployment with the next Tomcat TARPS squadron. VF-102 conducted an OPEVAL of the cameras en route to the MED in expectation of flying them over Lebanon, but the crisis had cooled down by then. The cameras then became forward deployed assets and [[cross-deck (naval terminology)|cross-decked]] between TARPS squadrons. Later, KS-153 LOROP cameras were also procured and also used as forward deployed assets. The KS-87 camera bay was eventually upgraded with a digital sensor so that imagery could be captured onto a [[PCMCIA]] Type II card for debrief, but could also be transmitted as desired by the RIO.

The TARPS mission first exposed the Tomcat to the AAA and SAM threat on a routine basis and spurred upgrades not only to the cameras, but to the aircraft itself. The existing RHAW gear, the ALR-45/50 was vintage Vietnam era and could not keep up with the latest threats of the SA-5 and SA-6, both present in several threat countries in the Mediterranean. As such, TARPS Tomcats were provided with an Expanded Chaff Adapter (ECA) rail that provided 120 extra expendable rounds and another rail that mounted an ALQ-167 "Bullwinkle" jammer. Eventually, the F-14B arrived with the improved ALR-67 RHAW gear capable of keeping pace with the latest threats. Prior to that, some Tomcat squadrons used modified "Fuzz-buster" automotive police [[radar detector]]s mounted ad hoc on the pilot's glare shield to detect threats not handled by the ALR-45/50.<ref>((cite news | url=https://www.upi.com/Archives/1987/04/29/Navy-using-fuzz-buster-radar-warning-devices/2670546667200/ | title=Navy using 'fuzz-buster' radar warning devices | agency=UPI | date=29 April 1987 | access-date=21 September 2020 ))</ref>

==Operational history==
[[File:Kynda class cruiser underway.jpg|thumb|right|Classic TARPS image of a Soviet [[Kynda-class cruiser]] during the height of the Cold War]]

TARPS was immediately impressed into the Cold War and used for surveillance of Soviet ships at sea and in their anchorages sometimes from over ((convert|1000|mi|km)) distant from patrolling aircraft carriers in the classic cat and mouse tactics of that era.

[[File:VF-102 F-14 overflies Balzam class.jpg|thumb|left|[[VF-102]] TARPS mission to keep an eye on Soviet [[Balzam class intelligence ship|Balzam]] intelligence gathering ship attempting to shadow NATO maneuvers in 1985.]]
TARPS resulted in Tomcats being put in harm's way shortly after it was introduced to the fleet in 1981. VF-102 Tomcats had been inadvertently been fired on by AAA and a single SA-2 SAM over Somalia in April 1983 while conducting peacetime mapping prior to a major exercise. A few months later VF-32 conducted TARPS missions in support of the invasion of Grenada and went on to join VF-143 and VF-31 in flying missions in the Eastern Med where three carriers had gathered to respond to the crisis in Lebanon. Thus, TARPS was responsible for the Tomcat's first sustained combat baptism of fire when the crisis in Lebanon heated up in 1983 requiring daily overflights over hostile AAA and SAMs. During operation El Dorado Canyon in 1986, Libya launched SCUD missiles at a US outpost on an island in the Mediterranean and VF-102 flew TARPS to ascertain if there had been any damage.

[[File:TARPS Desert Storm BDA.jpg|thumb|right|TARPS image of results after [[Lockheed F-117 Nighthawk|F-117]] precision bunker busting during Operation Desert Storm]]
Initially, TARPS was not a priority on the air tasking order during Desert Shield/Storm due to availability of strategic assets like the [[Lockheed U-2|U-2/TR-1]] and plentiful USAF RF-4 units. However, once Desert Storm started, the demand for realtime intel overwhelmed the other assets and TARPS missions were called upon to meet the demand. Immediately, it became obvious that Tomcats were favored for in country missions over the RF-4 as they required no escort and needed less fuel pre- and post-mission, which was a real concern at the time. TARPS continued to be utilized post Desert Storm and training was modified to take into account medium altitude tactics such as were flown in Desert Storm. Prior to that, the majority of TARPS missions training missions were low altitude overland and over water navigation and imagery. Only mapping was flown at medium altitudes. TARPS was used routinely in Operation Southern Watch over Iraq and called upon in Bosnia in 1995 and then again over Kosovo in 1999. The advent of [[LANTIRN]] into Tomcat operations provided a useful complement to TARPS. Since both systems need the same real estate in the rear cockpit for sensor operation control panels, they cannot be mounted on the aircraft at the same time, but they can be flown in formation yielding the best of both systems.

TARPS was used in the United States in 1993 when areas of the [[Mississippi River]] flooded. The [[Federal Emergency Management Agency]] (FEMA) requested TARPS flights be taken over the area to determine which locations were hardest hit.  TARPS has also been used for hurricane damage assessment. TARPS was also used to assess damages following the [[Waco siege]] in 1993, as well as damage to the [[Alfred P. Murrah Federal Building]] following the [[Oklahoma City bombing]]. In addition, TARPS equipped F-14s were used for [[Drug Enforcement Administration|DEA]] intel missions for anti-drug operations in the early 1990s.
((Citation needed|date=December 2023))

==Notes==
<references group="N"/>

==References==
((Reflist))

==External links==
((Commons|Tactical Airborne Reconnaissance Pod System))
*[http://www.fas.org/irp/program/collect/tarps.htm FAS Intelligence Resource Program: TARPS]
*[http://www.globalsecurity.org/intell/systems/tarps.htm TARPS page at GlobalSecurity web site, retrieved 23 November 2006]

[[Category:Aircraft instruments]]

Pages transcluded onto the current version of this page (help):

Tactical Airborne Reconnaissance Pod System (edit)
Template:Ambox (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite book (view source) (protected)
Template:Cite news (view source) (protected)
Template:Commons (view source) (template editor protected)
Template:Convert (view source) (template editor protected)
Template:DMCA (view source) (template editor protected)
Template:Dated maintenance category (view source) (template editor protected)
Template:Dated maintenance category (articles) (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:FULLROOTPAGENAME (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Ns has subpages (view source) (protected)
Template:Pagetype (view source) (protected)
Template:Plainlist/styles.css (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Side box (view source) (template editor protected)
Template:Sister project (view source) (template editor protected)
Template:Use dmy dates (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Commons link (view source) (template editor protected)
Module:Convert (view source) (template editor protected)
Module:Convert/data (view source) (template editor protected)
Module:Convert/text (view source) (template editor protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Ns has subpages (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/rfd (view source) (template editor protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:Side box (view source) (template editor protected)
Module:Side box/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Tactical Airborne Reconnaissance Pod System.

Retrieved from "https://en.wikipedia.org/wiki/Tactical_Airborne_Reconnaissance_Pod_System"