# NTSB ERA14LA244: Piper PA-28-235, N8683W, Brooksville, FL, May 9, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 8, 2014, 22:50 local (May 9, 2014, 02:50 UTC) - Place: Brooksville, FL - Coordinates: 28.473611, -82.455558 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=28.4736&lon=-82.4556&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report February 4, 2015 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 89231 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14LA244 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89231/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89231 - Page: https://openairdocs.org/ntsb/ERA14LA244 ## Probable cause The pilot’s loss of directional control while landing at night, which resulted in a runway excursion and collision with airport signage. Contributing to the accident was the total loss of electrical power, which necessitated the pilot having to land without the aid of the airplane’s landing lights and some of the available runway lighting. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Electrical power system: alternator-generator drive sys](https://openairdocs.org/ntsb-findings/01022410): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Piper PA-28-235, 1 case](https://openairdocs.org/ntsb-findings/01022410/cases.md?model=7102810), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/01022410/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-28-235, 28 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102810), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Piper PA-28-235, 1 case](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=7102810), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/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: [Piper PA-28-235, 10 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102810), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-climb to cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [Piper PA-28-235, 1 case](https://openairdocs.org/ntsb-events/332/sequence.md?model=7102810), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Piper PA-28-235, 4 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7102810), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Piper PA-28-235, 9 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102810), [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: [Piper PA-28-235, 14 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102810), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that the flight departed about 2 hours after sunset and that, several minutes after departure, the airplane's lights began to dim. The pilot reduced the electrical load; however, within several minutes, the airplane lost all electrical power. The pilot chose to continue to the destination airport, which was located 21 nautical miles from the departure airport and was within sight. Upon reaching the airport, the pilot used the runway end identifier lights and the runway's visual approach slope indicator lights to guide the airplane to the runway threshold. Due to the lack of electrical power, he was unable to use the airplane's radio to activate the other available runway lighting or use the airplane's landing lights to help him further locate the runway after crossing the threshold. The pilot misjudged the airplane's height above the runway, and, during the landing flare from an estimated height of about 4 or 5 ft, the airplane impacted the runway. The airplane then veered right, departed the runway, struck an airport sign, and was substantially damaged. A postaccident examination revealed that the alternator had failed, which likely led to the airplane's total loss of electrical power. Review of the airplane's maintenance logs found that no maintenance related to the alternator had been documented in the airplane's 50-year and 2,600-flight-hour history. A survey of airports near the airplane's route of flight showed no continuously lighted airports located within a reasonable distance of the airplane's route. ## Factual narrative On May 8, 2014, about 2250 eastern daylight time, a Piper PA-28-235, N8683W, was substantially damaged while landing at Hernando County Airport (BKV), Brooksville, Florida. The airline transport pilot and the pilot-rated passenger were not injured. Night visual meteorological conditions prevailed, and no flight plan was filed for the flight that originated from Inverness Airport (INF), Inverness, Florida, about 2225. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. The pilots were returning to their home airport following dinner. The flight departed about two hours after sunset, and several minutes after departure, the airplane's lights began to dim. The pilot noted an abnormal current reading on the ammeter. With the destination airport in sight, and only about 20 minutes of flight remaining, the pilot reduced the electrical load; however, within several minutes all electrical power was lost. Upon reaching the destination airport, the pilot utilized the runway end identifier lights along with the runway's visual approach slope indicator lights to guide the airplane to the runway threshold. Without electrical power, he was unable to use the airplane's radio to activate the other available runway lighting, or utilize a landing light in order to help him further locate the runway after crossing the threshold. The pilot stated that he misjudged the airplane's height above the 7,002-foot-long by 150-foot-wide, concrete runway, and during the landing flare, the airplane impacted the runway from an estimated height of about 4 or 5 feet. Upon touchdown, the airplane veered right and struck a runway distance remaining sign, resulting in substantial damage to the horizontal stabilizer. The nose of the airplane then struck the ground, resulting in damage to the nose landing gear and firewall. The airplane's most recent annual inspection was completed in June 2013, and the airplane had accumulated about 5 flight hours since that time. The pilot, who was also an airframe and powerplant mechanic, examined airplane's electrical system following the accident and noted that the alternator had failed. He also noted during a review of the airplane's maintenance logs that the alternator appeared to have been originally installed in the airplane when it was newly manufactured, about 50 years and more than 2,600 flight hours prior to the accident flight. No maintenance to the alternator itself was documented in the logs. One maintenance log entry dated October 1979 documented the completion of an annual inspection and stated, "Repair alternator adjuster bracket." A survey of the airports located in the vicinity of the airplane's 20 nautical-mile route of flight showed that with the exception of two airports located within a mode-C veil surrounding a major international airport, the nearest continuously lighted airport was located nearly 90 nautical miles from the mid-point of the 21 nautical mile route. ## Aircraft - Registration: [N8683W](https://openairdocs.org/aircraft/N8683W), registered now, S/N 28-10215, built 1964 (OpenAirDocs) - Reported make and model: PIPER PA-28-235 - Registry model: [Piper PA-28-235](https://openairdocs.org/model/piper-pa-28-235) (registry code 7102810) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-10215 - Year built: 1964 - Airframe hours: 2663 - Engines: LYCOMING O-540-B4B5 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Papweb Corp - Registered owner: Papweb Corp - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 5, 2013, 5 hours before - Departed: INF, Inverness, FL - Destination: BKV, Brooksville, FL - Airport: BKV, Hernando County, runway 09, 7,002 × 150 ft, concrete - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 67; injuries: none; airline transport, flight instructor, commercial; airplane ratings: single-engine sea, single-engine land, multi-engine land; instrument ratings: helicopter, airplane; medical: class 2, with waivers/limitations; last flight review August 13, 2012; seat: right; restraint: lap only; flight hours: 7,049 total, 246 in this make and model, 2.5 in the last 90 days, 1 in the last 30 days - Pilot-rated passenger; age 59; injuries: none; private; airplane ratings: single-engine land; medical: class 3, unknown; seat: left; restraint: lap only; flight hours: 541 total, 374 in this make and model, 1.3 in the last 90 days, 0.6 in the last 30 days ## Weather - Conditions: Visual (VMC), Night - Wind: 90° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 66 °F - Altimeter: 30.18 inHg - Observed at: KBKV ## 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 20140508009549A](https://openairdocs.org/incident/20140508009549A), May 8, 2014: Piper PA-28-235, Brooksville, FL, Substantial damage. The pilot began losing lights inside the cockpit shortly after departing X40. The pilot elected to continue onward to bkv because it is longer, wider and has… ## Other investigations on N8683W (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 MIA67D0448](https://openairdocs.org/ntsb/MIA67D0448), Mar 19, 1967: Piper PA-28 (N8683W), Ft. Myers, FL, substantial damage ## Docket (4 files) The files NTSB released with the investigation on December 31, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89231. 2.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 913 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420502&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Photo 1 – View of Damage to Horizontal Stabilizer (Photo Courtesy of FAA) (item 2, .PDF, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420503&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20View%20of%20Damage%20to%20Horizontal%20Stabilizer%20(Photo%20Courtesy%20of%20FAA)-Master.PDF - Maintenance Log Excerpt (item 3, .PDF, 426 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420504&FileExtension=.PDF&FileName=Maintenance%20Log%20Excerpt-Redacted.PDF - Chart Showing Airplane’s Route and Nearest Continuously Lit Airport (item 4, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420505&FileExtension=.PDF&FileName=Chart%20Showing%20Airplane%E2%80%99s%20Route%20and%20Nearest%20Continuously%20Lit%20Airport-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.