Aircraft Missionized Equipment Installation and Removal

Installation and Removal of Missionized Equipment

• Installation and removal of missionized equipment on an aircraft does not require a Technical Directive (TD).
• However, 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.

Data Files

• "Data files" refers to static, uncompiled data that does not alter the software footprint.
• 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

Software

• "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.

Technical Directives (TDs)

• TDs shall be titled based on the type of equipment or system affected, such as:
  • Airborne Weapon (AWC/75, AWB/76)
  • Meteorological Equipment (MEC/73, MEB/79)
  • Photographic (PHC/68, PHB/69)
  • Target Control System (TCC/77, TCB/78)

TD Categories

• Immediate Action: assigned when factors of combat necessity present hazardous conditions that could result in personal injury or damage to valuable property.
• Urgent Action: assigned when factors of combat necessity present hazardous conditions that could result in personal injury or damage to valuable property, but are less serious than those for which the Immediate Action category would be assigned.
• Routine Action: assigned whenever the urgency of the situation does not warrant assignment of the Immediate or Urgent Action categories.

Verification of TDs

• Verification of software TDs will normally be performed by designated Software Support Activities (SSA).
• Verification of a software TD, via SSAs, for an item of calibratable Support Equipment, shall ensure coordination with NSWC Corona and NAVAIR METCAL.
• 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.

Technical Directives (TDs)

• TDs must be routed for review using the Enterprise Change Management (ECM) tool and the TD Object workflow.
• The Assistant Program Manager for Logistics (APML)/Configuration Manager (CM) is responsible for establishing and maintaining distribution/approvals for each TD.

TD Review and Approval

• After TD review is complete, routing TD for approval signature shall be done in the same ECM tool as the review.
• Other reference documents, such as TD Verification Certification Form (5215/12), TD Logistics Support Checklist (5215/9), and supporting documentation, must be loaded in the routing folder.

TD Issuance

• All TDs shall be issued by the Commander, Naval Air Systems Command (NAVAIR).
• TDs will be issued following the format and business rules dictated in the applicable appendices of this SOP.

Technical Directive Types

• Interim Change TD: issued when a formal ECP is not available, and a draft ITD is submitted along with a completed Change Request Directive package.
• Formal Change TD: issued to supersede the Interim Change TD after a formal ECP is obtained and reviewed.

Urgent Action Category

• Assigned when factors of combat necessity present hazardous conditions that could result in personal injury or damage to valuable property.
• Requires compliance within specified time limits, typically within 10 flight hours to 36 months.

Routine Action Category

• Assigned when the urgency of the situation does not warrant assignment of the Immediate or Urgent Action categories.
• Used for TDs applicable to a foreign country under an FMS program.

Technical Directive Code Numbers

• Table 2-1 lists the TD code numbers and titles, including Power Plant Bulletin, Aircrew System Change, and more.

Technical Directive Developmental Stages

• TDs pass through several developmental stages, including preparation, validation, verification, approval, and publication.