NTSB CAROL · Event
Event WPR13LA310
Aircraft involved
Probable cause & findings
The pilots’ failure to follow the airplane manufacturer’s emergency procedures for a hydraulic system failure and emergency braking, which resulted in the loss of braking action upon landing and the subsequent loss of directional control while turning off the runway. Contributing to the accident was the loss of hydraulic pressure for reasons that could not be determined because postaccident testing and examination of the hydraulic system revealed no mechanical failures or anomalies that would have precluded normal operation.
Factual narrative
On July 5, 2013, about 1845 Pacific daylight time, a Rockwell International Corporation NA-265-65, Mexican registered XB-RSC, sustained substantial damage following a reported loss of control while taxiing at the McCarran International Airport (LAS) Las Vegas, Nevada. The airplane was registered to and operated by Eseasa Contrucciones, S. A. de C. V., under the provisions of Title 14 Code of Federal Regulations Part 91. The captain, first officer, and four passengers were not injured. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed for the personal flight which originated from Brownsville, Texas about 1755, central daylight time. The pilots reported that about 20 miles from the airport, the main hydraulic system lost pressure. They selected the auxiliary hydraulic system and continued the approach. During the landing roll, about two thirds down the runway, the pilots noticed that the brakes were not working normally and turned onto a taxiway to clear the runway. Once on the taxiway, the captain reported he was unable to stop or steer the airplane as it proceeded across a parallel runway and then into an adjacent grass field where it subsequently struck a metal beam located within a drainage area. Examination of the airplane wreckage by a Federal Aviation Administration Inspector revealed that the left wing was substantially damaged. The airplane was recovered to a secure storage facility for further examination. A review of the airplane's emergency procedures for Hydraulic Pressure or Hydraulic Caution Light On, revealed that the electrically driven hydraulic pump should be reset and if the hydraulic pressure does not return to normal, to select the hydraulic pump to "off," and use the emergency gear lowering procedures to extend the landing gear. After the gear is emergency extended, the hydraulic auxiliary pump should be selected "on" for landing. The flight crew stated that they did not attempt to reset the hydraulic pump and accomplished the emergency landing gear extension procedures with the auxiliary hydraulic pump engaged. Upon landing, the flight crew stated that they activated the emergency brake switch on the runway. The airplane's emergency procedures state when using emergency braking, as soon as the airplane is brought safely to a stop, that the flight crews should request towing assistance. The procedures also state that the number of brake applications available to the crew is dependent on the accumulator charge and may be depleted in a very short time. The landing runway was 10,525 feet in length, 150 feet wide, and had a 0.9 % uphill gradient. The flight crew did not bring the airplane to complete stop on the runway but taxied off the runway at an intersection, with about 3,900 feet of runway remaining. A postaccident examination of the airplane, revealed brake system continuity with the cockpit controls. The tires, brake assemblies, and brake pads were intact and undamaged. The hydraulic lines from the hydraulic pump to the wheel brakes were intact. No hydraulic fluid was observed leaking on the exterior or interior portions of the airplane. Further, the external portions of the brake assemblies were not contaminated with hydraulic fluid. The hydraulic reservoir quantity was observed low in fluid and about ¼ full. According to the airplane's maintenance manual, the reservoir maximum capacity was two gallons. The reservoir fluid was observed to be dark red/brown in color and had a musky burnt scent. A sample of the reservoir hydraulic fluid was sent to the National Transportation Safety Board Materials (NTSB) laboratory for analysis. The analysis of the hydraulic fluid revealed that the acid level was degraded beyond the normal range expected for this type of fluid but not to a critical level. Reference the Material Laboratory Factual Report in the public docket for additional information. The two hydraulic pumps were removed and sent to their respective manufacturer for a functional check. Examination and functional checks of both hydraulic pumps revealed that they operated normally. No mechanical failures or anomalies that would preclude normal operation were noted. The airplane's cockpit voice recorder (CVR) was sent to the NTSB Vehicle Recorder Division for readout. The recording of the accident flight was not present and consistent with the CVR being inoperative prior to the accident. The pilots reported that, during the approach, the main hydraulic system lost pressure. They selected the auxiliary hydraulic system "on," continued the approach, and extended the landing gear using the emergency landing gear extension procedures. During the landing roll, about two-thirds down the runway, the pilots noticed that the brakes were not working normally and then turned onto a taxiway to clear the runway. The captain reported that, once on the taxiway, he was unable to stop or steer the airplane as it proceeded across a parallel runway and into an adjacent field where it subsequently struck a metal beam. A postaccident examination of the airplane revealed brake system continuity with the cockpit controls. The tires, brake assemblies, and brake pads were intact and undamaged. The hydraulic lines from the hydraulic pump to the wheel brakes were intact. No hydraulic fluid was observed leaking on the exterior or interior portions of the airplane. The hydraulic fluid reservoir was found about 1/4 full. Further, testing of the two hydraulic pumps revealed that they were both functional, and no mechanical failures or anomalies that would have precluded normal operation were noted. The airplane's hydraulic system failure emergency procedures state that, if hydraulic pressure is lost, the electrically driven hydraulic pump should be reset and that, if the hydraulic pressure was not restored, that the primary hydraulic system should be disengaged and the landing gear should be lowered using the emergency landing gear extension procedures. After the gear is extended, the auxiliary hydraulic system should be selected "on" for landing. However, the pilots stated that they did not attempt to reset the electric hydraulic pump and that they performed the emergency landing gear extension procedures with the auxiliary hydraulic pump engaged. It is likely that the pilots' failure to select the auxiliary hydraulic system "off" before extending the landing gear caused the hydraulic pressure in the auxiliary system to dissipate, which left only the emergency brake accumulator available for braking during the landing. The number of emergency brake applications that can be made by the pilots depends on the accumulator charge, which may be depleted in a very short time. The airplane's emergency braking procedures state that, as soon as the airplane is safely stopped, the pilots should request towing assistance. However, the pilots did not stop the airplane on the runway despite having about 3,900 ft of runway remaining; instead, they turned off the runway at an intersection, which resulted in a loss of directional control. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Flight crew - C
- C Personnel issues-Task performance-Use of equip/info-Use of policy/procedure-Flight crew - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Flight crew - C
- F Not determined-Not determined-(general)-(general)-Unknown/Not determined - F
- — Environmental issues-Physical environment-Object/animal/substance-(general)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2013_WPR13LA310.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
Browse the full corpus — academia portal ↗