# NTSB WPR13CA362: Bellanca 7GCBC, N926BW, West Yellowstone, MT, August 1, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 1, 2013, 07:20 local (13:20 UTC) - Place: West Yellowstone, MT - Coordinates: 44.521667, -111.1175 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.5217&lon=-111.1175&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 5, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 87704 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13CA362 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87704/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87704 - Page: https://openairdocs.org/ntsb/WPR13CA362 ## Probable cause The pilot's failure to maintain directional control during the takeoff roll, which resulted in a runway excursion and a collision with an approach slope indicator system component. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Bellanca 7GCBC, 19 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=1220601), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Bellanca 7GCBC, 33 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=1220601), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Not specified; cases with it: [Bellanca 7GCBC, 1 case](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=1220601), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Bellanca 7GCBC, 26 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=1220601), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff-rejected takeoff: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); cases with it: [Bellanca 7GCBC, 4 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=1220601), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Takeoff-rejected takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Bellanca 7GCBC, 26 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=1220601), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot and the pilot-rated passenger planned to conduct a personal flight in the tailwheel-equipped airplane. The pilot was in the rear seat, and the passenger was in the front seat. The passenger did not have a tailwheel endorsement, but he planned to follow the pilot on the controls during the takeoff for familiarization purposes. During the takeoff roll when the airplane was approaching liftoff speed, the airplane made a rapid veeroff to the left. At that point, the pilot abandoned the takeoff, and made the conscious decision not to attempt to return to the runway, instead allowing the airplane to roll and decelerate on the grass/gravel beside the runway. That decision was based on the pilot's desire to avoid any potentially hazardous maneuvering or a ground loop. During the rollout, due to the pilot's inability to see directly ahead, the airplane struck the VASI (visual approach slope indicator) installation located about 1,300 feet down the runway, and offset about 145 feet from the runway centerline. The airplane sustained substantial damage to the left wing struts. The pilot stated that he did not believe that any mechanical malfunction or failure contributed to or caused the runway excursion, and that he could not rule out the possibility that he had inadvertently applied one wheel brake during the takeoff roll. ## Factual narrative The pilot and the pilot-rated passenger planned to conduct a personal flight in the tailwheel-equipped airplane. The pilot was in the rear seat, and the passenger was in the front seat. The passenger did not have a tailwheel endorsement, but he planned to follow the pilot on the controls during the takeoff for familiarization purposes. During the takeoff roll when the airplane was approaching liftoff speed, the airplane made a rapid veeroff to the left. At that point, the pilot abandoned the takeoff, and made the conscious decision not to attempt to return to the runway, instead allowing the airplane to roll and decelerate on the grass/gravel beside the runway. That decision was based on the pilot's desire to avoid any potentially hazardous maneuvering or a ground loop. During the rollout, due to the pilot's inability to see directly ahead, the airplane struck the VASI (visual approach slope indicator) installation located about 1,300 feet down the runway, and offset about 145 feet from the runway centerline. The airplane sustained substantial damage to the left wing struts. The pilot stated that he did not believe that any mechanical malfunction or failure contributed to or caused the runway excursion, and that he could not rule out the possibility that he had inadvertently applied one wheel brake during the takeoff roll. ## Aircraft - Registration: [N926BW](https://openairdocs.org/aircraft/N926BW), registered now, S/N 770-74, built 1974 (OpenAirDocs) - Reported make and model: BELLANCA 7GCBC - Registry model: [Bellanca 7GCBC](https://openairdocs.org/model/bellanca-7gcbc) (registry code 1220601) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 770-74 - Airframe hours: 3092 - Engines: Lycoming O-320-A2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 1, 2013, 3,092 hours before - Departed: KWYS, West Yellowstone, MT - Destination: KWYS, West Yellowstone, MT - Airport: KWYS, West Yellowstone, runway 19, 8,400 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; airline transport, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review June 7, 2013; seat: rear; flight hours: 7,100 total, 450 in this make and model, 6,960 as pilot in command, 50 in the last 90 days, 30 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 50 °F, dew point 45 °F - Altimeter: 30.20 inHg - Observed at: KWYS ## 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 20130801014789A](https://openairdocs.org/incident/20130801014789A), Aug 1, 2013: Bellanca 7GCBC, West Yellowston, MT, Substantial damage. On aug 1, 2013 at approximately 0720L at West Yellowstone, Montana airport (kwys), [privacy data omitted]PIC of N926BW (citabria 7GCBC), and a private pilot… ## Docket (5 files) The files NTSB released with the investigation on August 22, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87704. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398577&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Interview Summary - Pilot (item 2, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398580&FileExtension=.PDF&FileName=Interview%20Summary%20-%20Pilot-Master.PDF - Weather Reports and Records (item 3, .PDF, 137 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398579&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Front View of Airplane (FAA photo) (item 4, .PDF, 467 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398593&FileExtension=.PDF&FileName=Front%20View%20of%20Airplane%20(FAA%20photo)-Master.PDF - Side View of Wing and Struts (FAA photo) (item 5, .PDF, 868 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398594&FileExtension=.PDF&FileName=Side%20View%20of%20Wing%20and%20Struts%20(FAA%20photo)-Master.PDF 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.