- Date
- May 8, 2014, 22:50 local (May 9, 2014, 02:50 UTC)
- Place
- Brooksville, FL
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N8683WPiper PA-28-235
- Defining event
- Landing-flare/touchdown: Abnormal runway contact
- Weather
- Visual (VMC) · Night
- Status
- Completed · report February 4, 2015
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20140508009549A
- Case key
- 89231
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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 · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
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
- Reported as
- Piper PA-28-235
- Category
- Airplane
- Serial number
- 28-10215
- Built
- 1964
- Airframe hours
- 2,663
- Engine
- 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
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew · 2
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 67
- Injuries
- None
- Certificates
- 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
- Role
- Pilot-rated passenger
- Age
- 59
- Injuries
- None
- Certificate
- 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
Docket · 4
The files NTSB released with the investigation on December 31, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.4 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N8683W · 1
Matched to the same aircraft by N-number and date.