case_record stringclasses 3
values | scene_notes stringclasses 3
values | event_timeline stringclasses 3
values | failure_analysis stringclasses 3
values | response_records stringclasses 3
values | response_evaluation stringclasses 3
values | contributing_factors listlengths 4 4 | full_analysis_report stringclasses 3
values | personnel_statements stringclasses 3
values | consequences_and_impact stringclasses 3
values | evidence_and_uncertainty stringclasses 3
values | equipment_system_anomalies stringclasses 3
values |
|---|---|---|---|---|---|---|---|---|---|---|---|
Event: Brief unintended litter movement following an ambiguous movement command. Location: East Slope, Bracken Creek access route. Date: 2024-09-07. A team was hauling an attended litter up a steep wooded slope toward a trail bench. The litter was managed on a main haul line with a separate belay line. The litter moved... | At 14:06, the litter was moving uphill on a section of slope with roots and loose surface material. The lead rescuer identified an obstruction ahead and called for the team to hold. The haul operator reported hearing a command to lower by one increment and acted on that interpretation. The litter moved approximately 0.... | - 14:06 — The litter was being hauled uphill toward an obstruction; supported by the scene notes.
- Shortly afterward — The lead rescuer called hold, while the haul operator understood a lower-by-one-increment command and briefly released the haul; supported by the two statements and scene notes, with disagreement abou... | The event is best characterized as a brief loss of coordinated movement control rather than a documented hardware failure. A mismatch between the lead rescuer's intended stop command and the haul operator's understanding led to unintended release of the haul. The belay line had slack immediately beforehand, so it did n... | On the repeated stop call, the haul operator stopped movement and the belay operator maintained the line. The team confirmed that the litter was stable and checked the attendant and patient, with no injury reported. The load was held while the lead rescuer reassessed the route. The team then resumed only after the move... | The repeated stop call was followed by prompt cessation of movement. The belay operator maintained the line, and the team checked the patient and attendant before resuming. Repeating and acknowledging commands after the event was a useful immediate correction. Review should focus on using unambiguous standard commands,... | [
"The lead rescuer and haul operator reported different understandings of the movement command, and the intended hold was not acted on immediately.",
"The belay line had some slack immediately before the unintended movement, allowing a short downhill displacement before it became tensioned.",
"The litter was app... | ## Event overview
On 7 September 2024, an attended litter being hauled up East Slope near Bracken Creek moved approximately 0.25 m downhill after the lead rescuer called for the team to hold. The haul operator understood the command as an instruction to lower briefly. A separate belay line, reported to have some slack ... | The lead rescuer stated that the intended command was hold because the litter was approaching an obstruction. The haul operator stated that the command was understood as lower by one increment and that the haul was released briefly. A belay operator reported that the belay had some slack before the movement and tighten... | The litter moved approximately 0.25 m downhill before the belay arrested further travel. No injury, ground contact, or equipment damage was reported. The team paused the operation, checked the occupants, and reviewed the route and communications before continuing. The incident caused a short operational interruption an... | The timeline is supported by the scene notes and statements from the lead rescuer, haul operator, and belay operator. The lead rescuer's account of calling hold conflicts with the haul operator's account of hearing a lower command. The approximate 0.25 m movement and the belay's transition from slack to tension are rec... | No broken, deformed, or visibly damaged rope, connector, or anchor was reported. The belay line was reported to have slack before the unintended movement and to become tensioned as the litter moved downhill. The record contains no measured line loads, no measurement of the initial slack, and no inspection findings beyo... |
Event: Edge-protection displacement during a litter lowering operation. Location: Sector C, Alder Ridge. Date: 2024-05-18. The team was lowering a litter with an attendant from a rock ledge to a lower staging area. The operation used a primary lowering line and a separately anchored belay line. No injury was reported. | At 09:12, the litter was staged at the ledge and the edge-protection pad was placed where the primary line crossed the rock lip. The pad was secured before loading. At 09:18, while the litter was moving slowly below the lip, the attendant reported vibration and asked the team to stop. The litter remained suspended with... | - 09:12 — Litter staged and edge protection positioned; supported by the scene notes.
- 09:18 — During lowering below the lip, the attendant reported vibration and called for a stop; supported by the scene notes and attendant statement.
- Immediately after the stop — The litter remained suspended, and the team observed... | The documented event is consistent with loss of effective edge protection followed by rope contact with the rock lip. The pad displacement and localized rope glazing and abrasion support that interpretation, while the reported vibration provides a contemporaneous indication of increased or changing contact at the edge.... | The lowering team stopped movement, confirmed that the litter was stable, and maintained the independent belay. The edge team inspected the line path without moving the loaded system. After confirming that the operation could not continue safely with the observed rope condition, the team transferred the litter to a sta... | The attendant's stop call, the lowering operator's prompt compliance, and continued availability of the belay were effective controls. The team avoided continuing to load a rope with visible damage, quarantined it, and recorded the condition. The response could be strengthened by documenting a deliberate post-load chec... | [
"The edge-protection pad moved approximately 20 cm during the operation, allowing the primary line to contact the rock lip.",
"The rope crossed a rock edge where contact was possible; the post-event abrasion and glazing are consistent with that contact.",
"The condition was first recognized through vibration re... | ## Event overview
On 18 May 2024, a team lowering an attended litter from a rock ledge at Sector C, Alder Ridge, stopped the operation after the attendant reported vibration. The event resulted in localized abrasion and glazing on the primary rope and displacement of the edge-protection pad. No injury, rope break, or u... | The attendant reported a short vibration through the litter and requested an immediate stop; they did not report a sudden drop. The edge attendant stated that the protection pad had been positioned before loading and that the line appeared centered on it at the start. The lowering operator reported maintaining a slow r... | No injury or uncontrolled movement was reported. The operation was interrupted, the primary rope was removed from service, and the litter had to be moved to staging using the backup arrangement. The observed rope damage required inspection before any further use and reduced the team's immediately available equipment. T... | The scene notes establish the pad's initial placement, its later displacement, the timing of the stop, and the attendant's vibration report. The equipment record establishes localized glazing and abrasion on the primary rope and no reported visible damage to the belay or connectors. The response record establishes quar... | After the system was unloaded, a section of the primary rope approximately 1.2 m from the edge showed localized glazing and abrasion. The record does not document a cut, exposed core, or measured loss of diameter. The edge-protection pad had shifted from its recorded position. No visible damage was reported on the bela... |
Event: Portable anchor-frame movement during initial loading for a shaft rescue. Location: Service shaft 4, Larkspur Works. Date: 2025-02-11. A team was preparing to raise an attended litter from the shaft to the surface using a portable anchor frame and a separate backup line connected to a rock anchor. During initial... | At 16:32, the frame was positioned at the shaft edge on a gravel surface. A chalk mark had been placed beside the front foot to observe movement. As the team began a controlled initial loading with the litter still at the lower staging point, the front foot moved approximately 35 mm along the surface and the frame show... | - 16:32 — The portable frame was positioned at the shaft edge on gravel, with a chalk reference at the front foot; supported by the scene notes.
- During initial loading — The front foot moved approximately 35 mm and the frame tilted slightly; supported by the observer's statement and scene notes.
- Immediately after t... | The observed movement is consistent with the frame foot losing stable support on the gravel surface under initial loading. The displacement relative to the chalk mark and disturbed ground support a movement of the footing; the slight tilt indicates that the frame's position changed. The records do not quantify the appl... | The team stopped loading and maintained control of both lines. The frame was unloaded, and the litter remained at the lower staging point while the team reassessed the surface and anchor arrangement. The team then used a revised setup located on a firmer surface, with the backup remaining independent. Before proceeding... | The chalk reference made the foot movement visible, and the edge observer's call was followed by an immediate stop. Maintaining both lines, unloading the frame, and relocating to a firmer surface were appropriate responses to the observed instability. The team confirmed the revised arrangement under controlled loading ... | [
"The frame was positioned on gravel, and the front foot moved with visible ground disturbance during initial loading.",
"The approximately 35 mm displacement and slight tilt show that the initial support arrangement did not remain stable under the load applied.",
"The operation involved a shaft-edge setup where... | ## Event overview
On 11 February 2025, a portable anchor frame moved during initial loading at Service shaft 4, Larkspur Works. The frame stood on gravel at the shaft edge. An observer saw its front foot shift approximately 35 mm from a chalk reference and noted a slight tilt. The team stopped before raising the attend... | The edge observer stated that the front foot moved relative to the chalk mark and that the frame tilted slightly. The frame operator reported stopping the load as soon as the movement was called out. The backup-line operator stated that the line remained connected to the separate rock anchor and was tensioned during th... | The frame did not overturn, the litter remained at the lower staging point, and no injury was reported. The team halted the planned lift, unloaded and repositioned the frame, and delayed the rescue operation while confirming a stable setup. No visible damage to the frame, hardware, backup line, or anchor was reported. ... | The scene notes and observer statement establish movement of approximately 35 mm relative to a chalk mark, slight frame tilt, and disturbed gravel. The response record establishes that the frame was unloaded and repositioned before the litter was raised. Personnel statements report that the separate backup line remaine... | The front foot of the portable frame shifted approximately 35 mm from the chalk reference during initial loading. A disturbed area in the gravel was observed around the foot. No visible deformation, cracking, or connector damage was reported on the frame or attached hardware. The backup line and its separate rock ancho... |
Technical Rope Rescue Incident and Failure Analysis Report Dataset
This dataset focuses on incidents and system anomalies in technical rope and high-angle rescue, bringing together case details, scene notes, equipment anomalies, personnel statements, and response records alongside event summaries and failure analysis reports. Its contents cover event timelines, failure modes, contributing factors, consequences, response evaluations, and evidentiary uncertainty, supporting models that synthesize multiple sources of evidence into professional long-form reports. It is suitable for domain-specific fine-tuning, report-generation research, and safety review in rope rescue.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| case_record | string | Original case information, including the incident name, location, time, and rescue mission context. |
| scene_notes | string | Original records of scene observations, environmental conditions, rope system setup, and operational procedures. |
| event_timeline | string | A chronological account derived from source materials, identifying key events and their supporting evidence. |
| failure_analysis | string | An integrated analysis of failure modes and mechanisms in the rope rescue system or operational procedures, and their relationship to incident progression. |
| response_records | string | Original records of actions taken after the incident, including rescue efforts, system adjustments, medical care, and follow-up measures. |
| response_evaluation | string | An assessment of response measures, decisions, and coordination after the incident, including effective practices and opportunities for improvement. |
| contributing_factors | array | Factors identified and summarized from the case materials that caused or worsened the incident. |
| full_analysis_report | string | A professional long-form report based on source materials and analytical findings, covering the incident overview, timeline, failure and contributing factor analysis, consequences, response evaluation, and recommendations for improvement. |
| personnel_statements | string | Original statements from on-scene personnel, rescuers, or other witnesses about the incident, actions taken, and observations. |
| consequences_and_impact | string | A summary of actual or potential effects on personnel, equipment, rescue operations, and mission outcomes. |
| evidence_and_uncertainty | string | An explanation of the source evidence for analytical conclusions, relationships between sources, and any missing, conflicting, or unverified information. |
| equipment_system_anomalies | string | Records of anomalies, damage, or failures involving ropes, connectors, anchors, protective devices, or other rescue systems. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- 19