VT-86 ADMIN AND TACADMIN STANDARDS (TACSOP)

V T - 8 6 A D M I N A N D T A C A D M I N S T A N D A R D S 1

U P D A T E D J U L Y 2 0 2 1

VT-86 ADMIN AND TACADMIN STANDARDS (TACSOP)

Overview:

1. All ADMIN and TACADMIN comm at VT-86 shall be IAW this document.

2. This document outlines general procedures unique to the T-45C and VT-86. Reference the

various stage Stan Notes for further direction on specifics in each stage. This document is meant to be a

common reference throughout the UMFO syllabus and students should refer to it as required throughout

the syllabus.

3. COMM 1 is referred to as PRI and COMM 2 is referred to as AUX.

4. All comm examples assume a section at NPA with their tactical frequency (TAC) in AUX unless

specified otherwise. The tactical callsign (TAC C/S) refers to the section’s tactical callsign i.e. HEAT.

The callsign (C/S) refers to a specific member’s callsign i.e. HEAT 11.

Summary of Changes:

1. July 2021

a. Emergencies and contingencies section added to ADMIN.

i. Lost communication procedures

ADMIN

PREFLIGHT

Standard sequences, waypoints and GEOREFs:

1. Waypoints 1-16 and sequence 1 are available for student use. Waypoints 17-60 and sequence 2

and 3 must match the T-45 Standard Waypoint Load and shall be reset post flight if changed.

2. GEOREFs should be used to identify suitable emergency airfields along the route of flight and

the flight’s primary divert. KNPA as a GEOREF is not required.

3. Unless otherwise briefed, WYPT 59 (BFM) should be selected as A/A WYPT.

Standard HSI setup, waypoint usage, HDG and CALT bugs:

1. HSI setup

a. Takeoff: 40NM scale, TCN boxed, waypoint set to first expected navigation point, CRS line

set to active runway and boxed in PLAN mode. For multiplane takeoffs reference

TACADMIN section for A/A TCN usage.

b. Enroute: Scale should be set to the lowest scale to show the appropriate NAVAID, not less

than 40NM.

c. Approach/landing: Local sequences should remain boxed unless the IP requests or briefs to

deselect them during RTB. 10NM scale should be used when within 10NM.

i. VFR/GCA: Plan mode, WYPT/TCN selected as appropriate, CRS boxed and set to

runway heading

ii. IFR Approach: As required for the approach being flown. WYPT can be set to the

field for SA, but the approach must be flown from the appropriate navigation source.

2. HDG bug: Should be used to input the heading the flight is assigned. Once the flight is no longer

on an assigned heading, the HDG bug should be deselected.

3. CALT: Should be used to input the altitudes the flight is cleared to. If the flight is level, the

CALT may be used to input the climb out altitude instructions after an approach.


U P D A T E D J U L Y 2 0 2 1

LAW and BINGO changes:

Each change to the BINGO bug or LAW will be entered, verified and then verbalized over ICS. LAW

will be set to 200’ for takeoff. Passing 5,000’ AGL on the climb out LAW will be set to 5,000’. If the

flight never passes 5,000’ the LAW shall be set to 10% below the assigned altitude.

ADI/HUD repeater:

The HUD repeater may be used for all phases of flight and is the preferred attitude reference.

ON DECK

Clearance call:

PRI: “Clearance, ROKT XX, (single/flight of x), (stereo route/IFR to X) on request”

Wing will strive to copy ATIS and clearance prior to check-in. Once complete, monitor base on PRI.

Following element check-in and when ready to taxi:

PRI (BASE): “Base, ROKT XX, side XX, XX, outbound”

AUX: “TAC C/S, (ground freq), PRI”

PRI: “Ground, ROKT XX, (single/flight of x), taxi, (location if required), with (information)”

Reference VT-86 SOP for taxi intervals.

Approaching Holdshort:

AUX: “TAC C/S, (TWR Freq), PRI”

Any member of the flight needing additional time at the holdshort may request it as follows:

AUX: “C/S, needs (time)”

Ready for Takeoff:

PRI: “TWR, ROKT XX, (single/flight of x), (location if required), takeoff”

The standard multiplane takeoff is a 7 second interval go. Reference VT-86 SOP for amplifying

information.

ENROUTE

Unless otherwise briefed, join into parade at 250 knots.

With entire flight safely airborne:

PRI: “Departure, ROKT XX, (flight of X), passing (alt in hundreds of feet) for (altitude in

thousands of feet)”

Frequency changes:

All non-ATC directed frequency changes will be directed by lead as follows:

(i.e. switching back to ATC from a discrete)

AUX: “TAC C/S, (freq), PRI/AUX”

No acknowledgement is required.

Check-in to Area:

Reference stage specific STAN notes.


U P D A T E D J U L Y 2 0 2 1

MISSION CONDUCT

Check-in on safety of flight (SOF) or by exception:

AUX: “TAC C/S, check PRI”

PRI: “(tactical callsigns in order)”

Joker/BINGO:

When JOKER fuel is reached, students will advise and acknowledge via TAC freq. Once acknowledged,

the bingo bug will be set to the briefed BINGO setting.

Wingman first to reach JOKER:

AUX (wingman): “C/S, JOKER”

AUX (flight lead): “C/S, copy JOKER, reset BINGO”

Lead is the first to reach JOKER

AUX: “TAC C/S, reset BINGO”

RTB

ATIS and base call post fence out:

AUX: “C/S, off AUX”

To direct wingman off AUX for base and ATIS:

AUX (flight lead): “C/S, you are cleared off AUX for base and ATIS”

Call to base on RTB:

AUX: “Base, ROKT XX, on deck in (time), (aircraft status)”

No report of aircraft status is required if the aircraft is ‘up.’ If the aircraft is down, use plain language to

indicate mission status.

Reporting ATIS to flight:

If the wingman was cleared off for ATIS, they will switch to TAC and let lead know they are back up.

AUX (wingman): “C/S back up, with (identifier)”

AUX (flight lead): “Ready to copy”

AUX (wingman): “(VFR or IFR w/ weather conditions), runway (XX), altimeter XXXX”

If lead gets ATIS, pass the information once back on TAC.

AUX (flight lead): “C/S back up, with (identifier), (VFR or IFR w/ weather conditions), runway

(XX), altimeter XXXX”

Platform:

When approaching 5,000’ AGL:

ICS: “Approaching PLATFORM”

Once LAW has sounded and confirmed operation of the RADALT:

ICS (NFS): “Good tone, LAW reset XXX”

ICS (IP): “Good tone”

The LAW will be set to 10% below the AGL altitude you are descending to, rounded to the nearest 50’. In

mountainous terrain, LAW may be set as necessary to ensure terrain clearance and avoid constant LAW

warning tones. When on a step down descent, LAW will be stepped down not to activate. For precision

and non-precision approaches, LAW will be set per FAM FTI. The only two times LAW should activate

are descending through PLATFORM and on final.


U P D A T E D J U L Y 2 0 2 1

Initial Check-in with Tower:

Initial check-in with tower is per the FAM FTI. If conducting an abeam PA, coordinate with tower upon

initial check-in. Examples are in TAB A.

Low Key:

The comm for low key is:

PRI: “Tower, ROKT XX, low key, (gear), (intentions)”

Reference VT-86 SOP for line speeds and comms on runway.

Approaching taxiway at a safe taxi speed:

AUX: “TAC C/S, base and ground when clear”

Clear of Runways:

Once your wingman is clear of the active runway:

PRI: “Ground, ROKT XX, clear of RWY XX at (location), taxi (desired location)”

AUX: “Base, ROKT XX, safe on deck, (aircraft status)”

EMERGENCIES / CONTINGENCIES

Lost Communication Procedures:

If single aircraft and no radios (NORDO), follow FAA procedures and local course rules/procedures.

To signify a radio failure when in formation, use NATOPS hand signals. All NORDO signals shall be

acknowledged by good aircraft with appropriate hand signal.

If a lead change is desired, use hand signals.

Configuration changes shall be accomplished using hand signals.

(1) Rotary movement of clenched fist followed by a head nod.

A desire by the NORDO aircraft to land immediately shall be indicated to the wingman by making a

landing motion with an open hand. An extension of the hook/hook down hand signal indicates the need

for an arrested landing.

In day VMC conditions, with no Hydraulic Electrical Fuel Oxygen Engine “HEFOE” signals, the flight

lead should take the NORDO wingman back into the break. The NORDO wingman shall take interval on

the lead out of the break. Flight lead shall indicate clearance for a NORDO wingman to land by executing

a touch and go (or full stop if fuel critical) on the cleared runway. A wave-off by lead shall indicate that

clearance to land has not been given. Lead should remain airborne until the NORDO wingman is safely

on deck (fuel permitting).

During IMC conditions or when HEFOE signals are given, all NORDO aircraft shall fly on the right wing

of the lead and should expect an enroute descent with a Ground Control Approach (GCA) final. Dirty up

should be expected eight to 12 miles from touchdown at 150 KCAS. Both aircraft shall lower the landing

gear and select half-flaps. If a HEFOE (Hydraulics) signal is passed signifying a hydraulic failure,

emergency flaps and emergency gear extension shall be performed. Dirty up should be performed VMC,

if possible. The lead shall monitor the wingman's AOA lights to fly no slower than on-speed for the

wingman. The lead should drop the NORDO off at approximately one mile and no lower than 400’ AGL

to allow the wingman to transition to the visual landing aid. The lead shall initiate flight breakup by

giving the "kiss off" signal and breaking away, which is the NORDO aircraft’s clearance to land. The lead

should climb away at 150 KCAS and 800’ AGL or below the overcast (no lower than circling


U P D A T E D J U L Y 2 0 2 1

minimums). In the event of a wave-off, the wingman should acquire the lead at his 10 or 11 o'clock for a

rendezvous.

HEFOe signals should be interpreted as follows:

(1) Hydraulics - Assume HYD1 failure, perform emergency landing gear extension

(2) Electrical - Assume generator failure

(3) Fuel - Assume low fuel state

(4) Oxygen - Assume no pressurization/On Board Oxygen Generating System (OBOGS) failure

(5) Engine - Assume EGT/RPM Warning light

In the case of a NORDO aircraft in the target area, the NORDO aircraft should orbit 1,000’ above the

highest pattern altitude and hold in the direction of the pattern. Hold opposite the pattern if join-

up/assistance is required. If NORDO in Special Use Airspace (Warning Area, Military Operations Area)

proceed to the briefed lost communications/lost sight waypoint and hold, left hand turns if just NORDO

and right hand turns if NORDO with an emergency.

TACADMIN

ON DECK

Preflight:

Full TAC C/S should be used on all multi-plane events to the max extent possible. Students should

choose and brief an appropriate TAC C/S which consists of a name and a two digit number that matches

the ROKT two digit numbers. The mission number is the date followed by your ATC callsign number.

For example, on the 25th, ROKT 41 is mission number 25-41. If utilized for your event, ensure

deconfliction of A/A TCN, datalink information and TAC FREQ from all other events during your time

of flight. No later than 30 minutes prior to brief time, provide SDO/CDO with flight TAC

frequency, datalink frequency, BUNO and ID on the E-Schedule behind the SDO. The datalink

frequencies available for use are 1437 and 1442. The ID will be determined by place in flight and

counting up (e.g. lead = 3, wing = 4, use the lowest available ID during your time of flight, starting with

three). BUNO will match the last two digits of your ROKT callsign. In order to deconflict the A/A TCN,

lead will set the last two digits of your ROKT callsign and wing will set lead’s plus or minus 63 (e.g.

ROKT 11 will set 11/74 and ROKT 71 will set 71/08; 129 is the highest available A/A TCN channel).

If executing an out and in flight, update the BUNO and ID to match your callsign and position in flight

for each leg.

Initial check-in:

10 minutes prior to the scheduled takeoff time, Lead will initiate a check-in on AUX as follows:

AUX: “TAC C/S, check AUX, (tactical callsigns in order), (alibis)”

Hold the check-in if any aircraft is conducting PC checks during briefed check-in time. Check-in can be

conducted prior to briefed check-in time if all aircraft are in the marshal area.

In Division, Dash 3/4 should give proceeding flight member 2-3 seconds to check-in before checking-in

themselves.

NAV check:

Flight leads will brief a common reference waypoint TO which the NAV check will be conducted.

AUX: “TAC C/S, NAV check (waypoint name), (azimuth and range TO reference waypoint)”


U P D A T E D J U L Y 2 0 2 1

The tolerance for azimuth and range while on deck is 3 degrees and 3 NM.

Wing of a section or Dash 3 of a division should respond to a NAV check as follows:

AUX: “C/S”

Wing of a section or Dash 3 of a division may advise lead of a NAV check discrepancy as follows:

AUX: “C/S, shows (waypoint name), (azimuth and range TO reference waypoint)”

Alpha check:

Flight leads will brief a common reference waypoint FROM which the alpha check will be conducted.

AUX: “TAC C/S, alpha check, (bullseye), (azimuth and range FROM bullseye)”

The tolerance for azimuth and range while on deck is 3 degrees and 3 NM.

Wing of a section or Dash 3 of a division should respond to an alpha check as follows:

AUX: “C/S”

Wing of a section or Dash 3 of a division may advise lead of an alpha check discrepancy as follows:

AUX: “C/S, shows (bullseye), (azimuth and range FROM bullseye)”

SMS setup:

Setup the SMS page as follows, or as briefed:

A/A – RTGS and 31 ft. wingspan

A/G – BOMB/GUN, CCIP, QTY 4 per side, THGT as field elevation

VMTS setup:

The NFS is responsible for all VMTS setup. NFS is responsible for selecting the RDR page (once

available) and selecting OPR.

Datalink/RADAR setup:

The students are responsible for all data link setup. Ensure the BUNO, FREQ and ID are set per the brief.

Upon completion of the BIT, set the radar sets as follows:

MRM: RWS/6B/80NM/140Az/16s

SRM: RWS/6B/20NM/140Az/16s

The IP shall box T/R.

VREC setup:

Students are responsible to check and set displays as briefed. For every flight, the RMM shall be on from

takeoff to landing.

A/A TACAN:

For multiplane takeoffs check TACAN operation with the home field TACAN, and then switch to A/A

TCN prior to takeoff. If not receiving A/A TACAN approaching the hold short:

AUX: “C/S, negative yardstick” (all aircrew check A/A settings; if no joy note as alibi)

Utilize departure field waypoint, WYPT boxed, with a course line set for departure runway.

ENROUTE

Environmentals:

All flight members should assess and record the items listed below once in the operating area.

a. Sun azimuth and elevation

b. Cloud decks in operating area

c. Winds at altitude in operating area

d. Altimeter

Fence in:

Lead NFS will fence in the flight prior to reaching the operating area.


U P D A T E D J U L Y 2 0 2 1

AUX: “TAC C/S, fence in”

The ‘fence in’ call is a directive call to prepare all combat systems, and does not require a verbal

acknowledgement. Execute the ‘fence’ checklist. NFS should verbalize checks over ICS unless otherwise

briefed.

Fence checklist:

1. MSTR ARM.....................SET AS BRIEFED

2. A/A TACAN…….……. SET AS BRIEFED

3. DISPLAYS…..………… SET AS BRIEFED

4. BINGO……….…...…… SET AS BRIEFED

5. RECORDERS………… SET AS BRIEFED

6. SMS/MSTR MODE…….SET AS BRIEFED

7. SQUAWK/STROBE...….SET AS BRIEFED

*Reference stage specific Stan Notes for Fence In weapon system set-up.

G-Warm:

To initiate the G-Warm and clear wing to spread:

AUX (Lead IP): “TAC C/S, reference (HDG), accel G-Warm”

With wing established in combat spread, lead unloads to ~0.5 G at MRT until 10 degrees nose

low

Wing will unload to maintain lead on the horizon at MRT

At 350 KIAS lead will initiate the first 90 degree turn with:

AUX (Lead IP): “TAC C/S, 90 (right/left), go”

Both aircraft will roll and set a 4G, 10 degrees nose low turn for 90 degrees of heading change in

the direction called by lead.

After 90 degrees of turn, both aircraft will roll wings level, staying nose low until 400 KIAS then

smoothly pitch up to level flight.

Lead will initiate the second turn with:

AUX (Lead IP): “TAC C/S, resume”

The section will then execute the second half of the G-Warm for 90 degrees of heading change. Both

aircraft will execute a level pull peaking to 6G, then ease and maintain 4G. Both aircraft have one attempt

to achieve 6G, then must ease the pull to sustain 4G.

Fenced in:

Upon completion of the G-Warm the lead NFS will initiate fenced status:

AUX: “C/S, fenced in, (fuel state), good ‘G’(alibis)”

Flight members echo lead’s call in order

The ‘fenced in’ call completes the TACADMIN phase of flight, indicating all members are ready for the

tactical phase and have completed an assessment of themselves, the environment, their aircraft, weapons

and systems.

Post ‘fenced in’ lead will check the flight in on SOF frequency.

AUX: “TAC C/S, Check PRI”

PRI: “C/S” (Lead)

PRI: “C/S” (Wing)

AIC Check-in:

Upon completion of the positive check-in on PRI, the Lead SNFO will initiate communication with AIC.


U P D A T E D J U L Y 2 0 2 1

PRI: “SABRE, C/S, Mission Number XX-YY checking in as fragged, standing by Alpha Check

(bullseye)”

PRI (AIC): “C/S, Sabre, radar contact, 2 good tracks, Alpha Check (bullseye) XXX/YY

(bearing/range)”

PRI: “C/S, Good Alpha Check”

MISSION CONDUCT

Setting the war (AWI Flights):

Immediately following AIC check-in, the lead fighter will pass the environmental conditions over PRI.

AIC will simply acknowledge with their callsign and the bandit lead will contact the fighters. At VT-86

the Wing IP will assume the role as bandit lead, callsign Viper 1.

PRI (Lead SNFO): “C/S has the weather: Sun XXX/YY (bearing/angle above horizon), Winds

XXX/YY (from direction/magnitude), Decks/Ceilings (if applicable, or report sky clear), XX.XX

(Altimeter)”

PRI (AIC): “C/S”

PRI (Wing IP): “TAC C/S, Viper 1, welcome to your (event name), we have the (airspace name

and altitudes), bandits concur with your weather (or pass additional observations) recommend (TYPE OF

WAR*), (altimeter)”

PRI (Lead SNFO): “Fighters sets (TYPE OF WAR*), (altimeter)”

PRI (AIC): “C/S”

*The student supplement (TAB A) contains a breakdown of all war types and required comm.

Setting the war AWI examples:

Limited maneuvering:

PRI (Lead SNFO): “Heat 11 has the weather: Sun 090 at 45, winds 270 at 20 knots, sky is clear,

29.89”

PRI (AIC): “Sabre”

PRI (Wing IP): “HEAT, Viper 1, welcome to your AWI4202, we have W-155a/b from 9-FL300,

bandits concur with your weather, recommend all altitudes, 29.89”

PRI (Lead SNFO): “Fighters set the war all altitudes, 29.89”


-or-

PRI (Lead SNFO): “Heat 11 has the weather: Sun overhead, winds calm, undercast at 3k, 29.89”


PRI (Wing IP): “HEAT, Viper 1, welcome to your AWI4202, we have the WHODAT from SFC-

FL300, there is an undercast at 6k in the southern half of the airspace, bandits recommend high

war, 8k floor, 29.89”

PRI (Lead SNFO): “Fighters set a high war, 8k floor, 29.89”


Unlimited maneuvering:

PRI (Lead SNFO): “Heat 11 has the weather: Sun 060 at 30, winds 090 at 20 knots, sky is

clear,29.89”




PRI (Lead NFS): “Fighters set the war all altitudes, 29.89”


-or-


U P D A T E D J U L Y 2 0 2 1

PRI (Lead SNFO): “Heat 11 has the weather: Sun 060 at 30, winds 090 at 20 knots, undercast at

6k, 29.89”

PRI (Wing IP): “HEAT, Viper 1, welcome to your AWI4202, we have the WHODAT from SFC-

FL300,bandits concur with your weather, recommend high war, 8k floor, hard deck 11k, 29.89”

PRI (Lead NFS): “Fighters set a high war, 8k floor, hard deck 11k, 29.89”


Setting the war (BFM Flights):

After the G-Warm:

PRI (Lead IP): “TAC C/S, welcome to your (event name), TAC C/S sets (TYPE OF WAR*),

(altimeter)”

PRI (Wing IP): “TAC C/S, (TYPE OF WAR*), (altimeter)”

*The student supplement (TAB A) contains a breakdown of all war types and required comm.

Setting the war BFM example:

PRI (Lead IP): “Heat, welcome to your BFM4103, Heat 11 sets all altitudes, 29.89”

PRI (Wing IP): “Heat 12, all altitudes, 29.89”

-or-

PRI (Lead IP): “Heat, welcome to your BFM4103, we have a broken layer at 6k, Heat 11 sets

hard deck 11k, soft deck 16k, 29.89”

PRI (Wing IP): “Heat 12, hard deck 11k, soft deck 16k, 29.89”

‘OPS and G’ Checks:

Conducted periodically throughout flight as briefed:

AUX (Lead NFS): “C/S, (fuel state), good ‘G’, (new alibis)”

Entire flight responds in order.

Directing section flow:

All TACFORM shall be directed by the IP. Flow recommendations should be passed by the students on

ICS.

Mission Conduct:

For the conduct portion of the flight, refer to the appropriate STK/CAS/BFM/AWI FTI for specific

procedures or STAN notes for specific local procedures and mission specific TACADMIN.

Knock-it-off (KIO):

Anyone can direct KIO for safety of flight or training rule violation. The briefed evaluating instructor

owns KIO once training objectives are met. As most mid-air collisions occur post-KIO, it is important to

continue to maintain SA while redressing the flight. If the training is knocked off for a reason other than

training objectives met, include that in the KIO comm, not to delay termination of dynamic maneuvering.

The comm with a single element:

SOF (anyone): “Knock it off, knock it off, (C/S, reason)”

SOF (Lead IP): “C/S, knock it off”

SOF (Wing IP): “C/S, knock it off” (in order)

AUX (Lead IP): “TAC C/S, flow XXX”

The comm with multiple elements:

SOF (Anyone): “Knock it off, knock it off, (C/S, reason)”

SOF (Lead IP): “Fighters, knock it off”

SOF (Bandit/IGS INST): “Bandits, knock it off”

SOF (AIC/IGS INST): “AIC, knock it off”

AUX (Lead IP): “C/S, knock it off”


U P D A T E D J U L Y 2 0 2 1

AUX (wing IP): “C/S, knock it off” (in order)

AUX (lead IP): “TAC C/S, flow XXX”

RTB

Fence out & join up:

Lead NFS will initiate fence out at the completion of the tactical portion of the flight. The ‘fence out’ call

implies auto clearance to join into parade.

AUX (Lead NFS): “TAC C/S, fence out”

The ‘fence out’ call is a directive call to begin to secure all combat systems, and does not require a verbal

acknowledgment. Execute the fence checklist while monitoring the join. Do not change TAC FREQ or

TACAN channel during the critical phase of the rendezvous. The TACAN should be set for navigation

after a safe join is complete.

Battle Damage Checks (BDC):

BDC will be conducted on all multiplane events. Lead IP will initiate BDC via a cocked gun hand signal.

The wingman will step out to a cruise distance from lead, elevate to check the top, descend and cross

under checking the belly and then elevate on the other side checking the top again, remaining on that side.

The wingman will pass a thumbs up or communicate any problems. The flight lead will pass the lead to

the wingman, once given the cocked gun hand signal, execute BDC and be given the lead back upon

completion. Lead will maintain responsibility for SOF/ATC communications throughout the BDC.

If the formation is a flight of three, BDC will be initiated from fingertip. Once given the signal, dash 3

will step out to a cruise distance from lead elevate to check the top of lead, descend and cross under lead

and dash 2 checking the bellies and then elevate on the other side checking the top of dash 2, and then

return to the original position in the formation. Once given the signal dash 2 will step out to a cruise

distance from lead descend and cross under checking the belly of dash 3 and then elevate checking the top

of dash 3, and then return to the original position in the formation.

If the formation is a division, BDC can be initiated from fingertip or fluid 4 and shall be briefed

accordingly.

Fenced out:

At the completion of the BDC, Lead NFS will initiate the ‘fenced out’ call:

AUX (Lead NFS): “C/S, fenced out, (fuel state), good ‘G’”

Flight members respond in order. No amplification of aircraft status is required if the aircraft is ‘up.’ If

the aircraft is down, use plain language to indicate mission status.

AUX: “C/S, fenced out, (fuel state), good ‘G,’ down for GINA”


U P D A T E D J U L Y 2 0 2 1

TAB A: Student supplement

The following AWI example comm flow from startup to shutdown is provided below to enhance students

understanding. It is NOT to be used as a script. A division of fighters ATC callsign ROKT 41, tactical

callsign HEAT41-44 are going to W-155 to execute an AWI mission with Sabre as AIC. All ATC comm

is covered in the FTI, and if not specific to VT-86, not given in the example below.

GTS start time: Use flight leadership, if maintenance issues arise or you slide, flex or disregard the times

as appropriate.

Clearance call:

PRI: “Clearance, ROKT 41, flight of 4, NPA-13 on request”

Initial check-in:

At briefed check in time:

AUX: “HEAT, check AUX, HEAT 41”

AUX: “HEAT 42, negative clearance”

AUX: “HEAT 43, troubleshooting GINA, will be ready in two mikes”

AUX: “HEAT 44”

AUX: “HEAT, cleared as filed, squawk 5102” (this is only required because 42 did not copy)

Alpha check:

AUX: “HEAT, alpha check, Denver, 114/41”

AUX: “HEAT 43, shows Denver, 120/20”

Before you challenge an alpha check, ensure you are correct. If there is no agreement -2 breaks the tie.

AUX: “HEAT 42, shows Denver, 114/41”

NAV checks are conducted in the same manner as the alpha check.

AUX: “HEAT, NAV check, target, 060/45”

When ready to taxi:

PRI (BASE): “Base, ROKT 41, SIDE 10, 15, 16, 05 outbound”

AUX: “HEAT, three, PRI”

PRI: “Ground, ROKT 41, flight of four, taxi with C”

For home field ops, Sherman Ground knows where we are on the airfield and where we are going and that

information should be omitted.

Approaching Holdshort:

AUX: “HEAT, four, PRI”

AUX: “HEAT 44, needs 30 seconds”

It is incumbent on the flight member needing more time to notify lead when ready.

Ready for Takeoff:

PRI: “TWR, ROKT 41, flight of four, takeoff”

For home field ops, location can be omitted from takeoff call if using the full length of the runway. Plan

your takeoff call so the flight will not have to stop at the holdshort if no other aircraft are holding short.

With entire flight safely airborne:

The airborne call is NO LONGER MADE.

PRI: “Departure, ROKT 41, flight of four, passing one thousand three hundred for three

thousand”

Fence in:


U P D A T E D J U L Y 2 0 2 1

AUX (Lead NFS): “HEAT, fence in”

G-Warm:

AUX (Lead IP): “HEAT, reference 210, accel G-Warm”

AUX (Lead IP): “HEAT, 90 right, go”

AUX (Lead IP): “HEAT, resume”

Fenced in:

AUX (Lead NFS): “HEAT 41, fenced in, 2.5, good ‘G’”

AUX (-2 NFS): “HEAT 42, fenced in, 2.4, good ‘G’, negative yardstick”

AUX (-3 NFS): “HEAT 43, fenced in, 2.4, good ‘G’”

AUX (-4 NFS): “HEAT 44, fenced in, 2.5, good ‘G’”

Check-in on safety of flight

AUX (Lead NFS): “HEAT, check PRI”

PRI: (Lead NFS) “HEAT 41”

PRI: (-2 NFS) “HEAT 42”



Setting the war (AWI):

PRI (Lead SNFO): “Heat 41 has the weather: Sun 090 at 45, winds 270 at 20 knots, sky is clear,

29.89”




PRI (Lead NFS): “Fighters set the war all altitudes, 29.89”


‘OPS and G’ Checks:

AUX (Lead NFS): “HEAT 41, 1.6, good ‘G’”

AUX (-2 NFS): “HEAT 42, 1.7, good ‘G’”



Joker/BINGO:

AUX (Wingman): “HEAT 43, JOKER”

AUX (Lead IP): “HEAT 41, copy JOKER, reset BINGO”

Knock-it-off

Once training objectives are met or bandits recommend terminate:

SOF (Lead IP): “Knock it off, knock it off”

SOF (IP): “Fighters, knock it off”

SOF (IGS Instructor): “Bandits, knock it off”

SOF (IGS Instructor): “AIC, knock it off”

AUX (Lead IP): “HEAT 41, knock it off”

AUX (-2 IP): “HEAT 42, knock it off”



AUX (Lead IP): “HEAT, flow 270”

KIO for a reason other than training objectives met:

SOF: “Knock it off, knock it off, HEAT 42 BINGO”


U P D A T E D J U L Y 2 0 2 1

-or-

SOF: “Knock it off, knock it off, HEAT 42, OXYGEN Warning Light”

SOF (Lead IP): “C/S, knock it off”

SOF (-2,-3,-4 IP): “C/S, knock it off” (in order)

AUX (Lead IP): “TAC C/S, flow XXX”

Fence out & join up:

If the situation dictates (enough separation exists that the frequency swap can be completed prior to the

critical phase of the join up), direct the frequency switch prior to calling for ‘fence out’ to ensure all

members of the flight are on the same frequency for the join up.

AUX (Lead NFS): “HEAT, fence out”

Post BDC

AUX (Lead NFS): “HEAT 41, fenced out, 0.8, good ‘G’”

AUX (-2 NFS): “HEAT 42, fenced out, 0.9, good ‘G’”

AUX (-3 NFS): “HEAT 43, fenced out, 0.8, good ‘G’, down for GINA”

AUX (-4 NFS): “HEAT 44, fenced out, 0.9, good ‘G’”

Listen up for aircraft status during fence out so you can relay it to base.

RTB:

AUX: “HEAT, 15 PRI, 27 AUX”

The Lead NFS is responsible for the flight receiving ATIS and calling base.

AUX: “Heat 41, off AUX”

AUX : “Base, ROKT 41, on deck in 10, 16 down for GINA.”

AUX: “HEAT 41 back up, with A, the field is VFR, runway 7 is in use, altimeter 2986”

Initial tower check-in:

PRI: “Tower, ROKT 41, flight of four, point x-ray, request carrier with early descent”

If anyone in flight is going to low key:

PRI: “Tower, ROKT 41, flight of four, point x-ray, request”

PRI: “ROKT 41, request carrier with early descent. Dash 4, ROKT 44, will be touch-and-go to

low key”

Clear of Runways:

AUX: “HEAT, base, and ground when clear”

PRI: “Ground, ROKT 41, clear of RWY 7 at A6, taxi back to line”

AUX: “Base, ROKT 41 safe on deck, 16 is down for GINA”

Low Key:

PRI: “Tower, ROKT 44, low key, gear, full stop”

Clear of Runways:

AUX: “Base, ROKT 44, safe on deck”


U P D A T E D J U L Y 2 0 2 1

Setting the war:

The purpose of setting the war is to ensure AIC, fighters, and bandits all understand the airspace

limitations, weather, and altitude de-confliction plan in order to train safely. We will define the lateral and

vertical confines of the airspace we have been given (W-155 a/b, SFC-30k’) so no one busts the real

world airspace. We will give the weather so the bandits can setup to minimize the effect on their

presentation. In our case Sabre will also control the bandits, and if there are clouds from SFC-45k’ in the

Southern portion of the area, Sabre needs to know. Sabre would expect we will always flow North post

KIO and avoid the clouds. The type of war defines how we will fight within the already defined lateral

and vertical confines of our real world airspace. An ‘all altitudes’ war from 9k-FL300’ will frequently be

seen. Finally, we will set a common altimeter setting and will not change it throughout the fight (unless

the war is properly reset) so we can remain safely deconflicted in our blocks. We do not set ‘decks and

blocks as briefed,’ ‘limited maneuvering’ or ‘clear of clouds’ if it has not changed from what we briefed.

If the decks and blocks need to be reset due to type of war, they will be reset by the fighter lead and

echoed by all players. If we have briefed ‘unlimited maneuvering’, but due to weather cannot turn, then

we need to set ‘limited maneuvering.’

BFM: Always reference unlimited maneuvering. Floor is not referenced for BFM at VT-86.

AWI: Plan to reference limited maneuvering (180 deg of engaged turning maximum) unless otherwise

briefed.

Multi-plane weather criteria:

Weather

Type War

Restrictions

Comm

Sky clear or a few scattered clouds at any altitude.

All altitudes

None

“ … set(s) the war, all altitudes, 29.92”

Weather

Type War

Restrictions

Comm

Undercast layer ≤ 8k’

High war

Floor 2k’ > undercast layer (not required for BFM)

Hard deck 5k’ > undercast layer (highest undercast not to exceed 8k’)

“…set(s) a high war, _____ floor, hard deck_____, 29.92"

Weather

Type War

Restrictions

Comm

Undercast layer > 8k’

High war

Limited Maneuvering. Floor 2k’ > undercast layer.

“…set(s) a high war, _____ floor, 29.92"

Weather

Type War

Restrictions

Comm

Undercast layer and overcast layer

War between the layers

Limited Maneuvering. Floor 2k’ > undercast layer. Ceiling 2k’ < overcast layer.

“ … set(s) a war between the layers, _____ k’ floor, _____ k’ ceiling, 29.92”

Date post:	14-Apr-2022
Category:	Documents
Upload:	others
View:	12 times
Download:	0 times

VT-86 ADMIN AND TACADMIN STANDARDS (TACSOP)

Documents