Mil HDBK 3001
Mil HDBK 3001
com
NOT MEASUREMENT
SENSITIVE
MIL-HDBK-3001(AS)
15 May 2001
DEPARTMENT OF DEFENSE
HANDBOOK
OF
This handbook is for guidance only. Do not cite this document as a requirement.
MIL-HDBK-3001(AS)
FOREWORD
1. This military handbook is approved for use by the Department of the Navy and is available for use by all
Departments and Agencies of the Department of Defense (DoD).
2. This handbook provides non-regulatory guidance for the preparation of technical manuals that are required
to operate and maintain the various types of equipment and weapon systems within the Department of the
Navy. It is for guidance only and cannot be cited as a requirement. If it is, the contractor does not have to
comply.
3. This handbook expands and clarifies the requirements contained in MIL-STD-3001-1 through MIL-STD-
3001-8, Preparation of Digital Technical Information for Multi-Output Presentation of Technical Manuals,
and provides recommended writing style, comprehensibility, format, and graphics requirements used by the
U.S. Navy for the preparation of technical manuals to the work package concept.
4. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use
in improving this document should be addressed to: Commanding Officer, NAVAIRWARCENACDIV,
Systems Requirements Department, ATTN: Code 4.1.11.1, Lakehurst, NJ 08733-5100 by using the
Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this handbook or
by letter.
ii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
FOREWORD......................................................................................................................................................ii
1. SCOPE ........................................................................................................................................................... 1
1.1 Scope .................................................................................................................................................... 1
1.2 Applicability......................................................................................................................................... 1
2. APPLICABLE DOCUMENTS ................................................................................................................... 1
2.1 General ................................................................................................................................................. 1
2.2 Government documents ...................................................................................................................... 1
2.2.1 Specifications, standards, and handbooks ........................................................................................ 1
2.2.2 Other Government documents and publications .............................................................................. 2
2.3 Non-Government publications............................................................................................................. 3
2.4 Order of precedence ............................................................................................................................. 4
3. DEFINITIONS .............................................................................................................................................. 4
3.1 Acronyms used in this handbook ......................................................................................................... 4
3.2 Definitions of selected terms................................................................................................................ 5
3.2.1 Adjust ................................................................................................................................................ 5
3.2.2 Alert................................................................................................................................................... 5
3.2.3 Align.................................................................................................................................................. 5
3.2.4 American National Standards Institute (ANSI)................................................................................ 5
3.2.5 Assembly........................................................................................................................................... 5
3.2.6 Block diagram ................................................................................................................................... 5
3.2.7 Built-in Test Equipment (BITE)....................................................................................................... 6
3.2.8 Calibrate............................................................................................................................................ 6
3.2.9 Callout ............................................................................................................................................... 6
3.2.10 CALS (Continuous Acquisition Life-cycle Support) raster ........................................................... 6
3.2.11 Caution............................................................................................................................................ 6
3.2.12 Commercial and Government Entity (CAGE) Code ..................................................................... 6
3.2.13 Comprehensibility........................................................................................................................... 6
3.2.14 Computer Graphics Metafile (CGM) ............................................................................................. 6
3.2.15 Continuous Acquisition Life-cycle Support (CALS) ..................................................................... 6
3.2.16 Continuous tone photographs or drawings ..................................................................................... 6
3.2.17 Department of Defense (DoD)........................................................................................................ 6
3.2.18 Department of Defense Index of Specifications and Standards (DoDISS).................................... 6
3.2.19 Depot-level maintenance................................................................................................................. 6
3.2.20 Digital graphics forms .................................................................................................................... 7
3.2.21 Direct image copy (DIC)................................................................................................................. 7
3.2.22 Disassemble .................................................................................................................................... 7
3.2.23 Document Type Definition (DTD) ................................................................................................. 7
3.2.24 Electronic Display System (EDS)................................................................................................... 7
3.2.25 Electronic Technical Manual (ETM).............................................................................................. 7
3.2.26 Footer .............................................................................................................................................. 7
3.2.27 Formatting Output Specification Instance (FOSI) ......................................................................... 7
3.2.28 Frame-based Interactive Electronic Technical Manual (IETM)..................................................... 7
3.2.29 Functional diagram ......................................................................................................................... 7
3.2.30 Graphic(s) ....................................................................................................................................... 7
iii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
iv
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
v
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
vi
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
vii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
viii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
ix
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
x
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
PARAGRAPH PAGE
xi
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
FIGURE PAGE
xii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
FIGURE PAGE
xiii
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
FIGURE PAGE
FIGURE 31. Example of a typical corrosion control repair work package. ..................................................142
FIGURE 31. Example of a typical corrosion control repair work package - continued. ...............................143
FIGURE 31. Example of a typical corrosion control repair work package - continued. ...............................144
FIGURE 32. Example of a nondestructive inspection general information work package. ..........................145
FIGURE 32. Example of a nondestructive inspection general information work package - continued. .......146
FIGURE 33. Example of a nondestructive inspection typical procedures work package..............................147
FIGURE 33. Example of a nondestructive inspection typical procedures work package - continued...........148
FIGURE 33. Example of a nondestructive inspection typical procedures work package - continued...........149
FIGURE 34. Example of a nondestructive inspection specific procedures work package. ...........................150
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued. ........151
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued. ........152
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued. ........153
FIGURE 35. Example of a partial TM technical content selection matrix. ..................................................154
FIGURE 36. Example of an SGML document instance. ...............................................................................155
FIGURE 37. Example of lists.........................................................................................................................156
FIGURE 37. Example of lists - continued......................................................................................................157
FIGURE 38. Example of an aircraft systems wire run list.............................................................................158
FIGURE 39. Example of a wiring reference designation list. ........................................................................159
FIGURE 40. Example of an aeronautical equipment, airborne weapons/equipment
or support equipment wiring list....................................................................................................................160
FIGURE 41. Example of a page image area...................................................................................................161
FIGURE 41. Example of a page image area - continued................................................................................162
FIGURE 42. Example of text wrapping. ........................................................................................................163
FIGURE 43. Example of equations in text.....................................................................................................164
FIGURE 43. Example of equations in text - continued..................................................................................165
FIGURE 44. Example of numbering equations in text. .................................................................................166
FIGURE 45. Example of ETM/IETM installation data, CD label, and flyleaf data......................................167
FIGURE 45. Example of ETM/IETM installation data, CD label, and flyleaf data - continued. .................168
FIGURE 46. Example of preface information................................................................................................169
FIGURE 47. Example of CD content data. ....................................................................................................170
FIGURE 48. Example of title data. ................................................................................................................171
FIGURE 49. Example of log on. ....................................................................................................................172
FIGURE 49. Example of log on - continued. .................................................................................................173
FIGURE 50. Example of revision summary...................................................................................................174
FIGURE 51. Example one of List of Contents...............................................................................................175
FIGURE 52. Example two of List of Contents - manual title and front matter for scrollable ETM.............176
FIGURE 53. Example three of List of Contents - testing and troubleshooting work packages
for scrollable ETM. ........................................................................................................................................177
FIGURE 54. Example of "How To Use This IETM" information.................................................................178
FIGURE 55. Example of WP title and example one of WP initial setup.......................................................179
FIGURE 56. Example two of WP initial setup. .............................................................................................180
FIGURE 57. Example three of WP initial setup. ...........................................................................................181
FIGURE 58. Example four of WP initial setup for scrollable ETM..............................................................182
FIGURE 59. Example of supporting information WP - consolidated list of materials. ................................183
FIGURE 60. Example one of descriptive information. ..................................................................................184
FIGURE 61. Example two of descriptive information...................................................................................185
xiv
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
FIGURE PAGE
xv
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONTENTS
FIGURE PAGE
FIGURE A-5. Example of point-to-point and highway method signal flow. ................................................253
FIGURE A-6. Example of oval connectors to continue signals.....................................................................254
FIGURE A-7. Example of signal returns and breakoff symbols. ..................................................................255
FIGURE A-8. Example of boat symbols, numerical identifiers, and pyramid method. ................................256
FIGURE A-9. Example of signal difference techniques. ...............................................................................257
FIGURE A-10. Example of subordinate and coordinate junctions................................................................258
FIGURE A-11. Example of a hardware schematic diagram. .........................................................................259
FIGURE A-12. Example of a functional schematic. ......................................................................................260
FIGURE A-13. Example of a functional flow diagram..................................................................................261
FIGURE A-14. Example of uncrowded schematic diagram. .........................................................................262
FIGURE A-15. Example of components drawn on a schematic. ...................................................................263
FIGURE A-16. Example of a functional block diagram. ...............................................................................264
FIGURE A-17. Example of a cutaway diagram. ............................................................................................265
FIGURE A-18. Example of a logic diagram. .................................................................................................266
FIGURE A-19. Example of a truth table........................................................................................................267
FIGURE A-20. Example of a timing diagram................................................................................................268
FIGURE A-21. Example of a simplified diagram. .........................................................................................269
FIGURE A-22. Example of a partial diagram................................................................................................270
FIGURE A-23. Example of a test diagram.....................................................................................................271
FIGURE A-24. Example of a test setup diagram. ..........................................................................................272
FIGURE A-24. Example of a test setup diagram - continued........................................................................273
FIGURE A-25. Example of a power distribution diagram.............................................................................274
FIGURE A-26. Example of a pyramid diagram. ............................................................................................275
FIGURE A-27. Example of a wiring diagram. ...............................................................................................276
FIGURE A-27. Example of a wiring diagram - continued.............................................................................277
FIGURE A-28. Example of a wiring bundle routing illustration. ..................................................................278
FIGURE A-29. Example of a cabling diagram with table. ............................................................................279
FIGURE A-30. Example of a cable interconnect diagram. ............................................................................280
FIGURE A-31. Example of a piping diagram. ...............................................................................................281
FIGURE A-32. Example of port identification. .............................................................................................282
FIGURE A-33. Example of pattern codes......................................................................................................283
xvi
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
1. SCOPE.
1.1 Scope. This handbook provides non-regulatory guidance and information for the preparation of technical
manuals (TM) required to operate and maintain the various types of equipment and weapon systems within
the Department of the Navy. It provides preferred format and general writing style, graphics, revisions,
comprehensibility, and security guidance for the preparation of digital data for the delivery of all types of
work package TMs. Section 4 provides technical manual development guidance for the preparation of page-
based TMs. Section 5 provides technical manual development guidance for the preparation and display of
linear structured, scrollable, Electronic Technical Manuals and frame-based Interactive Electronic Technical
Manuals. Linear, scrollable Electronic Technical Manuals (hereafter referred to as ETMs) and frame-based
Interactive Electronic Technical Manuals (hereafter referred to as IETMs) are digital in form and designed for
interactive display to maintenance technicians or system operator end users by means of a computer
controlled Electronic Display System (EDS). Although this handbook encourages the delivery of digital files,
the requirement for digital files, paper, or both will be specified by the requiring activity. This handbook
provides guidance only. It cannot be cited as a requirement. If it is, the contractor does not have to comply.
1.2 Applicability. This handbook is applicable for use by the Department of the Navy and supporting
contractors.
2. APPLICABLE DOCUMENTS.
2.1 General. The documents listed below are not necessarily all of the documents referenced herein, but are
the ones that are needed in order to fully understand the information provided by this handbook.
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 listed in the latest issue of the Department of Defense Index of Specifications and
Standards (DoDISS) and supplemented thereto, and are referenced for guidance only.
SPECIFICATIONS
DEPARTMENT OF DEFENSE
1
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
STANDARDS
DEPARTMENT OF DEFENSE
HANDBOOKS
DEPARTMENT OF DEFENSE
(Copies of specifications, standards, and handbooks are available by request from Defense Automated
Printing Service, Building 4D, DPM-DODSSP, 700 Robbins Ave., Philadelphia, PA 19111-5094.)
2.2.2 Other Government documents and publications. The following other Government documents and
publications form a part of this handbook to the extent specified herein.
2
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Joint Pub 1-02 Department of Defense Dictionary of Military and Associated Terms.
NAVAIR 00-25-701 Technical Guide for Organizational Level Aircraft Wiring Systems
Repair Manuals.
OPNAVINST 5510.1 Department of the Navy Information and Personnel Security Program
Regulation.
Public Law Occupational Safety and Health Act, dated December 29, 1970
91-596 and Executive Order 11807.
(Copies of directives and instructions are available by request to Commander, Naval Inventory Control
Point Philadelphia, Publications/Forms Branch, Code 03334, 700 Robbins Avenue, Philadelphia, PA 19111-
5098.)
2.3 Non-Government publications. The following documents form a part of this document to the extent
specified therein. Unless otherwise specified, the issues of the documents that are DoD-adopted are those
listed in the latest issue of the DoDISS, and supplement thereto.
(Copies of the documents listed above are available from the American National Standards Institute,
Inc., 11 West 42nd Street, New York, NY 10036.)
(Copies of the document listed above are available from the IEEE Service Center, 445 Hoes Lane, P.O.
Box 1331, Piscataway, NJ 08855-1331.)
3
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
2.4 Order of precedence. In the event of a conflict between the text of this document and the references cited
herein, the text of the referenced document takes precedence. Nothing in this document, however, supersedes
applicable laws and regulations unless a specific exemption has been obtained.
3. DEFINITIONS.
3.1 Acronyms used in this handbook. The acronyms used in this handbook are defined as follows:
4
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.1 Adjust. To maintain or regulate within prescribed limits, by bringing into proper position, or by setting
the operating characteristics to specified parameters.
3.2.2 Alert. An alert is any message, communication, notice, or output which requires manual
acknowledgment from the user of the ETM/IETM.
3.2.3 Align. To adjust specified variable elements of an item to bring about optimum or desired
performance.
3.2.4 American National Standards Institute (ANSI). A private sector organization that plans, develops,
establishes or coordinates standards, specifications, handbooks or related documents.
3.2.5 Assembly. Two or more parts or subassemblies joined together to perform a specific function and
capable of disassembly (e.g., brake assembly, fan assembly, audio frequency amplifier).
NOTE
The distinction between an assembly and subassembly is determined by the
individual application. An assembly in one instance may be a subassembly in
another where it forms a portion of an assembly.
3.2.6 Block diagram. A modified schematic diagram in which each group of maintenance-significant
components that together perform one or more functions is represented by a single symbol or block. The
block or symbol representing the group of components shows simplified relevant input and output signals
pertinent to the subject diagram.
5
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.7 Built-in Test Equipment (BITE). Any identifiable device that is part of the supported end item and is
used for testing that supported end item.
3.2.8 Calibrate. To determine and cause corrections or adjustments to be made to instruments or test,
measuring, and diagnostic equipment used in precision measurement. Consists of comparisons of two
instruments, one of which is a certified standard of known accuracy, to detect and adjust any discrepancy in
the accuracy of the instrument being compared.
3.2.9 Callout. Anything placed on an illustration to aid in identifying the objects being illustrated, such as
index numbers, nomenclature, leader lines, and arrows.
3.2.10 CALS (Continuous Acquisition Life-cycle Support) raster. Compressed scanned raster images
(CCITT, Group 4) in accordance with MIL-PRF-28002.
3.2.11 Caution. A statement or some other notification about an operating or maintenance procedure,
practice, or condition that, if not strictly observed, could result in damage to, or destruction of, equipment
or loss of mission effectiveness.
3.2.12 Commercial and Government Entity (CAGE) Code. A five-character code assigned to commercial
activities that manufacture or supply items used by the Federal Government and to Government activities
that control design or are responsible for the development of certain specifications, standards, or drawings
which control the design of Government items. CAGE Code assignments are listed in the H4/H8 CAGE
Publications.
3.2.13 Comprehensibility. The completeness with which a user in the target audience understands the
information in the TM.
3.2.14 Computer Graphics Metafile (CGM). A standard digital form for vector graphics preparation as
defined by MIL-PRF-28003.
3.2.15 Continuous Acquisition Life-cycle Support (CALS). A DoD initiative to transition from paper-
intensive, nonintegrated weapon systems design, manufacturing, and support processes to a highly
automated and integrated mode of operation. This transition will be facilitated by acquiring, managing, and
using technical data in standardized digital form.
3.2.16 Continuous tone photographs or drawings. Continuous tone photographs or drawings have a
continuous gradation of tonal values ranging from light (white) to dark (black), including gray. These tonal
values are not created by lines or dots.
3.2.17 Department of Defense (DoD). The Office of the Secretary of Defense (OSD) (including all boards
and councils), the Military Departments (Army, Navy, and Air Force), the Organization of the Joint Chiefs
of Staff (OJCS), the Unified and Specified Commands, the National Security Agency (NSA), and the
Defense Agencies.
3.2.18 Department of Defense Index of Specifications and Standards (DoDISS). The DoD publication that
lists unclassified Federal and military specifications and standards, related standardization documents, and
voluntary standards approved for use by DoD.
3.2.19 Depot-level maintenance. Maintenance that is beyond the capability of the organizational and
intermediate support activities. Depot-level maintenance normally consists of overhaul, recondition,
6
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
manufacture, repair, or modification and requires technical assistance beyond lower maintenance level
capability.
3.2.20 Digital graphics forms. A standard graphics form acceptable for graphics preparation in accordance
with graphic standards listed in 6.1. These forms include CGM, CALS raster, and Initial Graphics
Exchange Specification (IGES).
3.2.21 Direct image copy (DIC). One-on-one reproducible without paste-overs or mortises, suitable for use
on a copier or making direct image masters. Quality should be such that if a negative were to be prepared,
only the imperfection due to the quality of photolithographic film would require touch up before making the
offset plates.
3.2.22 Disassemble. The step-by-step taking apart (or breakdown) of an assembly or subassembly to the
lowest level of its parts identification as maintenance-significant (i.e., assigned a Source, Maintenance and
Recoverability (SM&R) code for the category of maintenance under consideration).
3.2.23 Document Type Definition (DTD). The definition of the markup rules for a given class of documents.
A DTD or reference to one should be contained in any SGML-conforming document.
3.2.24 Electronic Display System (EDS). An electronic device on which display images can be represented;
most often a CRT or a liquid-crystal device.
3.2.25 Electronic Technical Manual (ETM). For the purpose of this handbook, an ETM is a technical
manual normally prepared from a linear SGML document file and not a hierarchically-based database as an
IETM. The ETM is also displayed on an EDS as a scrollable, linear structured document and may employ
a combination of an automated intelligent index, prompted dialog boxes, and content-driven logical
"NEXT" functions.
3.2.26 Footer. One or more lines of text that appear at the bottom of each page (also called feet and running
feet).
3.2.27 Formatting Output Specification Instance (FOSI). The FOSI interprets the style and formatting
requirements of the Output Specification (OS). The FOSI can include font, leading, hyphenation
characteristics, etc.
3.2.28 Frame-based Interactive Electronic Technical Manual (IETM). An IETM which has been designed to
be displayed frame by frame.
3.2.29 Functional diagram. A type of illustration in which symbols are connected by lines to show
relationships among the symbols. The symbols may be rectangles or other shapes, standard electronic
symbols representing components or functions, or pictorials representing equipment or components.
Where appropriate, voltage readings are shown. The lines may represent procedures or processes, such as
signal or logic flow, and physical items, such as wires. Functional diagram includes schematics, wiring
and piping diagrams, logic diagrams, flow charts, and block diagrams.
3.2.30 Graphic(s). Any type of presentation or representation which gives a clear visual impression.
3.2.31 Halftones. Halftones are the tonal values of gray and black created by lines or dots. A halftone is a
conversion of a continuous tone print.
7
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.32 Header. One or more lines of standard text that appear at the top of each page (also called heads and
running heads).
3.2.33 Horizontal (Landscape) TM format. Positioning of technical manual content so that the page
horizontal (width) dimensions are greater than vertical (height) dimensions.
3.2.34 Hotspot. An area of the display which acts as a hidden button. Touching the hotspot selects
designated information for display.
3.2.35 Icon. Pictorial representation; visual image to give immediate recognition of a hazard or to provide
essential information.
3.2.36 Illustration. A general term meaning graphic presentations of all types. Illustrations include
pictorials, functional diagrams, and line graphs. This term is used instead of such terms as figure, graphic,
drawing, diagram, and artwork.
3.2.37 Index numbers and letters. A number or letter (on a figure or an illustration) usually attached to a line
or an arrow which points to an object on the illustration. This number or letter corresponds to the same
number or letter in a legend or text that defines or identifies the object in the illustration.
3.2.38 Initial Graphics Exchange Specification (IGES). A standard digital form for vector graphics
preparation. Defined by MIL-PRF-28000.
3.2.39 Inspect. To determine the serviceability of an item by comparing its physical, mechanical, and/or
electrical characteristics with established standards through examination (e.g., by sight, sound, or feel).
3.2.40 Institute of Electrical and Electronics Engineers (IEEE). Membership organization that includes
engineers, scientists and students in electronics and allied fields. Founded in 1963, it has over 300,000
members and is involved with setting standards for computers and communications.
3.2.41 Interactive Electronic Technical Manual (IETM). An IETM is a technical manual, prepared
(authored) by a contractor and delivered to the Government or prepared by a Government activity, in digital
form on a suitable medium, by means of an automated authoring system; designed for electronic screen
display to an end user; and possessing the following three characteristics: (1) The format and style of the
presented information are optimized for screen presentation to assure maximum comprehension; that is, the
information presented is frame-oriented, not page-oriented; (2) The elements of technical information
constituting the IETM are so interrelated that a user's access to the information he/she requires is facilitated
to the greatest extent possible, and is achievable by a variety of paths; (3) The computer-controlled IETM
electronic display system (EDS) can function interactively (as a result of user request and information
input) in providing procedural guidance, navigational directions, and supplemental information; and also in
providing assistance in carrying out logistic support functions supplemental to maintenance.
3.2.42 Landscape mode. To print an image sideways on the page so that the longest edge of the form
corresponds to the horizontal axis.
3.2.43 Legend. A tabular listing and explanation of the numbers or symbols on a figure or an illustration.
3.2.44 Logic text. Text that is composed of procedures and actions branching to a series of questions,
8
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.45 Logistics Management Information (LMI). The selective application of scientific and engineering
efforts undertaken during the acquisition process, as part of the systems engineering process, to assist in
acquiring the required support; and providing the required support during the operational phase at
minimum cost. Replaces Logistics Support Analysis (LSA).
3.2.46 Logistics Support Analysis (LSA). The selective application of scientific and engineering efforts
undertaken during the acquisition process, as part of the systems engineering process, to assist in acquiring
the required support; and providing the required support during the operational phase at minimum cost.
3.2.47 Lubricant. Any solid, fluid, or semifluid material that performs a lubricating or related specialty
function. Such materials include lubricating oils, greases, hydraulic fluids, damping fluids, dielectric
coolants, anti-seize compounds, corrosion preventatives, and bonded or unbonded solid films.
3.2.48 Maintenance level. The separation of maintenance activities or functions in the U.S. Navy according
to the required skills and available facilities.
3.2.49 Maintenance step. A single maintenance action, such as setting a switch to the OFF position.
Usually, a step has one action, but in certain cases, there may be a series of identical actions, such as
removing seven bolts.
3.2.50 Marginal copy. Copy (generally headers and footers) placed outside that portion of the page used for
either text, full page tabular data, or full page illustrations, but within the printing area dimensions of the
page.
3.2.51 National Stock Number (NSN). A 13-digit number assigned to a repair part to be used for
requisitioning purposes.
3.2.52 Next Higher Assembly (NHA). Assembly or subassembly of which subject component(s) or
subassembly are a subpart.
3.2.53 Nomenclature. The approved name or alphanumeric identifier assigned to an item, equipment, or
component in agreement with an organized designation system.
3.2.54 Note. A statement or some other notification that adds, emphasizes, or clarifies essential information
of special importance or interest.
3.2.55 Orphan. Last line of a paragraph pushed to a new page, stranded alone (orphaned) at the top of the
page without the rest of its paragraph.
3.2.56 Overhaul. That maintenance effort (service/action) prescribed to restore an item to a completely
serviceable/operational condition as required by maintenance standards in appropriate technical
publications.
3.2.57 Part number (P/N). A primary number used to identify an item used by the manufacturer (individual,
company, firm, corporation, or Government activity) that controls the design, characteristics, and
production of the item by means of engineering drawings, specifications, and inspection requirements.
3.2.58 Phantom. Portraying an item (i.e., part, equipment, etc.) on an illustration with broken lines rather
9
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.59 Pictorial. A type of illustration showing the physical appearance of equipment or component parts.
This term is used instead of such general terms as illustration, drawing, and diagram.
3.2.60 Pre-screening. A process in which a clear material with a dot pattern or crossing opaque lines is used
through which an image is photographed in making a halftone.
3.2.61 Preventive maintenance (scheduled maintenance). The performance of scheduled inspections and
maintenance functions necessary to keep the equipment in serviceable condition and ready for its primary
mission.
3.2.62 Readability. Text comprehensibility measured by such variables as number of syllables, words, and
sentences.
3.2.63 Reference designator. Letters or numbers, or both, used to identify and locate discreet units, portions
thereof, and basic parts of a specific equipment, assembly, or subassembly.
3.2.64 Remove/install. To remove and install the same item when required to perform service or other
maintenance functions. Install may be the act of emplacing, seating, or fixing into position a spare, repair
part, or module (component or assembly) in a manner to allow the proper functioning of an equipment or
system.
3.2.65 Repair. The application of maintenance services (inspect, test, service, adjust, align, calibrate, and/or
replace), including fault location/troubleshooting, removal/installation, and disassembly/assembly
procedures, and maintenance actions to identify troubles and restore serviceability to an item by correcting
specific damage, fault, malfunction, or failure in a part, subassembly, module (component or assembly),
end item, or system. Repair is authorized by the LSA/LMI and the assigned maintenance level is shown as
the fourth position code of the SM&R code.
3.2.66 Repair part. Those support items that are an integral part of the end item or weapons system which
are coded as not repairable (i.e., consumable items).
3.2.67 Replace. To remove an unserviceable spare or repair part and install a serviceable counterpart in its
place. Replace is authorized by the LSA/LMI and the assigned maintenance level is shown as the third
position code of the SM&R code.
3.2.68 Requiring activity. The DoD component, activity, or organization of a using military service, or that
organization delegated by a using service, that is responsible for the selection and determination of
requirements for TMs.
3.2.69 Revision. A revision is comprised of corrected, updated or additional pages or work packages to the
current edition of a manual. It consists of replacement work packages that contain new or updated technical
information, or improves, clarifies or corrects existing information in the current edition of the manual.
3.2.70 Schematic diagram. A graphic representation showing the interrelationship of each component or
group of components in the equipment. The essential characteristic of these diagrams is that every
maintenance-significant functional component is separately represented. Also, where appropriate, voltage
readings are shown.
10
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.71 Scrollable. Ability to move a text or graphics display up and down, or left and right, or both.
3.2.72 Sentence. A group of words conveying a complete thought and terminated by a semicolon, period,
exclamation mark, or question mark. Headers, captions, and paragraph titles are not considered sentences.
3.2.73 Service. Operations required periodically to keep an item operating, i.e., to clean (includes
decontaminate, when required), to preserve, to drain, to paint, or to replenish fuel, lubricants, chemical
fluids, or gases.
3.2.74 Source, maintenance, and recoverability (SM&R) code. The five-position code containing
supply/requisitioning information, maintenance level authorization criteria, and disposition instruction.
The first two positions of the SM&R code determine how to get an item. The third position represents who
can install, replace, or use the item. The fourth position dictates who can do complete repair on the item.
The fifth position represents who determines disposition action on unserviceable items.
3.2.75 Spare part. Those support items that are an integral part of the end item or weapons system that are
coded as repairable (i.e., reparable items).
3.2.76 Standard Generalized Markup Language (SGML). A language for document representation that
formalizes markup and frees it of system and processing dependencies as defined in MIL-PRF-28001.
3.2.77 "Sticky". In reference to electronic tables, "sticky" infers that the title and column heads will be
continually displayed throughout the scrolling process of the entire table.
3.2.78 Subassembly. Two or more parts that form a portion of an assembly or a component replaceable as a
whole, but having a part or parts that are individually replaceable.
3.2.79 Task dialog. A pop-up display window by which the computer solicits user input, such as a selection
of choices.
3.2.80 Technical manuals (TMs). Documents that contain instructions for the installation, operation,
maintenance, and support of weapon systems, weapon system components, and support equipment. TM
information may be presented, according to prior agreement between the contractor and the Government, in
any form or characteristic, including hard printed copy, audio and visual displays, disks, other electronic
devices, or other media. They normally include operational and maintenance instructions, parts lists, and
related technical information or procedures exclusive of administrative procedures.
3.2.81 Test. To verify serviceability by measuring the mechanical, pneumatic, hydraulic, electrical, or
electronic characteristics of an item and comparing those characteristics with prescribed standards.
3.2.82 Text. The written parts of the technical sections excluding labels, legends, and callouts in
illustrations.
3.2.84 Verification. The final QA iteration by the Government for acceptance of the TM during
which a TM is tested to determine its adequacy and operational suitability for operation and maintenance of
equipment or systems using target audience personnel.
3.2.85 Vertical TM format. Positioning of technical manual so that the page horizontal (width) dimensions
11
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3.2.86 Warning. A statement or some other notification about an operating or maintenance procedure,
practice, or condition that, if not strictly observed, could result in long term health hazard, injury to, or
death of personnel performing the task prescribed in the TM.
3.2.87 Widow. First line of a paragraph that is left alone (widowed) at the bottom of a page.
3.2.88 Wiring diagram. Diagram illustrating signal flow or wiring connections. Where appropriate, voltage
readings should be shown.
3.2.89 Word. Any string of characters (including letters, numbers, symbols, and groups of letters) separated
from other strings by one or more spaces. Hyphenated words and contractions count as one word. For
example, each of the following count as one word: couldn't; GFE; i.e.; 32,008; 19-inch; +25oF; left-hand.
Thus a sentence like "The left-hand MLG door shouldn't open more than 25o." consists of 9 words.
3.2.90 Work packages (WPs). Presentation of information functionally divided into individual task packages
in the logical order of work sequence. These WPs should be stand-alone general information, descriptive,
theory, operating, maintenance, troubleshooting, parts, and supporting information units containing all
information required for directing task performance.
4.1 General. This section is intended to provide guidance and further clarify the requirements contained in
MIL-STD-3001-1 through MIL-STD-3001-8. The general style, format, and graphics guidance contained
herein are applicable for the preparation of the following types of page-based, technical manuals developed
to the work package (WP) concept.
12
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.2 Selective application and tailoring. This section contains guidance that may not be applicable for the
preparation of all TMs listed in 4.1. Selective application and tailoring of requirements are the
responsibility of the requiring activity and are accomplished using MIL-STD-3001-1 through MIL-STD-
3001-8. If an identifiable, written conflict exists between this section and the detailed content standard, the
detailed content standard takes precedence.
4.3 Preparation of TMs in digital format. Technical manuals prepared in work package format and delivered
digitally are Standard Generalized Markup Language (SGML) tagged and assembled using modular
Document Type Definitions (DTDs). These DTDs have been developed in accordance with MIL-PRF-
28001 and ISO 8879. The modular DTDs interpret the technical content and structure of the functional
requirements explained in MIL-STD-3001-1 through MIL-STD-3001-8 and this handbook.
4.4 Style and format for printed page-oriented TMs. Mandatory style and format requirements are provided
in MIL-STD-3001-1, Appendix B. The style and format guidance provided in this section is recommended
for use when acquiring TMs for the U.S. Navy. Formatting Output Specification Instances (FOSIs),
developed in accordance with MIL-PRF-28001, interpret the style and format requirements contained in
MIL-STD-3001-1 and this handbook. Style sheets developed by the TM developer may be used in lieu of
FOSIs for printing paper manuals.
4.5 Obtaining the modular DTDs/FOSIs. Information on using and obtaining the DTDs, FOSIs and
associated tag and attribute descriptions, which are SGML constructs, can be obtained from the requiring
activity.
4.6 Figures contained in this handbook. The work package examples (figures 1 through 44) show the style
and format requirements and subject matter contained in various types of WPs for page-based TMs. In an
attempt to minimize the size of this handbook, most of the technical content provided in the examples are in
abbreviated form and some figures referenced in the text of the example WPs have purposely been omitted.
The font size, leading and vertical spacing of the text for the examples have been intentionally compressed
to allow the data to fit within the boxed image area on the page. Appendix A of this handbook provides
examples of style and format requirements for the different types of specific graphics used in the
development of TMs.
4.7 Development of work package technical manuals. The style and format guidance provided in this section
has been established to facilitate the development of technical information for the page-based WP concept.
The WP concept is defined as a logical combination of requirements and improved presentation techniques
designed to enhance digital display of page-formatted pages. A WP technical manual is specifically
designed to support individual functional information or maintenance work tasks for a weapon system or
equipment. WP requirements are provided in MIL-STD-3001-1 through MIL-STD-3001-6. Periodic
maintenance requirements card decks are prepared on reduced sized card stock because of their frequent use
and for portability. Work package requirements are not used in the preparation of these card decks.
Technical content, and style and format for all card decks are contained in MIL-STD-3001-7. MIL-STD-
13
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3001-8 establishes the content requirements for separate printed, page-based IPBs.
4.7.1 Types of work packages. There are basically two types of work packages. The first type is an
information-oriented work package. (Refer to figure 1.) It provides support information such as general
information about the TM or weapon system/equipment, principles of operation, and operating instructions.
The second type of WP is task-oriented. (Refer to figure 2.) Task-oriented WPs reflect all required
maintenance tasks at the assigned level of maintenance, and environment, material, and support equipment
required for each defined task. WPs are written to reflect the engineering design, Logistics Support
Analysis (LSA), Logistics Information Management (LMI), approved maintenance plan, and the
established repair concept (Source, Maintenance and Recoverability (SM&R) Codes).
4.7.2 Technical manuals developed in accordance with MIL-STD-3001 series standards. This section may
be used in conjunction with the series of standards listed below to develop page-oriented WP technical
manuals for aircraft weapon systems, engines, aeronautical equipment, airborne weapons/equipment, and
support equipment. MIL-STD-3001-1 through MIL-STD-3001-8 contain the technical content and
mandatory style and format requirements for the preparation of technical manuals at all maintenance levels
through depot. Each of these Parts provides instructions on how to develop and structure the required
technical information into individual work packages in a logical order of work sequence.
4.7.3 Preparation of digital technical information for multi-output presentation of technical manuals (MIL-
STD-3001-1). This Part establishes the requirements needed to prepare and assemble digital technical
information for multi-output presentation of NAVAIR work package technical manuals (TMs). It contains
the following requirements and data:
b. General requirements and types of technical manuals covered by the series of standards.
c. Matrixes that provide the technical content requirements for all technical manuals covered in the
series of standards.
14
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
e. Front matter and introductory information used to develop and assemble complete TMs.
Author’s Note: Front matter consists of a title page, numerical index of effective work
packages/pages, Technical Publication Deficiency Reports (TPDR) page, Hazardous Materials
Warning Summary (HMWS) page, and an alphabetical index. Introductory information includes
WPs for a numerical index of part numbers, numerical index of reference designations, and
introductions for specific types of TMs and periodic maintenance requirements card decks. Also
considered introductory information is a WP for consolidated lists of technical directives, support
equipment, material, and references and an engine maintenance allocation WP.
4.7.4 Description, principles of operation, and operation data (MIL-STD-3001-2). This Part contains
technical requirements necessary to develop description, principles of operation, and operation data for
aircraft weapon systems, engines, aeronautical equipment, airborne weapons/equipment, and support
equipment. The information is divided into the following specific types of work packages, as applicable to
the weapon system/equipment:
Author’s Note: The above work packages are required when preparing a General Aircraft Information
manual, a Plane Captain’s manual or a Line Maintenance manual for an aircraft weapons system.
Author’s Note: Figures 3 through 5 provide examples of the technical content structure and
preferred style and format for several of the different types of the aircraft description WPs listed
above. The general structure, style and format provided in the examples can be used as an example to
facilitate the development of all the WPs listed above.
b. Aircraft system, subsystem, and component description WPs (see figure 6).
15
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author’s Note: Figure 10 provides an example of a principles of operation WP for an item of support
equipment. The general structure, style and format provided in the example can be used to facilitate
the development of description WPs for all types of aeronautical equipment, airborne
weapons/equipment, engines and engine systems, and other types of support equipment.
Authors Note: All principles of operation WPs may include descriptive data for better clarity or to
facilitate ease of use. When description and principles of operation are provided in the same WP,
separate WPs for descriptive data (b. through d. above) are not required.
4.7.5 Testing and troubleshooting procedures (MIL-STD-3001-3). This Part contains technical
requirements necessary to develop testing and troubleshooting procedures for aircraft weapon systems,
engines, aeronautical equipment, airborne weapons/equipment, and support equipment. The information is
divided into the following specific types of work packages, as applicable to the weapon system/equipment:
Maintenance code listing (for Fault Reporting Manuals only) (see figure 13).
Fault indications (for Fault Reporting Manuals only) (see figure 14) .
Fault descriptor (for Fault Reporting Manuals only) (see figure 15).
Symbology (for Fault Reporting Manuals only) (see figure 16).
Fault isolation troubleshooting procedures (for Fault Isolation Manuals only) (see figure 17).
Operational checkout (see figure 18).
Troubleshooting procedures.
16
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author’s Note: The structure, style and format of testing and troubleshooting procedures provided in
figures 18 through 21 can also be applied when developing test and troubleshooting procedures WPs
for all types of aeronautical equipment, airborne weapons/equipment and support equipment.
4.7.6 Maintenance information with illustrated parts breakdown (MIL-STD-3001-4). This Part establishes
the technical content requirements for the preparation of maintenance information with illustrated parts
breakdown (IPB) for aircraft weapon systems, engines, aeronautical equipment, airborne
weapons/equipment, and support equipment. The maintenance information is divided into the following
specific types of work packages, as applicable to the weapon system/equipment:
a. Maintenance WPs.
Author’s Note: These task-oriented maintenance work packages contain all authorized maintenance
tasks, such as remove, inspect, service, test, install, replace, disassemble, assemble, repair, clean,
adjust, align, etc., for the overall equipment and each maintainable system, subsystem, assembly, and
component. An Illustrated Parts Breakdown (IPB) should be included for all maintenance tasks that
require parts replacement. An example of a maintenance with IPB WP is shown in figure 2. This
example can be used as a guide to develop maintenance WPs for aircraft weapon systems, engines,
aeronautical equipment, airborne weapons/equipment, and support equipment.
Author’s Note: This support equipment WP is specifically used to provide maintenance procedures for
support equipment that is not covered in separate support equipment maintenance manuals.
Instructions for required fabrication of peculiar tools, when such fabrication is approved by the
requiring activity, should be included.
Author’s Note: This local manufacturing and assembly WP is specifically used to provide fabrication
procedures for items source coded as "Make From" or "Assemble From" items.
g. Preinduction and mandatory inspection WP (engines only) (see MIL-STD-3001-4 for an example).
h. External tubing, cabling and clamping WPs (engines only) (see MIL-STD-3001-4 for an example):
Numerical index.
Bracket installation.
External components.
Tubing, cabling and clamping installation.
Critical clearances.
17
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author’s Note: An engine SCC is only required when the requiring activity requests that it be
developed. The content and format for an SCC is not covered by the modular DTD for Maintenance
Information with IPB. See figure 27 for an example.
4.7.7 Aircraft wiring information (MIL-STD-3001-5). This Part establishes the technical content
requirements for the preparation of wiring information for an aircraft and its systems, subsystems, and
equipment. The wiring information is divided into the following specific types of work packages, as
applicable to the weapon system/equipment:
Author’s Note: An aircraft wiring diagram manual, an aircraft wire bundle manual, and an aircraft
wiring connector repair manual should be developed for every aircraft weapon system. The WPs
required for each of these TMs are listed below.
Author’s Note: Title block, reference material lists, record of applicable technical directives, support
equipment required lists, and materials required lists (refer to 4.7.3) are not required for individual
wiring diagram work packages. A reference material list, record of applicable technical directives,
support equipment required list, and materials required list should be included in the introductory
information in the front of the aircraft wiring diagram manual.
Wiring system bundle assembly identification and information (see MIL-STD-3001-5 for an
example).
Access information (see MIL-STD-3001-5 for an example).
Wire bundle assembly routing and parts data (see MIL-STD-3001-5 for an example).
Author’s Note: Unless otherwise noted below, WP examples are provided in NAVAIR 00-25-701.
4.7.7.1 Wiring information for engines, aeronautical equipment, airborne weapons/equipment, and support
equipment. Required wiring information for engines, aeronautical equipment, airborne weapons/equipment,
and support equipment is the same as for the aircraft wiring diagram WPs described in 4.7.7 a. When
18
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
developing separate TMs for engines, aeronautical equipment, airborne weapons/equipment, and support
equipment, this information, however, can be included as separate WPs or be included in other types of WPs
as supporting data (e.g., as part of a testing or troubleshooting WP).
4.7.8 Structural repair information (MIL-STD-3001-6). This Part establishes the technical content
requirements for the preparation of information for the repair, corrosion control, and nondestructive
inspection (NDI) of aircraft structure and structural components at all levels of maintenance. An Illustrated
Parts Breakdown (IPB) should be included for all maintenance tasks that require parts identification and
replacement. The structural repair information is divided into the following specific types of work packages,
as applicable to the weapon system/equipment.
Author’s Note: An example of a typical corrosion control repair WP is shown in figure 31. Even
though the content will vary based on the technical content requirements provided in MIL-STD-3001-6,
the example is typical and can be used as a guide for the structure and format presentation of all the
corrosion control WPs listed above.
Author’s Note: An Illustrated Parts Breakdown (IPB) should be included for all maintenance tasks
that require parts replacement.. An example of an IPB for structural, corrosion, and NDI repair
procedures is provided in MIL-STD-3001-6.
4.7.9 Periodic maintenance requirements (MIL-STD-3001-7). This Part establishes the technical content
requirements for the preparation of periodic maintenance inspection requirements for aircraft weapon
systems, quick engine change assemblies, powered aerial targets (missiles), support equipment, automatic
19
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
test equipment, airborne armament equipment or special stores, powered surface targets, and aviation life
support systems.
4.7.9.1 Periodic maintenance card sets. Periodic maintenance requirements consist of a series of scheduled
maintenance requirements that provide a basis for planning, scheduling, and execution of scheduled
maintenance. The requirements should be developed to provide general and specific instructions required to
perform scheduled maintenance at the organizational and intermediate maintenance levels. Periodic
maintenance requirements are contained and subdivided into a series of periodic maintenance card sets due to
their frequency of use and to facilitate ease of use on the flight line and other maintenance environments.
Periodic maintenance requirements card sets are divided into specific types of card decks for the weapon
system and types of equipment/systems listed below.
Author’s Note: Because periodic maintenance data are contained on 5-inch by 8-inch card stock, the
work package concept required by this handbook does not apply. Refer to MIL-STD-3001-7 for
additional content and format requirements for individual card sets.
a. Aircraft.
4.7.10 Illustrated parts breakdown (IPB) requirements (MIL-STD-3001-8). This Part establishes the
technical content requirements for the preparation of separate page-based IPBs for printing paper TMs or
for viewing page-based TMs on an EDS. This Part also provides the requirements needed to develop a
complete IPB including the front matter, alphabetical index, and numerical indexes of part numbers and
reference designations.
Author’s Note: IPB requirements for the development of separate page-based IPBs for paper output
have been included in MIL-STD-3001 to permit developers of revisions to legacy IPBs to use this
standard. For all new TM programs, IPBs should be included as part of the maintenance WPs (see
MIL-STD-3001-4). The requiring activity should be consulted before developing separate paged-based
IPBs.
4.8 How to develop and assemble a work package TM. The following general process should be followed
when requiring weapon system/equipment work package TMs.
a. Review contractual requirements and establish specific content requirements for each TM using the
20
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. Develop a detailed TM outline (refer to 4.8.1) for each TM, using the filled-out TM content
selection matrixes as a guide.
d. Develop an SGML-tagged source file (refer to figure 36) for each WP using the applicable modular
DTD.
e. Using the assembly DTD (refer to MIL-STD-3001-1), develop the required front matter and
applicable introductory information.
f. Using the assembly DTD, assemble the front, introductory, and all the technical content WP source
files developed for the specific TM into a complete TM. The applicable TM content selection matrix or
TM outline should be used as a guide.
4.8.1 Creating an outline. Basic outline development principles are controlled and identified in MIL-STD-
3001-1 through MIL-STD-3001-8. These standards divide manuals by functional information. Work
package manual information alignment must be specifically tailored to the maintenance requirements of the
individual weapon system, related systems, and components within the system or related equipment.
Source information such as engineering design, LSA/LMI, or the approved maintenance plan is used to
define and organize each function and task in their appropriate order of sequence in the applicable TM.
The review of all available source information should result in the identification of the following:
a. A complete, properly sequenced listing of every maintenance task required for product support.
b. Identification of testing and troubleshooting requirements, their points of observation, and their
method of accomplishment.
g. The rating requirements, skill levels and number of personnel required for task performance.
The task identification phase of technical manual development constitutes the identification and recording of
all descriptive data and operating and maintenance tasks necessary to accomplish maintenance on a given end
item. Once the task identification phase is complete, the manual developer can begin to develop the required
number of outlines for the weapon system, related systems, and components within the system or related
equipment.
4.8.1.1 Outline development. The development of the outline begins by identifying the appropriate technical
21
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
manual breakdown. This can be facilitated by using the technical manual content matrixes provided in MIL-
STD-3001-1, Appendix A.
Author’s Note: The technical manual breakdown list can be affected by system design complexity and
the volume of information required for complete coverage. MIL-STD-3001-1, in the interest of usability,
indicates a bulk restriction to printed manuals. This must be taken into consideration when preparing
the proposed list of TMs.
Once all individual technical manuals are identified by type, name, and maintenance level, an outline is
prepared for each TM identified. Outline development consists of breaking down the applicable system,
equipment or component TM into its smallest repairable unit and as dictated by the LSA/LMI or approved
maintenance plan. The required descriptive data, and operating and maintenance tasks are divided into WPs
and assigned WP numbers. The final outline should reflect the proper depth and scope of each manual as
defined.
4.8.1.2 Identifying work packages. The WP concept is based on simplified presentations by grouping
descriptive information or work actions into individual task packages of 30-50 pages or less. However, one of
the advantages to WP presentation is its flexibility. In some situations, too little information per unit could be
as detrimental as excessive data.
a. For example, when covering a simple system or component, it may be more beneficial and
informative to provide testing and troubleshooting as primary headings within a WP.
b. A similar situation may apply to related maintenance tasks. On occasion it would be more effective to
present a series of similar or related tasks (remove/install) in a single WP rather than a number of redundant
individual WPs.
c. For more complex coverage (greater volume), the philosophy could change to development of
principles of operation, testing, troubleshooting, introduction and maintenance tasks (with IPB) into
individual stand-alone WPs.
d. Note that the degree of flexibility has exceptional latitude. For example, troubleshooting coverage
under the WP concept could appear as a series of paragraphs within a WP, as one or more individual WPs
within a manual or, if necessary, as a separate troubleshooting manual.
4.8.2 How to develop work packages. The requiring activity must apply the requirement of weapon systems,
equipment or component engineering design to the development of the technical manuals. The guidelines
set forth in the approved LSA/LMI or maintenance plan dictate the technical content of the WP manuals.
The TM developer working with the requiring activity and using the TM content selection matrixes
provided in MIL-STD-3001-1, Appendix A, should develop TM outlines for each proposed TM. Using the
filled out TM content selection matrixes as a guide, develop an outline (refer to 4.8.1) that will reflect the
arrangement and alignment of the required technical information into the required volumes and WPs.
4.8.2.1 Development of individual work packages. Ideally, each WP in a manual will be an independent,
stand-alone data unit. The author will be required to group some information or maintenance tasks in one
work package and divide others into several WPs of suitable length. Division or selection of coverage will
depend on various factors. These factors may include but are not limited to:
22
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. A specific work package that is required by the TM content selection matrix or TM outline
approved by the requiring activity.
Author’s Note: An 'R' included for a specific WP requirement contained in the TM content selection
matrix (refer to figure 35) denotes that a WP or a WP requirement is mandatory and must be included
in the TM. An 'O' included for a specific WP requirement contained in the TM content selection
matrix denotes that a WP or a WP requirement is optional and should be included if applicable to the
subject weapon system or equipment.
Author’s Note: Separate maintenance WPs may be developed for the same equipment or component
for different maintenance levels (e.g., a WP for organizational maintenance and a WP for
intermediate maintenance for the same item of equipment).
d. Two or more WPs for an identical maintenance task may be required because the task is performed
differently due to differences in configurations.
e. More than one WP may be required because the size of the work package will exceed 30-50 pages.
Author’s Note: It is permissible to divide a set of maintenance tasks for a specific system, equipment
or component into two or more WPs to comply with the page size limitation (e.g., removal and
installation procedures could be placed in one WP and disassembly, cleaning, repair, and reassembly
could be placed in a second WP).
f. Development of more than one WP because the reduction in the size of the work package would
make it more useable.
g. Confining the information to one WP because dividing the information into several work packages
would degrade the usability.
Author’s Note: For example, splitting a disassembly procedure into two separate WPs would degrade
the usability of the maintenance procedure.
h. The use of separate WPs for a series of maintenance tasks for a repairable component due to the
use of different support equipment, materials required, etc.
Author’s Note: If the support equipment, tools, or materials used to perform removal and installation
are very different than the support equipment, tools, or materials used to perform disassembly and
reassembly for the same system or component, it may be better to separate this information into two
WPs.
4.8.3 Development of an SGML source file. Once an outline is prepared and all the work packages have
been identified, an SGML source file (document instance) should be developed for each WP. (Refer to
figure 36.) The SGML-tagged source file is composed of SGML-coded ASCII (American Standard Code
for Information Interchange), marked up (tagged) in accordance with the applicable modular DTD,
including the identification of the supporting graphics required. In order to tag WP text appropriately, the
author inserting the tags must be familiar with the DTD or must provide the text file to a person who is
experienced with the DTD and who understands the type of documentation being written, especially when
23
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
content tags are used. A customized template modeled for the applicable DTD may be available or
developed to assist the author in creating the document instance.
Author’s Note: A template can be implemented in a text editor, a WYSIWYG (What You See Is What
You Get) editor, a database input form, or an SGML authoring/composition system.
4.8.4 Printing the TM using the FOSI. The FOSI specifies the desired appearance of the content of the
document instances. Document formatting requirements such as page layout and hyphenation rules are
specified in the FOSI, as well as how document elements such as paragraph titles, tables, and lists are to be
formatted. The FOSI provides the composition and imaging characteristics to be applied to the SGML
tagging (including attributes) of an SGML-tagged text source file (document instance) to present the text
material in paginated or screen presentation form. The use of a FOSI is not mandatory.
4.8.5 Printing the TM using a style sheet. A style sheet may be used in lieu of a FOSI to specify the desired
appearance of the information content of the document instance. The style sheet provides the same
formatting requirements to an authoring/composition system as does a FOSI.
4.9 Format.
4.9.1 General. The format contained in this section has been included to expand, emphasize, and clarify the
requirements provided in MIL-STD-3001-1 through MIL-STD-3001-8. To avoid unnecessary repetition
and to provide the user of this handbook with a more useable document, requirements contained in MIL-
STD-3001-1 through MIL-STD-3001-8 that are self explanatory or can only be interpreted in one way
have been omitted from this handbook.
4.9.2 Major divisions. The hierarchical breakdown of a TM is: volumes (if required) and work packages
(WP). Each division used should have at least two occurrences (for example, where there is a Volume 1,
there should be a Volume 2).
4.9.3 Work packages. Work packages (WPs) are used to logically divide all data required for a certain
function (i.e., descriptive information, operator’s instructions, maintenance with IPB, troubleshooting, etc.).
Procedural maintenance tasks or descriptive information contained in a WP consists of a series of
paragraphs and procedural steps. When it is necessary to divide a maintenance task into subtasks, for
clarity subparagraph titles may be used. Refer to paragraph 4.9.4.
4.9.3.1 Work package numbering system. Each WP should be assigned a permanent number as required by
MIL-STD-3001-1. The WP number should be considered permanent upon distribution of the basic issue of
the manual and should not change until WPs are renumbered for a complete revision. The WP number should
be placed on each page of the WP in the extreme upper right corner of the reproduction area.
4.9.3.1.1 WP number assignment. Each WP number should be a five-digit number, beginning with the
number 001 00. There should be one blank space between the third and fourth digit. The basic WP number
is identified by the first three digits of the WP number. The last two digits can be used to add work packages
that reflect related coverage for the same basic descriptive information or operational or maintenance task
when there is a permanent configuration difference, different support equipment, or preferred and alternate
procedures required. Normally, "00" should be assigned as the last two digits of the WP, indicating all
required coverage for the WP subject (task) has been included. If additional work packages are required to
provide permanent configuration differences, different support equipment, or preferred and alternate
procedures for the same subject contained in the "00" WP, the additional WPs should be assigned an "01,"
"02," "03," etc.
24
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.9.3.1.1.1 WP numbers for front and introductory matter. WP numbers 001 00 and WP 002 00 are always
used for front and introductory information for the applicable technical manual. The last two digits are used
for specific types of front and introductory information as described below.
a. Alphabetical Index WP. The alphabetical index WP should be the first WP in the manual and should
be assigned WP number 001 00.
b. Numerical Index of Part Numbers WP. The Numerical Index of Part Numbers WP should be
assigned WP number 001 01.
c. Numerical Index of Reference Designations WP. The Numerical Index of Reference Designations
WP should be assigned WP number 001 02.
4.9.3.1.1.2 WP number for technical publication deficiency reports (TPDR) page. The TPDR page should
be assigned WP number TPDR-1, TPDR-2, etc.
4.9.3.1.1.3 WP number for hazardous material warning sheets (HMWS). The HMWS should be assigned
WP number HMWS-1, HMWS-2, etc.
4.9.3.1.1.4 WP numbers for introductory matter. The Introduction WP should be assigned WP number 002
00.
4.9.3.1.1.5 WP numbers for technical content. The technical content WPs should be assigned in numeral
sequence starting with the WP number 003 00 and continue through the WP number 999 00.
4.9.3.1.1.6 Assignment of the last two digits (basic WP number suffix). The Index WPs are normally the
only exceptions to the assignment of the last two digits of the WP number in the basic issue of the manual.
However, when the basic issue of a manual requires two or more WPs for proper coverage of the same basic
task, assignment of the last two digits is authorized (e.g., permanent configuration difference, different
support equipment, or preferred and alternate procedures). The last two digits of the WP are also used to
permit expansion of the manual to incorporate changed or new configuration data without affecting the WP
numbers previously assigned.
4.9.3.1.1.7 Reserved WP numbers. WP numbers may be reserved for future use for expansion purposes,
provided that the numbers reserved are not titled and are accounted for and marked "Reserved" in the
numerical index of effective work packages. If a WP number has been assigned a title and technical content
is not available at the time of distribution, the deficiency should be noted in the numerical index of effective
work packages by the statement "To Be Provided."
4.9.3.1.1.8 Deleted WP numbers. WPs deleted by a pickup revision should be accounted for and marked
"Deleted" in the numerical index of effective work packages. For complete revisions, WPs will be
renumbered and assigned new WP sequence numbers in consecutive order.
4.9.3.1.1.9 Work package numbers - division into volumes. When an existing manual is divided into
volumes, the previously assigned WP numbers should not be reassigned or renumbered. The first volume
should contain the front matter, including a comprehensive index for all volumes, and as many WPs as
appropriate beginning with WP 001 00. The second and subsequent volumes should contain a
comprehensive alphabetical index for the volume and the WPs contained in the volume.
25
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.9.4 Paragraphs.
b. Paragraphs and subparagraphs within a work package may have titles. If titled, the title should
begin at the left margin.
(1) A first level paragraph title stands alone and is in all capital letters.
(2) A second level paragraph title is run-in and is in all capital letters.
(3) A third level paragraph title stands alone and has the first letter of the first word and of each
principle word capitalized.
(4) A forth level paragraph title is run-in and has the first letter of the first word and of each
principle word capitalized.
(5) Paragraph text after stand-alone paragraph titles begins flush left.
Author’s Note: If additional titles levels are necessary over and above the four levels, unbolded upper
case stand-alone and unbolded upper case run-in capital letters should be used. No more than 6
levels should be used.
4.9.5 Procedural steps. Procedural steps present detailed, step-by-step instructions for performing an
operational or maintenance task - such as turning on a test set; changing oil; replacing a part; repairing an
assembly; or inspecting, cleaning, or removing an item of equipment, etc. Procedural steps are presented in
a logical sequence and reflect the sequence in which the tasks are actually performed. Procedural steps and
substeps are numbered consecutively with Arabic numerals or lower case letters. Procedural steps are
placed immediately after paragraph or subparagraph titles, or, if applicable, after a small paragraph that
introduces the procedural steps as shown by the examples below:
"1-1 REMOVAL
1-2 The procedure below is typical for the left or right MLG uplock switch (6, figure 1) except as noted.
4. Remove clamp (1) and attaching parts from switch (6) wires being removed.
5. In MLG wheelwell and access door 47, perform the substeps below:
26
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
OR
"1-1 REMOVAL
3. Remove SENSOR SELECT knob (5) from SENSOR SELECT shaft (6)."
4.9.5.1 Procedural step levels. Procedural steps may be, when required, divided into no more than six levels.
Author’s Note: The following demonstrates, by example, how procedural steps and substeps levels
are formatted and numbered.
EXAMPLE
1. Primary procedural step numbers (1, 2, 3, etc.) are flush left. Text begins two spaces after the period
following the numeral. The text is blocked.
a. The first-level procedural substep step letters (a, b, c, etc.) are immediately below the text of the first-
level procedural steps. Titles are not allowed. The text is blocked.
(1) The second-level procedural substep step numbers ((1), (2), (3), etc.) are immediately below the
text of first-level procedural substeps. Titles are not allowed. The text is blocked.
(a) The third-level procedural substep step letters ((a), (b), (c), etc.) are immediately below the
text of second-level procedural substeps. Titles are not allowed. The text is blocked.
1 The fourth-level procedural substep step numbers (1, 2, 3, etc.) are immediately below
the text of third-level procedural substeps. Titles are not allowed. The text is blocked.
a. The fifth-level procedural substep step letters (a, b, c, etc.) are immediately below
the text of fourth-level procedural substeps. Titles are not allowed. The text is
blocked.
Author's Note: If additional substep letters are required, use aa, ab, etc., after z, or (aa), (ab), etc.,
after (z), or aa, ab, etc., after z.
a. Tables are inserted in the TM on the same page or as soon after the first reference in the text as
possible.
27
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. Full-page tables using a horizontal (landscape) format are positioned so that the page must be
rotated 90 degrees clockwise to be read. The table number and title are placed at the top of the table.
4.9.6.2 Table numbering. Tables are numbered consecutively within each WP in the order of their reference
starting with Arabic number 1. If only one table is referenced in a WP, it is numbered. Tables that are not
referenced except from an adjacent paragraph and are one column in width should not be numbered. Tables
that are referenced in two or more paragraphs and tables that are full page width should be numbered.
4.9.6.3 Table titles. Each table has a title. The titles identify the contents or purpose of the table and
distinguish that table from others in the TM.
a. The table title consists of the word "Table" followed by the table number, a period, two spaces, and
the title. Capitalize the first letter of the first and each major word of the title.
b. Center table titles above the table. If the title is too long to fit on one line, align the second line with
the first letter of the title.
c. Identify tables applicable to one Service only in a joint service TM. (For example, Table 3. Fuel
Indicator Correction Factors (Navy Only).)
d. Identify tables applicable to more than one service in a joint service TM. (For example, Table 1.
UHF Radio Controls (Navy and Air Force Only).)
4.9.6.4 Table format. Certain required tables in MIL-STD-3001-1 through MIL-STD-3001-8 are referred to
as "standard tables." Tables designated as standard have no deviations to the number of columns and the
titles in the column headings. The format and table headings are automatically generated by the applicable
modular DTD and FOSI or style sheet used for the functional information. The following applies to all
nonstandard tables developed for a TM.
a. Place a horizontal rule at the beginning (head) and at the end (foot) of a table. Title columns
appropriately in boldface, upper case letters. Place a horizontal rule under the column titles. All tables have
outside vertical rules and, if required for clarity, vertical rules between columns.
b. When a table is continued on more than one page, the table number and title is repeated followed by
the notation "Cont" in parentheses. The closing rule is omitted at the foot of a continued table; the opening
rule is continued at the head of the continued portion along with the heading title data.
d. Align data within one column of a table by one method only, i.e., left justified, left justified with
substeps indented, centered, etc. However, different columns within the same table may be presented
differently, i.e., one column may have the data left justified while another column may have the data
centered.
e. Tables may contain procedural steps and substeps, with a maximum of four levels (i.e., (a), (b),
etc.). Number steps in accordance with 4.9.5.1. When space allows, indent the substeps two spaces.
4.9.6.5 Footnotes to tables. Footnotes in tables should not be used. Notes may be placed in tables, but not
28
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
at the bottom of a page, deliberately separated from the applicable table to which they apply.
a. There should be a clear space between columns. Row entries in tables may also be arranged in
groups separated with clear space.
(4) Alphabetic or alphanumeric data may be aligned flush left, flush right, or centered. Data may
also be indented.
c. Units of measure are identified in appropriate row entries or as separate column headings.
d. The user will not be required to interpolate (estimate between tabled values). Avoid interpolation
by expanding the table or by presenting the data in a graph.
4.9.7 Lists. Lists may be used in lieu of tables, when appropriate. Three types of lists are identified below.
Lists may be unnumbered, numbered sequentially, or lettered alphabetically. They may have an optional
title in all upper case bold letters. (Refer to figure 37.)
a. Definition list. The definition list consists of the term and the definition. It may have the headers,
"Term" and "Definition" above the appropriate sections of the list. Refer to MIL-PRF-28001 for more
information on the development of lists.
b. Random list. The random list consists of one or more items in a random order.
c. Sequential list. The sequential list consists of one or more items in a specified order, such as
alphabetic, numeric, or alphanumeric.
4.9.7.1 Wire list. Two types of wire lists are used to support maintenance and on-aircraft troubleshooting of
aircraft wiring systems. The first type is a wire run list. The second type is a wiring reference designation
list. Detailed content requirements are provided in MIL-STD-3001-5. For aircraft systems wiring TMs, the
lists are not used in lieu of wiring diagrams but are used to supplement the information provided on wiring
diagrams. For aeronautical equipment, airborne weapons/equipment, and support equipment TMs, these
lists may be used in lieu of preparing wiring diagrams, when authorized by the requiring activity.
4.9.7.1.1 Aircraft wire run list. The aircraft wire run list should contain the technical content information as
required by MIL-STD-3001-5 and include a list of all wires for the aircraft systems, subsystems, and
equipment (refer to figure 38). Wires should be listed in alphanumeric sequence by system wire number.
4.9.7.1.2 Wiring reference designation list. The wiring reference designation list work package should
contain a list of all wiring component reference designations and pin numbers (refer to figure 39).
29
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.9.7.1.3 Wire run list for aeronautical equipment, airborne weapons/equipment, and support equipment. For
these types of equipment manuals, wire run lists can be used in lieu of wiring diagrams when approved by the
requiring activity. Wire run lists are usually computer generated and are being used more and more by
contractors. Formats may vary; however, the content information shown in figure 40 should be included.
4.9.7.1.4 Placement of wire run lists. Wire lists should be contained in work packages. Aircraft wire run list
work packages should be placed in a separate aircraft system wiring diagram manual immediately following
the aircraft systems wiring diagrams. Aircraft reference designation list work packages should immediately
follow the aircraft wire run lists. When wire run list work packages are developed for other types of
equipment maintenance manuals, they should be placed where appropriate for maximum usability.
4.9.7.2 List format. Certain required lists in MIL-STD-3001-1 through MIL-STD-3001-7 are referred to as
"standard lists." Lists designated as standard have no deviations to the number of columns and the titles in
the column headings. The format and list headings are automatically generated by the applicable modular
DTD and FOSI or style sheet used for the functional information.
4.9.8 Figures/illustrations.
4.9.8.1 Figure numbering. Figures, with the exception of foldouts, are numbered consecutively within each
WP in the order of their reference starting with Arabic number 1. If only one figure is referenced in a WP, it
is numbered. Foldouts are placed at the end of each work package; therefore, foldout figure numbers should
start with the next number after the last standard size illustration figure number in the WP.
a. Illustrations should be assigned a figure title. The figure title should follow the figure number.
"Figure" is in upper and lower case, followed by the figure number, a period, two spaces, and the title.
Capitalize the first letter of the first and each major word of the title. Center figure titles on the graphic image
area below the graphic and begin the title on the same line with the figure number.
b. If the title of the figure is too long to fit on one line, align the second line with the first letter of the
title.
c. Identify illustrations applicable to one Service in a joint service TM. (For example, Figure 3. Fuel
Indicator (Navy Only).)
d. Identify illustrations applicable to more than one Service in a joint service TM. (For example, Figure
3. Fuel Indicator (Navy and Air Force Only).)
e. Each sheet of a multi-sheet illustration should be identified by a sheet number following the figure
number and title (e.g., Sheet 1, Sheet 2, etc.).
4.9.8.3 Legends. Legends are part of figures and not part of the text. Nomenclature use should be identical
in both the legend and in the supporting text.
4.9.9 Warnings, cautions, and notes. Warnings and cautions are short, concise, and used only to highlight
operating or maintenance procedures, practices, conditions, or statements which are considered essential to
protect personnel (Warnings) or equipment (Cautions). Notes are used to highlight procedures, practices,
conditions, or statements that are not considered essential to protect personnel. Warnings, cautions, and
30
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
a. Standard warnings and cautions consist of four parts: a heading (WARNING, CAUTION), a
statement of the hazard or precaution, minimum precautions to be taken, and a possible result if the warning
or caution is disregarded. Warnings and cautions immediately precede the text to which they apply. Notes
precede or follow applicable text, depending upon the material to be highlighted. When warnings, cautions,
and notes occur for the same text, warnings will appear first, cautions second, and notes last.
b. The header WARNING, CAUTION, or NOTE is bold and centered above the appropriate text.
Headers are not numbered. When a warning, caution, or note consists of two or more paragraphs, the
header WARNING, CAUTION, or NOTE is not repeated above each paragraph. Warnings, cautions, and
notes on unrelated topics may not be contained under one heading.
c. Indent all lines of warnings, cautions, or notes five spaces or characters from both left and right
margins.
e. Warnings, cautions, or notes are not divided so that first lines or groups of icons appear on one page
and remaining lines or group of icons appear on another page. Warnings, cautions, and notes are not
separated from the text to which they apply.
4.9.9.2 Hazardous materials warnings with icons. Procedures prescribed for the operation and maintenance
of equipment are consistent with the safety standards established by the Occupational Safety and Health Act
(OSHA) Public Law 91-596 and Executive Order (EO) 12196. It is mandatory to use the hazardous
material warnings with approved icons when preparing work package technical manuals. Refer to MIL-
STD-3001-1 for style, format, and content requirements for the hazardous material warnings. Also refer to
figure 34 for an example of placement of warning icons in a procedure.
a. Table I lists approved TM page sizes. The maximum printing area includes all printed matter on the
page (e.g., text, illustrations, revision bars, TM numbers, page numbers, etc.). (Refer to figure 41.) Other
page sizes may be used when authorized by the requiring activity. Table I also provides the image area for
the authorized page sizes. Image areas for other page sizes will be provided by the requiring activity.
b. Table II lists manual trim sizes, foldout maximum page trim sizes, and foldout maximum image
area for foldout pages. The minimum margin is 1/2-inch top and bottom and 1/2-inch on the side opposite
the binding edge. Binding edge margin should not be less than one inch. Foldouts will only appear in 8-1/2
by 11 manuals.
Maximum
Style Trim Size Format Printing Area
31
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
11 x 8-1/2 Horizontal 10 x 7
8-1/2 x 11 45 x 11 36 x 10
4.9.10.1 Authorized printed manual size by thickness. The thickness for an 8-1/2 x 11-inch manual should
not exceed 3 inches (approximately 600 sheets of paper). For 17 x 11-inch manuals, the thickness should
not exceed 1 inch (150 sheets of heavy stock paper). For PMRCs prepared on heavy stock, there are no
thickness limitations.
4.9.11 Type sizes and styles. Table III lists preferred type sizes and styles. All type sizes may be plus or
minus one point. Slight variations in spacing and leading are permitted. Except for pocket size TMs that
may use 6-point type size, 8 point is the smallest permissible type size.
32
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Preferred
Use Type/Size Capitalization Leading Vertical Spacing
Title Page: Security Same or larger than Upper case
Classification TM number
Title Page: TM Sans serif bold 18-20 Upper case
Number
Title Page: Sans serif bold 14 Initial caps
Publication or
Revision Number and
Date
Title Page: Words Sans serif bold 14 Upper case
Technical Manual
Title Page: Type of Sans serif bold 18 Upper case
Publication
Title Page: Sans serif bold 18 Upper case
Maintenance Levels
Title Page: Sans serif bold 18-20 Upper case
Nomenclature of
Equipment
Title Page: Type, Sans serif bold 14-18 Upper case
Model, Part Number,
National Stock
Number, or Subject
Title Page: Subtitle Sans serif bold 14 Upper case
(Volume Title and
Number)
Title Page: Sans serif bold 10 Upper and lower
Supersedure Notice, case
Cross-reference
Notice, Continuation
Notice
Title Page: Sans serif bold 10 for Upper case for
Distribution header and sans serif header and upper
Statement, Export 6 - 8 for text and lower case
Control Notice for text
Warning, Destruction
Notice
Title Page: Authority Sans serif bold 10 Upper and lower
Notice (Service case
Nomenclature)
"A" Page (Header Sans serif bold 16 Upper case
Information):
Publication Number
"A" Page (Header Sans serif bold 10 Initial caps
Information):
Publication Date,
Revision Number, and
33
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Preferred
Use Type/Size Capitalization Leading Vertical Spacing
Page Identification
"A" Page Title Sans serif bold 10 Upper case 48 points below TM
number; 18 points
above text
TPDR and HMWS Sans serif bold 16 Upper case
(Header Information):
Publication Number,
Security Classification
TPDR and HMWS Sans serif bold 10 Upper case.
(Header Information): Date initial caps.
Page Identification,
Publication Date
TM Number Sans serif bold 16 Upper case 30 points from top of
page
Page Number Sans serif bold 10 30 points centered
from bottom of page
Revision Number Sans serif bold 10 Upper case for
first letter of
revision
Security Classification Sans serif bold 16 Upper case *30 points from top of
page
Work Package Sans serif bold 10 Initial caps
Marginal: Publication
Date or Revision
Date, and Page
Numbers
Work Package: Title Sans serif bold 10 Initial caps
for Reference Material
List, Record of
Applicable Technical
Directives, Support
Equipment Required
List, and Materials
Required List
Paragraph Titles Sans serif bold 10 All upper case or 2 12 points below title
upper case for block bottom rule; 12
first letter of points above/below
each principal text, table, or
word (depending illustration; 12 points
upon emphasis) above/below warning,
caution, and note
headers/text
Text (including Group Serif 10 Upper and lower 18 points below TM
Assembly Parts List case. GAPL text number, WP or other
(GAPL)) upper case. header; 12 points
above/below table or
34
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Preferred
Use Type/Size Capitalization Leading Vertical Spacing
illustration; 6 points
above page no.; 6
points above/below
warning, caution, and
note headers
Emphasis Italic bold 10 Upper and lower 1
case
Formulas and Italic 10 Upper and lower 1 12 points above/below
Equations case text, table, or
illustration
Figure Number and Serif 10 Upper case for 2 18 points below
Title first letter of illustration (within the
each principal figure area)
word
Legend on Sans serif 8 Upper case for 1 As required
Illustrations first letter of
first word
Illustration Callouts Sans serif 8 Upper case As required
Illustration Captions Sans serif bold 10 Upper case 2 18 points below
illustration
Table Number and Serif 10 Upper case for 2 6 points above title
Title first letter of
each principal
word
Column Headers Serif bold 10 Upper case 1
Table Text Serif 10 Upper and lower 2
case
List Headers Sans serif bold 10 Upper case for 2 12 points above list
first letter of
each principal
word
*NOTE: When a TM is classified, the TM number is 48 points from the top of the page and the page
number 48 points from the bottom of the page. All other spacing is adjusted accordingly.
a. Preferred text format for 8-1/2 by 11-inch manuals is single column (page wide), although
double column can be used. An exception is that double column text can be used to present principles
of operation for better readability. Both single and double column formatted WPs can be included in a
single TM if it would make the data more readable or comprehensible; however, both formats should
not be used in the same work package. Text is single spaced (double spaces between procedural steps)
with the left margin justified.
b. The first line of a paragraph should not be located at the bottom of the page or column. The last
35
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
line of a paragraph should not be placed at the top of a new page. Do not place the title or header on the last
line of a page or column. Widows and orphans are not allowed.
c. Text should be double-spaced between paragraphs, procedural steps, and before and after the
headings "WARNING," "CAUTION," and "NOTE." IPB GAPL pages should be considered text. Layout
should conserve space without lessening usability or clarity of material. Double spacing of text within a
paragraph, or similar wastefulness, is unacceptable. Blank space on a page should be avoided whenever
possible unless clarity or readability is sacrificed.
b. Place text and illustrations in such a manner that will conserve space without crowding or degrading
the usability or clarity of the material. Avoid blank spaces whenever possible. Whenever possible, place
illustrations on the same or facing page of associated text. If this is not possible (for example, more than
one full-page illustration), place the illustration as close to the related text as possible.
c. Foldout illustrations are placed at the end of the applicable work package.
4.9.12.3 Text wrapping. Always position text within the required image area. Do not wrap text around
illustrations. (Refer to figure 42.)
4.9.12.4 Illustration placement options. Illustrations are placed either immediately above or below the
supporting text or the procedural step or group of steps. Illustrations may float on a page to reduce the
white space on a page. If there is not enough room on a page to place a supporting illustration, place the
illustration on a facing page, if possible. An illustration should not be inserted between two-column text on
a page. The illustration should be placed either above or below the text.
Author’s Note: When developing an SGML document instance, use the following words to indicate
placement options for digital illustrations: "Above," "Below," "Immediate (default)," "Facing," and
"Float." Tag the appropriate position in the text with the correct option.
a. Use the "Above" reference to place the illustration above the referenced text or steps.
b. Use the "Below" reference to place the illustration below the referenced text or steps.
c. Use the "Intermediate (default)" reference to place the illustration immediately below the
referenced text or steps.
d. Use the "Facing" reference to place the illustration on the page facing the referenced text or
steps.
e. Use the "Float" reference to place the illustration anywhere on the page with the referenced
text or steps.
4.9.12.5 Multiple tasks using same illustrations. When two separate tasks (e.g., Removal and Installation)
appear on the same page, one illustration can be used to support both tasks if space permits.
36
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.9.12.6 Repeating illustrations. Illustrations are not repeated unless necessary to support multipage
descriptions of tasks or to support a different requirement in another part of the TM.
4.9.13 National stock numbers. National stock numbers (NSNs) should not appear in NAVAIR WP
technical manuals.
4.9.14 Part numbers and reference designations. Part numbers and reference designations (Ref Des) should
not be used in the text or on illustrations except for the following:
a. Part numbers identifying specific support equipment or materials required are acceptable in text and
on illustrations when more than one item has the same nomenclature; for example, "Position clamp P/N
2469-10 over retaining fixture."
b. Part numbers identifying items contained in support equipment tool kits should be used in text or
illustrations. The tool kit part number should be included in the "Support Equipment Required" list.
c. Part numbers may be included in legends on, or adjacent to, the associated artwork as an aid in
identification.
d. When necessary for clarity, the specification, standard, or part number of consumable materials
(lockwire, adhesive, sealant, etc.) may be included in text and on maintenance WP illustrations but not on
IPB illustrations.
e. Part numbers may be used in figure titles to further identify the assembly or component being
illustrated. Part numbers will not be used when the Ref Des has been used.
f. Ref Des are encouraged to be used in text to couple the item or unit under discussion with the
supporting schematic or marking on the equipment.
g. Ref Des will be included in figure titles to further identify the item, assembly or component
illustrated.
a. "AN" nomenclature,
b. Nameplate nomenclature,
37
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
4.9.15.1 Nomenclature consistency and applicability. Nomenclature, other terms, and names must be
consistent within a manual and throughout other directly related manuals. Statements that explain
applicability for individual items of equipment will use specific serial numbers, block designations, model
designations, or similar identification. Such terms as "on later equipment" and "on early serial numbers"
will not be used.
4.9.15.2 Noun modifiers. Noun modifiers should be added to the description of parts as required to assure
positive identification, such as cotter pins/taper pins. These modifiers need not appear on the preparing
activity's drawing. Noun modifiers, once added for clarity, should be used throughout the technical data.
a. Simple identifying modifiers provided for parts may be dropped after the first full identification of
the item in the WP. For example, "Remove attaching bolt" is acceptable and preferred to "Remove cadmium
plated steel bolt," unless specific identification of one bolt within a group of similar objects is required.
b. When an item is identified by a common name, both this name and the correct technical name should
be clearly identified the first time the item appears in the text of a WP. The listing of common names in IPB
GAPLs is not required.
4.9.15.3 Neutral terms. TMs will make no reference to age, sex, race, or national origin. Use sex neutral
terms. Terms such as "airman" and "workman" are considered sex neutral. Terms such as male and female
connectors, pins, etc., are acceptable.
4.9.15.4 Military terms. Military terms used will be in accordance with Joint Pub 1-02, or any approved
dictionary or glossary of Navy military terms.
4.9.15.5 Automatic electronic test and checkout terminology. Terms used for automatic electronic test and
checkout will be in accordance with MIL-STD-1309.
4.9.15.6 Placard data. If all or a portion of the name of a control or display appears as a label on the
equipment, that portion should be written exactly as on the label, except that the placard should be written in
all capital letters to distinguish it from surrounding text (e.g., "POWER switch" or "MAIN PWR circuit
breaker"). It is also permissible to spell out the word for a symbol that cannot be reproduced by the machine
used to prepare the manuscript or reproducible copy.
4.9.15.7 Designation of equipment. The official designation of aeronautical equipment should be expressed
in specific terms such as model number, type, serial number range, or similar terms. Nomenclature
corresponding to that appearing on the equipment in the form of nameplates, decals, engraved legends or
other markings should be stated in text using the same wording that appears on the hardware.
a. At the first use of abbreviations and acronyms in a WP, spell out words completely and place the
abbreviation or acronym in parentheses immediately after the word(s). When a phrase is abbreviated as an
acronym, capitalize the first letter of each word and do not separate letters in the acronym by periods (for
example, "Illustrated Parts Breakdown (IPB)"). Abbreviations and acronyms accepted as words, such as
radar, sonar, laser, etc., need not be spelled out.
38
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. Do not create new abbreviations or acronyms to duplicate those presently listed in OPNAVINST
4790.2. The use of abbreviations or acronyms not listed in OPNAVINST 4790.2 should be held to a
minimum. Abbreviations and acronyms may be plural or possessive.
c. Spell out abbreviations and acronyms used in tables, but not found in the text or other portion of the
TM, in a note to the applicable table. Spell out abbreviations and acronyms used in illustrations or figures,
but not found in the text or other portion of the TM, in a note on the applicable illustration or figure.
d. When abbreviations or acronyms are used as markings on equipment (placarding), use the same
abbreviation or acronym in the TM.
4.10.2 Equations. The use of equations should be held to the minimum use required by the needs of the TM
user. For some examples of the use of symbols and punctuation in equations and equation alignment and
placement, refer to figure 43.
4.10.3 Connecting words. Place connecting words of explanation, such as "therefore" and "similarly," flush
left either on the same line with the equation or on a separate line.
4.10.4 Spacing. Use clear space above and below equations as needed. Center and indent any complex or
hard-to-read expressions in a clear space between the lines of text. Start a series of such expressions at the
left margin or indent in any consistent manner. Center and indent any important expression, regardless of
complexity, to introduce or emphasize it.
4.10.5 Numbering and referencing to equations. When it is necessary to reference equations in the text, give
the equation a reference number. The reference number consists of EQ, followed by an Arabic numeral
beginning with 1 within each WP (for example, EQ 1, EQ 2, etc.). (Refer also to figure 44.)
5.1 General. This section is intended to provide guidance and further clarify the requirements contained in
MIL-STD-3001-1 through MIL-STD-3001-7 for ETMs/IETMs developed to the work package (WP)
concept. The general style, format, and graphics guidance contained herein is applicable for the preparation of
the following types of technical information for aircraft weapon systems, engines, aeronautical equipment,
airborne weapons/equipment, and support equipment at all levels of maintenance.
Supporting information.
Descriptive information, principles of operation, and operation data.
Testing and troubleshooting information.
Maintenance and procedural information, including:
Structural repair information.
Wiring diagram information.
Aircraft wire bundle information.
Aircraft wire connector repair information.
Power plant build-up information.
Parts information.
39
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author’s Note: MIL-STD-3001-8 is not applicable for the development of ETMs/IETMs. MIL-STD-
3001-8 is to be used only for the development of separate IPBs for paper output or screen display of
page-based IPBs.
5.2 Selective application and tailoring. This section contains some guidance that may not be applicable for
the preparation of all ETMs/IETMs. Selective application and tailoring of requirements are the
responsibility of the requiring activity and are accomplished using MIL-STD-3001-1 through MIL-STD-
3001-7. If an identifiable, written conflict exists between this section and the detailed content standard, the
detailed content standard takes precedence.
5.3 Development of work package ETMs/IETMs. A work package ETM/IETM is specifically designed to
support individual functional information or maintenance work tasks for a weapon system or equipment.
Technical manual data developed for scrollable or frame-based display in work package format should be
prepared in accordance with the requirements of MIL-STD-3001-1 through MIL-STD-3001-7. Technical
manual data should be tagged using Standard Generalized Markup Language (SGML). This is
accomplished by applying the applicable Document Type Definitions (DTDs) and style sheets. The DTDs
interpret the technical content and structure of the functional requirements explained in MIL-STD-3001-1
through MIL-STD-3001-7 and are mandatory for use. The use of a specific style sheet will dictate the style
and format as it appears on the display device. Style sheets should be developed using the style and format
requirements contained in MIL-STD-3001-1 and in this handbook. Development of ETMs/IETMs is
accomplished through the use of the DTDs combined with the requirements contained in MIL-PRF-87268
and MIL-PRF-87269. The requirements contained in MIL-PRF-87268 and MIL-PRF-87269 apply unless
they conflict with the requirements in MIL-STD-3001. The requirements in MIL-STD-3001 take
precedence over the requirements contained in MIL-PRF-87268 and MIL-PRF-87269.
Author’s Note: The term "work package" is used throughout this section and the MIL-STD-3001
series to denote specific increments of technical content needed to ensure that the technical
information presented in support of a given task or process is complete, comprehensible, and
effective. The term "work package" has been retained because it was used extensively in the
development of most paper, page-based, NAVAIR technical manuals and is recognized as standard
terminology for an independent, stand alone data unit containing specific descriptive information or
maintenance task.
5.4 Obtaining the modular DTDs. Information on using and obtaining the DTDs and associated tag and
attribute descriptions, which are SGML constructs, can be obtained from the requiring activity.
5.5 Figures contained in this handbook. Figures 45 through 87 provide examples of preferred style and
format for the scrollable and frame-based display of ETM/IETM technical content work package data. In
an attempt to minimize the size of this handbook, most of the technical content provided in the examples
are in abbreviated form. Appendix A of this handbook provides examples of style and format requirements
for the different types of specific graphics used in the development of TMs.
Author’s Note: ETMs and IETMs for the U.S. Navy have been developed using a variety of authoring
and presentation systems. The "look and feel" of technical content differs greatly between
ETMs/IETMs depending on the authoring and presentation used. The examples provided in figures 45
through 87 have been selected from various weapon system/equipment ETMs/IETMs and are the
preferred style and presentation formats for the display of technical content information.
5.6 Types of work packages. There are basically two types of work packages. The first type is an
information-oriented work package. It provides information such as general information about the
40
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
ETM/IETM or weapon system/equipment, principles of operation, and operating instructions. The second
type of WP is task-oriented. Task-oriented WPs reflect all required maintenance tasks, including testing and
troubleshooting, at the assigned level of maintenance, and environment, materials, and support equipment
required for each defined task. WPs are written to reflect the engineering design, Logistics Support Analysis
(LSA) or Logistics Management Information (LMI), Level of Repair Analysis (LORA), approved
maintenance plan, and the established repair concept (SM&R codes).
5.7 ETMs/IETMs developed in accordance with MIL-STD-3001 series standards. This section should be
used in conjunction with MIL-STD-3001-1 through MIL-STD-3001-7 to develop work package
ETMs/IETMs for aircraft weapon systems, engines, aeronautical equipment, airborne weapons/equipment,
and support equipment. MIL-STD-3001-1 through MIL-STD-3001-7 contain the technical content and
mandatory style and format requirements for the preparation of technical manuals at all maintenance levels
through depot.
5.8.1 Technical manual outline. If required by the requiring activity, an outline should be developed prior to
the start of ETM/IETM development. Outlines need not be maintained current following the initial delivery
of the ETM/IETM.
5.8.1.1 Initial outline development. The first step in the development of an ETM/IETM outline is to
determine if all descriptive and maintenance information about the weapon system will be provided in a
single ETM/IETM. It may be more logical or effective to provide some aircraft specific maintenance
information in a separate ETM/IETM. For instance, structural repair, corrosion control, and nondestructive
inspection (NDI) repair data is unique, voluminous, requires frequent updating, and is used at specific areas
and sites. Therefore, it may be better to provide this data in a separate ETM/IETM. Similarly, Phased
Maintenance Requirements Manual (PMRM) card sets have the same characteristics and may also be better
suited to be in a separate ETM/IETM. Once a determination is made as to how many ETMs/IETMs should
be developed for an aircraft weapon system, a detailed outline can be generated for each using the specific
types of functional requirements listed in 5.8.1.2.
Author’s Note: The requiring activity should provide guidance on how many separate ETMs/IETMs
are required for a specific weapon system or equipment. ETM/IETM packaging can be based on
various factors, including weapon system site location; number, types, and availability of electronic
display devices; specialized maintenance facilities; and the need for only specific maintenance
information at a particular maintenance site. In addition, the frequency of change to certain types of
maintenance information may preclude it from being packaged or grouped with other information
(i.e., structural repair data may be better isolated from other nonscheduled aircraft system
maintenance because of the nature and detail of the repairs and replacement parts required and the
constant changes required to keep this type of information current).
5.8.1.2 Outline content and arrangement. An outline should be a detailed breakdown of system data. The
outline should also indicate recommended information that should remain in paper. An outline should be
developed for each system, subsystem, equipment, and major component, as applicable. For each system,
subsystem, equipment, and major component, the following types of data to be developed should be noted.
41
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Supporting information.
Types of descriptive data (i.e., description, theory of operation, use of controls and indicators, etc.).
Procedural tasks necessary to operate the system.
Procedural tasks necessary to perform complete maintenance.
Test and troubleshooting data.
Schematics and wiring information required.
5.8.2 Development of individual work packages. Ideally, each WP in a manual will be an independent, stand
alone data unit. The author will be required to group some information or maintenance tasks in one work
package and divide others into several WPs. Division or selection of coverage will depend on various
factors. These factors may include, but are not limited to:
b. A specific work package that is required by the TM content selection matrix or TM outline
approved by the requiring activity.
d. Two or more WPs for an identical troubleshooting or maintenance task may be required because the
task is performed differently due to differences in configurations.
e. Confining the information to one WP because dividing the information into several work packages
would degrade the usability (e.g., splitting a disassembly procedure into two separate WPs would degrade the
usability of the maintenance procedure).
f. The use of separate WPs for a series of maintenance tasks for a repairable component due to the
use of different support equipment, materials required, etc. (For example, if the support equipment, tools,
or materials used to perform removal and installation are very different from the support equipment, tools,
or materials used to perform disassembly and reassembly for the same system or component, it may be
better to separate this information into two WPs.)
5.8.3 Development of an SGML source file. Once all the work packages have been identified, an SGML
source file (document instance) should be developed for each WP. The SGML-tagged source file is
composed of SGML-coded ASCII, marked up (tagged) in accordance with the applicable modular DTD,
including the identification of the supporting graphics required. In order to tag WP text appropriately, the
author inserting the tags must be familiar with the DTD or must provide the text file to a person who is
experienced with the DTD and who understands the type of documentation being written, especially when
content tags are used. A customized template modeled for the applicable DTD may be available or
developed to assist the author in creating the document instance. (A template can be implemented in a text
editor, a WYSIWYG editor, a database input form, or an SGML authoring/composition system.)
42
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
5.8.4 Use of a style sheet. The style sheet specifies the desired screen presentation of the information content
of the document instances. Document formatting requirements such as layout and hyphenation rules are
specified in the style sheet, as well as how document elements such as paragraph titles, tables, and lists are
to be displayed. The style sheet provides the composition and imaging characteristics to be applied to the
SGML tagging (including attributes) of an SGML-tagged text source file (document instance) to present
the text material in screen presentation form.
5.9 Navigational, access, and other commands. The user should be provided with a comprehensive set of
commands to navigate and sequence through the information. The recommended minimum set of
navigation and control functions which should be available to the user and common to all ETMs/IETMs are
provided in MIL-STD-3001-1, Appendix C. Additional functions may be specified by the requiring
activity.
5.10 ETM/IETM divisions. The hierarchy of an ETM/IETM consists of front matter and a series of work
packages that include the types of data listed below.
a. Supporting information - Supporting information includes information such as the Numerical Index
of Part Numbers; Numerical Index of Reference Designations; Introduction; Consolidated Lists of Technical
Directives, Support Equipment, Materials, and References; and Maintenance Allocation (engines intermediate
maintenance only). Supporting information is divided into the support-oriented WPs that are required to
supplement or complement the technical information and task-oriented WPs developed in accordance with
MIL-STD-3001 series.
c. Testing and troubleshooting information - Testing and troubleshooting (fault isolation information) is
the data necessary to isolate faults found in a system, equipment, or component. Fault data basically contains
outcomes, faults, and corrective actions.
e. Parts information - Parts information is the necessary information required to identify and order a
new part, generally called IPBs (illustrated parts breakdowns) in a conventional TM.
Author’s Note: Refer to MIL-STD-3001-2 through MIL-STD-3001-6 for detailed requirements for the
preparation of specific work packages for the technical content data described above.
5.10.1 Front matter. The following ETM/IETM front matter is necessary to supplement the technical
content WPs.
b. CD (Compact Disk) label and flyleaf data (if applicable) (see figure 45).
43
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author’s Note: This ETM/IETM installation and CD and flyleaf data is not contained within the
ETM/IETM. It is the data that must be developed when the ETMs/IETMs are shipped or transmitted to
a user's site. The applicable DTD used in the development of front matter does not contain the
requirements to generate this data.
Author’s Note: Revision summary data is used in ETMs/IETMs to replace the numerical index of
effective work packages/pages (A page) used in traditional page-based TMs.
i. "How To Use This ETM" information or "How To Use This IETM" information (see figure 54).
Author’s Note: Refer to MIL-STD-3001-1, Appendix C for detailed requirements for front matter
preparation.
5.11 Work packages. Work packages (WPs) are used to logically divide all data required for a certain
function (i.e., descriptive information, operator’s instructions, maintenance with IPB, troubleshooting, etc.).
These data types can be further divided into tasks, subtasks (procedures), paragraphs; procedural steps;
tables; lists; warnings, cautions, and notes; and supporting graphics, etc. Parts information should be
accessible in any of the data types, as necessary.
5.11.1 Work package content. Each work package should consist of a title, work package initial setup
information, and the specific data necessary to develop the types of technical content work packages
described in 5.10.
Author’s Note: Refer to MIL-STD-3001-1, Appendix C for detailed requirements for work package
content preparation.
5.11.1.1 Work package title. Each WP should have a title that identifies the general subject or maintenance
or troubleshooting task contained in the WP. The title should be displayed in the title bar area of the user’s
EDS in all capital letters. (See figure 55.)
5.11.1.2 Work package initial setup information. Work package initial setup information should be included
for each work package, as required by MIL-STD-3001-2 through MIL-STD-3001-7. The following types
of information should be included, as applicable:
44
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
a. Maintenance level.
b. Effectivity.
c. Materials required.
e. Facilities required.
f. Personnel required.
j. Reference materials.
5.11.1.2.1 Display of work package initial setup information. This information may be displayed full screen
or split screen on one or multiple frames, or scrollable. (See figures 55 through 58 for examples.)
The maintenance level and effectivity data need not be displayed.
5.11.1.2.2 Effectivities. Effectivities (including tail numbers, BuNos, model numbers, serial numbers, part
numbers, etc.) are used to show limited applicability of information and instructions for different
configurations of equipment. Configuration differences may be the result of engineering changes made
during production or of service changes incorporated in the field. Effectivities should clearly show limited
applicability of affected portions of the data. The following guidelines should be followed.
a. Use specific and recognizable identification. This includes (but is not limited to) model, series, type,
block, software configuration, part, and/or serial numbers as required to adequately define the applicability.
Indefinite phraseology such as "on earlier models" or "on later aircraft" is not acceptable.
b. The manner in which the effectivity is presented will be consistent throughout the data for a given
item such as an aircraft.
c. Effectivities should not be displayed in the work packages. The effectivity should be selected by the
user when logging on.
5.11.1.2.2.1 Task effectivities. Show effectivities for tasks in the List of Contents.
5.11.1.2.2.2 Procedural step effectivities. When a procedural step must have an effectivity, use the following
guidelines.
a. When the effectivity affects a single step in a procedure, attach the effectivity to the step.
45
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. When two or more steps are affected by the same applicability restrictions, place the effectivity on
the first step and move the second and subsequent affected steps to substeps below the first step (create
substeps).
c. Do not attach more than one effectivity to a single step. If more than one effectivity affects the step,
create an alternate step and attach the applicable effectivities to the steps.
Author’s Note: Maintenance level and effectivity data should be included for every WP but need not be
displayed. The data is needed to permit users to automatically access all technical information by
maintenance level and tail or model number or both.
5.11.2 Supporting information work packages. Supporting information should be logically subdivided into
the support-oriented work packages that are required to supplement or complement the technical information
and task-oriented work packages developed in accordance with the MIL-STD-3001 series. Detailed technical
content requirements for the following supporting information are provided in MIL-STD-3001-1, Appendix
C. Supporting information includes:
This information may be developed and displayed in one or both of the following methods:
a. The information may be displayed in "traditional" tables and lists. (See figure 59.)
Author's Note: A "traditional" table or list will not include hotspotted information, but will be
scrollable through the entire table or list.
Author's Note: A hotspot from a descriptive, maintenance, or troubleshooting task would link to the
specific row(s) in the table or item(s) in a list instead of displaying the entire table or list.
5.11.3 Descriptive information work packages. Descriptive information work packages provide information
such as general information about the weapon system/equipment and principles of operation. Text developed
for descriptive information type work packages, such as description or principles of operation, will, as a
default, be displayed across the entire frame and in multiple frames or scrollable. When it is illustrated, the
illustrations may be full screen, or the text and illustration may be displayed in a split screen with the text on
the left and the illustration on the right. (Refer to MIL-PRF-87268.) (See figures 60 through 63 for
examples.)
Author’s Note: Refer to MIL-STD-3001-2, for detailed technical content requirements for the
preparation of description, operation, and principles of operation data.
5.11.4 Testing and troubleshooting information work packages. Testing and troubleshooting data should be
developed to the extent required to maintain the aircraft weapon system, aircraft engines, aeronautical
46
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
equipment, airborne weapons/equipment or support equipment at the authorized maintenance level. This
testing and troubleshooting information should guide the technician, in as practical a manner as possible, to
the system, subsystem, weapons replaceable assembly (WRA), shop replaceable assembly (SRA) or further
to the replaceable part, interconnecting wire, or mechanical linkage which caused the malfunction or failure.
See figures 64 through 67 for examples of screen display for testing and troubleshooting procedures.
5.11.4.1 Wiring and schematic graphic information. See figures 68 and 69 for examples of tabular and
illustrated wiring information. When possible, schematics and wiring diagrams should be simplified to
contain only the information referenced by the text for which they are displayed. However, the ETM/IETM
should provide the user access to the entire schematic or wiring diagram. If the schematic or wiring
diagram cannot be displayed in its entirety and in full detail, it should be displayed using interactive graphic
display techniques such as those described in MIL-STD-3001-1, Appendix C.
Author’s Note: All information required to perform the tests and evaluate probable malfunctions of the
assembled systems or equipment should be provided in accordance with the technical content
requirements of MIL-STD-3001-3.
5.11.5 Procedural information work packages. Task-oriented WPs reflect all maintenance tasks at the
assigned level of maintenance, and the applicable initial setup information (refer to 5.11.1.2) for each defined
task (see figures 70 through 74). The hierarchical organization for dividing procedural information is into
tasks, subtasks (procedures), and steps (substeps, if required). Additional requirements for displaying
procedural data are provided in MIL-STD-3001-1.
Authors Note: The requiring activity should provide guidance and recommendations on the method
used to display procedural steps prior to the actual development of the IETM.
5.11.5.1 Procedures with locator graphics. Complex graphics can sometimes be broken into several less
complex graphics. Figure 75 shows a context drawing (the aircraft) with an enlargement (detail) of the
interior of a wheel well. The detail and legibility of the enlargement are sufficient to support the
accompanying steps. Subsequent steps relate to the enlargement, but require more detail. Therefore, figure
76 uses a second graphic, a further enlargement of figure 75's enlargement. Again, the detail and legibility
are sufficient for the relevant steps. The locator view need not be displayed on subsequent frames of the
procedure, but should be linkable at any step or from any detail graphic.
5.11.5.2 Maintenance procedure leading to IPB information. Individual parts referenced in maintenance
steps should be called out on graphics using hotspot index numbers or nomenclature that link the user to
the applicable IPB information. (See figures 77 and 78.)
5.11.6 Parts data information. Parts information should be available at the point of the presentation in any
work package to which the specific system and equipment replaceable and repairable part is identified. See
figures 79 through 81 for typical examples of the display of parts data. Inclusion of parts information should
be used to:
47
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Authors Note: Refer to MIL-STD-3001-4 for detailed requirements for ETMs/IETMs parts data
information.
5.12 Style and format for display of work package text and graphics. In general the style and format for the
display of text and graphics should be in accordance with MIL-PRF-87268 and the information below.
5.12.1 Descriptive text. Work packages of descriptive text are generally formatted in paragraphs.
5.12.1.1 Paragraphs. Paragraphs within a WP for ETM/IETM display should be unnumbered. Paragraphs
may have titles. When used, paragraph titles should be in bold capital letters. Ensure that the style of
paragraph presentation is consistent throughout the entire ETM/IETM.
5.12.2 Procedural text. Procedural text is generally divided into tasks, subtasks (procedures), and steps (and
substeps, if required).
5.12.2.2 Subtasks (procedures). Each subtask should include all steps required to achieve a specific
objective. Each new subtask should begin on a new frame display. Subtasks are generally done
sequentially, and their specific objectives differ. Usually, the subtasks have to be broken up into steps.
5.12.2.3 Steps. A step is a unit of a procedural sequence which consists of a single technician action. Steps
compose subtasks (procedures). Procedural steps should be used to present detailed step-by-step instructions
for performing an operational or maintenance task. In each set of steps, individual steps should be
perceptually separated from each other. (Refer to 5.11.5.)
5.12.2.3.1 Step numbering. Unless specified by the requiring activity, procedural steps should be numbered
consecutively with Arabic numerals. Substeps should be numbered consecutively with lower case letters.
5.12.3 Task dialog displays. Task dialogs should be developed, as required, and formulated as prompting
questions to the user. Dialogs should be developed so that they require a user to respond (enter data)
before any subsequent processing occurs. Task dialogs may appear as pop-up windows in the maintenance
work packages to allow the user to indicate the results of the current maintenance activity. Examples of the
types of task dialog displays that may be used are:
48
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Author's Note: The content and the style and format of task dialog displays can vary widely, depending
on the specific type of dialog required to perform and complete the maintenance or troubleshooting
task. Implementation and presentation of these dialog displays are a function of the presentation
system, DTD, and style sheet used to generate this data.
5.12.4 Titles.
5.12.4.1 Assignment of titles. Easy access to technical data contained in the ETM/IETM is key to a
successful search for specific data. Titles should be assigned with full consideration of the importance they
have in finding information quickly.
a. Titles should be assigned to all systems, subsystems, and components, as applicable, and to all tasks
and descriptive information for each system, subsystem, and component.
b. The titles provided in the List of Contents should be identical to those assigned to systems,
subsystems, components, and individual tasks.
c. Each title should be exclusive within the system of which the data is a part. A complete title should
be definitive and descriptive of the content of the data.
5.12.5 Alerts.
5.12.5.1 Use of alerts. An alert is any message, communication, notice, or output which requires manual
acknowledgment from the user of the ETM/IETM. Alert messages are mandatory for use in ETMs/IETMs
and should be displayed within a border. Warnings (including hazardous material warnings), cautions, and
notes should be treated as alerts. Detailed requirements for development and display of all types of alerts are
provided in MIL-STD-3001-1.
5.12.6.1 Quality assurance procedures. Procedures that are essential to equipment performance or to safety
of personnel are considered to be "Quality Assurance Procedures." It is necessary to ensure that all required
tasks, including final testing of the end item (verification of repair), are accomplished prior to completion of
work.
5.12.6.2 Highlighting in-process quality assurance procedures and steps. Procedures considered to be
"Quality Assurance Procedures" should be highlighted by the addition of the abbreviation "(QA)" preceding
the procedure. It is necessary to ensure that all required tasks, including final testing of the end item
(verification of repair), are accomplished prior to completion of work. In some cases, only certain steps of a
procedure are considered to be "Quality Assurance Steps." These steps should also be highlighted by the
addition of the abbreviation "(QA)" preceding the individual step or steps. Alternate ways of highlighting
QA procedures and steps may be used when approved by the requiring activity. An explanation of the
requirements and highlighting should be given in the introduction to the data. These QA procedures and
steps may be summarized. Refer to 5.12.6.3.
5.12.6.3 Quality assurance procedure summary for procedural maintenance data. A summary of QA
procedures or QA steps(s) may be provided for each maintenance task containing a procedure or step(s)
designated for QA. This QA summary should be able to be user-invoked at any time during the
performance of the entire maintenance task.
49
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
5.12.7.1 Tables.
5.12.7.1.2 Display of rows. Certain tables provide data that may be required to supplement or complement
the descriptive information or maintenance or troubleshooting tasks contained in many of the work packages
within the ETM/IETM. Therefore, it may be more efficient to link the data to the specific row(s) in the
table where the applicable information is located instead of displaying the entire table (e.g., the consolidated
list of materials required table, which is used in almost all maintenance WPs). When it is determined that
only a specific row(s) of a complete table is required to support the associated procedural task or
informational data, the information contained in the entire row(s) should be displayed.
5.12.7.1.3 Table numbering. Tables for ETM/IETM display should not be numbered.
5.12.7.1.4 Table titles. In general, tables should have a title. Each title should be descriptive and unique.
The guidelines listed below should be followed:
a. Table titles should appear above the table. The table title should also appear in the display title bar.
b. If the table is scrollable, the table should have a "sticky" table title and all column heads.
Author's Note: "Sticky" infers that the title and column heads will be continually displayed
throughout the scrolling process of the entire table. (See figure 68 for an example of a wire list in
tabular format for frame-based display.)
5.12.7.1.5 Footnotes to tables. There should be no footnotes in tables. Notes should be used. Refer to
5.12.5. There should be an identifiable indication, such as an icon, to indicate the presence of a note.
5.12.7.2 Lists. Lists may be used in lieu of tables, when appropriate. Three types of lists are identified
below. Lists may be unnumbered, numbered sequentially, or lettered alphabetically. They may have an
optional title in all upper case bold letters.
a. Definition list. The definition list consists of the term and the definition. It may have the headers
"Term" and "Definition" above the appropriate sections of the list.
b. Random list. The random list consists of one or more items in a random order.
c. Sequential list. The sequential list consists of one or more items in a specified order, such as
alphabetic, numeric, or alphanumeric.
Author's Note: Numbering/lettering of items in a list is the function of the style sheet.
5.12.8.1 Figure numbering. Figure numbers for illustrations contained in work packages for ETMs/IETMs
may be used.
50
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
5.12.8.2 Figure titles. Figure titles for illustrations should not be used.
5.12.8.3 Illustration identification numbers. Each illustration should be assigned a unique identification
number. These identification numbers should not be displayed on the user's EDS.
5.12.9 Abbreviations and acronyms. Abbreviations, acronyms, and unusual terms may be used in any WP
text, when applicable. It is not necessary to spell out the words completely after the first use of an acronym
or abbreviation. A work package containing a consolidated list of abbreviations, acronyms, and uncommon
terms should be developed explaining all abbreviations, acronyms, and unusual terms used in the
ETM/IETM. It is not necessary to make the abbreviations, acronyms, and uncommon terms work package
automatically accessible when an abbreviation, acronym, or uncommon term is used in a WP. Hotspots
should be used to link all abbreviations, acronyms, and uncommon terms to the WP containing the complete
explanation and listing of abbreviations, acronyms, and uncommon terms.
5.12.10 References. The use of references in text can create undue hardship and/or confusion for the user of
the technical data. References should be kept to a minimum. A high amount of referencing in text frequently
indicates improper task analysis or LSA/LMI. As a practical consideration, linking should be used and
encouraged. Hotspots should be used to link cross-referenced material.
Author’s Note: For ETMs/IETMs the words "cross-referencing" mean linking to another source of
instruction or information. The primary goal of an ETM/IETM is preparation of self-contained task-
or descriptive-oriented data. Each WP is intended to be an independent data package for performing a
specific task.
6. GRAPHICS REQUIREMENTS.
6.1 Illustration preparation. Illustrations should be prepared in accordance with the requirements provided in
MIL-STD-3001-1, Appendix B for page-based TMs and MIL-STD-3001-1, Appendix C for ETMs/IETMs.
6.1.1 Types of illustrations. As applicable, the following types of graphics should be used in the preparation
of ETMs/IETMs. Preferred format requirements of these graphics and typical examples are provided in
Appendix A.
a. Line drawings.
b. Photographs.
c. Engineering drawings.
d. Diagrams.
7.1 Revisions for page-based TMs. There are two types of revisions that can be prepared for a page-based
NAVAIR TM: a pickup revision and a complete revision. The requiring activity will determine the type of
revision required. Detailed requirements for the preparation of revision data are provided in MIL-STD-
3001-1, Appendix B.
51
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
7.1.1 Pickup revisions. A pickup revision incorporates the basic issue or latest revision of a manual, all
previous change pages, and the new change pages that would require the issuance of an additional revision.
Only those updated or added change pages will have the current change number and date. Those pages not
affected by the current change should retain the previous change symbols and change number/date.
7.1.2 Complete revisions. A complete revision requires rewrite and reorganization of the technical content of
the data. All pages, paragraphs, illustrations and tables should be renumbered to establish correct sequence.
WPs will be renumbered and assigned new WP sequence numbers in consecutive order. All existing
change numbers, change bars, dates and change symbols will be removed. Change symbols will be inserted
only on those pages incorporating new or changed data during the preparation of the complete revision. The
revision date will be assigned by the requiring activity.
7.1.3 Change symbols. Change symbols should be inserted to identify technical changes in text, illustrations,
and tables.
a. Text and tabular data. The text and tabular data affected by a change should be indicated by the
letter "R" or a change bar in the outer margin of double column format material and in the outer margin
(opposite binding edge) of single column format material.
(1) Miniature pointing hand. A miniature pointing hand should be used to highlight the area
containing the changed material.
(2) Change bar. When several changes are made in one area, or the area is congested, a change bar
may be used to indicate a general area. The change bar should be placed in such a manner as to clearly
indicate the changed area without confusing the user. If an illustration has been extensively changed, a
change bar may be placed along the outer margin of the illustration (full page illustration) or in the
applicable margin (partial page illustration).
(3) Alternate method. An acceptable alternate method for use with an extensively changed full
page illustration is the use of the words "MAJOR CHANGE" enclosed in a box. The enclosed words
should be placed in a clear space of the illustration image area.
7.1.4 Renumbering in a work package during a pickup revision. Paragraphs, illustrations, tables, pages, and
index numbers on illustrations added between existing ones should be assigned the preceding number plus
consecutive capital letter suffixes; for examples 3A and 3B might be added between existing numerals 3
and 4. Suffix letters I and O should not be used. Other than the addition of suffix letters, existing
identification numbers and suffixes should not be renumbered.
52
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
a. Added material should be placed in proper sequential order within the WP. If this causes an
overrun, the material that will not fit on the existing page should be placed on an added page. If blank space
is available on either the preceding or following page of the one affected, this space may be used for overrun
material; however, correct sequential order of material must be maintained. Pages should not be added
between a right-hand (odd numbered) and a left-hand (even numbered) page. If additional copy is added to
a right-hand page, the overrun should be carried to the next left-hand page and the overrun from this page
should be placed on an added page. Therefore, such added pages should always be assigned even numbers;
for example: "2A, 2B, 4A, or 4B."
b. Deleted paragraphs, procedural steps, or callouts following index numbers on illustrations should
be indicated by placing the word "Deleted" after the affected item; for example: "r. Deleted." or "2
Deleted."
c. Deleted pages should be accounted for by placement of a note at the bottom of the preceding page
or at the top of the succeeding page; for example: "Page 7 Deleted." The note should be placed within the
required image area (with marginal copy).
7.2 Revisions and updates for ETMs/IETMs. When changes to ETMs/IETMs are ordered, the deliverable
product should be either an update or a complete revision. The requiring activity will determine the type and
frequency of the change required. Detailed requirements for the preparation of revision data are provided in
MIL-STD-3001-1, Appendix C.
7.2.1 Revisions. A complete ETM/IETM revision requires rewrite of the technical content of the data to
ensure that all new data and past updates are included. When applicable, all existing change numbers,
change bars, dates, and change symbols will be removed. When required by the requiring activity, a
revision summary should be provided. (Refer to 5.10.1.) Revisions will be incremental and the frequency
of revisions will be defined in the contract. Each revision to an ETM/IETM should be identified by a
revision date.
7.2.2 Updates. Updates are changes to the initial version of the ETM/IETM or to the latest complete
revision of an ETM/IETM. Updates are issued incrementally as necessary, or as required by the contract.
When authorized by the requiring activity, updates should include change symbols and change dates to inform
the user what has changed and where the changes or additional information is located. When required by the
requiring activity, a revision summary should be provided. (Refer to 5.10.1.)
7.2.3 Change symbols. When authorized by the requiring activity, change symbols should be inserted to
identify technical changes in text, illustrations, and tables.
a. Text and tabular data. The text and tabular data affected by a change should be indicated by the
letter "R" or a change bar in the outer margin.
(1) Miniature pointing hand. A miniature pointing hand should be used to highlight the area
containing the changed material.
53
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
(2) Change bar. When several changes are made in one area, or the area is congested, a change bar
may be used to indicate a general area. The change bar should be placed in such a manner as to clearly
indicate the changed area without confusing the user. If an illustration has been extensively changed, a
change bar may be placed along the outer margin of the illustration.
(3) Alternate method. An acceptable alternate method for use with an extensively changed
illustration is the use of the words "MAJOR CHANGE" enclosed in a box. The enclosed words should be
placed in a clear space of the illustration image area.
8. COMPREHENSIBILITY.
8.1.1 Standard English grammar. The U.S. Government Printing Office Style Manual will be used as a
general guide for standard American English usage, i.e., capitalization, punctuation, compounding of words,
numerals in the text, spelling of nontechnical words, etc. Colloquial and slang expressions will not be used.
a. Word order. Narrative text (nonprocedural) will be written using simple word order (subject, verb,
object) to the extent possible. Modifiers, including prepositional phrases, will be as close as possible to the
word modified. Simple word order will ordinarily be used for description and discussion statements such as
warnings, cautions, and notes.
b. Topical sentence. When necessary, for greater clarity, the first sentence of each paragraph will be
the topical sentence. The topical sentence describes or summarizes the content of the paragraph. All
information in the paragraph relates to the topical sentence.
c. Limitations for nonprocedural text. Explanatory, descriptive, or theoretical text will not contain
procedures.
8.1.3 Procedural text. Detailed task steps will be identified and then properly worded for the target audience.
Task steps will be organized in a logical order. They will be presented so that they sequentially show what
action the user will be performing or what the user sees or detects on the equipment at each step of the
procedure. Procedural steps will be worded and arranged in the order that will provide the most effective
and efficient results. Emphasis will be placed on the specific steps to be followed, the results that may be
expected or desired, and the corrective measures required when the expected results are not obtained.
8.1.3.1 Lead-in. Procedural steps will not be prefaced by a lead-in that merely duplicates the title as in the
following example: "Disassembly of a sensing unit. The sensing unit is disassembled according to the
following procedure:"
8.1.3.2 Form and content of procedures. A procedural step will be limited to a single operation or to
repetitions of a single operation with the following exceptions:
a. If simultaneous operations are required, they will be listed together in the same step.
54
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. If the step represents a detailed procedure, so basic that the details should rarely be needed by the
intended users, or if the procedure is very frequently repeated, such as a turn on, turn off, or calibrate
procedures, the written procedure for that step will use a single verb and cite a reference to the detailed steps
(e.g., "Turn equipment ON. [See WP 056 00 for details.]").
c. If needed, text will show verification of the result of a procedure performed in the step (e.g., "Press
pushbutton A and be sure indicator A is lit.").
8.1.3.3 Limitations for procedural text. Procedures should not contain explanatory, descriptive, or
theoretical material (except in notes, etc.).
8.1.3.4 Sentences in procedures. Sentences directing the actions of the user will begin with the verb (e.g.,
"Remove four screws (1) and cover (2)."). If more than one person is involved, the directions will be in the
active voice, for example, "Technician 1 should... while Technician 2…".
8.1.3.5 Positive form. Procedural steps will be in positive form (i.e., "Close container." rather than "Do not
leave container open.") unless the meaning demands the negative form.
9.1.1 General. When preparation of a classified technical manual (TM) is specified by the requiring activity,
the security classification markings will be identified in accordance with DoD 5200.1R, DoD 5220.22M,
OPNAVINST 5510.1 and Executive Order 12958. Specific markings for classified manuals, pages, work
packages, paragraphs, tables and illustrations are as prescribed herein. For guidance on security
classification and handling restrictive markings on Compact Disk-Read Only Memory (CD-ROM), refer to
MIL-HDBK-9660.
9.1.2 Overall classification. (Refer to figure 88). The overall classification assigned to all TMs agrees with
the highest classification assigned to any page therein. Place the overall classification assigned to a TM at
the top and bottom of the title page. When this results in a title page being marked with a higher
classification than that assigned to the contents of that page, provide an explanation of the higher
classification on that page under the bottom classification marking. For example:
CONFIDENTIAL or SECRET
(This page is UNCLASSIFIED) (This page is CONFIDENTIAL)
9.1.3 Classification of alphabetical index. (Refer to figure 89.) Every effort should be made to use
unclassified captions/titles in the alphabetical index. When classified captions/titles are used, place the
security classification of the caption/title between the paragraph number and the caption/title. The
classification marking is for the caption/title only and does not indicate classification of the content of work
packages, tables, or illustrations. Do not mark unclassified titles.
9.1.4 Classification of work packages. (Refer to figure 90.) Each work package is considered a stand alone
unit and for classification purposes is equivalent to a portion of the publication. Mark each page of the
55
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
work package with the highest classification required for any element of the work package. When any page
is marked with a higher classification than that assigned to its contents, provide an explanation on that page
beneath the bottom classification marking. For example:
CONFIDENTIAL or SECRET
(This page is UNCLASSIFIED) (This page is CONFIDENTIAL)
9.1.5 Classification of pages. (Refer to figure 91.) Mark each page (other than title page and work package
pages) according to its highest content. When classification of two pages of one sheet (two pages back to
back) differ, use the higher classification on both pages. When two pages of one sheet are unclassified,
mark each page unclassified. When any page is marked with a higher classification than that assigned to its
contents, explain the higher classification on that page beneath the bottom classification marking. For
example:
CONFIDENTIAL or SECRET
(This page is UNCLASSIFIED) (This page is CONFIDENTIAL)
If a blank page backs up a classified page, show the classification of the classified page on the blank page
and explain the higher classification as described above. Blank pages backing up unclassified pages need
not be marked. If the classification shown on the last page of a publication is not the same as that shown on
the title page, then add a blank sheet to the back of the publication showing the same classification as the
title page. The last page, if blank, of the publication reflects the same classification as the title page (i.e.,
the highest classification of the publication).
9.1.6 Paragraph and table markings. (Refer to figures 92 and 93.) Mark all paragraphs, subparagraphs,
steps and tables to show the level of classification contained in or revealed by it, or that it is unclassified.
Classification levels are shown by the appropriate classification symbols between the paragraph number,
procedural step number or letter and the start of the text and between a table number and title. Use the
following parenthetical symbols: (TS) for Top Secret, (S) for Secret, (C) for Confidential, and (U) for
Unclassified. In marking warnings, cautions, or notes, place the appropriate marking immediately preceding
and to the left of the warnings, cautions, or notes involved. The abbreviated classification markings are for
internal content use only, not for overall marking of pages. These instructions apply to all new and revised
publications.
9.1.7 Illustration markings. (Refer to figure 94.) Mark illustrations, photographs, figures, graphs, drawings,
charts and similar portions of classified documents to show their classification or unclassified status.
Ensure that markings stand out and are placed within the illustration. Mark captions, if used, on the basis of
their content alone by placing the symbol "(TS)," "(S)," "(C)," or "(U)" immediately before the caption.
56
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
9.2.1 Security classification markings. When preparation of a classified ETM/IETM is specified by the
requiring activity, the security classification markings will be identified in accordance with DoD 5200.1R,
DoD 5220.22M, OPNAVINST 5510.1, and Executive Order 12958. For guidance on security
classification and handling restrictive markings on Compact Disk-Read Only Memory (CD-ROM), refer to
MIL-HDBK-9660.
9.2.2 Display of security classification markings. Whenever classified information is displayed, the
classification level should be indicated in the left-hand corner of the footer area. The indication should be
the upper case spelling of the words corresponding to the classification level (e.g., CONFIDENTIAL or
SECRET). When color is used, these indications should be displayed with a consistent color. The
classification indication should be clearly distinguishable from the function indicators in the same area. If
any classified information is contained in the ETM/IETM, the classification of the entire ETM/IETM is that
of the highest classification level used, e.g., SECRET. In an IETM, if a given frame is unclassified, the
label UNCLASSIFIED should appear in the footer bar.
10. NOTES.
10.1 Intended use. Technical manuals prepared in accordance with the information and guidance contained
in this handbook are used to support operation and maintenance of various types of equipment and weapons
systems within the Department of the Navy.
10.2 Subject term (key word) listing. The following terms are to be used to identify the MIL-HDBK-3001
document during retrieval searches.
57
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-100 003 00
1 May 1995
ORGANIZATIONAL MAINTENANCE
PRINCIPLES OF OPERATION
Reference Material
1-2 SYSTEM DESCRIPTION. The landing gear 4. Warning and position indicating
system is made up of components listed in figure 1, and
provides: 5. Interface relays
2. Normal extension
58
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
1-8 Emergency extension is primarily free fall aided by 1. 30.0 + 1.0 seconds after aircraft touchdown
stored energy in the MLG shock absorber and hydraulic with LGCU P/N 8-347-01 installed.
system no. 2B pressure. Hydraulic system no. 2B pressure
is supplied by the Auxiliary Power Unit (APU) and 2. 60.0 +5.0 seconds after airdraft touchdown
emergency brake accumulators and serves to unlock the with LCU P/N 8-347-03 installed.
landing gear uplock mechanisms and aid in landing gear
down lock. Emergency extension is controlled by the LDG 1-15 COMPONENT DESCRIPTION
GEAR control or the EMER LDG GEAR control.
1-16 Emergency Landing Gear Manual
1-9 Warning and Position Indicating Control Valve Assembly
1-10 Warning and position indicating is controlled by the 1-17 The emergency landing gear manual control
landing gear control unit (LGCU) and provides visual valve assembly is a two-position manually activated
(lights) and audio (warning tone) indications to the crew of valve which controls hydraulic systems no. 2B pressure
landing gear position and safety. (emergency) and no. 2A return to and from the landing
gear system.
1-11 Interface Relays
1-18 Emerg Ldg Gear and Emerg Brk
1-12 Interface relay control is provided by the Coupler Assembly
LGCU which computes input data combinations and
provides outputs to control the state of the landing gear 1-19 On F/A-18B and F/A-18D, the emergency
system relays which in turn control various other aircraft landing gear and emergency brake coupler assembly
systems. provides a means of connecting forward and aft cockpit
push-pull control assemblies to a single output push pull
1-13 Built-In Test (BIT) control to operate the emergency landing gear manual
control valve assembly.
1-14 The BIT system electrically tests the initiated
BIT provided by the LGCU. Periodic BIT runs
landing gear system through a periodic BIT and an
59
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-742-300 012 00
1 April 1995
ORGANIZATIONAL MAINTENANCE
Reference Material
Materials Required
1-1 REMOVAL
3. On 16395 and up, perform EMI shields removal procedure (WP 014 00).
CAUTION
To avoid damage to equipment, make sure waveguide coupling latch mechanism is disengaged before
applying release pressure to the handle.
4. Unlatch waveguide coupling mating waveguide assembly (3, figure 1) to Radar Transmitter T-1377/APG-65.
7. Inspect waveguide assembly (3) for external corrosion and clean as required (NAVAIR 16-1-540). If internal
corrosion or evidence of arcing exists, replace waveguide assembly.
2-1 INSTALLATION
2. Make sure two seals (1 and 4, figure 1) are installed in waveguide flanges.
60
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-742-300 012 00
5. Latch waveguide coupling mating waveguide assembly (3) to Radar Transmitter T-1377/APG-65. Make sure scribe line
on latch is completely visible and parallel to top surface of clamp.
61
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-742-300 012 00
3-1 ILLUSTRATED PARTS BREAKDOWN
3-2 This illustrated parts breakdown has data required for identifying and ordering parts. The manual introduction
has more information on IPB data.
62
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 004 00
1 August 1995
ORGANIZATIONAL MAINTENANCE
AIRCRAFT ARRANGEMENT
1. Radome
2. Forward fuselage
3. Center fuselage
4. Aft fuselage
5. Wings
1-2 RADOME. The radome (figure 1) spans from Y coordinate 60.50 to Y coordinate 128.50. It is a filament
wound fiberglass/epoxy shell mounted on an articulated hinge to allow easy access to the radar set. It provides an electrically
transparent window for transmission and receiving of radar signals.
1-3 FORWARD FUSELAGE. The forward fuselage (figure 1) spans from Y coordinate 128.50 to Y coordinate 383.00.
The forward fuselage includes the following:
1. Windshield
2. Canopy
3. Cockpit
1-4 Windshield
1-5 The windshield is the aerodynamic fairing for the cockpit and allows forward visibility for the pilot. The one-piece
windshield is stretched acrylic attached to an aluminum frame. The frame is hinged to allow the windshield to rotate forward
for instrument panel servicing.
63
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 004 00
1-6 Canopy
1-7 The one-piece clamshell canopy is stretched acrylic attached to an aluminum frame. The F/A-18B and F/A-
18D canopy is 54 inches longer and 125 pounds heavier than the F/A-18A and F/A-18C canopy. The canopy may be opened
and closed either manually or electrically operating the canopy actuator. When closed, the F/A-18A and F/A-18C canopy is
secured by three latches and a forward latch pin on each side. The F/A-18B and F/A-18D canopy is secured by four latches
and a forward latch pin on each side.
1-8 Cockpit
1-9 The F/A-18A and F/A-18C (figures 2, 3 and 4) have a single place cockpit. The F/A-18B and F/A-19D (figure 5) have a
front and rear cockpit. These views are for familiarization purposes only.
1-11 The leading edge extension (LEX) is a highly swept and cambered extension of the wing leading edge and provides
added lift at high angles of attack. The boarding ladder is mounted in the left LEX (figure 1).
1-13 CENTER FUSELAGE. The center fuselage (figure 1) spans from y coordinate 383.00 to Y coordinate 557.50.
The center fuselage includes the following:
1-15 The main landing gear is a lever design with an oleo shock absorber. The lever design provides a stable platform for
aircraft carrier and shore based operations. The shock absorbs the energy from ground loads during landing and taxi
operations.
2-2 Maintenance personnel should walk only on designated areas shown. Protective shoe coverings should always be worn
when walking on aircraft is necessary. Protective covers should be placed on walk areas during periods of high volume traffic.
Portions of the flap and horizontal stabilator area may be used for walks, provided the applicable locks are installed. For
ground protective devices (A1-F18AC-PCM-000).
3-2 Some access doors are in an integral part of the aircraft structure. Any time the aircraft is subject to stress, these doors
must be installed and/or closed. Procedures in A1-F18AC-LMM-000 that apply these requirements, reference the A1-F18AC-
LMM-010.
64
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 004 00
65
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 005 00
1 August 1995
ORGANIZATIONAL MAINTENANCE
AIRCRAFT ARRANGEMENT
1-2 EJECTION SEAT AND CANOPY EMERGENCY ESCAPE SEQUENCING. On F/A-18A and F/A-18C,
seat ejection and canopy jettison sequencing is started by pulling the ejection control handle on the front of the ejection
seat bucket, firing the ejection seat initiators. Ballistic gas pressure produced by the right seat initiator does the following:
2. Fires the gas to SMDC initiator which fires the IFF switch and the canopy jettison system by way of the one-
way transfer valve.
5. Ballistic gas pressure from either delay initiator operates the catapult primary cartridge which starts seat ejection.
1-3 On F/A-18B and F/A-18D, the emergency escape sequencing system provices for canopy jettison and ejection of
seats in correct sequence. The selection of sequencing is made on the ejection selector in the rear cockpit. There are
three selections:
1. Normal – When sequence is initiated from the cockpit, both seats are ejected with the rear seat first. When
sequence is started from the rear cockpit, only the rear seat is ejected.
2. Solo – Selection is used when the rear cockpit is not occupied; only the cockpit or rear cockpit.
3. Aft Initiated – Both seats are ejected with the rear seat first when started from cockpit or rear cockpit.
1-4 On F/A-18C and F/A-18D aircraft, the ejection seat(s) are equipped with a SAFE/ARM indicator switch which
indicates the ejection seat(s) not being armed under certain conditions. On F/A-18D the rear cockpit is equipped with a
seat caution mode switch which overrides the rear cockpit SAFE/ARM indicator switch for solo flight.
1-6 Canopy jettison is started with the internal canopy jettison lever. On F/A-18A and F/A-18C, the internal canopy
jettison lever is mounted inboard and below the canopy sill found in the left side of the cockpit. The lever is operated
66
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 005 00
by pushing down on the safety button and rotating lever aft. Aft rotation of the lever fires the canopy jettison initiator
which in turn jettisons the canopy.
1-7 On F/A-18B and F/A-18D, canopy jettison is started with either the internal canopy jettison lever or the rear internal
canopy jettison lever.
2. Rear cockpit canopy jettison is located in the center of the left console.
1-9 The lever is operated by pushing in on safety button and pulling up. Pulling up on rear internal canopy jettison lever
fires the rear canopy jettison initiator which in turn jettisons the canopy.
1-10 External Canopy Jettison – 161353 THRU 162477. Ground emergency jettison of the canopy is started
by external canopy jettison handles which are in back of doors 5L and 5R. Each handle is attached to approximately
eight feet of cable. The cables are joined to a common cable that connects to the internal canopy jettison lever. When
either handle is pulled and the cable extended as far as possible, the canopy jettison initiator fires which in turn jettisons
the canopy.
1-11 EJECTION SEAT SYSTEM. On 161353 thru 164068, the SJU-5/A ejection seat is fitted to the F/A-18A,
F/A-18C and in the rear cockpit of the F/A-18B and F/A-18D aircraft. The SJU-6/A ejection seat is fitted to the cockpit
of the F/A-18B and F/A-18D.
1-12 On 164196 and up, the SJU-17(V)1/A ejection seat is fitted to the F/A-18C and the rear cockpit of the F/A-18D
aircraft. The SJU-17(V)2/A ejection seat is fitted to the cockpit of the F/A-18D.
1-13 The ejection seat provides support for the crewmember during normal flight conditions and a method of escape
from the aircraft during emergency conditions. The ejection seat is automatic, cartridge operated and rocket assisted.
2-2 LANDING GEAR. The landing gear is electrically controlled and hydraulically operated. Before the gear can be
raised normally, weight must be off the wheels and the launch bar must be retraced. The main gear is retracted aft and
inboard into the fuselage and the nose gear is retracted forward. When the gear is extended, all gear doors remain open.
2-4 The landing gear is controlled by a two-position, wheel-shaped LDG GEAR control handle, located above LH
vertical console control panel. Moving the LDG GEAR control handle up (with hydraulic and electrical power applied)
raises the gear. Moving the LDG GEAR control handle down lowers the gear. On the ground (weight on wheels),
movement of the LDG GEAR control handle from DN to UP is prevented by a solenoid in the LDG GEAR control
panel. However, a down lock override button next to the LDG GEAR control handle makes it possible to override the
weight on the wheels switch and retract the MLG, if a failure has occurred in the lock down solenoid circuit. In this case,
the override button allows the LDG GEAR control handle to be raised. During maintenance with electrical power
applied, the LDG GEAR control handle can be raised without pressing the override button with aircraft on jacks (weight
off wheels) and proximity switch control not connected.
67
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 006 00
1 August 1995
ORGANIZATIONAL MAINTENANCE
1-2 Areas including reservoirs of flammable liquids, gases under pressure, and explosive devices are shown in figure 1.
Rescue and maintenance personnel should be aware of the hazards related to these areas.
2-2 Many explosive devices (figure 2) are located in and around the crew station. The ejection seat(s) have rocket
motors, initiators, and controls that require special handling during ground operations. The canopy has rocket motors,
initiators, thrusters, and controls that also require special handling. Safety procedures are covered in A1-F18AC-PCM-
000.
2-3 On 164725 and up; also 164627 thru 164724 after F/A-18 AFC 126, the DFIRS impact initiator, underwater
initiator and the severable door (63L) are explosive devices. They do not require special handling during ground
operations.
3-2 External fuel tanks, vertical ejection racks, missile launchers and conventional/nuclear weapons (figure 3), loaded
on wing or fuselage centerline pylons, may be ejected by explosive cartridges. The area near these devices must be
considered hazardous for maintenance personnel when aircraft electrical power is on.
3-3 Missile exhaust area and path of trajectory are hazardous for personnel. An inadvertently fired missile can cause
death or injury from either end.
3-4 The M61A1 or M61A2 gun projectile trajectory path is hazardous to personnel. Gun fire can cause death or injury.
3-5 Aircraft carrying munitions must be loaded, unloaded, and parked in designated explosives parking areas.
4-1 ENGINE
4-2 Danger areas resulting from engine operation are related to exhaust velocity and temperature, air intake, and noise.
68
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 006 00
4-3 AIR INTAKE AND EXHAUST. During ground operation of the engines, the forward and aft ends
of the aircraft are danger areas (figure 4). Inrushing air can pull a person into or against the intake ducts. Engine exhaust air
can cause death or serious burns. The area immediately aft of the tail pipes is hazardous for 15 minutes after engine shutdown.
4-4 ENGINE NOISE HAZARD. The noise level of operating jet engines can cause hearing loss. Figure 5 shows
relative noise levels at various distances from aircraft. Ear protectors must be worn when working near operating engines.
5-2 When the radome is open and the radar system is operating (figure 6), personnel should be aware that the radar
antenna can make sudden position changes and should stay 3 feet away from the antenna.
6-1 RADIATION
6-2 Radar operations are the main source of radiation injury to personnel. All radio, countermeasures set, and radar
transmitters (figure 6) are sources of rf energy. Radiation hazards are listed below.
1. Long exposure to rf energy at close range will cause personnel injury. High rf energy areas should be
posted with warning signs.
2. Accidental firing of electroexplosive devices (EED) can result from rf energy radiated through an opening
in the EED, or conducted through the firing leads.
4. Radiation may cause sparking between metal surfaces such as a fuel hose nozzle and aircraft structure.
The sparks may ignite fuel vapor.
6-3 PRECAUTIONARY MEASURES. Personnel should not work in radiation fields of operating radar antennas.
6-4 All transmitting equipment should be turned off before bringing EED into the area.
6-5 Transmitters should not be operated within 500 feet of uninstalled EED.
7-2 AIR INTAKE AND EXHAUST. Danger areas resulting from APU operations are shown in figure 7. The
APU intake duct is in door 52. The APU exhaust duct is in door 66.
7-3 NOISE HAZARD. Noise levels near APU intake and exhaust ports during operation may cause hearing loss.
Ear protection must be worn when working near an operating APU.
FIGURE 5. Example of a danger areas and precautionary measures work package - continued.
69
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-GAI-000 006 00
Figure 1. Flammable Liquids, Compressed Gases and Explosive Devices (Sheet 1).
FIGURE 5. Example of a danger areas and precautionary measures work package - continued.
70
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
1 May 1997
ORGANIZATIONAL MAINTENANCE
DESCRIPTION
ADF SYSTEM
EFFECTIVITY: 161353 THRU 163782; ALSO 163985 THRU 164912 BEFORE F/A-18 AFC 185
Reference Material
1-1 DESCRIPTION section resolves the bearing of the adf audio received
from vhf/uhf receiver-transmitter.
1-2 The description of the adf system is divided as listed
below: 4-1 RELATED SYSTEMS
a. System Description 4-2 Related systems which interface with the adf
b. System Component system are:
c. Related Systems
d. System Controls and Indicators 1. VHF/UHF communication system
2. Mission computer systems
2-1 SYSTEM DESCRIPTION
4-3 VHF/UHF COMMUNICATION SYSTEM.
2-2 The Direction Finder Set OA-8690()/ARD controls VHF/UHF receiver-transmitter receives the rf from the
and indicators make up the automatic direction finder (adf) adf system. The detected adf audio is returned to the adf
system. The adf system provides bearing to a station. The system to determine adf bearing. The antenna selector is
station is selected on vhf/uhf receiver-transmitter. The adf an rf switching unit that connects the adf system to
system sends bearing information to the mission computer either one of the vhf/uhf receiver-transmitters. The
system. The mission computer system uses adf antenna selector automatically switches the vhf/uhf
information to position an adf bearing symbol on the HIS receiver-transmitter to the comm system antennas when
display. The bearing symbol position on the HIS display keyed for transmission.
shows the bearing of the selected station in relation to
aircraft position. The location of all system components is 4-4 MISSION COMPUTER SYSTEM. The
shown in figure 1. mission computer system uses adf information to
position the adf bearing symbol on the HIS display. The
3-1 SYSTEM COMPONENT HIS display shows bearing of the selected station in
relation to aircraft position.
3-2 DIRECTION FINDER SET OA-8697()/ARD.
5-1 SYSTEM CONTROLS AND INDICATORS
3-3 The direction finder operates in the 100 to 400 MHz
frequency range. It has two sections. The antenna section 5-2 Operating controls and indicators are described in
receives and modulates rf signals. The audio processing table 1. Cockpit displays are shown in table 2.
FIGURE 6. Example of an aircraft system, subsystem, and component description work package.
71
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
Table 1. System Controls and Indicators
CONTROL/INDICATOR FUNCTION
1. Electronic Equipment Control.
a. ADF switch
NOTE
b. COMM 1 VOL control Controls adf audio volume when direction finder interfaces vhf/uhf
receiver-transmitter no. 1.
c. COMM 2 VOL control Controls adf audio volume when direction finder interfaces vhf/uhf
receiver-transmitter no. 2.
d. COMM 1 channel selector Selects channel of station to which adf bearing is required when direc-
tion finder interfaces vhf/uhf receiver-transmitter no. 1.
e. COMM 2 channel selector Selects channel of station to which adf bearing is required when direc-
tion finder interfaces vhf/uhf receiver-transmitter no. 2.
FIGURE 6. Example of an aircraft system, subsystem, and component description work package -
continued.
72
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
FIGURE 6. Example of an aircraft system, subsystem, and component description work package -
continued.
73
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
INDEX
NO. NOMENCLATURE REF DES
1 GND PWR CONTROL PANEL ASSEMBLY 1A-H004
FIGURE 6. Example of an aircraft system, subsystem, and component description work package -
continued.
74
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
INTERMEDIATE MAINTENANCE
Reference Material
1-1 INTRODUCTION
2-6 Resistors R1 through R6 provide local sensing in
1-2 This work package provides information necessary the event that remote sensing is lost.
for proper maintenance of Reference Power Supplies
A2B4 and A2B5. This information includes a description 3-1 PRINCIPLES OF OPERATION
and principles of operation.
3-2 BIPOLAR OPERATIONAL POWER
2-1 DESCRIPTION SUPPLIES. Figure 1 is a schematic diagram of
Reference Power Supplies A2B4 and A2B5, and figure
2-2 Reference Power Supplies A2B4 and A2B5 are both 2 is a block diagram of BOP power supplies PS1 and
located in Equipment Cabinet A2B. Reference Power PS2 that are located within each assembly. Each BOP
Supply A2B4 provides the reference A high and low power supply consists of six internal power supplies:
voltages, and Reference Power Supply A2B5 provides the the –20 to +20 vdc programmable main dc power
reference B high and low voltages. supply, +15-volt power supply, +15-volt power supply,
+10-volt reference power supply, +12-volt power
2-3 Each reference power supply consists of two supply, and a driver collector power supply.
identical bipolar operational (BOP) power supplies
equipped with auxiliary digital programming cards and 3-3 AC power is supplied to the BOP power supplies
two identical switching power supplies mounted on a through a three-conductor line cord connected to input
panel assembly. power connector P201. The center contact of this
connector is connected to the BOP power supply
2-4 Two BOP power supplies (PS1 and PS2) within each chassis to provide a safety ground. AC power applied
assembly provide the voltages that are used by the stimulus to the BOP power supplies energizes the primary
circuits within the Digital Test Station (DTS) to drive the windings of the main and auxiliary transformers, which
unit under test (UUT). The BOP power supplies are then produce dc source voltage on the secondary
programmable to provide a reference voltage between –20 windings of the main auxiliary transformers.
and +20 vdc with a maximum voltage difference of 20
vdc. 3-4 The dual dc source voltages for the main dc
power supply are obtained from the center-tapped
2-5 Two switching power supplies (PS3 and PS4) within secondary windings of the main transformer. They are
each reference power supply are used to provide a 5-volt then bridge-rectified and smoothed by capacitor filters
signal in addition to the reference voltages produced by before being applied to two groups of series/parallel
BOP power supplies PS1 and PS2. connected NPN/PNP power transistors at the output
power stage and made available at terminal block
TB201 on the rear of the supply chassis.
1
FIGURE 7. Example of a combination description and principles of operation work package.
75
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3-7 The linear integrated circuits within the BOP 4-2 Output power from power supplies PS3 and PS4
power supplies are powered by the +15-volt power is interfaced to the DTS through connectors J3 and J4.
supply, which is a dual dc source originating from The sense lines for these power supplies interface
through connector J5
FIGURE 7. Example of a combination description and principles of operation work package - continued.
76
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F404A-MMI-200 004 00
1 March 1993
INTERMEDIATE MAINTENANCE
GENERAL INFORMATION
1-1 INTRODUCTION lubricates all the gearbox bearings, gear teeth, and all
splined couplings at the gearbox pads.
1-2 This work package (WP) contains a general
description of the oil system components. 2-7 The oil tank is vented to the B-sump. The C-sump
is vented to the B-sump between the high-pressure
2-1 OIL SYSTEM turbine shaft and fan drive shaft. The B-sump is vented
overboard and the A-sump is not vented.
2-2 The engine oil system is self-contained and requires no
external aircraft connections or inputs. The oil system 2-8 The oil system contains a pressure transmitter for
monitoring the pressure differential between the filter
consists of the following components: inlet and the B-sump. Resulting pressure is transmitted
to the cockpit for monitoring.
1. Pressured Oil Tank
2. 10-Micron Nominal Filter 3-1 OIL TANK
3. Oil Cooler (fuel/oil heat exchanger)
4. Lube and Scavenge Oil Pump 3-2 The oil tank (figure 1) is an elongated spherical
5. Three Main Sumps enclosure containing a fill tube, a vortex separator, and
6. Accessory Gearbox Sump a pick-up chamber.
7. Magnetic Chip Detectors and Scavenge Screens
(for each main sump and for the scavenge 3-3 It also contains ports for system oil supply and
system) scavenge return from the lube and scavenge oil pump,
8. Connecting Hoses and Tubing a vent connection to the B-sump, an oil level sight gage
9. Lube Oil Pressure Transmitter indicator, an oil level switch, an oil sampling valve, and a
drain with magnetic chip detector plug.
2-3 Oil is circulated from the supply side of the pump
through the accessory gearbox and oil cooler to a tee. 3-4 Excessive air is removed by a deaerator inside the
tank as scavenged oil is returned to the tank.
2-4 Flow from one side of the tee goes to the C-sump
where it lubricates the No. 4 and No. 5 bearings. From the 3-5 Deaerated oil enters an inner chamber of the tank
C-sump, part of the oil goes back to the gearbox sump by which is connected to the inlet of the oil pump. The
gravity and then returns to the tank. The balance of the oil inner chamber is maintained full of oil by the scavenged
from the C-sump returns to the tank through the scavenge oil plus required additional oil from the tank surrounding
side of the pump. the inner chamber. The additional oil, if required, enters
the inner chamber by scavenge oil driven eductors.
2-5 Flow from the other side of the tee goes to the A-sump,
B-sump, and gearbox. The oil in the A-sump lubricates the 4-1 OIL FILTER
No. 1 bearing and returns to the tank through the scavenge
side of the pump. 4-2 The oil system has a disposable 10-micron
(nominal) filter. The filter assembly, a part of the lube
2-6 The oil in the B-sump lubricates the No. 2 and No. 3 and scavenge oil pump, has a pressure relief bypass
bearings and returns to the gearbox sump where it is valve which operates when pressure across the filter
combined with oil from the C-sump and is scavenged by the reaches 41-49 psid. The filter is designed to prevent
pump and returned to the tank. The oil in the gearbox discharge of filter contaminant through the bypass valve.
1
FIGURE 8. Example of an engine system description work package.
77
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F404A-MMI-200 004 00
4-3 The filter housing has an automatic shutoff to Fuel flows in series, first through the lube oil cooler,
prevent oil drainage when the bowl is removed. The filter and then through the VEN oil cooler.
housing is equipped with a differential pressure activated
pop-out device. 6-1 LUBE AND SCAVENGE OIL PUMP
4-4 The device provides visual warning of impending 6-2 The lube and scavenge oil pump (figure 3) is a
bypass with an extended red indicator when the pressure multi-element vane pump. The pump has one pressure
differential across the filter element reaches 22-35 psid. element and five scavenge elements.
However, when engine oil is below 100°F (37.8°C), a
lockout function prevents indicator pop-out. Once 6-3 The pressure element supplies oil under pressure
activated, the red indicator remains extended until to the oil pressure transmitter and to the oil nozzles in
manually reset with filter bowl inverted. the A-, B-, and C-sumps to lubricate the bearings. It
also supplies oil to the gearbox to lubricate the gear
5-1 OIL COOLER train. The pump has a scavenge element for each
sump and two scavenge elements for the gearbox sump
5-2 The oil cooler (figure 2) located on the outer area.
bypass duct, consists of an aluminum shell and a cross-
counterflow fuel-to-oil heat exchanger. 6-4 The pump also provides filtered oil to lubricate
the drive spline located between the pump and the
5-3 The cooler is a full-flow type with no provisions VEN power unit.
for temperature regulation. Engine fuel is warmed as it
passes through the tubes, cooling the lubricating oil 6-5 The pump is mounted on the forward left-hand
which flows around the tubes. pad of the accessory gearbox, and provides
a mounting pad and drive for the VEN power unit.
5-4 The variable exhaust nozzle (VEN) oil cooker is
an integral part mechanically, although lubrication and 6-6 A 10-micron nominal filter is contained in the
VEN oil are separated functionally. pump, as is a relief valve set to crack at 200-240 psid
and be fully open at 285 psid.
78
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F404A-MMI-200 004 00
79
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
15 May 1997
ORGANIZATIONAL MAINTENANCE
PRINCIPLES OF OPERATION
EFFECTIVITY: 161353 THRU 163782; ALSO 163985 THRU 164912 BEFORE F/A-18 AFC 185
Reference Material
1-2 The operation of the adf system is divided as listed 5. Bearing Processing
below:
6. Bearing Hold Processing
1. Sequence of Operation
3-2 POWER. A synchro reference voltage (26vac,
2. Functional Operation C) from no. 2 circuit breaker panel assembly is sent to
the direction finder and to the control-converter. On
2-1 SEQUENCE OF OPERATION 161353 thru 161359, the direction finder also receives
28vdc from no. 2 circuit breaker panel assembly. On
To start adf operation, apply aircraft electrical power. See 161360 and up, the direction finder also receives 28vdc
table 1, GND PWR control panel assembly. On electronic from no. 4 circuit breaker panel assembly. This voltage
equipment control (equipment control), set ADF switch 1 is routed through the contacts of ground power relay no.
or 2 depending on which vhf/uhf receiver-transmitter is 5, 1K-F057, to the direction finder. When 26vac, phase
desired for adf operation. When adf 1 or 2 is selected, C and 28vdc voltage exist, the direction finder is ready
squelch is automatically deselected. Set the COMM 1 or for activation.
COMM 2 VOL control to midposition and set the COMM
1 or COMM 2 channel selector to a channel for adf 3-3 SYSTEM ACTIVATION. The adf system is
bearing. New adf frequencies can be entered using the activated by the adf on signal (ground). The ground is
equipment control. Refer to vhf/uhf communication provided by setting the ADF switch to 1 or 2 on
system, sequence of operation, WP 003 00. On F/A-18B equipment control. Setting the ADF switch to 1 or 2
161354 thru 161360, the COMM 1 or COMM 2 VOL enables the 28vdc to the direction finder power supply
controls on the equipment control and rear equipment and enables bandwidth control circuits in the vhf/uhf
control must be turned on for vhf/uhf receiver-transmitter receiver-transmitter. It also provides adf select signals to
equipment control comm option displays. To display the the mission computer system and antenna selector and
adf bearing marker (figure 1), turn on the Multipurpose disables the squelch on the selected vhf/uhf receiver-
Color Display IP-1535/A or Horizontal Indicator IP- transmitter.
1350/A. The adf bearing marker appears on the HSI
display when the direction finder receives a signal. 3-4 The adf select signal to the antenna selector
connects the direction finder to vhf/uhf receiver-
3-1 FUNCTIONAL OPERATION transmitter no. 1 when adf switch is set to 1. Setting the
adf switch to 2 connects the direction finder to vhf/uhf
For simplified schematic, refer to figure 1. The adf system receiver-transmitter no. 2. The mission computer
functional operation is divided into six functions: system uses the adf select signal to compute the adf
bearing marker on the HSI display.
1. Power
3-5 ADF RF SIGNAL RECEPTION. ADF system
2. System Activation activation enables reception of rf signals by the adf antenna
section of the direction finder. The rf is modulated at the
3. ADF RF Signal Reception rotation frequency of the antenna and sent to the antenna
selector. From the antenna selector the rf is routed to the
1
FIGURE 9. Example of an aircraft weapon system principles of operation work package.
80
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
vhf/uhf receiver-transmitter. The vhf/uhf receiver-
transmitter, tuned to a station, detects the modulated rf and 3-8 The digital computer receives the adf information
sends unattenuated audio and adf audio to the from the control-converter and does the computation
intercommunication amplifier-control. required to put the adf bearing marker on the HSI
display. The adf bearing marker (figure 1) position on
3-6 AUDIO SIGNAL PROCESSING. The the display shows the bearing of the adf signal source in
relation to the aircraft position.
intercommunication amplifier-control processes the audio
received from the vhf/uhf receiver-transmitter. The
unattenuated audio is routed to the headsets (pilot, 3-9 BEARING HOLD PROCESSING. If during
instructor, or ground crew) for an audio indication of adf adf operation the pilot or instructor keys either vhf/uhf
signal reception. The adf audio is amplified and routed to receiver-transmitter, a bearing hold signal is produced by
the direction finder for resolving bearing information the amplifier-control. The bearing hold signal is sent to
contained in the signal. the digital computer through the control-converter. The
bearing hold signal is used by the digital computer and
the control-converter to hold the previous (before
3-7 BEARING PROCESSING. Bearing information
keying) adf bearing symbol position on the HSI display.
in the adf audio is resolved by the direction finder. The
Unkeying of the vhf/uhf receiver-transmitter causes adf
resolved adf bearing signal (bearing X, Y and Z) is sent to
operation to revert to normal bearing processing.
the control-converter for processing. The control-converter
tests adf bearing validity and provides adf valid and adf
bearing signals to the digital data computer no. 1
FIGURE 9. Example of an aircraft weapon system principles of operation work package - continued.
81
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-600-100 011 01
FIGURE 9. Example of an aircraft weapon system principles of operation work package - continued.
82
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
INTERMEDIATE MAINTENANCE
Reference Material
83
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
2-5 The DTS utilizes System Computer A1M6, which 3-1 CHANNEL THEORY
is part of the overall AN-USM-449A (V) ATS. The
DTS communicates with the system computer via an 3-2 STIMULUS AND MEASUREMENT
IEEE-488 bus that is part of the input/output (I/O) CHANNELS. The DTS has 240 input/output
function of the DTS. The elements of the basic DTS channels, each of which can be either a stimulus and/or
(i.e., power supplies, output, and input) are now measurement path. Function selection is the
automatically controlled over a range limited only by the responsibility of the programmer. After the channels
internal hardware of the DTS. The UUT test have been designated as either stimulus or measurement,
requirements determine the quantity and complexity of the programmer assembles a test pattern for each
the remaining hardware in the DTS. The following channel. The resulting bit patterns of each channel are
paragraphs summarize these requirements by providing combined to form a set of test patterns called test
a description of DTS capabilities required in testing vectors, which are used to stimulate and measure
UUTs. A summary of DTS capabilities is contained in a digital UUT. The test vector has three main divisions:
Work Package 011 00. A description of the DTS built- the stimulus pattern, the expected response pattern, and
in test (BIT) is contained in WP 015 00, and a more the mask pattern. These three patterns must be
detailed description is contained in NAVAIR 16-45- constructed in relation to one another on a vector-by-
6162-20. vector basis. For example, if a programmer is checking
a simple two-input AND gate, the test vectors and
2-6 POWER SUPPLIES. The DTS contains three channel designation may be shown on figure 3.
UUT power supplies: one that provides a fixed 5-vdc
supply and two that supply from 0 to 36 vdc for 3-3 On figure 1, the mask pattern is not required
application to the UUT. These voltages are present on because each set of stimuli results in only one possible
the center row (voltage pins) of the rear bay assembly. UUT response unless the UUT is malfunctioning. The
The four voltage pins labeled D20 (Power Supply mask pattern is utilized in applications where several
Module A2A1PS1) are the voltage and sense lines for UUT outputs exist, the state of which is insignificant to
the fixed 5-vdc supply; the four voltage pins labeled D18 certain sets of input stimulus vectors. When only one
(Power Supply Module A2A2PS2) are for the UUT response exists, the programmer applies a stimulus
programmable power supplies. The programmable of logic 0 to channel 0 and logic 1 to channel 1. The
power supplies are programmable from 0 to 36 vdc with response from the AND gate should be logic 0. The
a 10-bit digital word at a resolution of 0.1 vdc per bit. programmer selects channel 2 as the measurement
return and establishes logic 0 as the correct response.
Based on this programmed measured response, the
DTS decides if the test is a go or no go.
FIGURE 10. Example of a support equipment principles of operation work package - continued.
84
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
AT-820FT-S78-010 005 00
15 January 1995
INTERMEDIATE MAINTENANCE
OPERATION INSTRUCTIONS
Reference Material
CONTROL POSITION
INPUT POWER DRAWER
115VAC 600 Hz MAIN POWER circuit breaker OFF
115VAC 400 Hz AFTA POWER circuit breaker OFF (74D053000-1001, -1003, -1005, AND -1009)
115VAC 400 Hz WRA POWER circuit breaker OFF
28VDC WRA POWER circuit breaker OFF
COCKPIT SIMLUATION DRAWER
SYSTEM POWER switch STANDBY
WRA POWER switch OFF
WRA COOLING switch OFF
1-3 START-UP PROCEDURE. To begin operation of IATS AIRISM, do the substeps below:
1. Lift switch cover and turn on the 115VAC 60 Hz MAIN POWER circuit breaker, located on the Input Power Drawer
Assembly, to apply power to the system. The cooling fans should turn on.
NOTE
2. On 74D053000-1001, -1003, -1005, and -1009, lift switch cover and turn on the 115VAC 400 Hz 3 Phase AFTA
POWER circuit breaker, located on the Input Power Drawer Assembly, to apply power to the AFTA.
3. Lift switch cover on the 115VAC 400 Hz 3 Phase WRA POWER circuit breaker, located on the Input Power Drawer
Assembly, to apply power to the UUT Interface Drawer for distribution to the WRA under test.
4. Lift switch cover and turn on the 28VDC WRA POWER circuit breaker, located on the Input Power Drawer Assembly,
to apply power to the UUT Interface Drawer for distribution to the WRA under test.
5. On 74D053000-1001, wait for the 115VAC 400 Hz, and 28VDC WRA POWER MONITOR lamps to illuminate
indicating power tolerance.
85
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
AT-820FT-S78-010 005 00
6. On 74D053000-1003, -1005, -1009 and -1027 wait for the 115VAC 400 Hz, and 28VDC WRA POWER
MONITOR lamps, located on both the AIRSIM and HALF RACK, to illuminate, indicating proper tolerance.
7. Apply system power by pressing the SYSTEM POWER switch, located on the Cockpit Simulation Drawer, until
the switch illuminates OPERATE.
8. Apply WRA power by pressing the WRA POWER switch, located on the Cockpit Simulation Drawer, until the
switch illuminates ON.
9. If required, apply WRA cooling power by pressing the WRA COOLING switch, located on the Cockpit Simulation
Drawer, until the switch illuminates ON.
10. On 74D053000-1001, after system power is applied, the operating system retrieves the proper program and the
main menu appears indicating that the AIRSIM is ready for use. Refer to tables 2 thru 4 for startup, tables 7 and 8
for EBIT and operating menu readouts.
11. On 74D053000-1003, -1005, -1009 and -1027 after system power is applied, the operating system retrieves the
proper program and asks the user if the Half Rack is required.
a. If the Half Rack is required, or the operator does not answer the question within a specified period of time, the
operating system will initialize the Half Rack and load the appropriate programs into the Half Rack computer.
b. If the user answers no, then the main menu appears indicating that the AIRSIM is ready for use. Refer to
tables 2 thru 8 for startup and operating menu readouts.
Any text which is underlined on the plasma display may be selected and indicates that further
instructions will follow.
NOTE
The UTILITIES menu can also be selected to run certain disk and setup programs prior to WRA
testing.
3. Select the desired EBIT test on the page 2 menu. Messages and results will be displayed while the test is in
progress. Refer to tables 6, 7 and 8 for screen layout.
1-5 SHUTDOWN PROCEDURE. After testing is complete or prior to disconnecting IATS AIRSIM from facility power,
do the following:
1. Turn off WRA power by pressing WRA POWER switch, located on the Cockpit Simulation Drawer, until the
switch illuminates OFF.
2. If operating, turn off WRA cooling by pressing WRA COOLING switch, located on the Cockpit Simulation
Drawer, until the switch illuminates OFF.
86
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
AT-820FT-S78-010 005 00
3. Turn off system power by pressing SYSTEM POWER switch, located on the Cockpit Simulation Drawer, until the
switch illuminates STANDBY.
4. Turn off the 28VDC WRA POWER circuit breaker, located on the Input Power Drawer, by lowering the switch
guard.
5. Turn off the 115VAC 400 Hz 3 Phase WRA POWER circuit breaker, located on the Input Power Drawer, by
lowering the switch guard.
6. On 74D053000-1001, -1003, -1005, and -1009 if AFTA power is on, turn off the 115VAC 400 Hz 3 Phase AFTA
POWER circuit breaker, located on the Input Power Drawer, by lowering the switch guard.
7. Turn off the 115VAC 60 Hz MAIN POWER circuit breaker, located on the Input Power Drawer, to remove all
power from the IATS AIRSIM.
1. On 74D053000-1001, -1003, -1005, and -1009, if the IATS must be shut down during normal operation to prevent
damage to equipment or personnel, the 115VAC MAIN POWER circuit breaker and the 115VAC AFTA POWER
circuit breaker, located on the Input Power Drawer, may be shut off by lowering the switch guard. Turn off all other
circuit breakers before reapplying 115VA MAIN POWER.
2. On 74D053000-1027, if the IATS must be shut down during normal operation to prevent damage to equipment or
personnel, the EMERGENCY STOP button on the Cockpit Simulation I drawer may be pressed. The circuit
breakers will automatically trip to the off position.
87
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
ORGANIZATIONAL MAINTENANCE
OPERATION DATA
SOFTWARE LOADING
S-3A
Reference Material
1-1 INTRODUCTION
1-2 This WP provides the maintenance technician with the necessary information to initialize, load, and execute the System
Test Program. Included in this work package is the PRE-POWER check list, avionics circuit breakers by system, TP load fault
procedures, and pertinent safety precautions. Also tables and figures are provided where applicable.
2-2 Perform PRE-POWER check outlined in table 1-1 upon entering aircraft.
WARNING
Do not connect external power before ensuring that sonobuoy safety switch is in open position, or during fueling,
defueling, on-loading, or off-loading weapons. Before turning on electrical power, ensure that all electrical access
panels are closed and personnel have been alerted that electrical power will be turned on.
CAUTION
Ground air conditioning must be applied (NAVAIR 01-S3AAA-2-1) if internal avionics is operated for longer
than:
If temperature can be measured in area between ADP and GPDC, the permissible temperature is 80 degrees (68 degrees
ambient + 12 degrees rise in internal bay = 80 degrees).
88
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3-2 At TACCO station POWER CONTROL PANEL, momentarily operate COMPUTER RESTART switch to ON.
When "SELECTION LOAD" is displayed, the following options are available:
SEL PROGRAM
1. OPERATIONAL
2. OPERATIONAL CONT
3. IFSTP
4. SYSTEM TEST
5. GPDC DIAG RECYCLE
6. TAPE COPY
NOTE
To ensure GPDC has attempted all possible load paths, wait 5 minutes after initiating RESTART for SELECTION
LOAD cue before reinitiating RESTART switch. If SELECTION LOAD is not displayed within 5 minutes, refer to
Paragraph 6-8 (NO SELECTION LOAD).
1. Select SYSTEM TEST by depressing numeric key 4 and ENTER on TACCO, SENSO, or Copilot INCOS. The
following cue will be displayed:
SELECTION LOAD
GPDC DIAG LOAD
DISPLAYS GOING BLANK
FOR UP TO 250 SEC
NOTE
If an STP Load failure occurs or the GPDC Diagnostic fails, record the fault isolation data and refer to paragraph 6-
10 or 6-12 for verification and possible work around.
2. After completion of GPDC Diagnostics, the Acoustic Data Processor (ADP) Program Load and Verification (PL+V)
subtest initiated. The following cue is displayed:
6-2 A transmission error occurs when the GPDC receives an illegal response from a peripheral. The total count of transmission
errors is displayed at completion of a SAT. An excessive number is indicative of an impending inability to communicate
properly with the General Purpose Digital Computer (GPDC).
89
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 003 00
1 May 1997
ORGANIZATIONAL MAINTENANCE
1-1 INTRODUCTION
1-2 All built-in test (BIT) maintenance codes are identified in this work package (table 1). A description, the related system, and
the recommended maintenance action are provided for each maintenance code.
1-3 When flag note and/or hexagonal box instructions are associated with a maintenance code, the instructions are to be done
before the recommended maintenance action.
1-4 Letters in the code column identify unique requirements for setting some codes:
1. M – Maintenance BIT
2. I – Initiated BIT
3. P – Periodic BIT
4. A – Weight Off Wheels
5. G – Weight On Wheels
6. F – Fluids Test
1-5 Some maintenance codes have entries in the Possible Related Indications column. These can be fault indications
provided by BIT or operator observations, depending on the type of failure. The possible related indications are
considered corrected when the maintenance codes are cleared. Clearing of maintenance codes is done after corrective
action or when corrective action is to ignore the maintenance code.
1-6 All caution line indications occur with LH advisory and threat warning indicator panel MASTER CAUTION light on and
master caution audio. See descriptions of cautions (WP 004 00).
NOTE
Before troubleshooting any Digital Data Computer 1 and/or 2 cautions, make sure Electrical Equipment
Rack (on 163427 thru 164279); also 164627 thru 164897 before F/A-18 AFC 11; MT-4955/APG-65
(A1-F18AC-742-300); on 164898 and up; also 164627 thru 164897 after F/A-18 AFC 211; MT-6809/APG-73
(A1-F18AH-742-300) is not disconnected or removed from the aircraft.
90
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 003 00
Avionic Mux Bus fail code set with no built-in test MUX FAIL displayed indicates that the mission computer is able to
communicate with the system terminal on only one avionic mux bus (X or Y). Normal system operation may continue,
but mux communication has lost one-half of its redundancy. Loss of the remaining mux bus may result in MUX FAIL
and the operational failure or degradation of the system.
2-2 When multiple avionic mux bus fail maintenance codes (001 thru 030, and 062) exist, malfunction can be caused by
defective avionic mux bus wiring. Using combinations of maintenance codes, tables 2 and 3 provide maintenance actions for
isolation of defective avionic mux bus 1x/1y or 2x/2y wiring. Multiple failures on mux bus 4x/4y, 5x/5y, or 6x/6y should be fault
isolated by analysis of the failure pattern/order using mux bus schematics of the A1-F18A ()-WDM-000 or A1-F18AE-741-500.
2-3 AVIONIC MUX BUS 1 FAILS. Table 2 lists the avionic mux bus fail maintenance codes for the components listed below:
6. Roll-Pitch-Yaw Computer
NOTE
Avionics mux terminals must be installed and turned on to be tested for mux bux failure. When using tables to
analyze mux failures, terminals not installed or not turned on should be considered in determining multiple failure
pattern.
2-4 When more than one avionic mux bus 1 fail maintenance code exists, do the maintenance action in table 2 for that
combination of codes. When an avionic mux bus fail maintenance code combination exists that is not listed in table 2, do the
maintenance action prescribed in table 1 for each maintenance code.
91
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 003 00
Table 1. Maintenance Codes
NOTE
Avionic Mux Bus fail code set with no built-in test MUX FAIL displayed indicates that the
mission computer is able to communicate with the system terminal on only one avionic mux
bus (X or Y). Normal system operation may continue, but mux communication has lost one-
half of its redundancy and loss of the remaining mux bus will result in MUX FAIL and the
operational failure or degradation of the system.
001 2 Air Data Computer Avionic Mux Bus lx/ly fail Digital Display Indicator
(Air Data Computer System) ADV-BIT
ADC BIT status message –
Replace Air Data Computer CP – 1334A/A, MUX FAIL
(A1-F18AC-560-300)
NOTE
Avionic Mux Bus fail code set with no built-in test MUX FAIL displayed indicates that the
mission computer is able to communicate with the system terminal on only one avionic mux
bus (X or Y). Normal system operation may continue, but mux communication has lost one-
half of its redundancy and loss of the remaining mux bus will result in MUX FAIL and the
operational failure or degradation of the system.
92
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FRM-000 004 00
ORGANIZATIONAL MAINTENANCE
1-1 INTRODUCTION
1-2 This work package contains warning, caution, advisory, fault indicator locations, and voice alert messages. It also lists
failure indications and describes the logic which causes the indication.
1-3 Table 1 describes voice alert messages sent to the pilot’s headset for critical aircraft cautions and warnings. In addition
to the voice alert messages, references are provided to other caution/warning indications related to the voice alerts.
1-5 Tables 2 through 16 and figures 29 and 30 describe fault indicators, list the related Digital Display Indicator ID-
2150/ASM-612 maintenance (maint) codes, and provide the maintenance actions for the fault indicators. When a fault
indicator and the related maintenance code exist, do the maintenance action prescribed. When a fault indicator exists and the
related maintenance code does not exist, reset and ignore the fault indicator.
1-6 Tables 17 to 27 and figure 29 describe indicator panel indications and miscellaneous cockpit indications and provide
schematic references for troubleshooting aid.
1-7 Figure 27 describes cautions and advisories which appear on the cockpit digital display indicators. In addition to the
descriptions, reference codes, schematic references, and troubleshooting references, maintenance actions are provided.
Reference codes are provided with each caution and advisory for entry points to operational flight program logic diagrams (A1-
F18AC-OLD-000). The schematic references are listed to provide the maintenance technician with a troubleshooting aid.
Troubleshooting references or specific maintenance actions are listed to aid in repairing the malfunction.
NOTE
Intercommunication and Audio System Functional Schematic
(A1-F18AC-600-500) may be used as an aid in troubleshooting if
required.
WARNINGS
"Altitude, Altitude" Indicates aircraft radar altitude below index setting
(index 1, fig 21) on Height Indicator ID-2163/A (fig
21) or aircraft barometric altitude is below setting
entered by way of Electronic Equipment Control C-
10380/ASQ (UFC). Voice alert set when low altitude
warning light (index 3, fig 21) on for radar altitude
or when aircraft is below barometric altitude setting
(WARN ALT, WP 009 00), fig. 1).
"Engine Fire Left, Engine Fire Left" Indicates fire in left engine/AMAD bay. Voice alert
set when FIRE (index 1, fig 17) indicator on.
93
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FRM-000 004 00
Table 2. Cockpit WRA Fault Indicators
RELATED
INDEX MALFUNCTION MAINT. CODE MAINTENANCE ACTION
1 Head-Up Display AN/AVQ-28 fault 098 Replace Head-Up Display Unit
indicator AN/AVQ-28 (A1-F18AC-745-
latched (black and white) 300)
2 Right Digital Display Indicator fault 096 Replace Right Digital Display
indicator latched (black and white) Indicator IP-1317/A
(A1-F18AC-745-300).
4 Left Digital Display Indicator fault 095 Replace Left Digital Display
indicator latched (black and white) Indicator (A1-F19AC-745-300).
8 Rear Left Digital Display Indicator 099 Replace Rear Left Digital
IP-1318() fault indicator Display Indicator IP-1318 ( )
latched (black and white) (A1-F18AC-745-300).
9 Rear Right Digital Display Indicator 100 Replace Rear Right Digital
IP-1318 ( ) fault indicator latched Display Indicator IP-1318 ( )
(black and white) (A1-F18AC-745-300).
10 Rear Center Digital Display Indicator 101 Replace Rear Center Digital
IP-1318 () fault indicator latched Display Indicator IP-1318 ( )
(black and white) (A1-F18AC-745-300).
94
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FRM-000 004 00
95
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FRM-000 004 00
96
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 005 00
1 May 1997
ORGANIZATIONAL MAINTENANCE
FAULT DESCRIPTOR
F/A-18 AFC-126 Addition of (DFIRS) Deployable Flight 1 Jun 92 ECP Coverage Only
Incident Recorder Set (ECP 321R1C1)
F/A-18 AFC-185 Incorporation of Have Quick Singars 15 Sep 94 ECP Coverage Only
(ECP MDA-F/A18-0292R1A3R2)
F/A-18 AFC-211 AN/APG-65, Replacement with AN/APG 1 Dec 95 ECP Coverage Only
-73 (ECP MDA-F/A-18-00508)
1-1 INTRODUCTION
1-2 This work package contains descriptions of reported malfunctions and related maintenance codes listed by system. The
action to take for each fault descriptor is listed along with other data pertinent to that descriptor. Faults are listed only when no
correlating maintenance codes exist. The maintenance codes listed by system may be used as an aid in relating reported
malfunctions to maintenance codes. When a maintenance code and reported malfunction exist for a system or subsystem, perform
the maintenance action for the maintenance code(s) (WP 003 00) first.
1-3 When a fault descriptor does not exist or the Maintenance Action column directs the user back to a functional test, do
Beyond BIT Troubleshooting (WP 002 01).
Cockpit utility and floodlights failure Do cockpit Utility and Floodlights Test
(A1-F18AC-240-200).
1
FIGURE 15. Example of a fault descriptor work package.
97
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 005 00
Table 1. Lighting System (Cont)
On F/A-18D, rear cockpit instrument lights failure Do Rear Cockpit Instrument Lights Test
(A1-F19AC-440-200).
On F/A-18D, rear cockpit console lights failure Do Rear Cockpit Console Lights Test
(A1-F18AC-440-200).
On F/A-18D, rear cockpit utility and floodlights Do Rear Cockpit Utility and Floodlights Test
failure (A1-F18AC-440.200).
98
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 007 00
1 May 1997
ORGANIZATIONAL MAINTENANCE
Reference Material
F/A-18 AFC-211 AN/APG-65, Replacement with AN/ 1 Dec 95 ECP Coverage Only
APG-73 (ECP MDA –F/A-18-00508)
1-1 INTRODUCTION
1-2 This work package contains illustrations and descriptions (table 1) of the display elements common to HUD displays. The
illustrations are not meant to represent typical displays, but to provide general appearance and positioning of the elements which
make up HUD displays. The descriptions may contain schematic references which show the development of the display
elements.
Table 1. HUD Display Symbology Descriptions
1 Heading Magnetic heading displayed when valid and indicated on moving 30° scale.
Moving scale provides trend information during turns. Not displayed when HUD
REJ 2 selected. (Navigation Attitude and Heading Functional Schematic, A1-
F18AC-730-500).
2 Data 1. The DL command heading symbol is displayed in vector mode when vector
Link/WYPT/ data is valid, command heading is valid, and heading is displayed. (Vector
Oap Command Mode Coupled Heading Functional Schematic, A1-F18AC-630-510/(C).
Heading
2. The waypoint/offset aimpoint command heading is displayed when WYPT
or OAP steering is selected. Provides steering to the selected WYPT/OAP.
When a target or OAP has been designated, symbol is replaced by diamond
(Bombing/navigation Functional Schematic, A1-F18AC-730-500).
3 Altitude 1. With ALT switch in BARO, barometric altitude is displayed in a box when
valid (Air Date Computer System Functional Schematic, A1-F18AC-560-
500).
2. With ALT switch in RDR, radar altitude is displayed in a box and identified
by an R next to the box. When RDR selected but not valid, barometric
altitude is displayed with a flashing B replacing the R.
1
99
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 007 00
Table 1. HUD Display Symbology Descriptions (Cont)
INDEX DISPLAY DESCRIPTION
NO. ELEMENT
(REF CODE)
If barometric altitude also not valid, only flashing B is displayed.
1 If the barometric altitude source error correction is invalid, an X will be displayed
next to the uncorrected barometric altitude.
The thousand and ten thousand digits are larger than the tens, hundreds, and units
(XX,xxx). When altitude less than 1000 feet, all digits are the same size (XXX). Box is
removed when HUD REJ 1 selected (Electronic Altimeter System Functional
Schematic, A1-F18AC-600-500).
4 Barometric The barometric setting displays the value set in the Standby Pressure Altimeter AAU-
Setting 39A. When the setting is changed, the new value is displayed for 5 seconds. It is also
displayed and flashed for 5 seconds when aircraft altitude is below 10,000 feet and
airspeed below 300 knots, after having been above both values (Air Data Computer
System Functional Schematic, A1-F18AC-560-500).
5 Data Link DL message discretes which appear in this area in vector mode are DATA,
Discretes/ TILT, ad DISENGAGE (Vector Mode Command Data Functional Schematic,A1-
Advisories F18AC-630-510/( C ).
6 Data Link CPL HDG displayed when FCS is coupled to data link vector mode heading
Discretes/ command. Flashed for 10 seconds, then removed when couple unsuccessful or
Advisories uncouple occurs when not commanded (Vector Mode Couple Heading Functional
Schematic, A1-F18AC-630-510/( C ).
7 Nosewheel NWS is displayed when nosewheel steering is engaged and weight on wheels.
Steering Case When high gain mode selected, NWS HI is displayed (Nosewheel Steering Functional
Schematic, A1-F-18AC-570-500).
DISPENSE Displayed to indicate that a threat has been detected and operator action is
4 required to dispense countermeasures.
8 Destination Steering destination range numerics, destination type, and destination number are displayed
Range in NAV and A/G modes. When waypoint steering is selected and the current waypoint has
offsets, the range to the OAP, the letter O, and the OAP number are displayed. When
waypoint steering is selected and the current waypoint or mark does not have offsets, range
numerics, W (waypoint) or M (mark) and the waypoint or mark number are displayed.
When a target is designated, target range and TGT are displayed. TACAN steering is
indicated by displaying TACAN range and TACAN station identification. Display removed
when HUD REJ 2 selected (Navigation Velocity and Position Keeping Functional
Schematic, A1-F18AC-730-500).
100
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AE-FRM-000 007 00
101
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FIM-000 084 00
15 December 1997
ORGANIZATIONAL MAINTENANCE
TROUBLESHOOTING PROCEDURE
Reference Material
Multimeter AN/USM-311
NOTE
NOTE
Aircraft Wiring
Engine Bleed Air Secondary Pressure Regulating and Shutoff Valve
Left Engine Bleed Air Pressure Regulating Shutoff Valve
No. 4 Relay Panel Assembly
Right Engine Bleed Air Pressure Regulating and Shutoff Valve
Secondary Bleed Air Overpressure Switch
102
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FIM-000 084 00
Table 1. Code 833 or Codes 832 and 833 (Cont)
PROCEDURE NO YES
CAUTION
To prevent damage to low level devices (switches/relay contacts), do not test for
continuity with multimeter on the RX1 scale. Pin to pin tests that do not go through
switches/relay contacts may use RX1 scale.
NOTE
The question used in logic tree "Does continuity exist" means to test for the items listed
below:
1. Do substeps below:
2. Do substeps below:
3. Replace secondary bleed air overpressure switch (A1-F18AC-410-300) and do step 11. - -
4. Do substeps below:
FIGURE 17. Example of a fault isolation troubleshooting procedure work package - continued.
103
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-FIM-000 084 00
Table 1. Code 833 or Codes 832 and 833 (Cont)
PROCEDURE NO YES
6. Isolate between no. 4 replay panel assembly wiring and relay 22K-N046
(A1-F18AC-420-300) and do step 11. - -
7. Do substeps below:
8. Replace right engine bleed air pressure regulating and shutoff valve
(A1-18AC-410-300) and engine bleed air secondary pressure regulating and
shutoff valve (A1-F18AC-410-300) and do step 11.
9. Do substeps below:
10. Replace left engine bleed air pressure regulating and shutoff valve (A1-F18AC-410-300, - -
F18AC-410-300) and do step 11.
11. If disconnected, removed, or opened during this procedure, make sure the items listed below - -
are connected, installed, or closed:
FIGURE 17. Example of a fault isolation troubleshooting procedure work package - continued.
104
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 00
15 August 1995
ORGANIZATIONAL MAINTENANCE
OPERATIONAL CHECKOUT
Reference Material
1-2 Arresting gear operational test (table 1) is used to verify correct operation of arresting gear system and that the cockpit
indicating light above the arresting HOOK manual control lever is functioning correctly with respect to hook position. For
component locator, refer to figure 1. The test must be completed in sequence given and any abnormal indication must be
corrected before going to the next step. The following prerequisite conditions must be followed:
WARNING
To prevent loss of or damage to aircraft, precise arresting hook servicing is mandatory for correct
system operation.
CAUTION
To prevent damage to aircraft, door 103 must be installed before arresting hook is extended or retracted.
105
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 00
Table 1. Arresting Gear System Operational Test (Cont)
PROCEDURE NORMAL INDICATION REMEDY FOR
ABNORMAL INDICATION
1. Make sure door 103 is in-
stalled (A1-F18AC-LMM-
010).
6. Read, record and reset nose No maintenance code exists. Do procedures specified in table 2.
wheelwell DDI (A1-F18AC-
LMM-000).
7. If arresting hook is not up, Arresting hook latches in up posi- Do arresting hook push-pull con-
manually raise and latch tion. trol assembly rigging or replace
arresting hook. push-pull control assembly (A1-
F18AC-130-000).
8. Do ground intercommunica- Arresting HOOK control advisory Arresting HOOK control advisory
tions hookup using external light off. light on with arresting HOOK
electrical power (A1-F18AC- manual control lever l and arrest-
LMM-000). ing hook up. Refer to table 1
(WP 010 01).
9. On INTR LT control box Arresting HOOK control advisory Arresting Hook control advisory
panel assembly, set LT TEST light comes on. light does not come on when LT
switch to TEST. TEST switch on INTR LT control
box panel assembly is set to TEST.
Refer to table 2 (WP 010 01).
106
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 00
Table 1. Arresting Gear System Operational Test (Cont)
PROCEDURE NORMAL INDICATION REMEDY FOR
ABNORMAL INDICATION
WARNING
12. Using stop watch, measure time 1. Arresting hook assembly releases 1. Arresting HOOK manual control
required to lower arresting hook and lowers in 2.5 seconds lever will not move to down
assembly. Set arresting HOOK maximum. position. Refer to table 3 (WP 010
manual control to down. 01).
107
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 05
1 June 1997
ORGANIZATIONAL MAINTENANCE
TROUBLESHOOTING
Reference Material
NOTE
Arresting Gear Schematic (A1-F18AC-130-500) may be used as an aid when doing this
procedure.
NOTE
Aircraft Wiring
Arresting Hook Up Switch
Arresting Hook Up Switch Rigging
Signal Data Computer CP-1726/ASQ-194
Temperature Compensated Pressure Switch
108
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 05
Table 1. 916 Code Displayed With Arresting Hook Actuator Properly Serviced
PROCEDURE NO YES
CAUTION
NOTE
The question used in logic tree "Does continuity exist" means to test for the items listed below:
1. Do substeps below:
d. Does continuity exist between 85P-F042D pin 41 and aircraft ground? .......................................... 2 5
2. Do steps below:
a. Manually raise speed brake and install speed brake aircraft ground safety lock
(A1-F18AC-PCM-000).
3. Does continuity exist between 19P-T012 pin 4 and aircraft ground? ....................................................... 8 4
4. Does continuity exist between 85P-F042D pin 41 and 19P-T012 pin 3?................................................. 9 12
5. Does an open circuit exist between 85P-F042D pin 46 and aircraft ground? ........................................... 10 6
FIGURE 19. Example of a troubleshooting procedures text-logic format work package - continued.
109
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-130-200 010 00
Table 1. 916 Code Displayed With Arresting Hook Actuator Properly Serviced (Cont)
PROCEDURE NO YES
6. Do steps below:
CAUTION
To prevent damage to aircraft, door 103 must be installed before arresting hook is extended
or retracted.
c. Does continuity exist between 85P-F042D pin 46 and aircraft ground? ....................................... 11 12
FIGURE 19. Example of a troubleshooting procedures text-logic format work package - continued.
110
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
AT-820YA-LTS-000 010 00
1 July 1997
Reference Material
1-1 INTRODUCTION
1-2 This work package (WP) provides the instructions for troubleshooting the Laser Target Simulator SMU-127/E (LTS).
2-1 TROUBLESHOOTING
2-2 Troubleshooting on the LTS is based on fault isolation. Refer to table 1 and figures 3 and 4 for general LTS system faults.
The following paragraphs deal with problems specific to the cables and power supplies. For removal/installation of any faulty
components, refer to WP 008 00.
WARNING
1. Set POWER ON/OFF switch S1 to OFF position and remove power cable W1 from facility power.
2. Cable continuity is checked through the use of a digital multimeter. Verify the wiring connections illustrated in figures
5 through 7 for cables W1-W3 and figure 8 for the power supply cable. Repair as needed (WP 008 00).
111
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
AT-820YA-LTS-000 010 00
Table 1. Laser Target Simulator Troubleshooting Procedures (Cont)
FIGURE 20. Example of a troubleshooting procedures tabular format work package - continued.
112
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-216PA-120-000 005 00
31 October 1996
AFC 429 1 May 1995 Electrical, Night Vision Goggle 28 Jun 1996
Revision B Compatible Cockpit Installation
(ECP PN37R1)
1-2 Testing and troubleshooting includes pretest setup, operational checkout, and troubleshooting procedures. Circled
uppercase letters key the malfunction symptoms to appropriate troubleshooting procedures provided in figure 1. Troubleshooting
procedures assume there is but one malfunction at a time. After all repairs are made, the operational checkout should be restarted
to make sure that the replacement did not introduce a new malfunction. Successful completion of the operational checkout
verifies proper operation of the equipment.
FIGURE 21. Example of a combined operational checkout and troubleshooting procedures logic flow
diagram format work package.
113
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-216PA-120-000 005 00
3-1 OPERATIONAL CHECKOUT
CAUTION
Do not go over 5 vac to control panel, as damage to panel lamps may result.
1. Increase variable transformer output from 0 to 5 vac. Check that information plate assembly lamps increase uniformly
to full brilliance.
WARNING
Make sure power supply is off before connecting and disconnecting leads from control
panel as injury to personnel or damage to equipment may occur.
3. With power supply adjusted for 28 vdc output, connect negative lead to P94-a and positive lead to P94-A. Check that
TURN RATE, NORM or ALT indicator lamps go on.
4. Press TURN RATE switch. Check that opposite indicator lamps go on.
5. Press TURN RATE switch so that NORM indicator lamps are on.
4-2 Troubleshooting procedures are provided in figure 1 and are keyed to the operational checkout results contained in
paragraph 3-1.
FIGURE 21. Example of a combined operational checkout and troubleshooting procedures logic flow
diagram format work package - continued.
114
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-216PA-120-000 005 00
FIGURE 21. Example of a combined operational checkout and troubleshooting procedures logic flow
diagram format work package - continued.
115
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-216PA-120-000 005 00
FIGURE 21. Example of a combined operational checkout and troubleshooting procedures logic flow
diagram format work package - continued.
116
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-T700A-MMI-200 005 00
1 July 1995
INTERMEDIATE MAINTENANCE
Reference Material
Materials Required
Gloves, Protective -- --
Gloves, Rubber ZZ-G-381, Type I --
Gloves, Thermally Insulated 9123T12 --
Goggles -- --
Machinery Towels DDD-T-541 --
Solvent, Dry Cleaning P-D-680 (81348) --
1-1 INTRODUCTION
1-2 This work package contains standard general maintenance procedures, miscellaneous inspections, and servicing
information.
1. To prevent damage to parts and injury to personnel, always use a hoist and recommended special lifting slings and
adapters to lift heavy parts and assemblies. Use proper tools and procedures at all times.
2. Use only the special tools and fixtures specified in this manual to remove/disassemble the engine. Careless
handling or improper use of tools or procedures can cause damage to engine parts, resulting in rejection of costly
parts at inspection or serious engine malfunctions.
3. Do not leave tools on any part of an assembly during disassembly operations. After using each tool, return it to its
proper storage place.
4. Avoid the use of makeshift tools. Special tools are identified by name and part number when they are required.
5. Visually inspect all tooling for damage or contamination before using the tool. Wipe tools with machinery towels
DDD-R-541, as required.
6. Do not use force to remove parts. If difficulty is encountered, remove tooling and determine cause of trouble
before proceeding.
7. When using a hydraulic pump to remove parts, stop the pumping operation if the needle on the gage enters the
danger area.
8. Do not use metal-head hammers on any part of the engine. Plastic, nylon, or rawhide-head hammers should be
used on parts.
117
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-T700A-MMI-200 005 00
3-1 CLEANING PRACTICES
NOTE
Cleaning of engine parts is necessary to permit adequate detailed inspection and subsequent repair of material
defects. The cleaner the parts, the more reliable will be the inspection.
1. Cap all openings and tube ends before and after cleaning a part to prevent contaminations from entering internal
passages.
3. To avoid corrosion, do not handle parts with bare hands if protective coatings have been removed.
4. Be sure that cleaning facilities provide for safety of operating personnel. The cleaning area should be clean and well-
ventilated.
5. Process each part only as long as necessary to clean the part adequately. The processing times specified in the cleaning
procedures are not absolutes and should be used only as guides.
4-2 PRELIMINARY INSTRUCTIONS. Before connecting electrical connectors, inspect for the following:
WARNING
Heat from oven or from hot parts can cause reddening and blistering of skin (or third degree burns) if hands are not
protected.
If skin is burned, immerse contacted area in cold water for 10 minutes If pain or blistering persists, immediately get
medical attention.
Use approved protective gloves when putting parts in or taking parts out of hot oven.
1. Inspect connectors (plugs and receptacles) to be sure they are free of moisture. If moisture is found, remove harness or
component and bake dry at 250oF for 2 hours. Using thermally insulated gloves, remove harness or component from
oven.
2. Inspect connectors to be sure they are clean and free of fuel and oil. If not, clean and dry them (WP 015 00).
3. Inspect all connectors for bent pins. If bent pins are found, refer to applicable inspection table for repair limits.
4. All electrical connectors should be installed dry. Do not lubricate seals or threads.
118
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-LMM-000 025 00
15 April 1996
ORGANIZATIONAL MAINTENANCE
Reference Material
1-1 SERVICING
WARNING
To prevent death or injury to personnel, always go toward MLG tire from forward or aft direction, never from
the side. Never go near MLG tire if suspected to be overheated because of long taxi or continued brake
application.
2. Service MLG tire (NAVAIR 04-10-506) to correct inflation pressure per substeps below:
a. If mission is to start, stop over or end on an aircraft carrier, inflate MLG tires to 345 to 355 psig.
b. If mission includes only ashore operations on semiprepared fields, inflate MLG tires to 245 to 255 psig.
c. If mission includes only ashore operations on prepared fields, inflate MLG tires to 245 to 255 psig.
119
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F404A-MMD-300 007 00
1 October 1991
DEPOT MAINTENANCE
MAINTENANCE
SUPPORT EQUIPMENT
Materials Required
1-1 INTRODUCTION
1-2 This work package (WP) contains information for the proper care and maintenance of the support equipment (tools)
provisioned for depot maintenance of the F404 engine. Because most of the tools are precision-made, they should be carefully
handled, properly maintained, and periodically inspected.
1. Use plastic or rawhide (never metal) hammer heads when driving on any of the pushers. Apply force evenly to all
bearing pushers or pullers.
2. Tighten jackscrews, bolts, and nuts in small increments on opposite planes. This is called cross-torquing.
3. Wipe tools clean before using them on the engine. Always use lint-free (Kim-Wipes) wipers for this purpose.
4. Always use the correct size wrench (or socket) to turn or tighten a tool, locknut, or bolt.
5. Never leave tools or gages on benches, engines, etc., where they could fall and be damaged.
1. Clean and lubricate all tools before returning them to the storage box or container.
2. Always store tools in their respective storage box or container (if provided). Otherwise, store in a clean, dry area.
2. Measuring type tools, such as torque wrenches and dial indicators that have been dropped, should be calibrated before
they are used again.
120
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F404A-MMD-300 007 00
5-1 SHIPMENT OF TOOLS
1. Wipe tools with a cloth treated with lubricating oil MIL-L-23699 or MIL-L-7808 before shipment.
2. Ship tools in their storage box or container (if provided). Package tools securely before shipment to prevent damage.
3. To protect tools against corrosion, ship tools in rigid, air-tight containers, or in air-tight, plastic (general purpose) bags.
Include desiccant MIL-D-3464.
6-2 Knowing when to service tools is as important as knowing how to service them. It is important that these tools be removed
from service when lubrication is required and when it is known, or there is reason to believe, they:
2. Inspect tools for high metal, cracks, or other visible defects which might keep them from working properly. Tools
having defects should either be repaired or replaced before using to avoid damaging engine parts.
8-2 Support equipment used for maintenance is protected against corrosion by use of paint, electroless nickel plate, or anodize.
These finishes will adequately protect the exposed surfaces against the formation of rust under normal conditions. However,
prolonged exposure to salt-laden or high-humidity air may corrode the parent metal (including certain stainless steels) if
preventive action is not taken. Therefore, in areas where corrosion may be a problem, a semi-annual spray application of
corrosion preventive compound, MIL-C-81309, is recommended. No special procedures have to be followed to prepare
equipment before spraying or after spraying. However, unexposed surface of equipment designed to come apart should also be
sprayed.
2
121
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
INTERMEDIATE MAINTENANCE
MAINTENANCE
Reference Material
1-1 INTRODUCTION
1-2 This Work Package (WP) contains instructions for the local manufacture of Support Equipment used at the intermediate
levels of maintenance of the T58-GE-16 engines. A complete list of Support Equipment is available in WP 013 00.
2-2 For instructions on the calibration, care and maintenance of Support Equipment, refer to NAVAIR 02-1-20.
1. No. 2 bearing rear stationary seal support guiding pin (figure 1).
2. Static fuel filter bowl removal and installation tool (figure 2).
122
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 25. Example of a local manufacturing and assembly work package - continued.
123
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-E2C2A-QEC-000 006 00
15 June 1988
INTERMEDIATE MAINTENANCE
MAINTENANCE
E-2C (T56-A-425)
Reference Material
Materials Required
Lockwire MS20995NC32 -
1-1 INTRODUCTION
1-2 This work package (WP) provides buildup procedures for the reduction gearbox. The reduction gearbox is part of the E-2C
(T56-A-425) turboprop engine. Refer to WP 002 00 for sequence of engine buildup. Refer to WP 003 00 for general
information.
124
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-E2C2A-QEC-000 006 00
2-1 REDUCTION GEAR FRONT HOUSING-COMPONENT INSTALLATION
1. Position negative torque bracket assembly (31, figure 1) on negative torque bracket assembly mounting pad (6) on
reduction gear front housing. Insert three screws (2, figure 2) and washers (3) through negative torque bracket
assembly and into reduction gear front housing. Torque screws to 40 to 50 inch-pounds (4.5 to 5.6 N•m) and
lockwire. (QA)
2. Adjust adjusting screw (4) to obtain 0.006 to 0.015 inch (0.152 to 0.381 mm), 0.008 inch (0.203 mm) optimum
clearance between reduction gear plunger (5) and adjusting screw (4). (QA)
1/12 Bolt * 2
1/30 Torque Retainer 543641 1
(Anti-Rotation
Bracket)
1. Position torque retainer (anti-rotation bracket) (30, figure 1) on torque retainer (anti-rotation bracket) mounting pad
(7).
2. Secure torque retainer (anti-rotation bracket) (30) to torque retainer (anti-rotation bracket) mounting pad (7) with
two bolts (12). Torque bolts to 155 to 165 inch-pounds (17.5 to 18.6 N•m) and lockwire bolts. (QA)
125
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-E2C2A-QEC-000 006 00
126
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-E2C2A-QEC-000 006 00
127
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
128
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
129
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
130
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
131
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
132
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
133
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-AV8BB-SRM-200 026 00
1 October 1988
GENERAL INFORMATION
CRASH HANDLING
Reference Material
1-1 INTRODUCTION
1-2 This work package contains information for recovery of a crash damaged aircraft.
2-1 DESCRIPTION
2-2 Every crash damaged aircraft will be evaluated on an individual basis and moved depending on surrounding terrain and
aircraft condition. It may have to be raised, leveled or supported before being towed to a suitable location for further evaluation.
The following paragraphs contain typical methods for moving crash damaged aircraft.
CAUTION
Every attempt must be made to keep crash damaged aircraft from additional damage.
134
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-LMM-000 026 00
3. Make sure electrical power is removed from aircraft (A1-AV8BB-GAI-100).
5. Make sure wing stores or external fuel tanks are removed (A1-AV8BB-LWS-000).
4-2 A crashed aircraft may be in one or more of the following conditions. The determining factors will be location, amount of
time to recover, and availability of equipment. Select method that is applicable.
5-2 This paragraph contains procedures, support equipment required and materials required for recovery of an aircraft with all
landing gear collapsed.
b. Lifting
6-2 This paragraph contains procedures, support equipment required and materials required for recovery of an aircraft with the
nose landing gear collapsed.
FIGURE 28. Example of a general aircraft structural information work package - continued.
135
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-250 003 00
1 January 1995
ORGANIZATIONAL MAINTENANCE
STRUCTURE REPAIR
TYPICAL REPAIR
MATERIAL PREPARATION
Materials Required
1-1 INTRODUCTION
1-2 This work package contains the materials and mixing procedures for making typical repairs.
2-2 This adhesive is a two-part compound. Mix adhesive per steps below:
Mix only amount of materials that will be used in 40 minutes. Ambient temperatures in excess of 90°F, mix
only amount of materials that will be used in 20 minutes. To avoid exotherm, mix no more than 5 cubic
inches (approximately 100 grams) of this material at one time.
136
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-250 025 00
2. Mix the two components thoroughly until a uniform color appears.
3. Allow adhesive to set for 5 minutes for air bubble removal before application.
3-2 This adhesive is a two-part compound. Mix compound per steps below:
Mix only amount of materials that will be used in 40 minutes. Ambient temperatures in excess of 90°F, mix only
amount of materials that will be used in 20 minutes. To avoid exotherm, mix no more than 5 cubic inches
(approximately 180 grams) of this material at one time.
NOTE
3. Add 14 parts (by weight) chopped glass floc to mixed adhesive. Thoroughly mix chopped glass floc with adhesive.
4. Allow adhesive to set for 5 minutes for air bubble removal before application.
4-2 This adhesive is a two-part compound. Mix adhesive per steps below:
NOTE
Mix only the amount of material that will be used in 75 minutes. To avoid exotherm, mix no more than 250
grams of this material at one time.
3. Allow adhesive to set for 5 minutes for air bubble removal before application.
137
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
STRUCTURE REPAIR
Reference Material
1-1 INTRODUCTION
1-2 This work package contains damage evaluation, damage limits, repair index and parts and material index on the aft center
fuselage external heat shields. The external heat shields are interchangeable assemblies.
2-2 Figure 1 lists and identifies parts and materials used on the heat shield bracket assembly.
3-2 For damage evaluation of the aft center fuselage external heat shields, see the paragraphs below.
3-3 ORGANIZATIONAL. Visual inspection of dents, gouges, cracks, loose or missing fasteners, and wear at heat shield
attachments.
3-4 INTERMEDIATE. Nondestructive inspection of visible damage using ultrasonic inspection (NAVAIR 01-1A-16).
Damage evaluation past this level of maintenance will not be necessary until the structural integrity values of the heat shield are
in question.
4-2 For damage limits on the aft center fuselage external heat shields, see the paragraphs below. The limits for specified
damage will be as follows, provided the structural integrity values of the part in question are not decreased.
4-3 ORGANZATIONAL. Loose or missing fasteners will be replaced as needed. Cracks are limited to 4 inches in length
anywhere on the aft portion of the heat shield. Maximum freeplay of heat shield is 0.025, measured at aft end of each portion.
Wear that exceeds 0.025 will require repair or replacement of worn parts. Worn links/brackets/angles will be reamed to next
applicable sizes or replaced. Any worn bolts/pins/collars on the aft portion of the heat shield that are below minimum limits will
be replaced (A1-AV8BB-SRM-250).
4-4 INTERMEDIATE. Damage limits at this level of maintenance will be determined on an individual basis according to the
size and extent of repair required past the organizational level of maintenance.
1
138
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
5-2 All repairs to the external heat shields that are approved are listed below. The repairs are listed under each maintenance
level to show where the repair can be done.
5-3 ORGANIZATIONAL. Maintenance of this level will include the repairs listed below.
5-9 This repair is good on ships up to 163853. There are two types of repairs approved. One repair uses bolts and nuts, the
other uses manufactured repair pins. Both repairs can be used in any and all situations. The wear limits for links/brackets are
given in Table 1 (A1-AV8BB-SRM-250). The maximum wear limit is given in each case. Any measurement that exceeds that
limit will require the link/bracket to be reamed to the next applicable size hole, or replaced. Disconnect links at position 6, 10,
11, 14 and 15. The wear limits of the bolts/pins are given in Table 2. The minimum wear limit is given in each case. Any
measurement that drops below that limit will require replacement of the bolt/pin. For repair (A1-AV8BB-SRM-250).
5-11 Bracket No. 9 should be replaced only if the fasteners become loose. This replacement occurs only on ships 161573 thru
162973. For repairs (A1-AV8BB-SRM-250).
5-15 If attach angles on forward heat shield become worn at pin locations, the attach angle slots for pins and collars should be
oversized and fitted with nuts and bolts or replaced. For repairs (A1-AV8BB-SRM-250).
5-16 INTERMEDIATE. Maintenance at this level will include all the repairs at the organizational level. At this time there are
no specific repairs approved for this level. Repairs will be based on an individual basis.
5-17 DEPOT. Maintenance at this level will include all the repairs at the organizational and intermediate level. At this time,
there are no specific repairs approved for this level. Repairs will be based on an individual basis.
139
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
Figure 1. Heatshield Bracket Assembly, AV-8B-161573 thru 164547, TAV-8B-162747 and up (Sheet 1).
140
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
141
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-500 003 00
1 February 1995
ORGANIZATIONAL MAINTENANCE
GENERAL INFORMATION
Reference Material
Cleaning................................................................................................................................... WP 006 00
Stripping................................................................................................................................... WP 007 00
Chemical Treatment ................................................................................................................ WP 008 00
Priming Procedures ................................................................................................................. WP 011 00
Finish System........................................................................................................................... WP 012 00
Aircraft Weapons Systems Cleaning and Corrosion Control.................................................. NAVAIR 01-1A-509
Plane Captain Manual ............................................................................................................. A1-F18AC-PCM-000
Materials Required
1-1 DESCRIPTION
1-2 The F/A-18A, B, C and D aircraft are a composition of aluminum, graphite epoxy, fiberglass, titanium, and steel. The
airframe is primarily made of aluminum. Graphite epoxy composite and fiberglass are used for many skins and doors. Titanium
is also used for skins and doors. Where maximum strength is required, beta annealed bar, plate, and forgings are used. High
strength steel is used in landing and arresting gear. Hydraulic tube assemblies are titanium.
1-3 TYPES OF CORROSION. Information on types of corrosion, cause, and appearance is contained in
NAVAIR 01-1A-509.
1-4 PROTECTIV E COVERS. Protective covers are necessary to aid in protecting aircraft during non-operational times.
Protective covers are required for corrosion control. Procedures for installation and removal are contained in A1-F18AC-PCM-
000, ground protective devices.
142
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-500 003 00
2. Do not use solvents in vicinity of smoking, sparks or open flames. Flammable solvents are extremely easy to ignite
and fires may occur with explosive violence. After using flammable solvents, be certain that no traces linger on
clothes or person before entering a smoking area.
3. Wear safety glasses or goggles, and rubber gloves while working with solvent.
4. Do not smoke while working with flammable solvents or while in a no-smoking area.
5. Bare filament heaters or other sources of ignition, including metal objects on shoes, are prohibited in flammable
solvent areas. Electrical equipment, including flashlights, should be explosion proof. Avoid any action which may
create sparks, including dragging of steel drums, metal work stands or similar objects across a concrete floor.
6. Any area larger than one square foot cleaned with a cloth moistened with a flammable solvent should be grounded
during cleaning operation.
7. Isolate flammable solvent storage areas from areas of fire hazard. Electrically ground all equipment in storage area.
Electrically bond dispensing and receiving containers to each other while transferring flammable solvents between
containers.
8. Store and handle solvents in properly labeled safety containers and keep them closed while not in use.
12. When using solvents, to reduce fire/toxic hazards, only amounts needed for short period of time should be available in
work area.
13. Avoid eye/skin contact when using accelerator components because they contain reactive oxides and solvent blends
which are flammable, toxic, and irritant.
14. Avoid contact with liquid nitrogen. Skin contact will cause severe destruction of body tissue by freezing.
15. Gloves are required to handle containers after removal from liquid nitrogen.
16. Spray operators must wear respirators during spray applications. Coveralls and protective barrier cream applied to bare
skin is required for personal protection.
18. After each job, or before break periods, spray operator(s) must thoroughly wash all exposed areas of skin using soap
and water.
19. No food or drink should be allowed in or near solvent, sealant, or spray areas.
20. When using chemical treatment, protective equipment must be worn, because solution is acidic and contains fluorides.
21. Stripper specified in this manual will burn skin on contact. Adequate protective clothing, including face shield and
rubber gloves, should be worn. If stripper contacts eyes, flush with water for 15 minutes and seek medical aid.
FIGURE 31. Example of a typical corrosion control repair work package - continued.
143
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-500 003 00
1-6 MASKING
NOTE
Windshield/canopy transparencies must be double masked when cleaning (WP 006 00), stripping (WP 007 00),
chemical treatment (WP 008 00), priming procedures (WP 011 00) and finish system (WP 012 00) is applied.
1. Cut one piece of plastic sheet slightly smaller than windshield transparency.
2. Cut one piece of plastic sheet slightly smaller than canopy transparency.
3. Tape plastic sheet around periphery of surrounding structure using 425 tape.
4. Cut one piece of plastic sheet slightly larger than windshield transparency.
5. Cut one piece of plastic sheet slightly larger than canopy transparency.
6. Position periphery of plastic sheets slightly beyond previously applied plastic sheets.
7. Apply 425 tape around periphery of plastic sheets overlapping previously applied tape.
8. Make sure all seams of tape are secure to structure to prevent any damaging materials from entering.
NOTE
Nonmetallic surfaces require double masking when: cleaning (WP 006 00), stripping (WP 007 00) or
chemical treatment (WP 008 00).
1. Cut one piece of plastic sheet slightly smaller than area to be covered.
2. Tape plastic sheet around periphery of surrounding structure using 421 or MIL-T-23397 tape.
3. Cut one piece of plastic sheet slightly larger than area to be covered.
4. Position periphery of plastic sheet slightly beyond previously applied plastic sheet.
5. Apply 421 or MIL-T-23397 tape around periphery of plastic sheet overlapping previously applied tape.
6. Make sure all seams of tape are secure to structure to prevent any damaging materials from entering.
1-10 Untreated kraft paper applied with MIL-T-21595 tape is used to cover areas not receiving cleaning (WP 006 00),
stripping (WP 007 00), chemical treatment (WP 008 00), priming (WP 011 00) or finish system (WP 012 00).
NOTE
Areas too small for untreated kraft paper may be masked with MIL-T-21595 tape only.
FIGURE 31. Example of a typical corrosion control repair work package - continued.
144
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 003 00
1 December 1992
NONDESTRUCTIVE INSPECTION
GENERAL INFORMATION
Reference Material
1-1 INTRODUCTION
1-2 This work package contains information related to nondestructive inspection of aircraft structure and structural components.
Nondestructive inspection personnel should be familiar with this information because some is not repeated or referenced in
typical or specific procedure work packages, for example, frequency of nondestructive inspections.
2-2 Established inspection frequency for aircraft structure or structural components is contained in (A1-F18AC-MRC-200 or
A1-F18AE-MRC-200).
3-2 See figure 1. Defects that may develop in laminates and bonded honeycomb assemblies are shown to aid nondestructive
inspection personnel in definition of suspected defects identified in specific procedure work packages.
145
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 003 00
Figure 1. Examples of Defects That May Develop in Laminates and Bonded Honeycomb Assemblies.
FIGURE 32. Example of a nondestructive inspection general information work package - continued.
146
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 004 00
1 December 1992
ORGANIZATIONAL MAINTENANCE
NONDESTRUCTIVE INSPECTION
PENETRANT METHOD
Reference Material
Materials Required
147
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 004 00
1-1 INTRODUCTION
1-2 Penetrant inspection is nondestructive inspection for discontinuities open to surface in parts made of nonporous materials.
This is done by treating surface area with fluid which penetrates surface discontinuity. Excess penetrant not in discontinuity is
removed and penetrant remaining in discontinuity returns to surface by capillary action. Developer is applied to provide
contrasting surface, and through absorption forms indication large enough to be visible to eye. Visual indications become distinct
by fluorescence of penetrant under black light. This method is effective for detecting defects open to surface in forgings,
castings, extrusions, formed sections, webs, and skins of ferrous or nonferrous material. Penetrant method of inspection requires
surface inspection area be thoroughly cleaned and stripped of paint or other surface coatings, for example, dry film lubricant.
1. Make sure safety requirements have been met before using electrical equipment near aircraft fuel cells, oxygen
systems, and stores (A1-F18AC-PCM-000).
2. Refer to NAVAIR-01-1A-16 for other safety precautions to be followed when doing penetrant inspection.
2-2 PERSONNEL QUALIFICATIONS. Personnel doing this nondestructinve inspection should be qualified and certified to
do penetrant inspections per OPNAVINST 4790.2 SERIES, NDI Technicians, NEC 7225/MOS 6044.
1. In inspection booth, white light should be less than 2 foot-candles and black light intensity should be at least 1000
micro-watts at surface of part. When checking background white light intensity, black light must be turned off or
removed from inspection area.
2. For on-aircraft inspections, surface under inspection must be heavily shaded, and black light should be held close as
possible to ensure bright indication. To inspect lighting adequacy, use pin or other sharp object to draw thin line of
penetrant on part near inspection area. This line should be bright and distinct.
Do not do prepenetrant etching on steel parts. Acid used for etching can cause embrittlement or corrosion of critical
structure.
1. Part must have finish system removed before inspection. Refer to specific procedure work package for details. If
specific procedure work package does not exist, chemically remove finish system (A1-F18AC-SRM-500).
1,1,1-Trichloroethane, 0-T-620TY1 12
2. Clean inspection area(s) with solvent-moistened cloth to make sure inspection area(s) is free of contamination or
foreign material.
FIGURE 33. Example of a nondestructive inspection typical procedures work package - continued.
148
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 004 00
5-1 INSPECTION PROCEDURE
CAUTION
Abrasive removal of material by grinding, sanding, or polishing at crack area will cause metal to be smeared in surface of
crack resulting in hidden flaws. If inspection surface has been mechanically worked before inspection but after most recent
aircraft flight, penetrant inspection should not normally be done unless surface is etched to remove smeared metal. Etching
should not be done without depot engineering disposition.
1. Do Fluorescent Penetrant Inspection (NAVAIR 01-1A-16). Penetrant materials should conform to MIL-I-25135,
Revision E. Refer to specific work package for type, method, and sensitivity level. If specific work package does not
exist, or materials are not specified, use type I, Method A, sensitivity level 2 or 3. Penetrant designated in latest
revision to qualified products list of MIL-I-25135.
Part or Ambient
Air Temperature Time
Above 120°F Do not inspect
100 -120°F 15 minutes
60 - 100°F 30 minutes
40 - 60°F 60 minutes
Below 40°F Do not inspect
4. Remove pentrant with non-haologenated solvent recommended by penetrant manufacturer or with solvent moistened
cloth.
6-1 INTERPRETATION
1. Initial interpretation should be immediately after developer has dried. Allow developer to dwell for minimum of 5
minutes but not more than 30 minutes before making final interpretation.
2. Interpretation should be done with naked eye unless specific procedure work package instructs use of magnification.
3. Mark all linear indications detected. Linear indications are defined as those having length: width ratio greater than or
equal to 3:1. Rounded indications should not be cause for evaluation unless stated in specific procedure work package
or unless rounded indications form line that could indicate partially closed crack.
1. Evaluation of all indications should be done using acceptance limits for inspection area listed in specific procedure
work package. If this information is not included in specific procedure work package, refer to structural repair manual
(A1-F18AC-SRM-210 through A1-F18AC-SRM-240 or A1-F18AE-SRM-600 through A1-F18AE-SRM-750)
damage limits for specific inspection area.
3
FIGURE 33. Example of a nondestructive inspection typical procedures work package - continued.
149
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-AV8BB-SRM-300 013 00
1 September 1991
NONDESTRUCTIVE INSPECTION
Reference Material
Circle Template - -
Materials Required
1-1 INTRODUCTION
1-2 This work package defines the safety requirements, surface preparation, ED-520 instrument setup and the procedure for
doing surface inspections and fastener inspections.
2-2 Make sure the safety requirements have been met before using electrical equipment near aircraft fuel cells, oxygen systems
and stores (A10AV8BB-GAI-500).
3-2 Eddy current surface inspection is a nondestructive means of getting information on material variables, for example, alloy
type, hardness, heat treat condition, thickness, cracks, and so forth. The information below describes the requirements to do an
eddy current surface inspection to detect flaws in aluminum. Eddy current inspections should be done at the organizational level
using intermediate level resources.
150
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 013 00
4-1 SURFACE PREPARATION
1. Clean surface of inspection area of all foreign matter, grease, and oil using dry cleaning solvent.
NOTE
When using battery power, if needle does not move above red line and maintain a steady reading, recharge batteries.
4. Position probe on part at designated reference point or on surface of 64900-E/C STD reference block. See WP
014 00, figure 1.
8. If the BALANCE control does not bring the meter needle on scale, return the BALANCE control to zero and then
turn the LIFT-OFF/FREQ knob to 0.2 of a turn (revolution), then repeat step 7.
9. If required, repeat step 8 to bring the meter needle on scale. After the meter needle is on scale, slowly turn the
LIFT-OFF/FREQ knob counterclockwise to cause an up-scale needle movement.
10. Continue clockwise rotation of the LIFT-OFF/FREQ knob (adjusting the balance knob as required to keep the
meter needle on scale) until the meter needle reaches a peak and starts to move in a down-scale direction.
11. When the meter needle goes from up-scale to a down-scale direction, decrease the LIFT-OFF/FREQ setting by
turning the knob 0.2 turn (revolution) in the counterclockwise direction for non-shielded probes. For ferrite
shielded probes, turn the knob in the same direction as before, except to 0.4 turn (revolution). At this point, the
instrument should be nearly set for the 0.003 of an inch of lift-off compensation. Insert a piece of writing paper
between the bare material and the eddy current probe and adjust the balance if required.
12. Remove the piece of paper from under the probe and note the direction and amount of needle movement. Adjust
the LIFT-OFF/FREQ control to cause the meter needle movement to move about the same amount and direction.
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued.
151
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 013 00
13. Repeat steps 11 and l3 until no needle movement occurs when the piece of paper is removed from between the probe
and the bare material.
15. Select MED mode as required to get the required inspection sensitivity. The sensitivity adjustment may require
adjustment after this is done. Place the probe on the part to be inspected and adjust the BALANCE control if required.
The instrument is now adjusted for 0.008 of an inch intermediate layer lift-off compensation.
a. Using reference block, position probe on surface of block having greater conductivity, away from holes and
edges. Record reading.
b. Position probe on the half of the reference block having the lower conductivity and record reading.
NOTE
c. If difference in microamperes is outside the range noted above, adjust meter deflection with SENSITIVITY
screw.
1. If required, place probe on part to be inspected and adjust the BALANCE CONTROL to locate the meter pointer at
250. Scan part by moving probe over surface at a rate of approximately 12 inches per minute.
NOTE
Paint thickness variations will cause meter deflections. These deflections will not be as sharply defined as responses
from cracks. Part thickness changes and edges will cause meter deflections as sharply defined as cracks.
2. For comparison purposes, mark with marker any part thickness changes machined subsurface edges on surfaces of
part.
NOTE
Sharp movements down scale are characteristic of crack indications. Up scale deflections are not significant.
3. If balance point moves down scale when probe is near the edge of part, turn BALANCE control to return needle to
250 microamperes.
4. Set FUNCTION switch to LO and rescan areas that gave off scale meter indications with FUNCTION switch set to
MED.
5. Set FUNCTION switch to HI and rescan areas giving extremely small meter indications with FUNCTION switch set
to MED.
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued.
152
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A1-F18AC-SRM-300 013 00
7. Mark with marker area where meter needle deflection is at least twice as great as variation taken during probe
movement on the standarization surface.
Figure 1. Eddy Current Scanning Around Fasteners Using Circle Template as Probe Guide.
FIGURE 34. Example of a nondestructive inspection specific procedures work package - continued.
153
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
TABLE A-I. GENERAL AIRCRAFT INFORMATION MANUAL, PLANE CAPTAIN’S MANUAL AND
LINE MAINTENANCE MANUAL
Title block
Work package information 2-5.2.1 <titleblk> R
Reference material list 2-5.2.2 <wpinfo> R
Record of applicable technical 2-5.2.2.1 <reflist> O
directives 2-5.2.2.2 <ratd> O
Support equipment required list
2-5.2.2.3 <selist> O
154
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
155
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3-5 When torquing a fastener, select a wrench whose range fits the required torque value. A
torque wrench is most accurate from 25% to 75% of its stated range. A wrench with a stated
range of 0 to 100 pound-feet (0-135 N-m) will be most accurate from 25 to 75 pound-feet
(33.8-101.3 N-m). The accuracy of readings will decrease as you approach 0 pound-feet (0 N-
m) or 100 pound-feet (135 N-m). The following ranges are based on this principle:
Term Definition
156
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
RANDOM LIST
1. When operating with Class I or Class II leaks, continue to check fluid levels as
required in the PMRM.
b. Class II - Leakage of fluid great enough to form drops but not enough to
cause drops to drip from item being checked/inspected.
c. Class III - Leakage of fluid great enough to form drops that fall from the
item being checked/inspected.
157
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
158
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
159
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
300J14
160
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
161
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
162
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
163
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
EXAMPLE A
==============================================
Equating the work done on the system with the rate of energy increase and cancelling the t's:
p1u1A – p 0u0 A =
Ap1 (v - u1 ) (e1 - 0.5 u12) – Ap0 (v-u0) (e0 + 0.50 2)
EXAMPLE B
==============================================
2-3 Cylinder Expansion Test
2-4 An important problem faced by the designer of fragmentation warheads is that he must
maximize the energy which is transferred from explosive to metal during the detonation. The
most frequently encountered configuration is that of an explosive-filled metal cylinder detonated
by a wave moving axially. The best scaling law that has been devised for this condition is that
of Gurney, who disregarded detonation conditions and shock effects in the metal and assumed
implicity that all the energy of the explosive is conserved. His equation for the cylinders is:
where v is the velocity to which the metal is accelerated by the explosive, E is unit energy
content of the explosive, C is the weight of the explosive, and M is the metal weight. This
expression of velocity in terms of C/M implies that weight-ratio scaling of explosive and metal is
of prime importance and that dimensional scaling need not be considered at all. The term 2 E
has the dimensions of a velocity as was pointed out by Gurney in his original report.
EXAMPLE C
164
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
2-6 Recovery can be accomplished by adding dilute acetic acid, but the product obtained will be
impure. The heat of formation at constant pressure is -112 to -126.3 kilocalories per mole. The
calculated heat of detonation is 0.367 kilocalories per gram. Lead azide is used extensively as an
ingredient in initiating compositions.
[N = N= N] - Pb++ [N=N=N=]-
EXAMPLE D
============================================
2-8 In the manufacturing process ethyl nitrate (C2H5.ONO2), ethyl nitrite (C2H5.ONO),
and nitroethane (C2H5NO2) also are produced. The intermediate products of oxidation and
nitration involved in the preparation of mercury fulminate are as follows:
CH3.CH2OH CH3.CHO
Ethanol Acetaldehyde
EXAMPLE E
============================================
2-12 Two equations are given for the specific heat of PETN as a function of temperature:
EXAMPLE F
===========================================
165
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
3-4 In a given amount of time, t, mass moves from one side of the shock front to the other
side. By definiton, mass, m, is given as a function of density, p, and volume, V, by the equation:
m = pV EQ 1
The volume, V, can be expressed in terms of area, A, and length, L, by the equation:
V = AL EQ 2
The length, L, is the distance a particle travels in our assumed time interval, t, times the velocity,
v:
L = tv EQ 3
v 0 = (v – u 0 ) EQ 4
and
v1 = (v - u1) EQ 5
========================================
By equations 1 through 5:
EQ 9
166
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 45. Example of ETM/IETM installation data, CD label, and flyleaf data.
167
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 45. Example of ETM/IETM installation data, CD label, and flyleaf data - continued.
168
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
169
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
170
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
171
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
172
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
173
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
174
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
175
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 52. Example two of List of Contents - manual title and front matter for scrollable ETM.
176
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 53. Example three of List of Contents - testing and troubleshooting work packages
for scrollable ETM.
177
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
178
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
179
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
180
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
181
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
182
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
183
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
184
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
185
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
186
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
187
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
188
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
WARNING
189
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
190
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
191
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
192
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
193
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
194
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
195
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
196
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
197
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
198
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 71. Example of procedures for IETM with unlimited number of steps (hotspotted arrow
leading to graphic).
199
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
200
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
201
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
202
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 75. Example of procedures with locator graphic leading to detail graphic.
203
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 76. Example of procedures with previous detail graphic used as locator.
204
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
205
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 78. Example of procedures with parts data displayed from hotspot callout.
206
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
207
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
208
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
209
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
210
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
211
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
212
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 85. Example two of single choice task dialog (IETM only).
213
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
214
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
215
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
216
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
217
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 90. Example of security classification markings for work package pages.
218
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE 91. Example of security classification markings for front matter pages.
219
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
220
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
221
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
222
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
223
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A.1 Scope. This appendix provides examples of the various types of graphics used in the development of
page-based TMs and scrollable and frame-based TMs. Additional graphics preparation requirements for
IETMs are provided in MIL-PRF-87268.
A.3 DEFINITIONS.
A.4.1.1 Requirements for digital graphics files. Graphics files are delivered in one of three acceptable
graphics formats: Computer Graphics Metafile (CGM) (MIL-PRF-28003), Continuous Acquisition and
Life-Cycle Support (CALS) raster (MIL-PRF-28002), or Initial Graphics Exchange Specification (IGES)
(MIL-PRF-28000). Other commercial graphic formats are acceptable if approved by the requiring activity.
b. All graphics files for a particular TM should be supplied in the same graphics format if practical.
Otherwise, files may be delivered in any combination of the allowable formats.
A.4.1.2 Illustration style and format preparation. Plan, lay out, and size illustrations to effectively portray
the required details, and prepare to the latest technical data.
A.4.1.2.1 Illustrations for the support of procedural data. Illustrations developed to support operator or
maintenance procedures should not contain the text steps on the illustration (in the figure area).
a. Illustrations for procedures should supplement the text by clarifying procedures that are of a special
nature or are not obvious.
b. Locate illustration(s) (except for foldouts) as close to the text step(s) as possible. For
ETMs/IETMs, illustrations should be hotlinked to the applicable text step(s).
c. It is not necessary to illustrate each step of a maintenance procedure, such as the removal of screws
with an ordinary screwdriver, lifting off a cover after the screws have been removed, etc.
A.4.1.2.2 Illustration preparation for tools and test equipment. Only uncommon or unusual uses and
connections for test purposes are illustrated if it is essential to do so to avoid misunderstanding. Unusual
operations should also be illustrated. Standard tools and test equipment are not illustrated, nor should
self-evident or generally known uses be shown.
224
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
a. Exploded views should not be used to identify electronic items such as components on circuit cards
that are not to be disassembled for repair. Index numbers should not be stacked (i.e., showing the index
numbers next to a bar at the end of a leader line) unless each item and the index number are shown in a
detailed view elsewhere on the illustrations.
b. Tables may be used rather than index leader lines to provide clarity. The table(s) should be part of
the figure and not part of the textual data. For GAPL illustrations, the reference designators for electronic
items should cross-reference the index numbers used in the associated parts list.
d. For ETMs/IETMs, electronic parts should be linked to their applicable parts data.
A.4.1.3.1 Illustration detail. Style and techniques should be of a quality that will produce illustrations that
will clearly, adequately, and economically portray the information to be illustrated. The amount of detail
should be limited to that required to support the content of the illustration.
a. When text alone is not adequate, supplement the text by using illustrations for depicting procedures
such as disassembly, assembly, removal, and installation. In addition, illustrations are used to describe an
item, process, or procedure; call attention to details; and provide identification of assemblies, parts, and tools,
etc. Number or nomenclature callouts can be used to key important items in the illustration to the text.
b. Present illustration views so that the TM user can best understand the text being supplemented. In
most instances this will be as the user would view the item in the performance of the associated task. In
some cases, however, depicting the procedure or location of parts and controls described in a procedure
would better serve the user if shown as viewed from a different position.
A.4.1.3.2 Line drawings quality. Line drawings must be of high reproduction quality.
a. Primary lines that create the basic outline (object line) of the drawing components must have
sufficient density (darkness), line weight, and sharpness to accommodate reproduction. Line width should
be in accordance with ANSI Y14.2. When electronically or optically reproduced, the primary lines should
require no additional graphic enhancement.
b. Secondary lines, such as those used to indicate extensions or measurements, are lighter than primary
lines, but strong enough to reproduce clearly at the required reproduction size.
c. Shading may be used to give substance and form to the item depicted, to sharpen the contrast
between the subject and its background, or to increase effectiveness.
(1) Shading and shadows are used only when necessary to provide a clear understanding of form,
shape, or depth.
225
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
e. For page-based TMs, lined, cross-hatching, or mechanical patterns used instead of color should
remain clearly defined on the direct image copy. (Refer to figure A-33.)
f. Parallel lines on diagrams/schematics should be no less than 1/16-inch apart when reduced to
printed size.
A.4.1.3.3 Scale. Illustrations should be prepared to as small a scale as possible consistent with effective
portrayal of the graphic with all essential detail clear and legible. If prepared oversize, the illustration
should meet all requirements stated herein after reduction to the proper image size. The desired sizes of
illustrations for 8-1/2 inch manuals are provided below. Although not recommended, the vertical dimension
of 1/4- and 1/2-page illustrations may be exceeded. The horizontal dimension may not be exceeded.
1/4-page image 3-3/8 inch (20 picas) x 4-1/4 inch (26 picas)
A.4.1.3.4 Letter size. For page-based TMs, the typeface size for text, dimensions and callouts on
illustrations, including schematics and diagrams, should be a minimum of 8 points and a maximum of 14
points, when printed. For page-based TMs, the scale of text on illustrations should provide for a minimum
final letter size, when printed, of 8 points (refer to 4.9.11.and 4.9.12). For frame-based TMs, refer to MIL-
PRF-87268.
A.4.1.3.5 Electrostatic discharge (ESD) sensitive acronym. Mark figures and schematics with the ESD
acronym.
A.4.2.1 Border rules and boxes. When necessary for clarity, border or bracket rules and boxes should be
used to separate multiview illustrations on the same page or for locator/detail views. (Refer to A.4.2.3.2,
A.5.1.3, A-5.1.5, and to figure A-2.) For IETMs, border rules and boxes do not apply.
A.4.2.2 Use of the human figure. When it is necessary to illustrate an operation, procedure, or installation,
illustrations may include a human figure or parts of the body. The illustrated human figure should not
obscure necessary details of the item(s) being illustrated.
A.4.2.3 Use of locator and detail views. Locator and detail views are used in many of the types of
illustrations described in A.5.1 through A.5.1.10.7 to clarify or simplify a complex or busy illustration.
A.4.2.3.1 Locator views. When required by the complexity of the equipment or to assist in user orientation
of part(s), illustrations should contain a locator view. The overall equipment or item is shown with the area
covered by the view highlighted. The locator view may be placed anywhere on the illustration that will
enhance the clarity. (Refer to figure A-2.)
226
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A.4.2.3.2 Detail views. A detail view of a part or subassembly should be illustrated when the subject matter
cannot be clearly illustrated in the main view. The desired subject matter may be identified with detail
letter(s) or detail letter(s) adjacent to index number(s) on the main view and illustrated, as required, in the
detail. (Refer to figure A-2.) Complex illustrations may reference sub-detail views from a detail view, and
sub-detail views may reference a sub-sub-detail view. Detail views should be boxed or bracketed.
Author’s Note: For ETMs/IETMs, detail views should be hotlinked to the main view. Methods other
than letters may be used to identify details on main views such as a hotlink icon.
a. Sub-detail views, if necessary, may be identified with the assigned detail view capital letter prefix
followed by a consecutive Arabic numeral beginning with the number 1 (e.g., A1, A2, etc.).
b. Sub-sub-detail views, if necessary, may be identified with the assigned sub-detail view’s
identification alphanumeric number, followed by a consecutive capital letter (e.g., A1A, A2A, etc.).
c. Sub-detail and sub-sub-detail views may also be identified by placing the item/part index number in
a detail bubble (refer to figure A-2).
b. A manufacturer's name, symbol, or trademark should not appear on illustrations for the purpose of
identifying the illustration.
c. If a contractor identifies an illustration with an identifying control number for retrieval purposes, the
number should be placed in the lower right-hand corner of the illustration. The number should be no larger
than 8-point type.
d. If a contractor's engineering drawing is included in the manual, the title block information usually
located in the lower right-hand corner of the drawing should be removed prior to use in the manual.
A.4.2.5 Callouts. Index numbers, reference designators, and nomenclature are used as callouts on
illustrations to identify equipment, components, and significant features. Leader lines, sweep arrows and
legends are used, in combination with the callouts to enhance the illustration.
a. Use leader lines or sweep arrows to help the readers orient themselves with respect to the
illustration and to provide directional movement in tasks.
b. Callouts are prepared by a mechanical or electronic method, rather than by freehand lettering.
(Callouts on engineering drawings prepared in accordance with A.5.1.2 are acceptable.)
c. Callouts and their leader lines should be easily distinguishable from components and other lines of
the illustration.
d. Callout leader lines or arrows are straight lines where possible. Don’t allow leader lines to cross
each other. Callouts should not touch the illustrated item.
e. When practical, all callouts should be placed outside the boundaries of the parts illustrated so that
the parts are not obscured.
227
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
f. Use a type size no smaller than 8 points and no larger than 10 points.
g. When an item is first illustrated and its location has not yet been specified, a simplified general
locator illustration may be used to identify the location of the equipment item within the system (refer to
figure A-2).
A.4.2.5.1 Index number callouts. Index number callouts start with Arabic numeral 1 and continue
consecutively. Index numbers continue in sequence from one sheet to another in a set of multisheet
illustrations.
Author’s Note: For page-based TMs only, when a series of illustrations are used within the same
informational, operational or maintenance task (e.g., theory, operator instruction, or removal
procedure), index numbers should continue from one illustration in that series to the next; however, if
an item that already has been assigned an index number is used in more than one illustration in that
series, it must retain the same index number.
Author's Note: To improve clarity in page-based TMs, all three index number sequence methods may
be used; however, the sequence method within individual WPs should remain consistent.
b. Identify all items shown as exploded. Items drawn in phantom need not be identified (refer to figure
A-2).
c. Index numbers should not be contained within circles unless required for a specific reason in MIL-
STD-3001-1 through MIL-STD-3001-8.
A.4.2.5.2 Nomenclature callouts. Nomenclature of more than one line should have the left margin justified
when placed on the illustration. All lines of copy should parallel the horizontal edges of the figure,
whenever possible. (Refer to figure A-2.)
b. Nomenclature may appear on illustrations only if it can be done without crowding or reducing type
size so as to make reading difficult. (Use diagram callouts of no smaller than 8 points.)
Author’s Note: The above nomenclature requirements do not apply in the development of an IETM.
A.4.2.5.3 Reference designator callouts. Reference designator callouts are a combination of letters and
numbers that identify equipment and components shown on illustrations and diagrams. Reference
designators may be used alone to identify an item or may be used in combination with an index number
callout (i.e., 3 (CR4)). For ETMs/IETMs, when reference designations are used, they should be linked to
their applicable parts data.
A.4.2.6 Legends. When callout numbers are used (with the exception of IPB GAPL maintenance
illustrations), a legend consisting of a numerical listing and associated identifying nomenclature may be
included on the illustration.
228
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
a. For page-based TMs, legends should always be a part of the illustration and not part of the textual
information. Nomenclature used on legends and associated text should be identical.
b. Legends are acceptable on maintenance IPB GAPL illustrations only when the illustration contains
reference designations for electronic components. The legend should consist of an alphanumeric listing of
the reference designations and their associated index numbers.
Author's Note: For ETMs/IETMs, legends should not be used. All callouts (index numbers and
reference designations) should be linked to the applicable parts data.
A.4.2.7 Leader lines and arrowheads. Do not allow leader lines to touch the callout. Arrowheads should
touch the object to which the leader line applies. Do not allow arrowheads to enter the object to which they
apply. If it is necessary to enter the object to provide for greater clarity, a breakoff symbol (refer to figure
A-7) should be used in lieu of an arrowhead.
a. Lines are to be uniform, short, and as straight as possible; avoid the use of dogleg-shaped lines
unless absolutely necessary.
c. Arrowheads should be used. A leader line may be highlighted if it will be easier to follow.
d. Arrowheads should be uniform in shape and size when multiple arrowheads are used on a page.
e. Lines and arrowheads should not cross or come in contact with other callout lines or arrowheads,
nor should they obscure essential details.
A.4.2.8 Sweep arrows. Sweep arrows are used to help the user of the illustration orient themselves with
respect to detail and locator views that appear on an illustration. (Refer to figure A-13.) Sweep arrows are
also used to provide directional movement in the performance of a maintenance or operational task.
A.4.2.9.1 Page-based TMs. Black and shades of black (one color) are normally used for TMs. Prior
approval for use of color must be obtained from the requiring activity. The requiring activity will provide
written approval, designating color(s) to be used.
a. When color (other than black) is required, it should be held to the minimum absolutely necessary to
highlight or clarify important information.
b. The number of colors should be kept to a minimum by use of various techniques such as tints,
patterns, cross-hatching, and dots.
c. Any number of shades of a primary color used can be considered as one color (e.g., a two-color
printing could consist of black and three shades of red).
d. When color is approved/specified, the primary colors of red and blue should be used first.
229
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A.4.2.9.2 Frame-based TMs. Color may be used when it will enhance the understanding of the data. The
use of some colors may not be appropriate for certain environmental conditions. The following color
limitations should apply.
a. For ETMs/IETMs that may be displayed on a monochrome system, reverse video and/or
underlining should be used for hotspots rather than color.
b. The use and choice of colors will be as specified by the requiring activity.
A.5.1.1 Photographs. Photographs may be used for illustrations. When a photograph provides for better
clarity than a line drawing, the photograph should be used. Photographs should not be used on foldouts.
a. Line tracings of photographs are also acceptable. When a line tracing is prepared, proper definition
of line work should be used in lieu of photo retouching. The intended subject matter should be highlighted
and unnecessary background should be eliminated. Items required for reference (location) should be subdued.
b. If halftones are used, they should be detailed and sharp, free of heavy shadows, distorted objects,
cluttered foregrounds or backgrounds, and should give good contrast from white, middle tones, and black.
c. Retouching may be used to emphasize detail, exclude unwanted detail, correct slight photographic
defects and eliminate undesirable shadow. Tonal values should be maintained.
Author’s Note: If the intention is to use photographs in lieu of line art, it is preferred that a digital
camera be used to produce the required photos. This will negate the use of halftones and the need for
retouching and screening. However, if the final reproducible copy is intended to produce paper output,
it may be better to prepare line art in lieu of photographs. Obtain approval from the requiring activity
for the use of photographs in paper TMs. For IETMs, it is preferred that a digital camera be used to
produce the required photos.
A.5.1.1.1 Prescreened photographs. Although not preferred, prescreened photographs are acceptable as
direct image copy provided they are screened only once. The screen of the final sized illustration will be
specified by the requiring activity. When prescreened photographs are used, they should be clearly marked to
indicate prescreening. Unscreened continuous tone photographs and/or original illustrations must be supplied
with final reproducible copy.
A.5.1.2 Engineering drawings. Do not use engineering drawings unless specified otherwise by the requiring
activity. When used, the drawings should meet the following criteria:
a. They should comply with MIL-STD-100 or user needs. They should be modified, as necessary, to
meet the legibility, format, and production requirements described in this document and the contract.
b. All unnecessary data that would reduce the comprehension or clarity of the drawing should be
removed. Data includes borders, title blocks, manufacturer’s notes, and other irrelevant material.
Manufacturer’s wiring diagram drawing numbers may be retained for the preparation of aircraft wiring
diagram manuals if the drawing numbers are used to develop an easy to use work package numbering
230
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
c. They must be reduced or redrawn to meet technical manual page or frame size restrictions.
A.5.1.3 Multiview illustrations (page-based TMs only). Multiple view illustrations should be provided
when necessary to identify significant features on an illustration, improve identification of parts or clarify
the relationship or the location of the parts. Each view should be oriented and enlarged as necessary to
identify significant features (refer to figure A-2).
a. Each view may be identified by a detail capital letter in block size print in a bubble or a caption.
Orientation should be by the use of directional arrows or text. For example: "Rotated 180 degrees" as it
relates to the main illustration.
b. Views may or may not be captioned, but if one view is captioned, all should be captioned. The
caption should be centered with respect to the view to which it applies. Where captions are not used, the
identifying letter should be so centered. When a caption and an identifying letter are used together, the
identifying letter should precede the caption. Identifying letters and captions should be larger and bolder
than any other lettering in the illustration. The identifying letter should be larger than the caption when both
are used.
A.5.1.4 Foldout and multisheet illustrations (page-based TMs only). When an illustration, including
diagrams, must be larger than a single TM page for clarity or to be easily viewed by the TM user, foldout
presentation should be used. Foldouts should be placed at the end of the applicable work package and not at
the rear of the technical manual. Foldout-foldup illustrations should not be used.
Author’s Note: When approved by the requiring activity, foldouts may be placed at the rear of the
applicable WP or at the rear of the TM for intermediate and depot level manuals.
a. A one-page apron is required for each printed foldout. The planning of a foldout illustration should
include consideration of its usability relative to the length of each data increment.
b. A foldout illustration page should not exceed 45 inches in width (including the apron) and 11 inches
in height. The image area of a foldout illustration page should not exceed 36 inches in width by 10 inches in
height including the marginal copy.
c. Foldout illustrations should be printed as right-hand pages and should be backed by blank pages.
Individual illustrations in groups of related illustrations capable of being presented on a single page should
not be grouped together as a foldout.
A.5.1.5 Exploded view illustrations. An exploded view (refer to figure A-3) is an illustration that shows a
unit separated or disassembled but with all the parts positioned in correct relationship to each other.
Exploded views are used to support the IPB GAPL and additional maintenance procedures in the
maintenance work packages. The following guidelines are recommended to ensure clarity of presentation:
a. Index numbers, keyed to a GAPL, legend, list, or text reference, can be used to identify parts.
b. No more than 20 items should be called out in a 7- by 10-inch area if nomenclature is used.
c. Whenever possible, the average maximum number of callouts within a 7- by 10-inch area should be
231
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
70. All callouts (numerals) should be outside the boundaries of the parts being illustrated.
d. There should not be more than five callouts (numerals) in any 1 square inch area.
e. If the criteria of subparagraphs c. and d. above cannot be met, use detail views of the figure.
f. When necessary, provide a locator view (refer to A.4.2.3.1) to show the orientation of the view with
respect to its next higher assembly (NHA) and also if the illustrated item is part of a larger unit. A locator
view showing the location of a weapons replaceable assembly (WRA) in an aircraft should not be provided
at the depot level of maintenance. A locator view showing the location of a WRA in an aircraft may be
provided at the intermediate level of maintenance when the intermediate level maintenance procedure is
contained in an aircraft maintenance manual containing both organizational and intermediate maintenance
procedures.
g. For maintenance IPB GAPL exploded views, index numbers should be assigned in disassembly
sequence. Nomenclature callouts may be added to further clarify or identify maintenance instructions on
maintenance IPB GAPL exploded views.
h. For all other exploded view illustrations, index numbers should be assigned in a clockwise order
beginning with the number 1.
i. Limit the level of detail to that required to positively identify parts. Excessive detail makes the
illustration complex and does not contribute to usability.
j. Use broken lines for parts shown merely for reference, but not called out. Ensure that the broken
lines are legible.
k. Center (axis) lines should be used on exploded views to show parts relationship.
A.5.1.7 Pictorial illustrations. This class of illustration includes end item familiarization views, locator
illustrations and assembly and installation illustrations which depict physical items (refer to figure A-4). It
does not include exploded views. These drawings must attempt to show the "how to" instructions defined in
the text. Their purpose is to present a direct duplication of what will be seen on the actual hardware. Some
of the recommended guidelines for preparing pictorial illustrations are:
a. Orient the illustration so that the view represented is identical to the view the technician sees when
performing the maintenance task. If the item is illustrated as installed in the end item, indicate the exact
orientation of the view by using a locator view and directional arrows. For example, for a view of an item
installed in an aircraft, use a locator view showing its location relative to the aircraft, and directional arrows
showing which way is forward, aft, inboard, or outboard (unless the orientation is obvious). When
necessary to portray position or relative location, other equipment items may be shown in phantom.
b. An alternate method, applicable to aircraft, is to provide aircraft reference numbers, such as the
numbers for fuselage station, wing station, butt line and waterline. With this method, at least two of each
type of reference line would be shown, so that the technician would be able to determine the orientation of
the view.
232
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
c. On mechanical equipment illustrations, use no more than 20 callouts in a 7- by 9-inch area when
nomenclature is used as callouts. There may be as many as 70 callout numbers in a 7- by 9-inch area,
provided they are all outside the boundary of the item illustrated. If placing some callouts inside the
boundary is unavoidable, use no more than 40 callouts.
d. On electronic circuit cards, use no more than 70 callouts. Use the maximum amount only when:
(1) all callout numbers are outside the boundaries of the circuit card,
(2) there are no more than five callouts in any square inch area,
e. When determined physically feasible, assign callout numbers clockwise in sequence, beginning in
the upper left of the drawing. When an illustration is used for both IPB and maintenance information, it will
be indexed in disassembly order.
f. Use straight (not doglegged) arrowheaded leader lines. In extremely rare cases, doglegged lines will
be necessary due to the type of artwork. Leader lines should never cross each other.
g. For callouts or other verbal material on illustrations, use all upper case, 8-point or larger type.
h. When drawing an illustration, use the heaviest lines for the outlines of the parts being illustrated.
Use medium lines for the leader lines, axis lines, and details that are necessary to identify parts.
A.5.1.8 Combination illustrations. Combining photographs or continuous tone artwork with line drawings is
not recommended.
b. Charts and graphs are prepared as illustrations. Instructions should be provided for use and
interpretation of complex graphs.
a. Clutter. The number of ideas conveyed per graph should be minimized. Line graphs should depict
a maximum of four relationships between the axis variables. Lines depicting relationships are to be coded
to distinguish one from another.
b. Orientation of axes. If there is a natural orientation for the axes (for example, altitude on the
vertical axis), the axes are to be so oriented.
c. Grid lines. The number of grid lines used are such that the user can read values to the required
degree of accuracy. Size of the illustration is such that the grid lines should be no less than 0.1 inch apart.
Grid lines are lighter than the graph lines and should not obscure detail necessary for proper use of the
graph.
233
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
d. Graph scales. Graph scales are linear or nonlinear as required for proper comprehension and use.
The axes should be labeled to indicate the variables and units of measurement.
A.5.1.10 Diagrams.
A.5.1.10.1 General preparation requirements. The following paragraphs describe the general preparation
requirements for the various types of diagrams that may be required to support the operation and
maintenance data contained in the TM.
A.5.1.10.3 General methods. The specifications listed in MIL-STD-3001-1, Appendix A and Appendix B,
are to be followed for general methods in acquiring diagrams. Other requirements are as follows:
a. Layout. The layout of all illustrations and diagrams should remain easily readable and compatible
with the intended use. The layout of the illustrations and diagrams should enhance and support the
maintenance text to which they apply.
(1) All electrical/electronic and fluid flow diagrams should conform to circuit or system flow
without regard to physical arrangement of components and parts and their relative location in the system.
The flow should read from left to right and top to bottom. Ideally arranged diagrams, including multi-frame
drawings, should show the primary inputs in the upper left corner and should flow across and down the
page/frame to end with the primary outputs in the lower right-hand corner of the diagram.
(2) Diagrams should consist of symbols grouped as circuit entities; for example, amplifiers and
power supplies. Each group should be located on the diagram so that the complete diagram requires a
minimum amount of wiring (electrical/electronic diagrams) or the shortest lines (fluid or mechanical). All
wires/lines should be routed as directly as possible so that they cross the fewest wires/lines as possible.
b. Consistency. A standard referencing system for associated text, signal flow, and other diagrams
should be used.
(2) If special graphic symbols are required, they should be made visually distinctive from other
graphic symbols used and included in a special symbols chart.
(3) Official nomenclature is used for hardware, controls, indicators, switches, etc.; consistent,
standard nomenclature is used for functions, signals, etc.
c. Appropriate detail. All information required to fulfill the intended purpose of the diagram should
be used; overcrowding must be avoided.
(1) Complete detail should be provided for hardware, function, signal identification, measurement
data (voltages and waveforms), explanatory text, connectors, terminal boards, pin numbers, signal names,
reference designators, component values and tolerances, replacement components, etc.
(2) All inputs and outputs should be clearly labeled. In single-page/frame diagrams, termination
points are shown for every relevant wire, pipe, etc. In multi-page/frame diagrams, unterminated line
234
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
segments should be identified by appropriate symbols with references maintaining continuity from page to
page. For IETMs, hotlinks should be used to provide continuity.
(3) To the extent possible, and to keep diagram format consistent for readability, place inputs and
associated labels near the diagram left or top edge and outputs and associated labels near the diagram right
or bottom edge. The continued portions of multi-sheet diagrams and schematics should align, or should be
labeled or hotlinked.
(4) For locating information, relevant components are identified on the diagram or referenced or
hotlinked to an explanatory listing. Where applicable, the wording on the diagram should correspond
exactly with the wording in the text.
d. Inappropriate data. Data not related to the purpose of the diagram should not be included.
Pertinent detail of nonrepairable and nonreplaceable components should be held to a minimum.
A.5.1.10.4 Signal flow. Signal flow, especially for electrical and electronic equipment, critically affects the
understandability of diagrams. To assist the TM user in following the diagram, where possible, major
signal or pressure flow should be from left to right, and feedback or return flow should be from right to left.
For IETMs, signal flow can be indicated using animation or color. As applicable, the methods for
portraying signal flow outlined in A.5.1.10.4.1.1 through A.5.1.10.4.1.3 should be used.
Author’s Note: For IETMs, signal flow for specific circuitry or for a single circuit may be displayed
separate from the entire diagram by providing hotlinks on the diagram. When the hotlink is activated,
only the flow for the specific circuitry or for the single circuit will be displayed. This may negate the
need to use some of the methods discussed below.
A.5.1.10.4.1 Signal connections. Signal connections can be portrayed in one of three methods.
a. Point-to-point method. Shows each signal separately with a continuous line to represent its flow.
(Refer to figure A-5.)
b. Highway method. Blends two or more signals together in a single line. (Refer to figure A-5.) This
method is useful in showing the flow of a group of related signals. Any number of signals may be blended
together. Any signal that has been blended into the main line is blended out at some other point on the line.
Once a signal has been blended out of a line, it can no longer be present on that line. Each signal blended in
or blended out of the line should be identified.
c. Interrupted flow method. Use special symbols to interrupt signal flow. This method may be used
within a single sheet/frame of a diagram, between sheets/frames of a diagram, or between diagrams. Refer
to paragraphs A.5.1.10.4.1.1 through A.5.1.10.4.1.3 for types of special symbols and techniques used to
interrupt signal flow. The method used to show interrupted signal flow should be consistent on all diagrams
in a TM.
A.5.1.10.4.1.1 Techniques within a single sheet of a diagram. Interrupted flow within a single sheet/frame
diagram is depicted using one of the following techniques.
a. Oval connector. Used to continue signals from one area of a sheet to another area.
235
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
(2) Each signal is identified at its source bracket and destination bracket.
(3) Oval connectors should have a unique letter identifier inside the oval. (Refer to figure A-6.)
(4) The position of the source and destination connectors can be identified by zone numbers.
(Refer to A.5.1.10.4.1.2 c.)
b. Signal returns. Used to continue signal returns within a single sheet of a diagram.
(2) Each return is labeled the first time it appears on the diagram (preferably on the left edge of the
diagram). (Refer to figure A-7.)
c. Breakoff symbols. Only power forms, clock pulses, and other multiuse, minor signals use the
breakoff symbol technique.
(2) The source of signals is shown at the left edge of the diagram. (Refer to figure A-7.)
Author’s Note: For IETMs, if this method is used, the origin and destination of the signal should be
hotlinked.
A.5.1.10.4.1.2 Techniques between sheets of a diagram. Interrupted flow between sheets of a diagram
should be depicted using one of the following techniques.
a. Boat symbol. Used to continue signals from the right edge of one sheet to the left edge of the
following sheet within a multisheet diagram (adjacent sheets of a diagram only).
(2) Boat symbols have a unique letter inside the boat. (Refer to figure A-8.)
b. Numerical or letter identifier. Used to continue signals between sheets of a diagram. Refer to figure
A-8 for an example of numerical identifiers. A unique letter identifier may also be used in lieu of numbers.
c. Oval connector. Used to continue signals from one area of a diagram to another. Application is the
same as within a single sheet of a diagram. (Refer to figure A-6.) For identification of source and
destination areas, the following recommended zoning requirements are used for multisheet diagrams:
236
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
(3) Zones are always numbered as below, even if all zones are not used on any sheet.
Author’s Note: For IETMs, zoning does not apply. The origin and destination of the signal should be
hotlinked.
A.5.1.10.4.1.3 Techniques between diagrams. Interrupted flow between diagrams is depicted using one of
the following techniques.
a. Oval connectors. Source and destination figure numbers are inserted before zone references. (Refer
to figure A-6.)
b. Pyramid diagram. Diagram number is included from one diagram to another. (For example,
include reference to 1 on diagram 2 and reference to 2 on diagram 1.) (Refer to figure A-8.)
Author’s Note: For IETMs, zoning does not apply. The origin and destination of the signal should be
hotlinked.
A.5.1.10.4.2 Signal difference. Various techniques are available to indicate signal flow, signal importance,
and type, such as the following. (Refer to figure A-9.)
c. For page-based TMs, use different colors if approved by the acquiring activity (refer to A.4.2.9).
A.5.1.10.4.3 Signal junctions. The relative importance of signals may also be indicated by the way signal
junctions are represented. Subordinate junctions are used to indicate differences in signal importance.
Coordinate junctions are used to indicate equality in signal importance. (Refer to figure A-10.)
A.5.1.10.5 Schematic and functional flow diagrams. Electrical schematic diagrams should be prepared in
general accordance with ANSI Y14.15. (Refer to figures A-11, A-12, and A-13.) Electrical and electronic
schematics and fluid and mechanical schematics should conform to circuit or system flow without regard to
physical arrangement of components and parts and their relative locations. The flow should read from left
to right and from top to bottom. Diagrams, to the extent possible, should show the primary inputs in the
upper left corner and should flow across and down the illustration to end with the primary outputs in the
lower right corner of the diagram. When diagrams are specifically prepared for maintenance purposes, as
much of the following information as applicable should be included. Any additional information that is
available and that will not disrupt the flow or understanding of the diagram should be included in the
illustration.
a. Use standard symbology and representation when depicting electronic circuitry. That is, whenever a
standard circuit, such as a Darlington amplifier or a logic gate is used in a schematic, it should be
recognizable. Ideally, all the components that perform one function, such as an amplifier, should be drawn in
237
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
c. An illustration should limit the number of components in any 2-inch square area. This limit should
not exceed 12 components. For example, figure A-14 displays two selected 2-inch square areas
encompassing only six and seven components in a fairly crowded situation. The total number of
components displayed in any full page/frame schematic or foldout should not exceed 80 components on any
page/frame.
d. Each component in the schematic must be identified. The labeling should be brief but contain
sufficient information to assure proper understanding and maintenance performance. For IETMs,
components shown on the schematic should be hotlinked to the applicable parts information data.
e. For callouts, component designations, and other textual material on schematics, use all upper case
8-point type or larger.
f. Briefly explain any nonstandard or uncommon symbols in a legend on each figure where they are
used. Place the legend and any additional notes in the lower left portion of the diagram. A detailed
explanation of nonstandard or uncommon symbols should be fully defined in the technical manual
introduction. For IETMs, the legend should be hotlinked from where the symbols are used on the diagram.
g. There should be no more than 15 intersections in any 2-inch square area. This includes all line
intersections, whether an electrical connection is made or not. Figure A-14 is an example of a schematic
with few intersecting lines.
h. Clearly label all inputs and outputs. Inputs should be at the left of an illustration and outputs at the
right.
i. Clearly label DC resistance of windings and coils (if more than 1 ohm).
j. Include or hotlink an illustration of CRT display next to the point at which it will be observed,
usually at a designated test point (TP).
k. Show wiring requirements for critical grounding points, shielding, pairing, etc.
o. Specify circuit voltage values at significant points (tube pins, test points, terminal boards, etc).
p. Specify significant circuit resistance values at designated reference points (information may be in
tabular form).
q. For page-based TMs, include zones (grid system) on complex schematics. When technical data is
238
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
r. For page-based TMs, include circuit element zone locations (on complex schematics) in tabular
form on the drawing or associated document when such location of information will facilitate use of the
schematic.
t. Device ratings should be located close to the device symbol to assure correct identification. Polarity
markers should be shown on all instrument transformers and capacitors.
u. Piece part details are shown only when replacement is authorized at the maintenance level covered
or when understanding is required for fault isolation.
v. For nonreparable assemblies, all inputs and outputs are shown with enough detail to understand
how inputs relate to outputs (complete details for simple circuits and symbols for complex circuits).
A.5.1.10.5.1 Circuit parameters. Circuit parameters should be marked according to their reference
designations (if applicable), types, and values. When these markings tend to clutter the field of the
illustration, a table of these markings, in order of reference designation (electrical or electronic diagrams) or
nomenclature (fluid or mechanical diagrams) should be included, or tabular data referenced, for all circuit
parameters. For IETMs, this circuit parameter data should be hotlinked. Reference designations should
agree with those used in related engineering drawings. Nomenclature should be in accordance with 4.9.15.
Normal operating conditions and other conditions specified by the applicable technical content standards
should be indicated.
A.5.1.10.5.2 Test point identification symbols. Identification of test points by symbols should not be
employed where the test points are readily identifiable by other means; for example: "Test jacks (TP-5),"
"Connector pins (J100-M)," and "Component pins (X4-2, Q1-E, and Z5-14)" are readily identifiable points
and do not require symbols. Test points that are not otherwise identifiable (artificial test points) should be
identified by test point symbols. The test point symbol should be an encircled upper case letter and an Arabic
numeral. These test points will be referred to in the text such as "Test point A2."
A.5.1.10.5.3 Use of artificial test points. Artificial test points should be used when specific voltage and
resistance test points, used in checking a circuit, are otherwise unidentifiable. Different letters should be
assigned to each component (on a diagram); for example, test points A1, A2 and A3 in component 1, test
points B1, B2 and B3 in component All test points should be identified on the diagram by their assigned
identifying code.
A.5.1.10.6 Functional diagrams. Functional block diagrams are designed to provide a simplified description
of particular operation or maintenance actions. The functional blocks are logically or sequentially arranged
239
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
to describe the action taking place and show all input and output signals. Variations of the block diagram
approach can be used to describe principles of operation, troubleshooting and maintenance efforts. Most
principles of operation are described in text form with supporting functional block diagrams as shown in
figure A-16. The following general guidance is provided concerning the preparation of block diagrams:
a. Abide by the basic schematic requirements that apply equally as well to functional flow diagrams.
b. Functional block diagrams show the complete system or subsystem on one sheet (if possible).
(Refer to figure A-16.) Methods to be used include functionalizing components, grouping subfunctions into
functions, or continuing until the complete system or subsystem can be shown on one sheet or frame. (For
page-based TMs, a foldout may be used when approved by the acquiring activity; refer to A.5.1.4).
c. Functional diagrams should provide enough details to relate the input to output signals by using
arrowheads to indicate signal flow direction when necessary and specifying signal characteristics and
tolerances in pictorial or tabular form. Indicate direction flow by arrows. Signal flow (electric/electronic) or
fluid/pneumatic flow should be from left to right. For IETMs, signal flow may be depicted using animation
or color.
d. Functional diagrams should account for all maintenance significant components by ensuring the
user can relate the schematic diagram to the functional diagram, blocking the components on the schematic
to correspond with blocks on the functional, or providing a table relating components to functional blocks.
e. Functional diagrams should show hardware boundaries by using solid, dashed, or dotted lines;
various line weights; or different colors or shades (when approved by the requiring activity).
g. Avoid reverse directional flow except for feedback. Feedback flow should be from right to left. For
IETMs, flow may be depicted using animation or color.
h. Label all inputs and outputs of each block on the diagram. The label can consist of the name of the
input or output, a waveform or symbol in the flow line itself.
i. Identify all test points clearly and distinctly. When required, place all waveforms in close proximity
to the appropriate test point or hotlink the waveform data from the test point. If impractical, provide a good
reference to its location.
j. Define any nonstandard or uncommon symbols in a legend on each diagram on which they appear.
Place the legend and any required notes in the lower left portion of the diagram. For IETMs, the legend data
should be hotlinked.
A.5.1.10.7 Cutaway diagrams. Cutaway diagrams (refer to figure A-17) employ pictorial symbols of
components drawn with interconnecting lines. Diagrams of this type provide a simplified method of
showing piping between components with the general piping arrangement emphasized. Complete principles
of operation of the flow path are difficult to explain as only the external features of the components are
shown. Internal flow within a component is not shown, thereby not fully describing the flow of the liquid or
gas. Arrowheads are used to show direction of mechanical action or fluid flow. For IETMs, direction of
mechanical action or fluid flow may be depicted using animation or color.
240
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A.5.1.10.8 Combination diagrams. The combination diagram utilizes the best features of the graphic,
pictorial and cutaway diagrams and symbols in the same drawing with integral interconnecting lines.
Diagrams of this type are best for illustrating principles of operation because they emphasize piping,
function and flow paths for each component and best describe the flow path of the fluid or gas (refer to
figure A-17).
a. Logic diagrams are used to show digital circuitry operation. Graphic symbols from IEEE STD 91-
84 are used. If the logic circuit has no specified symbol, it can be identified with a rectangle that is labeled
to show all circuit functions.
b. Power and clock connections are identified in a truth table or are connected using breakoff signals.
c. When necessary for clarity, a truth table or timing diagram should be prepared or should be
referenced or hotlinked from another diagram. For logic functions, the truth table timing diagram may be
shown inside a block to describe the relation of input to output signals. (Whenever possible, truth tables
should be placed in the text area, or hotlinked, and not on the figure.) (Refer to figures A-19 and A-20.)
A.5.1.10.10 Simplified diagrams. Simplified diagrams include key components for explanatory purposes
and omit selected components or groups of components, or details for clarity. Simplified circuitry and/or
simplified functional divisions indicate excluded or included components in the diagram title (for example,
"Figure 3. Simplified R-T Control Circuit with Cockpit Control Switch in Off Position (All Relays
Unoperated.")). Refer to figure A-21.
A.5.1.10.11 Partial diagrams. Partial diagrams are used to show all circuit details completely and reference
all destinations of input or output connections. (Refer to figure A-22.)
A.5.1.10.12 Test diagrams. There are two types of diagrams used to support test procedures. Test diagrams
(refer to figure A-23) are used to show test stimuli, item (or circuitry) under test, and test measurement
components. Test setup diagrams (refer to figure A-24) are used to show the interconnection between the
test equipment and the unit (s) under test. The setup diagram may be presented schematically or pictorially.
a. When diagrams exist for the item under test, a block diagram representation may be used.
b. In TMs containing testing data, the item under test should be emphasized (shown in detail); in test
equipment maintenance TMs, the test equipment should be emphasized.
A.5.1.10.13 Power distribution diagrams. Power distribution diagrams depict components involved in power
input, power form generation, and power distribution. They are grouped by power flow. (Refer to figure A-
25.)
241
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
b. If the equipment covered is complex, several levels of detailed block diagrams may be required.
(Refer to figure A-26.)
A.5.1.10.15 Wiring diagrams/illustrations. Weapon systems and equipment, engines, and support and test
equipment that have wiring or cabling should include interconnection information in one or more forms such
as wiring and cabling diagrams and wire bundle access and routing illustrations. Wire lists are also
considered interconnection information but are not illustrations and are covered under tabular data (refer to
4.9.7.1).
A.5.1.10.15.1 Wiring diagrams. Wiring diagrams (refer to figure A-27) should be structured and developed
in accordance with the requirements contained in MIL-STD-3001-5. To facilitate training and consistency
in presentation, the wiring requirements contained in SAE-AS59881 should be followed whenever possible
when preparing the wiring diagrams. These requirements include the standard methods for identifying
wiring system circuit functions, individual wires, connectors and terminal boards, and assigning reference
designations. In general, the layout of wiring diagrams should be the same as for schematic diagrams (refer
to A.5.1.10.5); however, the following additional ground rules apply.
a. Each line representing the wires and interconnections should be coded or otherwise identified.
c. Each wire should be drawn so that it can be traced from point of origin to destination.
d. Wires located within a cable harness should be shown as a single wire. Wire bundling techniques
for aircraft system wiring should not be used.
e. Normally, aircraft wiring diagrams are drawn and scaled for a foldout presentation. However, to
facilitate on-aircraft wire chasing and troubleshooting, wiring diagrams may be drawn and scaled to a 11-
inch x 8-1/2-inch landscape format and included in a normal size TM. These two formats should not be
combined in the same TM.
f. Wire colors may be indicated by using color designation codes. Indication of color designations is
preferable when many colors and color combinations such as BK-W are to be shown. Recommended single-
and two-letter color designations for use specifically on diagrams are as follows:
242
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
White W
g. A junction of lines will be indicated by a dot at the junction of the lines. Lines crossing each other,
without a dot, indicate that they are not connected in any way.
A.5.1.10.15.2 Wire bundle routing illustrations. For aircraft wiring systems, illustrations should be provided
showing the routing of all aircraft bundle assemblies throughout the aircraft (refer to figure A-28).
A.5.1.10.16 Cable diagrams. This type of cable interconnect diagrams is included in equipment and support
equipment TM if the technician must install or remove cables when performing test procedures, installation,
assembly, disassembly, modification, service, etc. (Refer to figure A-29.)
a. Cable diagrams provide all the information necessary to make the electrical connection between
assemblies, chassis, bays, units, and systems in an easily understood format.
b. Each cable diagram should consist of an illustration and accompanying table. If cable routing is of
a special nature, it should be so noted. For very complex systems where routing is of great importance,
additional diagrams showing desired cable locations may be necessary. (Refer to figure A-29.) The
accompanying table should meet the following requirements:
(1) Cable entries are listed in numerical order or by preferred connection sequence.
(3) Cable origin and destination include assembly name, assembly jack number, and cable plug
number.
(4) Both table and illustration should appear on the same page or facing pages. For IETMs, the
table should be hotlinked from the applicable illustration. The table is considered text and is not part of the
figure.
c. Cable diagrams show all related connectors. Assembly names and jack numbers should be listed.
d. For simple equipment, a table may not be needed, and an interconnection diagram that actually
shows the routing of the cables may be substituted (refer to figure A-30). The internal connections of the
equipment or assemblies are usually omitted.
A.5.1.10.17 Piping diagrams. Weapon systems or equipment that include piping in their design are
supported with information in the form of piping diagrams. The diagrams should meet the requirements for
illustrations and diagrams presented in this handbook. (Refer to figure A-31.)
A.5.1.10.18 Fluid power/gas diagrams. Fluid power/gas diagrams illustrate those systems that transmit
and/or control power through the use of pressurized fluid, within a closed circuit of tubing, pipes or hoses or
combination thereof. ANSI Y14.17 provides for fluid power/gas diagrams that are drawn either as graphic,
pictorial, cutaway, or combination drawings. In addition to the general requirements for the preparation of
schematic diagrams provided in A.5.1.10.5, refer to the additional requirements provided in A.5.1.10.18.1
and A.5.1.10.18.2.
243
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
illustrate their relationship in the circuit. Where a component requires a specific mounting position, its
symbol should be so drawn and a NOTE added to point out the correct positioning. Spacing should provide
room for adjacent data without crowding.
c. Pictorial and combination diagrams may use single or double lines or both.
A.5.1.10.18.2.1 Single lines. Conductors which convey power actuating fluid, either pressure or return, are
called working lines and should be drawn as a single unbroken line. Conductors that carry fluid that is used
to actuate components are called pilot lines and should be drawn as a series of long dashes. Sensing lines, if
very short such as gage lines, should be drawn the same as the line to which it connects. Internal seepage of
components or exhaust pilot fluid is returned to the tank by drain lines. The lines are drawn as a series of
short dashes. Working, pilot and drain lines should be drawn thick line width. Sharp angles (90 degrees)
should be used when lines drawn between symbols change direction. Dashes should join at corners. Fluid
and electrical lines, unless they are interrelated, should not be combined in one diagram. Graphic symbols
for fluid power diagrams present symbols for both pneumatic and hydraulic media in the same diagram.
A.5.1.10.18.2.2 Double lines. Double lines should be used to illustrate the conductors in cutaway diagrams.
Double lines are sometimes used in pictorial diagrams to illustrate the piping arrangements more clearly.
The included space between double lines can be used to show relative pipe size and may also be used to
indicate functions such as working, pressure, pilot, return, drain, bleed, different fluids, etc., when
crosshatching, shading, etc., are used. Double lines should be drawn thick line width.
A.5.1.10.18.2.3 Joining lines. Single lines which join should terminate with or without a dot. If no dot is
used, then one of the two joining lines should dead end. Dash lines should begin and end with a dash of full
length at the junction with other lines. Double lines forming a junction should have square corners.
A.5.1.10.18.2.4 Crossing lines. Single and double lines should cross with or without a loop. Where dash
lines and solid lines cross, the solid line should intersect the dash and not the space between the dashes.
A.5.1.10.18.3 Component data. Nomenclature, names, notes and values are sometimes necessary in addition
to the components symbol for circuit analysis, installation or service. This component data can be either on
the diagram or be identified through the use of index numbers with an accompanying legend. For, IETMs,
the legend data may be hotlinked. If the nomenclature, name, note or value is placed on the diagram, it must
be positioned so that it does not interfere with the piping or other features of the diagram.
A.5.1.10.18.4 Rotation. Direction of rotation should be indicated by an arrow. It is understood that the
arrow is on the near side of the shaft to denote direction of rotation. Arrows pointing in opposite directions
for the same motor shaft indicate the shaft can rotate in either direction. The text covering the component
will stipulate whether the direction of rotation is as the component is viewed from the front or the rear.
244
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
A.5.1.10.18.5 Direction of flow. Direction of flow in conductors will be shown by arrowheads on single lines
or by arrows within the double lines. For IETMs, direction of flow can be depicted using animation or
color.
A.5.1.10.18.6 Port identification. Functional ports of components should be clearly identified in the
diagram. Identification should agree with the port identification on the component and its installation
drawing. Identification should appear adjacent to or within the symbol and should be as close as practical to
the port being identified (refer to figure A-32).
A.5.1.10.18.7 Pattern code. Interconnecting lines in diagrams are sometimes patterned to show pressure,
flow, special functions, return, drain, or different fluids during selected phases of operation. A note,
preferably located in the lower left corner of the sheet, should identify and illustrate the code for each
condition used. Only those lines performing active functions for the phase shown should be coded (refer to
figure A-33). For IETMs, direction of flow can be depicted using animation or color.
A.5.1.10.18.8 Component enclosure. Where some of the components in the circuit are furnished as an
assembly, it will be so indicated in the diagram. A center line should surround a complete symbol or group
of symbols which represent the assembly. The center line represents the component enclosure. A note
adjacent to the enclosure may be required to identify the component.
A.5.1.10.18.9 Identifying components. In many cases it may be more effective to identify the components of
a circuit with index numbers rather than having the component nomenclature on the illustration. When index
numbers are used, they will be placed outside the illustration area with an arrowheaded leader line to the
component. A legend will be provided on the illustration. It should be keyed to the illustration by the assigned
index number and approved nomenclature of the indexed component. For IETMs, the legend data should be
hotlinked.
245
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
246
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE A-2. Example of multiview, locator view and detail view illustrations.
247
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE A-2. Example of multiview, locator view and detail view illustrations - continued.
248
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE A-2. Example of multiview, locator view and detail view illustrations - continued.
249
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
250
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
251
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
252
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
253
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
254
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
255
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
FIGURE A-8. Example of boat symbols, numerical identifiers, and pyramid method.
256
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
257
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
258
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
259
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
260
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
261
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
262
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
263
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
264
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
265
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
266
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
267
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
268
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
269
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
270
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
271
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
272
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
273
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
274
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
275
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
276
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
277
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
278
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
279
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
280
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
281
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
282
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
283
Downloaded from http://www.everyspec.com
MIL-HDBK-3001(AS)
CONCLUDING MATERIAL
Preparing activity:
Navy - AS
(Project TMSS N313)
284
Downloaded from http://www.everyspec.com