DOMAGALA v. Rolland

787 N.W.2d 662, 2010 Minn. App. LEXIS 138, 2010 WL 3396838
CourtCourt of Appeals of Minnesota
DecidedAugust 31, 2010
DocketA09-1945
StatusPublished
Cited by4 cases

This text of 787 N.W.2d 662 (DOMAGALA v. Rolland) is published on Counsel Stack Legal Research, covering Court of Appeals of Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
DOMAGALA v. Rolland, 787 N.W.2d 662, 2010 Minn. App. LEXIS 138, 2010 WL 3396838 (Mich. Ct. App. 2010).

Opinion

OPINION

CONNOLLY, Judge.

On appeal from the district court’s denial of a motion for a new trial, appellant argues that the district court erred when it (1) concluded there was no duty to warn appellant as a matter of law, and (2) improperly used “negative” jury instructions, which unduly emphasized respondents’ case and confused the jury. Because the district court correctly concluded there was no special relationship giving rise to a duty to warn, we affirm in part. But because the district court abused its discretion by giving the negative instructions, which confounded the standard of care owed to appellant, overemphasized respondent’s case and confused the jury, we reverse in part and remand for a new trial.

FACTS

Respondent Eric Rolland owns respondent Rolland Building Corporation, a Wisconsin construction company that designs and builds residential and commercial properties and performs remodeling services. Rolland and his corporation are collectively referred to herein as “respondent.” Appellant Bradley Domagala is married to respondent’s cousin. Appellant and his wife asked respondent to perform some grading work around their home. Their yard had a “rough grade” and respondent was “going to do a finished grade, which means preparing for sod or seed.” The project was expected to take approximately six hours.

On June 23, 2003, respondent brought his New Holland LX985 skid loader over to appellant’s home to work on the yard. Respondent also brought the corresponding forks; the leveling, or sod, bar; and the bucket attachments. Throughout the course of the project, respondent operated the skid loader while appellant watched and picked up rocks and debris from the yard. Respondent did not ask appellant to help him in any way. The machine was noisy and respondent wore ear protection. When appellant wanted to speak with respondent, he would approach the skid loader with his hands up, palms out, and respondent would then put his hands up in the air, indicating that his hands were away from the controls.

The skid loader’s attachments needed to be switched out on several occasions during the project. In order to change an attachment, respondent would first take off his seatbelt, go out through the front, walk over the bucket, and face the skid loader. Respondent would then pull up on the levers one at a time and the attach *666 ment would be released. Next, respondent would go back into the skid loader, put back on his seatbelt, back up, and then pull up to the desired attachment. Finally, respondent would hook up the hydraulics and saddles; check to make sure everything was set right; and again get out of the skid loader, face the machine, pull the levers down, and latch them in. After-wards, respondent would get back in the skid loader, lift the boom slightly, and check to make sure the pins were through the receivers.

It was common for dirt and other debris, such as rocks, to get lodged in the levers. When this occurred, respondent would detach the handle or pin that would release; raise the attachment a couple of inches off the ground; and “flutter the hydraulics to shake” the attachment. This would “create! ] extra play,” loosening whatever was stuck in the other lever. Approximately three-quarters of the way through the project, roughly two hours in, respondent needed to remove the skid loader’s bucket and attach the leveling bar. A piece of debris was stuck in one of the levers. Respondent released one of the levers and began “fluttering the bucket vertically.” Respondent described this as a very dangerous situation because the skid loader’s bucket was in the air, hanging by a single pin.

Respondent then became aware that appellant was coming straight at him. Appellant could see that there was a stone stuck in one of the levers. Respondent took his hands off the controls and raised them up. The bucket was approximately 10-20 inches off of the ground. Before respondent could say anything to appellant, appellant reached up and grabbed the lever, releasing the bucket. Appellant did not recall giving “any indication that [he] was going to release the lever.” The cutting edge of the bucket was pointed towards the ground, and landed directly on appellant’s left foot. As a result, three of appellant’s toes were crushed and eventually amputated.

Appellant sued respondent, alleging that respondent negligently and carelessly operated the skid loader and failed to warn him of the dangers associated with trying to unlatch the skid loader’s bucket. Respondent moved for summary judgment, asserting that there was no special relationship between the parties giving rise to a duty to protect or a duty to warn. The district court denied the motion for summary judgment, concluding that respondent “owed a duty of care to act in a reasonable manner” when operating the skid loader and that respondent “created a dangerous situation when [respondent] elevated the bucket attachment while it was attached to the machinery by only one lever; thus, creating a duty of care owed to [appellant].” However, the district court concluded as a matter of law that no special relationship existed between the parties giving rise to a duty to protect or a duty to warn. The case proceeded to a jury trial.

Among other instructions, respondent requested two special jury instructions in light of the district court’s summary-judgment order. The first stated that respondent had no duty to protect appellant:

A person generally has no duty to act for the protection of another person. A legal duty to protect will be found to exist only if there is a special relationship between the parties and the risk is foreseeable. The Court has ruled, as a matter of law, that no duty to protect exists in this matter and you must not consider such a duty in your deliberation in this case.

The second stated that respondent had no duty to warn appellant.

*667 A special relationship giving rise to a duty to warn is only found on the part of common carriers, innkeepers, possessors of land who hold it open to the public, and persons who have custody of another person under circumstances in which that other person is deprived of normal opportunities of self-protection. The Court has ruled, as a matter of law, that no duty to warn exists in this matter and you must not consider such a duty in your deliberation in this case.

Appellant objected to the proposed instructions, asserting that while

[i]t is undisputed that there is no special relationship between the parties that would require a heightened Duty to Protect or a heightened Duty to Warn[,] ... [i]t is feasible that the jury might find that the duty of reasonable care included a warning in order to protect [appellant] from the dangerous situation created by [respondent].

Appellant also argued that these instructions may be confusing to the jury and, because the district court already found that such duties did not exist, these instructions should not be part of the charge to the jury. The district court stated it would give both of the requested instructions, but also acknowledged that appellant was not foreclosed from arguing that a reasonable person would have warned appellant.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Ouradnik v. Ouradnik
897 N.W.2d 300 (Court of Appeals of Minnesota, 2017)
Mark Lanterman v. Michael Roman Afremov
Court of Appeals of Minnesota, 2016
Domagala v. Rolland
805 N.W.2d 14 (Supreme Court of Minnesota, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
787 N.W.2d 662, 2010 Minn. App. LEXIS 138, 2010 WL 3396838, Counsel Stack Legal Research, https://law.counselstack.com/opinion/domagala-v-rolland-minnctapp-2010.