NTSB CAROL · Event
Event ERA14LA244
Registry · N8683W
FAA Aircraft Registry record.
Make / Model
PIPER PA-28-235
Year of manufacture
1964 · 50 years old at event
Engine
LYCOMING 0-540 SERIES (250 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19631227
ADS-B equipped
Yes — Mode-S ABEF65
Registrant of record
MBP AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- F Aircraft-Aircraft systems-Electrical power system-Alternator-generator drive sys-Failure - F
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- — Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Effect on operation
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2014_ERA14LA244.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, runway excursion, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
Browse the full corpus — academia portal ↗