30 Jul 2010: SCHWEIZER SGS 2-33AK — TIDEWATER SOARING SOCIETY

30 Jul 2010: SCHWEIZER SGS 2-33AK (N17965) — TIDEWATER SOARING SOCIETY

No fatalities • Windsor, VA, United States

Probable cause

The unauthorized installation of a battery and associated wiring and electrical components, which resulted in an in-flight electrical fire of undetermined origin.

— NTSB Determination

Accident 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.

Contributing factors

  • cause Malfunction
  • cause Maintenance personnel

Conditions

Weather
VMC, wind 040/09kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.