Replies

Mission

The RC-135V/W Rivet Joint reconnaissance aircraft supports theater and national level consumers with near real time on-scene intelligence collection, analysis and dissemination capabilities.

Features

The aircraft is an extensively modified C-135. The Rivet Joint's modifications are primarily related to its on-board sensor suite, which allows the mission crew to detect, identify and geolocate signals throughout the electromagnetic spectrum. The mission crew can then forward gathered information in a variety of formats to a wide range of consumers via Rivet Joint's extensive communications suite.

The interior seats 32 people, including the cockpit crew, electronic warfare officers, intelligence operators and in-flight maintenance technicians.

The Rivet Joint fleet is currently undergoing significant airframe, navigational and powerplant upgrades which include re-engining from the TF-33 to the CFM-56 engines used on the KC-135R and upgrade of the flight deck instrumentation and navigational systems to the AMP standard. The AMP standard includes conversion from analog readouts to a digital “glass cockpit” configuration.

All Rivet Joint airframe and mission systems modifications are overseen by L-3 Communications (previously Raytheon), under the oversight of the Air Force Material Command. Background

The current RC-135 fleet is the latest iteration of modifications to this pool of –135 aircraft going back to 1964. Initially employed by Strategic Air Command to satisfy nationally tasked intelligence collection requirements, the RC-135 fleet has also participated in every sizable armed conflict involving U.S. assets during its tenure. RC-135s were present supporting operations in Vietnam, the Mediterranean for Operation El Dorado Canyon, Grenada for Operation Urgent Fury, Panama for Operation Just Cause, and Southwest Asia for Operations Desert Shield and Desert Storm. RC-135s have maintained a constant presence in both Southwest Asia and in the area of the Balkans since the early 1990s.

All RC-135s are assigned to Air Combat Command. The RC-135 is permanently based at Offutt Air Force Base, Neb. and operated by the 55th Wing, using various forward deployment locations worldwide. General Characteristics

Primary Function: Reconnaissance Contractor: L-3 Communications Power Plant: Four Pratt & Whitney TF33-P-5 turbofans Thrust: 16,050 pounds each engine Unrefueled Range: 3,900 miles (6,500 kilometers) Length: 135 feet (41.1 meters) Height: 42 feet (12.8 meters) Maximum Takeoff Weight: 297,000 pounds (133,633 kilograms) Wingspan: 131 feet (39.9 meters) Speed: 500+ miles per hour (Mach.66) Flight Crew: Five (augmented) - three pilots, two navigators Mission flight crew: 21-27, depending on mission requirements, minimum consisting of three electronic warfare officers, 14 intelligence operators and four inflight/airborne maintenance technicians Unit Cost: unavailable Date Deployed: Initial RC-135 conversions from 1964-1968; V/W configurations, 1981 Inventory: Active force, 14; Reserve, 0; Guard, 0

A couple of notes on this incident from an old Korea hand...

First, the fact that the MiGs got so close is stunning. RC-135 crews have different ROE for each type of mission they fly. Fighters from some countries are allowed to come alongside (Russia, for example), since their pilots are professional and don't display hostile intent. However, the most restrictive ROE in the RC-135 community pertains to North Korea. I've been told that the RJs have standing orders to bug out if there is the slightest indication of hostile intent from North Korean aircraft. I haven't been privy to their ROE in quite a few years, but its seems to me that this type of intercept is one that RJ would normally avoid. One reason for the tight ROE is that 1969 incident, when NK MiGs downed an EC-121 "College Eye" aircraft off the Korean coast. For those who don't remember, the College Eye was a forerunner of AWACS, built on an old Constellation airframe.

I'd sure like to know how the NK managed to get so close. The RC-135 backend crew (EWOs, linguists and assorted ELINT types) continuously monitor the voice and emission environment during their mission. These folks are world-class, and (again) they typically bug out if the NK's show any signs of doing anything unusual. My guess is that the NK's must have used a comm-out launch, with a high speed run to intercept, giving the RJ crew minimal time to react. It would also be helpful to know if the intercept took place over the Yellow Sea, or the Sea of Japan. Over the Yellow Sea, there is far less maneuvering room, due to the proximity of Chinese airspace.

And here's a final point for current USAF types, particularly those in the Far East: whatever happened to PARPRO alert. For many years, Kadena-based F-15s sat alert at Osan AB, Korea, for the purpose of intercepting NK MiGs if they went after an RC-135 or other recce platform. During my tenure in Korea, the Kadena boys passed the mission to Kunsan-based F-16s. I was later told that PARPRO alert was eliminated, due to the "decreased" threat from the DPRk. Bet you a dollar we've got F-15s or F-16s on alert now.....

"the first such intercept since 1969 - happened in international air space over the Korean peninsula.

Stay alert, their next escalation may be a Pueblo incident or taking an axe our soldiers in Panmunjom."

In 4/69, a Navy EC-121, a counterpart of the C-135 flew a track along the coast of Korea. It was based out of Atsugi, Japan. There were 31 crewmembers. They were outside any claim to territorial waters of the Kor Coms.

Two Mig 21-s (25's?) came out to greet them. I was up in the air about to land at Danang in SVN and our pilot turned on the PA; the last transmission we heard was: "we have just confirmed that we have been locked onto."

All gone.

I flew on the same plane along the coast of NVN 4 days earlier, with the same crew.

Remember PR-21.