# NTSB ERA12CA190: Piper PA-32R-300, N47863, Swainsboro, GA, February 18, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 17, 2012, 19:30 local (Feb 18, 2012, 00:30 UTC) - Place: Swainsboro, GA - Coordinates: 32.609165, -82.370002 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.6092&lon=-82.3700&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: No injuries - Injuries: 7 uninjured - Status: Completed, report July 18, 2012 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 82946 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA12CA190 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/82946/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=82946 - Page: https://openairdocs.org/ntsb/ERA12CA190 ## Probable cause The pilot’s failure to maintain the proper glidepath during final approach in night visual meteorological conditions, which resulted in a collision with trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Perception/orientation/illusion: perception](https://openairdocs.org/ntsb-findings/02022040): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Piper PA-32R-300, 1 case](https://openairdocs.org/ntsb-findings/02022040/cases.md?model=7103213), [All aircraft, 61 cases](https://openairdocs.org/ntsb-findings/02022040/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32R-300, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7103213), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-32R-300, 10 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7103213), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis The pilot reported that the airplane was approaching the destination airport on the base leg of the traffic pattern in night visual meteorological conditions. At that time, the runway lights were set on high intensity, which diluted the threshold lights. Additionally, the pilot stated that the red localizer antenna hazard lights distracted him (they were located about 750 feet before the runway threshold). He further stated that he was too low and struck trees during final approach. The airplane impacted trees with both wings about 2,400 feet before the runway threshold. The impact with trees resulted in damage to the left wing spar, lower fuselage, and the stabilator. The pilot stated that there were no preimpact mechanical malfunctions with the airplane. Following the accident, the airport manager checked all runway lighting and found them to be operational. ## Factual narrative The pilot reported that the airplane was approaching the destination airport on a base leg of the traffic pattern in night visual conditions. At that time, the runway lights were set on high intensity, which diluted the threshold lights. Additionally, the red localizer antenna hazard lights were distracting. The pilot further stated that he was too low and struck trees during final approach; however, the airplane landed on the runway without further incident. The pilot added that there were no preimpact mechanical malfunctions with the airplane. A Federal Aviation Administration inspector stated that the airplane impacted trees with both wings about 2,400 feet prior to the runway threshold. The impact with trees resulted in damage to the left wing spar, lower fuselage, and the stabilator. The runway was 6,021 feet long and was equipped with a localizer approach, but was not equipped with an instrument landing system approach. The runway was also not equipped with a visual approach slope indicator. The red localizer antenna hazard lights were located about 750 feet prior to the runway threshold. Following the accident, the airport manager checked all runway lighting and found them to be operational. ## Aircraft - Registration: [N47863](https://openairdocs.org/deregistered/N47863-2019-01-28), registration cancelled 2019-01-28, S/N 32R-7880025, built 1977 (OpenAirDocs) - Reported make and model: PIPER PA-32R-300 - Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32R-7880025 - Engines: LYCOMING IO-540 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Ronnie Osburn - Registered owner: All Pro Auto Parts Inc - Airworthiness certificate: Standard, Normal - Departed: GIF, Winter Haven, FL - Destination: SBO, Swainsboro, GA - Flight plan: IFR - Airport: SBO, Emanuel County Airport, runway 31, 6,021 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review April 23, 2011; seat: left; flight hours: 4,500 total, 300 in this make and model, 4,000 as pilot in command, 15 in the last 90 days, 5 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 54 °F, dew point 52 °F - Altimeter: 30.06 inHg - Observed at: SBO ## 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 20120217001999A](https://openairdocs.org/incident/20120217001999A), Feb 17, 2012: Piper PA-32R-300, Swainsboro, GA, Substantial damage. On February 18, 2012, this office was notified by the regional operations center (roc) at 11:30 am local time about an event involving a Piper PA-32-300… ## Other investigations on N47863 (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 ERA18LA070](https://openairdocs.org/ntsb/ERA18LA070), Jan 25, 2018: Piper PA32R (N47863), Marathon, FL, substantial damage. Probable cause: The pilot's failure to maintain directional control during takeoff. ## Docket (4 files) The files NTSB released with the investigation on May 24, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=82946. 716 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 515 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363765&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Interview Summary FAA Inspector (item 2, .PDF, 51 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363766&FileExtension=.PDF&FileName=Interview%20Summary%20FAA%20Inspector-Master.PDF - Weather Report (item 3, .PDF, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363767&FileExtension=.PDF&FileName=Weather%20Report-Master.PDF - Photo: Damage to Left Wing (Photo Courtesy of FAA) (item 4, .PDF, 133 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363768&FileExtension=.PDF&FileName=Photo%3A%20%20Damage%20to%20Left%20Wing%20(Photo%20Courtesy%20of%20FAA)-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.