Maryland's Thirty Out-of-Service Days Arguably Become Thirty-Seven After a Seven-Day Repair Shutdown

Maryland’s new motor vehicle warranty statute spends the number thirty twice in the same section. In one sentence thirty is a deadline the manufacturer has to meet, counted forward from a single fixed date. In the other, thirty is a running tally the vehicle has to accumulate across the warranty period. On a service file summary the two look identical. They behave nothing alike.

A third sentence in the same section extends some of the statute’s clocks when a war, a strike, a fire or a flood closes the repair bays. It names three things it extends. One of the two thirties is on that list; the other is not. And for the thirty that is on it, the word extended carries two readings running in opposite directions: either the threshold climbs from 30 days to 37 after a seven day closure, or it stays at 30 and only the window in which those days may accumulate grows by 7. One reading makes the presumption harder to reach, the other easier.

Two thirties, two jobs

The first thirty lives in the repair duty. Maryland General Assembly, Commercial Law § 14-1502 provides at subsection (b)(3): “The manufacturer or factory branch, its agent, or its authorized dealer shall correct the nonconformity, defect, or condition at no charge to the consumer, even if repairs are made after the expiration of the warranty period. The corrections shall be completed within 30 days of the manufacturer’s receipt of the consumer’s notification of the nonconformity, defect, or condition.”

Three things follow. The clock starts at receipt, not at mailing, which matters because (b)(1) requires the consumer to report the problem “by giving written notice to the manufacturer or factory branch by certified mail, return receipt requested” — the return receipt fixes the start date. It runs as ordinary calendar time, whether or not the vehicle is in a bay. And the duty survives expiry, because corrections are owed “even if repairs are made after the expiration of the warranty period”.

The second thirty lives in the presumption. Subsection (d)(2) reads: “The vehicle is out of service by reason of repair of 1 or more nonconformities, defects, or conditions for a cumulative total of 30 or more days during the warranty period; or”

This one is a sum, not a stretch. It gathers days from separate visits and accepts days attributable to different problems — “1 or more nonconformities” — which distinguishes it from the repair count branch. It is also bounded: the days have to fall “during the warranty period”, and Maryland General Assembly, Commercial Law § 14-1501 defines the subtitle’s one period term, “Manufacturer’s warranty period”, as “the earlier of: (i) The period of the motor vehicle’s first 18,000 miles of operation; or (ii) 24 months following the date of original delivery of the motor vehicle to the consumer”.

What the record has to show

Because the two thirties start from different events, a service file has to carry two kinds of proof, and most files carry only one well.

For the (b)(3) thirty, the load-bearing document is the certified mail return receipt with a legible delivery date. The repair orders matter only to show what happened in the 30 days that followed. A file with eight repair orders and no return receipt has no start date for this clock.

For the (d)(2) thirty, the load-bearing documents are the repair orders, and specifically two fields service writers often leave soft: the date the vehicle was taken in and the date it was released. A tally built from invoice dates understates out of service time whenever a car sat over a weekend waiting on a part. The statute says “out of service by reason of repair”, which tracks availability rather than labour hours billed. If a closure will be argued about, the record needs the closure dates too, because subsection (e) speaks of repair services being unavailable rather than the vehicle being undriveable.

Three branches, and the one that carries three elements

Subsection (d) opens with “It shall be presumed that a reasonable number of attempts have been undertaken to conform a motor vehicle to the applicable warranties if” and then runs three branches. Branch (d)(1) requires that the same problem “has been subject to repair 4 or more times by the manufacturer or factory branch, or its agents or authorized dealers, within the warranty period but such nonconformity, defect, or condition continues to exist” — the closing clause is the one that gets dropped, since four visits are not enough on their own. Four Repair Attempts Create a Presumption looked at how a fourth visit is counted elsewhere.

The third branch is routinely summarised into something shorter than it is: “A nonconformity, defect, or condition resulting in failure of the braking or steering system has been subject to the same repair at least once within the warranty period, and the manufacturer has been notified and given the opportunity to cure the defect, and the repair does not bring the vehicle into compliance with the motor vehicle safety inspection laws of the State.”

Read the conjunctions. Three requirements are joined by and: one repair of the same braking or steering problem inside the warranty period; a separate notice to the manufacturer plus an opportunity to cure; and a vehicle that still fails State safety inspection law afterwards. The middle element is a second step, not a restatement of the first — a repair visit at a dealership satisfies element one without touching element two, because (b)(1) routes notice to the manufacturer by certified mail rather than to the shop that did the work.

What extended does to a threshold

Here is the sentence the whole question turns on. Subsection (e): “The term of any warranty, the warranty period, and the 30 day out of service period shall be extended by any time during which repair services are not available to the consumer by reason of war, invasion, strike, or fire, flood, or other natural disaster.”

Take a concrete case. A flood closes every authorised dealer within range for 7 days. By the end of the warranty period the vehicle has been out of service for 30 cumulative days, 7 of which fall inside the closure. Has the presumption been triggered?

Reading B says yes: extending “the 30 day out of service period” means lengthening the stretch of time in which the 30 days may be collected. The threshold stays at 30, the consumer has 30, done. Reading A says no: the 30 day period is the measure itself, and extending it by 7 days means the tally has to reach 37 before the presumption fires.

The structure favours Reading A, for a reason easy to miss: subsection (e) already extends “the warranty period” in the same list, and branch (d)(2) counts its days “during the warranty period”. The window is lengthened by the second item before the third is reached. If the third also meant the window, it would be doing work the second has done. Reading it as the threshold gives it something of its own to do, and it fits the sentence’s purpose of stopping clocks against a manufacturer during a war, a strike or a flood.

Notice the direction that implies. The same verb, in the same list, moves two items in the consumer’s favour and the third against: a longer warranty term and period widen the consumer’s rights, a longer out of service threshold narrows them. Nothing flags the switch. Which Thirty Does Minnesota’s Tolling Clause Extend set out the same shape of problem from another angle.

Reading A has a built-in limit. If the 7 closure days are themselves out of service days — the car sitting at a shuttered dealership — raising the bar to 37 cancels them out, which is the sensible result. If they are days the consumer drove the car normally, the bar still rises to 37 and the consumer is worse off for a flood that cost the vehicle nothing. The sentence treats those situations alike, and that is the gap a Maryland record should be built to argue about.

The twenty day duty stays where it is

There is a fourth number in the same section, and it is the one that creates the paper trail. Subsection (f)(1)(i): “It shall be the duty of a dealer to notify the manufacturer of the existence of a nonconformity, defect, or condition within 7 days when the motor vehicle is delivered to the same dealer for a fourth time for repair of the same nonconformity or when the vehicle is out of service by reason of repair of one or more nonconformities, defects, or conditions for a cumulative total of 20 days.”

Two triggers, both lower than the consumer’s, and the notice goes by certified mail with “a copy of the notification shall be sent to the Motor Vehicle Administration”. A well-run file therefore holds a dated, third-party-copied record that the count reached 20 before anybody argued about 30. The 20 is not on the subsection (e) list. Neither is the (b)(3) thirty, nor the 15 days a manufacturer has under (f)(2) to report a returned vehicle to the Motor Vehicle Administration. Under Reading A, a 7 day closure widens the gap between the dealer’s filing trigger and the consumer’s threshold from 10 days to 17. One more clause in (f) closes a door that looks open — “failure of the dealer to give the required notice required under this subsection shall not affect the consumer’s right under this subtitle” — so a skipped filing costs evidence rather than the branch.

Where the consumer page and the codified text part company

Maryland publishes a consumer-facing summary, and on the third branch it is shorter than the statute in a way that changes the element count. The Office of the Attorney General of Maryland, Lemon Law page states it as “A brake or steering failure that was not corrected after the first repair attempt, and that causes the vehicle to fail Maryland’s safety inspection”. That is two conditions; the codified branch carries three. The one left out is the separate notice to the manufacturer and the opportunity to cure, so a reader who builds a file against the summary can arrive with one repair order and a failed inspection sheet and still be short an element.

Two smaller divergences sit alongside it. The page describes coverage as “new or leased cars, light trucks, and motorcycles registered in Maryland that are less than 24 months old and have fewer than 18,000 miles”, while the definition is keyed to delivery rather than age: “24 months following the date of original delivery of the motor vehicle to the consumer”. For a demonstrator, or a unit that sat on a lot for five months, those phrasings end on different dates. And the page states the correction period as “The law provides that a dealer or manufacturer must correct a defect within 30 days after the consumer writes to the manufacturer by certified mail.”, while (b)(3) measures from “the manufacturer’s receipt”. Both documents are Maryland’s own; date the file from the return receipt and plead the third element whatever the summary lists, because the codified text is the one a court reads. When Florida Counts 30 Days Out of Service covered a comparable mismatch.

The federal mechanism runs on its own clock

If the dispute goes to a manufacturer-sponsored informal dispute settlement mechanism, a separate deadline appears and Maryland’s subsection (e) has no purchase on it. Federal Trade Commission, 16 CFR 703.5 provides that where a dispute remains unsettled, “the Mechanism shall, as expeditiously as possible but at least within 40 days of notification of the dispute, except as provided in paragraph (e) of this section” render a decision and disclose it. That 40 day limit carries its own exception paragraph inside the federal rule, which is where any extension has to come from. The same rule, at 16 CFR 703.5(c), directs the mechanism to investigate “issues relating to the number of repair attempts, the length of repair periods” and other relevant issues — the measures branches (d)(1) and (d)(2) turn on.

Numbers to Re-check

Five entries carry the analysis, and each should be re-read in the codified text rather than in any summary, this one included. First, the 30 in (b)(3), with attention to “of the manufacturer’s receipt”. Second, the 30 in (d)(2), with attention to “cumulative total” and to “during the warranty period”. Third, the warranty period in § 14-1501 — the earlier of 18,000 miles or 24 months from original delivery, so whichever arrives first ends it. Fourth, the 4 in (d)(1), together with the requirement that the condition “continues to exist”. Fifth, the 20 and the 7 in (f)(1)(i), which are a dealer’s duty rather than a consumer’s threshold.

Then re-read subsection (e) and count its items: the term of any warranty, the warranty period, the 30 day out of service period. Three. Confirm that the (b)(3) thirty, the 20, and the 15 in (f)(2) are absent from that list, because the Reading A conclusion — 30 becoming 37 after a 7 day closure — rests on the list having exactly those three members and on the second and third meaning different things. If a refund is being modelled, check the 15 percent cap too: (c)(1)(ii) limits the use deduction to “A reasonable allowance for the consumer’s use of the vehicle not to exceed 15 percent of the purchase price; and” a separate damage allowance — a ceiling, not a formula.

Where this framework does not apply

The reading above is an argument from the structure of one sentence, not a holding. A Maryland court could read “the 30 day out of service period” as the window rather than the threshold and treat the overlap with the warranty period as ordinary belt-and-braces drafting. If that happens, Reading B controls and 30 stays 30.

The section leaves out several common situations. The definition in § 14-1501 excludes motor homes, so a coach owner is outside this subtitle even with 30 days in a bay, and the subtitle is keyed to vehicles registered in Maryland in the listed classes. A used vehicle bought after the 18,000 mile or 24 month period has closed is outside the presumption whatever the repair count. The affirmative defences in (c)(3) sit on top: a manufacturer may answer that the condition “Does not substantially impair the use and market value of the motor vehicle; or” that it is “the result of abuse, neglect, or unauthorized modifications or alterations of the motor vehicle”, and either can defeat a claim that cleared the day count cleanly. Subsection (e) is also drafted around a short list of causes — war, invasion, strike, fire, flood, or other natural disaster — so a parts shortage, a withheld software release, or a business-reasons closure are not obviously on it.

What would invalidate this: a reported Maryland decision construing “the 30 day out of service period” in subsection (e), a later amendment adding the (b)(3) correction period or the (f)(1)(i) 20 day duty to the (e) list, or a Motor Vehicle Administration interpretation of how closure days are treated in the tally. None of that was located within the research budget here, and the enrolled-act history of subsection (e) was not traced — only the codified text was read. Treat the 37 as the better reading of the text on the page, not as settled Maryland law.