WORKING WITH CROWDS ASTROWORLD CASE STUDY
Astroworld Case Study · Section 6 · Part 1

Event Permits, Licences and Regulatory Documentation

This section is particularly important because Astroworld exposes an unusual division between property ownership, municipal jurisdiction and event-specific regulatory approval.

NRG Park was county-owned property, but it sits inside the City of Houston.

The Astroworld Event Operations Plan itself stated that the festival site fell under the jurisdiction of the Houston Police and Fire Departments.

At the same time, some contractual and safety documentation was held by NRG Park/Harris County rather than by the City.

The resulting permit picture is therefore not a single “Astroworld licence”.

Instead, there were separate approvals and permits for matters such as:

Street closures
Tents
LPG / liquid gas
Assembly / fire precautions
Pyrotechnics
Fireworks
Food provision
Temporary event controls
Public-space interfaces

The principal festival safety plan was handled differently.

The City also stated that it did not issue an outdoor occupancy permit for Astroworld.

That distinction will become important later when examining capacity, barrier configuration, crowd density and responsibility.

The central regulatory question throughout this section is therefore not simply:

“Did Astroworld have permits?”

The more useful question is:

Which elements were regulated, by whom, under what authority, and who—if anyone—formally approved the overall crowd configuration?

Astroworld Case Study · Section 6 · Part 2

City of Houston — Municipal Permit Release

Mayor Turner Releases City Permits Related to Astroworld Fest

Source type: Primary-government material reproduced by contemporary media

This is the most useful single index to the municipal permits associated with Astroworld 2021.

The release was made following the disaster when Mayor Sylvester Turner directed the publication of the City-held permit material.

The City identified records held by the Mayor's Office of Special Events, Houston Health Department and Houston Fire Department.

It stated that the release was not necessarily the complete regulatory record because NRG Park was county-owned and other material might have been held elsewhere.

The records specifically identified were:

HFD Tent — Acme Party
HFD Tent — Aztec
HFD Occupant Safety Intervention Application
HFD Pyrotecnico — Flames and Pyrotechnics
HFD Pyrotecnico — Fireworks
HFD Spectrum — Liquid Gas
HFD Spectrum — Liquid Gas, Assembly and Tent
Houston Health — Food Permit Application
Houston Health — Permit List Food and Beverage
Mayor's Office of Special Events — Street Closure

The same release is significant for what it says was not issued.

The City stated that occupancy permits were not issued for events held entirely outdoors, and that Houston's Administrative and Regulatory Affairs department did not issue an NRG Park noise permit.

It also stated that the event safety plan would be filed by the producer with the property owner.

Full URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/

Research note: The original City webpage containing the complete downloadable permit packet has not yet been located.

This contemporary page reproduces the City's release, but obtaining the underlying individual permit files remains worthwhile.

ABC13 — Houston Releases Permits Issued in Advance of Astroworld

Source type: Contemporary local reporting based on City-released records

ABC13 independently reported the City's release and confirms the same regulatory split:

street closures, tents, food-related permits and pyrotechnic/fire controls were within the City-held file, while there was no outdoor occupancy permit for the festival.

This is valuable corroboration because it was published immediately after the event and was based upon the released municipal permit records rather than later retrospective interpretation.

Full URL
https://abc13.com/post/astroworld-festival-deaths-houston-concert-tragedy-city-permits/11216462/
Astroworld Case Study · Section 6 · Part 3

Astroworld 2021 Event Operations Plan — Jurisdiction and Regulatory Interface

Jurisdiction Statement

Source type: Event operational document

The 56-page Astroworld 2021 Event Operations Plan is a particularly important companion to the permit records.

Its jurisdiction statement explicitly says:

“The festival site falls under the jurisdiction of the City of Houston Police and Fire Departments.”

This is important because it demonstrates what the festival's own written operational documentation understood the jurisdictional position to be before the incident.

The plan also envisaged a unified-command structure in which the local jurisdiction would assume command when the local-jurisdiction Incident Command Post was activated.

The document should not, however, be treated as proof that every procedure described in it had received separate regulatory approval.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Relationship with Other Regulatory Programmes

Source type: Event operational document

A separate passage in the EOP is particularly useful when reconstructing the regulatory architecture.

The emergency section says that the EOP was intended to interface with other “regulatory required programs” rather than replace them.

This matters because the EOP should not be mistaken for the entirety of the regulatory file.

There should potentially have been multiple parallel records dealing with fire prevention, LPG, food safety, pyrotechnics, temporary structures, roads, medical operations and other event components.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf
Astroworld Case Study · Section 6 · Part 4

Permit Timing, Street Closures and Fire-Prevention Regulation

Washington Post — Astroworld Venue Filed Some Plans Only Days Before the Festival

Source type: Contemporary investigative reporting based upon released City records

This investigation is extremely useful because it examined the permit applications, emails and plans released by Houston rather than merely listing the documents.

The paper reported that some Astroworld-related material arrived only days before the event.

It identified an initial site map and road-closure proposal on 25 October, revised material on 31 October and further correspondence immediately before the festival.

A City permit concerning NRG Park was approved on 1 November.

The reporting also found that the November permit was connected with a broader NRG Park application originally approved earlier in 2021 covering multiple events rather than solely Astroworld.

According to the records examined by the newspaper, the earlier security submission made relatively little distinction between concerts and other NRG Park events.

The article additionally reports that Astroworld-related fire-code, catering and fireworks material was received between 27 October and 5 November and that one fire-safety document in the released collection appeared unsigned and undated.

This is an important line of enquiry, but the newspaper's interpretation should ultimately be checked against the complete original permit packet.

Full URL
https://www.washingtonpost.com/investigations/astroworld-permits-city-houston/2021/11/10/ffc962ea-41aa-11ec-9ea7-3eb2406a2e24_story.html

Mayor's Office of Special Events — Street-Closure / Special-Event Permitting

Source type: Official City of Houston regulatory information

Houston's Mayor's Office of Special Events is the municipal office responsible for coordinating permits where an event requires use or closure of City streets or other relevant public space.

Its permitting guidance is useful for understanding why the Astroworld municipal permit file contains a street-closure permit, despite the principal festival footprint being on NRG Park property.

The current guidance must be treated cautiously because Houston's event-permitting regime was subsequently changed after Astroworld.

It should therefore be used to understand the City's administrative structure, not automatically treated as the exact wording of the rules in force on 5 November 2021.

Full URL
https://www.houstontx.gov/specialevents/permittinginfo.html
Forms repository
https://www.houstontx.gov/specialevents/forms.html

Houston Fire Department — Fire Prevention Permits and Regulatory Controls

Source type: Official municipal regulatory information

The Houston Fire Marshal's Office administers a range of fire-prevention permits relevant to temporary events, including matters involving tents, assembly use, LPG/open flames and other fire hazards.

That regulatory structure corresponds closely with the Astroworld permits released after the incident:

Tent permits, liquid-gas permits, assembly-related documentation, pyrotechnic approvals and fireworks approvals.

These permits are therefore important evidence of component-specific fire regulation, but they should not be interpreted as a general approval of the crowd-management design.

Full URL
https://www.houstontx.gov/fire/business-information/
Fire Marshal standards and codes
https://www.houstontx.gov/fire/HFMO/standardsandcodes.html
Astroworld Case Study · Section 6 · Part 5

Houston Fire Department — Temporary Structures and Occupant-Safety Records

HFD Tent Permit — Acme Party
Underlying permit still to recover

Source type: Primary permit identified in City release

The City's Astroworld permit index specifically identifies a Houston Fire Department tent permit connected with Acme Party.

The underlying permit itself is worth retrieving because it may contain the temporary-structure dimensions, location, responsible contractor, inspection status and approval/signature information.

At present the document's existence has been verified through the City's published permit index, but a stable direct public copy of the actual permit has not been located.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
HFD Tent Permit — Aztec
Underlying permit still to recover

Source type: Primary permit identified in City release

A second separate tent permit was identified for Aztec.

Again, the value of the underlying document is not simply the existence of a tent approval.

It may show which temporary structures were inspected, the layout submitted to the Fire Marshal and exactly when approval occurred.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
HFD Occupant Safety Intervention Application
High-priority underlying document

Source type: Primary regulatory record identified in City release

This is potentially one of the most important permit-related documents in the City collection because its title relates directly to occupant safety.

The document is separately identified within Houston's released Astroworld permit inventory.

However, the document itself needs to be obtained before any requirements are attributed to it.

The title alone does not establish that Houston approved the overall crowd capacity, audience-pit design or crowd-density arrangements.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
Astroworld Case Study · Section 6 · Part 6

Pyrotechnics, Fireworks, LPG and Food Regulation

HFD Pyrotecnico — Flames and Pyrotechnics Permit

Source type: Primary permit identified in City release

This record concerns the special-effects elements incorporated into the performances.

Fire and flame effects require controls separate from general event safety planning, and Houston identified an Astroworld permit specifically covering flames and pyrotechnics.

It may eventually help reconstruct stage safety, exclusion zones, operator responsibilities and Fire Marshal inspection activity, although those issues are peripheral to the crowd-compression mechanism itself.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
HFD Pyrotecnico — Fireworks Permit

Source type: Primary permit identified in City release

Houston's release separately identifies a fireworks permit, suggesting that fireworks and other flame/pyrotechnic effects were handled through distinct fire-prevention documentation.

The original permit would be useful for identifying approved firing locations, responsible operators, safety distances and HFD inspection/sign-off.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
HFD Spectrum — Liquid Gas Permit

Source type: Primary permit identified in City release

The permit index identifies an HFD permit for liquid gas, most likely connected with LPG use associated with temporary event infrastructure or catering.

Houston Fire Department guidance confirms that LPG and open-flame activities form part of its fire-permitting regime.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
HFD Spectrum — Liquid Gas, Assembly and Tent Documentation

Source type: Primary permit identified in City release

A separate Spectrum-related record combined liquid gas, assembly and tent matters.

This is potentially useful because it may demonstrate how multiple temporary-event fire risks were packaged within a single inspection/permit process.

Again, the underlying permit should be recovered before drawing conclusions about what was physically inspected or approved.

Reference URL
https://stylemagazine.com/news/2021/nov/19/mayor-turner-releases-city-permits-related-astrowo/
Houston Health Department — Food Permit Application and Vendor Permit List

Source type: Primary municipal regulatory records

Houston's released Astroworld records include both a food permit application and a list of approved food-and-beverage vendors.

Houston Health Department documentation confirms that temporary public food operations require regulatory approval and inspection.

These records will not directly explain the crowd disaster, but they are useful when constructing the complete regulatory footprint of Astroworld.

They show that detailed regulatory oversight existed for several individual components of the festival even though there was no equivalent municipal outdoor occupancy permit.

Houston Health permit information
https://www.houstonhealth.org/services/permits/food-permits/temporary-food-permits
Astroworld Case Study · Section 6 · Part 7

Texas Mass-Gathering and Outdoor-Music-Festival Legislation

Texas Mass Gatherings Act — Health and Safety Code Chapter 751

Source type: Primary legislation

This statute requires careful handling because it has been repeatedly mentioned in post-Astroworld discussions.

Chapter 751 defines a regulated “mass gathering” as, among other things, one held outside the limits of a municipality.

That geographic element is decisive for Astroworld:

although NRG Park was owned by Harris County, it was located inside Houston municipal boundaries.

On the statutory wording, the ordinary Chapter 751 county mass-gathering permit mechanism therefore did not fit Astroworld in the same way that it would an event in an unincorporated county area.

Had Chapter 751 applied, its permit regime included questions concerning the maximum attendance, arrangements to restrict attendance, public safety, traffic control, health and sanitation and adequate medical care.

That makes the statute important comparative evidence, even though its geographical definition is central to why Harris County officials disputed suggestions that a Chapter 751 permit should have been issued for Astroworld.

Full statute
https://statutes.capitol.texas.gov/Docs/HS/pdf/HS.751.pdf

Texas Occupations Code Chapter 2104 — Regulation of Outdoor Music Festivals

Source type: Primary legislation

The second relevant Texas statutory regime is Chapter 2104 of the Occupations Code.

It defines an “outdoor music festival” for this chapter as a qualifying multi-day live-music event where more than 5,000 people attend and at least some performers or audience members are outdoors — but it also requires that the performance occur outside the boundaries of a municipality.

Again, because Astroworld was within Houston, this statutory county-level outdoor-music-festival framework does not neatly apply to the 2021 festival.

This distinction is important because references to Astroworld having “no music-festival permit” can be misleading unless the reader first understands the territorial scope of the legislation.

Full URL
https://statutes.capitol.texas.gov/Docs/OC/pdf/OC.2104.pdf
Astroworld Case Study · Section 6 · Part 8

Permitting Disagreement, Overall Event Approval and the 2018 City–County Arrangement

Texas Task Force on Concert Safety — Permitting Findings

Source type: Official post-incident government review

The April 2022 Texas Task Force report is valuable here because the Task Force identified inconsistent permitting and jurisdictional arrangements as an issue requiring reform.

Its recommendations emphasised clearer, more standardised permitting and responsibility structures.

There is, however, an important point of interpretation.

The Task Force report contains wording stating that, according to officials, “no permits were obtained”.

That cannot sensibly be read as meaning no permit of any kind existed, because Houston publicly released multiple Astroworld permits.

The better reading is that the report was addressing the absence of a comprehensive mass-gathering/outdoor-festival permit framework of the type being discussed by the Task Force.

Harris County Fire Marshal Laurie Christensen publicly disputed the applicability of the county mass-gathering and outdoor-music statutes precisely because both statutes were geographically limited to events outside municipal boundaries.

This is therefore an area where the study should preserve the documented disagreement rather than simplify it.

Full URL
https://gov.texas.gov/music/page/governor-abbotts-texas-task-force-on-concert-safety-april-2022-report

ABC13 — Who Approved the Overall Event?

Source type: Contemporary investigative reporting

ABC13 investigated this jurisdictional problem immediately after the disaster.

It found that Harris County Fire Marshal's Office did not issue the relevant municipal fire permits because NRG Park was located inside Houston, while Houston's released permits dealt primarily with specific hazards and temporary-event components rather than approving the complete audience configuration.

Houston Fire Chief Samuel Peña also explained that an outdoor occupancy permit was not issued because Houston did not use that type of occupancy permit for wholly outdoor events.

Who, if anyone, formally approved the overall crowd configuration rather than its individual component parts?

This article is valuable because it identifies the central regulatory question that runs through the Astroworld evidence.

Full URL
https://abc13.com/post/astroworld-2021-festival-travis-scott-astro-fest-security/11217243/

2018 City–County NRG Park Memorandum / Interlocal Arrangement

Source type: Government agreement — original document not yet recovered

Contemporary reporting indicates that a City–County arrangement dating from 2018 governed aspects of fire-inspection responsibility at NRG Park.

Later accounts disagree somewhat over how broadly that agreement should be interpreted.

Houston Fire Chief Peña subsequently stated that the arrangement required City fire inspectors to perform maintenance inspections of NRG Park buildings, but said it did not itself allocate responsibility for outdoor events in the parking areas.

Harris County Fire Marshal Laurie Christensen relied on the jurisdictional arrangement in arguing that Harris County had no permitting authority over the Astroworld event.

The original 2018 agreement is therefore a high-priority document.

We should not rely permanently on newspaper descriptions when the precise wording may affect questions of inspection, permitting and authority.

Status: original executed 2018 City–County agreement still to recover.

Secondary reference
https://www.houstonchronicle.com/news/houston-texas/houston/article/Harris-County-officials-dismiss-Abbott-Astroworld-17106679.php

Astroworld Public-Facing Rules and Alcohol Provision

Source type: Contemporary festival material

The surviving official Astroworld website confirms that alcohol was sold at the festival and set out rules relating to identification, prohibited outside alcohol, intoxicated customers and event security screening.

It also confirms that carnival rides and games operated within the event.

These details indicate two further regulatory areas that should form part of the documentary search:

alcohol licensing / temporary authorisation and amusement-ride inspection / certification.

A reliable publicly indexed copy of the Astroworld-specific Texas Alcoholic Beverage Commission authorisation or the individual ride inspection/certification records has not yet been found.

These should not be assumed or reconstructed.

Full URL
https://www.astroworldfest.com/faq/
Astroworld Case Study · Section 6 · Part 9

Important Documentary Gaps

There are several records that should be considered essential before this section is closed completely.

1
The complete original City of Houston Astroworld permit packet

Every page, stamp, signature, amendment, inspection record and approval associated with the ten permits publicly identified.

2
The final street-closure permit and all associated NRG Park/City correspondence

Particularly the October–November 2021 revisions.

3
The original HFD Occupant Safety Intervention Application

This may be particularly significant and should be prioritised.

4
The approved site plan and all Fire Marshal mark-ups

Including the identity and authority of the approving inspector.

5
The complete 2018 City of Houston–Harris County NRG Park MOU/interlocal agreement

The precise wording may materially affect questions of inspection, jurisdiction and authority.

6
The event-use/licence agreement between NRG Park/ASM Global/HCSCC and Live Nation/Scoremore

Including clauses allocating safety, capacity, security and emergency-planning responsibility.

7
Any Harris County/HCSCC approval of the Astroworld safety plan

Together with correspondence showing who reviewed it and what revisions were required.

8
TABC alcohol licensing/temporary-event records

Specific to Astroworld 2021.

9
Amusement-ride registration, inspection and insurance certification records

For the carnival attractions operating within the event.

10
Every HFD inspection report produced during build, event opening and show day

Rather than only the permit applications.

11
Any temporary electrical, structural, stage, rigging or generator permits/inspection documents

Associated with the festival.

12
The final approved version of the Astroworld site plan

With document-control/version information enabling it to be distinguished from preliminary plans.

What Section 6 Establishes So Far

The evidence does not support the simple statement that “Astroworld was unpermitted”.

Multiple City permits clearly existed.

Equally, those permits should not be described as a comprehensive municipal approval of the overall crowd-management system.

Houston regulated numerous individual event components, while the festival safety plan and overall event arrangements sat within a more complicated relationship involving the promoter, venue operator/property interests, City public-safety agencies and county ownership.

The principal Texas county-level mass-gathering and outdoor-music-festival statutes were geographically framed around events outside municipalities, creating a significant distinction for an event held on county-owned land inside Houston.

This sets up the next stage of the study particularly well.

Section 7 — Astroworld Event Operations and Safety Plans can move beyond asking which permissions existed and begin reconstructing what the event plans actually required.
Astroworld Case Study · Section 7 · Part 1

Astroworld Event Operations and Safety Plans

This section moves from regulatory approval into the actual operational planning system intended to govern Astroworld 2021.

The evidence shows that Astroworld did not operate without written safety planning.

There was a substantial Event Operations Plan, an emergency-response framework, an evacuation plan, a security plan, an HFD Event Action Plan, Incident Command System documentation, a medical plan and additional Live Nation safety/security material.

The more important questions are therefore what risks those plans identified, how responsibilities were allocated, whether the documents were final and complete, how the separate plans interfaced, and whether the arrangements described on paper were functioning during the incident.

Astroworld 2021 — Event Operations Plan

Source type: Primary event-planning document

This 56-page document is the principal publicly available operational plan for Astroworld 2021.

The publicly circulated copy identifies NRG Park, the dates 5–6 November 2021, ScoreMore branding and Version 0.1. Personal names and contact details have been redacted from the copy.

Its contents are divided broadly into:

General Information
Security Plan
Emergency Response Plan
Evacuation Plan

The document also contains supplemental material.

It covers management responsibilities, the Incident Command System, Event Control, security deployment, access control, incident reporting, emergency communications, medical emergencies, mass-casualty incidents, severe weather, fire, hazardous materials, evacuation, show-power shutdown and evacuation maps.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Management Structure and Allocation of Responsibility

The EOP divided responsibility across several festival departments.

Administration
Overall operation
Site Operations
Infrastructure and build
Safety & Security
Guest and employee safety, hazard mitigation and emergency response
Production
Stages, sound, lighting and artist/touring liaison

Significantly, the plan states that Production was ultimately responsible for stage safety during an incident.

This division becomes important when examining the eventual show-stop process because responsibility did not sit with a single operational function.

Astroworld Case Study · Section 7 · Part 2

Incident Command, Unified Command and EOP Version Control

Astroworld EOP — Incident Command System

Source type: Primary event-planning document

The EOP explicitly adopted an Incident Command System based on NIMS and said the festival would use a unified-command model for significant incidents.

All routine safety and security activity was intended to flow through the Event Control Center (ECC).

For minor incidents, the festival emergency manager would direct the response.

If an incident escalated and the festival emergency manager requested activation of the local-jurisdiction Incident Command Post, the plan stated that the local jurisdiction would assume command.

Incident detected → Event Control → Festival Emergency Manager / Security AOD → ICP activation where required → Local jurisdiction / Unified Command

The distinction between Festival Event Control, the Festival ICP and the public-safety command arrangements operated by HPD/HFD is consequently a major issue for later examination.

Important “TBD” Fields in Version 0.1

The publicly available Version 0.1 contains several fields still marked “TBD”.

Event Control Center location
ECC telephone number
Incident Command Post telephone number
Employee entrance
Community contact
Press contact
Designated area of refuge
Employee marshalling area

That does not establish that these arrangements did not exist operationally.

It establishes only that they were not completed in the publicly available copy.

This becomes particularly important because later evidence indicates that another EOP version existed.

EOP Version 1.1 and Authorship

Source type: Court filing — party submission, not an independent judicial finding

A March 2024 defence filing in the Astroworld civil litigation refers to Exhibit 35 as “Astroworld 2021 Event Operations Plan, v. 1.1”.

The same filing states, citing evidence produced in discovery, that Seyth Boardman of B3 Risk Solutions was the Astroworld Safety and Risk Director and author of the festival EOP.

This is highly significant because the publicly available document is labelled Version 0.1, while litigation evidence refers to Version 1.1.

The court filing should not be treated as an independent court determination of disputed liability issues.

However, its identification of a later EOP version and underlying exhibit gives us an important documentary retrieval target.

Full URL
https://dallasexpress.com/wp-content/uploads/2024/04/Travis-Scott-motion-for-summary-judgment.pdf

Was the Public EOP the Final Plan?

The Houston Chronicle established another important uncertainty.

It reported that the licence agreement required ScoreMore to prepare an Event Operations Plan and obtain approval from ASM Global on behalf of Harris County.

However, the Harris County Sports and Convention Corporation told the newspaper that it did not believe the 56-page copy obtained by the Chronicle was the final version, while its counsel reportedly said the county possessed no newer copy.

The study should therefore avoid describing Version 0.1 unequivocally as “the final Astroworld safety plan.”

It is more accurate to call it:

the principal publicly available Astroworld 2021 Event Operations Plan.

The question of what constituted the final approved plan remains important.

Full URL
https://www.houstonchronicle.com/projects/2021/astroworld-no-escape-plan/
Astroworld Case Study · Section 7 · Part 3

Security Plan and Front-of-Stage Barrier Provision

Astroworld EOP — Part 2: Security Plan

Source type: Primary event-planning document

The Security Plan explicitly acknowledged several significant event risks.

It identified potential alcohol/drug incidents, evacuation requirements and the “ever-present threat of a mass casualty situation” as key concerns.

Security was intended to cover:

Roadways and access points
Emergency egress gates and routes
Perimeter fencing
Production areas
Front and rear of stages
VIP areas
Activations
Roaming positions throughout the site

The document therefore recognised both crowd-management and emergency-response functions as part of security.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Front-of-Stage Barrier Provision

Source type: Primary event-planning document

The EOP contains only a very short description of the stage-front barrier arrangement.

It states that the fronts of the stages would be protected by MOJO-style barricade using an apron for stability and to prevent movement.

That is significant because the EOP provides considerably more detail for issues such as access screening, firearms, active shooters and bomb threats than it does for the management of large standing audiences immediately in front of the performance stages.

The detailed physical configuration of the main-stage barrier system therefore has to be reconstructed from the separate site plans, engineering drawings, photographs, video and subsequent investigation rather than from this paragraph alone.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf
Astroworld Case Study · Section 7 · Part 4

Incident Management and the Crowd-Compression Planning Gap

Incident Identification, Notification and Response

Source type: Primary event-planning document

The EOP established a five-stage incident-management process:

Identification → Notification → Response → Assist → Report

Once an incident was identified, personnel were expected to report it to Event Control, which would allocate security, medical or other resources and record the incident through an Incident Management System.

The plan also classified incidents into Classes 1–3.

Class 1 covered the most serious incidents, including major trauma and death, and required upper-management involvement and frequently law-enforcement involvement.

At what point did the accumulating medical emergencies cease to be treated as individual incidents and become recognised as one developing crowd emergency?
Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Civil Disturbance / Riot and Dangerous Crowd Behaviour

Source type: Primary event-planning document

The EOP did contain a section dealing explicitly with crowds.

Under Civil Disturbance/Riot, it states that whenever large groups gather there is potential for serious disorder and that effective management should begin when the doors open.

Personnel were instructed to identify potentially dangerous crowd behaviour at an early stage.

However, the warning indicators primarily concern behaviours such as:

Aggressive conduct
Inflammatory language
Attempts to arouse the crowd
Agitated groups
Threatening behaviour
Destructive behaviour

This is predominantly a public-order model of crowd risk rather than a detailed treatment of high-density crowd dynamics.

Crowd Surge / Crowd Compression Gap

Houston Public Media reviewed the EOP shortly after the disaster and observed that, despite considerable coverage of severe weather, active shooters, bomb threats and other emergencies, the document did not contain a specific crowd-surge procedure.

Crowd-safety specialist Paul Wertheimer characterised the plan as insufficiently specific to the risks of the event's standing-audience configuration.

Independent examination of the EOP supports the narrower documentary point:

it contains sections covering civil disturbance and threatening crowd behaviour, but no equivalent incident procedure headed:

crowd surge, crowd crush, crowd compression, dangerous crowd density or front-of-stage crowd pressure.

That distinction is central to this study.

Full URL — Houston Public Media / TPR
https://www.tpr.org/news/2021-11-10/astroworlds-safety-plan-failed-to-account-for-key-crowd-issues-expert-says
Astroworld Case Study · Section 7 · Part 5

Mass-Casualty Planning and Emergency Escalation Thresholds

Astroworld EOP — Multiple Casualty Incidents

Source type: Primary event-planning document

Unlike crowd compression, mass-casualty response was expressly planned for.

The EOP defined an MCI operationally as a situation in which on-site EMS became overwhelmed and outside resources had to be summoned.

If patient care became jeopardised, the EMS Director was expected to inform Event Control and recommend activation of the MCI plan.

The planned response included:

Establishment of Incident Command
Notification of the local jurisdiction
Reporting casualty numbers and ambulance access
Establishing triage and communications
Hospital notification
START triage
Ambulance staging
Transport coordination

This is a critical distinction:

The plan contemplated how to manage large numbers of casualties once they existed, but did not contain an equivalent detailed protocol for detecting and controlling the crowd conditions capable of producing those casualties.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Emergency Incident Management Thresholds

Source type: Primary event-planning document

The EOP required Event Control and the Security AOD to be notified immediately where an incident involved:

A fatality
Hospitalisation of three or more people from the same incident

This is potentially very important when the live timeline is reconstructed.

The existence of that written threshold allows us later to compare when multiple casualties became known within the command structure against when escalation or show-stop decisions occurred.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf
Astroworld Case Study · Section 7 · Part 5

Mass-Casualty Planning and Emergency Escalation Thresholds

Astroworld EOP — Multiple Casualty Incidents

Source type: Primary event-planning document

Unlike crowd compression, mass-casualty response was expressly planned for.

The EOP defined an MCI operationally as a situation in which on-site EMS became overwhelmed and outside resources had to be summoned.

If patient care became jeopardised, the EMS Director was expected to inform Event Control and recommend activation of the MCI plan.

The planned response included:

Establishment of Incident Command
Notification of the local jurisdiction
Reporting casualty numbers and ambulance access
Establishing triage and communications
Hospital notification
START triage
Ambulance staging
Transport coordination

This is a critical distinction:

The plan contemplated how to manage large numbers of casualties once they existed, but did not contain an equivalent detailed protocol for detecting and controlling the crowd conditions capable of producing those casualties.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Emergency Incident Management Thresholds

Source type: Primary event-planning document

The EOP required Event Control and the Security AOD to be notified immediately where an incident involved:

A fatality
Hospitalisation of three or more people from the same incident

This is potentially very important when the live timeline is reconstructed.

The existence of that written threshold allows us later to compare when multiple casualties became known within the command structure against when escalation or show-stop decisions occurred.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf
Astroworld Case Study · Section 7 · Part 7

Houston Fire Department Event Action Plan and Incident Command Documents

HFD Special Events — Astroworld Festival Event Action Plan

Source type: Primary public-safety planning record summarised within HPD investigation

The HPD investigation preserved and summarised a separate Houston Fire Department Special Events Event Action Plan covering 5–6 November 2021.

The HFD plan included assigned emergency-operations personnel, communications personnel, Special Response Group resources, inspectors, a command vehicle, command-post arrangements, radio channels and private-event medical providers.

This is important because the promoter's EOP was not the only emergency plan in operation.

There was simultaneously a separate HFD planning and command structure.

Working copy of complete HPD investigation
https://www.documentcloud.org/documents/23889335-travis-scott-concert-final-police-report/
ICS-202 — Incident Objectives

Source type: Primary Incident Command System document

The HPD investigation identifies an HFD ICS-202 covering the operational period beginning 5 November.

Its objectives included:

protecting responders and the public; responding with medical care and protection of life/property; maintaining normal public-safety services; coordinating operations between agencies; and maintaining effective communications.

The document was identified as having been prepared by the HFD liaison.

ICS-203 — Command Structure

Source type: Primary Incident Command System document

The ICS-203 identified the HFD Incident Commander and other command positions for the operational period.

Its existence is valuable because it allows the public-safety chain of command to be reconstructed independently from the festival's own Event Control structure.

That distinction becomes especially important when analysing who had operational information and who possessed authority to act upon it.
ICS-204 — MCI Resource Assignment

Source type: Primary Incident Command System document

One HFD ICS-204 assignment specifically allocated a medical resource to remain available:

“Standby in the event of MCI, Prepare to set up for treatment area. Assist in monitoring the situation.”

This is strong evidence that an MCI was not an unforeseeable concept introduced only after the disaster.

MCI contingency had been incorporated into pre-event public-safety planning.

ICS-205 / ICS-205A — Communications Plans

Source type: Primary Incident Command System documents

The HPD case file identifies multiple communications documents covering law enforcement, HFD medical operations and Harris County Emergency Corps.

Channels included separate primary and expanding channels for:

law-enforcement interior operations; exterior/traffic operations; HFD medical operations; and Harris County Emergency Corps.

This makes later communications failures or gaps especially important to analyse at the level of interoperability, rather than simply asking whether radios existed.
ICS-206 — Medical Plan

Source type: Primary Incident Command System document

The ICS-206 identified the ParaDocs main medical tent at Gate 16, Harris County Emergency Corps resources operating within the event footprint and a list of receiving hospitals.

This is particularly useful because it demonstrates a pre-planned interface between:

Private festival medical provision → Ambulance transport → Receiving hospitals

The effectiveness of that interface is a separate question from whether it existed in the plan.

HPD investigation URL for ICS records
https://www.documentcloud.org/documents/23889335-travis-scott-concert-final-police-report/
Astroworld Case Study · Section 7 · Part 8

Live Nation Safety Policies, Security Assessment and Venue Approval

Live Nation Entertainment Safety Policies

Source type: Corporate safety-policy material identified in the HPD investigation

This is a particularly important body of evidence that has received considerably less public attention.

Detective J. Caten records reviewing approximately 219 pages of Live Nation documentation, numbered LNAW_HPD_0000065 through LNAW_HPD_0000284.

The material included policies, roles, templates and safety guidance intended for event-production teams.

Caten specifically noted that he could not determine from the documents alone which elements were actually practised at Astroworld.

The collection included a policy titled:

Live Nation Entertainment — After Action Review — Policy S-012

and, later in the file:

Astroworld — Festival Security Assessment — North America Festivals — 2021.

These underlying documents are a major retrieval priority.

Full HPD report copy
https://media.telemundohouston.com/2023/07/Astroworld_Redacted_Final.pdf

Astroworld Festival Security Assessment — North America Festivals 2021

Source type: Event-specific corporate security assessment — known to exist, underlying document not yet publicly recovered

HPD specifically identifies this document beginning at Bates number LNAW_HPD_0000225 within material supplied by Live Nation.

Its title suggests that it may be substantially more event-specific than the public EOP.

This document could potentially answer questions including:

What crowd risks Live Nation assessed before the event
Whether previous Astroworld incidents were considered
Whether performer/audience behaviour was assessed
Whether crowd surge or compression was recognised
What staffing assumptions were used
What mitigation measures were required

Until the document itself is recovered, those questions should remain open.

Reference URL
https://media.telemundohouston.com/2023/07/Astroworld_Redacted_Final.pdf

Harris County Sports and Convention Corporation Event Approval Letter

Source type: Primary venue/government approval record — known to exist

HPD Detective Caten records receiving an HCSCC Event Approval Letter from ASM Global attorney Brett Young.

The same investigator also received an unredacted Astroworld EOP from ASM Global.

The approval letter is potentially extremely important because it may establish:

Exactly what HCSCC/ASM Global approved
Which plan version was approved
Whether approval was conditional
When approval occurred
What responsibilities remained with ScoreMore/Live Nation
Whether specific security or medical requirements were imposed

A complete publicly accessible copy of the letter has not yet been located.

Reference URL
https://www.documentcloud.org/documents/23889335-travis-scott-concert-final-police-report/
Astroworld Case Study · Section 7 · Part 9

Planning Records Submitted Shortly Before the Festival and Key Documentary Gaps

Washington Post — Plans Submitted Shortly Before Astroworld

Source type: Contemporary investigative journalism based on released planning/permit records

The Washington Post found that some Astroworld documentation was still being supplied or revised shortly before the festival.

It also reported that an updated detailed Astroworld security plan was not present in the City permit material it examined, while noting that the separate 56-page EOP contained more extensive security and emergency planning.

This is useful for distinguishing the event's operational planning records from the narrower documentation contained in the municipal permit file.

Full URL
https://www.washingtonpost.com/investigations/astroworld-permits-city-houston/2021/11/10/ffc962ea-41aa-11ec-9ea7-3eb2406a2e24_story.html

Key Documentary Gaps for Section 7

1
Astroworld Event Operations Plan Version 1.1

Including all appendices and unredacted decision-maker roles.

2
Any version between 0.1 and 1.1

With document-control history showing what changed.

3
HCSCC Event Approval Letter

The complete underlying approval record.

4
Written evidence identifying precisely which EOP version ASM Global/HCSCC approved

This is essential to resolving the document-control question.

5
Astroworld Festival Security Assessment — North America Festivals — 2021

The complete event-specific assessment.

6
The complete 219-page Live Nation safety/security policy package

Supplied to HPD under Bates numbers recorded in the investigation.

7
The original HFD Astroworld Event Action Plan

Rather than only the HPD transcription or summary.

8
Original ICS-202, ICS-203, ICS-204, ICS-205/205A and ICS-206 files

Needed for direct command, communications and medical-plan analysis.

9
The complete private ParaDocs medical plan and contract

Needed to establish the private medical provider's planned responsibilities.

10
Security deployment plans showing actual numbers, posts and supervisor responsibilities

Required to test planned versus actual security deployment.

11
Event Control radio plan and complete radio-channel matrix

Needed for communications and interoperability analysis.

12
Command-post layouts and personnel lists

To establish who was physically present in each command location.

13
Briefing packs and evidence of what security personnel were actually briefed on

Written planning is not equivalent to communicated operational knowledge.

14
Any formal crowd risk assessment separate from the EOP

Particularly any specialist assessment dealing with dense standing audiences.

15
Documented calculations or assessments dealing with front-of-stage density, barrier geometry, audience distribution or maximum safe population within individual crowd pens

This is a major priority for the subsequent site-design analysis.

Astroworld Case Study · Section 7 · Part 10

What Section 7 Establishes

There was a substantial planning architecture

The planning evidence is more complex than simply saying Astroworld had either a “good plan” or “no plan”.

There was a substantial planning architecture incorporating security, emergency response, unified command, medical response, MCI procedures, evacuation and show interruption.

The principal public EOP was comparatively weak on high-density crowd risk

At the same time, the principal public EOP gives detailed treatment to threats such as active shooters, suspicious packages, severe weather and civil disturbance while providing comparatively little specific treatment of:

standing-crowd density, crowd compression, crowd surge, progressive crowd pressure or the monitoring of individual front-of-stage audience compartments.

The distinction between prevention and consequence management is important

The planning system contained substantial procedures for responding to severe incidents once they existed.

Mass-casualty procedures, triage, hospital notification, ambulance staging, Incident Command, evacuation, show-power interruption and emergency announcements were all contemplated.

The documentary gap is more pronounced in relation to the early identification and control of the crowd conditions capable of creating multiple simultaneous casualties.

There were multiple parallel command and planning systems

The ScoreMore/festival EOP was not the only planning framework.

HFD had its own Event Action Plan, Incident Command structure, communications plan and medical-support arrangements.

Live Nation also held a substantial body of corporate safety documentation and an event-specific security assessment.

The eventual analysis must therefore examine how these systems interfaced, not merely assess each document in isolation.

There is a major document-control question

The public copy is Version 0.1.

Litigation records identify a Version 1.1.

The venue-side organisation reportedly questioned whether the 56-page public version was final.

A separate HCSCC Event Approval Letter also existed.

Until those records are recovered, it remains uncertain exactly which plan was final, which version was approved and which operational roles were named in the unredacted documents.

Written procedures create testable operational questions

The EOP established escalation thresholds, incident classifications, evacuation authority and show-power-shunt authority.

Those written requirements provide a benchmark against which the live evidence can later be tested.

The existence of a procedure does not demonstrate that it was followed, but it allows the study to ask much more precise questions about when information was received, by whom, how it was classified and what action followed.

Section 8 — Event Site Design, Barrier Configuration and Crowd Geometry can now move from the written plan to the physical environment in which the crowd was actually placed, with particular attention to the main-stage audience area and its four-sided / three-sided barrier compartments.
Astroworld Case Study · Section 8 · Part 1

Event Site Design, Barrier Configuration and Crowd Geometry

This section is central to understanding Astroworld because the fatal incident was not distributed evenly across the festival site.

The evidence increasingly points to the interaction between site capacity, audience distribution, stage programming, internal barricades and the ability—or inability—to regulate entry into individual audience compartments.

There are several different descriptions of the main-stage barrier arrangement in the evidence.

Contemporary reporting commonly describes four audience quadrants, Houston Landing describes T-shaped barricades, while an HPD interview records a member of Travis Scott's team referring to the “cross” design.

These descriptions appear to concern the same broad system of internal barriers and access corridors, but the terminology should not be treated as interchangeable until the final CAD plan itself is examined.

Astroworld 2021 Event Site Plan — Version 1.38

Source type: Primary planning document identified in civil-litigation evidence

One of the most important documents identified so far is:

Astroworld 2021 Event Site Plan, Version 1.38

Document reference: REG_ASTROWORLD_000262.

The existence and precise version number are confirmed in a March 2024 summary-judgment filing. The filing identifies the plan as Exhibit 14 and states that the festival consisted of two performance stages: Stage 1/Main Stage and Stage 2.

The Site Plan is more important for this part of the study than the simplified map contained in the public Event Operations Plan because it appears to have been the detailed operational/CAD plan used during the later stages of event planning.

The complete Exhibit 14 does not appear to be incorporated into the publicly available 67-page motion itself. Obtaining the original plan at full resolution is therefore a major research priority.

Full URL
https://dallasexpress.com/wp-content/uploads/2024/04/Travis-Scott-motion-for-summary-judgment.pdf

Planning for Movement from Stage 2 to Stage 1

Source type: Civil-litigation evidence — party filing based on depositions and exhibits

The 2024 filing contains important evidence concerning how the site was changed before Astroworld.

The proposal was for Travis Scott to be the only performer on Stage 1 on 5 November, while the remaining performances took place on Stage 2 beforehand.

According to the filing, planners explicitly discussed concern about a possible large-scale movement—or what witnesses termed a potential “stampede”—when the Stage 2 audience transferred to Stage 1.

Changes reportedly made in response included:

Removing rides, games, activations and landscaping
Substantially widening the route between stages
Reorientating Stage 2
Relocating the VIP area
Creating additional Stage 2 exits
Opening an additional route around Lantern Point

A third stage was also considered but ultimately not adopted.

This evidence is significant because audience migration between stages was recognised as a foreseeable planning issue before the festival.

However, the filing represents the position advanced by the Scott defendants and should not be treated as an independent finding that the measures ultimately proved adequate.

Astroworld Case Study · Section 8 · Part 2

Houston Police Department — Main-Stage Barrier Design

Source type: Primary police investigation

The HPD investigation contains an important interview concerning the physical design.

During the investigation, David Stromberg stated that planning for the stage and site had been taking place with Live Nation and the venue for more than a year.

He identified BWG as the infrastructure/planning contractor and said that the company worked with the venue and Houston fire officials in relation to the event design.

According to his account, decisions concerning barricade placement and capacity were made by those responsible for the site rather than by Travis Scott's personal team.

Most significantly, Stromberg recalled asking during planning whether there were enough barricades.

He said he was told that the configuration had been designed to improve security mobility and facilitate pulling people over barriers if necessary.

A “cross” design in the middle was intended to assist access to different sides of the audience.

This is valuable evidence of the stated design intention behind the internal barricades.

It does not demonstrate that the resulting configuration achieved those objectives under live crowd conditions.

Official HPD report
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf
Alternative public copy
https://www.houstonpress.com/wp-content/uploads/2023/07/astroworld_redacted_final.pdf.pdf
Astroworld Case Study · Section 8 · Part 3

Pre-Event Concern About Main-Stage Capacity

Houston Landing — “No way we are going to fit 50k”

Source type: Investigative journalism based on subsequently filed court records and expert reports

This March 2024 investigation substantially expands the documentary record relating to the site's design.

Ten days before Astroworld, Safety and Risk Director Seyth Boardman wrote to operations director Emily Ockenden expressing concern about whether 50,000 people could fit in front of the main stage, specifically mentioning the trees within the viewing area.

The reporting also identifies communications from 27 October between Ockenden and Kathryn Paraskevas, who was preparing the CAD site plan.

Ockenden asked for the plan to demonstrate capacity for 40,000 at Stage 2 and 50,000 at Stage 1.

Paraskevas replied that the Stage 1 calculation had reached approximately 40,105 and that she was struggling to identify space for another 10,000 people.

By 29 October, the plan reportedly represented: 44,000 General Admission + 3,500 VIP

This is one of the most important planning records yet identified.

Full URL
https://www.houstonlanding.org/astroworld-planners-foresaw-crowding-before-deadly-festival-no-way-we-are-going-to-fit-50k/

The T-Shaped Barricade System

Houston Landing reports that Live Nation/Scoremore contractors developed T-shaped internal barricades dividing the Stage 1 audience into four principal sections.

Their stated intention was to reduce crowd pressure while creating routes through which security and emergency responders could access the audience.

Dividing a large standing audience into compartments can be a legitimate crowd-management technique.

The critical question is not simply whether secondary barriers existed, but whether each resulting compartment had:

Appropriate safe capacity
Controlled admission
Adequate exits
Density monitoring
Ability to stop further inflow
Effective emergency access

Plaintiffs' experts later argued that these issues had not been adequately resolved.

Those opinions remain expert evidence produced for civil litigation, rather than findings of an independent public inquiry.

Astroworld Case Study · Section 8 · Part 4

Washington Post Reconstruction — Four Audience Quadrants

Source type: Major forensic-style journalistic reconstruction

The Washington Post performed one of the most detailed independent spatial reconstructions of the incident, combining geolocated video, witness evidence and crowd-science analysis.

It found that the main-stage standing audience was divided into north, south, east and west quadrants by metal barriers.

The barriers also created narrow corridors through the audience that could be used by security and medical personnel.

North
South
East
West

The south quadrant became particularly significant.

The Post found that it was bounded by rigid barriers on three sides and that a large proportion of the serious casualties were concentrated within this area.

Its reconstruction includes the main stage, four audience sectors, internal barrier lines, Stage 2, principal movement toward Stage 1, casualty locations and the production/platform area.

Full URL
https://www.washingtonpost.com/investigations/interactive/2021/what-happened-astroworld-travis-scott/

Concentration of Fatal Casualties

The Post initially located at least seven of the ten people who died within the same relatively small area of the south quadrant.

Subsequent reporting established that Bharti Shahani was also within that area, increasing the independently identified total to at least eight.

Independently identified in the same general south-quadrant area: At least 8 of 10 fatalities

This concentration is important because the forensic evidence established that the deaths resulted from compression asphyxia.

It therefore strengthens the need to examine physical conditions within that particular compartment rather than relying on overall attendance density across the entire festival site.

Fatality reconstruction URL
https://www.washingtonpost.com/investigations/2021/12/16/astroworld-deaths-compression-asphyxia-autopsies/

Estimated Density Within the South Quadrant

Researchers working with the Washington Post analysed video footage and estimated that parts of the south quadrant provided as little as 1.85 square feet per person.

Equivalent simple reciprocal density: ≈ 5.8 persons/m²

This equates to approximately 0.172 m² per person.

The researchers cautioned that the true density could have been greater because darkness, smoke and restricted visibility made counting difficult.

The figure should therefore be described as an estimated local density derived from video analysis, not an official measured density applying to the whole quadrant.

Astroworld Case Study · Section 8 · Part 5

Four Pens, Escape Opportunity and Audience Migration

Houston Chronicle — Four Pens and Limited Escape Opportunity

Source type: Long-form investigative reconstruction

The Houston Chronicle independently examined the main-stage arrangement and described four audience pens, each surrounded by barriers on three sides and separated by two narrow access routes used by security and emergency personnel.

Some compartments were estimated to extend approximately 100 feet from their open entrance to the furthest barricade.

The importance of this geometry is that people entering the open end could continue moving inward without necessarily being able to observe the crowd conditions at the closed extremity of the compartment.

Experts consulted by the Chronicle argued that additional pressure-relief exits along the barrier system could have provided greater opportunity for customers to escape increasing density.

That is expert interpretation rather than an official investigative conclusion.

Full URL
https://www.houstonchronicle.com/projects/2021/astroworld-no-escape-plan/

Audience Migration from Stage 2

Source type: Video reconstruction and eyewitness evidence

The spatial problem cannot be considered independently of the performance schedule.

The Stage 1 viewing area had already been filling for approximately three hours before Travis Scott appeared.

Around 8:30 p.m., the final Stage 2 performance by SZA ended and another audience began moving toward the main stage.

Witnesses and video reviewed by the Post indicate particularly substantial movement towards the south-side / house-left portion of the Stage 1 audience area because it was the most natural route from Stage 2.

This creates an important distinction:

The overall Stage 1 viewing area may have contained theoretical spare space while one individual compartment was already experiencing dangerous local loading.

That issue becomes especially relevant to the later expert reports.

Astroworld Case Study · Section 8 · Part 6

Civil-Litigation Crowd and Capacity Expert Evidence

Darrell Darnell — Astroworld Report

Source type: Plaintiff-retained expert report filed in civil litigation

Darrell Darnell, a former Washington, D.C. emergency-management director, was retained by plaintiffs in the Astroworld litigation.

His report argues that organisers considered the overall Stage 1 viewing capacity without adequately determining safe capacities for each of the individual compartments created by the barricade arrangement.

That is a particularly important proposition because once barriers divide an audience into independent areas, total available area alone is no longer sufficient to establish whether any individual area is safe.

The report is evidence submitted on behalf of litigants.

Its conclusions should therefore be attributed to Darnell rather than treated as judicial findings.

DocumentCloud record
https://www.documentcloud.org/documents/24485395-astroworld-report-by-darrell-darnell

Dr G. Keith Still — Astroworld Expert Report

Source type: Plaintiff-retained specialist crowd-science report

Dr G. Keith Still's report is one of the most technically relevant documents for this section.

According to the publicly reported conclusions, Still challenged the capacity methodology used during planning.

The planning calculations reportedly assumed approximately five square feet per person.

Still argued that the applicable calculation should instead have allowed seven square feet per person.

On that basis, his report calculated Stage 1 capacity closer to: 32,000 GA + 2,500 VIP rather than the represented 44,000 + 3,500.

This is a contested expert interpretation produced for plaintiffs.

It should not be converted into an unqualified statement that the venue's lawful capacity was definitively 34,500.

The defence expert evidence was not publicly available when Houston Landing published its investigation.

DocumentCloud record
https://www.documentcloud.org/documents/24485401-keith-still-astroworld-report
Direct PDF
https://s3.documentcloud.org/documents/24485401/keith-still-astroworld-report.pdf
Astroworld Case Study · Section 8 · Part 7

Trees, Sightlines and Practically Usable Audience Space

The site contained mature trees around portions of the Stage 1 audience area.

Boardman's pre-event concern specifically referenced those trees when questioning whether 50,000 people could fit in front of Stage 1.

This matters because gross plan area and practically usable audience area are not necessarily the same thing.

Customers generally move towards locations providing usable sightlines rather than distributing themselves evenly across every theoretically available square foot.

Houston Landing reports that McSwain Engineering calculated that, if the area outside a second line of trees was excluded as practically unattractive viewing space, the general-admission viewing area could accommodate significantly fewer people under the methodology applied by the plaintiffs' experts.

Again, this is plaintiff expert analysis and should be presented as such.

McSwain Engineering Astroworld Report

Source type: Plaintiff-retained engineering analysis

McSwain Engineering examined the physical layout and usable audience area.

The report appears particularly useful because it addresses physical obstructions and sightline-driven audience behaviour, rather than treating every part of the mapped area as equally attractive or usable.

That distinction may help explain why a site that appeared to offer a relatively large gross footprint nevertheless developed extreme local crowd concentration.

DocumentCloud record
https://www.documentcloud.org/documents/24485398-astroworld-report-by-mcswain-engineering
Supporting investigation
https://www.houstonlanding.org/astroworld-planners-foresaw-crowding-before-deadly-festival-no-way-we-are-going-to-fit-50k/

Larry Perkins Crowd-Management Expert Report

Source type: Plaintiff-retained expert report

Crowd-management specialist Larry Perkins also prepared a report for plaintiffs.

Houston Landing reports that Perkins considered the shortcomings in the site plan sufficiently apparent that, in his opinion, SMG/NRG Park should have identified them during its review of the event arrangements.

The Houston Chronicle separately reports that Perkins criticised planning, ingress and crowd-flow management and alleged that the festival did not meet appropriate industry crowd-management standards.

These remain expert allegations rather than judicial conclusions.

DocumentCloud record
https://www.documentcloud.org/documents/24485389-astroworld-report-by-larry-perkins
Astroworld Case Study · Section 8 · Part 8

Production Infrastructure, Barrier Condition and Scene Reconstruction

Production Camera Crane Within the Crowd Area

Source type: Primary HPD witness evidence

The HPD investigation contains useful evidence about production infrastructure positioned inside the audience.

A camera crane was located approximately 50 feet into the crowd area.

Witness evidence indicates that the space immediately associated with the crane and its barricades was intended to remain clear for production purposes.

As conditions deteriorated, people were being lifted over or crossing the surrounding barriers, and CPR was eventually being undertaken close to or beneath the crane equipment.

Camera personnel communicated increasingly serious conditions back to the production trailer.

Geometry
Production compounds, camera towers and corridors affect the space physically available to a crowd.
Observation
Elevated production positions may provide views unavailable to personnel standing at ground level.
HPD report
https://www.houstonpress.com/wp-content/uploads/2023/07/astroworld_redacted_final.pdf.pdf

Alleged Barricade Failure

Source type: Primary HPD witness evidence

The HPD report also contains evidence that a report of a failing or failed barricade was sufficiently concerning to prompt senior emergency personnel to move towards the main medical facility because they believed barrier failure could indicate serious injuries within the audience.

The evidence requires further examination before determining:

which particular barrier was involved; whether it structurally failed, moved, buckled or was simply reported as failing; the exact time; whether it was part of the principal Stage 1 cross-barrier system; and who received the report.

This should therefore remain an open evidential question rather than being stated simply as “the barricades collapsed”.

HPD Forensic Mapping of the Scene

Source type: Primary police forensic evidence

Following the disaster, HPD SWAT small-unmanned-aircraft personnel conducted systematic aerial mapping of the Stage 1 scene.

The investigation records two AutoGrid flight plans and at least:

1,011 + 620 images 1,631 images across the two recorded aerial series.

The photographs covered the elevated main stage, surrounding front and rear areas and the ground-level spectator area.

This represents potentially one of the best primary datasets for reconstructing the as-built barrier geometry after the incident, rather than relying solely upon pre-event CAD plans.

The full image set does not appear to have been published with the redacted HPD report.

Official investigation URL
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf
Astroworld Case Study · Section 8 · Part 9

Prior Barrier Warning and Governmental Scrutiny

2019 Astroworld — Relevant Prior Barrier Warning

Source type: Subsequently disclosed after-action records

One particularly important discovery from later civil records concerns the 2019 Astroworld after-action meeting.

Houston Landing reports minutes recording HPD Executive Assistant Chief Larry Satterwhite's concern about children pressed against the Stage barricade during the 2019 festival.

The minutes reportedly recorded concern about:

crowd crush, people turning blue and the need for additional ways of reaching customers experiencing difficulty in the middle of the audience.

This is significant for Section 8 because the 2021 cross-barrier arrangement appears, at least in part, to have been intended to improve internal security and emergency access.

That does not establish whether the 2021 design was a direct response to the 2019 recommendation, but it establishes an important line of enquiry.

Full URL
https://www.houstonlanding.org/astroworld-planners-foresaw-crowding-before-deadly-festival-no-way-we-are-going-to-fit-50k/

U.S. House Committee on Oversight — Barricade Concerns

Source type: Official Congressional correspondence

In December 2021, members of the U.S. House Committee on Oversight and Reform opened an inquiry into Live Nation's role in Astroworld.

The committee specifically noted reports that the placement of barricades made it difficult for some attendees to escape and referred to expert concerns about warning signs and event safety.

This is not an independent technical determination of the site design.

It does, however, confirm that barrier configuration had become an explicit subject of governmental scrutiny shortly after the incident.

Full URL
https://oversightdemocrats.house.gov/news/press-releases/maloney-comer-lead-members-in-launching-bipartisan-investigation-into-live
Astroworld Case Study · Section 8 · Part 10

Key Documentary Gaps for Section 8

1
Full-resolution Astroworld Event Site Plan v1.38 — REG_ASTROWORLD_000262

Including scale, revision history and CAD layers.

2
Earlier site-plan versions

Showing exactly when the cross/T barrier design was introduced.

3
Capacity calculations attached to every major revision

Needed to track how projected audience capacity changed with the design.

4
Emily Ockenden / Kathryn Paraskevas correspondence

Concerning Stage 1 capacity and the CAD planning process.

5
Approval record for the final barrier configuration

Showing who formally accepted or authorised the final design.

6
Barricade contractor engineering or supplier drawing

Needed to establish the intended physical system.

7
Exact barrier dimensions, types, gates and removable sections

Required for accurate geometry and emergency-access reconstruction.

8
Intended and actual capacity of each individual Stage 1 quadrant

This is central to compartment-level safety analysis.

9
Any system for counting customers entering or leaving each quadrant

Needed to establish whether compartment occupancy could actually be controlled.

10
Complete HPD 1,631-image aerial forensic photography set and AutoGrid reconstruction

Potentially the strongest post-incident evidence of as-built geometry.

11
Houston Forensic Science Center scene plans and measurements

Needed for independent measurement of the physical scene.

12
NRG CCTV and elevated camera footage

Showing density development within each quadrant.

13
Complete Video/Apple production feeds

Particularly Camera 6 and other elevated views.

14
Full plaintiff and defence crowd-engineering expert reports and exhibits

Needed for balanced comparison of the competing technical analyses.

15
Any Fire Marshal inspection drawing showing the as-built barricade configuration on 5 November

This would provide an important regulatory cross-check against the design drawings.

What Section 8 Establishes

The evidence shows that site geometry was being actively considered before Astroworld.

Planners recognised the challenge of moving tens of thousands of customers between stages, altered the site accordingly and deliberately introduced internal barricades intended to provide pressure management and emergency access.

The problem requiring deeper investigation is therefore not simply that “barriers were used”.

The more important question is whether the resulting four-compartment system was matched by compartment-level capacity control and density monitoring.

The strongest evidence currently suggests a mismatch between gross Stage 1 capacity calculations and the way the audience actually distributed itself.

The house-left/south section received a disproportionate inflow from Stage 2, was bounded on several sides by rigid barriers and became the location in which the fatal compression was concentrated.

This leads directly into Section 9 — Crowd Capacity, Attendance and Admission, where four figures need to be separated carefully:

ticketed attendance · persons actually on site · whole-site capacity · safe capacity of individual crowd compartments.
Astroworld Case Study · Section 9 · Part 1

Crowd Capacity, Attendance and Admission

Astroworld's attendance figures require careful separation because several different numbers appear throughout the evidence and they do not describe the same thing.

The strongest available evidence supports a festival-day ticket demand of approximately 50,000, but the final Live Nation scanner report subsequently given to Harris County recorded 37,858 scanned admissions.

At the same time, Houston Fire Department records indicated that several thousand people had bypassed screening or scanning during repeated perimeter breaches.

Separately, the event medical plan was built around an estimated 70,000 attendees, while detailed main-stage planning struggled to demonstrate sufficient viewing space for the expected audience.

tickets sold ≠ tickets scanned ≠ people physically present ≠ festival-site capacity ≠ main-stage capacity ≠ safe capacity of an individual crowd compartment

Those figures should remain separate throughout the study.

Measure Figure What the figure actually represents
Tickets sold / expected festival demand 50,000 Ticketed demand for the sold-out festival day.
Final recorded ticket scans 37,858 Live Nation scanner total subsequently reported by Harris County; not necessarily the number physically inside.
Estimated people bypassing checkpoints 3,000–5,000 HFD command-log estimate of people who had bypassed security/scanning; this does not prove all were unticketed.
ParaDocs medical-planning assumption 70,000 attendees Medical-resource planning estimate; not an occupancy permit or verified attendance figure.
Event attendance limit described by HFD Chief Samuel Peña 50,000 Operational attendance limit described after the incident.
Broad outdoor NRG Park capacity cited by Peña c.200,000 General fire-code potential of the much larger outdoor area, not safe main-stage viewing capacity.
Stage 1 planning calculation by 29 October 44,000 GA + 3,500 VIP = 47,500 Planned audience-area capacity shown by the later site-planning calculations.
Plaintiff expert Keith Still's alternative Stage 1 calculation 32,000 GA + 2,500 VIP = 34,500 Contested expert calculation using a different area-per-person methodology; not an official occupancy determination.

This table immediately exposes why statements such as “there were 55,000 people inside” require caution.

An estimate that 3,000–5,000 people bypassed scanning cannot simply be added to 50,000 tickets sold: some of those people may have held valid tickets but entered without having them scanned, while some ticket purchasers may never have entered.

The surviving evidence does not presently establish an exact final physical occupancy.

Astroworld Case Study · Section 9 · Part 2

Ticket Demand and Scanner Records

Houston Chronicle — No Escape Plan

Source type: Major investigative reconstruction

This remains one of the most useful sources for reconciling the different attendance numbers.

The Chronicle reports that 50,000 tickets had been sold, while Harris County later reported that the final Live Nation scanner data showed only 37,858 tickets scanned.

It also records the Fire Department estimate that between 3,000 and 5,000 people entered without normal scanning or screening during the numerous perimeter incidents.

The source is particularly important because it correctly highlights the resulting uncertainty: there is no simple verified total showing exactly how many people were physically within the Astroworld footprint at the critical time.

Full URL
https://www.houstonchronicle.com/projects/2021/astroworld-no-escape-plan/

Final Live Nation Scanner Figure — 37,858

Source type: Ticketing/venue record reported by Harris County

Final scanner total: 37,858

The 37,858 figure deserves particular weight because it originated from the event's ticket-scanning system rather than from an immediate crowd estimate.

The Houston Chronicle reports that Harris County subsequently obtained the Live Nation scanner figure and identified 37,858 scans against approximately 50,000 tickets sold.

However, a scanner count measures successful scanner transactions—not necessarily physical occupancy.

The difference of approximately 12,000 between tickets sold and scanned could potentially include several categories:

Valid ticket holders who bypassed scanning
People admitted through other authorised processes
Complimentary/VIP credentials handled differently
Ticket holders who never attended
Duplicate or incomplete scanning records
People entering without tickets

The public evidence currently available does not allow those groups to be separated reliably.

That means 37,858 should not be presented as the final Astroworld attendance, but it is probably the strongest surviving numerical measure of controlled admission.

Early 34,000 Scanner Figure

Los Angeles Times — Contemporary reporting based on interviews with HFD Chief Samuel Peña

Immediately after the disaster, Peña said investigators were seeking a complete ticket manifest.

At that stage he referred to approximately 34,000 tickets having been scanned, while noting that VIP, complimentary and other admissions also had to be considered.

The later 37,858 final scanner report should therefore supersede the early 34,000 figure when describing the completed ticketing record.

This is a useful example of why contemporary figures should not automatically be treated as final.

The article also reports Peña describing 50,000 as the event attendance limit, despite the much larger theoretical capacity of the wider outdoor NRG Park property.

Full URL
https://www.latimes.com/world-nation/story/2021-11-09/astroworld-organizers-had-extensive-medical-security-plans-ddid-they-follow-them
Astroworld Case Study · Section 9 · Part 3

ParaDocs — Astroworld Medical Operations Plan 2021

Source type: Primary operational planning document

The ParaDocs medical plan contains one of the most striking conflicting planning figures.

Under General Event Information, it records:

Capacity — Estimated 70,000 Attendees

The plan covers NRG Park for 5–6 November 2021 and was used to determine medical staffing and resource provision.

This figure should not be interpreted as an approved event capacity.

It appears in a medical-planning document and is specifically described as estimated.

Why was medical provision being designed around 70,000 attendees when the publicly described event limit and ticketed audience were approximately 50,000?

Possible explanations should not be invented.

The difference needs to be resolved through producer correspondence, medical-contract documentation and plan revision records.

Full URL
https://ca-times.brightspotcdn.com/64/58/47ca5aed47558c5d028b5f2ca71d/aw21-medical-plan.pdf
Astroworld Case Study · Section 9 · Part 4

Perimeter Breaches and Loss of Reliable Admission Control

ABC13 — Houston Fire Department Command Logs

Source type: Contemporary reporting based directly on HFD Incident Command logs

These records are critical for admission control.

ABC13's examination of the HFD logs found repeated failures at the external security perimeter throughout the day.

Estimated people bypassing normal checkpoints: 3,000–5,000

The records also document problems beginning before the venue formally opened and continuing through repeated gate and fence incidents during the day.

This evidence is stronger than retrospectively describing Astroworld simply as having “too many people”, because it establishes a specific operational problem:

the admission system lost reliable control over whether every person entering had passed through the intended ticketing and security processes.

It does not, however, establish that every person bypassing the checkpoint lacked a ticket.

Full URL
https://abc13.com/post/astroworld-2021-festival-houston-fire-department-hfd-response/11226357/

Early-Morning Gate Control Problems

Houston Chronicle — Detailed contemporary timeline

Crowds had formed before opening.

Between approximately 9:15 and 10:00 a.m., people repeatedly breached checkpoints, including bypassing the COVID-testing area.

When the venue gates opened at approximately 10 a.m., further crowd movement damaged gates and overwhelmed portions of the entrance arrangements.

Further attempts to enter through fences, barriers and unauthorised routes continued during the day.

This is significant because the Astroworld EOP itself stated that successful crowd management needed to begin “from the minute the doors open.”

The admission difficulties were therefore not merely unrelated incidents at the perimeter; they affected one of the primary mechanisms used to establish who was inside the site.

Full URL
https://www.houstonchronicle.com/projects/2021/travis-scott-astroworld-timeline-houston-tragedy/

VIP Entrance Breach

Source type: Contemporary video and investigative reporting

One of the best documented admission failures occurred at approximately 2 p.m., when a large crowd overwhelmed the VIP entrance.

The Houston Chronicle's reconstruction describes more than 200 people entering during a short video sequence alone.

The importance of the episode is broader than the numerical increase in attendance.

People bypassing a controlled entrance potentially bypassed:

Ticket scanning
Security search
Prohibited-item controls
Counting mechanisms
Wristband / credential checks

The breach therefore affected the reliability of both security assurance and occupancy data.

Full URL
https://www.houstonchronicle.com/projects/2021/astroworld-no-escape-plan/

Repeated Perimeter Breaches Throughout the Day

Houston Chronicle — reporting based upon primary Fire Department logs

The HFD activity logs record repeated attempted or successful breaches throughout the afternoon, including people dismantling barricades, scaling fences and reportedly using bolt cutters to access restricted areas.

A site may have an appropriate ticket-sales ceiling yet still lose control of physical occupancy if the perimeter and scanning operation cannot reliably account for entrants.

Conversely, repeated breaches do not automatically establish that the festival exceeded its overall numerical attendance limit.

Both propositions need to remain separate.

Full URL
https://www.houstonchronicle.com/news/houston-texas/astroworld-fest-tragedy/article/firefighter-logs-astroworld-tragedy-minute-look-tx-16615779.php
Astroworld Case Study · Section 9 · Part 5

Overall NRG Park Capacity Versus Astroworld Capacity

Houston Chronicle / PolitiFact — Astroworld Capacity Fact Check

Following the disaster, claims circulated that Astroworld had exceeded the capacity of NRG Park by tens of thousands.

That framing was misleading.

≈ 200,000 Broad theoretical outdoor NRG Park fire-code capacity described by HFD Chief Peña
≈ 50,000 Astroworld festival attendance limit described by Houston officials

The 200,000 figure is therefore not useful for assessing the safety of the Travis Scott audience area.

A 350-acre property can theoretically accommodate a very large population while a relatively small compartment within it simultaneously becomes dangerously overcrowded.

That distinction is fundamental to the Astroworld case.

Full URL
https://www.houstonchronicle.com/politics/texas/politifact/article/fact-check-astroworld-fest-capacity-travis-scott-16615062.php
Astroworld Case Study · Section 9 · Part 6

Stage 1 — Requirement to Accommodate the Festival Audience

Houston Landing — “No way we are going to fit 50k”

Source type: Investigative journalism based on civil-discovery documents and expert reports

The detailed planning correspondence obtained in the civil litigation provides perhaps the strongest evidence concerning where organisers expected the audience to go.

On 27 October 2021, operations director Emily Ockenden told CAD planner Kathryn Paraskevas:

“I need to show 40k at stage 2 and 50 at stage 1.”

The reason was apparent: Travis Scott was the sole final performer at Stage 1 and planners anticipated that most or potentially all ticketed attendees would migrate there.

Paraskevas initially calculated approximately 40,105 in Stage 1 and told Ockenden she did not believe she could find another 10,000 spaces even after bringing the calculated audience close to the barricades.

This is exceptionally important evidence because it demonstrates that main-stage capacity was actively recognised as a planning problem before the festival.

Full URL
https://www.houstonlanding.org/astroworld-planners-foresaw-crowding-before-deadly-festival-no-way-we-are-going-to-fit-50k/

Final Pre-Event Stage 1 Capacity Calculation

By 29 October, the planning documents examined by Houston Landing showed capacity represented as:

44,000 General Admission
3,500 VIP
47,500 Total

This creates an immediate numerical question.

The planning brief sought space for 50,000 at Stage 1, yet the identified drawing provided only 47,500 places even under the organisers' own capacity methodology.

This does not by itself establish that exactly 50,000 people attempted to enter the Stage 1 area.

It does establish that the planning record was grappling with a recognised mismatch between expected demand and mapped viewing capacity.

Astroworld Case Study · Section 9 · Part 7

Keith Still — Alternative Main-Stage Capacity Analysis

Source type: Plaintiff-retained crowd-safety expert evidence

Professor G. Keith Still subsequently challenged the methodology used by Astroworld planners.

The planners' calculations reportedly used approximately five square feet per person.

Still argued that the relevant calculation should have provided approximately seven square feet per person.

Organiser planning figure 47,500 44,000 GA + 3,500 VIP
Still's alternative calculation 34,500 32,000 GA + 2,500 VIP

This must remain properly qualified.

Still's report was prepared as expert evidence for plaintiffs in civil litigation.

It is not an official governmental capacity determination and should not be described as a judicial finding.

The underlying expert report nevertheless deserves inclusion within the study because it contains detailed crowd-science analysis of the site design.

Referenced report
https://www.documentcloud.org/documents/24485401-keith-still-astroworld-report
Supporting investigation
https://www.houstonlanding.org/astroworld-planners-foresaw-crowding-before-deadly-festival-no-way-we-are-going-to-fit-50k/

Whole-Stage Capacity Versus Compartment Capacity

This is probably the single most important capacity issue in the case.

Even if one accepted the 47,500 Stage 1 calculation, that figure described the overall viewing area.

Section 8 established that internal barriers divided the audience into distinct areas.

“How many people can fit in front of Stage 1?”

changes to:

“How many people can safely occupy each individual compartment, and how is that number controlled?”

The public evidence reviewed so far has not produced a contemporaneous document assigning a specific safe capacity to each individual Stage 1 quadrant or demonstrating a live counting system regulating admission to each compartment.

That absence is significant enough to make the underlying site-plan calculations, security deployment and crowd-monitoring documentation high-priority retrieval items.

Houston Landing reports that plaintiff experts similarly criticised the planning for focusing on overall viewing-area capacity rather than the resulting individual spaces.

Astroworld Case Study · Section 9 · Part 8

Capacity Does Not Equal Density

Astroworld also illustrates why capacity and density cannot be used interchangeably.

Imagine 40,000 people within a space theoretically calculated for 47,500.

That does not mean every location within it is operating below capacity.

People concentrate unevenly because of:

Stage sightlines
Performer popularity
Access routes
Barriers
VIP structures
Trees and physical obstructions
Arrival direction
Crowd preference for proximity to the performer

At Astroworld, the migration from Stage 2 brought a significant inflow toward one portion of Stage 1, while parts of the wider site remained comparatively less occupied.

The Washington Post's subsequent video reconstruction estimated extremely high local density in the fatal area despite the festival not being proven to have exceeded the overall NRG Park attendance limit.

This is why an argument based solely on “the event was below site capacity” would not answer the crowd-safety question.

The 70,000 / 50,000 / 47,500 Planning Discrepancy

There are therefore at least three substantially different pre-event capacity assumptions within the material:

70,000 ParaDocs estimated attendance for medical planning
50,000 Ticketed / operational festival demand
47,500 Mapped Stage 1 audience capacity identified in late-October planning

That does not necessarily mean one document was fraudulent or deliberately inaccurate.

Different planning functions sometimes use conservative or contingency numbers.

But for a major festival, the difference requires an explanation because security, medical, sanitation, egress and crowd-management provision should ultimately be tied to a clearly understood planning population.

One of the documents still needed is therefore a single approved capacity statement identifying the authoritative planning population for each element of the event.

Astroworld Case Study · Section 9 · Part 9

What We Should Not State

At this point several common statements about Astroworld should be avoided because the available evidence does not support them with sufficient precision.

“55,000 people attended.”

Possible, but not conclusively established. It commonly results from adding estimated unauthorised entries to 50,000 tickets sold.

“5,000 people without tickets broke in.”

The records indicate several thousand people bypassed security/scanning; they do not establish that every one lacked a valid ticket.

“The festival was 5,000 over capacity.”

Not demonstrated by the available evidence.

“NRG Park's capacity was 50,000.”

Incorrect. The broader complex could accommodate substantially more; approximately 50,000 was the Astroworld attendance limit described by Houston officials.

“The main stage was officially limited to 34,500.”

Also incorrect. That is an expert's later alternative calculation, not an official pre-event limit.

“Because fewer than 50,000 were present, overcrowding could not have occurred.”

This ignores local distribution and the capacities of the individual crowd compartments.

Those distinctions will materially strengthen the accuracy of the final case study.

Important Source — Harris County Sports and Convention Corporation

Source type: Official venue-governance body

The HCSCC managed the county-owned NRG Park property through its venue arrangements and is therefore a primary source for several records still needed, including ticket-scanner reports, contractual attendance figures and board material.

Its website also confirms that its records are subject to the Texas Public Information Act, making it an important route for obtaining records not currently indexed online.

Full URL
https://www.nrgpark.com/hcscc/
Astroworld Case Study · Section 9 · Part 10

Key Documentary Gaps for Section 9

1
Complete Live Nation/Ticketmaster scanner report

Showing the final 37,858 figure.

2
Time-series scanner totals throughout 5 November

Needed to reconstruct admission volume over the course of the day rather than relying only on the final figure.

3
Credential-type breakdown

General admission, VIP, complimentary, employee, artist/guest and other credentials.

4
Exact ticket inventory

Tickets sold, issued, refunded, cancelled and unused.

5
Any post-event reconciliation between ticketing data and physical attendance

This may provide the best available attempt to establish the actual site population.

6
Underlying HFD record estimating 3,000–5,000 unscanned entrants

The primary log should be used instead of relying permanently on secondary reporting.

7
CCTV/video analysis quantifying actual perimeter breaches

Needed to move beyond broad operational estimates.

8
Exact number of individuals removed or intercepted following unauthorised entry

This would affect any attempt to calculate net occupancy.

9
Astroworld Event Site Plan v1.38 with capacity layers

Needed to connect the capacity figures with the physical design.

10
Earlier CAD revisions

Showing the evolution from approximately 40,105 to 47,500 Stage 1 capacity.

11
Calculations supporting the five-square-foot-per-person planning basis

Needed to understand the methodology rather than merely the resulting number.

12
Any Fire Marshal or venue review of the Stage 1 capacity calculation

This would show whether the methodology received independent scrutiny.

13
A formal Stage 1 capacity certificate or approval, if one existed

This would distinguish planning assumptions from formally accepted capacity.

14
Capacity calculations for each of the four Stage 1 audience compartments

This is one of the most important missing records in the entire case study.

15
Evidence of any live system for counting people entering those compartments

Needed to determine whether local capacity could actually be controlled operationally.

16
Correspondence explaining why the medical plan used 70,000

The discrepancy should be explained from the original planning record rather than inferred.

17
The authoritative event-planning document defining the 50,000 figure

Specifically whether it represented tickets sold, maximum attendance or simultaneous occupancy.

What Section 9 Establishes

The evidence does not presently demonstrate that the disaster occurred because the whole Astroworld festival exceeded an overall 50,000-person limit.

The more compelling capacity issue is considerably more localised.

Astroworld had demand approaching 50,000 customers for a final performance that planners expected virtually the entire festival audience to want to see.

Internal barriers divided the main-stage audience into separate compartments.

Pre-event correspondence shows planners struggling to demonstrate enough space for that audience, while the final identified Stage 1 plan represented only 47,500 places even under the organisers' own calculation.

At the same time, repeated breaches compromised the reliability of admission data, leaving uncertainty over exactly how many people were physically on the site.

The crucial operational question therefore becomes:

not simply how many people entered Astroworld, but whether organisers knew how many people were entering each critical crowd space and possessed a mechanism to stop that inflow before local density became dangerous.
Astroworld Case Study · Section 10 · Part 1

Security Provision and Crowd-Management Arrangements

Astroworld had a very substantial security presence on paper. The more difficult question is whether the available personnel had the correct competence, deployment, supervision, information and authority for the developing crowd conditions.

The evidence reveals an important distinction between security and crowd management.

The Event Operations Plan devotes considerable detail to perimeter security, ticket checks, weapons, searches, access control and incident response.

It says that security would be deployed at the front and rear of stages and throughout the venue.

However, the publicly available plan does not specify numerical staffing levels, compartment capacities, crowd-density thresholds or a dedicated system for monitoring progressive crowd compression.

Astroworld 2021 Event Operations Plan — Security Plan

Source type: Primary event-planning document

Part 2 of the Astroworld EOP is the principal publicly available statement of the festival's planned security operation.

It says a security-management structure had been created to provide direct communication between festival management and the various security vendors.

Security personnel were intended to cover:

Roadways and access points
Emergency egress routes
Exterior fence lines
Production areas
Front and rear of stages
VIP and activation areas
Roaming positions across the interior and exterior

The public copy contains a table identifying the security management hierarchy and another identifying security vendors, but the names have been redacted.

Importantly, the section describes where security should exist, but it does not provide a detailed numerical deployment showing how many personnel were to occupy each location.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Security Management Roles

The EOP allocates several distinct senior responsibilities.

Executive Producer

Oversaw festival administration and possessed authority to stop the show.

Festival Director

Managed festival operations and also possessed authority to stop the show.

Director of Risk & Safety

Directed security operations, developed and implemented security policy and held responsibility for festival safety and security.

Director of Security

Managed stage safety and security, coordinated security companies, facilitated emergency operations, led the Emergency Response Team and acted as Security AOD/festival emergency manager while on property.

The written plan therefore did not envisage a loose collection of independent contractors. It envisaged an identifiable management structure above them.

Astroworld Case Study · Section 10 · Part 2

Event Day Briefing and Physical Security

Astroworld EOP — Event Day Briefing

Source type: Primary event-planning document

The Event Security Director or nominee was supposed to produce an Event Day Briefing at the start of each festival day.

It was intended to communicate:

Event-specific information
Emergency assignments
Identity of the Security AOD
Contact information
Special considerations

The briefing was to be passed to department heads and the Emergency Response Team.

This creates one particularly important missing record:

the actual 5 November Event Day Briefing.

It could establish what senior personnel knew about anticipated crowd behaviour, previous Astroworld problems, likely stage migration, expected audience numbers, gate-rushing risks, front-of-stage arrangements and escalation procedures.

That briefing has not yet been located publicly.

Full URL
https://ca-times.brightspotcdn.com/bf/57/11bc2a094c9886f3407cc641e1e7/astroworld-2021-eop-1.pdf

Astroworld EOP — Physical Security

The EOP required a hard perimeter around the ticketed festival footprint using:

8-foot Harris fencing
Crowd-control barriers
Snow fencing
Concrete bollards

Within the venue, restricted areas were also to be separated using fencing and barriers.

Stage fronts were to use MOJO-style barricade.

The entrance arrangements included wristband scanning, walk-through metal detectors, visual checks, bag searches and potentially pat-down searches.

Search personnel were supposed to be trained and supervised.

These provisions demonstrate substantial emphasis on preventing unauthorised entry and prohibited items.

Astroworld Case Study · Section 10 · Part 3

The Security Staffing Numbers — An Important Conflict

There are several widely quoted staffing figures, but they should not be combined casually.

At the first post-incident briefing, Harris County Judge Lina Hidalgo stated that the 2021 operation included:

505 Event-security personnel
91 Armed private-security personnel
76 Houston Police Department officers

She contrasted these with 2019 figures of:

409 event-security personnel, 30 armed security personnel and 47 HPD officers.

At the same briefing, Houston officials also referred to:

528 HPD officers
≈ 755 Private-security personnel

These are clearly different accounting populations, rather than two straightforward competing totals.

Later, Police Chief Troy Finner said the security personnel records provided to investigators were insufficiently clear and described the documentation concerning private security staffing as problematic.

For the study, it would therefore be misleading simply to state:

“Astroworld had 1,283 security personnel.”

Houston Officials' Initial Security Staffing Statement

Source type: Contemporary official press briefing — transcript

The 6 November press briefing provides the earliest official explanation of the security resources.

Hidalgo gave the specific 505 + 91 + 76 breakdown, while Mayor Sylvester Turner and other officials discussed the much larger overall HPD and private-security operation.

It is valuable because it establishes what government officials believed immediately after the incident, but the later police investigation showed that the private-security staffing record was considerably less straightforward.

Full URL
https://transcripts.cnn.com/show/cnr/date/2021-11-06/segment/07
Astroworld Case Study · Section 10 · Part 4

HPD's Own Security Plan and Pre-Event Staffing Concerns

Houston Police Department — Supplement No. 0092

Source type: Primary police investigative record

A senior HPD account preserved in the final investigation says the department had concerns arising from previous Astroworld events and decided to supplement the normal private-security and off-duty-police arrangements with on-duty HPD resources.

HPD developed a separate security plan covering:

Vehicle ingress and egress
Pedestrian ingress and egress
Traffic posts
Crowd control
Mounted patrol
Tactical assets
Special Operations
Traffic Enforcement

HPD also worked with the venue on staging and ingress points.

This demonstrates that the public-policing operation and the promoter's private-security operation were related but not identical systems.

Official report URL
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf

Police Concern About Security Staffing Before the Festival

The same HPD account contains one of the most significant pre-event warning indicators.

22 October Venue-side concern about guest-to-staff ratio was already being expressed.
3 November HPD was still being told organisers did not have final numbers for extra-job officers or private security.
4 November The event agreement was amended to require additional security and medical personnel.

During planning, HPD understood that the venue was having difficulty obtaining sufficient extra-job police officers for the interior operation.

The venue increased the rate offered to officers in an attempt to recruit more personnel.

At the final planning meeting on 3 November 2021, HPD was still being told that the organisers did not have a final number for either available extra-job officers or private security.

The officer specifically records that this was concerning to HPD.

The evidence therefore establishes that staffing uncertainty existed 48 hours before the festival opened.

NRG Park / ASM Global Concern About the Guest-to-Staff Ratio

Houston Chronicle — No Escape Plan

NRG Park General Manager Mark Miller reportedly told the Harris County Sports & Convention Corporation board on 22 October 2021 that he had concerns about the event's “ratio of guests to staff.”

ASM Global was sufficiently concerned about staffing that the issue continued into the final days before Astroworld.

This corroborates the HPD evidence that security-resource questions had not been completely resolved well in advance of the event.

Full URL
https://www.houstonchronicle.com/projects/2021/astroworld-no-escape-plan/

4 November Contract Amendment

On 4 November 2021—the day before Astroworld opened—Harris County and ScoreMore amended the event agreement.

The amendment required the promoter to obtain additional:

security personnel and medical personnel.

Ordinarily, NRG Park's exclusive arrangements meant organisers used Contemporary Services Corporation (CSC) for event security.

The amendment apparently allowed ScoreMore to obtain supplemental personnel elsewhere because the existing provision was considered insufficient.

It remained unclear exactly which additional companies were ultimately hired and how the county verified that sufficient supplemental personnel had actually been delivered.

The original amendment should therefore be obtained for the study.

Astroworld Case Study · Section 10 · Part 5

Security Contractors and the Deployment Question

Contemporary Services Corporation — Principal Venue Security Provider

Source type: HPD investigative evidence and venue reporting

CSC was NRG Park's regular security contractor and was heavily involved in Astroworld.

The HPD investigation describes CSC as a company regularly employed at NRG and states that it worked with Apex Security and HPD to protect the perimeter fencing.

HPD also involved the Texas Department of Public Safety in investigating security companies including:

Contemporary Services Corporation
Apex Security
AJ Melino & Associates
Valle

This is a stronger basis for identifying the contractors than relying solely on names appearing as defendants in lawsuits.

HPD report
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf

Multiple Security Companies — Civil Litigation

Source type: Court pleadings — allegations, not findings

Civil filings identify a wider subcontracting structure including:

Contemporary Services Corporation
Apex Security
AJ Melino & Associates
Valle Security / Valle Services
State Patrol Services / SPS Security

One early complaint specifically alleged that CSC had been contracted to provide security and crowd-management services.

Another pleading identified CSC, Apex, SPS and Valle collectively as security defendants.

The presence of a company in litigation does not by itself establish its precise contractual duties.

The eventual study should therefore use the original contracts and deployment schedules wherever possible.

Full URL — Gutierrez complaint
https://www.courthousenews.com/wp-content/uploads/2021/11/noah-gutierrez-astroworld-lawsuit.pdf
Full URL — further pleading
https://www.houstonpress.com/wp-content/uploads/2021/11/2021.11.16_original_petition_astroworld__filestamped.pdf.pdf

Where Were the Security Companies Actually Deployed?

This question remains unresolved.

In later civil proceedings, lawyers representing CSC and Apex argued that their personnel were used principally at festival gates rather than in the main-stage area where the fatal compression occurred.

Plaintiffs disputed attempts to separate gate security from the broader crowd-control system.

That makes the actual post-by-post security deployment plan essential.

Knowing that 500 or 700 guards were “at Astroworld” tells us very little unless we know how many were:

Searching at gates
Protecting perimeter fencing
Working traffic
Guarding backstage
Protecting VIP areas
Working front-of-stage barriers
Monitoring internal crowd sectors
Supervising other personnel
Available as response teams
headcount is not deployment.
Astroworld Case Study · Section 10 · Part 6

Last-Minute Recruitment, Training and Licensing

AJ Melino & Associates — Samuel and Jackson Bush

Source type: Security-worker testimony reported contemporaneously; allegations were disputed matters

Samuel and Jackson Bush said they were recruited shortly before Astroworld by AJ Melino & Associates.

They alleged that the company did not check their credentials, conduct an appropriate background check or establish that both men held the necessary security licensing.

Samuel Bush said he did not hold the required licence.

They subsequently brought civil claims relating to their employment.

These accounts are important, but they should be presented as worker allegations, not established findings applying to every Astroworld security operative.

Full URL
https://www.houstonchronicle.com/news/houston-texas/astroworld-fest-tragedy/article/There-was-no-training-Astroworld-security-16642676.php

Bush Security-Worker Accounts — KPRC/Click2Houston

Source type: First-hand worker account

Jackson Bush described a lack of training and said personnel had not been familiarised with the site or clearly instructed on their posts.

He also described limited radio provision and communication between some security teams.

This evidence is useful because the written EOP envisaged structured supervision, briefing and radio-based coordination.

The issue is therefore not simply whether a written briefing procedure existed, but whether it reached temporary and subcontracted security workers.

Full URL
https://www.click2houston.com/news/local/2021/11/22/2-astroworld-security-guards-injured-during-travis-scott-concert-to-announce-lawsuit-attorney-says/

CSC Security Worker — Darius Williams

Source type: First-hand worker account reported contemporaneously

Darius Williams said he was recruited to work Astroworld for CSC shortly before the event and attended security training immediately before the festival.

He alleged that the Level II training was rushed and that personnel were assisted through the examination.

He said he ultimately left his Astroworld assignment because he considered the operation inadequately staffed and felt insufficiently prepared.

Again, this is one individual's account and does not prove that all CSC personnel had the same training experience.

Nevertheless, it is directly relevant because it can be tested against:

CSC training records
DPS licensing data
Guard rosters
Instructor records
Event briefing records
Full URL
https://www.tmz.com/2021/11/09/astroworld-security-guard-felt-unprepared-training-day-before-festival/

Texas DPS — Level II Security Training Requirements

Source type: Official regulatory guidance

Texas DPS guidance in force before Astroworld confirms that the Level II course and examination was required for non-commissioned security officers, commissioned security officers and personal-protection officers, subject to specified exemptions.

This provides an authoritative benchmark against which claims of hurried or absent security training can eventually be tested.

It does not mean that everyone wearing an event vest necessarily performed a function regulated as a licensed security officer; the precise employment function matters.

Training guidance
https://www.dps.texas.gov/section/private-security/training-and-continuing-education
Texas private-security legislation
https://tcss.legis.texas.gov/resources/oc/htm/oc.1702.htm
Astroworld Case Study · Section 10 · Part 7

Perimeter Control and Previous Astroworld Risk

Perimeter Control Failed Repeatedly

Security planning cannot be judged solely from the fatal main-stage period.

As established in Section 9, HFD and HPD records show that the festival perimeter experienced repeated breaches beginning around opening time.

The HPD/HFD timeline records incidents including:

Participants breaching a secondary checkpoint
Apex Security requesting assistance
Damaged venue fencing
Periods where officials recorded no control of participants
People jumping perimeter fences

These incidents absorbed police and security resources for much of the day.

perimeter integrity + admission processing + crowd movement + stage security + emergency response

The security operation was therefore dealing simultaneously with several competing demands long before the fatal crowd conditions developed.

HPD report
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf

Previous Problems Influenced Police Planning

HPD's later investigative account states that it intentionally increased the 2021 operation because of public-safety concerns associated with earlier events.

The plan used on-duty officers in addition to the normal private-security and extra-employment arrangement, with crowd-control, traffic, mounted and tactical resources included.

2021 was not being planned as an ordinary low-risk concert.

Authorities had already recognised characteristics of the audience and previous Astroworld experience as justifying additional intervention capability.

Astroworld Case Study · Section 10 · Part 8

Festival Command Centre and the Critical Security Warning

Reece Wheeler Interview — HPD Supplement No. 0077

Source type: Primary police interview

Reece Wheeler worked for Unified Command as a festival liaison and coordinator/dispatcher and was positioned inside the festival's command centre.

He told investigators that his work included:

Command-centre monitoring
Radio communications
Use of an Incident Management System
Coordination of festival-security information

His background included supervising gates, stages, barricades and VIP areas before moving into event-command work.

This establishes an important distinction:

the festival command centre was not the same thing as the HPD or HFD command posts.

That fragmentation becomes central to Section 11.

HPD report
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf

Reece Wheeler → Shawna Boardman Communications

Source type: Primary communications recovered by HPD

Shortly before or around the beginning of Travis Scott's performance, Wheeler was monitoring crowd conditions and reported to security manager Shawna Boardman that the stage-right crowd was being crushed and that unconscious people were already being extracted.

He warned that conditions could deteriorate rapidly and subsequently advised that, in his view, the performance should not continue.

The police investigation later recorded that Boardman's lawyers said she visited or assessed the area and concluded conditions were not as serious as Wheeler believed, so she did not further escalate his warning.

This is crucial because it demonstrates that serious crowd-risk information existed within the private-security structure at approximately the time the headline performance began.

Houston Public Media
https://www.houstonpublicmedia.org/articles/news/criminal-justice/2023/07/28/458049/astroworld-concert-incident-report-released-by-houston-police/
Texas Tribune
https://www.texastribune.org/2023/07/28/travis-scott-houston-concert-police-report/
Astroworld Case Study · Section 10 · Part 9

Crowd Monitoring Versus Incident Response

The public EOP contains detailed procedures for reporting an incident once one has been identified.

What is much less apparent is a formal system for continuously monitoring:

Crowd density
Crowd pressure
Progressive loss of individual movement
Distress within individual Stage 1 compartments
Flow into and out of those compartments
Barrier loading
Rates of people being extracted over front-of-stage barricades

Searches of the public EOP find no specific use of “crowd surge” or “density”.

That does not prove that no one monitored crowds operationally.

Security workers clearly did observe and extract distressed customers.

Rather, the unresolved question is whether there was a defined crowd-monitoring function with measurable intervention thresholds and authority to regulate inflow or interrupt the performance.

Crowd Conditions Before Scott Took the Stage

Source type: Analysis of primary police investigation

The HPD investigation subsequently revealed that worrying crowd conditions were apparent before the headline set began.

Wheeler observed unconscious customers being passed out of densely occupied areas and communicated his concern through the security structure.

Houston Landing also reports that HPD investigators identified wider communication problems between festival personnel, security, production and medical functions.

The disaster should not be examined only from the point at which the formal mass-casualty incident was declared. There was an earlier period during which local indicators of deteriorating crowd conditions were already becoming available.
Full URL
https://www.houstonlanding.org/six-takeaways-from-the-houston-police-investigation-of-the-travis-scott-astroworld-concert/

Professional Security Opinion Recorded by HPD — John McGuire

Source type: Police interview with experienced event-industry professional; contextual evidence, not eyewitness evidence

HPD interviewed industry professional John McGuire about concert safety, barriers and security practice.

Among the issues he emphasised was the importance of the barrier itself and personnel monitoring the barrier.

He discussed the limitations of relying upon lightly trained event-security personnel without appropriate oversight.

His evidence is useful as professional context but must be treated separately from the facts of the event because he was not present at Astroworld 2021.

HPD report
https://www.houstontx.gov/police/pdfs/Astroworld_Redacted_Final.pdf

Later Civil Proceedings — Security Companies Remained in the Case

Source type: Court reporting

In April 2024, several security companies sought summary judgment in the consolidated Astroworld litigation.

Four companies remained in the case at that stage:

Contemporary Services Corporation; Apex Security Group; AJ Melino & Associates; and Valle Services.

This does not constitute a finding of liability. The court merely declined at that stage to remove them from the litigation.

It is useful because the proceedings generated further contracts, depositions and deployment evidence that should eventually be added to the source archive.

Full URL
https://www.houstonchronicle.com/news/houston-texas/crime/article/astroworld-lawsuit-dismissals-apple-travis-scott-19395990.php
Astroworld Case Study · Section 10 · Part 10

Key Documentary Gaps for Section 10

1
Final private-security staffing roster for 5 November 2021

Listing every operative actually checked in.

2
Planned staffing compared with actual attendance for duty

Needed to distinguish scheduled provision from personnel physically present.

3
Full breakdown of the reported 755 private-security personnel

Including employer, role and location.

4
Explanation of the separate 505 event security + 91 armed security + 76 HPD figures

Needed to reconcile the different accounting populations.

5
CSC's original Astroworld security contract and scope of work

Required to establish its precise obligations.

6
Contracts with Apex, AJ Melino, Valle and any additional subcontractors

Needed to map the full subcontracting structure.

7
4 November Harris County/ScoreMore contract amendment

Requiring supplemental security and medical personnel.

8
Post-by-post security deployment sheets

One of the highest-priority operational records.

9
Supervisor-to-operative ratios

Needed to assess management and span of control.

10
Exact number and location of personnel assigned to each Stage 1 crowd compartment

Critical for the local crowd-management analysis.

11
Front-of-stage barrier-security numbers

Needed to establish the extraction and monitoring resource at the main barrier.

12
Security positions within the internal cross/T barrier corridors

Required to assess the emergency-access concept described in planning.

13
Actual Event Day Briefing for 5 November

Needed to determine what information and instructions were communicated.

14
Records establishing which subcontracted guards attended that briefing

Written procedures only matter if they reached the deployed personnel.

15
Individual Texas DPS security-licensing records for deployed personnel

Required to test the licensing allegations.

16
CSC / AJ Melino training records

Including instructors, dates, examination and qualification records.

17
Radio allocation sheets

Identifying which security personnel actually carried radios.

18
Security radio recordings

Needed to reconstruct live information flow.

19
Security control-room incident logs

Required to compare reported incidents against subsequent action.

20
Complete Incident Management System data from Unified Command

Potentially the strongest source for the private command-centre timeline.

21
All messages between Wheeler, Shawna Boardman, Seyth Boardman and senior festival management

Needed to reconstruct the escalation chain.

22
Records showing what action followed Wheeler's warning

This is central to the transition from detection to decision-making.

23
CCTV monitoring assignments and screen layouts in Festival Command

Needed to determine what visual information was available and to whom.

24
A written crowd-monitoring plan, if one existed

Particularly any allocation of specific sectors to observers.

25
Predetermined crowd-density or extraction-rate escalation thresholds

Needed to determine whether measurable intervention triggers existed.

26
Records showing who could order individual crowd compartments closed to further entry

Critical to assessing local capacity control.

27
Proof that the last-minute personnel increase required on 4 November was actually supplied

The contractual requirement and operational delivery need to be distinguished.

What Section 10 Establishes

Astroworld was not an event with no security.

Hundreds of private-security personnel and police officers were deployed, and the written plan contained a structured security hierarchy, Event Control, briefing procedures, stage security, perimeter protection and access-control arrangements.

But the evidence exposes a different problem.

Weeks before the event, NRG Park management was concerned about the guest-to-staff ratio.

Two days before the festival, HPD still did not have final private-security or extra-police numbers.

One day before opening, the contract had to be amended to require additional security and medical personnel.

Some additional guards later alleged that they had been recruited at extremely short notice and received little or inadequate training; those claims require testing against the original employment and training records.

Most importantly, the security structure did detect serious danger.

At approximately the beginning of the headline performance, information was circulating within the festival-security system that unconscious customers were already being removed and that one experienced coordinator believed the show should not continue.

That changes the central question from:

“Were there enough security guards?”

to a much more useful set of questions:

Were the right people in the right positions?
Were they trained to recognise dangerous crowd compression?
Was there a dedicated monitoring system?
Did information from the crowd reach those with authority?
When serious warnings were received, what happened to them?
WORKING WITH CROWDS ASTROWORLD CASE STUDY

Translate »