# NTSB WPR12LA366: Piper PA-30 B, N222BP, Scappoose, OR, August 23, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 23, 2012, 16:30 local (23:30 UTC) - Place: Scappoose, OR - Coordinates: 45.769165, -122.856941 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.7692&lon=-122.8569&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 26, 2015 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 84779 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR12LA366 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/84779/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=84779 - Page: https://openairdocs.org/ntsb/WPR12LA366 ## Probable cause The failure of the landing gear to fully extend as a result of a failure of the landing gear transmission assembly for reasons that could not be determined based on the available evidence. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-30, 13 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103002), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Runway/land/takeoff/taxi surface: soft surface](https://openairdocs.org/ntsb-findings/03023020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-30, 1 case](https://openairdocs.org/ntsb-findings/03023020/cases.md?model=7103002), [All aircraft, 264 cases](https://openairdocs.org/ntsb-findings/03023020/cases.md) - [Landing gear system: landing gear actuator](https://openairdocs.org/ntsb-findings/01023233): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Piper PA-30, 1 case](https://openairdocs.org/ntsb-findings/01023233/cases.md?model=7103002), [All aircraft, 54 cases](https://openairdocs.org/ntsb-findings/01023233/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Piper PA-30, 8 cases](https://openairdocs.org/ntsb-events/330/sequence.md?model=7103002), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md) - [Landing-flare/touchdown: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-30, 8 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7103002), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) ## Analysis The pilot reported that the landing gear would not fully extend before landing. He attempted to extend the gear manually but was unsuccessful. The pilot decided to make a gear-up landing on the grass median next to the runway. During the landing, the airplane sustained substantial damage to the lower fuselage. A postaccident examination of the airplane revealed that there was a failure of the landing gear transmission assembly, which prevented the full extension of the nose landing gear. After the accident, the transmission was replaced, and the failed transmission was not retained for further testing, which precluded a determination of the reason for the failure of the landing gear to fully extend. ## Factual narrative On August 23, 2012, about 1630 Pacific daylight time (PDT), a Piper PA-30 B, N222BP, made a gear up landing at Scappoose Industrial Airpark, Scappoose, Oregon. The owner/pilot was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot was not injured; the airplane sustained substantial damage to the underbelly structure during the landing on the grass next to runway 33. The cross-country personal flight departed Vancouver, Washington, about 1600. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported that prior to landing, he lowered the landing gear, but it would not fully extend. He attempted to manually extend the gear but was unsuccessful. The pilot determined that due to his low fuel state he would perform a gear up landing. He elected to land on the soft infield grass adjacent to runway 33 versus on the runway itself in an attempt to minimize the damage to the airplane. After recovery of the airplane, it was determined that the lower fuselage had sustained substantial damage to the structure as a result of the soft ground ripping the aluminum sheet metal and belly frame structure. The airplane was secured for further examination of the landing gear. The airplane was examined by maintenance personnel and an inspector from the Federal Aviation Administration (FAA). During the examination, it was found that there was a failure of the landing gear transmission assembly, which prevented the extension of the nose landing gear. The landing gear transmission assembly was replaced, but the damaged assembly was not retained for further testing due to a miscommunication with the repair facility. ## Aircraft - Registration: [N222BP](https://openairdocs.org/deregistered/N222BP-2015-01-26), registration cancelled 2015-01-26, S/N 30-1510, built 1967 (OpenAirDocs) - Reported make and model: PIPER PA-30 B - Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs) - Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30-1510 - Airframe hours: 5656.5 - Engines: LYCOMING IO-320 SERIES 150 horsepower reciprocating; LYCOMING IO-320 SERIES 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 22, 2011, 141 hours before - Departed: VUO, Vancouver, WA - Destination: SPB, Scappoose, OR - Airport: SPB, Scappoose Industrial Airpark ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 38; injuries: none; private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; seat: left; flight hours: 774 total, 138 in this make and model, 580 as pilot in command, 130.3 in the last 90 days, 33.5 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 6 knots, gusting 16 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 68 °F, dew point 43 °F - Altimeter: 30.09 inHg - Observed at: SPB ## 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 20120823021359A](https://openairdocs.org/incident/20120823021359A), Aug 23, 2012: Piper PA-30, Scappoose, OR, Substantial damage. Pilot departed pearson field for Scappoose Industrial Airpark to refuel. Arriving at scappose the pilot attempted to lower the gear normally, but was… ## Docket (2 files) The files NTSB released with the investigation on March 6, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=84779. 1.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423209&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation- FAA Inspector (item 2, .PDF, 14 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423210&FileExtension=.PDF&FileName=Record%20of%20Conversation-%20FAA%20Inspector-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.