49 CFR Part 557, Petitions for Hearings on Notifications and Remedy on Defects

Forms and Documents

Forms and supporting documents for this ICR

Document	Type	Status	Availability
2127-0039 Supporting Statement_2018.doc	Supporting Statement A	Uploaded 2018-06-05	Available

IC Document Collections

Information collection document groups

IC ID	Collection	Type	Status	Form
26159	49 CFR Part 557, Petitions for Hearings on Notifications and Remedy on Defects		Unchanged

ICR Details

OMB Control No: 2127-0039	ICR Reference No: 201806-2127-004
Status: Active	Previous ICR Reference No: 201407-2127-003
Agency/Subagency: DOT/NHTSA	Agency Tracking No:
Title: 49 CFR Part 557, Petitions for Hearings on Notifications and Remedy on Defects
Type of Information Collection: Reinstatement without change of a previously approved collection	Common Form ICR:  No
Type of Review Request: Regular
OIRA Conclusion Action: Approved without change	Conclusion Date: 03/22/2019
	Date Received in OIRA: 06/29/2018
Terms of Clearance:

table that charts list comparision

	Inventory as of this Action	Requested	Previously Approved
Expiration Date	03/31/2022	36 Months From Approved
Responses	1	0	0
Time Burden (Hours)	1	0	0
Cost Burden (Dollars)	0	0	0

---

Abstract: 49 CFR Part 557 allows anyone to petition the agency for a hearing to determine if a manufacturer has reasonably met its obligation to notify owners, purchasers, and dealers of a safety defect or noncompliance, and to remedy that safety defect or noncompliance.Persons who believe that a manufacturer has been deficient in notifying owners, purchasers, or dealers of a safety related defect or noncompliance with FMVSS, or has not remedied the problem in accordance with statutory requirements, may petition the agency pursuant to 49 CFR Part 557. The agency uses the petition, and may use other information available to it, to determine whether a hearing is necessary to determine whether a manufacturer has reasonably met its obligation to notify owners, purchasers, and dealers of the safety defect or noncompliance with FMVSS, or to remedy that defect or noncompliance. Should the agency, on the basis of information provided at that hearing or other information, determine the manufacturer has not reasonably met its obligations, the agency orders the manufacturer to take specified action to bring itself into compliance with those obligations.

---

Authorizing Statute(s): US Code: 49 USC 30118 and 30120 Name of Law: Transportation, Chapter 301- Motor Vehicle Safety
  

Citations for New Statutory Requirements: None

---

Associated Rulemaking Information
RIN:	Stage of Rulemaking:	Federal Register Citation:	Date:
	Not associated with rulemaking

---

Federal Register Notices & Comments
60-day Notice:	Federal Register Citation:	Citation Date:
	83 FR 7297	02/20/2018
30-day Notice:	Federal Register Citation:	Citation Date:
	83 FR 23523	05/21/2018
Did the Agency receive public comments on this ICR? No

---

Number of Information Collection (IC) in this ICR: 1

table that charts list of burden

IC Title	Form No.	Form Name
49 CFR Part 557, Petitions for Hearings on Notifications and Remedy on Defects

---

ICR Summary of Burden

table that charts list of burden

	Total Approved	Previously Approved	Change Due to New Statute	Change Due to Agency Discretion	Change Due to Adjustment in Estimate	Change Due to Potential Violation of the PRA
Annual Number of Responses	1	0	0	0	0	1
Annual Time Burden (Hours)	1	0	0	0	0	1
Annual Cost Burden (Dollars)	0	0	0	0	0	0

Burden increases because of Program Change due to Agency Discretion: No

Burden Increase Due to:

Burden decreases because of Program Change due to Agency Discretion: No

Burden Reduction Due to:

Short Statement:

---

Annual Cost to Federal Government: $0

Does this IC contain surveys, censuses, or employ statistical methods? No

Does this ICR request any personally identifiable information (see OMB Circular No. A-130 for an explanation of this term)? Please consult with your agency's privacy program when making this determination.     No

Does this ICR include a form that requires a Privacy Act Statement (see 5 U.S.C. §552a(e)(3))? Please consult with your agency's privacy program when making this determination.     No

Is this ICR related to the Affordable Care Act [Pub. L. 111-148 & 111-152]? No

Is this ICR related to the Dodd-Frank Wall Street Reform and Consumer Protection Act, [Pub. L. 111-203]? No

Is this ICR related to the American Recovery and Reinvestment Act of 2009 (ARRA)? No

Is this ICR related to the Pandemic Response? Uncollected

---

Common Form ICR:  No

---

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).

The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:

(a) It is necessary for the proper performance of agency functions;

(b) It avoids unnecessary duplication;

(c) It reduces burden on small entities;

(d) It uses plain, coherent, and unambiguous language that is understandable to respondents;

(e) Its implementation will be consistent and compatible with current reporting and recordkeeping practices;

(f) It indicates the retention periods for recordkeeping requirements;

(g) It informs respondents of the information called for under 5 CFR 1320.8 (b)(3) about:

(i) Why the information is being collected;

(ii) Use of information;

(iii) Burden estimate;

(iv) Nature of response (voluntary, required for a benefit, or mandatory);

(v) Nature and extent of confidentiality; and

(vi) Need to display currently valid OMB control number;

(h) It was developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected.

(i) It uses effective and efficient statistical survey methodology (if applicable); and

(j) It makes appropriate use of information technology.

If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.

Certification Date: 06/29/2018

---