Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the easy-footnotes domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-document-embedder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-tables-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the spam-free-wordpress domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themelia domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6121

Deprecated: The called constructor method for WP_Widget class in wpcs_search_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 6121

Deprecated: The called constructor method for WP_Widget class in wpcs_most_view_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 6121
Lack of Inspection Evidence Properly Results in Denial of Summary Judgment for Defendants in Personal Injury Slip-and-Fall Case – Pospis Law, PLLC
Warning: Trying to access array offset on value of type null in /var/www/wp-content/themes/themelia/inc/themelia.php on line 274

Lack of Inspection Evidence Properly Results in Denial of Summary Judgment for Defendants in Personal Injury Slip-and-Fall Case

A recent Second Department decision, Bergin v. Golshani, is instructive on the issue of when summary judgment is properly awarded to a defendant in a slip-and-fall case.

Here is the law:

A defendant landowner moving for summary judgment in a slip-and-fall case has the initial burden of establishing that it did not create the alleged defect or have actual or constructive notice thereof. To constitute constructive notice, a defect must be visible and apparent and it must exist for a sufficient length of time prior to the accident to permit [the defendants] to discover and remedy it. When a defect is latent and would not be discoverable upon a reasonable inspection, constructive notice may not be imputed. In demonstrating that it lacked constructive notice of a visible and apparent defect, the defendant must offer some evidence as to when the area in question was last cleaned or inspected relative to the time when the plaintiff slipped and fell.

The court then explained why defendants were not entitled to summary judgment:

Here, the deposition testimony of the defendant Afshin Golshani established, prima facie, that the defendants did not create or have actual notice of the allegedly loose piece of slate on the slate stone landing which allegedly caused the plaintiff Patrick Bergin to fall. However, in the absence of any evidence as to when the defendants last inspected the landing before the accident, or that the allegedly loose piece of slate on the landing was a latent defect that could not have been discovered upon a reasonable inspection, the defendants failed to establish, prima facie, that they lacked constructive notice of the allegedly loose piece of slate on the landing.

Share This: