Check-In Procedure

A) Check In.

(1) The purpose of check in is for aircrew and TAC C2 airspace control elements to establish contact, allow the airspace element to establish accountability of the airborne asset, and to pass critical information to the aircrew before handoff to a final mission controller.

1. TAC C2 will verify position and identity of the aircraft.
2. TAC C2 will route the aircrew to their mission area.
3. The aircrew will gain updated information for their mission area.
4. The aircrew can check secure communication systems

(2) The aircrew should establish communication with TAC C2 on a dedicated check-in NET. Dedicated NETs support TACADMIN without interfering with employment.

(3) Once all tactical information has been relayed to the check-in aircraft, TAC C2 will switch the aircrew to the final controller tactical NET.

NOTE: When checking in with the final controller, the on-coming aircraft is assumed to be TACADMIN complete.

(4) For continuous operations (e.g. lane handoff), TAC C2 should consider passing big-picture information before pushing air assets to the tactical NET.

(5) Check in should accomplish the items in table 2 before and after mission execution.

Table 2. Check-In Procedures
1.	Ensure positive friendly identification.
	a.	Correct or valid response to IFF (i.e., modes 1, 2, 3A, 4, 5, and S).
	b.	PPLI is present on Link 16 or similar data link systems.
	c.	Secure voice with radar correlation.
	d.	Authentication procedures (e.g., challenge and reply, time, or ISOPREP).
	e.	Adherence to ACO.
	f.	Adherence to briefed sanctuaries (e.g., TL, TR, MRR, or LLTR).
2.	Accomplish ALPHA CHECK from BULLSEYE.
3.	Verify WORDS received via digital means (primary; e.g., J28.2) or voice.
4.	Provide safety-of-flight information (e.g., airspace coordinating measure, airspace changes, or block changes).
5.	Check weather.
	a.	Combat. Update operating area weather that impacts the briefed plan.
	b.	Training. Relay the weather plan or a war call.
6.	Accomplish a post-mission in-flight report.
Notes: 1.     Specific procedures are outlined in the SPINS. 2.     ALPHA CHECK correlation is defined as within 3nm. Solving for correlation rests with the aircraft checking in. 3.     Mulitple TAC C2 NETs may be used to accomplish these check-in tasks.
Legend: ACO – airspace control radar IFF – identification, friend or foe ISOPREP – isolated personnel report LLTR – low-level transit route MRR – minimum-risk route nm – nautical mile			PPLI – precise participant location and identification SPINS – special instructions TAC C2 – tactical command and control TL – transit levels TR – transit route

B) Aircrew Check In with TAC C2

(1) The full aircraft check-in format should include mission number and aircraft number and type, position and altitude, ordnance, PLAYTIME, capabilites, and abort code.

Note: MNPOPCA is a mnemonic useful for remembering the order of check in. (See table 3.)

(2) AS FRAGGED Check In. AS FRAGGED means the unit or element is performing as briefed, in accordance with the air tasking order (ATO) or air plan.

(a) Use an abbreviated aircraft check when aircraft are on a published ATO or air plan.

(b) Check In with the aircrew's mission number, AS FRAGGED, and request an ALPHA CHECK from the assigned BULLSEYE. The ALPHA CHECK provides aircrew a position system check.

Check In AS FRAGGED Aircraft: "MISER, HORNET 1, MISSION NUMBER 5-1-1-1, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK DEPOT." TAC C2: "HORNET 1, MISER, CONTACT, ALPHA CHECK DEPOT 270/30." Aircraft: "HORNET 1."

(3) Aircrew must check in "with exceptions" if there are deviations.

(a) Communicate pertinent exceptions to the current mission.

(b) The following deviations should always be communicated by aircrew and controllers at check in:

• • • • Number of aircraft (e.g., a three-ship flight when four-ships are anticipated).
      • Ordnance. WEAOPNS YELLOW or RED or changes to the tasked loadout.
      • PLAYTIME. FUEL YELLOW or RED.
      • Capabilites (e.g., TIMBER SOUR, NEGATIVE JACKAL, GADGET BENT).
      • Other pertinent mission-specific exceptions (identify them during mission planning).

(c) The following is an examble of a check in with exceptions.

Example #1: Check In with Exceptions Aircraft: "MISER, EXXON 1, MISSION NUMBER 6-1-1-1, CHECKING IN WITH EXCEPTIONS, REQUEST ALPHA CHECK BULLSEYE." TAC C2: "EXXON 1, MISER, ALPHA CHECK BULLSEYE 270/30, CONTINUE WITH CHECK IN." Aircraft: "EXXON-1, OFFLOAD, FRAG MINUS 30 K."1

(d) The following is an examble of a check in with controller exceptions:

Example #2: Check In with TAC C2 Exceptions Aircraft: "MISER, HORNET 1, MISSION NUMBER 5-1-1-1, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK BULLSEYE." TAC C2: "HORNET 1, MISER, ALPHA CHECK BULLSEYE 270/30." Aircraft: "HORNET 1." TAC C2: "MISER, TIMBER SOUR." Aircraft: "HORNET 1."

(4) Unmanned aircraft systems (UAS) should check in with TAC C2 via tactical chat using the same format.

Unmanned Aircraft System (UAS) Check In Example <#UAS_OPS Chat Room> MUSTANG 01: KINGPIN, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK BULLSEYE.

¹In this case a refueling aircraft might have 85k lbs of fuel planned but only checks in with 55k lbs of fuel for offload.