Downloaded from http://www.everyspec.

com

INCH-POUND

MIL-DTL-5096H(USAF)
12 August 2019

SUPERSEDING
MIL-DTL-5096G(USAF)
w/AMENDMENT 1
16 July 2018

DETAIL SPECIFICATION
MANUALS, TECHNICAL - INSPECTION AND
MAINTENANCE REQUIREMENTS; INSPECTION
WORK CARDS; AND CHECKLISTS; PREPARATION
OF

Comments, suggestions, or questions on this document should be addressed to

AFLCMC/HIAM Technical Data Section, 4170 Hebble Creek Road, Bldg. 280, Door 15,
Area A, Wright-Patterson AFB, OH 45433-5653 or emailed to [email protected].
Since contact information can change, you may want to verify the currency of this address
information using the ASSIST Online database at https://assist.dla.mil.

AMSC 10067 AREA TMSS

 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

This specification is approved for use by the Department of the Air Force and is available for use
by all Departments and Agencies of the Department of Defense.

1 SCOPE
1.1 Scope. This detail specification covers the requirements for the preparation of inspection and maintenance
requirements (-6) manuals and inspection (-6WC) work cards. This detail specification also covers the
general requirements for all checklists and specific requirements for maintenance checklists (as applicable to
aircraft, Communication Electronic (CE) equipment, air/ground launched missiles, drones, support/systems
equipment, rockets and electronic systems). Some systems may require an inspection requirements manual
only or work cards only. For other systems a combination of both inspection manual and work cards may
be more suitable. This specification provides for Standard Generalized Markup Language (SGML) Document
Type Definitions (DTD) usage required for preparation of manuals, workcards and checklists listed in this
specification (see appendices A through F, (appendices B, C, and E have been deleted)).
1.2 Illustrations in the specification. The illustrations appearing in this specification are used only as
examples. If there is any conflict between the text and illustrations of this document, the text applies.

2 APPLICABLE DOCUMENTS
2.1 General. The documents listed in this section are specified in sections 3 and 4 of this specification.
This section does not include documents cited in other sections of this specification or recommended for
additional information or as examples. While every effort has been made to ensure the completeness of this
list, document users are cautioned that they must meet all specified requirements of documents cited in
sections 3 and 4 of this specification, whether or not they are listed.
2.2 Government documents.
2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form
a part of this document to the extent specified herein. Unless otherwise specified, the issues of these
documents are those cited in the solicitation or contract
DEPARTMENT OF DEFENSE SPECIFICATIONS
MIL-DTL-38769 - Manuals, Technical - Work Unit Code
MIL-DTL-83495 - Manuals, Technical - On Equipment Maintenance Manual Set
DEPARTMENT OF DEFENSE STANDARDS
MIL-STD-1808 - System Subsystem Sub-Subsystem Numbering
MIL-STD-1798 - Mechanical Equipment and Subsystems Integrity Program
MIL-STD-38784 - Manuals, Technical: General Style and Format Requirements
(Copies of these documents are available online at https://quicksearch.dla.mil.)
2.2.2 Other Government documents, drawings, and publications. The following other Government documents,
drawings, and publications form a part of this document to the extent specified herein. Unless otherwise
specified, the issues of these documents are those cited in the solicitation or contract.

AIR FORCE TECHNICAL MANUALS

TO 00-5-3 - Air Force Technical Order Life Cycle Management
TO 42B1-1-15 - Cross Reference-NATO/ASIC Interchangeability of Aviation Fuels,
Lubricants, and Allied Products
(Copies of these documents required by users with “.mil” government web address access are available
online at https://www.my.af.mil/etims/ETIMS/index.jsp. Refer to helpdesk information if obtaining copies
without a TO subscription account. Copies of documents required by contractors in connection with specific
procurement functions should be obtained from the acquiring activity or as directed by the contracting officer.)
2.3 Order of precedence. Unless otherwise noted herein or in the contract, in the event of a conflict
between the text of this document and the references cited herein, the text of this document takes

2
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a
specific exemption has been obtained.

3 REQUIREMENTS
3.1 General. As specified by the acquiring activity (see 6.2b), each contract shall state which documents
are required for aircraft, air/ground launched missiles, rockets, drones, CE, and support systems. An aircraft
or ground system may require an inspection requirements manual only, or work cards only. Others may use
the work cards, inspection manual, and checklist. The requirements of MIL-STD-38784 are applicable,
except as otherwise specified herein.
3.1.1 General criteria. Unless otherwise specified herein, the general preparation and format for all manuals
covered by this detail specification shall be in accordance with MIL-STD-38784 (see 6.6.12 for explanation
of print versus electronic presentation requirements specified herein). The following exceptions apply:
3.1.2 Equipment nomenclatures. When related Organizational Maintenance Manuals (OMMs) are prepared to
the requirements of MIL-DTL-83495, equipment nomenclatures in inspection manuals shall be followed by
the applicable higher level designation in parenthesis. System titles in the inspection manual (-6) shall
be followed by the applicable Work Unit Code (WUC) system number in parenthesis followed by the
applicable System/Subsystem/Sub-Subsystem Number (SSSN). SSSN definition and assignment instructions are
contained in MIL-STD-1808.
3.1.3 Security classification. When possible, the contents of the documents shall be so arranged and
worded that they shall be unclassified. However, if classified information is required, it shall be prepared
in accordance with MIL-STD-38784.
3.1.4 Effectivity markings. Effectivity markings, such as flag note symbols, base codes, and other
indicators, shall be used to denote wing applicability, configurational differences, alternate actions, and other
equipment differences. Markings shall be explained in the introduction.
3.2 Inspection and maintenance requirements (-6) manual.
3.2.1 Requirements (-6) manual. There shall be one manual prepared for the aircraft, air/ground launched
missiles, rocket, drone, CE and support systems entitled: “Technical Manual, Scheduled Inspection and
Maintenance Requirements.” The need for additional manual(s) shall be as specified by the acquiring
activity (see 6.2c).
3.2.1.1 Basis. Initial requirements as determined by the acquiring activity (see 6.2d), shall be based on
technical and maintenance analysis, using the following objectives of an efficient maintenance program:
a. To prevent deterioration of the inherent design levels of reliability and operating safety.
b. To accomplish this protection at the minimum practical costs.
3.2.1.1.1 Requirements to be included. The manual shall include all scheduled and special inspections,
replacement and check flight requirements and base level repair restrictions for the weapon system and
equipment installed therein. Also included shall be requirements pertaining to the marriage of an aircraft
with weapons, missiles and other stores, when applicable. The manual shall establish a complete preventive
maintenance program for the weapon system to which it pertains. The inspection requirements shall reflect
the requirements contained in the inspection work cards. No requirement shall be omitted.
3.2.1.1.2 Frequency requirements. The determination of each individual requirement and how frequently
these requirements should be scheduled, shall be accomplished from the source data collected from the
Mechanical Equipment And Subsystems Integrity Program (MECSIP) process spelled out in MIL-STD-1798,
(see 2.2.1). The acquiring activity (see 6.2e), shall specify the maximum safe interval between inspections so
that the weapon system is not over inspected.
3.2.1.2 Excluded information. The inspection requirements shall not explain procedures for removal or
installation of equipment nor contain instructions for repair or adjustment. Reference to this type of
information shall be in accordance with MIL-STD-38784.
Electronic Presentation: References shall be linked to the data to which it applies.

3
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

3.2.1.3 Functional nature requirements. The design of a weapon or support system may include various
functional systems (i.e. made up of components from several systems). In such cases, the inspections may
be broken out by functional systems, as necessary, under suitable headings.
3.2.1.4 Additional considerations. Preparation of the inspection requirements may involve more than just
inserting data applicable to systems or end items. The impact of a component failure upon the remainder of a
functional system, the impact of a part failure upon the remainder of a functional system, and the impact of
a part failure in a component shall also be considered. If visual inspection or other nondestructive inspection
can be utilized to detect wear or other evidence of impending failure, those factors shall be weighed in
determining scheduled maintenance. When preparing structural inspections, consideration shall be given in
determining what stresses are applied to the structure and what structural components are likely to be affected.
3.2.1.5 Syntax. The syntax for stating inspection requirements shall be “Noun” followed by the adverse
condition to be sought. Example: “Exhaust Nozzle for cracks and corrosion.”
3.2.1.6 Inspection intervals. To simplify recording and scheduling of inspections, all inspection intervals
shall be divisible by the lowest interval, rounded to the conservative side. This information cannot be any
more specific. Since this specification covers all inspection manuals, and covers all intervals from hours
to years, the details need to be specified by the acquiring activity.
3.2.1.7 Components coverage. Unless otherwise specified by the acquiring activity, all installed subsystems,
components, etc., shall be covered. The acquiring activity will provide a listing of any items, components
or subsystems exempt from coverage (see 6.2f).
3.2.2 Arrangement and contents (-6) manual. Appendix A provides the directions for obtaining digital
tools for the electronic preparation of the -6 manual. The manual shall be arranged and divided into
chapters as follows:
Front Matter
Chapter 1 Scheduled Inspection and Maintenance Requirements
Chapter 2 Special Inspections and Maintenance Requirements (includes Depot Level
Requirements, Acceptance and Functional Check Flight)
Chapter 3 Replacement Schedule
Chapter 4 Repair Restrictions
Print Presentation: The manual shall be prepared in 8 ½ by 11 inch format.
Electronic Presentation: Data for chapters 1 through 4 shall be formatted as a scrolling table viewable
by section.
3.2.2.1 Front matter (-6) manual. Front matter shall be prepared in accordance with the requirements
of MIL-STD-38784 except that the introduction shall contain the statements shown in figure 1, with
appropriate changes for the type of equipment being addressed. The need for additional information
applicable to a specific weapon system or any modifications to the introduction shall be as specified
by the acquiring activity (see 6.2g).
3.2.2.2 Chapter 1 - Scheduled Inspection and Maintenance Requirements. This chapter shall contain all
inspections that must be accomplished at specified intervals. To identify the various intervals, this chapter
shall be divided by sections. Unless otherwise specified by the acquiring activity (see 6.2h), all sections
listed in paragraphs 3.2.2.2.1 through 3.2.2.2.6 shall be used. When not required, they shall be included
and marked “Not Applicable.” When specified by the acquiring activity (see 6.2i), additional sections
shall be included and shall begin after the last of the required sections. These additional sections shall
be of the type specified by the acquiring activity. Data shall be formatted in accordance with figure 2
with appropriate wording for the type of inspection and equipment.
3.2.2.2.1 Chapter 1, Section I - Preflight/Preoperation. This inspection shall include:
a. Items that, due to environment, are subject to damage by outside forces, such as ground
equipment, maintenance crews, elements of nature, etc.

4
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

b. Items that, due to design characteristics, normally require service or verification of service
prior to the first flight/operation of the day.
3.2.2.2.2 Chapter 1, Section II - End of Runway. This inspection shall include:
a. Items that are subject to damage during ground operations or are not readily apparent until
after operation begins.
b. Items, such as panels and doors, that must be secure prior to flight/operation.
c. Items, such as down locks, safety pins, and protective covers, that must be removed prior to
flight/operation.
3.2.2.2.3 Chapter 1, Section III - Thruflight. This inspection shall consist of the same type items as
the basic postflight/postoperation (see 3.2.2.2.4).
3.2.2.2.4 Chapter 1, Section IV - Basic Postflight/Postoperation. This inspection shall consist primarily
of the following:
a. Items that due to their operational characteristics are subject to loss of lubricant, fluids, air,
etc., during flight/operation.
b. Items that due to flight/operation are subject to damage such as impact, foreign objects,
etc., during operation.
c. Items of critical nature that are subject to developing defects which are not readily apparent to
the users during operation.
d. Items, such as down locks, safety pins, and protective covers, that must be installed prior
to maintenance.
3.2.2.2.5 Chapter 1, Section V - Hourly Postflight/Postoperation. This inspection shall augment the basic
postflight/postoperation requirements. It shall include requirements that fall in the following categories:
a. Items that due to their installation characteristics are subject to excessive chafing and insecure
mounting.
b. Items that are subject to extreme heat conditions.
c. Items that due to their design characteristics are subject to developing leaks or unusual cracks.
d. Items that require more frequent verification of serviceability or operation than the
periodic/phased/isochronal inspection interval.
e. Items that require more frequent verification of service than the periodic/phased/isochronal
inspection interval.
3.2.2.2.6 Chapter 1, Section VI - Periodic, Phased or Isochronal. The inspection (periodic, phased, or
isochronal) to be used, shall be as specified by the acquiring activity (see 6.2j). These inspections shall
include those requirements to be accomplished at a specified interval or multiples of the specified
interval. They shall consist primarily of requirements that are necessary at more extended intervals than
the hourly postflight/postoperation inspection; in certain instances are more searching in scope than the
hourly postflight/postoperation inspection. Isochronal inspections shall be divided into Home Station Check
Inspection, Minor Inspection and Major Inspection. This section shall primarily include requirements
that fall in the following categories:
a. Items that are subject to developing defects after periods of operation in excess of the hourly
postflight/postoperation inspection interval and may require disassembly to ascertain wear or
deterioration that may cause failure of the unit.
b. Items that due to their function within a system require a periodic examination or servicing less
frequent than the hourly postflight/postoperation interval or in some instances, less frequent
than the basic periodic/phased/isochronal inspection interval to detect impending failure or a
servicing requirement.

5
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

c. Items that require periodic removal for bench check to determine functional reliability, extent of
physical wear, and evidence of incipient failure.
d. Items that require less frequent verification of service than the hourly postflight/postoperation
interval.
3.2.2.3 Chapter 2 - Special Inspection and Maintenance Requirements. Special inspections shall include
those functions to be accomplished at the expiration of a specified number of flying hours, equipment hours
of operation, and lapse of calendar time. The special inspections shall also include those functions to be
accomplished after the occurrence of a specific or unusual condition or incident, and when accepting an
aircraft after extensive modifications. Unless otherwise specified by the acquiring activity (see 6.2k), all
sections listed in paragraphs 3.2.2.3.1 through 3.2.2.3.4 shall be used. When not required, they shall be
included and marked “Not Applicable.” When specified by the acquiring activity (see 6.2l), additional
sections shall be included and shall begin after the last required section. They shall be of the type specified
by the acquiring activity. Data shall be formatted in accordance with figures 3 through 6 with appropriate
wording for the type of inspection and equipment.
3.2.2.3.1 Chapter 2, Section I - Special Inspections after a specific occurrence (see figure 3). These
inspections shall be designed to meet the following criteria:
a. Items that due to their physical characteristics are subject to deterioration after long periods
of service.
b. Items that due to their structural characteristics are subject to fatigue after long periods of service.
c. Items that due to their function within a system are subject to damage from specific events, such
as hard landings, violent maneuvers, hot starts, false starts, etc.
3.2.2.3.2 Chapter 2, Section II - Depot (see figure 4). The depot section shall include inspections and
maintenance to be accomplished on a scheduled calendar time cycle basis. Inspection requirements shall
insure that all accessible areas and components not afforded coverage at other inspection intervals are given
thorough and adequate attention. Work cards to detail these requirements shall be prepared. This chapter
and section also includes Programmed Depot Maintenance (PDM).
3.2.2.3.3 Chapter 2, Section III - Acceptance and Functional Check Flight (FCF) inspection requirements
(see figure 5). This section shall list those conditions which require a functional check flight to verify
maintenance performed on the aircraft or its airworthy condition. Specific conditions for FCFs shall be
determined for each aircraft, based upon technical conditions and operational experience. It may also
be necessary to prescribe FCFs for component changes such as engines or major flight control surfaces
when the possibility of failure or a malfunction of the component is greater during its initial period of
operation. These types of requirements shall be related to experience factors on component failures or
malfunction rates, the number of like components installed in the aircraft, the number of these items that
could be changed simultaneously without creating an unacceptable safety of flight risk, and whether or not
an emergency backup system is provided for use in the event of a failure of the main system. This section
shall include requirements that fall in the following typical conditions:
a. After a periodic or specific numbered phase, i.e., sixth and twelfth inspection has been completed.
If a complete functional check flight inspection has been accomplished within 150 hours of a
sixth or twelfth phased inspection, no functional check flight inspection will be required.
b. When an aircraft is removed from extended storage.
c. After fixed flight surfaces have been replaced or removed for repairs and reinstalled.
d. After replacement or removal and reinstallation of engine main fuel control (single engine aircraft).
e. After movable flight surfaces have been replaced or removed for repairs and reinstalled.
f. After flight control cables, rods or actuators have been rerouted, rerigged, readjusted or
replaced. A single aileron actuator change does not normally constitute a requirement for
a functional check flight.

6
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

g. On fly-by-wire aircraft, an FCF shall be performed at the discretion of the Logistics Group
Commander when work has been performed on the flight control computers.
h. After a major structural modification or repair is accomplished.
i. After extensive maintenance or repair is accomplished of such a scope that a test flight is
determined to be necessary by the Logistics Group Commander.
j. After a propeller or propeller governor has been replaced and/or adjusted and reinstalled
(single engine aircraft).
k. After adjustments or changes have been made to the photo system requiring a flight to insure
operational capability (although this is normally an “In Flight Check,” certain weapon systems
may need an FCF to assure all photo systems are working correctly).
l. After three or more engines, on a four engine aircraft, two or more engines on a three engine
aircraft, or one engine on a two engine or less aircraft are replaced by new or completely
overhauled engines resulting from a single maintenance action.
3.2.2.3.4 Chapter 2, Section IV - Historical Documents (see figure 6). This section shall contain a listing
of specific weapon system components that require preparation of any of the historical documents Air Force
Technical Order Forms prescribed by the 00-20-series technical orders. The listing shall be by WUC,
nomenclature of components and form required.
3.2.2.4 Chapter 3 - Replacement Schedule (see figure 7). As specified by the acquiring activity (see 6.2m),
this chapter shall include those items and components that must be removed and changed for new or
overhauled like items at the expiration of a specified number of flying hours, expiration of a number of
cycles, or an interval of calendar time. It shall include only those items that are readily identifiable for
record purposes and that fall in the following categories:
a. Items whose failure due to location or function within a system could compromise flight safety
beyond reasonable limits and acceptable risk.
b. Items whose failure due to location or function within a system would cause an operational or
support mission to abort.
c. Items whose cost is high and whose failure might cause damage beyond economical repair.
d. Items whose physical characteristics are subject to deterioration from calendar time, flying
hours, cycles, operation, or usage.
e. Life sustaining items such as oxygen regulators, pressurization components, egress, or jettison
system components.
3.2.2.5 Chapter 4 - Repair Restrictions. These restrictions do not apply to normal preventative maintenance
actions such as cleaning, reseating, etc.
NOTE: A part number shall be preceded by the Federal Supply Class (FSC).
3.2.2.5.1 Chapter 4, Section I - Base Level Restrictions (see figure 8). This section shall contain a listing
of items by WUC, noun, FSC and part number for which base level (organizational and intermediate) repair
restrictions are established. A description of repair restrictions shall be provided. Items listed shall be limited
to recoverable type items. Items which are Source, Maintenance and Recoverability (SMR) coded “depot
repair only” shall not be listed. The part number shall consist of the basic part number for the preferred
item and all substitutes. Dash numbers reflecting modifications shall not be listed.
3.2.2.5.1.1 Item selection. Selection of items to be listed in Chapter 4, Section I - Base Level Restrictions
shall be as specified by the acquiring activity (see 6.2n).
3.2.2.5.1.2 Repair limitation. Repair limitations shall be stated in a manner to positively identify the
repair restriction within the limitation statement without any requirement for field activities to relate the
text of the introduction with the statements of the restrictions. As an example, statements such as “No
Repair” and “No Repairs Requiring Disassembly” shall not be used. To permit the intent of the above
statements to stand completely on their own content, the terms “No Repair Authorized” and “Repair

7
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

Requiring Disassembly Not Authorized” shall be used. Repair restrictions shall always be worded in the
form of limitations. Statements reflecting repair authorizations shall not be used as a substitute for repair
restrictions to reduce the amount of coverage required.
3.2.2.5.1.3 Technical manual references. Reference to repair technical manuals is permissible but shall be
kept to a minimum. References shall be in accordance with MIL-STD-38784. Where it is practical the
preference is to extract repair limitations from the applicable repair technical manuals and present them in a
condensed form in Chapter 4, Section I. Where it is impractical to condense repair limitations into a brief
but concise statement of repair restrictions, reference to a technical order is permitted.
Electronic Presentation: References shall be linked to the data to which it applies.
3.2.2.5.2 Chapter 4, Section II - Supplemental Repair Restrictions for contingency operations. This section
supplements Chapter 4, Section I, by listing additional items of equipment by WUC, noun, FSC and part
number for which repair restrictions are established for contingency operations.
3.3 Work cards and checklists, general.
3.3.1 System series designation. Print Presentation: When the work card/checklist covers more than
one system series and it is necessary to identify the series to which each page applies, the system
designator for which the work card/checklist applies shall be placed at the upper binding edge of
each page, i.e., F-16C/F-16D.
Electronic Presentation: The system designator (i.e., F-16C/F-16D) for which the work card/checklist
applies shall be placed in the header (see 3.4.2).
3.3.2 Work card/checklist introduction. The introduction shall begin with the following standard paragraph:
“This (work card/checklist) is a step-by-step guide in abbreviated form for use as a reference to ensure
accomplishment of selected tasks by a predetermined sequence procedure. The intent of this (work
card/checklist) is to eliminate the probability of omission of a step in the accomplishment of the intended
task. The procedures contained herein are presented in the shortest practical form for use by qualified
personnel and are not intended to provide full technical instructions. This (work card/checklist) provides, in
an abbreviated form, procedures for (appropriate tasks, inspections, etc.). These procedures are derived from,
but do not replace, the detailed procedures contained in Technical Orders (TO). When malfunctions occur
reference to the TO shall be made.”
Electronic Presentation: References shall be linked to the data that it applies.
3.3.3 Preliminary instructions. The preliminary instructions shall precede the work card/checklist task and
shall contain information pertinent to accomplishment of the task, such as applicable technical manuals,
mechanic or Air Force Specialty Code (AFSC) types required, and special tools or equipment required.
3.3.4 Nomenclature. First use of a nomenclature used in a work card/checklist shall be identical with the
nomenclature used in any manual to which the work card/checklist applies. Further use of a nomenclature in
a work card/checklist may be abbreviated. Abbreviations shall be in accordance with MIL-STD-38784.
3.4 Work cards.
3.4.1 Work card requirements. Separate and distinct work card sets, as they apply to the breakout of the
inspection requirements chapters of the -6 inspection manual; e.g., system(s) or end item(s) of equipment,
etc., shall be prepared for each type of inspection; i.e., Preflight/Preoperation, Basic Postflight/Postoperation,
Hourly Postflight/Postoperation, Periodic/Phased/Isochronal, etc. When specified by the acquiring activity
(see 6.2o), the preflight/preoperation shall be combined with the basic postflight/postoperation (equipment
using the periodic or phased concept) or the thruflight (equipment using the isochronal concept) into one set
of work cards . Work cards shall be prepared for supplemental periodic inspection requirements which
become due in multiples of the particular periodic (see figure 9). If no inspection requirements manual is
prepared, the work cards shall include all inspections, including event orientated special inspections.
3.4.2 Work card format. Print Presentation: Work cards shall be prepared in horizontal, 8 by 5 inch
format. Unless otherwise specified by the acquiring activity (see 6.2p), work cards shall be arranged
head to head. When specified, work cards shall be arranged head to foot. Spacing and arrangement

8
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

shall be utilized to achieve uniformity. Individual inspection requirements shall be identified by double
spacing between each requirement.
Electronic Presentation: Appendix D provides the directions for obtaining digital tools for the electronic
preparation of work cards. Work cards shall be formatted as scrollable tables. The header and footer
information (from front card) will stay fixed while the text will scroll inside of the work card. Individual
inspection requirements shall be identified by double spacing between each requirement.
3.4.3 Work card arrangement. Work card sets shall be arranged as follows:
a. Front Matter
b. Work Area Diagrams
c. Inspection Requirements
d. Lubrication Requirements (Lubrication may be included with inspection items)
3.4.3.1 Work card front matter. Front matter shall be prepared in accordance with MIL-STD-38784 except
the List of Effective Pages shall be titled List of Effective Cards (see 3.4.4.1).
3.4.3.2 Work area diagram cards. Work area diagram cards (see figure 10) shall be prepared to reflect the
work area breakdown for each weapon/support system required for each type of inspection.
3.4.3.3 Inspection requirements (see figure 11). The inspection requirements work cards shall reflect the
requirements contained in chapters 1 and 2 of the -6 inspection manual for all areas/parts requiring
inspection, lubrication, and servicing. If specified by the acquiring activity, work cards may be developed as
self-contained documents and only need to be referenced in the -6 inspection manual (see 6.2q). The card(s)
shall cover systems, assemblies, or components logically grouped together to show an easily understood and
orderly progression of inspection requirements. The cards shall contain the appropriate inspection requirement
statements on the face of the card and inspection illustrations on the reverse side. If specified by the
acquiring activity (see 6.2r), and no inspection illustrations exist, the inspection requirement statements
may flow to the reverse side of the card. The illustration shall reflect the alphanumerically identified
inspection/servicing locations specified on the face of the card. Special enlarged and detailed views shall be
used to identify otherwise obscured inspection items. Additional information essential to the work card
requirements may be obtained from maintenance manuals and other current technical data. Work card
information shall include the listing of specified pressures, torques, clearances, tolerances, fluid levels,
notes, cautions, warnings, etc. When an inspected item requires a servicing action, such as hydraulic
accumulator servicing, the inspection requirement shall indicate the service reference required, i.e. “Check
hydraulic accumulator for proper service (if service is required refer to JG 12-10-05)”. Should deviations be
specified by the acquiring activity (see 6.2s) (e.g. for different models of equipment) all information of a
general nature, such as keys, added symbols, effectivity codes and explanatory notes shall be shown on the
introduction cards. Notes shall be brief and explicit.
Electronic Presentation: Graphics shall be linked to the first step it is referencing.
3.4.3.4 Lubrication requirements (see figure 13). The lubrication work cards shall show periodic lubrication
requirements for all parts. Cards shall cover systems, assemblies, or components logically grouped together
to show an easily understood and orderly progression of lubrication requirements. The cards shall contain the
appropriate lubrication requirement statements on the face of the card and lubrication illustrations on the
reverse side. The illustration shall reflect the alphanumerically identified lubrication locations specified on the
face of the card, the lubricants required for each location, and a symbol indicating the method of application.
Special enlarged and detailed views shall be used to identify otherwise obscured lubrication items. Lubrication
work cards text shall be brief and explicit, providing the necessary lubrication information and shall present
complete lubrication requirements without need for other manuals. Should deviations be specified by the
acquiring activity (e.g. for different models of equipment), (see 6.2t), all information of a general nature
such as keys, added symbols, effectivity codes and explanatory notes shall be shown on the introduction
cards. The lubrication requirement work cards shall be included within specific mechanic type groups.
Electronic Presentation: Graphics shall be linked to the first step it is referencing.

9
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

3.4.4 Work card preparation. Work cards shall be prepared in accordance with 3.4.4.1 through 3.4.4.15
and figures 11 and 13.
Electronic Presentation: The fixed footer row may be left off when it is identical to fixed header row.
3.4.4.1 Card number. Each work card shall be assigned one number which shall appear on the front
and back of the card (including front matter cards). If the back of the card has no data it shall be
blank. Each card shall be numbered consecutively with a three digit number starting with 001 for the first
card of each set, except front matter cards which shall be numbered in accordance with MIL-STD-38784.
Where the set is divided into chapters, card numbers shall be preceded by the chapter number. For
example: Chapter 1, card 10 would be 1-010; Chapter 2, card 22 would be 2-022. These blocks do not
apply to the phased inspection cards (see 3.4.4.1.1).
Electronic Presentation: Work cards shall only be enumerated on new card elements.
3.4.4.1.1 Phased inspection card number. Each card shall be assigned a sequential number which shall
appear on the front and back of the card. When specified by the acquiring activity (see 6.2u), card numbers
shall be prefixed according to their groupings or applicable phase (e.g. first phase, second phase, etc.).
Electronic Presentation: Data shall be formatted as a scrolling table.
3.4.4.2 Work area(s). These blocks shall list the work area or areas in which the tasks listed on the card shall
be performed. The work area numbers shall be obtained from the work area diagram. When more than one
work area is involved, the work area numbers shall be listed in the order in which the areas will be occupied.
3.4.4.3 Type mechanic required. This entry shall identify the type mechanic or specialist (e.g., AIRCRAFT,
ENGINE, HYDRAULIC, etc.) required to accomplish the tasks listed on the card. Where assistance is
required by a type mechanic other than that listed, an “Assisted by mechanic type” note shall be
added to the beginning of the task.
3.4.4.4 Mechanic number required. This entry shall identify the number of specialists required to accomplish
the tasks outlined on the work card.
3.4.4.5 Card time. This entry shall indicate the amount of time needed to accomplish the tasks prescribed
by the card. This shall be the total time required for all items reflected in the body of the card. Time
shall be indicated in hours and minutes; i.e., 02:15, 01:40, 00:25, etc. All time shall be reflected to
the nearest minute and reflected in four digits.
3.4.4.6 Technical manual identification and change numbers. The technical manual identification number
and change number shall be placed in the respective blocks. Neither the publication nor change
dates shall be given.
3.4.4.7 Body heading (inspection requirements). An entry shall be made in this block to indicate the
type of inspection for which the card set applies. For example: Preflight, Basic Postflight, Periodic,
100 hour, 200 hour, 180 days, etc.
3.4.4.8 Electrical power.
a. When power is required during the accomplishment of the tasks entered on the card, the
word “ON” shall be placed in this block.
b. When it is mandatory that power be off during the accomplishment of the tasks entered on the
card, the word “OFF” shall be placed in this block.
c. When power may be on or off during the accomplishment of the tasks entered on the card, this
block shall be left blank.
d. Power on and off requirements shall normally not be stated on the same card except when
necessary for continuity of the operation, in which case, the word “ON/OFF” shall be placed
in this block and each power ON requirement shall be preceded by an “at” (@) symbol
in the body of the card.
3.4.4.9 Service. When specified by the acquiring activity (see 6.2v), this block shall be completed,
otherwise it shall be left blank. When service must be interrupted to accomplish the tasks on the card, the

10
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

word “OUT” shall be placed in this block. When service need not be interrupted to accomplish the tasks on
the card, the word “IN” shall be placed in this block. When there are both in and out of service conditions
relating to the tasks on the card, the words “IN/OUT” shall be placed in this block.
3.4.4.10 Figure. Unless otherwise specified by the acquiring activity (see 6.2w), this block shall be left
blank. When specified by the acquiring activity, figure numbers or other identifier shall be assigned to the
figures on each card and this shall be inserted in the figure block.
3.4.4.11 Man-minutes column. The man-minutes required to accomplish each individual inspection item
shall be entered in this column. If work cards contain a series of short time items, a horizontal dash may
be placed on the line for the first and last items of the group and the time may be made as a single
entry midway between the two horizontal dashes.
3.4.4.12 Work area column. The work area in which each item or items will be accomplished shall be
listed in this column.
3.4.4.13 WUC column. Unless otherwise specified by the acquiring activity (see 6.2x), the WUC column
shall use two columns, (system and subsystem columns, see 3.4.4.13.1, 3.4.4.13.2, and figure 11). If
specified by the acquiring activity, WUC entries into this column shall be in one column utilizing the
WUC in its entirety as defined by MIL-DTL-38769 (see figure 12).
3.4.4.13.1 WUC system column. The first two digits of the WUC are used to designate a system. Entries
shall be made in this column to denote the system WUC number for each item. Requirements of a
general nature, which cannot be coded to a specific system, shall not be coded. Wire bundles are
an example of this category.
3.4.4.13.2 WUC subsystem column. Entries shall be made in this column to denote the WUC subsystem
and component number for each item. Coding of other requirements shall be accomplished to the appropriate
level. This level may be to the third, fourth, or fifth digit. Routine servicing and lubrication items shall not
be coded since these items are covered by support general codes.
3.4.4.14 References. All requirements for operational checks or adjustments shall include specified
instrument readings, tolerances, etc., or reference to applicable technical manuals in which the information
may be found. Requirements to be included in the work cards are not collectively reflected in a single
manual. Therefore, these requirements must be obtained from several sources, including service tests,
service experience, contractor's recommendations, and technical manuals.
Electronic Presentation: If the capability exists, references to other Technical Manuals shall be linked
to the TO that they apply.
3.4.4.15 Lubrication symbols. A lubrication symbol shall consist of a North Atlantic Treaty Organization
(NATO) number (reference TO 42B1-1-15) or a specification number, an application symbol (see figure 14),
and an alphanumeric identifier corresponding to the lubrication location. Special notes shall be included
when necessary. The lubrication symbol shall have a leader line extending to the point on the diagram, or
drawing, that requires servicing. The symbol shall designate one point of servicing; however, several leader
lines may branch from the main leader to designate adjacent points of servicing.
3.4.5 Inspection requirements cards. If the inspection requirement cards are divided into Preflight, Basic
Postflight, etc., each group shall be preceded by a introduction card. The inspection work cards shall be
arranged so that preparation requirements precede the inspection requirements. These requirements shall
identify the tasks necessary to prepare the system/equipment for each inspection, e.g., listing of special
tools, test equipment, etc. Inspection work cards of each set shall be arranged so as to provide distinct
groups for each type of mechanic or specialist required to perform the inspection. In the case of
periodic/phased/isochronal inspections, the set shall be divided into major groups and subgroups; that is, if
predock work cards are provided, they would be the first group, the dock inspection work cards would be
the next group and the postdock cards would be the third group, each group subgrouped by mechanic type.
3.4.5.1 Special inspections. Special inspection requirements to be accomplished on an event oriented basis
shall not have inspection work cards prepared except as specified in 3.4.1.

11
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

3.4.5.2 Servicing. Servicing work cards shall be prepared to cover all items that require scheduled
service, i.e., aircraft batteries, hydraulic reservoirs, etc.
3.4.5.3 Phased inspection work cards.
3.4.5.3.1 Workload requirements. Determination of the total workload requirements shall be as specified by
the acquiring activity (see 6.2y) and shall reflect a breakdown of the number of items and man-hours required
by interval groupings of basic and hourly postflight and subsequent hourly intervals for which inspections are
prescribed. A listing of equipment, by systems, for which there is an inspection requirement, shall be as
specified by the acquiring activity (see 6.2z) and shall include the inspection interval, the time required to
make the inspection, and the work areas of the aircraft or equipment in which the item is located.
3.4.5.3.2 Interval. Determination of the interval at which phased inspections will be made shall be
as specified by the acquiring activity (see 6.2aa).
3.4.5.3.3 Number of packages. Inspection requirements shall be grouped into approximate equal workloads
for each package. As far as possible, associated items shall be grouped together. If an area is opened up for
inspection or lubrication, then any other necessary inspection or lubrication in the same area shall be phased
in at the same time. The workload shall be distributed in such a way as to avoid repeated movement of
access or ground support equipment, etc. Care shall be taken to put all items located in the same difficult
access area in the same package to minimize time involved in gaining access to the equipment.
3.4.5.3.4 Combining packages. Instructions on whether phased packages can be combined and the number
of packages authorized at one time for an approved inspection shall be as specified by the acquiring
activity (see 6.2ab) and reflected in the introduction of the phased work cards. Typical statements are:
“Accomplishment of multiple packages for interval greater than the basic phased interval is not authorized,”
or “Combining 2 packages for a 50 hour interval or 4 packages for a 100 hour interval is authorized.
Combination of more than 4 packages for other intervals is not authorized.”
3.4.5.4 Periodic inspection work cards. Periodic inspection work cards shall reflect the requirements in the
inspection manual and shall provide for a complete inspection of the aircraft or equipment.
3.4.5.5 Isochronal inspection work cards. Isochronal inspection work cards shall reflect the requirements in
the inspection manual. The following inspection work cards shall be included in isochronal inspections:
a. Home station check inspection work cards.
b. Minor inspection work cards.
c. Major inspection work cards.
3.5 Checklists (see figure 15). Appendix F provides the directions for obtaining digital tools for the
electronic preparation of checklists.
3.5.1 Checklist front matter. Front matter shall be prepared in accordance with MIL-STD-38784.
3.5.2 Checklist size and arrangement. Print Presentation: Unless otherwise specified by the acquiring
activity, checklists shall be prepared in 5 by 8 inch size (see 6.2ac) and be arranged head to head. When
specified by the acquiring activity, checklists shall be prepared in 8 ½ by 11 inch size and/or be arranged
head to foot (see 6.2ad). When arranged head to foot, the technical manual identification number shall be at
the upper right and, the page and change numbers shall be in the lower right.
Electronic Presentation: Data shall be formatted as a scrolling table.
3.5.3 Style and format of text pages. Text shall be single spaced, except between procedural steps
where double spacing shall be used.
Print Presentation: Style, format, and numbering shall be in accordance with MIL-STD-38784 except that if
the checklist chapters bear titles such as Normal Procedures, Emergency Procedures, Alert Procedures, etc.,
the pages of each chapter shall be numbered N-1, N-2; E-1, E-2; A-1, A-2; etc.
Electronic Presentation: Normal Procedures, Emergency Procedures, Alert Procedures, etc., shall be identified
in the TOC and linked to the data in which it applies.

12
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

3.5.4 Illustrations. Illustrations shall be included only when absolutely necessary to preclude continuous
reference to critical data in applicable maintenance manuals. They shall be limited to charts or graphs that
contain information which is variable such as temperature or humidity stabilization prior to testing.
3.5.5 Maintenance/operation (non-flight crew) checklists. The parent manuals shall be used as the source
documents for obtaining the basic checklist requirements. Checklists shall condense required tasks. They
shall standardize, control, integrate, and time phase tasks. They shall be prepared to prevent potential
injury or loss of life to personnel. Tasks shall be listed in the most logical and convenient sequence
of accomplishment. Checklists shall tell what to do and when it shall be accomplished. They shall
not contain instructions on how to do a task.
3.5.5.1 Maintenance/operation (non-flight crew) checklist format. Checklist tasks shall be presented in a
demand/response format, when practical, with the demands at the left and the responses at the right. The
responses shall be in upper case letters or figures. Blank lines shall be provided to the right of the responses
as check spaces. If insufficient space is available, the blank line shall be entered below each response. Normal
readings (and tolerances, if applicable) shall be shown in the response column. Leaders shall be inserted
between the columns; e.g. “Demand...…Response”. The demand/response presentation need not consist of a
complete sentence. The function title shall be in upper case letters and shall be underlined. All controls such
as switch names and switch positions shall be as marked on the hardware. All other tasks shall have only
the first letter of the first word capitalized. When checklist procedures are written for individual performance
(such as motor vehicle inspection and operation), the demand/response format need not be followed.
Print Presentation: Each new function within a checklist shall be started on a new page.
Electronic Presentation: Data shall be formatted as a scrolling table.
3.5.5.2 System/Subsystem/Sub-Subsystem Number (SSSN) (maintenance checklists only). Some checklists
are prepared from parent OMMs, the checklists are produced in accordance with MIL-DTL-83495.
Print Presentation: When applicable, SSSN numbers shall be included on the applicable pages in accordance
with MIL-STD-38784.
Electronic Presentation: The SSSN shall be marked on the TOC. There are no specific requirements for
running footer info regarding a SSSN. If the capability exists, the SSSN shall be placed on the bottom left
corner of the viewing area to which it applies.
3.5.5.3 References (other manuals). The applicable maintenance and/or operation manual may be referenced
at the end of the task in order to provide additional information to accomplish, amplify or clarify a
procedure, or to correct a discrepancy or malfunction that may develop when accomplishing the task. Tasks
shall be grouped into major functions.
Electronic Presentation: If the capability exists, references shall be linked to the data to which they apply
3.5.5.4 Emergency procedures. Emergency procedures shall be included within the normal checklist and
shall also be contained at the end of the checklist. If the same emergency is likely to occur in more than
one phase of the checklist, the emergency procedures shall be repeated for each occurrence. Emergency
procedures at the end of the checklist shall be numbered separately as required by 3.5.3.

4 VERIFICATION
4.1 Verification requirements. When the technical data produced according to this specification is offered for
acceptance, all tests, reviews, and verifications required by the acquiring activity to determine that it conforms
to the requirements in section 3 of the specification, shall be accomplished as specified (see 6.2ae and 6.8).
4.2 Compliance. Technical Manuals (TMs) shall meet all requirements of section 3 and the appropriate
markup language tools appendix (see appendices A through F, (appendices B, C, and E have been deleted))
of this specification, as specified by the acquiring activity (see 6.2). The requirements set forth in this
specification shall become a part of the contractor’s overall inspection system or quality program. The
absence of any requirements in this specification shall not relieve the contractor of the responsibility of
ensuring that all products or supplies, submitted to the government for acceptance, comply with all

13
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

requirements of the contract. Use of sampling inspections shall be at the discretion of the contractor, and in
accordance with commercially acceptable quality assurance procedures. However, use of sampling in QA
procedures does not authorize submission of known defective material, either indicated or actual, nor does it
commit the government to accept defective material.

5 PACKAGING
5.1 Packaging. For acquisition purposes, the packaging requirements shall be as specified in the contract or
order (see 6.2af). When packaging of materiel is to be performed by Department of Defense or in-house
contractor personnel, these personnel need to contact the responsible packaging activity to ascertain packaging
requirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activities
within the Military Service or Defense Agency, or within the military service’s system commands. Packaging
data retrieval is available from the managing Military Department’s or Defense Agency’s automated packaging
files, CD-ROM products, or by contacting the responsible packaging activity.

6 NOTES
(This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.)
6.1 Intended use. Technical manuals, work cards, and charts prepared in accordance with this specification
are intended for use by Air Force organizational, intermediate and depot maintenance activities as a guide
for performing preventative maintenance (i.e., isochronal, programmed depot maintenance, combined type,
etc.) found in the 00-20-series technical manuals, on Air Force equipment. Checklists are intended to be
used by operations and maintenance personnel to ensure that no step is overlooked. The military unique
requirements for the technical data covered by this specification are contained in 00-20-series TOs.
6.2 Acquisition requirements. Acquisition documents should specify the following:
a. Title, number, and date of this document.
b. Types of manuals required (see 3.1).
c. If more than one inspection and maintenance requirements manual may be prepared (see 3.2.1).
d. Basis for inspection and maintenance requirements (-6) manual (see 3.2.1.1).
e. Maximum safe interval between inspections of weapon system (see 3.2.1.1.2).
f. If component coverage will be other than as specified in this document and, if so, items
exempt from coverage (see 3.2.1.7).
g. If additional information applicable to a specific weapon system or any modifications to the
introduction is required (see 3.2.2.1).
h. If any specified sections in chapter 1 of inspection and maintenance requirements (-6) manual will
not be used (see 3.2.2.2).
i. If additional sections in chapter 1 of inspection and maintenance requirements (-6) manual will
be included and type required (see 3.2.2.2).
j. Inspection concept (periodic, phased, or isochronal) to be used (see 3.2.2.2.6).
k. If any specified sections in chapter 2 of inspection and maintenance requirements (-6) manual will
not be used (see 3.2.2.3).
l. If additional sections in chapter 2 of inspection and maintenance requirements (-6) manual will
be included and type required (see 3.2.2.3).
m. Items and components that must be removed and changed for new or overhauled like items at
the expiration of a specified number of flying hours, expiration of a number of cycles, or
an interval of calendar time (see 3.2.2.4).
n. Selection of items to be listed in Chapter 4, Section I - Base Level Restrictions (see 3.2.2.5.1.1).

14
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

o. If the preflight/preoperation inspection will be combined with the basic postflight/postoperation

(periodic or phased concept)/thruflight (isochronal concept) inspection (see 3.4.1).
p. If work cards will be head to foot (see 3.4.2).
q. If work cards are to be developed as self-contained documents (see 3.4.3.3).
r. If inspection requirement statements are to flow to the reverse side of the card (see 3.4.3.3).
s. If deviations are required for inspection requirements (see 3.4.3.3).
t. If deviations are required for lubrication requirements (see 3.4.3.4).
u. If phased inspection card numbers will be prefixed (see 3.4.4.1.1).
v. If the service block will be completed (see 3.4.4.9).
w. If the figure block will be completed (see 3.4.4.10).
x. If WUC column is to use two columns or one column (see 3.4.4.13).
y. Workload requirements for phased inspection work cards (see 3.4.5.3.1).
z. A listing indicating equipment, by system, for which there is an inspection requirement (see
3.4.5.3.1).
aa. Interval at which phased inspections will be made (see 3.4.5.3.2).
ab. Instructions on whether phased packages can be combined and the number of packages authorized
at one time for an approved inspection (see 3.4.5.3.4).
ac. If checklist size will be 8 1/2 by 11” inch size (see 3.5.2).
ad. If checklist arrangement will be head to foot (see 3.5.2).
ae. The requirements for tests, reviews, and verifications specified for manuals developed under
this specification (see 4.1).
af. Packaging requirements (see 5.1).
6.3 Technical manuals. The requirement for technical manuals should be considered when this specification
is applied on a contract. If technical manuals are required, specifications and standards that have been
authorized and assigned an Acquisition Management Systems Control (AMSC) number must be listed on a
separate Contract Data Requirements List (DD Form 1423), which is included as an exhibit to the contract.
The technical manuals must be acquired under separate contract line item in the contract.
6.4 Coordination. The procuring activity, after coordination with the using command(s), will specify the
publication(s) required. An inspection requirements manual and work card set will be developed for each
system i.e., aircraft, C-E, support equipment, etc.
6.5 Additional information. Additional information relative to Air Force aircraft, missile and space weapon
inspection systems, policies, and procedures may be obtained from the 00-20-series technical orders.
6.6 Definitions. To clarify the terms used throughout this specification, the following definitions are given:
6.6.1 Acceptance inspection. An inspection that will be performed on all newly assigned or extensively
modified aircraft, drones, missiles, and support equipment to determine mechanical fitness for flight or use
and which usually requires an FCF or Functional Check.
6.6.2 Accessible. A term applied to equipment that may be inspected without further disassembly or
removal of covers, cowling, closures, panels, etc, other than those required to accomplish the more specific
requirements applicable to the particular inspection.
6.6.3 Basic postflight/postoperation inspection. This inspection is a visual examination of certain components,
areas, or systems, to assure that no defect exist which would render the aircraft/equipment unsuitable for
flight/use. Primary items check are as follows:
a. Items that due to their operational characteristics are subject to loss of lubricant, fluids, air,
etc., during flight/operation.

15
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

b. Items that due to and during flight/operation are subject to damage such as impact, foreign
objects, etc.
c. Items of critical nature that are subject to developing defects which are not readily apparent to
the users during operation.
d. Items, such as down locks, safety pins, and protective covers, that must be installed prior
to maintenance.
6.6.4 Cautions. A caution is a short message which calls attention to an essential operating or maintenance
procedure, practice, condition, statement, etc., which, if not strictly observed, could result in damage to, or
destruction of equipment or loss of mission effectiveness.
6.6.5 End item. Entity of hardware which is not to be installed in another piece of equipment. The end
item for the weapon/support system could be the aircraft, rocket, drone, training device, etc.
6.6.6 End of Runway inspection. This inspection detects critical defects which may have developed during
ground operation. Items checked are those subject to damage during ground operations or are not readily
apparent until after operation begins. Also checked are items such as panels and doors, that must be secure
prior to flight/operation, and down locks and protective covers, that must be removed prior to flight/operation.
6.6.7 Excessive. Condition which has progressed to the degree that, if not corrected, could result in
failure or malfunction of the component prior to the next scheduled accomplishment of the requirement
which directed attention to the condition.
6.6.8 Functional system. Those units which make up a system without regard to whether the units are
hydraulic, electrical, pneumatic, electronic, or mechanical in nature. The components which comprise a
functional system are those components which contribute to the actual function or activation of the system.
For example, the components which supply the hydraulic source of power are included under the
hydraulic system, whereas a flight control actuator which is hydraulically operated is included under the
flight control system, which is a functional system.
6.6.9 Home station check inspection. Home station check inspections are accomplished after return from a
long range mission or at expiration of a short term calendar period. Home station check inspections are
accomplished in conjunction with the minor and major inspections.
6.6.10 Hourly postflight/postoperation inspection. An inspection which includes those requirements to be
accomplished at a specified interval (hours/cycles) or multiples of the specified interval that are necessary to
assure no condition exists in a known problem area that would be detrimental to the safety of flight
operation. These requirements augment the basic postflight/postoperation requirements. Included are
requirements that fall in the following categories:
a. Items that due to their installation characteristics are subject to excessive chafing and insecure
mounting.
b. Items that are subject to extreme heat conditions.
c. Items that due to their design characteristics are subject to developing leaks or cracks.
d. Items that require more frequent verification of serviceability or operation than the
periodic/phased/isochronal inspection interval.
e. Items that require more frequent verification of service than the periodic/phased/isochronal
inspection interval.
6.6.11 Isochronal inspections. Isochronal inspections are accomplished based upon calendar periods of
equal duration and recurring at regular intervals.
6.6.12 Linear Technical Manual (TM) print versus electronic presentation requirements. Within this detail
specification, requirements labeled as electronic or print presentation are defined as follows:
a. Electronic presentation: Specifies requirements that apply to TM data that are displayed on an
electronic/digital system, such as various kinds of work station computers, or portable electronic
devices. These requirements only apply to technical data composed as linear Electronic TMs

16
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

(ETMs), i.e., linear structured compositions to be rendered in HTML for display in a browser.
Requirements for digital nonlinear data, Interactive ETMs (IETMs) or Interactive Electronic
Technical Publications (IETPs), are contained in a separate specification.
b. Print presentation: Specifies requirements that apply only to page-oriented and printed TMs.
Print presentation requirements apply overall to PDF TM files, with some exceptions, as
specified by the acquiring activity. For example, in the case of references, electronic linking
requirements should apply.
6.6.13 Major inspection. Major inspections consist of inspections to determine if conditions exist which
could result in failures or malfunctions prior to the next scheduled inspection and are more searching in
scope than the home station check and minor inspections.
6.6.14 Minor inspection. Minor inspections consist of inspections to determine if conditions exist which
could result in failures or malfunctions prior to the next scheduled inspection and are more searching
in scope than the home station check inspection.
6.6.15 Notes. A note is a short message which describes an unusual procedure or condition to which
special attention must be paid for any reason (but it may not replace a caution or warning.)
6.6.16 Parent manuals. Parent manuals are those that contain complete operational and maintenance
instructions and from which checklist items are extracted.
6.6.17 Periodic inspection. Periodic inspections are accomplished upon accrual of a number of flying
hours, operating hours, or at the expiration of a calendar period.
6.6.18 Planned inspection concept. Method of performing specific preventive maintenance and inspection
requirements on a scheduled basis and predetermines the numbers and skills of maintenance personnel
required to accomplish the predictable portion of the inspection. It effectively utilizes maintenance personnel
in accordance with their skills against a time schedule using work cards and sequence charts.
6.6.19 Preflight/preoperation inspection. A (flight) preparedness inspection that checks items that, due to
environment, are subject to damage by outside forces, such as ground equipment, maintenance crews,
elements of nature, etc. This inspection also checks items that, due to design characteristics, normally require
service or verification of service prior to the first flight/operation of the day.
6.6.20 Preventive maintenance. The normal inspection, upkeep, and lubrication of equipment which may be
required to maintain serviceability of equipment which has been subjected to usage, wear and deterioration.
6.6.21 Special inspection. An inspection which supplements other inspections (daily, preoperation, periodic,
flying hours, operating hours, or calendar) and are accomplished because of specific circumstances or upon
occurrence of specific conditions or events. This may also include those requirements having a prescribed
interval or frequency which do not coincide with the scheduled periodic, phased or isochronal inspection.
6.6.22 Special inspection and maintenance requirements. The special inspection acceptance and functional
check flights, depot level inspection, and maintenance level requirements are performed to determine item or
weapon system serviceability. Special inspections include the following:
a. Functions to be accomplished at the expiration of a specified number of flying hours, equipment
hours of operation, and lapse of calendar time.
b. Functions to be accomplished after the occurrence of a specified or unusual condition or incident,
and when accepting an aircraft after extensive modifications.
6.6.23 Support equipment. All articles required to make a weapon system, command and control system,
support system, advanced objective, subsystem, or end item or equipment operational in its intended
environment. This includes all equipment required to install, launch, arrest, guide, control, direct, inspect, test,
adjust, appraise, gage, measure, assemble, disassemble, handle, transport, safeguard, store, actuate, service,
repair, overhaul, maintain, or operate the system, subsystem, end item, or component. This comprises special
tools and test devices, including measurement standards required for support of items supporting equipment.

17
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

6.6.24 Thruflight inspection. This inspection is a between flights general visual examination of certain
components, areas, or systems, to assure that no defects exist which would render the aircraft unsuitable
for flight continuance.
6.6.25 Warnings. A warning is a short message which calls attention to an essential operating or
maintenance procedure, practice, condition, statement, etc., which, if not strictly observed, could result in
injury to, or death of personnel or long term health hazards.
6.6.26 Work Unit Code. A code used to identify the equipment for a weapon/support system by system,
subsystem and component breakout consisting of a combination of five numeric and alphabetic characters.
These codes are contained in a WUC (-06) Manual.
6.7 Subject term (key word) listing.
Acceptance Inspection
Inspection Manual
Isochronal Inspection
Periodic Inspection
Phased Inspection
6.8 TM verification requirements. See 4.1. The Air Force Technical Order Policy and Procedures (AF
TOPP) team, AFMC/A4FI, provides the specific requirements for verification of technical data developed and
delivered through this specification, as well as guidance for including these requirements in the solicitation or
contract (see TO 00-5-3, AF Technical Order Life Cycle Management).
6.9 Changes from previous issue. The margins of this specification are marked with vertical lines to
indicate where changes from the previous issue were made. This was done as a convenience only and the
Government assumes no liability whatsoever for any inaccuracies in these notations. Bidders and contractors
are cautioned to evaluate the requirements of this document based on the entire content irrespective of the
marginal notations and relationship to the previous issue.

18
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 1. Example Introduction (-6) manual.

19
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 1. Example Introduction (-6) manual - Continued.

20
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 2. Example Chapter 1 page (-6) manual (Phased Inspection Showing Hourly Intervals).

21
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 2. Example Chapter 1 page (-6) manual (Phased Inspection

Showing Hourly Intervals) - Continued.

22
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 3. Example Chapter 2 Section I Page (-6) manual.

23
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 4. Example Chapter 2 Section II Page (-6) manual.

24
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 5. Example Chapter 2 Section III Page (-6) manual.

25
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 6. Example Chapter 2 Section IV Page (-6) manual.

26
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 7. Example Chapter 3 Page (-6) manual.

27
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 8. Example Chapter 4 Page (-6) manual.

28
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 9. Example Inspection Multiples.

29
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 10. Example Work Area Diagram.

30
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 11. Example Inspection Work Card (Front).

31
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 11. Example Inspection Work Card (Front) - Continued.

32
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 12. Example Inspection Work Card (Front) WUC Column.

33
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 13. Example Lubrication Work Card.

34
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 13. Example Lubrication Work Card - Continued.

35
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 14. Example Application Symbols.

36
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

FIGURE 15. Example Typical Checklist Page.

37
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

APPENDIX A

INSPECTION AND MAINTENANCE REQUIREMENTS TECHNICAL MANUAL

MARKUP LANGUAGE TOOLS

A.1 SCOPE
A.1.1 Scope. This appendix describes the standard Air Force (AF) tagged language digital tools created
for developing and delivering AF Technical Manuals (TMs). These tools are available as subsets in the
Digital Support Suites (DSS) (see A.2) provided by the AF Technical Manual Specifications and Standards
(TMSS) activity. This appendix is a mandatory part of this detail specification. The information herein
is intended for compliance.
A.1.2 Template Tool. The Document Type Definition (DTD) is the primary tool used as a template for
authoring AF TMs and is based on rules outlined in MIL-HDBK-28001 and ISO 8879. See A.2.1 for
information about the DTD specified for this appendix subset.

A.2 DIGITAL SUPPORT SUITES (DSS)

The DSS is comprised of the following tools for authoring and rendering the TM. See A.3 for information
about obtaining DSS component files in digital format through the TMSS activity website. For information
about the current status of DSS tools, see A.3.4.
A.2.1 Document Type Definition (DTD). The DTD provides the structure and content template in
accordance with the content specific requirements of this specification (see 3.2.2). To be delivered digitally,
the TM shall be tagged using the applicable DTD provided through the TMSS activity. Information
concerning the markup language type and use of DTDs currently provided, i.e., Standardized General Markup
Language (SGML), may be obtained through the contacts listed under A.3.
A.2.2 Tag Description Table (TDT). The TDT provides detailed descriptions of the elements contained in
the DTD. The TDT contains the element tagging structure, parent elements, full element name, source
paragraph, attribute descriptions unique to the element, and entities.

A.3 OBTAINING DSS TOOLS

A.3.1 Obtaining files by users with .mil web site access. The following applies to those interested in
obtaining DSS component files who are on a .mil internet domain, having .mil web address access.
A.3.1.1 AF TMSS web site. DTDs, TDTs, and other files in the DSS can be accessed at the TMSS
website at https://techdata.wpafb.af.mil/tmss/index.html. On the web page, the “Baseline Tools” menu option
in the left pane contains three bulleted options called “Specifications”, “Standards”, and “Handbooks”. Hover
the cursor over “Specifications” and a listing of the TMSS specifications will appear. Hover over the desired
specification number and another drop down list will appear that contains an entry indicating the PDF
version of the specification and other entries for the associated appendices. To obtain the preferred subset
DTD, select the desired appendix from the list. The following items will appear on the downloading page:
The name of the specification, the appendix number and name, the current version of the DSS, buttons to
download specific DSS files provided and a “Download” button to download the entire DSS zip file.
A.3.2 Obtaining files by users with a Public Key Infrastructure (PKI) certificate or a Common Access
Card (CAC). The following applies to those interested in obtaining DSS component files who have
a PKI certificate or a CAC:
A.3.2.1 AF TMSS SharePoint web site. DTDs, TDTs, and other files in the DSS can be accessed at the
AF TMSS SharePoint web site: https://cs2.eis.af.mil/sites/12316/default.aspx.
A.3.3 Obtaining files by users without .mil access, PKI certificate, or CAC. Those seeking to obtain DSS
files who do not have .mil web access, a PKI certificate, or a CAC should contact their government
Program Management Office (PMO) or see A.3.4 to obtain information.
A.3.4 TMSS Helpdesk assistance. Address any requests or questions relating to the DSS by E-mail to
[email protected] (organizational address: AFLCMC/HIAM-TMSS HLPDSK) or by postal mail to

38
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

APPENDIX A

Air Force Technical Manual Specifications and Standards, AFMC/AFLCMC/HIAM, 4170 Hebble Creek
Road, Building 280, Door 15, Wright-Patterson AFB OH 45433-5653.

39
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

APPENDIX D

WORK CARDS
MARKUP LANGUAGE TOOLS

D.1 SCOPE
See A.1.

D.2 DIGITAL SUPPORT SUITES (DSS)

See A.2.
D.2.1 Document Type Definition (DTD). The DTD provides the structure and content template in
accordance with the content specific requirements of this specification (see 3.4.2).

D.3 OBTAINING FILES

See A.3.

40
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

APPENDIX F

CHECKLIST
MARKUP LANGUAGE TOOLS

F.1 SCOPE
See A.1.

F.2 DIGITAL SUPPORT SUITES (DSS)

See A.2.
F.2.1 Document Type Definition (DTD). The DTD provides the structure and content template in accordance
with the content specific requirements of this specification (see 3.5).

F.3 OBTAINING FILES

See A.3.

41
 Downloaded from http://www.everyspec.com

MIL-DTL-5096H(USAF)

CONCLUDING MATERIAL

Custodians: Preparing activity:

Air Force - 16 Air Force - 16
(Project TMSS-2019-001)

Review activities:
Air Force - 01, 02, 10, 13, 19, 70, 71, 184

NOTE: The activities listed above were interested in this document as of the date of this document.
Since organizations and responsibilities can change, you should verify the currency of the information
above using the ASSIST Online database at https://assist.dla.mil.

42