If you or a family member was caught in a crowd surge at a concert or festival in Las Vegas, or if you lost someone in a crush incident, you’ve probably already encountered the framing that makes recovery feel impossible: “It was the crowd. The crowd is just an unfortunate dynamic. Nobody can really be held responsible for what a crowd does.” If your injury at a festival or concert was something other than a crush, such as a fall, a heat illness, or rough handling by security, the general guide to suing after an injury at a music festival or large event covers those claims.
That framing is wrong, but defeating it requires understanding which entities controlled which decisions, and how Nevada law allocates responsibility across them.
What You Need to Know Before You Decide What to Do
If you were injured or lost a loved one in a crowd surge or crush at a Las Vegas concert or event:
- Crowd surge is compression asphyxia, not trampling. The actual injury mechanism is sustained chest compression preventing breathing, established across Hillsborough (1989), the 1991 NYC basketball game, and Astroworld (2021). The distinction matters because compression asphyxia is preventable through documented crowd-density management standards.
- Multiple parties control different parts of the picture. A modern concert involves a venue owner, event promoter, performer, security contractor, event organizer, and sometimes a barrier subcontractor or ticketing sponsor, each controlling distinct decisions that contribute to or prevent surge conditions.
- Nevada law provides multiple paths for recovery. The premises-liability duty of reasonable care, foreseeability for third-party crowd acts as in Humphries v. New York-New York, the non-delegable duty to provide responsible security personnel where a venue outsources security, and the multi-defendant structure that allows naming all responsible parties.
- Assumption of risk is the defense to expect. After Turner v. Mandalay Sports Entertainment the court, not the jury, decides whether a risk is one the venue owed no duty about, so the work is showing that what happened went beyond the risks a patron accepts at a show.
- Astroworld is the industry inflection point that triggered serious attention to crowd-density management. It is not legal precedent; the cases settled with no admissions of liability and no published appellate ruling.
This article is structured as a decision tool. If you’d like to talk through your specific situation, call Jack Bernstein Injury Lawyers at (702) 633-3333 for a free consultation. Otherwise, here’s the working framework.
The Multi-Defendant Allocation Framework
Most consumer content collapses concert-injury responsibility into “the venue.” Senior plaintiff event-injury practice does not. A modern concert is the product of distinct operational decisions made by separate entities, each owing duties to ticket-holders.
The defendants who routinely appear in crowd-surge cases:
| Defendant | Operational Sphere | Duty Source | Typical Defenses |
|---|---|---|---|
| Venue owner / operator | Premises condition; capacity decisions; permanent infrastructure | Premises liability; duty of reasonable care to entrants under NV common law (Foster v. Costco, 128 Nev. 773, 291 P.3d 150 (2012)); non-delegable duty for security personnel (Rockwell) | Open-and-obvious; voluntary entry; security was outsourced |
| Event promoter | Operational planning; production decisions; contractual control over venue safety measures | Negligence in event planning; contractual duty to attendees | Local subcontractors handled crowd management; “unforeseeable” attendance surge |
| Performer | Audience interaction; decisions to continue or halt the show | Negligence where performer actively encourages dangerous behavior or continues in face of warnings | First Amendment expressive activity; lack of contemporaneous knowledge |
| Security contractor | Crowd management at point of contact; response to developing surge conditions | Negligence in providing reasonably qualified, adequately staffed security | Contract scope was limited; venue retained ultimate control |
| Event organizer | Pre-event safety planning; capacity calculations; emergency protocols | Negligence in safety planning | Industry-standard practices were followed; deferred to venue |
| Barrier subcontractor / ticketing or livestream sponsor | Equipment installation; in some cases co-promotion of the event | Negligence in equipment / co-sponsor operational role | No operational control; no foreseeability |
Each entity has its own contracts, insurance coverage, and tort exposure. The Astroworld multidistrict litigation in Texas (naming Travis Scott, Live Nation Entertainment, Scoremore Holdings, ASM Global as venue operator, Contemporary Services Corporation as security contractor, Apple Music as livestream sponsor, and Drake as guest performer) illustrates the typical structure.
Two operational consequences: First, plaintiffs who name only the venue leave significant recovery on the table; each defendant carries its own insurance limits. Second, defendants typically cross-claim against each other to allocate fault, meaning the case becomes an internal allocation fight as well as a plaintiff-defendant fight, which plaintiff counsel uses to develop evidence.
The Nevada Legal Substrate
Three Nevada doctrines govern crowd-surge cases involving multi-defendant venue events.
Premises liability and the duty of care. Under Foster v. Costco Wholesale Corp., 291 P.3d 150 (Nev. 2012), a landowner owes a duty of reasonable care to entrants for risks that exist on the property, so a venue owes ticket-holding concert attendees that same reasonable care. The duty is an active one: in Twardowski v. Westward Ho Motels, 86 Nev. 784, 476 P.2d 946 (1970), the court held an owner must inspect the premises to discover dangerous conditions it does not know about and must warn of hidden or concealed perils it knows or should know of. The elements of the negligence claim are duty, breach, legal causation and damages (Hammerstein v. Jean Development West, 111 Nev. 1471, 907 P.2d 975 (1995)). Hammerstein rejected the argument that a hotel owes its guests more than reasonable care, so what a venue owes is reasonable care measured against the circumstances it created, not a heightened duty.
Foreseeability for third-party acts. Humphries v. New York-New York Hotel & Casino, 133 Nev. Advance Opinion 77 (2017), interpreting NRS 651.015, rejected the narrower reading that would have required notice of the specific impending act, and it compared prior incidents by location, level of violence and the security concerns they raised. Under the statute a wrongful act is not foreseeable unless the owner failed to exercise due care, or prior incidents of similar wrongful acts occurred on the premises and the owner had notice or knowledge of them. Humphries read the due-care route in NRS 651.015(3)(a) as calling for a totality-of-the-circumstances approach, building on what Nevada described in Doud v. Las Vegas Hilton Corp., 109 Nev. 1096 (1993), which Estate of Smith v. Mahoney’s Silver Nugget, 127 Nev. 855 (2011), held NRS 651.015(3) codified. Estate of Smith also affirmed summary judgment for the casino and held that the district court decides foreseeability as a matter of law. What Humphries did was reverse a summary judgment for the casino and send the case back, so it decides that the claim could proceed, not that the venue was liable.
For crowd-surge cases, this is the operationally critical doctrine. A crowd surge is usually caused by other patrons rather than by employees of the venue, so which foreseeability rule applies depends on the venue: NRS 651.015 speaks to an owner or keeper of a hotel, inn, motel, motor court, boardinghouse or lodging house, so it reaches a surge inside a lodging property, and whether it reaches a stand-alone arena, stadium or festival ground is a question for the case. Where it does not apply, the common law governs, and an operator may owe its visitors reasonable care as to foreseeable criminal acts of third parties (Doud v. Las Vegas Hilton Corp., 109 Nev. 1096 (1993)). Crowd crush is a documented danger in the industry (Hillsborough Stadium 1989, Station nightclub fire 2003, Love Parade Duisburg 2010, Astroworld 2021, Seoul Halloween 2022), but that record does not settle foreseeability in a given case. Where NRS 651.015 applies, an act is not foreseeable unless the owner failed to exercise due care for the safety of people on the premises, or prior incidents of similar wrongful acts occurred on the premises and the owner had notice or knowledge of them, and the court decides as a matter of law whether the act was foreseeable and whether the owner had a duty to take reasonable precautions. Humphries reads the due-care branch on the totality of the circumstances, so a venue does not defeat foreseeability merely by showing that no identical incident had happened there before.
Modified comparative fault. NRS 41.141 bars recovery only when the plaintiff’s negligence is greater than the negligence of the defendant, or the combined negligence of the defendants against whom recovery is sought. At or below that line, damages are reduced in proportion to the plaintiff’s share of the fault. The comparison runs against the defendants still in the case: a defendant who settles before judgment has that defendant’s negligence and the settlement amount kept from the jury, and the judge deducts the settlement from the net sum otherwise recoverable. Defense will argue that voluntary GA-floor or pit entry assigns substantial comparative fault. The doctrine works against that argument: voluntary entry is one of multiple operational decisions that contributed to injury, and the venue’s failure-to-manage typically dwarfs individual choice in foreseeability terms.
Non-delegable duty for security. Rockwell v. Sun Harbor Budget Suites, 112 Nev. 1217, 925 P.2d 1175 (1996), held that a property owner who hires security personnel to protect the premises and the people on them has a personal and non-delegable duty to provide responsible security personnel, and that those guards count as the owner’s employees even where a third party engaged them. The duty is stated in security terms and it does not by itself establish liability: Rockwell reversed a summary judgment and left questions such as whether the guard was acting within the scope of his employment for trial. What it does mean is that pointing at the security vendor is not an answer to the venue’s own duty. Both contractor and venue can share liability, and plaintiff strategy treats the contract between them as a discoverable allocation document. This pairs with the negligent security framework for understanding how venue-and-contractor cases develop in parallel.
Standards-of-care evidence. NFPA 101 (Life Safety Code) is the model code most often cited on crowd management. Its assembly occupancy provisions call for trained crowd managers, scaled to the size of the crowd, and for a life safety evaluation at larger festival-seating events. Two cautions before anyone leans on it. The section numbers, the crowd manager ratio and the evaluation thresholds have changed between editions, so the figures that matter are the ones in the edition actually in force. And NFPA 101 is a model code with no effect in Nevada except where Nevada or Clark County has adopted it, so the first question in a case is which edition applies to the venue you were injured in.
ANSI ES1.9 (Crowd Management) and ANSI ES1.40 (Event Security), published through the Event Safety Alliance, are the modern industry standards event professionals work to. These are private consensus standards rather than law, and they matter in a case only so far as a court accepts them as evidence of what reasonable care looked like. What they give you is a yardstick: a venue that ignored the practice its own industry publishes has a harder time arguing it behaved reasonably.
A venue that fell short of the crowd manager staffing the adopted code calls for, exceeded its code occupancy limit, or skipped a life safety evaluation the code required of it has a harder time arguing it acted reasonably. How much that shortfall is worth in a given case, and whether the court lets the jury hear it at all, is decided case by case.
The Las Vegas venue ecosystem.
| Venue | Capacity / Configuration |
|---|---|
| Sphere | 17,600 seated; 20,000 with GA standing |
| T-Mobile Arena | Up to 20,000 (variable floor including standing pit) |
| Allegiant Stadium | ~65,000 (with GA floor configurations available) |
| Resorts World Theatre | 5,000 |
| Brooklyn Bowl Las Vegas | ~2,000 (GA layout) |
| EDC Las Vegas (Motor Speedway) | 100,000+ per night across 9 stages |
| iHeartRadio Music Festival | T-Mobile Arena scale |
| Fremont Street Experience | Open-air pedestrian district |
None has experienced a publicly-reported major crowd-surge incident, but the ecosystem density is precisely the structural condition where rigorous crowd-density management discipline matters.
What the Defense Will Argue: And the Honest Reality
Crowd-surge cases are not easy. The defense bar has well-documented counter-positions, and surfacing them honestly serves you better than implying recovery is straightforward.
Astroworld is not legal precedent. All ten Astroworld wrongful death lawsuits and approximately 100 personal injury lawsuits have settled with confidential terms and gag orders. No defendant (including Travis Scott, Live Nation Entertainment, Scoremore Holdings, ASM Global, or Contemporary Services Corporation) has admitted liability. A Harris County grand jury declined criminal charges in June 2023. No published Texas appellate opinion has resolved the multi-defendant allocation, the performer-incitement liability theory, or the assumption-of-risk-versus-negligent-management framework. The settlement record shows plaintiffs received compensation, but controlling appellate law remains unresolved.
Defense position 1: Assumption of risk for voluntary GA-floor or mosh pit entry. When a plaintiff voluntarily entered a known-dangerous activity area, the doctrine holds they implicitly accepted ordinary risks. Pushing, shoving, falling: these are part of the standard pit experience. Defense will work hard to keep your case framed within those ordinary risks. This is not simply a fault-allocation argument. In Turner v. Mandalay Sports Entertainment, LLC, 124 Nev. 213, 180 P.3d 1172 (2008), the Nevada Supreme Court disapproved Mizushima to the extent it had held that primary implied assumption of risk was abolished by the comparative negligence statute, and to the extent it had treated the determination of duty as a factor left to the jury. After Turner, the district court addresses that doctrine as part of its initial duty analysis rather than leaving it to a jury to weigh alongside fault.
Counter: Plaintiffs argue that the following go beyond the risks a patron accepts by walking onto a general-admission floor:
- Overcrowding beyond venue capacity or fire-code occupancy limits
- Failure of crowd-density management (NFPA crowd manager ratio violations; absence of LSE for required venues; main entrance/exit capacity below code)
- Specific performer incitement of dangerous behavior
- Failure to halt a show in face of documented warnings (the Astroworld pattern: a security contractor texted the festival director “Someone’s going to end up dead” before the show was stopped)
- Compression asphyxia conditions, which are not inherent to ordinary moshing; they require sustained density beyond what voluntary participants reasonably contemplated
Whether any of that takes a case outside the ordinary risks a patron accepted is argued on the facts of the particular show, and defeating summary judgment to reach a jury is what plaintiff counsel works toward. Ask your attorney how the doctrine is likely to be applied to what happened to you.
Defense position 2: Multi-defendant fault allocation reduces per-defendant exposure. Modified comparative fault under NRS 41.141 also applies among co-defendants: you recover as long as your own negligence was not greater than the negligence of the defendant, or the combined negligence of the defendants you are suing, and subsection 4 then makes each defendant severally liable only for the portion of the judgment that represents its own percentage of negligence. Subsection 5 leaves joint and several liability intact for claims based on strict liability, an intentional tort, a toxic or hazardous release, concerted acts, or an injury resulting from a product. In a typical six-defendant crowd-surge case, each defendant attempts to allocate fault to others.
Counter: Even if plaintiff is found 0% at fault, the venue, promoter, performer, security contractor, and others fight a separate allocation battle that affects which insurance limits actually apply. Plaintiff strategy: name all responsible parties early, then prepare for the internal allocation fight as a discovery opportunity.
Defense position 3: The SAFETY Act federal defense. Mass-casualty venues with security contractors certified by the U.S. Department of Homeland Security may attempt to invoke the SAFETY Act, 6 U.S.C. §§441 to 444, to claim federal immunity. MGM raised this defense in Route 91 Harvest Festival litigation; it was briefed but never decided before settlement.
Counter: The Act applies to acts of “terrorism” (which crowd-surge incidents are not), but defense bar will sometimes attempt the argument to gain federal forum. Untested for crowd-surge specifically.
Defense position 4: “We followed industry practice.” A venue that complied with general event-industry norms will argue substantial compliance defeats negligence.
Counter: following general industry practice is evidence that a venue acted reasonably, not a defense that ends the case. A Nevada jury decides whether the care actually taken was reasonable in the circumstances, and a plaintiff can argue that the practice itself was inadequate for this crowd, or that the venue’s own written plan, staffing levels and density limits went further than the industry norm and were not followed. How far that argument gets depends on the facts and on what the court admits.
The practical takeaway: when evaluating firms for a crowd-surge case, ask which of these specific defense positions they have actually litigated against.
Questions to Ask Any Firm: And What Not to Do
The framework above is genuinely useful regardless of which firm you choose. Here is how to use it.
Specific questions to ask any law firm being evaluated for a crowd-surge case:
- “How do you allocate liability across the venue, promoter, performer, security contractor, and event organizer?” Tests whether the firm uses the multi-defendant framework or collapses to “the venue.”
- “How do you defeat the assumption-of-risk defense for general-admission floor entry?” Tests whether the firm understands the doctrine’s boundaries and the evidence required to overcome it.
- “How do you use Humphries v. New York-New York to establish foreseeability when there’s no prior crowd-surge at this specific venue?” Tests Nevada-specific doctrinal capability.
- “What standard-of-care evidence do you build the case around: NFPA 101? ANSI ES1.9? Both?” Tests use of industry standards as affirmative evidence.
- “How do you handle a defendant’s claim that they followed industry practice?” Tests knowledge of the ANSI ES1.40-2023 caveat that compliance does not confer immunity.
- “How do you investigate capacity calculations and crowd-density evidence in the first weeks after the incident?” Tests early-investigation discipline.
A firm that fails these questions is not equipped. A firm that passes them is, regardless of name.
What NOT to do regardless of which firm you choose:
- Do not give a recorded statement to the venue’s claims department, the promoter’s insurer, or the security contractor’s adjuster. Each will document your statements for use in claim valuation.
- Do not sign anything before counsel review, particularly broad releases that may extinguish claims against parties you did not specifically intend to release.
- Do not assume Astroworld means easy recovery. No published appellate ruling has resolved the underlying liability questions.
- Do not delay. Nevada’s statute of limitations on an action for injuries to a person, or for the death of a person caused by the wrongful act or neglect of another, is generally two years under NRS 11.190(4)(e). Different deadlines and exceptions can apply, so confirm your own deadline with an attorney.
If you lost a family member in a fatal crush incident, your case is a wrongful death case rather than the personal injury case an injured survivor would bring. Under NRS 41.085 the heirs and the estate’s personal representative may each bring an action: the heirs recover grief or sorrow, loss of probable support, companionship, society, comfort and consortium, and damages for the pain, suffering, or disfigurement of the person who died, while the estate recovers pre-death special damages such as medical expenses, funeral expenses, and penalties including punitive damages, and its wrongful death share does not include the decedent’s pain and suffering. Nevada also has a survival statute (NRS 41.100) under which the estate can continue claims the injured person could have brought, and an attorney will plead the claims that fit your facts. Bernstein has a separate practice page covering Las Vegas wrongful death representation. Review it, then schedule a consultation. The same multi-defendant allocation and Nevada-law framework applies, but the damages model is different.
If your situation involves a serious crowd-surge or crush injury at a Las Vegas concert, festival, or event, and you are evaluating which firm to retain, a free consultation lets you evaluate whether Bernstein is the right fit. Jack has been a Nevada plaintiff personal injury attorney for over 40 years. Call (702) 633-3333 to schedule.
Frequently Asked Questions
What is a crowd surge, exactly?
A sudden compression of crowd density in a confined area, typically toward a stage barrier, exit, or fixed structure. The actual injury mechanism is compression asphyxia: sustained chest compression preventing breathing. Forensic findings across documented incidents (Hillsborough 1989, NYC 1991, Astroworld 2021) consistently show petechiae of conjunctivae and face from chest compression, with minimal blunt-force injuries. Death can occur within three to five minutes of sustained high compression.
Can the venue actually be sued for what a crowd does?
Yes, though “the venue” is one of multiple parties. Venues owe a duty of care to ticket-holders as invitees under Nevada law, including managing foreseeable risks of crowd surge through capacity decisions, crowd manager staffing, life safety evaluations, and main entrance/exit design. A venue owes its visitors reasonable care to protect them from foreseeable criminal acts of third parties (Doud v. Las Vegas Hilton Corp., 109 Nev. 1096 (1993)); whether a crowd act was foreseeable depends on the circumstances, including what the operator knew about prior incidents. The venue is one defendant; the promoter, performer, security contractor, and event organizer typically share allocation.
Can I sue the performer for inciting the crowd?
Sometimes it is pleaded, usually on the theory that the performer actively and knowingly encouraged dangerous behavior or kept performing after being warned during the show. No Nevada decision settles when a performer can be held responsible for a crowd’s conduct, and the suits filed elsewhere against performers have not produced a published appellate ruling that sets the standard, so treat this as an argument to be made on your facts rather than a rule, and ask your attorney whether it fits your case. It is in any event a small part of most crowd-surge claims, which turn on the venue’s and the promoter’s crowd management.
Will my case win because Travis Scott settled all those Astroworld lawsuits?
Astroworld is not legal precedent. The cases settled with confidential terms and no admissions of liability. A Harris County grand jury declined criminal charges. No published Texas appellate opinion has resolved the underlying liability questions. Your case rises or falls on its own facts: capacity calculations, crowd-density management failures, security deployment, the venue’s compliance with NFPA 101 and applicable ANSI standards, and whether defendants had foreseeability under Humphries.
How long do I have to file a crowd-surge case in Nevada?
Generally two years after the cause of action accrues, for an injury claim and for a wrongful death claim alike, under NRS 11.190(4)(e). Different deadlines and exceptions can apply, and the period does not run while the person entitled to sue was under 18 or insane when the claim accrued (NRS 11.250). Evidence preservation begins immediately: capacity records, security deployment records, dispatcher communications, venue surveillance footage, and EMS records all benefit from early preservation demands.
Get the Right Help
Statute of limitations: generally 2 years. Nevada’s NRS 11.190(4)(e) provides two years on most personal injury claims, and wrongful death is two years from the date of death. Different deadlines and exceptions can apply depending on the claim and its circumstances, and the period does not run while the injured person was under 18 or insane when the claim accrued (NRS 11.250), which matters when the person hurt in a crowd surge is a child. Evidence preservation begins immediately.
Crowd-surge cases turn on operational details that do not come up in most premises-liability claims. The decisions about which defendants to name, how to defeat assumption-of-risk, how to use industry standards as affirmative evidence, and how to leverage Humphries foreseeability for Nevada cases shape every case.
Call Jack Bernstein Injury Lawyers at (702) 633-3333 for a free consultation. Jack has been a Nevada personal injury attorney for over 40 years. There is no fee unless we recover for you.