FTW03LA154
2003-05-18 · Houston, Texas, United States · Minor · 1 aircraft · Status: Completed
Airport IWS
N2SM has since been reassigned. It is now registered to a different aircraft (LEARJET INC 31A, built 1991), which was not involved in this event.
Aircraft involved
Probable cause & findings
The severed hydraulic brake hoses induced a loss of braking action, which resulted in the pilot's failure to control the aircraft.
Factual narrative
On May 18, 2003, at approximately 0935 central daylight time, a Beech BE-300 twin-engine airplane, N2SM, registered to and operated by OSO-RIO LLC of Houston, Texas, was substantially damaged during a runway overrun while landing on Runway 33 at the West Houston Airport (IWS), near Houston, Texas. The airline transport pilot, who was the sole occupant of the airplane, received minor injuries. Visual meteorological conditions prevailed for the Title 14 Code of Federal Regulations Part 91 personal flight, and a flight plan was not filed. The flight departed William P. Hobby Airport (HOU) at approximately 0915. The 5,200-hour pilot stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that while on the base leg for IWS, the annunciator light for the "low-pitch stop" propeller system on the right side illuminated. The pilot pulled the circuit breaker and left it out, as per the pilot operating handbook (POH). During the landing-roll, the pilot encountered a severe yaw to the right. The pilot added power to the right engine and realigned the airplane down the centerline. He then applied brakes and reverse thrust. The pilot stated that " it felt like I had no braking action and then felt the right side grab and brake, but not the left." The combination of right side braking and the "right low-pitch stop" system malfunction caused considerable adverse yaw, jerking the plane to the right. The pilot applied power again and straightened the nose of the airplane. He then made the decision to initiate a go-around, but at this point did not have adequate airspeed or runway length to safely accomplish a go around. He applied the brakes again, and the airplane immediately yawed to the right again, at which time the pilot was unable to compensate before the airplane caught the edge of the 3,953 feet long by 75 feet wide asphalt runway. The airplane went into the grass, where the pilot attempted to control the direction of the airplane and bring it to a complete stop. The airplane continued pulling to the right until it was moving in a sideway direction in relation to the runway. The airplane came to rest in a bayou located approximately 20 feet beyond the departure end of Runway 33. The pilot exited the aircraft unharmed. An inspection of the airplane by the operator revealed the "right low-pitchstop" system was not completely assembled, and the left brake line was leaking fluid and appeared to have been ruptured. Examination of the hydraulic brake hoses from the left and right main landing gears was conducted by Materials Analysis, Inc., and revealed that both hoses appeared to have been damaged with a hand tool. There was no evidence to suggest that the damage was caused by foreign objects striking the hoses, such as runway debris picked up the tires. No evidence of progressive failure was found on any of the fracture faces. The aircraft overran the departure end of the runway while landing on Runway 33. The 5,200-hour pilot reported that while on the base leg, the annunciator light for the "low pitch stop" propeller system on the right side illuminated. The pilot pulled the circuit breaker and left it out, as per the pilot operating handbook (POH). During the landing-roll, the pilot encountered a severe yaw to the right. The pilot added power to the right engine and realigned the airplane down the centerline. He then applied brakes and reverse thrust. The pilot stated that " it felt like I had no braking action and then felt the right side grab and brake, but not the left." The combination of right side braking and the right low pitch system malfunction caused considerable adverse yaw, jerking the plane to the right. The pilot applied power again and straightened the nose of the airplane. He then made the decision to go around, but at this point did not have adequate airspeed or runway length to safely accomplish a go around. He applied the brakes again, and the airplane immediately yawed to the right again, at which time the pilot was unable to compensate before the airplane caught the edge of the runway. The airplane went into the grass, where the pilot attempted to control the direction of the airplane and bring it to a complete stop. Examination of the hydraulic brake hoses from the left and right main landing gears revealed that both hoses appeared to have been damaged with a hand tool. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_FTW03LA154.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…