# NTSB WPR12CA299: Bellanca 17-30, N7322V, Hillsboro, OR, July 6, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 6, 2012, 14:10 local (21:10 UTC) - Place: Hillsboro, OR - Coordinates: 45.428333, -122.941947 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.4283&lon=-122.9419&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 4, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 84245 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR12CA299 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/84245/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=84245 - Page: https://openairdocs.org/ntsb/WPR12CA299 ## Probable cause The pilot’s failure to maintain directional control during landing, which resulted in a runway excursion and collision with an airport lighting system. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Bellanca 17-30, 3 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=1220432), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [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 17-30, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=1220432), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Bellanca 17-30, 1 case](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=1220432), [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. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Bellanca 17-30, 3 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=1220432), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Bellanca 17-30, 3 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=1220432), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); cases with it: [Bellanca 17-30, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=1220432), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The pilot stated that he configured the airplane for landing and touched down with the main landing gear contacting the surface first. The airplane continued a normal landing roll until the nose gear touched down, at which point the airplane veered sharply to the left. The pilot manipulated the rudder pedals in an attempt to regain directional control, but the airplane continued to the left. Despite his efforts, the airplane collided with the visual approach slope indicator lighting system, sustaining substantial damage to the left wing. A postimpact examination of the nose gear showed no evidence of mechanical malfunctions or failures that would have precluded normal operation. ## Factual narrative The pilot stated that he configured the airplane for landing and touched down with the main landing gear contacting the surface first. The airplane continued a normal landing roll until the nose gear touched down, at which point the airplane made a sharp veer to the left. The pilot manipulated the rudder pedals in an attempt to regain directional control, but the airplane continued to the left. Despite his efforts, the airplane collided with the Visual Approach Slope Indicator (VASI) lighting system, sustaining substantial damage to the left wing. A Federal Aviation Administration Airworthiness inspector performed a post impact examination of the nose gear and found no evidence of mechanical malfunctions or failures that would have precluded normal operation. ## Aircraft - Registration: [N7322V](https://openairdocs.org/aircraft/N7322V), registered now, S/N 30177, built 1968 (OpenAirDocs) - Reported make and model: BELLANCA 17-30 - Registry model: [Bellanca 17-30](https://openairdocs.org/model/bellanca-17-30) (registry code 1220432) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30177 - Engines: CONT MOTOR IO 520 SERIES 285 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: TTD, Troutdale, OR - Destination: HIO, Hillsboro, OR - Flight plan: Unknown - Airport: HIO, Portland-Hillsboro Airport, runway 31, 6,600 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 62; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; flight hours: 3,750 total, 750 in this make and model ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none ## 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 20120706012439A](https://openairdocs.org/incident/20120706012439A), Jul 6, 2012: Bellanca 17-30, Hillsboro, OR, Substantial damage. After N7322V touched down on the centerline of runway 31 at Portland Hillsboro airport, it immediately departed the left border of the runway into the adjacent… ## Docket (2 files) The files NTSB released with the investigation on August 2, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=84245. 4.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40373730&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Federal Aviation Administration (FAA) Inspector Statement (item 2, .PDF, 27 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40373731&FileExtension=.PDF&FileName=Federal%20Aviation%20Administration%20(FAA)%20Inspector%20Statement-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.