NAVAIR SOP 00-25-300 - CH. 2.pdf

CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 CHAPTER 2 TECHNICAL DIRECTIVE REQUIREMENTS AND PROCEDURES...

CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 CHAPTER 2 TECHNICAL DIRECTIVE REQUIREMENTS AND PROCEDURES 2.1 INTRODUCTION. 2.1.1 Retrofit configuration changes to delivered Naval aviation systems including aircraft, airborne weapons, airborne systems and system components, aircraft launch and recovery equipment, aviation support equipment, and training systems shall be made only upon receipt of an approved TD, with the following exceptions: a. Operating commanders are authorized to take actions deemed necessary to ensure safe operation of assigned aviation systems per COMNAVAIRFORINST 4790.2 (Series) and OPNAVINST M-8000.16. b. TYCOMs/controlling custodians may authorize one prototype installation (Per TYCOM) of a proposed change per COMNAVAIRFORINST 4790.2 (Series) and OPNAVINST M-8000.16. NOTE A prototype is not an authorized configuration change as it is, by definition, a test of concept or process and is used to test the concept or process. See paragraph f. below for complete definition. Because prototypes are not authorized configuration changes, they must be used sparingly and must be followed up with incorporation via a published formal TD. c. Record Purpose category TDs are authorized for installation after Configuration Control Board (CCB) approval, but prior to the formal TD being issued. Record Purpose TDs are for Depot (D-) Level changes only and shall not be used for changes that are incorporated at (O-) Level or (I-) Levels. Record Purpose TDs must be written in past tense as all incorporations have occurred prior to TD issuance. d. Installation and removal of missionized equipment on an aircraft does not require a TD. If a configuration change is required for an item of missionized equipment, it will be treated as any other configuration item and will follow the policy and procedures for a configuration change. This includes CCB approval and then a TD to accomplish and track that approved configuration. The TD type would be dependent on whether an aircraft, or other component, modification would be required for the mission equipment for it to operate or to be attached. e. Release and installation of data files; however, this exclusion shall not apply to any data file that is produced as part of an Engineering Change Proposal (ECP). 2-1 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 NOTE “Data files” refers to static, uncompiled data that does not alter the software footprint. This data is simply input, through defined interfaces, to its associated software. Examples of data files include: Threat data. Navigation data. Digital terrain data. Miscellaneous parametric data. Other data files that provide static input to the mission critical computer software addressed in this manual and/or NAVAIRINST 4130.1 (series), Naval Air Systems Command Configuration Management Policy. This type of change will be released via plain language message (see Figure 2-1 for formatting). “Software” refers to executable machine code that is produced by an assembler or compiler. Software does not include the data (or data files) that are processed by an application program or system software such as operational flight or mission planning for combat system data entry programs. f. PROTOTYPE. A prototype is an early sample, model, or release of a product built to test a concept or process. It is a term used in a variety of contexts, including semantics, design, electronics, and software programming. System analysts and users generally use a prototype to evaluate a new design to enhance precision. 2-2 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 FM COMMAND//OFFICE CODES//(AS APPROPRIATE)// TO DESTINATION COMMAND PLAIN LANGUAGE ADDRESS DESIGNATOR (PLAD) NOTE: THE USE OF CNAF AIGS CAN BE AUTHORIZED FOR DISTRIBUTION OF DATA FILES INFO (ADDRESS) PLAD BT UNCLASS//NXXXXX//(CLASSIFY AS APPROPRIATE)//(USE APPROPRIATE STANDARD SUBJECT IDENTIFICATION CODE (SSIC)) MSGID/GENADMIN/COMMAND IDENTIFIER// SUBJ/LIST APPROPRIATE DATA FILE NAME AND VERSION WITH SUFFICIENT DETAIL FOR RECIPIENT TO IDENTIFY LOAD FOR APPROPRIATE SYSTEMS (WUC XXXXXXX, AND AIRCRAFT AFFECTED BY TMS REF/A/DOC/NAVAL AIR SYSTEMS COMMAND/NAVAIR SOP 00-25-300/YMD: 20150730 NOTE: THIS AND SUBSEQUENT REFERENCES SHOULD INCLUDE ANY MESSAGES FOR WHICH THIS RELEASE ADRESSES ISSUE. HOWEVER, REF A WILL ALWAYS BE THE MOST CURRENT VERSION OF NAVAIR 00-25-300. AMPN/NARR/REF A IS TD SYSTEMS MANUAL. PARAGRAPH 2.1.1.E EXEMPTS DATA FILES FROM THE TECHNICAL DIRECTIVES PROGRAM EXCEPT THOSE RELEASED AS PART OF AN ECP. PROVIDE APPROPRIATE AMPLIFICATION OF ADDITIONAL REFERENCES AS REQUIRED./ POC/NAME, INIT/RANK:CALL SIGN:UNIT IDENTIFIER/LOCATION/TEL:COMM XXX-XXX- XXXX/TEL:DSN XXX-XXXX. NOTE: THE POC LIST SHOULD INCLUDE THE FOLLOWING: 1. LOGISTICS POC 2. ENGINEERING POC 3. TECHNICAL POC (IF REQUIRED) GENTEXT REMARKS: 1. COG CODE: PMA-XXX IS RESPONSIBLE FOR THIS DATA FILE UPDATE. Figure 2-1. Data File Format (Sheet 1 of 4) 2-3 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2. PURPOSE: DEFINE PURPOSE OF DATA FILE, PLATFORM, THEATRE OF OPERATION, AND PASSING INSTRUCTIONS, AS REQUIRED. APMLIFICATION OF THE ISSUES ADDRESSED IN THE DATA FILE MAY BE APPROPRIATE. INCLUDE A LIST OF SOFTWARE TROUBLE REPORTS THAT THIS UPDATE WILL FIX IF APPLICABLE. IN CASES WHERE DATA FILE CROSSES PLATFORMS/EQUIPMENT SUITES, INCLUDE THE FOLLOWING: THIS IS A COORDINATED (LIST PMAS AND/OR SSAS INVOLVED/IMPACTED) FLEET RELEASE NAVAL MSG. 3. SOFTWARE (S/W) MANAGER RELEASER: A. S/W MANAGING ACTIVITY (1) NAME (2) OFFICE (3) CODE B. S/W RELEASING ACTIVITY (1) NAME (2) OFFICE (3) CODE 4. DOCUMENTS AFFECTED: LIST AND DESCRIBE ALL MANUALS, OR OTHER DOCUMENTS REQUIRING UPDATE, AS A RESULT OF THE RELEASE OF THIS DATA FILE. 5. APPLICATION: DESCRIBE APPLICABILITY IN ENOUGH DETAIL AS TO LEAVE NO ROOM FOR MISINTERPRETATION AS TO WHICH AIRCRAFT AND WRA THE DATA FILE APPLIES. A. AIRCRAFT TMS OR EQUIPMENT: DEFINE TO SUCH DEGREE AS NECESSARY TO AVOID CONFUSION, THE PLATFORM TO WHICH THIS FILE IS TO BE INSTALLED. B. WRA: DEFINE THE WEAPONS REPLACEABLE ASSEMBLY TO WHICH THE FILE APPLIES. THE FOLLOWING FIELDS SHOULD BE UTILIZED TO THE FULLEST EXTENT POSSIBLE TO AVOID CONFUSION AS TO WHICH WRA THIS UPDATE APPLIES. (1) PART NUMBER (2) NOMENCLATURE (3) CAGE (4) SERIAL NUMBER (AS APPLICABLE) 6. PRESENT AND NEW SOFTWARE CONFIGURATION IDENTIFICATION: DESCRIBE, TO SUCH DEGREE AS NECESSARY TO AVOID CONFUSION, THE PRESENT SOFTWARE CONFIGURATION PART NUMBER/NOMENCLATURE, AND NEW SOFTWARE CONFIGURATION PART NUMBER/NOMENCLATURE. A. READ IN FIVE COLUMNS: NOMEN FILENAME OLD VER NEW VER ID DISPLAY AN/XXX-XXX XXXX-XXXX-X XXXX-XXXX XXXX-XXXX X-X Figure 2-1. Data File Format (Sheet 2 of 4) 2-4 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 7. DISTRIBUTION PROCEDURES: DESCRIBE, TO SUCH DEGREE AS NECESSARY TO AVOID CONFUSION, THE PROCESS FOR DISTRIBUTION. ENCOURAGE THE NAVAL DATA DISTRIBUTION SYSTEM (NDDS) BE USED AS THE PRIMARY MODE OF DISTRIBUTION. ENSURE DETAILED INSTRUCTIONS ARE INCLUDED IN THE BODY OF THIS PARAGRAPH. FOR EXAMPLE: 7. DISTRIBUTION PROCEDURES: THREAT DATA FILES HAVE BEEN PREVIOUSLY PROVIDED TO FLEET USER ACTIVITES VIA US MAIL-DISTRIBUTED PCMCIA CARDS. SINCE MAY 2008, THREAT DATA FILES PRIMARILY WILL BE DISTRIBUTED VIA NDDS SECURE SIPRNET WEBSITE. FLEET ACTIVITIES MAY DOWNLOAD THE REQUIRED FILES BY ACCESSING THE NDDS THROUGH A SIPRNET CONNECTION ON A CLASSIFIED COMPUTER AT HTTP://NDDS.MUGU.NAVY.SMIL.MIL. ONCE THE WEBSITE HOMEPAGE LOADS, CLICK “ENTER THE SITE.” IF THE USER DOES NOT ALREADY HAVE AN NDDS ACCOUNT, CLICK “NEW USER REGISTRATION” TO OBTAIN A MSGID/GENADMIN, USMTF 2021/COMNAVAIRFOR SAN DIEGO CA/ACCOUNT. OTHERWISE, ENTER USER NAME AND PASSWORD THEN CLICK “LOGIN.” THE USER WILL BE DIRECTED TO A SCREEN DISPLAYING ALL OF THE PLATFORMS/SUPPORT EQUIPMENT AVAILABLE FOR ACCESS AS WELL AS WEBSITE ANNOUNCEMENTS. SELECT ONE OF THE BUTTONS ON THE LEFT FOR DESIRED AIRCRAFT PLATFORMS/SUPPORT EQUIPMENT. NOTE: THESE FILES ARE CLASSIFIED, THUS THE USB THUMB DRIVE/PCMCIA CARD/DISKETTE WILL BE CLASSIFIED. APPLY SECURITY MEASURES AS APPLICABLE. TO ACCESS PLATFORMS, CLICK ON THE RESPECTIVE AIRCRAFT PLATFORM FOLDER AND ALL FILES AVAILABLE WILL BE LISTED TO THE RIGHT. LOCATE THE BOLD TYPE HEADER FOR TYPE FILE DESIRED. UNDER THIS HEADER LOCATE THE DESIRED FOLDER. THE FIRST FILE LISTED IN THE FOLDER WILL BE A README FILE CONTAINING DETAILED DOWNLOAD INFORMATION/PROCEDURES. THE SECOND FILE LISTED WILL BE THE SPECIFIC THREAT DATA FILE(S), AND HAS AN.RRT FILE EXTENSION. FOR YOUR DATA FILE UPDATE CLICK “DOWNLOAD” NEXT TO APPLICABLE FILE SAVE THIS COMPOSITE FILE TO THE USER’S MACHINE. ONCE THE FILE HAS BEEN DOWNLOADED TO THE USER’S MACHINE, FOLLOW THE PROCEDURES CONTAINED IN THE “README” DOCUMENT. 8. SOFTWARE LOADING INSTRUCTIONS: DECRIBE, TO SUCH DEGREE AS NECESSARY TO AVOID CONFUSION, THE SOFTWARE LOADING INSTRUCTIONS FOR AIRCRAFT/COMPONENT. Figure 2-1. Data File Format (Sheet 3 of 4) 2-5 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 9. VERIFIED BY: DEFINE THE ACTIVITY/SQUADRON, AND IF APPLICABLE, AIRCRAFT ON WHICH DATA FILE LOADING PROCESS WAS VERIFIED. INCLUDE VERIFICATION RESULTS. IF APPLICABLE TO MORE THAN ONE AIRCRAFT/EQUIPMENT TYPE/MODEL/SERIES (T/M/S) DATA FILE LOADING PROCESS SHALL BE VERIFIED ON EACH AFFECTED AIRCRAFT/EQUIPMENT T/M/S. 10. RELATED INSTRUCTIONS/INFORMATION: A. TRAINING AND ASSOCIATED TRAINING TECHNICAL DATA UPDATED B. RELEASE NOTES PROVIDED VIA SEPCOR. 11. TYCOM/ACC CONCURRENCE/AMPLIFYING REMARKS: FOR EXAMPLE A. COMNAVAIRFOR: CONCURRED (DD/MMM/YYYY) VIA EMAIL. (1) COMMENTS, ADDITIONAL/AMPLIFYING REMARKS: CNAF N421 HAS REVIEWED AND CONCURS WITH THIS DATA FILE MESSAGE AND DIRECTS ALL CNAF ACTION UNITS TO TAKE FORAC. (2) POC: (NAME RANK CODE), DSN XXX-XXXX, COMM (XXX) XXX-XXXX. B. COMNAVAIRFORES: CONCURRED (DD/MMM/YYYY) VIA EMAIL. (1) COMMENTS, ADDITIONAL/AMPLIFYING REMARKS: COMNAVAIRFORES HAS REVIEWED AND CONCURS WITH THIS DATA FILE MESSAGE AND DIRECTS ALL COMNAVAIRFORES ACTION UNITS TO TAKE FORAC. (2) POC: (NAME RANK CODE), DSN XXX-XXXX, COMM (XXX) XXX-XXXX. C. COMNAVAIRSYSCOM ACCO: CONCURRED (DD/MMM/YYYY) VIA EMAIL. (1) COMMENTS, ADDITIONAL/AMPLIFYING REMARKS: ACCO HAS REVIEWED AND CONCURS WITH THIS DATA FILE MESSAGE AS WRITTEN. (2) POC: (NAME RANK CODE), DSN XXX-XXXX, COMM (XXX) XXX-XXXX. D. CNATRA: CONCURRED (DD/MMM/YYYY) VIA EMAIL. (1) COMMENTS, ADDITIONAL/AMPLIFYING REMARKS: CNATRA HAS REVIEWED AND CONCURS WITH THIS DATA FILE MESSAGE AS WRITTEN. (2) POC: (NAME RANK CODE), DSN XXX-XXXX, COMM (XXX) XXX-XXXX. Figure 2-1. Data File Format (Sheet 4 of 4) NOTE The plain language message referred to in Figure 2-1 is not issued as a TD and does not require compliance via DECKPLATE-TDRS or CM/DM concurrence. 2-6 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 g. Attrition implementation actions are those actions that must be a complete replacement of similar items with no impact on form, fit, or function. Form, Fit, and Function as described by the EIA-649-1A and NAVAIR 4130.1 SOP are as follows: FORM: The shape, size, dimension, mass, weight, cleanliness, recertification/expiration date, and other measurable parameters, which characterize an item. For software, form denotes operating systems, compilers, input/output schemas, and formats. FIT: The ability of an item to interface or interconnect with or become an integral part of another item. FUNCTION: (1) The action or actions which a system or system component is designed to perform. (2) The actions or actions which the user, operator, or maintainer is expecting to perform, or which a system or system component is designed to perform. NOTE A configuration change is defined as an alteration of the form, fit, or function of a configuration item. As such, a configuration change cannot be processed via attrition. NOTE The addition or removal of parts within an item violates this function requirement and would require a TD to be issued. Level of configuration control is the main driver in making this decision. These implementation actions are not driven as a forced retrofit and no TD is issued. This is because no configuration change is involved and no modification of the Configuration Item (CI) is performed. These actions are made via exhaustion of the original configuration item. The PMA processing the attrition action will be responsible for its implementation documentation for configuration management status accounting. It is imperative the applicable NALCOMIS OOMA BLM is included as part of the ECP review and approval process to ensure new configuration identification information is added to the NALCOMIS OOMA baseline. An example of a typical attrition implementation action is when a manufacturer goes out of business or no longer produces an item, and a new manufacturer is qualified with a new part number. This new manufactured part has the same form, fit, function as the original CI. This new part number is added to publications allowing usage as an alternate part number. Original CIs will be used until exhausted. 2-7 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 h. Once an ECP/CCB is approved using the Enterprise Change Management (ECM) tool, the TD(s) must be routed for review using the same tool with the TD Object workflow. The Assistant Program Manager for Logistics (APML)/Configuration Manager (CM) will be responsible for establishing and maintaining the distribution/approvals required for each TD. By using the same tool for review and routing, all applicable history and documentation will either be in the same folder or be linked for all reviewers to refer to when/if needed. This will eliminate printing and routing paper documents, reducing workload and costs. After TD review is complete, routing TD for approval signature shall be done in the same ECM tool as the review. Specifics on the process for this routing will be described later in this SOP. To be complete, other reference documents must also be loaded in the routing folder, such as TD Verification Certification Form (5215/12), TD Logistics Support Checklist (5215/9), and any other supporting documentation. 2.1.2 All TDs shall be issued by the Commander, Naval Air Systems Command (NAVAIR). 2.1.3 All TDs will be issued following the format and business rules dictated in the applicable appendices of this SOP. 2.1.4 NAVAIR technical manuals, or parts thereof, shall not be used as parts of TDs. Requirements of technical manuals should be referenced in TDs. 2.1.5 Local Engineering Specifications (LESs), Local Engineering Directives (LEDs), Local Engineering Processes (LEPs), Maintenance Engineering Directives (MEDs) or other engineering advisories are not Technical Directives and shall not be used to incorporate configuration changes on aircraft, engines, components, or support equipment. 2.1.6 Airworthiness Directives (ADs) issued by the Federal Aviation Administration (FAA), Air Force Time Compliance Technical Orders (TCTOs), Army Modification Work Orders (MWOs) and Manufacturer Service Bulletins/Advisories, shall be implemented via the appropriate type of NAVAIR Technical Directive In Accordance With (IAW) this SOP, if applicable to Naval equipment owned and managed by NAVAIR. 2.1.7 Flight clearances do not provide authorization to modify aircraft; they only provide authorization to fly an aircraft in a certain configuration. Flight clearances (Interim or Permanent) must be approved and released prior to TD Validation (Prototype or Verification being performed) if the modification is to remain installed. 2.1.8 Placing a TD in abeyance is done by issuing a naval message after concurrence with all stakeholders. This abeyance pertains to the entire TD, and only the entire TD, and shall not be issued for one specific aircraft. The abeyance message can be released by the PMA with TYCOM concurrence or by the TYCOM with PMA concurrence. Taking a TD out of abeyance is also processed via a message with the same concurrences as required for placing it in abeyance. If changes to an issued TD are required, then an amendment or revision must be issued to correct/make changes. 2-8 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.2 TECHNICAL DIRECTIVE TYPES. NAVAIR uses four types of TDs: Formal Change, Interim Change, Bulletin, and Rapid Action Minor Engineering Change (RAMEC). The purpose and uses of each TD type are discussed in the following paragraphs. NOTE All TDs will be issued in a paper format using the appendix applicable to that TD type. All TDs will be processed for review and approval via the command ECM tool using the TD Object folder type and workflow. This includes amendments and revisions. 2.2.1 FORMAL CHANGE. A formal change TD is the primary NAVAIR document for implementing a configuration change. A formal change TD contains instructions and information which direct accomplishment and recording of a material change, repositioning, modification, or an alteration of the characteristics of a system. It shall be used to direct the addition, removal, alteration, relocation, or change of parts of material from an existing configuration. A Formal Change TD is always identified by title as an “Airframe” Change (AFC), “Avionics” Change (AVC), etc. (see paragraph 2.4 for a complete list of TD titles). Further details concerning the preparation and processing of Formal Change TDs, Foreign Military Sales (FMS) and Commercial Derivative Aircraft (CDA), as well as Software Changes, are contained in the Appendix for that type of TD. 2.2.2 INTERIM CHANGE. Sometimes, urgency requires temporary change incorporations to be initiated without delay, following Configuration Control Board (CCB) approval. In such cases, proposed changes are submitted to NAVAIR and are disseminated immediately after approval. These TDs are designated “Interim Change” (e.g., Interim Airframe Change (IAFC), Interim Avionics Change (IAVC), etc.) and are filed in publications libraries in the same manner as Formal Change TDs. They are designed to meet Urgent requirements and only apply to a portion of the inventory (no more than 25 percent of the inventory) of the affected item to meet that Urgent requirement. They must not include the entire inventory, as they are considered as a temporary change and all logistical elements are not addressed until the formal ECP is processed. If more of the inventory must be included, a TD Waiver form must be processed through the CM/DM Group during CCB review and approval to justify the requirement. All logistical elements must be in place to support the additional requirements. Although some elements are not fully supported during the interim process, all elements, such as kit numbers, part numbers, calibration, and interim rapid action changes (IRACs)/electronic rapid action changes (ERACs) must be addressed to support the LIMITED effectivity of the ITD. The draft ITD is used instead of a formal ECP. If an ECP is available, it must be submitted and there should be no reason for an interim TD. If no ECP is available, then a draft ITD must be submitted along with a completed Change Request Directive package, instead of an ECP. 2-9 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 When an Interim Change TD is issued, a formal ECP shall be obtained within 180 days from CCB approval of the interim TD to permit thorough review of all engineering and logistic elements of the change. This formal ECP is processed as a separate CCB action from the interim CCB action. Although separate folders, these must be linked together for historical review and reference. After ECP review and CCB approval, a Formal Change TD shall be issued to supersede the Interim Change TD. Further details concerning the preparation of ITDs are contained in Appendix B of this SOP. NOTE Once an ITD is issued as a formalized TD via an approved formal ECP, an interim TD shall not be issued using the same TD number. If a different Interim TD is required, then a new ITD number shall be obtained even if the ECP number remains the same. 2.2.3 BULLETIN. All Bulletins are “Sacred” and should be treated as such. Appropriate action must be taken to expedite their completion in order to mitigate their inspection requirements and return aircraft and equipment to a full mission capability. A bulletin TD directs an event-based inspection of aircraft or equipment to determine if a given condition exists and specifies what action shall be taken if the condition is found. It may contain instructions for corrective action using approved repair procedures, provided no change in configuration is involved. Or it may require issuance of a change TD to remedy a deficiency. Bulletins are issued using the Urgent or the Immediate category. Bulletins shall not be used to gather data or information from maintenance records that can be acquired from OOMA or DECKPLATE maintenance records. This should be done through other means of correspondence. These actions are not caused by a defect or sustainment issue, but rather a maintenance malpractice (such as looking for a Collateral Duty Quality Assurance Representative (CDQAR) Stamp) that should be handled by a Chief Naval Air Forces (CNAF)/Program Manager AIR (PMA) issued One- Time Conditional Inspection vice a Bulletin TD. This type of usage overburdens the TD process and other maintenance data systems. An example of this would be inspecting an aircraft logbook, or another maintenance record document, just to look for a particular maintenance action, inspection completion, or repair. Another example would be looking for a CDQAR stamp and re-inducting a piece of equipment for re-inspection. Bulletins shall not be used instead of technical manual changes (e.g., to establish continuing maintenance/inspection requirements). Use of the term One-Time Inspection is not allowed in Bulletin TDs. Any bulletin exceeding 10 man-hours to complete must be concurred with TYCOM leadership at the GS-15/O-6 level or above, as well as NAVAIR, prior to being issued. Verification must be performed on all bulletins that are issued even if a Bulletin Support Document (BSD) is provided to supplement compliance of the bulletin. A waiver of verification can be processed if urgency outweighs the need for accuracy, utilizing the procedures within this SOP. Bulletins that restrict flight operations by requiring inspection prior to further flight, preflight, turn-around, daily inspection, next equipment use, or within the next ten flight hours are referred to as “Grounding Bulletins.” Because of their operational impact, Grounding Bulletins require special coordination and concurrences with 2-10 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 TYCOMs/Controlling Custodians, with concurrence from SUSTAINMENT GROUP, ENGINEERING, CNO, and when applicable, CMC, and approved by AIR-00, via the Red Stripe Memorandum Process, before being released. For details concerning the Red Stripe process, refer to the NAVAIRINST 13100.17 series. For step-by-step processing of Grounding Bulletins and the Red Stripe Memo, refer to the Product Support Management/Integration Department SWPV411-002. Bulletins that have significant operational impact due either to imposed flight/operational limitations, or to severe/unique impact on logistic support, are referred to as Flight Restriction Bulletins. Flight Restriction Bulletins shall be processed in the same manner as Grounding Bulletins. Further details concerning the preparation and processing of Grounding Bulletin TDs are contained in Appendix C of this SOP. The differences between Grounding and Flight Restriction Bulletins, and other Bulletins, are the TD category/urgency, and the Red Stripe Memorandum Process. Bulletin numbers are assigned using the bulletin number assignment section of NATEC website. This is a role based assignment so only those authorized can obtain bulletin number assignment. 2.2.4 RAMEC. The concept of the RAMEC program is “fleet self-help.” Procedures are designed so that minor engineering changes may be processed quickly and, after approval, incorporated promptly by (O-) Level and/or (I-) Level maintenance activities, to ensure commonality of configuration throughout the inventory. (D-) Level incorporation is not authorized for Support Equipment, except for Support Equipment which is used at both the (I-) Level and (D-) Levels. Changes approved IAW RAMEC procedures are issued as numbered TDs. Proposed RAMECs are initiated by fleet activities, FST/ISSCs, or engineering activities in response to requirements identified by fleet activities. PMAs, NAVAIR System Headquarters, or contractors may not sponsor or initiate RAMECs. RAMECs shall not be used to affect retrofit of, or to satisfy logistics requirements resulting from, Class II changes. RAMECs shall not be used to introduce new parts into aircraft or equipment. Those changes must be introduced via a Class 1 (Major) ECP. This includes new parts manufactured via Additive Manufacturing. Fleet activities must request RAMEC sponsorship from their controlling custodians prior to prototyping one item per COMNAVAIRFORINST 4790.2 (Series). After successfully prototyping a prospective RAMEC, the proposed RAMEC TD will be prepared and forwarded to the sponsoring controlling custodian for processing. NAVAIR ISSCs may initiate, and sponsor proposed RAMECs on items for which they have primary cognizance, provided they accept responsibility for coordinating related fleet support and obtaining concurrences from affected TYCOMs/Controlling Custodians. RAMECs are issued as change TDs (e.g., AFCs, AVCs) within seven working days of CCB approval. Drawings and publications impacted by RAMECs are updated to provide for subsequent parts procurement and maintenance instructions for the modified aircraft, systems, or components. RAMECs are considered a Formal TD. 2-11 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 NOTE When a RAMEC is modifying an item of supply, re-identification of the modified item may be required (i.e., new part number). When re-identification is required, the ISSC will obtain new part numbers from contractors when the master drawings are held by the contractor or assign a new ISSC part number. The following guidelines apply: When master drawings are held by a contractor who agrees to update the drawings to reflect the proposed design change, the ISSC shall obtain the estimated cost to update the drawings from the contractor and include them in the proposed RAMEC. When master drawings cannot be located or when master drawings are held by a contractor who refuses to modify them to reflect the design change, the RAMEC may be forwarded to NAVAIR Headquarters (HQ) for approval, only if the cognizant ISSC is prepared to create new drawings and to serve as the production source for the modified parts. In these cases, the ISSC shall provide cost estimates for creating the new drawings. Use of the RAMEC TD is restricted by its special application. In order to receive NAVAIR approval, a RAMEC must: a. Be limited to minor engineering changes to aircraft, unpiloted and remotely piloted aerial vehicles, related power plants/propulsion units, components, airborne armament equipment, aerial refueling stores, external tanks, support equipment, aviation life support systems, and airborne weapon systems. Software changes to any of the previous items shall not be processed as a RAMEC. b. Be verified before submitting proposed RAMECs to NAVAIR for review and CCB approval. TYCOM concurrence of verification messages can be used as the Decision Memo (DM) for CCB review and approval. c. Be confined to a simple change that can be easily and rapidly incorporated, and that does not require extensive technical review or work effort. The RAMEC process cannot be used for issuing software changes due to the validation/verification processes required for developing software coding being outside the (O-) Level and (I-) Level capabilities. d. Be authorized for incorporation by (O-) Level or (I-) Level maintenance activities, including regular contractor maintenance support at those levels. (D-) Level incorporation is not authorized except in the case of RAMECs for support equipment which is used at both (I-) Level and (D-) Levels. 2-12 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 NOTE RAMECs will not normally be incorporated by (D-) Level maintenance activities. However, if a TD is being incorporated by a (D-) Level and an unincorporated RAMEC is a prerequisite, the RAMEC may be incorporated by the (D-) Level. e. Require no more than eight maintenance man-hours per installation to accomplish. Requirement can be greater than eight man-hours if concurred with by TYCOM but is greatly discouraged. This specific TYCOM concurrence must be provided during CCB review and approval and documented within the ECM. f. Use only standard stock items and/or raw materials and source-coded items that may be manufactured by the cognizant FRC. This material should be readily obtainable by a requesting activity through normal supply system requisitioning procedures. The total cost of the material required should not exceed $1,500 per installation. For the purposes of satisfying this requirement, items procured for specific applications and local open-purchase items are not considered “standard stock items.” Parts included in the supply requirement, are those parts used by the FRC to manufacture piece parts. g. Not exceed the $1,500 limit but meet all other RAMEC requirements. RAMECs must have TYCOM concurrence, specifically addressing the cost overage, during CCB review and approval. Specific documentation of this concurrence must also be included in the ECM tool. h. Be complied with as directed by the applicable TD, but not later than the next Calendar/Phase inspection requiring access to the area/zone containing the items(s) to be changed, or next induction of the item(s) into an (I-) Level maintenance activity. i. Be coordinated with, and agreed to by, each affected controlling custodian, PMA, and In-Service Support Center (ISSC). j. Be coordinated with, and agreed to by, the Center for Naval Aviation Technical Training Unit (CNATTU) when trainers under its cognizance are affected. k. Provide for modification of spares and trainers, if affected. l. Not require the development, fabrication, procurement, or stocking of retrofit kits. m. Not be used to amend or supplement an existing Interim or Formal TD. n. Not generate a requirement for additional or new support equipment, with an aircraft RAMEC. 2-13 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 o. Not generate a change to O- Level support equipment. p. Not affect operational or avionics automatic test equipment or missile subsystems test sets, or the software programs and/or tapes associated therewith. q. Not require changes to general-purpose electronic test equipment under the technical/procurement cognizance of the Space and Naval Warfare Systems Command. r. Not generate a requirement for new technical manuals. If updates to existing technical manuals are required, based on an issued RAMEC, then an IRAC shall be issued for those updates to cover the timeframe from TD issuance to formal publication update. s. Not apply to items having a Source, Maintenance, and Recoverability (SM&R) code with “D” in the fourth position, except support equipment items. t. Not apply to non-consumable items procured and managed by another service. (Formal ECPs are required to change such items.) Further details concerning the preparation and processing of RAMEC TDs are contained in Appendix D of this manual. 2.3 TECHNICAL DIRECTIVE CATEGORIES. A TD shall be assigned one of four categories depending upon its type, urgency, or purpose. A Formal Change TD, issued to supersede an ITD, shall be assigned the same category as the ITD. The four TD categories are Immediate Action, Urgent Action, Routine Action, and Record Purpose. General criteria for assigning TD categories are as follows: 2.3.1 IMMEDIATE ACTION. The Immediate Action category is assigned when unsafe conditions exist. If uncorrected, these conditions could result in fatal or serious injury to personnel or extensive damage to, or destruction of, valuable property. Such conditions embody risks that are calculated to be unacceptable. The urgency of these TDs requires immediate action to ground aircraft, prevent launch of missiles, or deny the use of related support equipment or munitions. Whenever possible, methods for correcting the unsafe condition are included in the Immediate Action TD. Assignment of this category shall be justified by incident, accident, hazard, or similar reports, and must be concurred with by CNO/CMC. Immediate Action TDs require compliance prior to next flight, next use of equipment, or within the next 10 flight hours. This category is primarily only used on Grounding Bulletins and is used in conjunction with the Red Stripe Memorandum process. 2-14 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.3.2 URGENT ACTION. The Urgent Action category is assigned when factors of combat necessity present hazardous conditions that could result in personal injury or damage to valuable property; when unacceptable reductions in operational readiness exist; and when such conditions, if uncorrected, compromise safety or embody risks that are calculated to be acceptable within defined time and/or performance limits. These conditions are less serious than those for which the Immediate Action category would be assigned. Urgent Action TDs shall require compliance within specified time limits. Assignment of this TD category is based on a timeframe greater than 10 flight hours to 36 months but is not to be used to assign a compliance statement. This timeframe is not indicative for a bulletin that is issued to correct an Urgent issue. Bulletin TDs must be evaluated for specific compliance times that should be as soon as possible to correct the condition for which they are being issued. The 36-month timeframe is designed for change TDs that take longer to acquire and schedule change compliances. Compliance timeframes will be assigned in the Compliance element of each TD. If compliance is not accomplished by expiration of the specified time limit, action will be required to ground aircraft, discontinue use of air-launched weapons, prevent launch of missiles, discontinue operation of ground communications, electronic or meteorological equipment, or discontinue use of support equipment, personnel equipment, materials, or munitions. Any TD that is specified as a “Safety” change must use this category. 2.3.3 ROUTINE ACTION. The Routine Action category will be assigned whenever the urgency of the situation does not warrant assignment of the Immediate or Urgent Action categories and the assignment of Record Purpose would be inappropriate. The Routine Action category shall not be assigned to ITDs or Bulletins. Assignment of Routine Action is appropriate when conditions exist which embody degrees of risk calculated to be acceptable within broad time limits. Governing factors include equipment or procedural deficiencies of a material, mechanical, operational, or tactical nature, the uncorrected existence of which could: a. Constitute a hazard through prolonged use. b. Have a negative effect on operational effectiveness or readiness. c. Reduce tactical utility or supportability. d. Reduce operational service life. Routine Action TDs are issued to authorize retrofit changes and provide detailed instructions for installing those changes. Assignment of this TD category is based on the timeframe of greater than 36 months but is not to be used to assign a compliance timeframe. Compliance timeframes will be assigned in the Compliance element of each TD. 2-15 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.3.4 RECORD PURPOSE. The Record Purpose category is assigned to Formal Change TDs issued to document configuration changes that have been incorporated in all affected equipment by the change designer/originator, before the TD is issued. The following restrictions apply to assignment of the Record Purpose category: a. TDs issued to supersede and formalize ITDs may not be Record Purpose. b. Bulletins, ITDs, and RAMEC TDs may not be assigned the Record Purpose category. c. The Record Purpose category may be assigned only to Formal Change TDs and only when the period for change incorporation in all affected systems is 18 months, or less, from date of CCB approval. d. Documentation of TYCOM concurrence shall be provided prior to assignment of the Record Purpose category. This must be accomplished prior to NAVAIR CCB approval. e. Record Purpose category cannot be used on (O-) Level or (I-) Level incorporation TDs. This is applicable to (D-) Level TDs only. f. If compliance is recorded by SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH in DECKPLATE-TDRS, it will show on all compliance reports as Incorporated. OOMA processing must also be completed to reflect incorporations. g. Record Purpose TDs must be written in past tense as all modifications are performed prior to TD issuance. h. All aircraft BUNOs or component serial numbers must be included in the application element as all modifications have been completed prior to TD issuance. 2.4 TECHNICAL DIRECTIVE TITLES, CODES AND NUMBER. 2.4.1 GENERAL. Each TD is assigned a title by the Assistant Program Manager Logistics/Logistics Manager (APML/LM) after collaboration with the PMA Configuration Management Point of Contact (CM POC). TD titles are assigned to appropriately reflect the object or purpose of the TD. The end item being modified or inspected should determine the TD code selected. Removal and replacement of a component from an aircraft that does not involve on-the-spot modification and re-installation of the same component should be considered an Airframe Change (AFC) because the end item modified is the aircraft (for example if an RT-1234 is replaced with an RT-5678). If the removed component is to be modified and will be returned to the fleet, then a separate component level TD must be initiated. Selection of the TD type must not be made without considering the impact on Auto Logsets (ALS), proper documentation practices, 2-16 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 obtaining NALCOMIS OOMA Baseline Management, and functionality verification. Compliance level will also play an important role in this decision. For example, a change, or a RAMEC affecting an airframe or integral airframe component, would be given the title, “Airframe Change” (AFC). A similar Interim Change would be titled, “Interim Airframe Change” (IAFC), and a Bulletin would be titled, “Airframe Bulletin” (AFB). TD titles are represented by TD Codes in the CNAFINST 4790.2 Series (NAMP) and DECKPLATE-Technical Directive Reporting System. For example, all AFCs, including IAFCs, are represented by TD CODE 50 and all AFBs by TD CODE 74. The TD titles currently in use are described in the following paragraphs. Associated title abbreviations and TD Code numbers for Changes and Bulletins are shown immediately after each title. Table 2-1 shows all TD titles listed in TD Code number sequence. In addition to TD titles and TD code numbers, NATEC assigns each TD a unique TD number; this includes assignment of TD Parts, Revision letters and Amendment numbers. Change TD numbers are assigned immediately following CCB change approval. Bulletin TD numbers are assigned through NATEC by pre-approved user accounts prior to release for compliance. TDs are either numbered sequentially by title (e.g., Avionics Change 3500) or sequentially by title within specified type/model of equipment (e.g., F-18 Airframe Change 100). When a TD is applicable to a foreign country under an FMS program, the two-letter “Country Organization and Code,” found in DOD 5105.38-M, is placed after the TD number (e.g., P-8 AFC-2(JA) for Japan). It is recommended that each FMS country be issued their own separate TD to eliminate any releasability issues. It is also not recommended to issue combination FMS/Domestic US TDs as each has their own specific rules for content. 2-17 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 Table 2-1. Technical Directive Code Numbers CODE TITLE CODE TITLE 01 Power Plant Bulletin (PPB) 66 Aircrew System Change (ACC) 02 Power Plant Change (PPC) 67 Aircrew System Bulletin (ACB) 03 Quick Engine Change Kit Change 68 Photographic Change (PHC) (QEC) 04 Quick Engine Change Kit Bulletin 69 Photographic Bulletin (PHB) (QEB) 05 Training Equipment Change 73 Meteorological Equipment Change (TEC) (MEC) 06 Training Equipment Bulletin (TEB) 74 Airframe Bulletin (AFB) 07 Reusable Container Change 75 Airborne Weapon Change (AWC) (RCC) 08 Reusable Container Bulletin 76 Airborne Weapon Bulletin (AWB) (RCB) 40 Commodity Software Change 77 Target Control System Change (TCC) (CSC) 41 Commodity Software Bulletin 78 Target Control System Bulletin (TCB) (CSB) 50 Airframe Change (AFC) 79 Meteorological Equipment Bulletin (MEB) 51 Dynamic Component Change 83 Aircraft Launch and Recovery Equipment (DCC) (ALRE) Ship Installed/Expeditionary Airfield Change (LRC) 52 Dynamic Component Bulletin 84 Aircraft Launch and Recovery Equipment (DCB) (ALRE) Ship Installed/Expeditionary Airfield Bulletin (LRB) 54 Avionics Change (AVC) 91 Naval Air Maintenance Trainer Change (NTC) 55 Avionics Bulletin (AVB) 92 Naval Air Maintenance Trainer Bulletin (NTB) 2-18 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 CODE TITLE CODE TITLE 56 Aviation Armament Change (AAC) 93 Airborne Software Change (ASC) 57 Aviation Armament Bulletin (AAB) 94 Airborne Software Bulletin (ASB) 58 Accessory Bulletin (AYB) 95 Support Software Change (SSC) 61 Accessory Change (AYC) 96 Support Software Bulletin (SSB) 62 Support Equipment Change (SEC) 97 Naval Air Maintenance Trainer Support Software Change (TSC) 63 Support Equipment Bulletin (SEB) 98 Naval Air Maintenance Trainer Support Software Bulletin (TSB) 64 Propeller Change (PRC) 99 Age Exploration Bulletin (AEB) 65 Propeller Bulletin (PRB) 2.4.2 AIRFRAME (AFC/50, AFB/74). TDs shall be titled “Airframe” when the action required affects non-serialized items that are integral parts of the basic structure, such as ribs, attach fittings, skin, empennage, fuselage or fixed surfaces that cannot be moved from aircraft/UAS Control System to another aircraft/UAS Control System. TDs shall also be titled “Airframe” when the action required affects systems or components that are part of the aircraft/UAS Control System configuration but do not involve on-the-spot removal, modification, and re-installation on the same aircraft/UAS Control System. An AFC example would be the replacement of the existing AN/ARC-123 Radio with the AN/ARC-125 Radio in which the existing component/system is removed and replaced by the new component/system. Subsequently, if the removed item is being modified then a separate component level TD Avionics Change, Accessory Change (AVC, AYC, etc.) would be required to document the modification of that item. Such systems include, but are not limited to, the airframe portions of fuel, oil, pressurization, fire extinguishing, air conditioning, anti-icing, anti-g, oxygen systems, and some aircraft wiring. Special care shall be taken with TDs involving routine removable/replaceable airframe components. In many cases, such TDs should be assigned Accessory/Avionics (AY/AV) rather than Airframe (AF) titles and codes. This may be driven by OOMA requirements based on Work Unit Code (WUC) assignment also. The TD type decision shall not be made without considering the impact on proper AV-3M documentation, Auto Logset requirements, and NALCOMIS OOMA functionality. The NALCOMIS OOMA Baseline Manager must be consulted to ensure these impact issues are addressed. Compliance level will also play an important role in this decision. (For example, you will not comply with an (AF) at an “I” level facility and document compliance against an aircraft bureau number (BUNO)). Airframe TDs shall be subdivided by, and numbered sequentially within, specific type/model equipment (e.g., “F-18 Airframe Change (AFC),” “P-8 Airframe Bulletin (AFB)”). 2-19 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 NOTE When a Work Unit Code (WUC) series is identified for a TD type it does not mean every TD of that type must use the same WUC. For example, Dynamic Component changes use 15 series it does not mean all Dynamic Component changes will have 15 as the WUC. It could be 15300 or 15215. 2.4.3 DYNAMIC COMPONENT (DCC/51, DCB/52). TDs shall be titled “Dynamic Component” when the action required affects any component in the helicopter or VSTOL dynamic system(e.g., transmissions, clutches, brakes, rotor actuating mechanisms, rotor groups main and tail, rotor hubs main and tail, and drive shafts). Dynamic Component TDs shall be subdivided by, and numbered sequentially within, specific type/model equipment (e.g., “H-1 Dynamic Component Change (DCC),” "H-60 Dynamic Component Bulletin (DCB)”). Dynamic Component TDs apply to items that are identified in WUC series 15 and 26 (or UNS equivalent) only. 2.4.4 POWER PLANT (PPC/02, PPB/01). TDs shall be titled “Power Plant” when the action required affects an integral part of an aircraft engine/engine module. All TDs for modular engines shall be issued against the module serial number (S/N) identified in DECK-ETR reporting. TDs modifying routine removable/replacement engine or engine module (internal or external) components shall be assigned accessory (AYC) rather than power plant (PPC) titles and codes. Power Plant TDs shall be subdivided by, and numbered sequentially within, specific type/model equipment (e.g., “F-405 Power Plant Change (PPC),” “T-700 Power Plant Bulletin (PPB)”). 2.4.5 AVIONICS (AVC/54, AVB/55). TDs shall be titled “Avionics” when the action required affects the following. These items are identified in the following WUC series: 42 - Electrical Power/Distribution Systems 43 - Fiber Optic Equipment 44 - Electrical Lighting Systems 50 - Cockpit Management Systems 51 - Instrumentation/Indicating Systems 52 - Autopilot Systems 54 - Telemetry Systems 55 - Vehicle Management System 56 - Flight Reference Systems 57 - Integrated Guidance and Flight Control Systems 58 - In-Flight Test/Malfunction Analysis and Recording Equipment 59 - Target Scoring and Augmentation Systems 60 - General Use Communications Equipment 61 - HF Communications Systems 62 - VHF Communications Systems 63 - UHF Communications Systems 64 - Interphone Systems 65 - Identification Friend or Foe (IFF) Systems 2-20 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 67 - Communication/Navigation/(IFF) (CNI) 69 - Miscellaneous Communications Systems 70 - Miscellaneous Navigation Systems 71 - Radio Navigation Systems 72 - Radar Navigation Systems 73 - Bombing Navigation Systems 74 - Weapons Control Systems 76 - Countermeasures Systems 77 - Photographic/Video-Graphic/Reconnaissance/Surveillance Systems/Equipment 80 - UAS Control Systems (Electrical/Electronic only) 95 - Integrated Processor Equipment 99 - Miscellaneous/General Training/Personal Computing Equipment 2.4.5.1 Airborne Electronic Equipment includes: communications (excluding personal survival radios), radar, navigation, recognition/Identification Friend-or-Foe (IFF), electronic fire control/weapon release, infrared, electro-optic, laser detection/designation, teletype, data transmission, data recording, NBC detection, magnetic detection, Electronic Warfare and Electronic Countermeasures (EW/ECM), telemetry, intercommunications, embedded computer, Loran, Omega, compass, radio/radar altimeter, marker beacons (excluding personal survival beacons), ground proximity warning, collision warning, altitude alert, flight data recording, inertial platform, gyro reference, flight director, automatic pilot, automatic stabilization, control panels, headsets, microphones, switches, sonar, sonobuoys, data processors, cameras, and the Light Airborne Multi-Purpose System (LAMPS). 2.4.5.2 Airborne electrical/electronic components include: aircraft power distribution equipment and associated wiring harnesses, meters, electrical parts of generators and inverters, reverse-current relays, voltage regulators, over-voltage relays, warning lights, test switches, junction boxes, batteries, battery vent systems, internal and external lights, and the electrical/electronic portions of the airframe and engine accessories. 2.4.5.3 Airborne instruments include engine instruments, flight instruments, weapon system and navigational displays, sensor displays, Pitot-static system, heads-up displays, integrated displays, instrument panels, angle of attack systems, yaw systems and associated equipment. 2.4.5.4 Air traffic control and landing systems (WUC series 24) not included in paragraph 3.4.14 (TARGET CONTROL SYSTEM (TCC/77, TCB/78)), and other avionics devices not installed in aircraft will fall under this category. Decisions in making the choice of (AF) vice (AV) should not be made without considering the impact on proper documentation and tracking using NALCOMIS OOMA. 2-21 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 NOTE Total System replacement must be performed using an AFC, not an AVC. AVCs are used for modifications of existing systems or Weapon Replacement Assembly (WRA). An example of an AFC would be the replacement of the existing AN/ARC-123 Radio with the AN/ARC-125 Radio in which the existing component/system is removed and replaced by the new component/system. If the removed item is being modified, then a separate component level TD (AVC, AYC, etc.) would be required to document the modification of that item. 2.4.6 AVIATION ARMAMENT (AAC/56, AAB/57). TDs shall be assigned this TD category when the action required affects weapons and armament related end items and/or their removable components. These items are identified in WUC Series 75000, 84000, and 92000, as well as applicable explosive devices found in WUC series 97000. 2.4.7 ACCESSORY (AYC/61, AYB/58). TDs shall be titled “Accessory” when the action required affects a removable repairable component, unit, subsystem, or system that is considered an accessory to a major system such as the airframe, engine, or engine module. Such items include but are not limited to serialized panels or flight surfaces, engine/engine module mounted (internal or external) accessories, generators, inverters, pumps, compressors, actuators, constant speed drive mechanisms, auxiliary power units, emergency generators and pumps, aircraft deceleration parachutes, accumulators, aircraft installed arresting gear and launch bars, and liquid oxygen converters. In many cases, TDs should be assigned AYC/AVC rather than AFC/PPC titles and codes. This may be driven by OOMA requirements based on WUC assignment also. The choice of AFC/PPC vice AYC/AVC shall not be made without considering the impact on proper documentation and tracking using OOMA, and consulting with the NACOLMIS OOMA BLM. These items are identified in the following WUC series: 11 - Airframes 12 - Furnishings/Compartments 13 - Alighting/Launching Systems 14 - Directional Flight 16 - Unmanned Air Vehicle (non-BUNO, part of UAS system of systems) 21 - Reciprocating/Radial Engine (subcomponents only) 22 - Turboshaft/Turboprop Engine (subcomponents only) 23 - Turbojet Engine (subcomponents only) 24 - Auxiliary Power Systems 25 - Jet/Rocket Assist Propulsion Systems 27 - Turbofan Engines (subcomponents only) 29 - Power Plant Installation 36 - Ducted Fans 41 - Environmental Control/Pneumatic Systems 2-22 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 45 - Hydraulic Systems 46 - Fuel Systems 48 - Ice/Rain Removal/Protection Systems 49 - Miscellaneous Emergency/Utility Systems 80 - UAS Control Systems (non-Electrical/Electronic only) 93 - Deceleration/Drag Chute Equipment 2.4.7.1 Weapon system designation or component nomenclature shall be included in the TD subject immediately following the TD code (e.g., Accessory Change No. 123, TD CODE 61, Air Conditioning Compressor Modification). 2.4.8 SUPPORT EQUIPMENT (SEC/62, SEB/63). TDs shall be titled “Support Equipment” when the action required affects equipment, other than fixed base facilities, used to support operation and maintenance of aircraft and associated airborne systems. “Support Equipment” is defined as the equipment required to make an aircraft system, support system, subsystem, or end item of equipment (support equipment for SE) operational in its intended environment. This includes all equipment required to install, launch, arrest (except Navy shipboard and shore based launching and arresting equipment), guide, control, direct, inspect, test (including ATE hardware and software), adjust, calibrate, appraise, gauge, measure, assemble, disassemble, handle, transport, safeguard, store, actuate, service, repair, overhaul, maintain or operate the system, subsystem, end item, or component. This includes, but is not limited to, the following: 2.4.8.1 Avionics support equipment includes: electronic test sets, test benches and associated harnesses, voltage/current/power/waveform measuring equipment, electro-mechanical devices such as rate tables, vacuum pressure chambers, electronic blade trackers, propeller balancers, missile test sets, engine test sets, weapon system test sets, test program sets, special purpose electronic test equipment, alignment checkers, circuit testers, continuity testers, etc. 2.4.8.2 Gasoline, electric, and diesel-powered servicing equipment includes: air compressors, hydraulic test stands, mobile air conditioners, mobile electric power plants and trailers, aircraft/equipment tow tractors, vans, weapon handlers, mobile target vehicles, and loaders. 2.4.8.3 Gas turbine powered servicing equipment such as the GTC-85, the NCPP-105, and similar equipment. 2.4.8.4 Trailers, dollies and carts: equipment such as engine removal and transportation trailers, bomb trucks, cryogenic servicing trailers, spotting dollies, crash dollies, wheel removal dollies and cages, preservation carts, load banks, weighing scales, water-alcohol trailers, weapons skids, shipment stands, and engine test stands. 2-23 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.4.8.5 Mechanical support equipment includes: equipment such as jacks, work stands, hoists, tow bars, slings, adapters, ladders, fixtures, wheel chocks, portable tools, tie downs, analyzers, line testers (other than avionics), and bomb hoists. 2.4.8.6 Automatic Test Equipment (ATE) includes: all types of land, and ship-based, automatic, and semi-automatic, test equipment used in the maintenance of airborne systems, support equipment, and components thereof. This includes ATE operating systems and test program sets. It also includes changes to software when that change is required by virtue of a hardware change. See “Support Software,” paragraph 2.4.19, for support equipment “software only” changes. 2.4.9 PROPELLER (PRC/64, PRB/65). TDs shall be titled “Propeller” when the required action affects items that are identified in WUC Series 32. This includes a propeller assembly, spinner, spinner after-body, oil control governor, synchronizer, or other integral component of a propeller system. 2.4.10 AIRCREW SYSTEM (ACC/66, ACB/67). TDs shall be titled “Aircrew System” when the required action affects the following: NOTE All Aircrew Systems Changes/Bulletins must be routed and concurred with by PMA 202 CM prior to issuance. 2.4.10.1 Aviation life support systems include: inflatable survival equipment, survival kits and associated items, personal survival radios and beacons, oxygen equipment, pressure suits, helmets, integrated restraint and containment systems, parachute hardware, parachute packs and containers, protective equipment, and other items worn or carried by flight crew personnel. 2.4.10.2 Aviation escape systems include: ejection seats and rocket extraction systems including inertia reels (powered and unpowered), shoulder harnesses, lap belts, ballistic and rocket catapults, rocket motors, drogue guns, ballistic transmission lines, firing units and related Cartridge Actuating Devices (CADs), ballistic canopy removal systems (including fracturing devices and related components), detonating cords and lines, removers, thrusters and related CADs, and seat mounted stabilizing and deceleration parachutes. 2.4.10.3 Other related equipment/systems include: in-flight feeding and water systems, first aid kits, and helicopter rescue equipment. 2.4.10.4 Equipment shall be clearly identified as aircraft mounted or personal equipment in the application section of each TD. 2-24 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.4.10.5 These items are identified in WUC Series 17, 47, 66, 91 and 96 as well as applicable explosive devices found in WUC series 97. 2.4.11 PHOTOGRAPHIC (PHC/68, PHB/69). TDs shall be titled “Photographic” when the action required affects airborne photographic components including: cameras (except scope and gun cameras), view finders, associated controls, solenoids, indicator lights, switches, control boxes, intervalometers (except weapon intervalometers), vacuum pumps, heaters and window washers (that are part of photo equipment only). These items are identified in WUC Series 77. 2.4.12 METEOROLOGICAL EQUIPMENT (MEC/73, MEB/79). TDs shall be titled “Meteorological Equipment” when the action required affects units or components that sense or measure meteorological parameters, and compute, analyze, or display the resulting data in usable form. Such equipment provides for the acquisition and use of wind velocity, temperature, relative humidity, barometric pressure, visibility, cloud cover, and related meteorological data from the surface to the upper limits of the atmosphere. These items are identified in WUC Series 94. 2.4.13 AIRBORNE WEAPON (AWC/75, AWB/76). TDs shall be titled “Airborne Weapon” when the action required affects the structural, hydraulic, electronic, electrical, optical, or explosive components of air delivered weapons including missiles, free fall weapons/munitions, mine clearance/countermeasure systems, sonobuoys, decoys, and ammunition. These items are identified in WUC Series 75, 83, and 84. 2.4.14 TARGET CONTROL SYSTEM (TCC/77, TCB/78). TDs shall be titled “Target Control System” when the action required affects airborne target or drone control system components including telemetry, tracking beacons, miscellaneous distance measuring equipment, command control equipment and in-flight recovery systems. These items are identified in WUC Series 53. NOTE UAS Control Systems assigned an A-series TEC will use AF/AV/AY TD codes. 2.4.15 AIRCRAFT LAUNCH AND RECOVERY EQUIPMENT (ALRE), SHIP- INSTALLED/EXPEDITIONARY AIRFIELD (LRC/83, LRB/84). TDs shall be titled “Aircraft Launch and Recovery Equipment (ALRE), Ship-Installed/Expeditionary Airfield,” when the action required affects the following expeditionary airfield or ship- installed systems: catapults, arresting gear, barricades, deck lighting, airfield lighting, optical landing systems, jet blast deflectors, airfield matting, earth anchors, earth anchor installation equipment, launch holdback/release systems, and related systems and components. LRCs and LRBs are numbered by NATEC after CCB approval. These items are identified in WUC Series 24000. 2.4.16 QUICK ENGINE CHANGE KIT (QEC/03, QEB/04). TDs shall be titled “Quick Engine Change Kit” when the action required affects a component of a Quick Engine Change Kit as defined in the applicable aircraft Illustrated Parts Breakdown (IPB) technical 2-25 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 manual. Quick Engine Change Kit TDs shall be subdivided by, and sequentially numbered within, specific type/model equipment (e.g., C-130 Quick Engine Change Kit Change (QEC), or P-3 Quick Engine Change Kit Bulletin (QEB)). These items are identified in WUC Series 29000. 2.4.17 NAVAL AIR MAINTENANCE TRAINER (NTC/91, NTB/92). TDs shall be titled “Naval Air Maintenance Trainer” when the action required affects Naval Air Maintenance Trainers (NAMT) in the inventory (custody) of Center for Naval Aviation Technical Training (CNATT) and the change is NAMT only. NAMT changes required, as a result of weapon system changes, should be implemented by the weapon system change TD. 2.4.18 AIRBORNE SOFTWARE (ASC/93, ASB/94). TDs shall be titled “Airborne Software” when the action required affects programmable elements of digital systems and associated documentation applicable to systems that are unique to a single type/model aircraft platform or weapon systems. This includes computer software for weapon systems, electronic warfare systems, surveillance and warning systems, airborne control systems, navigation systems, data link, and other tactical communication systems. The “Airborne Software” title should be used when there is only software action. When the software action is related to, or required by virtue of a hardware change, it should be implemented by the weapon system (hardware) TD rather than by separate Airborne Software TD. Airborne Software TDs shall be subdivided by, and sequentially numbered within, specific type/model equipment (e.g., F/A-18 Airborne Software Change (ASC) or H-1 Airborne Software Bulletin (ASB) or T408 Airborne Software Change (ASC)). BUNOs of aircraft or engine serial numbers affected should be listed in the application section of the TD. Software changes that affect components within an aircraft and are logged on the affected component OOMA Auto Logset. Identification of the component in the Basic Equipment section is mandatory. 2.4.19 SUPPORT SOFTWARE (SSC/95, SSB/96). TDs shall be titled “Support Software” when the action required affects software associated with support equipment systems and is software only. Software actions related to, or required by virtue of, SEC TDs (see paragraph 2.4.8) should be implemented by the SEC TDs. Software changes that affect components within an item of SE are logged on the affected component OOMA Auto Logset. Identification of the component in the Basic Equipment section is mandatory. 2.4.20 COMMODITY SOFTWARE (CSC/40, CSB/41). TDs shall be titled “Commodity Software” when the action required affects programmable elements of digital systems and associated documentation applicable to common systems, including computer software for weapon systems, data link, and other tactical communications systems that have multi-platform application. Software changes affect components within an aircraft and are logged on the affected component OOMA Auto Logset. Identification of the component in the Basic Equipment section is mandatory. The “Commodity Software” title should be applied when the action is software only. Software actions required by virtue of hardware TDs should be implemented by the hardware TD. 2-26 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 In cases where only one of the multiple platforms is involved, this TD type can still be used. However, when and/if other platforms are ready to receive this software, TD Parts shall be issued for each platform via a CCB action (if not already processed). If previously CCB approved, then an amendment must be processed to add the applicable T/M/S to the basic TD. TD number(s) requested at time of CCB approval shall be managed by component manager (owning/parent PMA). This will eliminate the need for an individual platform ASC, issued against the common equipment. If a single platform needs to issue a change to a commodity vice the aircraft, this TD type must be used. The TD will be tracked against the component, not the aircraft and the TMS affected should be listed in the application section of the TD along with the part number and cage code of the component. The commodity manager (Owning/Parent PMA) must manage the configuration of their equipment on these single platform applications. 2.4.21 NAVAL AIR MAINTENANCE TRAINER SUPPORT SOFTWARE (TSC/97, TSB/98). TDs shall be titled “NAMT Support Software” when the action required affects the computer software of NAMT systems and the software action is not related to, or required, because of the hardware action of a NAMT or a weapon system TD. 2.4.22 REUSABLE CONTAINER (RCC/07, RCB/08). TDs shall be titled “Reusable Container” when the action required affects reusable shipping or storage containers for NAVAIR cognizant material. These items are identified in WUC Series 21000 and 85000. 2.4.23 AGE EXPLORATION (AEB/99). Bulletin TDs shall be titled “Age Exploration” when the action is required in execution of an age exploration program. Age exploration programs gather and analyze specific user maintenance data through a sampling process for the purpose of adjusting preventive maintenance tasks and time intervals, which were initially established by Reliability Centered Maintenance (RCM) analysis. Prior to issuance of an AEB, the data to be collected must be validated to provide desired results. It is not appropriate to issue and collect data if a desired result is not achieved. All AEBs must include a start and stop date for data collection. Age Exploration Bulletins shall be subdivided by, and sequentially numbered within, specific type/model equipment (e.g., AV-8 Age Exploration Bulletin (AEB) and T-700 Age Exploration Bulletin (AEB)). 2.4.24 TRAINING EQUIPMENT (TEC/05, TEB/06). TDs shall be titled “Training Equipment” when the action required affects training equipment under the management control of NAVAIR PMA 205. TECs and TEBs are managed by PMA 205 and are authorized by SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH. TECs and TEBs are assigned numbers by the submission of a NAVAIR approved CCB package through ECM tool to NATEC. TEB numbers are assigned using the bulletin number assignment section of NATEC. 2-27 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.4.25 SERVICE LIFE (No TD Code). No TD code is assigned to Service Life Bulletins (SLBs). SLB’s are not TDs like an AFB or AVB. They shall be used to issue immediate or urgent changes to defined life limits of systems or equipment under the cognizance of NAVAIR. They should be structured and issued via plain language message following the guidelines of the latest versions of NAVAIR 13120.1 series for Fixed Wing Aircraft or NAVAIR 13130.1 series for Rotary Wing Aircraft. SLBs shall be subdivided by, sequentially numbered within, specific Type/Model equipment (e.g., F/A 18 Service Life Bulletin (SLB)). It is recommended that PMAs use the IDR within ECM to process SLBs for review within the PMA prior to release. 2.5 TECHNICAL DIRECTIVE DEVELOPMENTAL STAGES. During preparation, validation, verification, approval and publication, TDs pass through several/a few developmental stages. The three most used developmental stages are defined and discussed in the following paragraphs. 2.5.1 DRAFT. The term “Draft” is applied to initial versions of TD documents that pertain to changes that are validated but are not verified (see paragraphs 2.8 and 2.9). Draft TDs shall be submitted to NAVAIR for information, review, and/or comment. Draft TDs shall not be distributed to activities outside NAVAIR without approval of the cognizant APML/LM. 2.5.2 PROPOSED. The term “Proposed” is applied to TDs submitted to NAVAIR for review and approval. The RAMEC process requires verification be accomplished before submitting proposed RAMECs to NAVAIR for review and approval. All TDs to include Interim Changes, as well as Bulletin TDs submitted to NAVAIR for review and approval, are designated “Proposed” until they are approved and issued. Distribution of Proposed TDs shall be strictly controlled by the APML/LM. Distribution of Proposed TDs for verification must include NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH, NALCOMIS OOMA BLM, NAVSUP, ISSC, and affected TYCOMs/Controlling Custodians. TYCOMs/Controlling Custodians will assign and then forward to the designated verifying activity. 2.5.3 APPROVED. All Change TDs are published and are approved when they are signed by the NAVAIR TD approval authority, then posted to the NATEC website by owner of the TD Object. NATEC electronic publication media includes formal publishing requirements. Grounding Bulletins are approved when they are released for compliance. TDs will not be added to the NALCOMIS OOMA baseline until they have been posted to the NATEC website. Exceptions to this policy can be made for time sensitive TDs with National Lead/Process Owner NALCOMIS Baseline Development/Validation/Sustainment and TYCOM concurrence. 2-28 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.6 TECHNICAL DIRECTIVES ISSUED IN PARTS. Implementation of approved engineering changes and inspections issued as a bulletin, occasionally requires preparation and issuance of TDs in parts when: (1) the total directed action will be accomplished incrementally in separate distinct parts, (2) directed actions will be accomplished on different configurations of affected equipment, as approved detailed instructions and/or required change kits are developed and become available, (3) directed action involves separate reportable compliance actions at different maintenance levels, (this would be applicable for a modification to an item at the OEM/Depot and then that item is installed at the (O-) Level and documentation of each action is required for proper configuration status accounting), or (4) when the change is applicable to different T/M/S. When a TD is to be issued in parts, the first, or basic, issuance of the TD will always be Part 1, even though it will not be identified as such in the TD number. Subsequent issuances shall be identified by Arabic numbers as Part 2, Part 3, etc. (e.g., F/A-18 AFC 217 Part 2, F-5 AFB 217 Part 2). All parts shall have the same category and subject. Each part shall be a complete, stand-alone TD with its own issue date. TDs issued in parts require their own amendments and revisions when corrections or changes arise and are needed. There can be revisions to parts of TDs, but not parts to revisions. Parts are only issued against basic TDs. 2.7 TECHNICAL DIRECTIVES PREPARED IN DATA PACKAGE FORMAT. NOTE All Installation Data Packages (IDP) must have an assigned issue date and revision identifier in order to maintain configuration management principles for each document. NOTE When an IDP is used in a TD, (O-) Level involvement will only be allowed for assisting actions. Their man-hours/actions must be documented using the Technical Directive Assist (AT) work order as shown in the Man-Hours and Records Affected sections of appendices for each TD type (See CNAF 4790, paragraph 5.5.5, page 15-31). NOTE IDPs shall not be used in Interim TDs as this negates the need for Urgency driving an Interim TD vice a Routine TD. Also Interim TDs are temporary modifications until formalized by approved ECP/CCB action. If an IDP is to be used, a Waiver of TD process must be routed for approval by CM/DM Group. 2.7.1 DEPOT. Depot level TDs that implement extensive changes may be written in IDP format. This does not apply to (O-) Level or (I-) Level. This format eliminates unnecessary and expensive reproduction of detailed installation instructions for each TD copy published. This also applies to extensive kit contents. Instead, a separate installation data package is prepared, and it is reproduced only as necessary to provide 2-29 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 one copy to each installing activity. Installation Data Packages consist of detailed instructions and parts list that are needed to complete the modification. Drawings only are not considered as an IDP and cannot be used as an IDP. 2.7.2 The requirement for a separate data package is identified in the TD and instructions for obtaining it must be provided. Mixed format TDs are also permitted. For example, a TD implementing a minor change may contain complete instructions for installing the change in the basic equipment and identify a separate data package containing the necessary instructions for changing affected trainers. IDPs are located on NATEC website with the TD. However, they are considered standalone documents and shall not be independently corrected via an amendment. To correct or change an IDP, a TD amendment shall be generated to clarify, correct, add to, delete from, or make minor change to, both the IDP and TD. The amendment shall state corrections to the IDP and all applicable elements in the TD that will change. All IDPs must have an assigned issue date and revision identifier in order to maintain configuration management principles for each document. 2.7.3 Bulletin Supporting Documents (BSD) - This element is used for Grounding Bulletin TDs only. BSDs shall consist of drawings, narrative instructions, and technical data, as required. The narrative instructions shall contain additional instructions/steps to assist in completing the inspection required by the associated bulletin. The TD title and number shall be shown on each page of the supporting data package. BSDs shall be distributed to each activity authorized to install the TD and to NATEC. BSDs are standalone documents and shall not be independently corrected via a Bulletin amendment. To correct or change a BSD, a bulletin amendment shall be generated to clarify, correct, add to, delete from, or make minor changes to, both the BSD and the Bulletin. The amendment shall state correction to the BSD and all applicable elements in the bulletin that will change. NOTE ALL IDPs and BSDs must be posted to the NATEC website along with their associated TDs (at the same time the TD is loaded to NATEC), unless waived by NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH. If proprietary data is an issue, then a Restrictive/Sensitive cover sheet can be uploaded instead of the actual document. 2.8 TECHNICAL DIRECTIVE VALIDATION. Validation is an engineering process by which the originator accomplishes all tasks required by a proposed change to ensure the modified items function as intended. Validation is usually conducted at an organic depot or contractor facility but may be conducted at an operational site as directed by the APML/LM. Because the validation is an installation using an ECP or a preliminary TD, it does not constitute an incorporation of an approved TD. A draft TD is usually the product of a completed validation. This occurs before the formal TD development and must be verified after proposed TD issuance to determine if all TD requirements have been met. 2-30 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 Prototype installs also fall into this category and must be verified against the TD once issued, before becoming documented as an actual compliance. A validation must be performed for all TDs unless a waiver is approved. Bulletins must follow this validation process also even though there is no modification. There is no ECP in the case of a bulletin. Therefore, the validation is to determine if the bulletin, as written, accomplishes the intent of the bulletin, to determine if a condition exists, and any repair identified returns aircraft or equipment to a fully operational status. NOTE PROTOTYPE. A prototype is an early sample, model, or release of a product built to test a concept or process. It is a term used in a variety of contexts, including semantics, design, electronics, and software programming. A prototype is generally used to evaluate a new design to enhance precision by system analysts and users. 2.8.1 TDs applicable to more than one aircraft/equipment Type Model Series (T/M/S) shall be validated on each affected aircraft/equipment T/M/S, unless waived by NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH. Validation forms are optional, however, are recommended for historical purposes. 2.9 TECHNICAL DIRECTIVE VERIFICATION. Verification is the process for determining the accuracy and adequacy of a proposed TD and reporting results to the preparing activity. Verification is the actual installation of change kits, incorporation of changes, or performance of inspections by personnel of the prescribed skill, and performed at the compliance level approved by the CCB action. This uses a proposed TD, support equipment, and special tools available at, and in, an environment comparable to the average service facilities of the lowest authorized compliance maintenance level. Verification also includes the administrative review of the proposed TD by the appropriate personnel at NAVAIR to include NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS RANCH, cognizant ISSC, and TYCOM. Successful verifications are authorized installations and may remain installed if approved by TYCOM. They must be properly documented after TD has been approved and published. Verifications are authorized installations and may remain installed if approved by TYCOM. They must be limited to one verification per T/M/S unless problems are incurred that require a second re-verification. After a successful verification is completed, if any further verifications are required, they must be approved via a waiver of the TD process by NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH using the 5215/14 Waiver form. 2.9.1 For a bulletin, verification is to determine if the bulletin, as written, can be accomplished at the maintenance level chosen for compliance. Complexity of the inspection must be considered when choosing the compliance maintenance level. When determining complexity, the number of inspection points must be evaluated, as well as the actual steps to be performed to complete the bulletin. 2-31 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 2.9.2 All TDs shall be verified prior to issuance, unless a waiver of verification or a waiver for a concurrent validation/verification is approved. TD verification shall be assigned a sufficiently high priority to enable completion of the required action within the prescribed time limit. 2.9.3 Verifications shall include the procedures associated with gaining access to the areas/equipment involved, as well as performing tests required to ensure satisfactory operation after completion. 2.9.4 Verification of power plant and component changes shall include interface, clearance, and fit checks, as necessary, to ensure compatibility with installation and with support systems (e.g., Verification of power plant changes may require engine buildup and installation in an aircraft and/or compatibility checks with support equipment, as well as reusable shipping containers when external dimensions are changed). In addition, verification of power plant TDs on multi-engine platforms may require verification on all installed engines due to differing access/compatibility problems among installed engines. 2.9.5 Verification of software TDs will normally be performed by designated Software Support Activities (SSA). Software verification at a Navy user level installation activity, if required, will normally be limited to verification of proper installation and operation of the software. If the same standard loading process is used for every software change (i.e. MLVS loader or similar device), then no incorporation level verification is required and the SSA verification is all that is needed. If the standard method is not used, then an incorporation level verification must be performed to ensure that level can in fact comply with TD as written. Verification of a software TD, via SSAs, for an item of calibratable Support Equipment, shall ensure coordination with NSWC Corona and NAVAIR METCAL. 2.9.6 TDs applicable to more than one aircraft/equipment Type Model Series (T/M/S) shall be verified on each affected aircraft/equipment T/M/S, to include verification of multiple kits on each T/M/S, unless waived by NAVAIR SUSTAINMENT GROUP, TECHNICAL DIRECTIVES/BULLETINS BRANCH. If configuration varies among blocks of aircraft, it should be considered to perform separate verifications on each block. TDs requiring compliance action at more than one maintenance level shall be verified at all maintenance levels involved. 2.9.7 Organic (I-) Level and (D-) Level verification plans shall be coordinated with SUSTAINMENT GROUP/FRC. Verifications performed by (O-) Level maintenance activities shall be coordinated through applicable TYCOMs/Controlling Custodians. 2.9.8 Verifying activities shall report results to their cognizant TYCOM/Controlling Custodians. The TYCOM will then forward results along with their concurrence to the APML/LM. If a verifying activity determines a TD to be unsatisfactory or deficient in any respect, that activity shall report difficulties and request instructions from the TYCOM/Controlling 2-32 CUI  CUI NAVAIR SOP 00-25-300 Date: 05 JULY 2023 Custodian via official correspondence. These results will then be forwarded to the APML/LM for further disposition. 2.9.9 Verifying activities shall evaluate costs to the installing activity for materials required incident to TD compliance. If these costs are projected to exceed $1,000 per squadron, the verifying activity shall identify the excess costs in the verification report to the cognizant TYCOM/Controlling Custodian. The cognizant TYCOM/Controlling Custodian will then forward the verification report to the APML/LM, who will determine what further action is required. 2.9.10 When processing verifications for bulletins, TYCOMs must consider the complexity of the inspection to be performed. When determining the complexity, the number of inspection points and the actual steps to be performed must be evaluated to complete the bulletin. If the total number of man-hours to complete the bulletin exceeds the out- of-service time of eight hours, and the actual completion man hours of ten, then concurrence level must be elevated above the class desk to the CNAF GS-15/O-6 or above level. 2.9.11 When a proposed amendment invalidates the verification performed on the basic TD, a new verification must be performed. 2.9.12 When a proposed revision invalidates the verification performed on the original TD or previously issued revision or corresponding amendment, the proposed revision must have a new verification performed. 2.9.13 A TD verification form must be used and routed with the TD pending approval when a TD verification is performed. The completed form should be routed to the PMA by the cognizant TYCOM/ACC with the TYCOM’s signature attached. 2.9.14 Interim Flight clearances must be in place for any aircraft that is modified during the verificatio