Cal. Civ. Code § 16-41-27-29
Liens
Operative Text
Sec. 29. (a) Subject to subsection (b), the owner, operator, or caretaker of a mobile home community has a lien upon the property of a guest in the same manner, for the same purposes, and subject to the same restrictions as an innkeeper's lien or a hotel keeper's lien. (b) With regard to a lienholder: (1) if the property has a properly perfected secured interest; and (2) the lienholder has notified the owner, operator, or caretaker of the mobile home community of the lienholder's lien by certified mail; the maximum amount of the innkeeper's lien may not exceed the actual late rent owed for not more than a maximum of sixty (60) days immediately preceding notification by certified mail to the lienholder that the owner of the property has vacated the property or is delinquent in the owner's rent. (c) If the notification to the lienholder under subsection (b) informs the lienholder that the lienholder will be responsible to the owner, operator, or caretaker of the mobile home community for payment of rent from the time the notice is received until the mobile home, manufactured home, or industrialized residential structure is removed from the mobile home community, the lienholder is liable for the payment of rent that accrues after the notification.
Indiana Code § 16-41-27-29 grants the owner, operator, or caretaker of a mobile home community a lien against a guest's property, modeled on the traditional innkeeper's lien. When a third-party lienholder holds a perfected secured interest in that property and has given certified-mail notice of that interest, the community operator's lien is capped at actual late rent for no more than the 60 days immediately before the operator notified the lienholder of the vacancy or delinquency. Additionally, if the operator's notice to the lienholder states that the lienholder will be responsible for ongoing rent until the home is removed, the lienholder becomes liable for rent accruing from the moment that notice is received.
Plain English — not legal advice.
Under Ind. Code § 16-41-27-29, mobile home community operators generally maintain records of any third-party lienholders who have sent certified-mail notice of a perfected secured interest in a resident's property, because that notice triggers the 60-day cap on the lien amount. When a resident vacates or falls delinquent, compliant operators send timely certified-mail notification to any such lienholder, and that notice may include a statement making the lienholder responsible for rent accruing until the home is removed from the community. Keeping thorough documentation of all certified-mail correspondence and dates is a standard practice for operators seeking to preserve their lien rights under this section.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
Ind. Code § 16-41-27-29 establishes that a mobile home community operator can assert a lien against a resident's property for unpaid rent, but the scope of that lien can be limited when a third-party lienholder—such as a lender financing the home—has properly notified the operator of its interest. Residents who are aware of a lender or other lienholder on their home may want to understand how that lienholder's certified-mail notice to the operator affects the amount of rent that can be claimed under the lien. Tenants with questions about how this lien provision applies to their circumstances can reach out to a local tenant-rights organization or legal aid office for general information.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated October 14, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
No outbound references recorded yet for this provision.
References In
Rules and statutes that cite this regulation
Related Rules
Source Information
Use this in your app
Access this data programmatically via our API