# NTSB SEA99LA040: Piper PA-12, N4328X, Salem, OR, March 6, 1999 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: March 5, 1999, 16:30 local (Mar 6, 1999, 00:30 UTC) - Place: Salem, OR - Coordinates: 45.010055, -122.909072 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.0101&lon=-122.9091&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report June 21, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 45861 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA99LA040 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/45861/pdf - Page: https://openairdocs.org/ntsb/SEA99LA040 ## Probable cause The pilot-in-command's misjudgment of distance/altitude on final approach, and overload of the left main landing gear. A factor was the embankment at the end of the landing strip. ## Analysis The pilot reported that 'while practicing [a] short field approach, I landed a little shorter than planned.' The aircraft impacted the up-sloping terrain short of the threshold to the pilot's 900 foot long, turf landing strip and nosed over, coming to rest approximately 18 feet beyond the gear contact with the up-sloping edge. The left main landing gear folded aft upon ground impact. ## Factual narrative On March 5, 1999, approximately 1630 Pacific standard time, a Piper PA-12, N4328X, registered to and being flown by a private pilot, was substantially damaged when the aircraft impacted sharply up-sloping terrain just short of the landing threshold at the pilot's personal, non-airspaced landing strip near Salem, Oregon. The aircraft was on a short final approach, landing to the south, when the main gear impacted the terrain and collapsed. The aircraft then nosed over. The pilot sustained minor injuries. Visual meteorological conditions prevailed, and no flight plan had been filed. The flight, which was personal, was to have been operated under 14CFR91, and originated from Salem approximately 1610. The pilot reported that "while practicing [a] short field approach, I landed a little shorter than I planned. The landing wheels contacted the very end of the runway, which caused the nose to make contact on the grass strip, and [the plane] flipped over on its back. " The pilot stated that there was no mechanical malfunction with the aircraft at the time. An inspector with the Federal Aviation Administration's Hillsboro Flight Standards District Office examined the aircraft and accident site/landing strip. He reported that the landing strip was approximately 900 feet in length, 45 feet in width, and oriented along a north/south magnetic bearing (refer to DIAGRAM I). The landing surface was grass and the north end of the strip descended sharply approximately 20 feet (vertical height) to lower terrain (refer to photograph 1). Marks in the soil at the crest of the up-sloping edge of the runway's north threshold matched the distance between the main landing gear, and were consistent with a gear impact (refer to photograph 2). The aircraft was observed to be inverted at a point approximately 18 feet beyond the main gear impact at the up-sloping north end, and displayed extensive aftward left main landing gear deformation(refer to photograph 3). ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Engine tearaway, approach - vfr pattern - final approach - distance/altitude - misjudged, pilot in command (cause) - Gear collapsed, approach - vfr pattern - final approach - landing gear,main gear - overload (cause) - terrain condition - drop-off/descending embankment (contributing factor) - Nose over, approach - vfr pattern - final approach ## Aircraft - Registration: [N4328X](https://openairdocs.org/aircraft/N4328X), registered now, S/N 12144, built 1946 (OpenAirDocs) - Reported make and model: Piper PA-12 - Registry model: [Piper PA-12](https://openairdocs.org/model/piper-pa-12) (registry code 7101202) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 12144 - Airframe hours: 4049 - Engines: Lycoming O-320 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Stuart, Donald, L. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 23, 1998, 4 hours before - Departed: AURORA, OR - Airport: runway 18, 900 × 45 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 72; private; airplane ratings: single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: front; flight hours: 1,900 total, 25 in this make and model, 1,900 as pilot in command, 25 in the last 90 days, 4 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 350° at 7 knots - Visibility: 10 statute miles - Temperature: 43 °F, dew point 34 °F - Altimeter: 30.00 inHg - Observed at: SLE, 7 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 19990306002069A](https://openairdocs.org/incident/19990306002069A), Mar 6, 1999: Piper PA12, Salem, OR, Substantial damage. Acft flipped over after landing. Other circumstances are unknown. (-23) it appears that while attempting to land on a private air strip, the a/c's landing… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; 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.