# NTSB MIA01LA092: Bellanca BL-17-30A, N8844V, Sylacauga, AL, March 4, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: March 4, 2001, 11:15 local (17:15 UTC) - Place: Sylacauga, AL - Coordinates: 33.175277, -86.309165 - Nearby events: https://openairdocs.org/map.md?lat=33.1753&lon=-86.3092&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 30, 2001 - Report: Approved by Office Director - Parties: FAA - NTSB case key (mKey): 51868 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA01LA092 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/51868/pdf - Page: https://openairdocs.org/ntsb/MIA01LA092 ## Probable cause The pilot's failure to maintain directional control during landing rollout, and the subsequent runway excursion and collision with trees. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - directional control - not maintained, pilot in command (cause) - On ground/water collision with object, landing - roll - object - tree(s) ## Analysis Tfhe aircraft landed runway 27 in winds that were being reported as from 230-degrees at 15 knots, gusting to 21 knots. The aircraft touched down and immediately began leaving rubber streaks on the runway from all three tires. The aircraft departed the runway surface at about a 45-degree angle, and collided with trees located about 50 feet from the runway edge. Postcrash examination of the aircraft revealed no precrash mechanical malfunctions of the steering system or braking system. ## Factual narrative On March 4, 2001, about 1115 central standard time, a Bellanca BL-17-30A, N8844V, registered to a private individual, operating as a Title 14 CFR Part 91 personal flight, sustained a runway excursion on landing at Merkel Field Sylacauga Municipal Airport, Sylacauga, Alabama. Visual meteorological conditions prevailed and no flight plan was filed. The private-rated pilot and a passenger were not injured, and the aircraft sustained substantial damage. The flight departed Mobile, Alabama, about 0915. According to the pilot, his landing touchdown on the main gear was smooth, and when he lowered the nosewheel onto the runway, the aircraft took a violent swerve to the left, and departed the left runway edge. Once in the wet grass, he started sliding and his rudder pedals had no effect on steering. The aircraft collided with a stand of pine trees, and sustained a collapsed nose landing gear and wing collision damage. The pilot stated that, "I suspect that a steering collar or steering rod failed, but I was unable to check due to the collapsed nose gear." According to an FAA inspector, runway tire marks revealed that the aircraft landed on runway 27 and ran off the runway surface's left edge at a 45-degree angle. He stated, "There were three skid marks on the runway from each of the landing gear tires for almost 100 feet. With all three landing gear skid marks, the pilot was applying heavy braking. The nose tire skid marks indicate that the nose of the aircraft was being forced into the ground." The aircraft continued through adjacent grass until colliding with trees located about 50 feet from the left runway edge. According to an aircraft inspector on the field, he examined the wreckage for possible precrash mechanical malfunctions of the braking and steering systems. He stated the type of damage he observed to the steering collar and steering rods could only have occurred postcrash. Examination of the nose tire streak on the runway indicated that the aircraft was being subjected to some amount of nose down pitch forces. ## Aircraft - Registration: [N8844V](https://openairdocs.org/deregistered/N8844V-2004-03-04), registration cancelled 2004-03-04, S/N 30368, built 1971 (OpenAirDocs) - Reported make and model: Bellanca BL-17-30A - Registry model: [Bellanca 17-30A](https://openairdocs.org/model/bellanca-17-30a) (registry code 1220433) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30368 - Airframe hours: 2649 - Engines: Continental IO-520K 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 22, 2000, 20 hours before - Departed: MOB, Mobile, AL - Destination: SCD, Sylacauga, AL - Airport: SCD, Merkel Sylacagua, runway 27, 5,390 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review December 10, 2000; seat: left ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 15 knots, gusting 21 - Visibility: 10 statute miles - Lowest ceiling: 3,100 ft overcast - Temperature: 54 °F, dew point 45 °F - Altimeter: 29.96 inHg - Observed at: ANB, 39 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 20010304003699A](https://openairdocs.org/incident/20010304003699A), Mar 4, 2001: Blanca 1730A, Sylacauga, AL, Substantial damage. (-23) Pilot departed mobile regional for Sylacauga, Alabama. The winds at the time of the accident were gusty. The pilot landed the a/c at higher than normal… ## Other investigations on N8844V (1) 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. - [NTSB FTW74FRG99](https://openairdocs.org/ntsb/FTW74FRG99), Jun 24, 1974: Bellanca 17-30A (N8844V), Austin, TX, substantial damage 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.