Downloaded from https://www.everyspec.com for a period not less than two years after completion of the fiscal year. j. Aviation units performing OSA mission support will conform to the reporting requirements contained in the OSA Remote User’s Guide and this regulation (1) The aviation unit commander will appoint an airlift coordina- tor. The airlift coordinator will perform duties in accordance with the OSA Remote User’s Guide. (2) All training flights will be reported in PMRs in accordance with OSA Remote User’s Guide . (3) Training missions may be scheduled by the aviation unit.
Aviation units are strictly prohibited from scheduling training mis- sions for the purpose of carrying passengers and or cargo. (4) Will retain all post-mission data, including non-OSA mis- sions, for a period of not less than two years after completion of the fiscal year. submitted not later than four duty days in advance of the date of desired travel or as soon as the requirement is identified. e. Cancellations or changes to CONUS OSA flights will be trans- mitted to JOSAC in accordance with OSA Remote User’s Guide. f. Passenger reporting time for OSA flights is not later than 30 minutes prior to scheduled departure time. g.
Approved requests for Non-NCR Army helicopter OSA will be submitted to the validator and forwarded to the helicopter sched- uling authority in accordance with local procedures. Installations will forward annual helicopter OSA utilization data to MACOMs for consolidation and forwarding to OSACOM. Because of the ex- tensive costs associated with rotary wing operations, their use for OSA should be closely monitored and approved only when other modes of travel will not fulfill requirements. h. Validators will not submit requests for fixed wing back up support for approved helicopter requests. 3–7. Justification.
Within the policy guidance prescribed by DoD directive 4500.43 and this regulation, scheduling authorities schedule the use of air- craft for OSA missions based on the following criteria: a. Cost analysis procedures are based on the OSA scheduling system. Commercial cost comparisons for fixed wing and rotary wing OSA are accomplished by incorporating cost elements speci- fied in DoD directives and regulations. b. For airlift requests meeting the criteria prescribed above, each OSA flight request will be assigned an appropriate PUJC code by the OSA validator that is established in the OSA Remote User’s Guide and DoD directive 4500.43. 3–9. Data collection and use. a.
Army OSA/Non-OSA fixed wing and rotary wing OSA utili- zation data will be collected by OSACOM for the purpose of: (1) Justifying use of Government aircraft in lieu of commercially available aircraft or the use of one Government aircraft in lieu of another. (2) Recovering the costs of operating Government aircraft when appropriate. (3) Determining the cost-effectiveness of various aspects of air- craft programs. (4) Analysis of trends in inventory and seat utilization for each mission, type, design, and series OSA aircraft, by priority of travel, to include opportune airlift.
( 5 ) C o m p a r i n g O S A / n o n - O S A f l y i n g h o u r s a c t u a l l y f l o w n t o those budgeted in the annual flying hour program will be accom- plished by the automated post mission reporting system as collected by OSACOM. (6) Summarizing the number of OSA/non-OSA missions flown. (7) Summarizing passenger requests and total passengers moved by priority. b. OSACOM will retain all requests for aircraft support and post mission data for a period of not less than two years after completion of the fiscal year. The OSA validator will retain a copy of all requests for OSA support for a period of not less that two years after completion of the fiscal year.
The aviation unit will retain all post mission data, including reports on all training flights, for a period of not less than two years after completion of the fiscal year. 3–8. Procedures. a. The OSA validators will publicize transportation requests and aircraft scheduling procedures within their areas of responsibility. Procedures will include requirements for units or individuals to request OSA in advance and to accept variations in departure or arrival times and will be reviewed by the authorizing official. Ur- gent operational demands will be considered when determining if a spread is possible in departure and arrival times.
Validators will establish the PUJC codes for all OSA requests in accordance with the OSA Remote User’s Guide and DoD 4500-43.. Rank or grade alone is not sufficient to justify support of airlift requests or place- ment in any particular PUJC. b. Army personnel will submit requirements for official travel to the authorizing official within their chain of command. c. Authorizing official will state requirements for official govern- ment travel and forward all approved requests to OSA validators a minimum of four duty days prior to the date of intended travel and in sufficient detail to allow the validator to assign the airlift requests with the appropriate PUJC.
Signature of the senior traveling passen- ger is required and can not delegated. In addition, Senior federal travelers (all general officer and civilian equivalent) will have their travel requests reviewed and approved no lower than the grade of Major General. d. OSA validators will ensure that requests are received from a proper authorizing official with appropriate signature of the senior passenger. They will submit approved requests for Army fixed wing OSA within CONUS and rotary wing OSA within the National Capital Region (NCR) to the OSACOM. The OSACOM automated remote users’ system will be used to submit OSA requests.
Requests will be submitted to OSACOM within the time frames outlined below. (1) Flight requests will normally be submitted to OSACOM not later than four duty days prior to the departure or as soon as an OSA mission requirement is identified. Priority “1” requests may be submitted telephonically and confirmed by message. (2) Team or group travel request (as defined in DoD 4515.13-R) for fifteen or more individuals for Army OSA flights will be sub- mitted not later than 30 days prior to departure date. This does not include requests for SAM support. A team consisting of fourteen or less individuals traveling as a group, or part of a group, may be 3–10.
Special missions Unless specified, approval authorities for missions authorized in this paragraph are MACOM or CNGB. They may delegate approval authority no lower than installation , U.S. Army Reserve Command (ARCOM) commanding generals or State Adjutants General. In a d d i t i o n t o o p e r a t i o n a l m i s s i o n s a n d o p e r a t i o n a l s u p p o r t a i r l i f t , Army aircraft my be used for the following purposes: a. Public affairs travel. Army aircraft may be used for public affairs in accordance with DoD 4515.13-R, Chapter 3. b. Orientation flight. Army aircraft may be used for orientation flights in accordance with DoD 4515.13-R, Chapters 4 and 10. c.
Aeromedical evacuation. (1) Aeromedical evacuation is applicable to eligible personnel described in DOD 4515.13, Chapter 5. (2) Army aircraft may be used to transport U.S. Armed Forces patients (DoD 4515.13-R, Chapter 5) when deemed necessary by competent medical authority. The OSA fixed wing aircraft are not equipped to handle litters or patients requiring special medical atten- tion en route, therefore will only transport ambulatory patients who require no en route medical treatment, except in an emergency situation.
(3) Civilian personnel, and those personnel not covered in (1) and (2) above may be provided aeromedical transportation to the nearest medical facility where immediate treatment is available. This will be done only when there is an emergency involving immediate threat to life, limb, or sight, and when suitable commercial services 7 AR 95–1 • 1 September 1997