4790.2D NAMDRP (NAMSOP)

To the Commercial AIDR Quality Team. Refer to the JDRS ST Look-up tool: Under Aircraft T/M/S, select "Lower Level" and then select "COMMERCIAL" Screening (New or COMM Reworked).

Naval Aviation Maintenance Program Standard Operating Procedures

Naval Aviation Maintenance Discrepancy Reporting Program

The Naval Aviation Maintenance Discrepancy Reporting Program (NAMDRP) establishes requirements for reporting deficiencies that impact naval aviation aircraft and equipment due to substandard materials, workmanship, and technical publications

NAMDRP establishes policy for Aircraft Delivery Deficiency Reports (ADDR), Acceptance Inspection Deficiency Reports (AIDR), Baseline Trouble Reports (BTR), Hazardous Material Reports (HMR), Product Quality Deficiency Reports (PQDR), and Technical Publication Deficiency Reports (TPDR). NAMDRP also directs policy for Engineering Investigations (EI) to determine the cause of material discrepancies that impact the airworthiness of aircraft or the safety of aircrew or maintenance personnel.

Category 1 (CAT 1) DRs are used to describe deficiencies, discrepancies, and defects that create a safety risk that could result in death or injury to personnel, risk of damage to or loss of aircraft, equipment, or facilities.

Category 2 (CAT 2 or CAT II) DRs are used to describe deficiencies, discrepancies and defects that do not create a safety risk or potential for damage, but do pose a risk to the quality of maintenance and operational readiness.

No. Deficiency reports do not fulfill the requirement for submitting a Hazard Report per OPNAVINST 3750.6 on conditions that can cause injury, illness, or death to personnel; damage to or loss of a system, equipment or property; or damage to the environment. Commands are required to submit a separate OPNAVINST 3750.6 Hazard Report when the incident or discrepancy meets the intent of both instructions.

Joint Deficiency Reporting System enables the creation, transmission and tracking of DRs. Automatically routes DRs to corresponding team depending on what type of report was created.

ADDR, AIDR, BTR, HMR, PQDR (Cat 1 & 2 only), and TPDR.

Conventional Ordnance Discrepancy Report Explosive Event Reports A report initiated upon detection of malfunctions, induced or discovered defects involving conventional ordnance, explosives, ammunition, explosive systems, and launch devices, such as bomb racks, missile or rocket launchers, and gun systems and AWSE (armament weapons support equipment)

Via AWIS. All Weapons Information System.

Explosive Mishap Report.

Will be reported to Risk Management Information (RMI) via thé Air Force Safety Automated system website.

NOTES: 1. When JDRS is not accessible, CAT I and CAT II DRs will be transmitted by naval message in the format shown in the HMR Report Message Template (Figure 10.9-1), Category 1 Technical Publication Deficiency Report (Figure 10.9-2) or Baseline Trouble Report Message (Figure 10.9-3). Priority precedence will be used for CAT I DR messages. Routine precedence will be used for CAT II messages. 2. If the FST, Quality Team, or SWPT cannot be determined, contact the JDRS Clearinghouse Representative via JDRS using the Technical Dialog tool or the "Help Menu", under the "Contract Us" link. 3. Uploading classified information or images to AWIS, JDRS, or PDREP AIS websites is strictly prohibited.

The originating activity must assign a RCN to each DR in the following format: a. Element (1) - Service Designator Code (N, V, or R) of the originating activity. • Use "N" for Navy and Marine Corps aviation non-deploying units. • Use "V" for Navy and Marine Corps Aviation Atlantic Fleet operating forces. • Use "R" for Navy and Marine Corps Aviation Pacific Fleet operating forces. b. Elements (2) through (6) - DODAAC/UIC of the originating activity, for example, 54056. c. Elements (7) and (8) - Calendar Year, for example, 10. d. Elements (9) through (12) - Locally assigned control numbers (numeric only), sequentially numbered throughout the calendar year without regard for type of report. For example, the first report of the year is an AIDR assigned control number 0001; the second report is an HMR assigned control number 0002; the third report is another AIDR assigned control number 0003; the fourth report is a TPDR assigned control number 0004. NOTE: The RCN or message report Date Time Group (DTG) must be referenced on all correspondence.

ADDRs are submitted by Depot FRCs to document deficiencies associated with inadequate periodic maintenance (PM) found by Depot FRC Aircraft Examiners during rework, modification, Planned Maintenance Interval (PMI), Integrated Maintenance Concept/Program (IMC/P), or long- term storage where the Depot FRC has accepted custody.

To the squadron that inducted the Aircraft.

The initial ADDR (including zero deficiency responses) must be submitted via JDRS within 20 calendar days of completion of the initial evaluation.

An AIDR must be submitted for all newly manufactured, modified, or newly reworked aircraft, including Planned Maintenance Intervals (PMI) and other scheduled Depot events. b. AIDRs will only list those deficiencies attributed to the manufacture, modification, or rework processes. Discrepancies not directly pertaining to the quality of rework, manufacture, or not covered in the negotiated work package or rework specification will not be reported in an AIDR. AIDRs (including No Deficiencies Noted reports) will be submitted via the JDRS website within 5 calendar days after completion of the acceptance inspection functional check flight. If no functional check flight is required, the AIDR will be submitted within 5 calendar days after completion of the acceptance inspection. The AIDR will include discrepancies noted by the ferry aircrew, if attributable to manufacture, modification, or rework process.

1. An AIDR is required even if no deficiencies attributable to manufacturing, modification, or rework processes are found. In this case, no deficiencies will be listed, and JDRS will auto-default to a "No Deficiency Noted, AIDR". 2. An AIDR is not required for Depot In-Service Repairs (ISR). Document discrepancies with ISR work on a Field Maintenance Team Feedback Report per local instructions. 3. Do not use an AIDR to report equipment shortages, ferry or shipping damages, or deterioration during pool storage. Contact the providing activity for resolution. 4. Malfunction Code "174" will be used on AIDRs, Work Order (WOs), and Maintenance Action Forms (MAFs) related to AIDR deficiencies.

1. Manufacturing, modification, or rework process deficiencies found within 30 calendar days of the initial AIDR will be reported on a supplemental AIDR using a new RCN. Add "Supplemental" to the title in block 6; i.e., change from Initial AIDR to Supplemental AIDR. 2. Components or parts deficiencies discovered during initial acceptance of newly manufactured, modified, or reworked aircraft must also be reported on a PQDR per paragraph 10.9.3.4. The PQDR will be referenced in block 3B of the AIDR.

To the Depot FRC AIDR Quality Team. Refer to the JDRS ST Look-up tool: Under Aircraft T/M/S, select "Lower Level" and then select "ORGANIC" Screening (NAVAIR Reworked).

Detailed descriptions of defects, corrective actions taken by the originator and any parts involved. They will either be categorized as Critical, Major or Minor.

Defects that create hazardous or unsafe condition with risk to the airworthiness of the aircraft or the safety of personell.

1. Critical Deficiencies on components or parts discovered defective during initial acceptance of newly manufactured, modified, or newly reworked aircraft must also COMNAVAIRFORINST 4790.2D 1 Feb 2021 10-105 be reported as a CAT I PQDR per paragraph 10.9.3.9. The PQDR will be referenced in Block 3B of the AIDR. 2. Critical Deficiencies in systems, for example, fuel system or hydraulic system contamination, FOD, or logbook errors are Critical in nature and will be documented as a Critical deficiency without a CAT I PQDR submitted.

Defects that are not an airworthiness or safety risk, but do materially reduce the operational capability of the aircraft.

Defects that do not materially reduce operational capability of the aircraft, but do depart from established quality standards.

A report that documents deficiencies for Naval Aviation Logistics Command Management Information System (NALCOMIS) Optimized Organization Management Activity (OOMA) that prevent the issuance of Work Order (WOs) for inspections, Technical Directives (TDs), or unscheduled maintenance against aircraft or tracked components.

(1) Wrong work unit code (WUC) to CAGE or part number (P/N) relationship (2) Items with no WUC (3) Incorrect removal intervals for life limited components (4) TDs not in the baseline (5) Incorrect inspections intervals for an aircraft or tracked component, such as aircraft armament equipment, mission mounted equipment, and aerial refueling stores

via the JDRS website. When JDRS is not accessible, BTRs will be submitted by priority naval message, addressed to the Baseline Help Desk COMFRC FST HQ Technical Data Department with info copy to COMNAVAIRFOR (N421) and the appropriate Type Wing, per the Baseline Trouble Report Message

A CODR reports incidents where ordnance or weapon systems fail to function per the design or intent of the system and result in no property damage or injury

improper storage, explosives, ammunition, explosive systems or devices, including weapon systems components that come in direct contact with the ordnance (e.g., ammunition, explosives, missiles) and AWSE or Ordnance IMRL items used to manufacture, fire, handle, test, load, deliver, store or transport ordnance.

An EER reports accidents or incidents involving conventional ordnance, ammunition, explosives, explosive systems and devices resulting in an unintentional detonation, firing, deflagration, burning, launching of ordnance material (including all ordnance impaction off range), leaking or spilled propellant fuels and oxidizers (less OTTO fuel II), or chemical agent release. This pertains to all events that do not meet the severity classification of a Class A, B, or C mishap per OPNAVINST 5102.1.

Via the All Weapons Information System (AWIS) website

An EMR reports accidents and incidents defined as explosive mishaps which meet a severity classification of class A, B, or C per OPNAVINST 5102.1.

EMRs will be reported using Risk Management Information (RMI), even if an ordnance system works as designed, and human error contributed to an incident or accident. Any explosive event not meeting one of these severity classifications will be reported as an EER. EMRs will be reported to Risk Management Information (RMI) and monitored via the Air Force Safety Automated System website d. Ordnance PQDRs will be submitted via the JDRS website (https://jdrs.mil), per the procedures of 10.9.3.9.

If a Weapons Department is receiving AWSE maintenance support from an I-level activity, the Weapons Department and I-level activity will provide each other with a copy of submitted AWSE DRs.

A physical examination of discrepant material conducted by the designated Fleet Support Team (FST) to determine the root cause of defects and deficiencies.

HMR, PQDR (Cat 1 or 2)

(1) To support investigations of material associated with aircraft or grand mishaps, lightning strikes, electromagnetic interference, and stray voltage problems (2) To investigate a component rejected by the Navy Oil Analysis Program (NOAP) after all authorized repairs are attempted (3) To support the mandatory investigation requirements of Activated Aircraft Emergency Egress Systems per OPNAVINST 3750.6 (4) When aircraft readiness is seriously impaired due to poor material reliability (including Support Equipment) (5) When directed by higher authority.

The FST engineer for the discrepant material or equipment is responsible for determining whether an EI will be conducted, closed with a final response, or closed administratively

A HMR is a report that is submitted for any material deficiency, which, if not corrected, could result in death or injury to personnel, or damage to or loss of aircraft, equipment, or facilities. AN HMR MUST BE SUBMITTED REGARDLESS OF HOW OR WHEN THE DISCREPANT CONDITION WAS DETECTED.

All HMRs are considered Category 1 safety discrepancies and must be submitted within 24 hours of discovery of any of the following conditions: (1) Malfunction or failure of a component, which, if not corrected, could result in death or injury to personnel, or damage to or loss of aircraft, equipment, or facilities. (2) A configuration deficiency in aircraft, engines, support equipment (SE), or components that creates a safety hazard. (3) A design flaw that allows incorrect installation of parts resulting in possible system malfunction or failure. (4) In-flight or ground loss of aircraft parts (things falling off aircraft (TFOA)) in which maintenance or material factors are involved. HMRs are submitted via the JDRS website

1. When JDRS is not accessible; HMR will be reported by priority precedence message, within 24 hours of discovery, using the HMR and PQDR Message Template (Figure 10.9-1). 2. For HMR incidents where lack of training or improper training in maintenance procedures is a contributor to the discrepancy or incident, the Center for Naval Aviation Technical Training Unit, Pensacola, FL will be included in the "info" block of the HMR PLA: CENNAVAVNTECHTRA PENSACOLA, FL. 3. Things falling off aircraft related to Aircraft Armament System (AAS) parts or components will be dual-reported as an HMR per this instruction and a CODR per OPNAVINST M-8000.16. 4. Due to DOD service differences in JDRS terminology, an HMR is submitted in JDRS as a "CAT I EI with HMR intent."

for new or newly reworked material, products, and software with deficiencies attributable to the use of poor quality material, or substandard workmanship by the supplier, contractor, or rework facility The deficiency must have been discovered during receipt COMNAVAIRFORINST 4790.2D 1 Feb 2021 10-108 inspection or during the initial installation, initial operational check, or first flight with the material installed. PQDRs will also be submitted for materials that fail prematurely during the specified warranty period and for materials manufactured or maintained under a Performance Based Logistics (PBL) or Contract Logistics Support (CLS) contract

NOTES: 1. When JDRS is not accessible; HMR will be reported by priority precedence message, within 24 hours of discovery, using the HMR and PQDR Message Template (Figure 10.9-1). 2. For HMR incidents where lack of training or improper training in maintenance procedures is a contributor to the discrepancy or incident, the Center for Naval Aviation Technical Training Unit, Pensacola, FL will be included in the "info" block of the HMR PLA: CENNAVAVNTECHTRA PENSACOLA, FL. 3. Things falling off aircraft related to Aircraft Armament System (AAS) parts or components will be dual-reported as an HMR per this instruction and a CODR per OPNAVINST M-8000.16. 4. Due to DOD service differences in JDRS terminology, an HMR is submitted in JDRS as a "CAT I EI with HMR intent."