JAP 100A 01 Chap 1.10.2-UNCONTROLLED COPY WHEN PRINTED-Station, Ship, Unit and Squadron, Unit Aviation Engineering Orders

Stn/Ship/Unit and Sqn/Unit Aviation Engineering Standing Orders (AESOs) and Aviation Engineering Routine Orders (AEROs) are a method of publicizing low-level engineering instructions from hierarchical organizations to a wider audience. This chapter describes the purpose, scope, layout and format of AESOs and AEROs, and defines how they are issued and reviewed. AEROs are to be used for promulgating Aviation Local Technical Instructions (ALTIs); as detailed in Chapter 10.5.6. This chapter should be read in conjunction with Chapter 1.10 and Chapter 1.10.1.

1.2 Associated publications

This chapter is associated with the following publications:

1 QR RN Paragraph 1101 – Responsibilities of the Ship or Air Station Air Engineer Officer.

2 QR Army Paragraph 5.122 – Orders.

3 4AP100B-01 Order 1.1D – Responsibilities of Unit Engineering and Logistic Staff within the Overall Airworthiness Framework.3

4 DEME(A) Engineering Standards.

1.3 Applicability

This chapter is applicable to the Military Air Environment.

2 Policy on Stn/Ship/Unit and Sqn/Unit aviation engineering orders

Stn/Ship/Unit authority level Ks are to promulgate aviation engineering orders as detailed in the associated publications. These documents are to be called Stn/Ship/Unit Aviation Engineering Standing Orders (AESOs) and Stn/Ship/Unit Aviation Engineering Routine Orders (AEROs). These may be discrete documents, or may form part of a broader Stn/Ship/Unit publication embracing non-aviation engineering and supply instructions that are an integral part of the Stn/Ship/Unit function. They may also include orders relating to collocated Depth support organizations. However, in all cases, the aviation engineering element is to be arranged according to this chapter. Sqn/Unit authority level Js may issue Orders as described at paragraph 8. These orders facilitate the expansion of higher authority instructions in order to account for local environment/conditions. They are not to contain nor countermand information in higher policy instructions without the written approval of the higher instruction sponsor. Any concessions so obtained are to be included in the text of the relevant AESO and are to be reviewed in accordance with paragraph 5.

3 Deconfliction and amalgamation of orders

At locations shared by a number of units, low level engineering policy publications (AESOs and AEROs) should be amalgamated to the maximum extent in order to promote best practice and efficient use of shared facilities and avoid conflicting instructions. The following sub-paragraphs amplify this in respect of collocated units of differing Front Line Commands (FLCs) and Depth support units collocated with Forward units.

3.1 Collocated units of differing Front Line Commands (FLCs)

Where 2 or more units of differing FLCs operate from the same location, the AESOs are to detail from which FLC the orders emanate, to ensure deconfliction. Deployed units are to adhere to their Stn/Ship/Unit or Sqn/Unit AESOs (as appropriate) and are to adopt pertinent orders of the hosting Stn/Ship/Unit AESOs. Where deployed/hosting unit orders conflict, the safest or most stringent order is to be adopted as best practice.

Note:

The exception to this rule is that when a Sqn/Unit is deployed afloat, the Ship’s Standing Orders take precedence over the orders of the deployed Sqn/Unit.

3.2 Depth Support Units (DSUs) collocated with Forward units

Where a DSU is collocated with one or more Forward units and uses Forward unit facilities, both units’ AESOs are to include the arrangements for this shared usage. Where practicable, this should be achieved by using a common set of AESOs, sub-divided into three sections: the first section comprising those orders that apply to all units at the location, followed by sections that apply to the individual Forward and Depth units. The authority level K of the host unit is to take the lead in arranging this integration.

4 Scope, structure and layout of Station/Ship/Unit Aviation Engineering Standing Orders (AESOs)

4.1 Scope

AESOs are to contain the organization’s:

1 Function.

2 Responsibilities.

3 Terms of reference.

4 Local orders and procedures.

Note:

The primary purpose of local orders and procedures is to take account of the local conditions and/or to achieve a more efficient task scheduling. They may refer to the Aircraft/Equipment Document Set (ADS/EDS) but are not to duplicate or be used to replace any Technical Information within the ADS/EDS. Where local orders and procedures do refer to the ADS/EDS they are to state the amendment state of the referenced document. A list of reference publications is to be maintained as an order, so that when reference publications are amended, the local orders or procedures that refer, may be reviewed for continued accuracy of content and amended as appropriate.

Local orders and procedures are not to be used to correct errors or omissions in the ADS/EDS; the appropriate method for correcting the ADS/EDS is detailed at Chapter 8.2.

This note also applies to paragraph 8.1.

They are to form part of the quality management system (QMS) iaw Chapter 15.1.

4.2 Structure

AESO structure is detailed below. AESOs are to consist of 2 books that are to be structured in accordance with the information detailed in Table 1 and Table 2 and paragraphs 4.3 and 5.

Table 1. Aviation Engineering Standing Orders, Book 1 – Function, Organization and Responsibilities.

Header	Content
Preliminary pages	1. Title Page. 2. Amendment Record Certificate. 3. Distribution list. 4. Introduction. 5. Contents.
Part 1	Function, organization and responsibilities.
Chapters	For each sub-organization. Note: Where flying squadrons are co-located with support units, the flying squadrons’ chapters are to be last, in numerical order.
Sections	For each sub-sub organization.
Orders	Terms of reference to a rank level determined at the discretion of the relevant authority level K.
Part 2	Duties.
Chapters	For each sub-organization.
Orders	For duty personnel within each sub-organization.

Table 2. Aviation Engineering Standing Orders Book 2 – Orders.

Header	Content
Preliminary pages	1. Title Page. 2. Amendment Record Certificate. 3. Distribution list. 4. Introduction. 5. Contents.
Part 1	General orders.
Chapters	Orders of general applicability for common equipment/reasons.
Orders	Orders are to be used to direct personnel in conducting specific engineering tasks, eg the restriction of aero-engine ground running at night.
Part 2	Specific orders.
Chapters	For sub-organizations. Where flying squadrons are co-located with support units, the flying squadrons’ chapters are to be last in numerical order.
Sections	For sub-sub organizations.
Orders	Orders are to be used for the direction of personnel in conducting specific engineering tasks, eg the use of a workshop overhead gantry.

4.3 Layout

The heading on the first page of each order is to be annotated with the Book/Part/Chapter/Section/Order details and the order title; additionally it is also to show the order sponsor details. The foot of each page is to be annotated with the page number and order amendment state. The layout of individual pages within the AESOs is at the discretion of the relevant authority level K.

5 AESO issue, review, amendment and withdrawal

The relevant authority level Ks are to define and document the process by which AESOs are sponsored, issued, reviewed, amended and withdrawn.

6 Stn/Ship/Unit AESO distribution, reading and recording

6.1 Distribution

AESOs may be promulgated in any medium and are to be distributed down to a level that is at the discretion of the authority level K. A master copy of AESOs is to be maintained by a post identified by the relevant authority level K. Additionally, a full copy is to be held by the unit quality coordinator. Sub and sub-sub organizations are to hold only those orders that apply to them.

6.2 Reading and recording

Personnel are to sign as having read and understood the orders and procedures that are applicable to them. This is to take place on the following occasions:

1 On arrival at a Stn/Ship/Unit or Sqn/Unit.

2 Following a change of employment at a Stn/Ship/Unit or Sqn/Unit.

3 Following the issue of new or amended orders.

7 Stn/Ship/Unit Aviation Engineering Routine Orders (AEROs)

AEROs are to be used, by way of example, for:

1 Publishing information of a temporary nature.

2 Bringing information to the attention of personnel pending inclusion within AESOs.

3 Publishing brief details of relevant ALTIs, as detailed in Chapter 10.5.6.

AEROs are controlled documents and are to be classed as records within the QMS. Each issue of AEROs is to be authorized by the relevant authority level K. Within each issue, individual orders are to be numbered and, in parallel with AESOs, each order is to be annotated with the post of the sponsor. They may be promulgated in any medium and at intervals that are at the discretion of the relevant authority level K. The first order of each year is to state the last serial number issued for the preceding year. Whilst the layout of AEROs is at the discretion of the relevant authority level K, AEROs must contain as a minimum:

1 The Stn/Ship/Unit location or Sqn/Unit title.

2 The title ‘Aviation Engineering Routine Orders’.

3 Serial number in the format NN/YY where N is the sequential number and YY is the year.

4 Date.

8 Sqn/Unit

A Sqn/Unit may have its own AESOs or AEROs.

8.1 Sqn/Unit AESOs

The authority level J is responsible for the issue, upkeep and withdrawal of any Sqn/Unit AESOs but he is to consult the relevant authority level K before withdrawing any Sqn/Unit AESO. Sqn/Unit AESOs may be included within the Sqn/Unit Standing Orders or held in a discrete book and are to have the same layout as the parent Stn/Ship/Unit AESOs as described at paragraph 4.

8.2 Sqn/Unit AEROs

The authority level J may issue Sqn/Unit AEROs at his discretion whether deployed or not. Sqn/Unit AEROs are to take the same layout as the parent Stn/Ship/Unit AEROs as described at paragraph 7.

9 Contractor’s Engineering Orders

9.1 Contractors employed subject to level K authority

Where a contractor is employed, subject to authority level K authority, to maintain, control or operate aircraft or equipment, the contract will almost invariably require the contractor to comply with Service orders and regulations. The contractor is to prepare procedures needed by Service personnel using the contractor’s equipment and is to forward these procedures to the authority level K for inclusion in AESOs. In addition, the contractor is to publish all necessary orders and regulations for adherence by his own staff as Company Procedures (CPs) or similar instructions. Copies of these CPs are to be made available to the authority level K and to the Stn/Ship/Unit Quality Representative or Quality Assurance Co-ordinator. The reading and signing of CPs by contractor’s personnel is to comply with the contractor’s normal practices.

9.2 Contractors holding level K authority

9.2.1 Forward engineering

On units where the main Forward engineering task has been contractorized, the Chief Engineering Manager will, unless otherwise directed by the Contracting Authority, be responsible to the Commanding Officer for discharging the responsibilities of an authority level K, where these responsibilities apply to contractorized elements. All orders and regulations required in addition to the regulations detailed in the contract are to be published on the authority of the Chief Engineering Manager as CPs or within a Company Order Book (COB). The reading and signing of CPs and the COB by a contractor’s personnel is to comply with the contractor’s normal practices.

9.2.2 Depth engineering

On Depth units where the engineering task has been contractorized, the Chief Engineering Manager will, unless otherwise directed by the Contracting Authority, be responsible to the Commanding Officer for discharging the responsibilities of an authority level K, where these responsibilities apply to contractorized elements. All orders and regulations required in addition to the regulations detailed in the contract are to be published on the authority of the Chief Engineering Manager as CPs or within a Company Order Book (COB). The reading and signing of CPs and the COB by a contractor’s personnel is to comply with the contractor’s normal practices.

Where Depth units are collocated with Forward units, local orders are to be integrated as far as possible; see paragraph 3.2. Where a Depth contractor is not required by the Contracting Authority to comply with JAP 100A-01, the Contracting Authority is to require the contractor to agree, with the Forward authority level K, procedures for shared use of facilities. The resulting procedures are to be published in Forward AESOs/AEROs and in the CP/COB.

9.3 Exception to the issue of Stn/Ship/Unit AESOs

On Stns/Ships/Units where there are so few Service personnel that the issue of AESOs is impractical, the Unit Commander may issue a single order in Stn/Ship/Unit Standing Orders. This order is to direct Service personnel to follow contractor’s published procedures, provided that the specific procedures to which the order applies are identified and the conditions for reading and signing the procedures are met.