Love Parade Duisburg · 24 July 2010
A crowd-safety case study examining the planning, site design, crowd movement, operational controls and systemic failures associated with the 2010 Love Parade disaster in Duisburg, Germany.
Case study
From an open-city parade to a constrained event site
Love Parade began in Berlin in 1989 and developed into one of Europe's largest electronic dance music events. Earlier editions had operated through wide streets and large open spaces. The 2010 event in Duisburg was fundamentally different: the principal festival area was a former freight yard enclosed by railway infrastructure and a motorway, with visitor access concentrated through the Karl-Lehr-Straße tunnel system and a ramp leading into the event site.
The change in venue form was operationally significant. Duisburg was the first Love Parade to use an enclosed festival area rather than the open street and park environment traditionally associated with the event.
Public descriptions of expected attendance varied enormously. Media and promotional figures associated with earlier Love Parades frequently reached more than one million people. Internal planning documents used much lower operational figures and contemplated approximately 450,000–485,000 total visitors, with no more than 250,000 intended to be present within the event site at one time.
The distinction between publicity attendance figures, total visitors across the day and simultaneous occupancy is essential when examining the case. These numbers described different things and should not be treated as interchangeable.
Contemporary reporting repeatedly used terms such as “stampede”, “panic” and “mass panic”. Those descriptions should be treated cautiously. Subsequent crowd-science analysis identified extreme density, loss of individual movement, crowd turbulence and progressive crowd collapse rather than a simple panic-driven stampede. The behaviour of people trying to escape dangerous compression should not be confused with the cause of the disaster.
Event environment
The crowd journey was dependent upon a constrained access system
Visitors approaching from the city and railway station were channelled towards the event through access routes leading into the Karl-Lehr-Straße tunnel system. From the tunnel, visitors moved towards a broad ramp which rose into the former freight-yard event site.
Former freight yard
The main event area was a bounded former railway freight site rather than the extensive open urban environment used by earlier Love Parades. Occupancy therefore had to be regulated rather than allowed to disperse freely through streets and adjoining open space.
Tunnel and ramp
The tunnel and associated ramp formed the critical connection between the external approach system and the festival site. Incoming and outgoing customers ultimately relied upon the same constrained route system.
Entrance-control installations
Separation or admission controls were positioned to regulate visitor demand before people entered the tunnel. Their ability to hold demand safely was therefore essential to the overall system.
Ramp head
Passing through the tunnel did not complete ingress. Visitors still had to move up the ramp and disperse effectively onto the event site. Congestion at the upper end of the ramp could therefore propagate backwards into the access route.
Incoming and outgoing flows
Customers entering and leaving the site used the same general corridor. Where those movements interacted, available effective width and throughput could reduce significantly.
Multiple organisations
Lopavent, the City of Duisburg, private security, state police, Federal Police, fire and medical services each controlled different parts of the operation. Safe movement therefore depended upon effective coordination across organisational boundaries.
The tunnel itself cannot be examined in isolation
The developing disaster involved the complete crowd system: arrivals outside the entrance controls, release into the tunnels, movement onto the ramp, congestion at the ramp head, outgoing visitors moving in the opposite direction, operational intervention by police, private-security control of entrance points and the ability of customers to disperse once they entered the festival site.
Operational sequence
A connected failure rather than one isolated event
The evidence accumulated after the disaster does not support a simple explanation based upon one act, one crowd reaction or one organisation. Multiple planning and operational factors interacted until the overall crowd system could no longer absorb the developing conditions.
Concerns about capacity and access
Internal documents show repeated discussion of the size of the event area, expected attendance, maximum simultaneous occupancy, escape arrangements and the capacity of the tunnel/ramp access system.
Reliance on regulating upstream demand
The operational concept relied heavily upon the ability to regulate how many people entered the tunnel. If downstream movement deteriorated, entrance controls needed to reduce or stop further admission until sufficient receiving space was restored.
Congestion develops at the ramp head
Visitors moving onto the festival site encountered opposing flow and people remaining close to the parade route and floats. Movement away from the ramp slowed and accumulation extended backwards.
Police cordons attempt to create space
Police formed cordons within the tunnel and ramp system in an attempt to interrupt movement and create a buffer while congestion ahead was addressed. The intervention depended upon further demand being held outside the system.
Entrance controls do not remain closed
Further visitors entered through the external control points while police intervention was affecting movement further ahead. Communication between police, security personnel and the Crowd Manager was inadequate and the complete system was not operating as one coordinated control.
Opposing flows and increasing density
Incoming customers, people attempting to leave, people trying to reach perceived escape routes and people who were effectively unable to move independently occupied the same constrained area.
Crowd turbulence and progressive collapse
At extreme density, physical forces were transmitted through people's bodies. Individual control of movement was lost. Wave-like movements developed, people lost balance and groups progressively fell onto one another.
Casualty care begins within a continuing event
Police, medical personnel, security personnel and members of the public attempted rescue and resuscitation while many people elsewhere on the festival site remained unaware that fatalities had occurred.
21 fatalities and hundreds injured
Twenty-one people died and 652 were reported injured. The Love Parade organisation subsequently announced that the festival would never be held again.
Evidence and reconstruction
Start with the material — not the headlines
Love Parade is unusual among major crowd disasters because an enormous volume of contemporaneous footage, photographs, eyewitness material, planning documents and subsequent analysis became publicly available. This allows the event to be examined at a level of detail rarely possible after a crowd incident.
Documentation of the events of Love Parade 2010
Independent archive created shortly after the disaster. It brings together photographs, eyewitness reports, planning information, police communications and hundreds of videos.
Open evidence archiveReconstruction of 24 July 2010
Detailed chronological reconstruction of movements, barriers, tunnel conditions, ramp conditions and operational developments using video and eyewitness material.
Open reconstructionCrowd Disasters as Systemic Failures
Dirk Helbing and Pratik Mukerji's detailed open-access analysis uses video and planning material to examine the interacting factors that produced the disaster.
Read academic paperWDR Love Parade chronology
WDR's surviving historical chronology follows the event, investigations, criminal proceedings and eventual termination of the trial.
Open WDR chronologyIndividual videos show only one position and one period of time. They are most useful when synchronised with other footage and mapped against location, time and operational actions. The independent documentation project was created specifically to undertake that reconstruction.
Contemporary reporting
News coverage across the incident and legal timeline
The following reports were retained on the original Working With Crowds page because they show how understanding of the disaster developed over time. Early reports should be read with caution: terminology and casualty information changed as more reliable evidence became available.
Love Parade festival fatalities
Initial breaking-news coverage published before the final casualty figures and detailed mechanism of the disaster were known.
Love Parade Tragedy: In the Tunnel of Death
Early survivor-focused reporting describing conditions encountered by people caught within the affected crowd.
Festivalgoers killed at Love Parade in Germany
Contemporary reporting illustrating how early accounts framed the event before later reconstruction corrected a number of assumptions.
Germany mourns Love Parade victims
Reporting from the memorial service held for the 21 people who died.
Organiser releases CCTV recordings
Reporting on the release of CCTV footage and the dispute between Lopavent and police about responsibility.
Timeline of the Love Parade tragedy
Contemporary chronological account of the day and the developing emergency.
Ten people indicted over the Love Parade disaster
Reporting following the decision by prosecutors to bring charges against six city employees and four Lopavent employees.
Court initially refuses to open a criminal trial
The Duisburg Regional Court initially declined to open the prosecution case. That position was subsequently reversed on appeal and the trial began in December 2017.
Love Parade accused initially will not stand trial
Industry reporting on the original decision not to open the criminal proceedings.
New civil damage claims
Reporting on civil claims pursued by people injured at the Love Parade.
Terms such as “stampede” and “panic” remain in the original article titles because they form part of the historical record. Their inclusion here does not mean Working With Crowds accepts those descriptions as an accurate explanation of the crowd mechanism.
Research and technical material
Crowd science, medical response and analytical resources
The Love Parade disaster subsequently generated substantial academic and professional analysis. The material below provides useful starting points for understanding crowd turbulence, systemic failure, emergency medical response and the distinction between crowd behaviour and crowd conditions.
Crowd Disasters as Systemic Failures
Helbing and Mukerji analyse the disaster as an interacting systemic failure rather than a simple consequence of individual crowd behaviour.
Read paperPanic was not the cause of the Love Parade disaster
Accessible explanation of Helbing's analysis of crowd turbulence, transmitted physical forces and why “mass panic” is an inadequate explanation.
Read analysisPatient Care at the 2010 Love Parade
Clinical analysis of patient presentation, emergency medical arrangements and hospital response following the disaster.
Read medical paperVideos, photographs and eyewitness evidence
Volunteer evidence project containing synchronised video, police communications, eyewitness statements, plans and reconstructed timelines.
Open archiveSystem performance is more important than isolated controls
Love Parade demonstrates why capacity, entrance processing, route width, internal receiving space, opposing flows, communications, observation, escalation and emergency intervention must be assessed as one connected system. A control can work correctly at its own location and still contribute to failure elsewhere if its effect on the wider crowd journey is not understood.
Primary document archive
Planning, approval and operational records
The original Working With Crowds page retained an extensive index of planning and administrative material released after the disaster. That index has been preserved below because it provides an unusually detailed record of how a major event moved from initial proposal through planning, approval and delivery.
Documents 1–9 · Early planning and governance
- 1 · Sector Map Event logistics, camera locations, emergency points and operational sectors.
- 2 · Political authority and funding decisions Authority granted to the Mayor of Duisburg to enter a framework agreement with Lopavent, together with the later decision that public money should not be invested in the Love Parade.
- 3 · Meeting protocol · 25 September 2009 Meeting involving city authorities, Lopavent and Aurelis concerning the proposed event.
- 4 · Meeting protocol · 2 October 2009 Planning discussion involving city authorities, Lopavent and stakeholders. Includes an estimate of approximately one million visitors.
- 5 · Traffic Task Force · 20 October 2009 Includes observations from rail/transport representatives that approximately 90% of visitors at earlier Love Parades had travelled by train.
- 6 · Planning status presentation · 29 October 2009 Early presentation describing the developing state of preparations.
- 7 · Invitation to planning meeting · 21 April 2010 Formal invitation relating to the continuing Duisburg planning process.
- 8 · Overview of Love Parade task forces Lists working groups for transport, event administration, public relations/citizens and security, together with prospective participants.
- 9 · Security Task Force protocol · 23 April 2010 Record of the security working group meeting, excluding attachments.
Documents 10–19 · Event concepts and crowd planning
- 10 · Lopavent event description · 28 May 2010 Estimated approximately 90% rail arrivals, around 450,000 total visitors and up to 250,000 simultaneous occupancy. Described approximately 70 security personnel in the entrance/tunnel area and a security lead positioned near the ramp.
- 11 · Internal security concept draft · 20 May 2010 Used a maximum simultaneous occupancy of 250,000 and described observers at tunnel entrances equipped with radios to report critical conditions to event control.
- 12 · Police planned measures · 29 June 2010 Proposed road closures and temporary fencing, circulated between police, fire and city authorities.
- 13 · Contract with Professor Michael Schreckenberg €20,000 commission to provide advice relating to visitor-flow management and the proposed event site.
- 14 · Ordnungsamt letter and meeting notes · July 2010 Records discussions with Professor Schreckenberg and notes supplied to the city administration and police.
- 15 · Police scenario workshop protocol · 8 July 2010 Describes visitor counting, sector arrangements, response to congestion and major incidents, communication requirements and event-control contacts.
- 16 · City administration meeting · 15 July 2010 Records requests for remaining safety concerns to be raised before the event.
- 17 · Lopavent visitor estimate · 8 July 2010 Internal estimates distinguished operational numbers from public/media attendance figures. Approximately 485,000 total visitors were contemplated with no more than 250,000 intended to be present simultaneously.
- 18 · Formal event approval request · 1 February 2010 Application by Lopavent's solicitors addressed to the Mayor of Duisburg.
- 19 · Confidential event concept · 15 January 2010 Early internal event-planning document.
Documents 20–28 · Capacity concerns and approval process
- 20 · City meeting · 2 March 2010 Records concerns that the proposed event area was insufficient when applying lower density assumptions. The document discussed possible peaks substantially above the site's preferred occupancy and described the problem as potentially unsolvable.
- 21 · Planning meeting · 8 March 2010 Records concerns about the size of the event area, simultaneous occupancy, rail capacity and the fact that incoming and outgoing customers would depend upon the tunnel system.
- 22 · Lopavent internal event concept · 15 March 2010 Internal document marked as not intended for public use.
- 23 · Meeting notes · 21 April 2010 Records discussion of density limits and reductions to usable event area.
- 24 · Building authority request · 14 June 2010 Identifies missing documents including the final security and fire-protection concepts. Also records concerns about density assumptions, available event area and escape-route provision.
- 25 · Internal note · 18 June 2010 Identifies fire protection, maximum density and escape arrangements as unresolved critical issues. Also records senior pressure to find a solution that would allow the event to proceed.
- 26 · Meeting · 25 June 2010 Agreement to conduct additional escape analysis to determine whether deviation from normal requirements could be accepted.
- 27 · Extension of deadline Lopavent request and subsequent city approval for additional time to submit missing documentation.
- 28 · Second interim assessment · 14 July 2010 Identifies outstanding plans, fire-protection documentation, security information and other material shortly before the event.
Documents 29–36 · Final concepts and approvals
- 29 · Detailed Lopavent event description · 16 July 2010 Uses a maximum simultaneous occupancy of 250,000 and identifies the tunnel as a particularly important element because it provided the principal entry route. Describes approximately 100 security personnel for the tunnel area, camera monitoring and the ability to close access if congestion developed.
- 30 · Event-area map Plan showing intended visitor-entry flow.
- 31 · Request for exceptional use of Karl-Lehr-Straße · 19 July Formal request submitted shortly before the event.
- 32 · Approval for exceptional road use · 21 July City approval relating to Karl-Lehr-Straße.
- 33 · Fire-protection concept · 22 July 2010 Updated expert fire-safety concept issued only two days before the Love Parade.
- 34 · Building-law exception approval · 21 July 2010 Included exceptions concerning required escape-route dimensions and fire-service plans. Conditions included application of the fire-protection concept and a maximum simultaneous occupancy of 250,000.
- 35 · Lopavent logistics/security presentation Presentation prepared during the final stage of planning after mid-July.
- 36 · Sector map · 12 July 2010 Operational sector plan used during event planning.
Documents 37–42 · Event records and post-incident evidence
- 37 · Utilisation notification · 26 July 2010 Spreadsheet containing reported sector utilisation. Entries for the tunnel sector were incomplete and no figures were recorded after 17:00.
- 38 · Event log · dated 25 July 2010 Partial operational log covering only part of the recorded event period.
- 39 · Note concerning tunnel access blockage Written during the early hours of 25 July following the event.
- 40 · Photograph of the ramp Event-day image from the ramp/tunnel environment without confirmed timestamp.
- 41 · Photograph of Tunnel West Event-day image without confirmed timestamp.
- 42 · Resident eyewitness letter · 27 July 2010 Account submitted to the City of Duisburg describing conditions around the Karl-Lehr-Straße entrance between approximately 13:00 and 16:00, including observations of police activity and increasing congestion.
Read individually, many of the documents appear to concern relatively narrow technical or administrative matters. Read together, they provide a record of how capacity, event-space availability, access, escape, transport, visitor estimates, responsibilities and operational control were discussed over many months. Their value is therefore in understanding the development of the complete system rather than searching for one document that “caused” the disaster.
Criminal proceedings
Love Parade Trial Archive · 2017–2020
The original version of this case-study page pre-dated the criminal trial. The Working With Crowds archive now preserves the proceedings from the first survivor testimony through the final discontinuance of the case in May 2020.
Survivor evidence, forensic material, Adolf Sauerland, Rainer Schaller and the opening evidential phase.
Open archive → 2018 · Part Two June–December 2018City officials, police commanders, Crowd Manager, Gerlach expert evidence and later operational witnesses.
Open archive → 2019 Three Defendants RemainSeven proceedings end and the remaining trial focuses increasingly on Lopavent organisation and responsibilities.
Open archive → 2020 Final ProceedingsFinal security evidence, COVID-19 interruption and the discontinuance of the criminal case after 184 days.
Open archive →The criminal case ended without a judgment
Ten people originally faced proceedings arising from the disaster. Cases against seven defendants were discontinued in February 2019. Proceedings continued against three former Lopavent employees until 4 May 2020, when the court discontinued the remaining cases. The trial therefore ended without a final judgment allocating individual criminal guilt.
Crowd-safety learning
The enduring value of the Love Parade case
Love Parade remains valuable to crowd-safety practitioners because it demonstrates how apparently separate planning and operational decisions can combine to create a systemic failure. It should not be reduced to a story about a tunnel, a police cordon, a crowd manager, a barrier or the behaviour of customers.
Design the complete crowd journey
Ingress cannot be considered complete at the entrance threshold. Downstream receiving space must remain capable of accepting the flow being released upstream.
Match throughput to demand
Entry processing, route capacity and internal receiving capacity need to be assessed together. A restriction in any one stage can generate accumulation elsewhere.
Plan opposing movement deliberately
Incoming and outgoing flows sharing constrained space require specific control. Counterflow can substantially reduce effective capacity.
Maintain effective observation
Density and flow deterioration must be detected early enough for intervention to work before individual movement is lost.
Integrate command and communication
Police, organisers, security and control functions cannot operate safely as isolated systems when their actions directly affect the same crowd.
Verify operational delivery
A written plan is not a control until trained and briefed personnel, equipment, communication and supervision are actually in place to deliver it.
Prepare for control failure
Contingencies are required for barriers opening, radio or telephone failure, insufficient personnel, unplanned counterflow and congestion beyond the expected location.
Avoid blaming the crowd
Extreme density can remove individual control of movement. Behaviour observed in the final stages of a dangerous crowd condition may be a consequence of system failure rather than its cause.
Documentation of the events for the Love Parade 2010 in Duisburg
Videos
Inquest
View the available footage before drawing conclusions from the incident
Where possible, take time to review as much of the available footage as possible when examining the Love Parade disaster. Dokumentation der Ereignisse zur Loveparade 2010 in Duisburg has undertaken extensive work to locate, organise and preserve video footage, photographs, eyewitness material and other evidence relating to the events of 24 July 2010.
Individual recordings provide only one viewpoint and one moment in time. Their greatest value comes from comparing multiple recordings against location, timing, crowd movement and operational actions across the wider event environment.
External historical evidence archive · Opens in a new tabExternal Resources
Websites and Further Reading
The original Working With Crowds case study included a collection of external websites and articles examining the Love Parade disaster, its crowd dynamics and the subsequent legal proceedings. These resources are retained here as part of the historical archive.
‘Crowd Quakes’ Were a Key Factor in the Love Parade Disaster
An accessible examination of the research undertaken by Dirk Helbing and Pratik Mukerji into the extreme crowd conditions that developed in Duisburg.
The article discusses crowd turbulence and the phenomenon sometimes described as “crowd quakes”, where physical forces propagate through extremely dense groups and individual control of movement is progressively lost.
Timeline of the Love Parade Tragedy
Deutsche Welle's contemporary chronology follows the events of 24 July 2010 and the developing emergency around the tunnel and ramp.
It provides a useful historical account of how the incident was understood during the immediate aftermath, before the extensive later reconstruction and criminal proceedings.
10 Charged in 2010 Love Parade Disaster That Killed 21
Contemporary reporting following the decision by German prosecutors to bring criminal charges against ten people associated with the planning and approval of the event.
Six of those charged had worked for the City of Duisburg and four had worked for organiser Lopavent.
The German Love Parade Disaster: Not a Tragic Accident, but a Crime
Published shortly after the disaster, this commentary examines concerns surrounding site selection, planning, political pressure and the responsibilities of the organiser and public authorities.
It represents one contemporary interpretation of the disaster and should be read alongside the subsequent investigations, academic research and criminal proceedings.
Love Parade Accused Won’t Stand Trial
Live-events industry reporting on the Duisburg Regional Court's original 2016 decision not to open criminal proceedings against the ten accused.
That decision was subsequently overturned on appeal and the criminal trial eventually began in December 2017.
Love Parade, Duisburg Facing New Damage Claims
Reporting on further civil claims brought by people injured during the 2010 disaster.
The article provides useful background to the wider legal consequences of the disaster outside the subsequent criminal proceedings.
Some contemporary sources use terms such as “stampede”, “panic” or “mass panic”. These descriptions are retained where they form part of an original article title, but they should not automatically be interpreted as an accurate explanation of the crowd mechanism. Later analysis identified extreme density, crowd turbulence, loss of individual movement and progressive crowd collapse as key features of the disaster.
Documents
Planning and Operational Document Archive
A chronological collection of German planning, approval, operational and post-incident records relating to the Love Parade held in Duisburg on 24 July 2010. Together, these documents provide an unusually detailed record of how the event developed from initial proposal through planning, approval, delivery and subsequent examination.
The documents are grouped below by phase of the planning process. Select a section to expand it. Records identified as particularly important to understanding crowd capacity, access, egress or approval have been visually highlighted.
Documents 1–9 · Early Planning and Governance 2007 – April 2010
Sector Map
Sector map including event logistics, camera locations, emergency points and other operational locations.
Political Authority and Funding Decisions
Authorisation granted to the Mayor of Duisburg by the city parliament to sign a framework contract with Lopavent GmbH for the 2010 Love Parade, together with the later decision that public funds would not be invested in the event.
Meeting Protocol · 25 September 2009
Meeting involving City authorities, Lopavent and Aurelis concerning the proposed event.
Meeting Protocol · 2 October 2009
Planning meeting involving City authorities, Lopavent and other local stakeholders. The document includes an estimated attendance of approximately one million visitors.
Traffic Task Force · 20 October 2009
Includes observations from German Rail and VRR participants that approximately 90% of visitors to the 2007 and 2008 Love Parades had arrived by train.
Planning Status Presentation · 29 October 2009
Presentation describing the current state of preparations for the Duisburg Love Parade.
Invitation to Duisburg Planning Meeting · 21 April 2010
Invitation issued by the clerk's office for a further planning meeting concerning the Love Parade.
Overview of Love Parade Task Forces
Overview of the working groups established for traffic and transportation, event administration, public relations and citizens, and security, together with prospective participants.
Security Task Force Protocol · 23 April 2010
Record of the Security Task Force meeting, excluding the associated protocol attachments.
Documents 10–19 · Event Concepts and Crowd Planning January – July 2010
Lopavent Event Description · 28 May 2010
Estimated that 90% of visitors would arrive by rail, with approximately 450,000 total visitors and a maximum of 250,000 present at any one time.
The document used an event area of approximately 110,000m² and a maximum density of 2.5 persons/m². It described mobile security patrols in the tunnel, approximately 70 security personnel in the entrance and tunnel area, and a security lead positioned at the ramp with authority to temporarily close the tunnel entrance if congestion developed.
Panic situations were described as extremely unlikely or impossible because of the high noise levels; unlike other hazards, no specific mitigation was identified.
Internal Security Concept Draft · 20 May 2010
Estimated a maximum simultaneous attendance of 250,000, with the ability to regulate entrance if actual visitor numbers became significantly higher.
The document referred to observers at the tunnel entrances equipped with radio communication to notify event control of critical situations.
Police Planned Measures · 29 June 2010
Police documentation covering road closures and temporary fencing, circulated to the Fire Department and City administration. Includes maps showing intended fence locations.
Contract with Professor Michael Schreckenberg
€20,000 commission dated 21 May 2010 for Professor Schreckenberg of the University of Duisburg-Essen to review visitor-flow management and the proposed event location.
Ordnungsamt Correspondence with Professor Schreckenberg
Letter dated 13 July 2010 containing internal City and police notes concerning a meeting with Professor Schreckenberg on 12 July, together with confirmation that the notes accurately reflected the discussion.
Police Scenario Workshop · 8 July 2010
Protocol covering visitor counting, the sector system, crowd congestion and responses to different hazardous situations.
The tunnel was designated Sector V-1. The document required speaker systems to provide information during congestion and blockages and contained response arrangements for major incidents.
Attachments included the sector plan, flight plan, scenario documentation and event-control contact lists.
City Administration Meeting · 15 July 2010
Meeting involving multiple stakeholders. Remaining security concerns were invited to be raised before the event.
Lopavent Visitor Estimate · 8 July 2010
Confidential internal estimate sent personally to Mr Bölling of the Duisburg Ordnungsamt.
The document expressly distinguished the operational estimates from the larger “official visitor numbers” used for media purposes.
Approximately 485,000 total visitors were estimated, with no more than 250,000 expected to be present at any one time. Rail-station capacity was identified as a limiting factor.
Formal Event Approval Request · 1 February 2010
Formal application for approval of the Love Parade submitted by Lopavent's solicitors to Mayor Adolf Sauerland.
Confidential Event Concept · 15 January 2010
Early confidential event-planning concept prepared by Lopavent.
Documents 20–28 · Capacity Concerns and Approval March – July 2010
City Meeting · 2 March 2010
The meeting considered the maximum permitted number of visitors against available event space.
At two persons/m², the proposed location was described as insufficient, allowing approximately 180,000 people. Even lower attendance estimates contemplated 500,000–600,000 total visitors and peaks of around 300,000 simultaneous visitors.
The protocol described the problem as “not solvable” and recorded concern that members of approving authorities could face legal consequences.
Planning Meeting · 8 March 2010
City departments raised concerns that the event area was too small for the expected number of visitors.
A maximum density of two persons/m² was discussed. Expected rail capacity suggested approximately 400,000 total visitors and around 200,000–250,000 simultaneous visitors.
The meeting also recorded that both incoming and outgoing visitors would use the tunnel and that access blockages could only be maintained for short periods.
Internal Lopavent Event Concept · 15 March 2010
Internal planning document marked “not for public use”.
Meeting Notes · 21 April 2010
Internal notes from discussions between Lopavent, Duisburg City officials and the site owner.
The documents recorded a maximum of two visitors/m² and noted that reductions in usable event area would further reduce the number of visitors that could be accommodated.
Building Authority Request · 14 June 2010
Lopavent was instructed to provide missing documents necessary for approval, including a final site-specific security concept and fire-protection concept.
The preliminary assessment stated that Lopavent's proposed density of 2.5 persons/m² exceeded the City's two persons/m² assumption, reducing potential simultaneous occupancy to approximately 220,000 even before service areas were deducted.
Escape arrangements were also considered insufficient, with the submitted concept providing secure escape capacity for only around one third of visitors.
Internal Note · 18 June 2010
Three critical issues were identified: fire protection, acceptable visitor density and the escape concept.
Lopavent disagreed with the City's two persons/m² position and considered escape provision for one third of visitors sufficient.
The note records Wolfgang Rabe stating that the Mayor wanted the event and that a solution therefore had to be found, with authorities and the Fire Department assisting Lopavent in producing an acceptable concept.
A handwritten note from Jürgen Dressler recorded his refusal to accept responsibility and accountability for what he regarded as an improper administrative process.
Meeting · 25 June 2010
Agreement between Lopavent, an external agency, the Fire Department and City officials to conduct additional escape analysis.
If that analysis did not justify deviation from normal requirements, the building authority would not approve the event.
Extension of Documentation Deadline
Two records covering Lopavent's request for additional time to submit missing documents and the City's approval extending the deadline to 7 July 2010.
Second Interim Assessment · 14 July 2010
The building authority recorded that the event-area plan was not current, building plans were missing, the fire-protection concept remained outstanding and the security concept was not up to date.
A new deadline was set for the end of the 28th calendar week.
Documents 29–36 · Final Concepts and Approvals 12 – 22 July 2010
Detailed Lopavent Event Description · 16 July 2010
The document identified the City of Duisburg as responsible for detailed planning of access and exit routes.
Maximum simultaneous attendance was again stated as 250,000 within an event area of approximately 110,000m².
The tunnel was identified as particularly important because it provided the principal entry route. Access was intended to be closed if necessary.
Approximately 100 Lopavent security personnel were planned for the tunnel area, with entrance security management positioned on the ramp. Seventeen cameras were intended to provide almost complete monitoring and allow ad hoc visitor counting and density calculations.
The document again described panic as either impossible or likely to have only limited negative consequences.
Event-Area Map
Site plan showing the proposed visitor-entry flow.
Request for Exceptional Use of Karl-Lehr-Straße · 19 July
Formal request submitted by Lopavent's solicitors for exceptional use of Karl-Lehr-Straße in connection with the Love Parade.
Approval for Exceptional Road Use · 21 July
City approval permitting exceptional use of Karl-Lehr-Straße for the event.
Fire-Protection Concept · 22 July 2010
Updated expert fire-protection assessment issued only two days before the Love Parade, replacing an earlier version dated 17 July.
Building-Law Exception Approval · 21 July 2010
Approval containing two exceptions: a waiver relating to legally required minimum escape-route width and a waiver relating to fire-brigade plans.
Conditions included compliance with the fire-protection concept and a requirement that simultaneous attendance never exceed 250,000 people.
Lopavent Logistics and Security Presentation
Undated presentation produced after 14 July 2010, principally concerning event logistics and security.
Sector Map · 12 July 2010
Operational sector map prepared during the final stage of event planning.
Documents 37–42 · Event and Post-Incident Records 24 – 27 July 2010
Utilisation Notification · 26 July 2010
Spreadsheet recording reported utilisation across event sectors.
No figures were recorded after 17:00. For Sector V-1, covering the tunnel, police entries recorded 100% utilisation at both 13:00 and 14:00.
Lopavent entries for the same sector recorded 24% at 13:00, 48% at 14:00 and 82% at 15:00.
Data relating to arrivals at the main railway station was also incomplete.
Event Log · 25 July 2010
Only pages 10–19 of a 53-page event log were available. The surviving extract begins at 07:23 on 24 July and ends at 12:52, before the critical period of the incident.
Note No. 733 · Tunnel Access Blockage
Note concerning blockage of access to the tunnel, recorded at 01:09 on 25 July 2010.
Photograph · Ramp to Tunnel
Photograph taken during the Love Parade at the ramp leading towards the tunnel. No confirmed timestamp is available.
Photograph · Tunnel West
Photograph taken during the Love Parade at the western tunnel area. No confirmed timestamp is available.
Resident's Letter to the City of Duisburg · 27 July 2010
Eyewitness description of conditions around Karl-Lehr-Straße and the tunnel entrance between approximately 13:00 and 16:00.
The witness described police allowing additional people to move towards the tunnel despite visible crowding at approximately 14:45.
The letter also recorded that three police officers in Karl-Lehr-Straße had been filming the situation for several hours.
No single document explains the Love Parade disaster. Their value comes from reading them together. Across the sequence, repeated issues emerge around attendance estimates, usable event space, crowd density, tunnel and ramp capacity, entrance regulation, escape arrangements, communications, responsibilities and the pressure to achieve approval. Together they provide a detailed record of how the final operational system developed before 24 July 2010.
