41st VSFS/Pilot & RIO Communications
More actions
01 / Purpose
The Intercommunications System (ICS) allows the Pilot and RIO to operate from the same mental picture.
ICS communication must be:
Early, Concise, Standardised, Actionable and Predictable
The crew should not attempt to narrate every cockpit action. Information is transmitted when it changes a decision, affects safety, supports the mission or confirms that an important action was understood.
The basic communication contract is:
The Pilot communicates intentions and decisions. The RIO communicates the situation and recommendations.
This page covers internal crew communication. It does not replace MTTP/ACC, which defines communication with controllers, flight members and external agencies.
02 / ICS Setup and Check
The F-14 ICS provides normal, backup and emergency communication between the cockpits.
Before taxi, both crewmembers confirm:
ICS audio is clear, HOT MIC or COLD MIC is selected as briefed, Required radio audio can be heard, External radio ownership is established, Radio assignments are understood and a backup plan exists for ICS failure.
Pilot: ICS check
RIO: Loud and clear. Check
Pilot: Loud and clear
When using HOT MIC, both crewmembers must control background noise, breathing, keyboard noise and unrelated conversation.
When using COLD MIC, critical information must not be delayed because a crewmember forgot to key the ICS.
03 / Internal Transmission Types
Internal transmissions use five basic forms.
Informative: Provides information. A response is only required when the information is critical or uncertain.
Fuel eight-point-zero, five hundred above Joker.
Interrogative: Requests information or a decision.
Confirm north group targeted?
Recommendation: Provides a proposed action for the responsible crewmember.
Recommend right turn heading zero-three-zero.
Directive: Orders an immediate action under established authority.
Break left, missile!
Challenge: Identifies an unsafe action, incorrect assumption or unresolved restriction.
Hold fire, identification incomplete.
04 / Communication Priority
The highest-priority transmission interrupts all lower-priority communication.
1. Immediate survival:
Missile, collision, terrain, fire, ejection
2. Immediate tactical threat:
Threat group, radar lock, second bandit, friendly conflict
3. Aircraft or weapon limitation:
Engine problem, radar failure, invalid identification, weapon malfunction
4. Tactical decision:
Commit, targeting, weapon recommendation, extend, recover
5.Mission management:
Fuel, navigation, timing, frequency change
6. Administrative information:
Non-critical setup, explanation or debrief discussion
Administrative discussion stops during:
Takeoff, Close formation, Air-to-air refuelling contact, Weapon employment, Defensive manoeuvring, Visual combat, Final approach, Aircraft emergencies, etc...
05 / Acknowledgements and Readbacks
The Pilot and RIO acknowledge information when confirmation is required.
Copy: Information received and executing the request
Unable (state reason): Action cannot safely or practically be performed
Stand by: Transmission received, response temporarily delayed
Say again: Repeat the last transmission
Negative: Information or requested action is incorrect or rejected
The following normally require acknowledgement or readback:
Emergency calls, Defensive direction, Heading or altitude instructions, Target assignment, Commit or disengagement decision, Weapon-employment restriction, Fuel minimum, Frequency change, Task transfer
Example:
RIO: Turn right heading zero-three-zero.
Pilot: Zero-three-zero.
Silence does not mean understanding.
06 / Information Formats
Pilot Intent
The Pilot communicates major manoeuvres before they occur whenever time permits.
Format:
ACTION, DIRECTION OR PARAMETER
Examples:
Pilot: Crank right.
Pilot: Left thirty degrees, climbing angels twenty-five.
Pilot: Extending south.
Pilot: One circle, descending.
This allows the RIO to maintain radar contact, manage sensor limits and understand the intended tactic.
RIO Recommendation
Format:
RECOMMEND ACTION, REASON
RIO: Recommend left twenty degrees. Target approaching right radar limit.
RIO: Recommend extend south. Fuel approaching Bingo.
Contact Information
For an ownship-relevant contact, use BRAA:
GROUP OR CONTACT, BRAA, ALTITUDE, ASPECT, DECLARATION OR STATUS
Example:
RIO: North group, BRAA three-four-zero for fifty-five, twenty-eight thousand, hot, hostile.
For the shared tactical picture with wingmen or tactical, use BULLSEYE in accordance with MTTP/ACC. Example:
RIO: Additional group, Bullseye two-seven-zero for forty, twenty thousand, track east, bogey.
Identification terminology must match MTTP/ACC and the mission Rules of Engagement.
Steering
Format:
TURN DIRECTION, HEADING
Examples:
RIO: Turn right heading zero-three-zero.
Pilot: Zero-three-zero.
For small corrections:
RIO: Come right ten degrees.
A direction should be included whenever ambiguity could cause the Pilot to turn the long way.
07 / Ground Operations and Departure
Before taxi:
Pilot: Ready front.
RIO: Ready back.
During taxi, the Pilot communicates unexpected routing or aircraft issues. The RIO manages external communication and monitors traffic, navigation and checklists.
During takeoff, only critical information should interrupt the Pilot.
Examples:
RIO: Engine instruments normal.
RIO: Traffic crossing, abort!
08 / Transit and Mission Administration
During transit, the RIO provides information before it becomes a problem.
RIO: Waypoint three, thirty-five miles, ten degrees right.
RIO: Two miles right of course. Recommend left ten degrees.
Timing
RIO: Two minutes behind timeline.
RIO: Push point in three minutes.
Fuel
RIO: Fuel eight-point-zero.
RIO: Five hundred above Joker.
RIO: Joker.
RIO: Bingo. Recommend immediate recovery.
The Pilot acknowledges fuel thresholds and states the decision.
Pilot: Copy Joker. One engagement remaining.
Pilot: Bingo. Recovering.
Frequency Changes
The RIO coordinates the internal frequency change. The external call and flight check follow MTTP/ACC.
09 / Tactical Picture Updates
The RIO maintains the Pilot's usable tactical picture. The Pilot should not need to ask where the primary threat is or which group the aircraft is supporting.
A picture update is required when:
A relevant group appears, A group splits or joins, A group changes aspect, A new group becomes the priority threat, The assigned target changes, A friendly aircraft affects employment, Identification changes, Track fades, The picture becomes uncertain, The aircraft approaches a tactical decision point.
Format:
NUMBER OF GROUPS, PRIORITY GROUP, POSITION, STATUS, RECOMMENDATION
Example:
RIO: Two groups. Primary north group, BRAA three-four-zero for fifty-five, twenty-eight thousand, hot, hostile. Secondary east group, BRAA zero-one-five for seventy, twenty-two thousand, flanking east. Recommend commit target north.
Pilot: Roger, commiting north group.
Only tactically relevant contacts are reported. The RIO should not flood the Pilot with every radar return.
Uncertain Picture
Uncertainty must be stated immediately.
RIO: North group faded, last seen BRA 270, 43 miles, 24'000
RIO: Picture uncertain. Datalink and radar do not correlate.
RIO: Unable to confirm target identity.
10 / Commit and Targeting
COMMIT authority is determined by the mission brief and MTTP/ACC. Internal communication does not replace the required external authority.
RIO Recommendation
RIO: North group meets commit criteria. Recommend commit.
If the aircraft or Pilot holds the required authority:
Pilot: Commit north group.
If higher authority is required:
Pilot: Request commit north group.
The RIO then makes the required external transmission.
External Directive Received
RIO: Lead directs commit north group.
Pilot: Committing north group.
Target Confirmation
RIO: North group targeted.
RIO: Sorted lead contact.
RIO: Target changed to trail contact.
Any target change must be stated explicitly. The Pilot should never be expected to infer that the RIO has switched contacts.
11 / Intercept Steering
The RIO provides steering that creates the required intercept geometry. The Pilot advises before manoeuvring whenever the change may affect radar support.
Heading: Turn right heading zero-three-zero.
Altitude: Recommend climb angels twenty-five.
Speed: Recommend accelerate.
Radar limit: Target approaching left radar limit.
Timeline: Inside planned timeline. Recommend crank right.
The Pilot communicates execution:
Pilot: Zero-three-zero.
Pilot: Climbing angels twenty-five.
Pilot: Crank right.
If unable:
Pilot: Unable turn, maintaining formation.
The RIO then develops another solution rather than repeating an impossible instruction.
12 / Weapon Employment
Air-to-Air
Before recommending a shot, the RIO should communicate the information required for a safe employment decision:
Correct target Identification status Weapon status Range and geometry Friendly proximity Sensor support
Example:
RIO: North group lead contact hostile. Phoenix selected, in parameters, friendlies clear. Recommend shoot.
Pilot: Fox Three.
After launch, the RIO reports only information affecting the weapon or next action.
RIO: Track good.
RIO: Target turning cold.
RIO: Track lost, weapon support degraded.
RIO: Recommend out south.
A shot recommendation is not weapon-release authority.
Air-to-Surface
RIO: Target captured.
RIO: Target coordinates verified.
RIO: Laser armed, code one-six-eight-eight.
RIO: In launch region. Recommend release.
Pilot: In.
Pilot: Pickle.
13 / Defensive Communication
Defensive calls are immediate and use plain, direct language.
Format:
THREAT, CLOCK POSITION OR DIRECTION, ELEVATION, ACTION
RIO: Missile, six o'clock low, break left!
Pilot: Defending left.
Known survival information should not be withheld merely to preserve a rigid call sequence.
During the defence, the RIO reports:
Missile position, Additional missiles, Bandit position, Nearby friendlies
Changes requiring a different manoeuvre
RIO: Missile now five o'clock, level.
RIO: Second missile, twelve o'clock high.
The RIO should not provide routine picture information while an immediate missile threat exists.
After the threat:
RIO: Missile no longer visual. RWR clear.
RIO: Picture rebuilding.
RIO: Recommend extend south.
The phrase MISSILE DEFEATED should only be used when the crew has sufficient information to support that assessment.
The Pilot decides whether to continue defensive, extend, recommit or recover.
14 / Visual Combat
Inside the visual arena, calls must use clock position, range, elevation and movement.
Format:
CONTACT, CLOCK POSITION, RANGE, ELEVATION, MOVEMENT
RIO: Bandit, ten o'clock, one mile, low, left to right.
Pilot: Tally.
If the Pilot does not see the bandit:
Pilot: No joy.
The RIO continues the talk-on:
RIO: Nine o'clock, half mile, level.
The RIO gives immediate priority to additional threats.
RIO: Second bandit, two o'clock high!
Friendly aircraft are called as VISUAL or BLIND. Hostile or target aircraft are called as TALLY or NO JOY, in accordance with MTTP/ACC.
The Pilot communicates the geometry so the RIO can support the fight.
Pilot: One circle, descending, northbound.
Pilot: Bandit switched.
15 / Aircraft and System Status
Aircraft and sensor problems are communicated using:
SYSTEM, CONDITION, TACTICAL EFFECT
Aircraft status and system faults should be communicated in plain english to be as efficient as possible.
The receiving crewmember acknowledges and states the resulting action.
16 / External Communication Ownership
The RIO normally manages external communication with:
ATC, Carrier agencies, Tankers, TACC2, AWACS and GCI, Flight and package members, JTAC or FAC, Other mission agencies
The Pilot may transmit when required by radio configuration, immediate tactical need, safety, RIO task saturation or positive task transfer.
Transfer to other crewmember
RIO: You've got radios.
Pilot: I've got radios.
The previous owner retains the task until the transfer is acknowledged.
External transmissions must use the formats, callsigns and brevity defined in MTTP/ACC.
17 / Air-to-Air Refuelling
During rendezvous, the RIO provides navigation, tanker position and communication.
RIO: Tanker BRAA zero-one-zero for twelve, angels twenty.
RIO: Tanker visual, twelve o'clock, five miles.
During close formation and contact, ICS traffic is reduced.
Useful calls include:
RIO: Fuel six-point-zero.
RIO: Traffic moving on right side.
The RIO should not continuously coach small position corrections unless requested. The Pilot owns aircraft position and contact.
18 / Recovery and Landing
During recovery, the RIO communicates:
Recovery instructions, Navigation, Fuel, Traffic, Checklist status, Aircraft configuration concerns, Divert or emergency information
In addition, he communicates with the LSO or Marshal.
19 / Emergency Communication
Emergency communication has priority over every other transmission.
Emergency commands are short:
Pull up!
Break right, traffic!
Fire left engine!
Eject, eject, eject!
Do not use recommend when immediate action is required.
After the immediate action, the crew returns to structured communication.
Pilot: Fly the aircraft, establish a safe condition and state intentions
RIO: Identify the malfunction, support the checklist and coordinate recovery
Example:
Pilot: Left engine secured. Maintaining angels ten.
RIO: Copy. Checklist complete. Nearest recovery base bearing zero-eight-zero, forty miles.
Checklist responses should be deliberate and unambiguous. Do not rush through challenge-and-response items merely to reduce ICS traffic.
20 / ICS Failure
If intercommunication is lost:
Attempt another ICS transmission. Confirm headset and volume settings. Select the backup amplifier if required. Select emergency amplification if the normal and backup paths fail. Use an available radio as an internal backup. Apply the pre-briefed lost-communication contract.
When the emergency amplifier is used, normal audio functions may be reduced and HOT MIC may be unavailable.
If communication cannot be restored, the Pilot retains aircraft control and makes conservative mission decisions. The RIO continues sensor, navigation and threat support to the extent possible.
An unbriefed no-ICS tactical engagement should not continue unless immediate mission or safety requirements demand it.