# NTSB CHI03LA230: Murch Rotec Rally 3, N317RE, Searcy, AR, July 24, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 24, 2003, 09:30 local (14:30 UTC) - Place: Searcy, AR - Coordinates: 35.239295, -91.730957 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.2393&lon=-91.7310&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 2, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 57573 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI03LA230 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57573/pdf - Page: https://openairdocs.org/ntsb/CHI03LA230 ## Probable cause The frayed rudder cable that failed during the turn to final. A factor was the ditch the airplane encountered during the forced landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, approach - vfr pattern - base leg/base to final - flt control syst,rudder control cable/rod - frayed (cause) - flt control syst,rudder control cable/rod - failure (cause) - Forced landing, emergency descent/landing - On ground/water encounter with terrain/water, emergency landing - terrain condition - ditch (contributing factor) ## Analysis The experimental amateur-built airplane sustained substantial damage during a forced landing following an in-flight rudder cable failure. The pilot stated, " As I made my turn south (Final) applying right rudder the right rudder cable broke. Because of pressure being applied to both rudder pedals I inadvertently applied left rudder causing the aircraft to go into a death spiral. I applied full right [ailerons] but continued to spiral after three to five rotations I used basic spin recovery and was able to level the aircraft and maintain minimal control at about 250 ft [above ground level]. I landed in an empty lot which was not quite long enough for roll out and came to rest in a ditch ... ." Examination of the failed cable revealed the ends of the separation were frayed. ## Factual narrative On July 24, 2003, about 0930 central daylight time, an experimental amateur-built Murch Rotec Rally 3, N317RE, piloted by a private pilot, sustained substantial damage during a forced landing following an in-flight rudder cable failure near Searcy, Arkansas. The personal flight was operating under 14 CFR part 91. Visual meteorological conditions prevailed at the time of the accident. No flight plan was on file. The pilot reported no injuries. The local flight departed from Searcy Municipal Airport, near Searcy, Arkansas, and was maneuvering in the traffic pattern at the time of the accident. The pilot stated: It was a cool, calm summer morning for July in Arkansas. I departed Searcy Municipal Airport (SRC) at 9:30 AM. The departure was to the south. I made a right hand turn to the west. Remaining in the traffic pattern at 1250 ft [mean sea level] I made a second turn to the right heading north. Just after turning east (base) I heard on my radio that a twin Jet was on its way in for landings at Searcy. I slowed and lingered on base for separation. As I made my turn south (Final) applying right rudder the right rudder cable broke. Because of pressure being applied to both rudder pedals I inadvertently applied left rudder causing the aircraft to go into a death spiral. I applied full right [ailerons] but continued to spiral after three to five rotations I used basic spin recovery and was able to level the aircraft and maintain minimal control at about 250 ft [above ground level]. I landed in an empty lot which was not quite long enough for roll out and came to rest in a ditch ... . A Federal Aviation Administration inspector examined the rudder cable separation. The cable separation appeared frayed. ## Aircraft - Registration: [N317RE](https://openairdocs.org/deregistered/N317RE-2006-04-07), registration cancelled 2006-04-07, S/N 25186, built 1983 (OpenAirDocs) - Reported make and model: Murch Rotec Rally 3 - Registry model: [Murch John ROTEC RALLY 3](https://openairdocs.org/model/murch-john-rotec-rally-3) (registry code 05675JY) (OpenAirDocs) - Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 25186 - Airframe hours: 275 - Engines: Rotax 503 48 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Kenneth H. Stump - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Continuous airworthiness, March 11, 2003, 25 hours before - Departed: SRC, Searcy, AR - Destination: SRC, Searcy, AR - Airport: SRC, Searcy Muni, runway 19, 5,007 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 42; injuries: none; private; airplane ratings: single-engine land; medical: class 1, valid medical--no waivers/lim.; last flight review December 15, 2001; seat: left; flight hours: 60 total, 60 in this make and model, 950 as pilot in command, 55 in the last 90 days, 45 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 4 knots - Visibility: 8 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 72 °F - Altimeter: 30.20 inHg - Observed at: SRC, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20030724021409A](https://openairdocs.org/incident/20030724021409A), Jul 24, 2003: Amtr RALLY3, Searcy, AR, Substantial damage. (-23) On July 24, 2003, at 09:30 CDT, a rotec rally 3, N317RE, lost directional control while maneuvering for landing in the traffic pattern for the Searcy… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.