NTSB CAROL · Event
Event ERA10LA387
Aircraft involved
Probable cause & findings
The unauthorized installation of a battery and associated wiring and electrical components, which resulted in an in-flight electrical fire of undetermined origin.
Factual narrative
On July 30, 2010 about 1450 eastern daylight time, a Schweizer 2-33A glider, N17965, was destroyed when it collided with trees and terrain following an in-flight fire and forced landing near Windsor, Virginia. The certificated private pilot suffered minor injuries. The glider was consumed in the subsequent post-crash fire. Visual meteorological conditions (VMC) prevailed, and no flight plan was filed for the local instructional flight which departed Garner Gliderport (3VA8), Windsor Virginia, about 1435 and was conducted under the provisions of 14 Code of Federal Regulations Part 91. In both a telephone interview and a written statement the pilot said that he had stopped flying airplanes several years earlier, but recently began training to add a glider rating to his certificate. On the morning of the accident, the pilot arrived at the gliderport to practice for a "check ride" that was scheduled for 1600 that afternoon. The pilot selected and installed a "Gel-cell" battery behind the forward pilot seat during the preflight inspection of the glider. The battery was used to power the radio in the instrument panel. The pilot completed a low-level, traffic pattern flight and was then towed to 3,000 feet msl for a second flight. The glider climbed to 3,400 feet about 5 miles from the gliderport where the pilot "smelled something." The pilot said the odor got stronger, he felt heat, looked behind him, and "saw fire in the back seat." The pilot then "put out all spoilers" to complete an emergency descent. During the descent, the cockpit filled with smoke, and the pilot opened the canopy to clear the smoke. The smoke cleared, but the increased airflow "caused the fire to worsen." The pilot completed a forced landing to trees short of the gliderport, and egressed the glider with only minor burns to the back of his head. The pilot held a private pilot certificate with a rating for airplane single-engine land. He reported 180 total hours of flight experience; 140 hours of which were in single engine airplanes, and 40 hours of which were in gliders. The pilot did not hold a current Federal Aviation Administration (FAA) medical certificate, but neither was he required to for glider flights. According to FAA and maintenance records, the glider was manufactured in 1973 and had accrued 1,545 total aircraft hours as of December 2, 2009, when the last annual inspection was completed. According an FAA safety inspector (airworthiness), examination of logbooks revealed the accident glider, and others in the soaring club fleet, had been modified to accommodate avionics and the batteries to power them. However, there were no logbook entries to reflect the work, or any FAA approval of the modifications. At 1853, the weather conditions reported at Suffolk County Airport (SFQ), 12 miles south of the accident site, included clear skies, 10 miles visibility, and winds from 040 degrees at 9 knots. The temperature was 30 degrees Celsius (C), the dewpoint 19 degrees C, and the altimeter setting was 29.91 inches of mercury. The glider was examined at the site on July 30, 2010, by FAA inspectors and all major components were accounted for at the scene. The glider rested upright in trees close to the ground, and the metal wings remained largely intact, though impact damaged. The fabric and wood-covered tubular metal frame was severely fire damaged. The battery and any recognizable electrical wiring was harvested and forwarded to the NTSB Materials Laboratory in Washington, DC, for examination at a later date. On October 7, 2010, the battery and associated wiring from the accident glider were examined by a fire and explosion expert in the NTSB materials laboratory, Washington, D.C. The battery sustained too much fire-related damage to identify any signs of arcing on the contacts. The wiring had significant fire related damage and most of the insulation had burned away. The wiring showed no signs of arcing with the exception of one small bead on the end of a single conductor. The other conductors within that strand showed no signs of arcing or electrical damage. There were some signs of narrowing and necking on a few of the conductor ends. The rest of the conductor ends demonstrated either melting or fractures consistent with mechanical damage. On the morning of the accident, the pilot arrived at the gliderport to practice for a check ride he was scheduled to take later that afternoon. The pilot, who was not a mechanic, selected and installed a "Gel-cell" battery behind the forward pilot seat during the preflight inspection of the glider. The battery was used to power the radio in the instrument panel. The pilot completed a low-level, traffic pattern flight and was then towed to 3,000 feet msl for a second flight. The glider climbed to 3,400 feet, about 5 miles from the gliderport, where the pilot smelled an unusual odor. The odor got stronger, he felt heat, and observed fire in the back seat. The pilot then deployed the spoilers and initiated an emergency descent. During the descent, the cockpit filled with smoke, and the pilot opened the canopy to clear the smoke. The smoke cleared, but the increased airflow exacerbated the fire. The pilot completed a forced landing to trees short of the gliderport, during which the glider sustained substantial damage in the ensuing post-crash fire. Examination of the glider by an NTSB fire and explosion expert could not determine the exact source of ignition in the battery or its associated wiring. Examination of the maintenance logbooks revealed that there were no entries for the work performed to install the electrical system, and neither was there any approval paperwork from the FAA pertaining to the modification. 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).
- C Aircraft-Aircraft systems-Electrical power system-Battery/charger-Malfunction - C
- C Personnel issues-Task performance-Maintenance-Modification/alteration-Maintenance personnel - C
Verbatim from NTSB's published report. Source file
NTSB_2010_ERA10LA387.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, 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.
- 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…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗