You are on page 1of 8

27th vFighter Wing 522nd vFighter Squadron (Fireballs) 523rd vFighter Squadron (Crusaders) 524th vFighter Squadron (Hounds

of Heaven)
Prepared by Mitch Sundown Sommer th OPERATIONS OFFICER, INSTRUCTOR PILOT- 27 FW Reviewed by Mark Lawndart Eckard th COMMANDER, INSTRUCTOR PILOT - 27 FW Approved by ____________________________

rev. 20-March-2013

STANDARD OPERATING PROCEDURES


CHAPTER 1 INTRODUCTION Airpower has become predominant, both as a deterrent to war, and in the eventuality of war as the devastating force to destroy an enemys potential and fatally undermine his will to wage war. General Omar Bradley

1-1.

Purpose. As an active member and officer assigned to one of the squadrons under the 27th Fighter Wing, the following are guidelines and means set forth to capture the processes that take place in the normal course of employment. These processes are not all-inclusive and specific actions may be scenario driven. There are overlapping areas of concern that will arise in certain situations which will require a review of these procedures, and as we perform each exercise and operation we will enhance these procedures to best serve the Air Force Special Operations Command (AFSOC), Fighter Wing, Fighter Squadrons and its officer pilots. Further, these guidelines govern all squadrons within the 27th Fighter Wing without deviation.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 1

CHAPTER 2 ORGANIZATION 2-1. Chain of Command. The 27th vFW has a complete chain of command that can be viewed at any time at 27thvfw.org. Officers with questions, comments, suggestions or issues should utilize their immediate chain of command to maintain structure and to ensure the proper handling of your request. Forums. It is strongly recommended that each pilot becomes a member of 1 or more BMS-related forums. These forums are very active and contain extremely valuable information on updates, glitch fixes, hardware support, suggested settings, mods and tutorials. Conduct. The 27th FW operates under an implied Code of Conduct. As such, when a member utilizes forums and either promotes the 27th FW in any regard or speaks on behalf of the attached Fighter Squadrons on any level, it is expected that the member will conduct him/herself in a professional manner. Any member witnessed acting in a manner inconsistent with the values of the 27th FW or other forums/websites rules while being attached to the 27th FW (for example posting inappropriate threads in a forum while having in your signature anything related to the 27th FW or the attached squadrons) will have a negative impact on your standing in the Squadron and may lead to dismissal (refer to Noncompliance, Insubordination and Mutiny section regarding Dismissal). Be respectful of other flight simulators, simulator enthusiasts and both allied and rival squadrons. Kneeboard / Binder. It is strongly recommended that all pilots regardless of experience or status maintain a binder that is readily available during flight containing various documentation (at a minimum) as set forth below: -Mission Briefing Details -Emergency Procedures -Airbase / Airstrip directories with TACAN/ILS/UHF/VHF/Approach/Departure info -Threat Guides -Theater Maps -Current BMS keystrokes -Checklists (Ramp Start, Aircraft Systems, Weapons Deployment) Updates and Mods. The 27th FW will run BMS with the most current program update installed to ensure compatibility during all exercises and sorties. It is the pilots responsibility to ensure he or she has properly installed the program and is current on all updates. Although program mods are available, most of them are not sanctioned by the BMS programmers and may disrupt compatibility. As such, the 27th FW encourages each pilot not to employ them within our operations. Keystrokes. At the suggestion of the programmers of BMS, it is recommended that each pilot use or modify BMS-specific keystrokes profiles to ensure full functionality of all implemented systems within the program. Many program updates contain new functions that are not keymapped in older keystroke files or files from other Falcon-based platforms such as Open Falcon, Free Falcon and Allied Force. Page 2

2-2.

2-3.

2-4.

2-5.

2-6.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

CHAPTER 3 TRAINING AND EXERCISES

...and as water has no constant form, there are in war no constant conditions. Thus, one able to gain the victory by modifying his tactics in accordance with the enemy situation may be said to be divine. - Sun Tzu 3-1. Aircraft. The 27th FW operates the GD/LHM F-16 Multirole Fighter exclusively with its various MLUs and variants. Unless specifically directed, all tactical engagements, training exercises, campaigns and other logged time flights are to be flown using a variant of the F-16. Exceptions may include an IP during specific training operations, aggressor IPs and AWACS/Tankers.

3-2a. HOTAS. It is strongly recommended that each pilot use a HOTAS device given the amount of commands that lie within BMS. The more commands you can map to HOTAS buttons, the less time you will be spending looking down at your keyboard, not to mention having to memorize 300+ keystrokes. 3-2b. Head Tracking Devices. It is strongly recommended that each pilot uses a head tracking device (such as TrackIR or an accelerometer-based unit) as this will help maintain a high level of situational awareness and increase the realism factor. BMS is capable of 6DOF. 3-2c. Miscellaneous Equipment. There are many USB devices made for todays flight simulators and nearly all of them work well in BMS. To further enhance the pilots experience, it is recommended (but not required) to employ the use of rudder pedals, replica MFDs, various flight control panels and touchscreens in order to provide for more keystroke commands. BMS can export to many different touchscreens. Brevity. To add further realism to an already accurately modeled simulation, the use of proper brevity codes is a must for all pilots. Within the BMS documentation and on the 27th vFW website is a handbook on the use of brevity that each pilot must become fluent in and use during all operations. Vox Communications. Squadron members will use Teamspeak 3 during all operations in order to maintain comms throughout mission setup, briefings, debriefings and instruction. It is strongly recommended that each pilot uses a headset with a quality microphone in order to maintain clear communication during each session. As these sessions can last a few hours, the pilot should consider a comfortable headset. Radios and IVC. During most flights, the employment of onboard radios will be required. UHF and VHF frequencies will be determined in preflight briefings by the Flight Lead and may change during the flight based on situational needs. Host is responsible for setting up the IVC for each session.

3-3.

3-4.

3-5.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 3

3-6. 3-7.

Firewalls. In order for pilots to host, Windows firewalls should be set to allow data from BMS, Wippien and Teamspeak 3. Ramp Starts. All training exercises, tactical engagements and cooperative missions with other Fighter Wings will begin from a ramp start unless otherwise directed from the Flight Lead or IP. This is a crucial yet fundamental task that must be mastered. Flight Logs. Each pilot is responsible for the submission of properly formatted Pirep/Misrep forms after each flight. Pirep/Misrep forms and formats are available for download at the 27 vFW website and the timeliness of each report is solely the responsibility of the pilot. All flights that begin with a briefing are considered logable missions and therefore must be filed with the vUSAF regardless of the outcome of the mission or status of the pilot. Being KIA or MIA is not an excuse not to file a Pirep/Misrep. All reports must contain, but are not limited to: Callsign Name of Mission Gross Wt at T/O Fuel at T/O Fuel at touchdown T/O runway Landing runway Departure used Loadout including HMCS, TGP, Ext F/T, ECM, LAC Ordinance used and Accuracy of each Mission outcome Lessons learned ACMI Additional info (pilots discretion) PreFlight Briefings. The Flight Lead owns the engagement and therefore the briefing. Tactics, loadout, departure, victory conditions are set by the Flight Lead without exceptions and cannot be modified. Lead will inform the flight of all possible scenarios, threats, targets, opportunities and any counter actions that may be needed if the situation changes. Flight Lead is solely responsible for the outcome of each operation.

3-8.

3-9.

3-10a. Airbase-Specific Departures. Default for all engagements, Flight Lead will direct the flight to utilize the airbase departure as described in the navigation volumes for each runway. Steerpoint 2 shall be referenced during takeoff and pilots will proceed with appropriate burn rate (see Other Departures below) and will follow the defined departure route in formation at proper spacing. 3-10b. Other Departures. By default all flights will takeoff in full buster (military power) with Steerpoint 2 referenced and rotate upon command from the Flight Lead, maintain 300 knots at a positive 5 degree pitch and climb to the briefed altitude. Proper formation and spacing will be maintained at all times. The Flight Lead may under certain conditions require a full gate burn on takeoff depending on the sortie criteria and gross takeoff weight and in such case, the flight will maintain 350 knots while referencing Steerpoint 2 at a 10 degree pitch and climb to briefed altitude. Proper formation and spacing will be maintained at all times.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 4

3-11a. Flight DataLink. Flight Lead is responsible for establishing a Continuous DataLink for his or her flight. This will be done during the rampstart or during taxi. 3-11b. Package DataLink. Each pilot will establish the Package DataLink to selected Flight Leads within his or her package as desired. 3-12. Engagements. In the event that departure from the predetermined flight plan is necessary in order to successfully complete mission tasks, permission must be granted from the Flight Lead before altering course, ingress, egress, initial points, RTB time and tactics both offensive and defensive. 3-13. TOS. Pilots must be within one minute of TOS (time over steerpoint) in order to fall within the timed strike parameters for each leg of every engagement unless unanticipated circumstances arise that hinder a successful mission. Example, enemy fighter launched from nearby airbase to intercept your flight or friendly package. 3-14. Flight Time. You are required to perform at least one Currency Flight per week (four per month) to remain in Active flight status as a member of the 27th FW. Your Quarterly Currency status is always available for review via the 27th vFW website, as are the minimum requirements for each period. All flights are in the Korean theater of operations unless otherwise specified. 3-15. F-16 B-Course. The full spectrum of the F-16 and its avionics, weapons, instruments and ACM are implemented in BMS and as such, all pilots regardless of experience and prior training are required to pass a regimented twenty-four sortie qualification program known as the B-Course. This is a course designed by the senior officers of the 2tth FW for use with BMS and all sections must be passed (in sortie number order) before becoming MRd and a candidates progress may be viewed at any time via the 27th vFW website under your squadron tab. While enrolled in the B-Course, it is customary for the IP to bestow upon the candidate a unique and personalized callsign that will be used in all future operations. It is left to the discretion of the IP when to impart, what callsign to give, or the IP may allow the candidate to keep an existing one. Upon graduation of the program, the pilot is then to be promoted to the rank of 1st Lieutenant** (refer to Miscellaneous section regarding Transfers) and be given his or her MR status for participation in all online campaigns and Inter-Wing cooperative missions. 3-16. B-Course Sortie Completion. In order for a training sortie to be considered passed and complete, an IP must be present during the flight and signoff on the task as complete. Screenshots or videos of a pilot performing the compulsory skills to fulfill a requirement as a candidate for MR status will not be accepted. Likewise, any sorties similar in nature previously passed while a member of another vFW or vFS will not count toward the 27th FW B-Course requirements. 3-17. DOR (Drop on Request). At any time during enrollment in the 27th FW F-16 B-Course an officer pilot may request a DOR. The officer pilot will immediately be de-enrolled from the B-Course program and will either be considered for a section role (either supervisory or non-supervisory) or be transferred out of the 27th FW at the discretion of the Squadron Commander. DOR is only applicable to non-MRd officer pilots.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 5

CHAPTER 4 SQUADRON ASSIGNMENTS 4-1. Section Leaders. The career of a pilot attached to the 27th FW does not exclusively include supporting your unit from the air. There is an abundance of work to be done on the ground at an administrative level to ensure that the goals of the squadrons are exceeded and that we remain an elite arm of the AFSOC. Upon successful completion of the F-16 B-Course and promotion to 1st Lieutenant** (refer to Miscellaneous section regarding Transfers) a pilots background and strongest skills will be evaluated and he or she may be assigned an executive role in a section of the squadron in which they have been assigned commensurate with the current needs of the Wing (ie Training Officer, Operations Officer, Technology Officer etc.). This role will be incremental to the officers obligatory pilot duties and will be crucial to the success and standing of the squadron in the FW with respect to future development enhancements.

CHAPTER 5 MISSION READINESS MR means MR. Only MRd members of the 27th FW may participate in official online campaigns and cooperative Inter-Wing flights. No exceptions will be granted. Proficiency. In order to be strongest, most adept and most prepared FW in BMS, we must continually enhance and refine our skills in all aspects of the F-16 and its systems, weapons, brevity, ACM, navigation, ground operations and warfare tactics. You will be asked to join training flights often, help others become MRd, create new TEs or campaign scenarios and become an integral part of the unit. Becoming MRd is not a graduation in the traditional sense, and your newly acquired skills will be put to the test every time you take to the skies. Be sure to keep practicing the basic skills set forth in the B-Course syllabus in order to optimize the FWs capabilities and combat readiness status. Officer pilots that repeatedly exhibit lack of any fundamental core skillsets as outlined in the F-16 B-Course may be required at the discretion of the Squadron Commander to requalify on a particular sortie(s), and may or may not result in a change in the pilots MR status.

5-1. 5-2.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 6

CHAPTER 6 MISCELLANEOUS 6-1. Leaves of Absence. A pilot may at his/her own discretion choose to be placed on LOA if circumstances arise that require the individual to be Inactive Reserve for a specified period of time. A maximum of two weeks will be granted in such case, and a maximum of three additional two week blocks may extend a members LOA status for a total of eight inactive weeks. Each two week block will have the following consequences as outlined below. Status after return from LOA (for previously MRd pilots only): LOA is 1 day to 14 days: No change in MR status. LOA is 15 days to 28 days: No change in MR status. Squadron Commander may at his/her discretion select up to three (3) B-Course sorties for the pilot to requalify on before including the pilot in Online Campaigns or Inter-Wing cooperative missions. LOA is 29 days to 42 days: Status reduced to NMR. Squadron Commander will select no less than six (6) B-Course sorties for the pilot to requalify on to reinstate pilots MR status. LOA is 43 days to 56 days: Status reduced to NMR. Squadron Commander will select no less than twelve (12) B-Course sorties for the pilot to requalify on to reinstate pilots MR status. LOA is 57 days or longer: Status reduced to NMR. Squadron Commander to requalify pilot on all B-Course sorties to reinstate pilots MR status. Status after return from LOA (for NMRd pilots only): LOA is 1 day to 14 days: Continue B-Course with no requalifying of previously passed sorties. LOA is 15 days or longer: Candidate to restart B-Course from the beginning. 6-2. Transfers In. In the event an officer pilot transfers into the 27th FW from another Fighter Wing, the pilot must pass all sorties the 27th FW F-16 B-Course per Section 3, Paragraph 15 of the 27th vFW (AFSOC) Standard Operating Procedures. Upon successful completion of the F-16 B-Course and after an evaluation of the officers pilot skills and knowledge of the executive roles held in his or her previous duty stations section (if applicable), the Squadron Commander may at his or her discretion assign the transferee to a section in an executive role at the rank of either 1st Lieutenant or Captain, so long as the pay grade does not match or exceed the current pay grade of the squadrons Commander. This is to ensure that the Commander has adequate confidence that the transferee meets or exceeds the standards of the Squadron and that the transferee officially reports up to the Squadron Commander in all respects. For transferees being assigned to the 27th FW in a capacity more senior than that of a Squadron Commander, the Commander of the 27th FW shall be given full placement authority. Transfers Out. In the event an officer wishes to transfer out of the 27th FW either to join another Wing or retire from service, the Squadron Commander will revoke the officers MR status immediately. An officers request for reintroduction into the 27th FW after officially transferring out will be at the Wing Commanders discretion. Page 7

6-3.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

CHAPTER 7 NONCOMPLIANCE, INSUBORDINATION AND MUTINY 7-1. Dismissal. An officer judged by the Squadron Commander to be repeatedly noncompliant with all guidelines set forth in the 27th vFW (AFSOC) Standard Operating Procedures or who has demonstrated recurrent acts of insubordination may be subject to immediate dismissal. Similarly, seditious actions committed by an officer may be deemed as mutinous in nature by the Squadron Commander and may lead to immediate dismissal after all relevant facts have been reviewed by the Wing Commander.

27th vFW USAF (AFSOC) Standard Operating Procedures. Rev. 200313

Page 8