306_FTG_OI_21-104.pdf

BY ORDER OF THE COMMANDER 306 FTG OPERATING INSTRUCTION 21-104

306 Flying Training Group

6 July 2012

Air and Space Maintenance

SCHEDULING PROCEDURES

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSABILITY: This publication is available digitally in the 306 FTG Stan/Eval

Publication Library: https://eim.usafa.edu/unit/306ftg/ftgv/frst/default.aspx

RELEASABILITY: There are no releasability restrictions on this publication

OPR: 306 OSS/OSO Certified by: 306 FTG/CD

(Lt Col Hayes)

Supersedes: 306 FTG OI 21-104, 10 July 2009 Pages: 16

This publication implements Air Force Policy Directive (AFPD) 21-1, Air and Space

Maintenance. This Operating Instruction (OI) applies to Commanders (CC), maintenance, operations supervisors and aircrews assigned or attached to the 306th Flying Training Group

(FTG) [excluding 1 st Flying Training Squadron (FTS)]. The purpose of this OI is to define the scheduling process In Accordance With (IAW) Air Education and Training Command

Instruction (AETCI) 21-104, Aircraft Planning and Scheduling Procedures, paragraph 1.6. and set guidance for internal coordination of scheduling requirements IAW AETCI 21-104, paragraph 2.9. Submit suggested improvements to this instruction on AF Form 847, Recommendation for Change of Publication, through 306 FTG Standardization/Evaluation channels. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN) 33-363, Management of

Records, and disposed of in accordance with the Air Force Records Disposition Schedule (RDS), located at https://www.my.af.mil/afrims/afrims/afrims. See Attachment 1 for a Glossary of

References and Supporting Information.

SUMMARY OF CHANGES

Clarified fly order (paragraph 1.1.3.); re-designated paragraph title (paragraph 3.1.); clarified

Maintenance Contractor accountability (paragraphs 4.2.1. and 4.3.1.); clarified process for schedule changes (paragraph 4.4.); clarified coordination (paragraph 4.4.); deleted paragraph concerning early launches and renumbered (paragraph 4.4.3.2.); clarified weather adding sorties

(paragraph 4.4.3.3.); clarified flying window (paragraph 4.4.3.4).

https://eim.usafa.edu/unit/306ftg/ftgv/frst/default.aspx https://www.my.af.mil/afrims/afrims/afrims

2 306 FTG OI 21-104, 6 Jul 2012

Chapter 1 – GUIDANCE

1.1. AETC Guidance

Chapter 2 – RESPONSIBILITIES

2.1. Responsibilities

Chapter 3 – SCHEDULING MEETINGS

3.1. Operations/Maintenance Recap

3.2. Weekly Group Scheduling Meeting

3.3. Weekly Squadron Scheduler’s Meeting

3.4. Quarterly Scheduling Meeting

3.5. Annual Scheduling Meeting

Chapter 4 – SCHEDULING SUSPENSES

4.1. Annual Plans

4.2. Quarterly Plans & Reflows

4.3. Monthly Plans & Contracts

4.4. Weekly Schedule/Contracts

4.5. Changes

Table 4.1. AF Form 2407 Requirement

4.6. Off-Station Sorties

4.7. Deployment Notification

4.8. Static Display Support

Chapter 5 – REPORTS

5.1. 19 AF Form , Weekly Aerial Events Report

5.2. AETC/A3RA Monthly Flying Hour Report

Attach 1 – GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

306 FTG OI 21-104, 6 Jul 2012 3

Chapter 1

GUIDANCE

1.1. AETC Guidance. AETCI 21-104 and AFI 21-101, Aerospace Equipment Maintenance

Management, will be used as a guide to develop a joint OI outlining the 306 FTG scheduling process.

1.1.1. 306 FTG, in concert with Headquarters (HQ) Air Education and Training Command

(AETC)/A4, will continue to refine the maximum sustainable Utilization (UTE) rates for each Mission Design Series (MDS).

1.1.2. 306 FTG MDS experience higher attrition rates than other AETC MDS. This attrition is primarily due to the exaggerated effects of weather on light, Visual Flight Rules (VFR)-only aircraft. These high attrition rates necessitate flying schedule planning inputs that exceed the definition of surge operations as defined in AETCI 21-104. The required over-scheduling of sorties to overcome daily attrition, meet training goals and meet flying hour goals will not be considered surge operations nor will the 306 FTG be limited to operating in this capacity for just two days a month IAW AETCI 21-104.

1.1.3. Flight order, listing MDS tail numbers to be used for the day, will be provided by maintenance (MX) prior to commencing flying operations. Each MDS is prioritized on the fly order with the intent of the #1 aircraft flying the most hours, #2 aircraft flying the next highest hours, etc. One spare per MDS, if available, will be designated for each flying day.

The scheduled spare concept will not be applied to 306 FTG MDS with a Primary Aircraft

Inventory (PAI) of four or less due to small fleet dynamics to allow proper fleet management and inspection flow. MX is not accountable for MX or supply non-deliveries. Additionally, air abort and ground abort rates are defined by the Contractor Statement of Work (CSOW).

All deviations will be documented on the 306 FTG Attrition Tracker. Due to the high unpredictability of sortie requirements, the scheduled spare concept, contract schedules and recording schedule deviations will not be required for deployments and off-station competition. The initial departure sortie from home station for Out & Backs, cross-country, and deployments, will be scheduled and deviations will be recorded. Actual off-station sorties and hours flown during deployments will be reported as both scheduled and flown by the operations squadrons using the 306 FTG Attrition Tracker, however; off-station deviations are not required to be reported to Higher Headquarters (HHQ).

4 306 FTG OI 21-104, 6 Jul 2012

Chapter 2

RESPONSIBILITIES

2.1. The CSOW does not require a Maintenance Operations Center (MOC), Maintenance Data

Systems Analysis (MDSA) or a Maintenance Information System (MIS).

2.1.1. Each operations squadron is responsible for reporting the execution of the flying schedule to the flight line expediter or directly to the plans and scheduling office. The operations squadron will record all deviations on the 306 FTG Attrition Tracker and MX will provide historical weather attrition statistics for each MDS via the weekly Group Scheduling meeting.

2.1.2. Upon landing, the Pilot in Command (PIC) for any 306 FTG assigned aircraft will conduct a face-to-face debrief with MX for the following:

2.1.2.1. Pilot-reported discrepancies that affect safety of flight.

2.1.2.2. Pilot-reported discrepancies that are mandatory impound items.

2.1.2.3. Functional Check Flights (FCF).

2.1.3. The MX contractor plans and scheduling office will fulfill the duties of Plans, Scheduling, and Documentation (PS&D) IAW the CSOW.

2.1.4. The Civilian Contractor Logistics Support Manager will fulfill the role of MXG/CC equivalent, IAW with the current CSOW, only for the duties and responsibilities defined by the CSOW.

2.1.5. As requirements are defined, each operations squadron will refine their Flying Hour

Program (FHP) for each MDS to ensure the availability of an accurate Programmed

Allocation (PA) and resources.

2.1.6. 306 FTG Attrition Tracker.

2.1.6.1. The previous day’s flying hours and sorties for each MDS will be reconciled daily between MX, squadron scheduling and Squadron Aviation Resource Managers (SARM’s). Once reconciled, the previous day’s flying hours and sorties will be loaded by squadron scheduling/SARM’s using the 306 FTG Attrition Tracker.

2.1.6.2. Flying squadron inputs to the 306 FTG Attrition Tracker are due no later than (NLT)

1200L (Monday-Friday) and NLT 0900L during the FHP closeout window. The FHP closeout window begins 1 September and ends on 30 September each year.

2.1.6.3. Squadron scheduling and SARM’s will ensure that the 306 FTG Attrition Tracker and

DOSS MMI products match by the 4 th of every month.

2.1.6.4. By the 5th workday of each month, 306

th Operations Support Squadron (OSS)/OSO will ensure the 306 FTG Attrition Tracker and DOSS MMI products match hours and sorties for the previous month.

306 FTG OI 21-104, 6 Jul 2012 5

Chapter 3

SCHEDULING MEETINGS

3.1. Operations/Maintenance Recap. The Operations/Maintenance Recap meeting convenes on Tuesdays and Thursdays, and is chaired by the 306 FTG/CC or a designated representative.

3.1.1. Attendees. This meeting is attended by designated group and squadron representatives from the following functional areas:

3.1.1.1. MX.

3.1.1.2. Operations.

3.1.1.3. Safety.

3.1.1.4. Quality Assurance Evaluation (QAE).

3.1.1.5. 306 OSS/OSO (if required).

3.1.2. Agenda. The meeting agenda will include (but is not limited to) the following items:

3.1.2.1. Execution recap of the previous flying week.

3.1.2.2. Validation, analysis, and reconciliation of deviations (Reference 2.1.6.).

3.1.2.3. Review of flying hours and sortie counts.

3.1.2.4. Overview of the schedule for the current and upcoming week.

3.1.2.5. Review of overall fleet health statistics.

3.1.2.6. Review of recent safety issues or developing trends (Thursday meeting only).

3.2. Weekly Squadron Schedulers Meeting. The weekly squadron Schedulers Meeting convenes each Wednesday at 1500 and is chaired by the 306 OSS/DO or a designated representative. If Wednesday is a down day then the meeting will be held on Thursday at 1000L.

3.2.1. Attendees.

3.2.1.1. One scheduling representative from each flying squadron.

3.2.1.2. MX Scheduling representative.

3.2.1.3. Group scheduling (306 OSS/OSO).

3.2.2. Agenda.

3.2.2.1. Review squadron flying schedules, the Supervisor of Flying schedule and the airfield operating hours for the upcoming week.

3.2.2.2. Review monthly and weekly AETC Forms 206, Monthly Flying Coordination.

3.2.2.3. Review calendar of upcoming events.

3.2.2.4. Identify and resolve scheduling conflicts between Operations & MX.

3.3. Weekly Group Scheduling Meeting. The weekly group scheduling meeting convenes each Thursday at 1400 and is chaired by the 306 FTG/CC or a designated representative.

Squadron Scheduler’s slides will be firm two hours prior to meeting.

3.3.1. Attendees.

6 306 FTG OI 21-104, 6 Jul 2012

3.3.1.1. Squadron Directors of Operations (DO) (or designated representatives).

3.3.1.2. MX representative.

3.3.1.3. QAE.

3.3.1.4. Group Scheduling (306 OSS/OSO).

3.3.2. Agenda.

3.3.2.1. Review status of program goals.

3.3.2.2. Review 306 FTG flying hour program.

3.3.2.3. Review upcoming events affecting the 306 FTG flying schedule.

3.3.2.4. Sign weekly contract between MX and operations.

3.4. Quarterly Scheduling Meeting. The quarterly scheduling meeting convenes on the 5th of

December, March, and July or the first duty day following. The meeting is chaired by the

306 OSS/DO and attended by representatives from MX, operations, and QAE. The next quarter’s FHP, reflows, and sell backs will be reviewed.

3.5. Annual Scheduling Meeting. The annual scheduling meeting convenes on 5 September or the first duty day following. The meeting is chaired by the 306 OSS/DO and attended by representatives from MX, operations, QAE, and 306 OSS/OSO. The next Fiscal Year’s annual

FHP will be reviewed.

306 FTG OI 21-104, 6 Jul 2012 7

Chapter 4

SCHEDULING SUSPENSES

4.1. Annual Plans. Flying squadrons will build annual plans derived from AETC programmed allocation. Allocations will be distributed by 30 August. The flying squadrons will submit their annual plans to 306 OSS/OSO by 4 September, in the format defined by AETCI 21-104. Once approved by 306 FTG/CC, 306 OSS/ OSO will submit the approved plans to AETC/A3RA and applicable authorities, IAW AETCI 21-104, by 10 September.

4.2. Quarterly Plans & Reflows. Each quarter, operations squadrons will review the previous quarter’s actual executed hours and the remaining fiscal year’s planned hours.

4.2.1. Actual hours flown each quarter may cause deviations from the annual plan. In order to account for these deviations, it may become necessary to “reflow” the hours by developing a refined annual flying hour plan.

4.2.2. The reflowed plan will communicate how the remaining hours will flow into the months remaining in the fiscal year, accounting for fleet health and operational capabilities agreed upon by both operations and MX.

4.2.3. If a flying squadron is planning to deviate by +/- 10% from the programmed allocation, as approved by HQ AETC/A3RA, then the 306 FTG/CC must approve the planned deviation and the MX contractor must be notified to determine MX capability.

4.2.4. The refined annual plan will be submitted in the format provided by 306 OSS/OSO the day prior to the Quarterly Meeting. Once approved by 306 FTG/CC, 306 OSS/OSO will submit the approved, updated plans to AETC/A3RA and applicable authorities IAW AETCI

21-104.

4.3. Monthly Plans and Contracts. The monthly plan and contract is a continuation and refinement of the quarterly plan. Once signed, it establishes the foundation for the development of the weekly schedules and contracts.

4.3.1. Each month, flying squadrons will submit a plan for the upcoming month to

306 OSS/OSO. Monthly schedules are due the Monday prior to the first weekly scheduling meeting of the month and will provide the following:

4.3.1.1. Number of sorties and hours required.

4.3.1.2. Number of sorties and hours scheduled .

4.3.1.3. Attrition sorties and hours added.

4.3.1.4. Special requests (night sorties, off station sorties, demos, statics, etc.).

4.3.2. Sortie/flying hour adjustments to the quarterly plan are allowable provided MX has the resources available to support them. Squadrons will provide justification for deviating more than +10% from the annual plan to 306 FTG/CC for approval.

4.3.3. 306 OSS/OSO will forward monthly plans to MX the Tuesday prior to the first weekly scheduling meeting of the month.

4.3.4. MX will respond to their respective operations squadrons by the second weekly scheduling meeting of the month to coordinate any changes.

8 306 FTG OI 21-104, 6 Jul 2012

4.3.5. At the third weekly scheduling meeting of the month all flying hour contracts between operations and MX will be signed for the upcoming month.

4.3.6. The MX contractor will only be held accountable for meeting mission required sorties and hours. Post attrition numbers are for squadron use only.

4.4. Weekly Schedule and Contracts.

4.4.1. Operations squadrons will submit a scheduling request for the upcoming week to their respective MX representatives by 1600L each Tuesday and courtesy copy 306

OSS/OSO.

4.4.1.1. Deviations from the squadron monthly plan must be approved by the squadron director of operations. Squadrons will provide justification for deviating more than

+ 10% from the monthly plan.

4.4.1.2. Sortie/flying hour adjustments from the monthly plan are allowable provided

MX has the resources available to support.

4.4.2. MX will review each request and work directly with the flying squadron to arrive at an acceptable, coordinated schedule and solidify the contract for the upcoming week.

4.4.3. The weekly contract (AETC Form 206, or locally approved form reflecting the proposed weekly line schedule for each MDS) will be signed by the MX contractor and the

306 FTG/ CC (or designated representative) at the weekly scheduling meeting.

4.4.3.1. Once signed, the weekly AETC Form 206 and Weekly Schedule becomes final and contractual.

4.4.3.2. Changes made after the weekly schedule has been signed will be coordinated via

AF Form 2407, Weekly/Daily Flying Schedule Coordination.

4.4.3.3. 306 OSS/ OSO will disseminate the weekly AETC Form 206 and Schedule no later than 1400L on Friday.

4.4.3.4. The MX contractor will only be held accountable for meeting mission required sorties and hours. Post attrition numbers are for squadron use only.

4.4.4. Due to the unique operations of the 94 FTS, takeoff and land times will not be published on the weekly line schedule. Only the fly period start/end times and number of scheduled hours/sorties per period will be recorded on the AETC Form 206 and weekly line schedule. The period start and end times will be coordinated and agreed upon by both MX and operations via the Weekly AETC Form 206 and line schedule. MX will only be charged with a MX deviation after 45 minutes from being notified in order to provide them sufficient time to correct the MX discrepancy.

4.4.5 Due to the unique operations of the 557 FTS, takeoff and land times for USAFA

Flying Team will not be published on the weekly line schedule. Only the fly period start/end times and number of scheduled hours/sorties per period will be recorded on the AETC Form

206 and weekly line schedule. The period start and end times will be coordinated and agreed upon by both MX and operations via the Weekly AETC Form 206 and line schedule. MX will only be charged with a deviation after 45 minutes from being notified in order to provide them sufficient time to correct the MX discrepancy.

306 FTG OI 21-104, 6 Jul 2012 9

4.4.6. Due to the unique operations of the 98 FTS, takeoffs and land times will not be published on the weekly line schedules for aircraft sorties in support of jump lines. Only the start/end times and number of scheduled sorties per aircraft will be recorded on the AETC

Form 206 and weekly line schedule. The start and end times will be coordinated and agreed upon by both MX and operations via the Weekly AETC Form 206 and line schedule. All other sorties will require a published takeoff and land time. MX will only be charged with a deviation after 45 minutes from being notified in order to provide them sufficient time to correct the MX discrepancy.

4.4.7. Flying squadrons requesting Extra Day Operations (Ops) (e.g.. Saturday Ops) will provide 7 days notification to 306 OSS/OSO and MX/QAE. Extra Day Operations will be approved by 306 FTG/CC.

4.4.7.1. Notification of less than 7 days may result in denial of requests.

4.4.7.2. QAE will obtain Contracting Officer approval IAW the CSOW.

4.4.7.3. 306 OSS/OSO will ensure adequate airfield manning is available to meet the request.

4.5. Changes. Changes to the signed weekly contract must be coordinated and approved by the

MX contractor and the Squadron Operations Supervisor via the AF Form 2407. See Table 4.1.

to aid in determining when an AF Form 2407 is required.

4.5.1. AF Form 2407 scheduling conflicts will be mediated by 306 OSS/OSO. If still unresolved, the 306 FTG Deputy Commander will mediate.

4.5.2. MX will send all approved AF Forms 2407 to 306 OSS/OSO. Changes for the following day will be coordinated and approved no later than 1500. Changes after this time will be treated as same day changes and accomplished IAW paragraph 4.5.7.

4.5.3. Any changes to the weekly flying schedule via AF Form 2407 that extend the flying window or request additional aircraft will be routed through the flying squadron DO then to

MX PS&D. Once changes have been coordinated, MX will forward the AF Form 2407 to

306 FTG/CC for approval.

10 306 FTG OI 21-104, 6 Jul 2012

Table 4.1. AF Form 2407 Requirement

I

T

E

M

A B C D

Event

Is AF Form 2407 required?

Remarks YES NO

1 Addition or subtraction of aircraft IAW

Paragraph 4.5.7.1.

X

Coordination between squadron and PS&D/Maintenance

Management required.

Requires 306FTG/CC approval.

2 Change to scheduled takeoff and/or landing time less than 30 minutes

IAW Paragraph 4.5.4.

X

Unless it directly affects execution of subsequent daily scheduled sorties. Verbal coordination with Maintenance

PS&D/Maintenance

Management is required.

3 Change to scheduled takeoff and/or landing time greater than 30 minutes IAW Paragraph

4.5.7.4.

X

Coordination between squadron and PS&D/Maintenance

Management required.

4 Adding Weather Attrition

Sorties IAW Paragraph

4.5.7.3.

X

Coordination between squadron and PS&D/Maintenance

Management required.

5 Cancelling sorties due to

Weather. X

Coordination between squadron and PS&D/Maintenance

Management required.

6 Adding/Cancelling OPS

Sorties IAW Paragraph

4.5.9.1.

X

Coordination between squadron and PS&D/Maintenance

Management required.

7 Extending the Flying

Window IAW Paragraph

4.5.3. X

Coordination between squadron and PS&D/Maintenance

Management required.

Requires 306 FTG/CC approval.

4.5.4. A change to the scheduled takeoff or landing time of 30 minutes or less does not require an AF Form 2407 to be initiated unless it directly affects execution of subsequent daily scheduled sorties. However, early takeoffs or planned late landings must be coordinated with the PS&D/Maintenance Management through the flight line expediter.

4.5.5. Changes involving tow aircraft will be submitted by 1300 the day prior with an

AF Form 2407.

306 FTG OI 21-104, 6 Jul 2012 11

4.5.6. Weekly Flying Schedule Changes.

4.5.6.1. The 306 FTG Weekly Flying Schedule will be approved during the weekly scheduling meeting.

4.5.6.2. Coordination with 306 OSS/OSO is only necessary if operations squadrons plan to operate outside of their original flying window.

4.5.7. Same Day Changes.

4.5.7.1. Coordination. The addition of an aircraft or additional spare aircraft, which had not been previously committed to the daily schedule, or the subtraction of scheduled aircraft must be coordinated and approved by the squadron Operations Supervisor and

PS&D/Maintenance Management and approved by the 306 FTG/CC. Operations

Supervisors will send a follow up AF Form 2407 to MX and 306 OSS/OSO describing the action coordinated.

4.5.7.2. Late Launches. See AETCI 21-104, paragraph 15.4.

4.5.7.3. Weather (WX) Adds.

4.5.7.3.1. Units may only add weather sorties if they are behind on the student training timeline.

4.5.7.3.2. WX adding sorties to aircraft previously scheduled and within the original flying window may be verbally coordinated between the operations squadron and

PS&D/Maintenance Management.

4.5.7.3.3. WX additions will be documented on an AF Form 2407.

4.5.7.3.4. IAW AETCI 21-104, WX additions that exceed the current number of WX losses available will be recorded as chargeable operations additions.

4.5.7.3.5. Units may request weather adds up to the Non-Chargeable WX deviation total for the current month. Total Non-Chargeable WX deviations for each squadron will be maintained on the 306 FTG Attrition Tracker.

4.5.7.3.6. All WX adds will be annotated on the 306 FTG Attrition Tracker.

4.5.7.4. Flying Window Extensions. Flying window extensions require 306 FTG/CC approval and will be coordinated on an AF Form 2407.

4.5.8. Deviations.

4.5.8.1. Operations squadrons will record all previous day’s sortie deviations, sorted by number and type, by 1200L each day (Monday-Friday).

4.5.8.2. Deviation documentation will include the total number and type of deviation(s) and will be annotated on the 306 FTG Attrition Tracker (Reference AETCI 21-104).

4.5.8.3. MX will validate sortie deviations from the previous day’s flying and resolve any conflicts with the squadron DO prior to 1530.

4.5.9. Operations Adds (Ops Add) and Cancellations (Ops Cnx).

4.5.9.1. For changes to the weekly schedule, Ops Add and Ops Cnx actions will be initiated on an AF Form 2407.

12 306 FTG OI 21-104, 6 Jul 2012

4.5.9.2. Each scheduled line affected will be documented on the AF Form 2407 and submitted for approval (94 FTS is only required to list the original action and the total sum of lines affected, not each individual line).

4.5.9.3. Same day cancels require verbal coordination between Operations and

PS&D/maintenance management and will be annotated on the 306 FTG Attrition

Tracker.

4.5.9.4. Each entry on the 306 FTG Attrition Tracker will include a comment summarizing all actions covered on the AF Form 2407.

4.6. Off-Station Sorties. Deployment commanders and aircraft commanders on overnight off-station sorties will provide a daily status report to their respective squadron.

4.6.1. The daily status report will include the following:

4.6.1.1. Total sorties and hours flown.

4.6.1.2. Takeoff, land times and sortie duration for each aircraft flown (94 FTS will also include type of sortie flown such as acro, spin, etc.).

4.6.2. If aircraft will be deployed for more than one day, aircrews or MX (if MX supported) will FAX (or call if FAX is unavailable) AFTO Forms 781, ARMS Aircrew/Mission Flight

Data Document, back to MX for inclusion into the flying hour reconciliation process each day.

4.7. Deployment Notification. Flying squadrons will provide MX with at least 30 days notification prior to deployment. Deployment requests will be annotated on the approved deployment request form provided by 306 OSS/OSO.

4.8. Static Display Support. Flying squadrons requesting static display support will provide 15 days prior notification to MX in order to prepare the aircraft IAW the CSOW. Notification of less than 15 days may result in denial.

306 FTG OI 21-104, 6 Jul 2012 13

Chapter 5

REPORTS

5.1. AETC Form 8, Weekly Aerial Events Report.

5.1.1. The AETC Form 8, Weekly Aerial Events Report, provides a two-week outlook to

AETC for upcoming 306 FTG temporary duty (TDY)s, static displays and demonstrations.

5.1.2. Flying squadrons will update and submit their AETC Form 8 each week to 306

OSS/OSO by Tuesday close of business (COB).

5.1.3. 306 OSS/OSO will verify the data and forward the consolidated report to 306 FTG

(Workflow) by Wednesday, 1100L.

5.1.4. 306 FTG (Workflow) will forward the report to AETC Aerial Events Workflow

(aetc.ae3v.aetcaerialeventswork) and 12 FTW/CP by Thursday, 1100L.

5.1.5. 12 FTW/CP will integrate 306 FTG activities with the weekly AETC Significant

Events Report distributed to AETC commanders.

5.2. AETC/A3RA Monthly Flying Hour Report.

5.2.1. Squadron hours and sorties will be reconciled between MX and operations squadrons and then reported to 306 OSS/OSO by the 5th day of each month.

5.2.2. If sorties or hours do not fall within + 10% of the monthly plan approved by

AETC/A3RA, the flying squadrons will provide appropriate comments (alibis) to account for the deviations.

5.2.3. 306 OSS/OSO will submit the preliminary flying hour report to AETC/A3RA by COB on the 5th day of the month. The final report with 306 FTG/CC approved comments (alibis) will be submitted by the 10th day of the month.

CHRISTOPHER E. PLAMP, Col, USAF

Commander, 306 th

Flying Training Group

14 306 FTG OI 21-104, 6 Jul 2012

Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

AETCI 21-104, Aircraft Planning and Scheduling Procedures, 28 December 2010

AFI 21-101, Aerospace Equipment Maintenance Management, 26 July 2010

AFMAN 33-363, Management of Records, 01 March 2008

AFPD 21-1, Air and Space Maintenance, 25 February 2003

Forms Adopted

AETC Form 8, Weekly Aerial Events Report, 1 February 2005

AETC Form 206, Monthly Flying Coordination, 1 September 1998

AF Form 847, Recommendation for Changes of Publication. 22 September 2009

AF Form 2407, Weekly /Daily Flying Schedule Coordination, 1 June 1972

AFTO Form 781. ARMS Aircrew/Mission Flight Data Document, 11 September 2008

Forms Prescribed

None

Abbreviations and Acronyms

AETC–Air Education and Training Command

AETCI–Air Education and Training Command Instruction

AFMAN–Air Force Manual

AFPD–Air Force Policy Directive

CC–Commander

COB–Close of Business

CSOW–Contractor Statement of Work

DO–Director of Operations

FCF–Functional Check Flight

FHP–Flying Hour Program

306 FTG OI 21-104, 6 Jul 2012 15

FTG–Flying Training Group

FTS–Flying Training Squadron

HHQ–Higher Headquarters

HQ–Headquarters

IAW–In Accordance With

MDS–Mission Design Series

MDSA–Maintenance Data System Analysis

MIS–Maintenance Information System

MMI–Maintenance Management Indicator

MOC–Maintenance Operations Center

MX–Maintenance

NLT–No Later Than

OI–Operating Instruction

Ops–Operations

Ops Add–Operations Additions

Ops Cnx–Operations Cancellation

OSS–Operational Support Squadron

PA–Programmed Allocation

PAI–Primary Aircraft Inventory

PS&D–Plans, Scheduling, and Documentation

QAE–Quality Assurance Evaluation

RDS–Records Disposition Schedule

SARM–Squadron Aviation Resource Manager

TDY–Temporary Duty

UTE–Utilization

16 306 FTG OI 21-104, 6 Jul 2012

VFR–Visual Flight Rules

WX–Weather

Terms

Reflow–Documented total hours flown for the prior quarter subtracted from total allocated hours. Redistribute remaining hours for the rest of the year or sell them back.