NHTSA Interpretation File Search
Overview
NHTSA's Chief Counsel interprets the statutes that the agency administers and the standards and regulations that it issues. Members of the public may submit requests for interpretation, and the Chief Counsel will respond with a letter of interpretation. These interpretation letters look at the particular facts presented in the question and explain the agency’s opinion on how the law applies given those facts. These letters of interpretation are guidance documents. They do not have the force and effect of law and are not meant to bind the public in any way. They are intended only to provide information to the public regarding existing requirements under the law or agency policies.
Understanding NHTSA’s Online Interpretation Files
NHTSA makes its letters of interpretation available to the public on this webpage.
An interpretation letter represents the opinion of the Chief Counsel based on the facts of individual cases at the time the letter was written. While these letters may be helpful in determining how the agency might answer a question that another person has if that question is similar to a previously considered question, do not assume that a prior interpretation will necessarily apply to your situation.
- Your facts may be sufficiently different from those presented in prior interpretations, such that the agency's answer to you might be different from the answer in the prior interpretation letter;
- Your situation may be completely new to the agency and not addressed in an existing interpretation letter;
- The agency's safety standards or regulations may have changed since the prior interpretation letter was written so that the agency's prior interpretation no longer applies; or
- Some combination of the above, or other, factors.
Searching NHTSA’s Online Interpretation Files
Before beginning a search, it’s important to understand how this online search works. Below we provide some examples of searches you can run. In some cases, the search results may include words similar to what you searched because it utilizes a fuzzy search algorithm.
Single word search
Example: car
Result: Any document containing that word.
Multiple word search
Example: car seat requirements
Result: Any document containing any of these words.
Connector word search
Example: car AND seat AND requirements
Result: Any document containing all of these words.
Note: Search operators such as AND or OR must be in all capital letters.
Phrase in double quotes
Example: "headlamp function"
Result: Any document with that phrase.
Conjunctive search
Example: functionally AND minima
Result: Any document with both of those words.
Wildcard
Example: headl*
Result: Any document with a word beginning with those letters (e.g., headlamp, headlight, headlamps).
Example: no*compl*
Result: Any document beginning with the letters “no” followed by the letters “compl” (e.g., noncompliance, non-complying).
Not
Example: headlamp NOT crash
Result: Any document containing the word “headlamp” and not the word “crash.”
Complex searches
You can combine search operators to write more targeted searches.
Note: The database does not currently support phrase searches with wildcards (e.g., “make* inoperative”).
Example: Headl* AND (supplement* OR auxiliary OR impair*)
Result: Any document containing words that are variants of “headlamp” (headlamp, headlights, etc.) and also containing a variant of “supplement” (supplement, supplemental, etc.) or “impair” (impair, impairment, etc.) or the word “auxiliary.”
Search Tool
NHTSA's Interpretation Files Search
Interpretations | Date |
---|---|
search results table | |
ID: AIT.jegOpenMr. Daniel H. Fagerstrom Dear Mr. Fagerstrom: This responds to your inquiry whether a "truck-mounted hydraulic crane 'bundle extractor'" you wish to import is considered a motor vehicle that would have to comply with the applicable Federal Motor Vehicle Safety Standards. You submitted your inquiry on behalf of your client, Hydro-Engineering, Inc. According to your letter, the unit "comprises a used Peinemann Truck Mounted Bundle Extractor (TMBE) which consists of a hydraulic crane apparatus permanently mounted on a special-order Mercedes diesel truck chassis." The TMBE is used to remove, handle, and replace bundles of heat exchanger and cooling tubes from industrial heat exchangers and cooling towers. The work for which the TMBE is designed is performed in oil refineries, electric power and process chemical plants, or other similar heavy industrial settings. You stated that "(t)ypically the TMBE spends extended periods of time at a single jobsite." You also stated that the intended use of the TMBE is definitely that of off-road applications, and that there are numerous features of its design and construction that make it unsuitable for anything other than sporadic, short-term road travel. By way of background information, the National Highway Traffic Safety Administration (NHTSA) interprets and enforces the laws under which the Federal motor vehicle safety standards are promulgated. NHTSA's statute defines the term "motor vehicle" as follows:
Whether the agency considers a vehicle such as you describe to be to be a motor vehicle depends on its use. It is the agency's position, for example, that this statutory definition does not encompass mobile construction equipment, such as cranes and scrapers, which use the highway only to move between job sites and which typically spend extended periods of time at a single job site. In such cases, the on-highway use of the vehicle is merely incidental and is not the primary purpose for which the vehicle was manufactured. In contrast are instances where vehicles, such as dump trucks, frequently use the highway going to and from job sites, and stay at a job site for only a limited time. Such vehicles are considered motor vehicles, since the on-highway use is more than "incidental." Based on the information you provided, it appears that the TMBE is not a "motor vehicle" within the meaning of the statutory definition. I hope this information is helpful. Sincerely, |
2000 |
ID: Alani.1OpenMr. Y. Alani Dear Mr. Alani: This is in response to your letter and subsequent e-mail to Eric Stas in which you requested clarification as to the proper application of speed rating codes for replacement tires. Specifically, your letter asked whether it would be permissible to replace original equipment tires with an "H" speed rating with replacement tires with a "T" speed rating, whether it would be permissible to place "H"-rated tires on the front axle and "T"-rated tires on the rear axle of a vehicle, and whether a damaged "H"-rated tires would retain that designation after being repaired. For the reasons discussed below, the National Highway Traffic Safety Administration (NHTSA) cannot advise you as to the proper application of these codes. Speed ratings are not required under our Federal motor vehicle safety standards (FMVSSs). It is our understanding that the tire speed rating system was established by the European Tyre and Rim Technical Organization (ETRTO), so you may wish to consult with that organization about the proper application of such codes (see http://www.etrto.org/pub_gb.html for contact information.) We assume that you wrote to us because some tires sold in the U.S. are labeled with speed rating codes. By way of explanation, NHTSA is authorized to issue FMVSSs that set performance requirements for new motor vehicles and items of motor vehicle equipment (e.g., tires) introduced into the U.S. market. NHTSA does not issue approvals of these products, but instead, a manufacturer of motor vehicles or motor vehicle equipment must self-certify that its products meet all applicable safety standards, prior to offering such products for sale in the United States. Under our FMVSSs related to tires, manufacturers are not required to label tires with speed ratings. However, tire manufacturers are permitted to label additional information on the sidewall of tires, including speed rating codes, provided that the additional information does not obscure or confuse the meaning of the required information, or otherwise defeat its purpose. If you have further questions, you may contact Eric Stas of my staff at (202) 366-2992. Sincerely, Jacqueline Glassman ref:109 d.6/21/05 |
2005 |
ID: Alliance 114OpenMr. Robert Strassburger Vice President Safety Vehicle Safety and Harmonization Alliance of Automobile Manufacturers 1401 Eye Street, N.W., Suite 900 Dear Mr. Strassburger: This letter responds to your May 14, 2010 request, on behalf of the Association of International Automobile Manufacturers, Inc. (AIAM) and the Alliance of Automobile Manufacturers (Alliance), for clarification regarding the brake transmission shift interlock (BTSI) provisions of the Cameron Gulbransen Kids Transportation Safety Act of 2007 (K.T. Safety Act). NHTSA incorporated the BTSI provisions into Federal Motor Vehicle Safety Standard (Standard) No. 114, Theft Protection and Rollaway Prevention (49 CFR 571.114, S5.3), by a final rule dated March 30, 2010 (75 FR 15621). You ask for confirmation that the BTSI requirement does not apply to the gear selection control override option permitted by S5.2.4 of Standard No. 114. Our answer is the BTSI requirement would not apply to a gear selection control override. Background Currently, S5.2.2 of Standard No. 114 requires that a vehicle with a park position must be designed so that the transmission or gear selection control cannot be moved from the park position unless the key is in the starting system. An exception to this requirement is provided in S5.2.4, to allow a gear selection control override option. Specifically, S5.2.4 states, in pertinent part: The vehicle may have a device by which the user can move the gear selection control from park after the key has been removed from the system. This device must be operable by one of [three specified options]. In August 2006, the Alliance and the AIAM developed a voluntary agreement requiring full implementation of a BTSI system not later than September 1, 2010. A BTSI system requires that the service brake pedal be depressed before the transmission can be shifted out of the park position and must function in any starting system key position. A BTSI system is designed to prevent an unattended child from shifting the transmission out of the park position when the child is left in a vehicle with the vehicles key. The voluntary agreement was substantially incorporated into a self-executing provision of the K.T. Safety Act.[1] The Act specifies in Section 2(d)(1): Each motor vehicle with an automatic transmission that includes a park position manufactured for sale after September 1, 2010, shall be equipped with a system that requires the service brake to be depressed before the transmission can be shifted out of park. This system shall function in any starting system key position in which the transmission can be shifted out of park. In August 2009, NHTSA issued an NPRM that proposed to incorporate the text of the BTSI requirement from the K.T. Safety Act into new paragraph S5.3 of Standard No. 114.[2] AIAM commented on and generally supported that proposal, but requested a gear selection control override option analogous to that provided in S5.2.4, which would override the BTSI system and allow a vehicle to be shifted out of park without depressing the service brake. In the final rule, NHTSA rejected the AIAMs request, citing three reasons.[3] First, NHTSA noted that it was not clear that such an override is permissible within the language of the K.T. Safety Act. Second, NHTSA stated that it was outside the scope of the rulemaking to incorporate the override. Third, AIAM did not make clear why the lack of override would create the consumer backlash it had said would occur. On May 11, 2010, representatives from the AIAM and the Alliance met with NHTSA staff to explain what AIAM representatives characterized as unclear text in AIAMs comment, which you thought could have led to a possible misunderstanding by the agency of the comment. In a follow-on letter dated May 14, 2010, you wrote NHTSA clarifying that AIAM was not seeking a separate override of the BTSI system, but was instead seeking to make sure the preexisting override option of S5.2.4 continues. Discussion First, we must acknowledge the difference, as we understand it, between the AIAMs comments on the August 2009 NPRM and your current request in the May 14, 2010 letter. It is correct that we understood your comment on the August 2009 NPRM to request that we allow a separate gear selection control override option, similar to that allowed by S5.2.4, for the BTSI requirement in S5.3. We now understand your request to be limited solely to the relationship between the existing gear selection control override option in S5.2.4 and the BTSI requirement of S5.3. We address this issue below. In the August 2009 NPRM, NHTSA sought comments on four interpretations of various provisions of the K.T. Safety Act. In one in particular, we interpreted the last sentence of section 2(d) of the K.T. Safety Act, which states: This system shall function in any starting system key position in which the transmission can be shifted out of park. We stated in the
preamble that this sentence means that no matter the starting system position the key is in (e.g., lock, accessory, or start) the transmission must only shift out of park when the service brake is depressed.[4] We believe that the emphasized language above conveyed our understanding that a BTSI system need only function when the key is in the starting system. We do not believe that it is necessary that a BTSI system function when the key is not in the starting system. The BTSI safeguard is unnecessary when the key is not in the system because S5.2.2 of Standard No. 114 already requires that a vehicle be designed such that the transmission or gear selection control cannot be moved from the park position unless the key is in the starting system. Thus, it would be superfluous to require that a BTSI system be operational when the key is not in the starting system because the vehicle already cannot be shifted out of park in that situation (i.e., without the key in the starting system). Because the BTSI system applies only when the key is in the starting system, the BTSI requirement does not apply to the operation of a gear selection control override option allowed by S5.2.4 of Standard 114. The gear selection control override is to function (allowing the user to shift out of park) after the key has been removed from the starting system. Thus, a gear selection control override option would not be subject to the BTSI requirement, which applies only when the key is in the starting system. Although we believe that the foregoing analysis addresses your concerns, we wish to make the following clarification in response to some language in your letter. In your letter, you express concern that a BTSI system is required to be operational with the key in the vehicle but the starting system in an off position. Included in S5.3 of FMVSS No. 114 is the statement from the K.T. Safety Act: This [BTSI] system shall function in any starting system key position in which the transmission can be shifted out of park. If a vehicle is designed in a manner such that the transmission cannot be shifted out of park when the starting system is in the off position (even if the key is in the starting system), the BTSI system need not function when the starting system is in the off position. As we stated above, if it is not possible to shift out of park, a BTSI system is superfluous. If a vehicle can be shifted out of park with the key in the starting system in the off position, the BTSI requirement applies to prevent the vehicle from being shifted out of park without applying the service brake. You requested in your letter that, if we cannot confirm your interpretation that the BTSI requirement does not apply to the gear selection control override option permitted by S5.2.4 of Standard No. 114, we treat your request as a petition for reconsideration of the BTSI final rule. Because we have confirmed your interpretation, we consider this letter to be a complete response to your request. I hope this information is helpful. An identical response has been sent to Mr. Michael X. Cammisa of the AIAM. If you have any further questions, please feel free to contact David Jasinski of my office at (202) 366-2992. Sincerely yours, O. Kevin Vincent Chief Counsel Dated: 7/20/2010 |
2010 |
ID: Alliance Letter - Sale of Electronic Odometer Resetting DevicesOpenCERTIFIED MAIL Robert Strassburger Alliance of Automobile Manufacturers 1401 Eye Street, N.W., Suite 900 Washington, D.C. 20005-6562 Re: Legality of electronic devices that change odometer readings on motor vehicles Dear Mr. Strassburger: This letter is in reference to an April 9, 2013 conference call you had with David Sparks of the National Highway Traffic Safety Administration (NHTSA). During that conference call, you requested NHTSAs view on the legality of devices that have appeared for sale on the internet that purport to change the mileage showing on electronic odometers of motor vehicles. These are essentially hand-held devices that connect directly with a vehicles on-board computer system through the vehicles diagnostic port and provide the user the ability to change the mileage displayed on the vehicles electronic odometer. In the Agencys view, marketing for sale, sale, and/or use of such a device to change an odometer display constitute violations of Federal law. NHTSA would like to initiate a dialogue with the manufacturers concerning the implications of these devices ability to circumvent the algorithms used to secure a vehicles odometer reading. Pursuant to 49 U.S.C. 32703(1), a person may not advertise for sale, sell, use, install, or have installed, a device that makes an odometer of a motor vehicle register a mileage different from the mileage the vehicle was driven, as registered by the odometer within the designed tolerance of the manufacturer of the odometer. It is NHTSAs view that the marketing for sale and sale of hand-held devices that are capable of accessing a motor vehicles computer system to alter the mileage displayed on the vehicles odometer violates 49 U.S.C. 32703(1). These devices make odometers register a mileage different from the mileage the vehicle was driven, whether or not the device is actually used to do so, and thus their marketing and sale violate the statutes prohibition. As a result of the changes made by the MAP 21 statute last year, NHTSA can now impose civil penalties of $10,000 for each violation up to a maximum of $1,000,000 for a related series of violations under 49 U.S.C. 32709. We have also enclosed a copy of the related interpretation letters to Kenneth Rose and Dwayne Bitz, both dated May 31, 2012 that David Sparks referenced in your conference call. For your information we are posting copies of these interpretation letters to NHTSAs public database at http://isearch.nhtsa.gov. I hope this information adequately addresses your concerns. If you need any further assistance in this matter, please contact Marie Choi of my staff at (202) 366-1738 or by email at marie.choi@dot.gov. Sincerely, O. Kevin Vincent Chief Counsel Enclosure Date: 8/7/13 |
2013 |
ID: alliance(9-2-03).ajdOpenMr. Robert S. Strassburger Dear Mr. Strassburger: This is in reply to your letter of September 2, 2003, regarding my July 21, 2003 letter to Mr. Cavallo of Halcore Group, Inc., which discussed the early warning reporting (EWR) responsibilities of small volume manufacturers. I had advised Mr. Cavallo that "[f]or the purposes of determining whether the production of vehicles meets or exceeds the 500 vehicles per year threshold in Section 579.21 et seq., the production of the divisions, parent, subsidiaries and affiliates must be aggregated." This interpretation is consistent with other letters interpreting the EWR regulation.See Letter from Jacqueline Glassman to John D. Evans of April 11, 2003, at p. 3; Letter from Jacqueline Glassman to Rod Nash of August 20, 2003, at p. 2; and Letter from Jacqueline Glassman to Rod Nash of October 10, 2003. You assert that the interpretation that I provided to Mr. Cavallo was inconsistent with statements made by a person other than the Chief Counsel at a public meeting. The September 24, 2002 public meeting you reference concerned technical issues, such as security and acknowledgement of submissions, regarding electronic EWR submissions to the agency. The Federal Register Notice announcing this meeting was clear that this was to be only a technical meeting. See 67 FR 55448. Moreover, at the time of the meeting, we expressly stated that the information presented was not binding upon the agency, and that nothing stated at the meeting should be construed as a final NHTSA interpretation. Transcript p. 8. [1] In addition, the Alliance of Automobile Manufacturers (Alliance) and its members are familiar with NHTSAs interpretive processes. As such, the Alliance is fully aware that the Chief Counsel is the only NHTSA official with authority to issue interpretations of agency regulations. See 49 CFR 501.8(d)(4). Second, you state that the interpretation in the Cavallo letter is inconsistent with how the agency intends to use the information collected from EWR, as stated in the final rule. You also said that the value in the information provided by low volume manufacturers is very limited when conducting trend analysis because a single incident can look like a high "incident rate" relative to the performance of other vehicles manufactured in larger quantities. In addition, you concluded that "the agencys guidance from September 2002 public meeting regarding the limited reporting requirements for low volume subsidiaries makes sense in the overall context of the EWR rule and the uses to which NHTSA plans to put the EWR information." We disagree with your conclusion. The statement was not "the agencys guidance." We determined that the 500 unit production threshold is the appropriate demarcation point in part based on small business concerns. We also determined that aggregate reporting is appropriate in order to capture all vehicles manufactured by an entity with affiliates or subsidiaries. Moreover, while a single incident may skew the "incident rate" relative to other vehicles, it is not the only factor that controls NHTSAs initiation of a defect investigation or the determining factor in deciding to issue an initial determination. Also, EWR information will not be the sole basis for opening a defect investigation. As we stated in the preamble to the final rule, "if we identify matters that might possibly suggest the existence of a defect, we plan to seek additional clarifying information from the manufacturer in question, and from other sources, to help us to decide whether to open a formal defect investigation." 45822 FR at 45865. We see no reason to vary from our current position. Lastly, you stated that, in the context of FMVSS No. 208 phase-in requirements, the agency in an interpretation letter previously determined that low volume subsidiaries of larger parent companies retain their low volume status. As you recognize in your letter, a letter interpreting FMVSS No. 208 does not control the interpretation of the EWR regulation. We also noted in that letter that the interpretation provided therein only reflected consideration of factors underlying FMVSS No. 208, and did not provide guidance for interpreting any other regulatory provisions. See Letter from John Womack to Grant Nakayama of August 22, 2001. We do not believe that the concerns underlying that interpretation letter are the same as those underlying the EWR regulation. First, the exclusion of low volume subsidiaries from the phase-in requirements of FMVSS No. 208 reflected the technical challenges faced by smaller manufacturers given the complexity of the advanced air bag requirements. Second, that exclusion simply deferred compliance with the advanced air bag rule by low volume subsidiaries to the end of the phase-in period. In contrast, your suggestion would, in effect, totally exclude low volume subsidiaries from the comprehensive reporting requirements of the EWR regulation. If you have any questions, you may call Andrew DiMarsico of this Office (202-366-5263). Sincerely, Jacqueline Glassman ref:579 [1] Docket NHTSA 2001-8677-530. Available at http://dms.dot.gov. |
2003 |
ID: Alliance.1OpenRobert Strassburger, Vice President Dear Mr. Strassburger: This acknowledges receipt of your October 24, 2005, letter regarding our September 7, 2005, final rule responding to petitions for reconsideration under Federal Motor Vehicle Safety Standard (FMVSS) No. 138, Tire Pressure Monitoring Systems (TPMS)(70 FR 53079). Specifically, your letter raised an issue with paragraph S4.4(c)(2) of the standard, which sets requirements for flashing a combined low tire pressure/TPMS malfunction telltale for a period of 60-90 seconds to indicate to the driver when one or more malfunctions in the TPMS have occurred. The Alliance believes that this provision of the standard, as explained in the final rule, is design restrictive to the extent that the flashing sequence for a combined TPMS telltale is permitted only once per ignition cycle, regardless of the number of TPMS malfunctions encountered. Your letter also, argued that there is not a safety need to restrict the combined TPMS telltale to a single flashing sequence in the rare event of multiple TPMS malfunctions. According to the Alliance, many current TPMSs have design architectures that automatically send a TPMS malfunction alert each time a new malfunction is detected, and you suggested that for manufacturers using such systems, a redesign would not be practicable before the September 1, 2007, compliance date for the TPMS malfunction indicator requirement. Consequently, your letter requested that the agency permit, but not require, vehicle manufacturers to install TPMSs with combined telltales that reinitiate the prescribed flashing sequence upon detection of subsequent TPMS malfunctions. Your letter sought this result either through a letter of interpretation of S4.4(c)(2), or alternatively, you asked that your letter be treated as a petition for reconsideration of the September 7, 2005, final rule. Given the language of the standard and the preambles generally clear explanation of the agencys expectations regarding the requirements of S4.4(c)(2), we do not believe that the issue you have raised is amenable to a response via a letter of interpretation. Accordingly, we have decided to treat your letter as a petition for reconsideration of the final rule, and after careful consideration of the issue you have raised, we will respond accordingly. If you have further questions, please feel free to contact Mr. Eric Stas of my staff at (202) 366-2992. Sincerely, Stephen P. Wood cc: Docket No. NHTSA-2005-22251 |
2005 |
ID: Alliance.jegOpenRobert S. Strassburger, Vice President Dear Mr. Strassburger: This responds to your letter seeking our concurrence that "Alliance members are allowed to combine the fleets of motor vehicle manufacturing subsidiaries owned by Alliance members for purposes of determining the overall fleet compliance with the compliance percentages set forth in various safety standard phase-in requirements." As discussed below, we generally agree with your suggested interpretation. In your letter, you note that, in our mid-1980s rulemaking establishing the phase-in requirements associated with automatic occupant protection requirements for passenger cars, we addressed the need to accommodate complex relationships among manufacturers. See NPRM proposing phase-in requirements for Standard No. 208, 50 FR 14589, 14595-97, April 12, 1985. In that rulemaking, we adopted an attribution rule that generally permits companies to agree among themselves which entity will be treated as the manufacturer for purposes of meeting the phase-in percentages when any of those companies could be considered the "manufacturer." We have adopted similar attribution rules in subsequent rulemakings involving phase-ins. You state in your letter that "(a)s Alliance members have consistently interpreted these phase-in requirements, member companies with ownership interests in other motor vehicle manufacturers have been able to combine the fleets for reporting purposes to the agency." You note, however, that in a recent interpretation to Mr. Nakayama of Kirkland & Ellis regarding the status of certain small volume manufacturers, we observed: (T)he vehicles of related manufacturers are not ordinarily grouped together for purposes of determining compliance with phase-ins of new safety standards. We note that this is in contrast to determinations of compliance with fuel economy standards, where vehicles of related manufacturers are grouped together. However, the grouping of vehicles of related manufacturers for purposes of fuel economy standards is done pursuant to an explicit statutory provision. You state that the Alliance "understands the above observation reaffirms that vehicles of related manufacturers are not ordinarily required to be grouped together by the Safety Act, unlike the contrasting situation for fuel economy." You state further, however, that because of the potential for the first sentence of the quoted paragraph to be misunderstood, particularly if it is taken out of context, the Alliance "seeks confirmation that a group of related vehicle manufacturers may continue to choose, if they so desire, to combine fleets for safety standard phase-in purposes." In considering your letter, we note that, in interpreting the provision at issue, we have not taken the position that we would consider a particular vehicle to have been manufactured by two or more manufacturers solely based on the corporate relationships between those manufacturers. We considered this issue to some degree in a September 18, 1987, interpretation to General Motors (GM), addressing whether it could be deemed the manufacturer of passenger cars produced by Lotus for purposes of the phase-in of the automatic occupant protection requirements. In our interpretation, we noted that in the April 1985 NPRM proposing phase-in requirements for Standard No. 208, we had stated that we consider the statutory definition of "manufacturer" to be sufficiently broad to include "sponsors," depending on the circumstances. We stated in the NPRM that if a sponsor contracts for another manufacturer to produce a design exclusively for the sponsor, the sponsor may be considered the manufacturer of those vehicles, applying basic principles of agency law. We presented the following analysis to support our conclusion that GM could be considered the manufacturer of Lotus passenger cars: Both LCL, the actual assembler, and LPC, the actual importer, are wholly-owned subsidiaries of GM. By itself, GM's ownership of both the producer and importer of these cars might not be sufficient to establish that GM was the sponsor of these vehicles for the purposes of Standard No. 208. In addition, however, another GM wholly-owned subsidiary distributes and markets the vehicles in the United States. GM coordinates the activities of all these subsidiaries. Since GM wholly owns the actual producer of these vehicles and is actively involved in the importation, distribution, and marketing of these vehicles, we believe that GM should be considered to sponsor the importation of the Lotus vehicles. Accordingly, GM rather than LPC, may be considered the importer and manufacturer of these vehicles. Thus, in considering whether GM could be considered a manufacturer of Lotus passenger cars, we looked to GM's overall involvement with those vehicles and not merely to the fact that it owned the producer and importer of those vehicles. In now considering the Alliance's request for interpretation, we believe several factors are relevant. First, we believe that the application of the manufacturer attribution provisions applicable to phase-in requirements needs to be clear, without the necessity of addressing each specific situation by interpretation. Second, we believe that, as a practical matter, there is typically sufficient interaction among related manufacturers, and direct involvement by a "parent manufacturer" in the actions of its subsidiaries, that their fleets can reasonably be considered as a single fleet for purposes of complying with phase-in requirements. Third, from a public policy perspective, there is little (if any) difference in the number of compliant vehicles introduced into the fleet during the phase-in years between the case in which commonly owned manufacturers are permitted to combine their fleets and the case in which commonly owned manufacturers are permitted to separate their fleets for compliance purposes. Fourth, as a general matter, NHTSA does not have any interest under the Safety Act as to how companies choose to structure themselves, so long as Safety Act obligations are fully met. Thus, in a situation in which one manufacturer corporation buys another, NHTSA does not generally have any interest in whether the corporation that has been purchased becomes a division of the other manufacturer or is maintained as a subsidiary. Given the above considerations, we have concluded that vehicle manufacturers may combine the fleets of motor vehicle manufacturing subsidiaries they own for purposes of determining overall fleet compliance with the compliance percentages set forth in the various safety standard phase-in requirements, subject to the agreement of those other manufacturers. Moreover, recognizing the different levels of ownership that exist in the industry and wishing to avoid further requests for interpretation in this area, we take the following further position: For purposes of complying with phase-in requirements under Federal motor vehicle safety standards, vehicle manufacturers may combine, with their fleet, the fleets of motor vehicle manufacturers that are considered to be within the same "control" relationship for purposes of the CAFE standards (and which are in fact included in the same fleets under the CAFE statute), subject to the agreement of the other manufacturers. To the extent that the fleets of more than one manufacturer are so combined, we would consider each manufacturer jointly and severally liable for any failure to meet a relevant percentage phase-in requirement. Since this interpretation is based on specific factual determinations and policy concerns related to phase-ins of new safety requirements, it should not be considered as precedent for how we would interpret the term "manufacturer" in other contexts. I also note that this interpretation does not overturn the one we sent to Mr. Nakayama. In that interpretation, we addressed the status of certain small volume manufacturers in the context of ownership relationships with other manufacturers. Our conclusion that the small volume manufacturers at issue qualified for the special small volume implementation schedule reflected a number of considerations, including the operational independence of the companies. Sincerely, Jacqueline Glassman ref: 208 |
2002 |
ID: alliance.march20OpenRobert Strassburger, Vice President Dear Mr. Strassburger: This is in response to your letter of March 18, 2003, in which you asked questions regarding our interpretation of certain provisions of the early warning reporting rules promulgated by the National Highway Traffic Safety Administration, Subpart C of 49 CFR Part 579. You requested prompt turn around in view of the fact that the first reporting period will soon begin. This letter provides that response. I will first paraphrase your inquiries and then provide a brief statement of our interpretation. 1. Reporting Information on the Face of a Claim/Complaint. The Alliance inquired as to whether manufacturers must report complaints/claims based on the information contained on the face of the complaint or claim, rather than reporting on the basis of the manufacturers review or analysis of the complaint/claim. The answer is yes. Reporting is to be based on the information in the complaint or claim, rather than on the manufacturers assessment. Even if the manufacturer disagrees with the assertions of the consumer/claimant after conducting its analysis, the manufacturer must still report the complaint or claim. Each of the five examples given in your letter would be reportable as a "consumer complaint" under the early warning reporting rules. 2. Marketing Survey Information. The Alliance sought NHTSAs concurrence that marketing information purchased from third-party vendors (such as J.D. Power) or supplied by third parties (such as Consumer Reports magazine), which might contain information reflecting a consumers dissatisfaction with a product, is not reportable in the early warning program as a "consumer complaint," or otherwise, even if the information contains "minimum specificity" about the make, model, and model year of a vehicle. You also asked about complaints that are included in "marketing information" solicited by a manufacturer directly from the purchasers of its products. We concur with respect to third-party submissions, since they are not "addressed to the company . . . ." and therefore do not fall within the regulatory definition of "consumer complaint" in Section 579.4(c). However, if a manufacturer collects the information directly from its consumers, by itself or through a contractor, it would have to report any "complaints" included in that information, regardless of whether the primary purpose of the activity is marketing. As you note in your letter, consumers responding to such manufacturer surveys are "likely aware that they are communicating with the manufacturer." The fact that the comments are solicited by the manufacturer is not determinative, particularly since many consumers who make a complaint about a vehicle in this context will justifiably believe that they need not repeat that complaint to a different office within the company. 3.Dealer Repair Work Orders. The Alliance sought the agencys views on whether dealer repair work orders, if received in writing by a vehicle manufacturer, are reportable as " dealer field reports." These work orders are the dealers internal records of service performed at dealerships. As described in your letter, these work orders are not requested by, or provided to, manufacturers in the ordinary course of business, but might be submitted in the context of "lemon law" proceedings, product liability litigation, or similar proceedings, often many years after the service in question was performed. As such, we would not consider them to be "field reports" under the rule, and they would not have to be reported under that category. However, if the work had been performed under warranty, it would have to be reported as a warranty claim. 4.Vehicle Inspections Conducted to Determine Eligibility for Insurance and/or Extended Warranty Coverage. Finally, the Alliance asked whether written reports of vehicle inspections conducted solely to determine eligibility for insurance and/or extended warranty coverage are reportable as "field reports." As described in your letter, these reports are not prepared in response to an assertion that a specific problem exists in a particular vehicle, which is the normal genesis of field reports. Thus, although it is possible that an inspection report might identify a problem in a vehicle, it would not be a "communication . . . regarding the failure, malfunction, lack of durability, or other performance problem . . . ." As such, these inspection reports would not have to be reported to us as field reports. If you have any questions, pleas call Taylor Vinson or Lloyd Guerci of this office at (202) 366-5263. Sincerely, Jacqueline Glassman ref:579 |
1970 |
ID: alliance.ztvOpenMr. Robert S. Strassburger Dear Mr. Strassburger: This is in reply to your letter of January 13, 2003, asking two questions with respect to the final rules set forth in 49 CFR Part 579. Your first question cited a portion of the early warning reporting final rule, Section 579.21(b), which applies to "all light vehicles less than ten calendar years old at the beginning of the reporting period." Under subsection (b)(1), a manufacturer must report "each incident involving one or more deaths occurring in a foreign country . . . involving a manufacturers vehicle, if that vehicle is identical or substantially similar to a vehicle that the manufacturer has offered for sale in the United States." You asked that we concur in your understanding that the ten-year old limitation "applies both to the age of the vehicle in which the fatality occurred in a foreign country and to the offering for sale of a substantially similar vehicle in the United States." You presented a situation in which a fatality occurs in a vehicle that is substantially similar to a vehicle previously offered for sale in the United States but whose sale was discontinued more than ten years before the beginning of the reporting period. In this event, the Alliance understands that the "ten calendar year" limitation applies and that a manufacturer would not have to report the incident. You are correct that the purpose of the regulation is to identify potential defects in vehicles in the United States. Although safety defects can and have existed in vehicles older than ten calendar years, the early warning reporting requirements are intended to be consistent with the amendment to 49 U.S.C. 30120(g) under which the period for remedy of defective and noncompliant motor vehicles without charge was increased from eight to ten years. Therefore, we confirm your understanding that a claim involving a fatality or injury occurring in a foreign vehicle need not be reported if no sales of a substantially similar vehicle have occurred in the United States for more than ten years before the beginning of the reporting period. On the other hand, in a situation in which a fatality or injury occurs in a foreign vehicle that is more than ten years old and a substantially similar U.S. vehicle has been sold within a ten-year period before the reporting period, a related claim must be reported to us. This interpretation applies not only in the context of Section 579.21(b), but also with respect to the ten-calendar-year language of Sections 579.22(b), 579.23(b), and 579.24(b), and the five-calendar-year provisions of Section 579.25(b) and 579.26. Your second question arises in the context of the foreign defect reporting final rule. Section 579.11(d)(2) (as originally adopted) provided that a manufacturer need not report a foreign safety recall or other campaign to NHTSA if "the component or system that gave rise to the foreign recall does not perform the same function in any vehicles or equipment sold or offered for sale in the United States." It is your understanding that "no report would be required when a foreign campaign is conducted on a vehicle that is substantially similar to one offered for sale in the United States, but the component or system that gave rise to the foreign recall is not installed on the U.S. vehicles." In response to the Alliances petition for reconsideration of the foreign defect reporting final rule, we amended Section 579.11(d)(2) to state that a manufacturer need not report if "the component or system that gave rise to the foreign recall or other campaign does not perform the same function in any substantially similar vehicles or equipment sold or offered for sale in the United States." 68 FR 4111, January 28, 2003. Since we have clarified that we do not require reporting if a component or system is present on a substantially similar U.S. vehicle but does not perform the same function as on a foreign vehicle, we believe that it is also clear that a manufacturer need not report to us if the system or component leading to the foreign recall or other campaign is not installed at all on the substantially similar U.S. vehicle. If you have any questions, you may call Taylor Vinson of this Office (202-366-5263). Sincerely, Jacqueline Glassman ref:579 |
2003 |
ID: alliancerecords.ztvOpenMr. Robert Strassburger Dear Mr. Strassburger: This is in reply to your letter of August 13, 2003, asking for an interpretation of the early warning reporting (EWR) rule, 49 CFR Part 579, Subpart C, with respect to the updating of certain information under Section 579.28(f). You pointed out that under a NHTSA recordkeeping regulation, 49 CFR 576.5(b), manufacturers must retain, for five years, all the "underlying records" that form the basis for EWR information submitted under Part 579. You asked us to confirm your understanding that "manufacturers must update previously submitted information on fatalities or injuries pursuant to Section 579.28(f) for a period of five years from the quarter in which the fatality or injury was initially submitted to NHTSA." You argued that, in view of the need (explained at a public meeting held on June 19, 2003) to submit updates as part of a resubmission of the entire Excel workbook containing fatality and injury information, "reporting updates beyond that time is inconsistent with the recordkeeping requirement." We confirm your understanding, and note that it is extremely unlikely that a manufacturer would have to update any such reports at such a late date. If you have any questions, you may call Taylor Vinson or Andrew DiMarsico of this Office (202-366-5263). Sincerely, Jacqueline Glassman ref:576#579 |
2003 |
Request an Interpretation
You may email your request to Interpretations.NHTSA@dot.gov or send your request in hard copy to:
The Chief Counsel
National Highway Traffic Safety Administration, W41-326
U.S. Department of Transportation
1200 New Jersey Avenue SE
Washington, DC 20590
If you want to talk to someone at NHTSA about what a request for interpretation should include, call the Office of the Chief Counsel at 202-366-2992.
Please note that NHTSA’s response will be made available in this online database, and that the incoming interpretation request may also be made publicly available.