# NTSB GAA19CA016: Piper PA24, N8220P, Winder, GA, October 4, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 4, 2018, 19:30 local (23:30 UTC) - Place: Winder, GA - Coordinates: 33.980278, -83.660835 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.9803&lon=-83.6608&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 8, 2019 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 98462 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA016 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98462/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98462 - Page: https://openairdocs.org/ntsb/GAA19CA016 ## Probable cause The pilot’s failure to maintain an adequate approach path at night after an electrical failure, which resulted in the airplane striking runway lights. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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-24-250, 4 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102404), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-24-250, 34 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102404), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Electrical power system](https://openairdocs.org/ntsb-findings/01022400): Aircraft › Aircraft systems · Inoperative; cases with it: [Piper PA-24-250, 1 case](https://openairdocs.org/ntsb-findings/01022400/cases.md?model=7102404), [All aircraft, 48 cases](https://openairdocs.org/ntsb-findings/01022400/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Effect on operation; cases with it: [Piper PA-24-250, 1 case](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=7102404), [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. - [Approach-VFR pattern final: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [Piper PA-24-250, 3 cases](https://openairdocs.org/ntsb-events/332/sequence.md?model=7102404), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) (defining event); cases with it: [Piper PA-24-250, 3 cases](https://openairdocs.org/ntsb-events/370/sequence.md?model=7102404), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-24-250, 55 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102404), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, during a night flight, while lowering the flaps for landing, the cockpit lights turned off. He attempted to turn the lights back on to no avail. He added that the precision approach path indicator (PAPI) lights were off and that he could not get the runway lights to turn on either. As he was landing past "the first arrow in front [chevron in the displaced threshold]," he heard a "thump." He taxied the airplane to the ramp without further incident. The passenger, an airframe and powerplant mechanic, reported that, during approach after the cockpit lights went out, he used his flashlight to light up the cockpit. He was unable to correct the panel lights but observed that the runway lights were "bright." He added that, during the landing, he felt the "bottom drop out" and that the airplane landed hard and bounced. Postaccident examination revealed that the right horizontal stabilator sustained substantial damage. The pilot added that he and the passenger went to the beginning of the approach runway and found pieces of broken runway lights. Archived NOTAMs for the date of the accident stated that: RWY 31 PAPI UNUSABLE ## Factual narrative The pilot reported that, during a night flight, while lowering the flaps for landing, the cockpit lights turned off. He attempted to turn the lights back on, to no avail. He added that the precision approach path indicator (PAPI) lights were off, and he could not get the runway lights to turn on either. As he was landing past "the first arrow in front [chevron in the displaced threshold]", he heard a "thump". He taxied to the ramp without further incident. The passenger, an airframe and powerplant mechanic, reported that, during approach after the cockpit lights went out, he used his flashlight to light up the cockpit. He was unable to correct the panel lights but observed that the runway lights were "bright". He added that, during the landing, he felt the "bottom drop out" and the airplane landed hard and bounced. Postaccident examination revealed that the right horizontal stabilator sustained substantial damage. The pilot added that he and the passenger went to the beginning of the approach runway and found pieces of broken runway lights. Archived Notices to Airmen (NOTAMs) for the date of the accident stated that: RWY 31 PAPI UNUSABLE ## Aircraft - Registration: [N8220P](https://openairdocs.org/aircraft/N8220P), registered now, S/N 24-3473, built 1963 (OpenAirDocs) - Reported make and model: Piper PA24 (250) - Registry model: [Piper PA-24-250](https://openairdocs.org/model/piper-pa-24-250) (registry code 7102404) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 24-3473 - Year built: 1963 - Airframe hours: 5145.31 - Engines: Lycoming O-540-A1D5 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 14, 2018 - Departed: WDR, Winder, GA - Destination: WDR, Winder, GA - Airport: WDR, Barrow County, runway 31, 5,500 × 100 ft, asphalt - Equipment: Stall warning system, Auto-pilot, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 72; injuries: none; private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review December 16, 2017; seat: left; restraint: lap only; flight hours: 1,226.5 total, 40.2 in this make and model, 181.1 as pilot in command, 8.6 in the last 90 days, 2.4 in the last 30 days ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 68 °F - Altimeter: 30.10 inHg - Observed at: KWDR ## Other investigations on N8220P (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 NYC67D0533](https://openairdocs.org/ntsb/NYC67D0533), Feb 22, 1967: Piper PA-24 (N8220P), West Chester, PA, substantial damage ## Docket (4 files) The files NTSB released with the investigation on February 6, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98462. 4.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470066&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Passenger's Statement (item 2, .PDF, 136 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470067&FileExtension=.PDF&FileName=Passenger%27s%20Statement-Master.PDF - Archived NOTAMs (item 3, .PDF, 102 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470068&FileExtension=.PDF&FileName=Archived%20NOTAMs-Master.PDF - Accident Photo (item 4, .PDF, 1 photo, 759 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470069&FileExtension=.PDF&FileName=Accident%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.