The U.S. aircraft register, updated daily
Accidents · NTSB IAD02LA048 · Final report

Burkhart Grob G103 accident near Fairfield, Pennsylvania, May 5, 2002

On May 5, 2002 at about 4:10 pm local time, a Burkhart Grob G103 (glider), registered N5364G, was substantially damaged in an accident near Fairfield, Pennsylvania (Mid-Atlantic Soaring Center airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to attain proper runway alignment. A factor in the accident was the pilot's delay in retracting the spoilers.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 5, 2002 · about 4:10 pm local time · cases in 2002
Place
Fairfield, Pennsylvania · Mid-Atlantic Soaring Center · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Burkhart Grob G103 · all G103s on the register
Registration
N5364G · registry record · serial 3865
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot completed a left traffic pattern to land on runway 33L, one of two parallel grass runways. He overshot the runway, and decided to land on runway 33R. He subsequently left the spoilers deployed for too long, and descended faster than expected. He attempted to align the glider with the runway, but was unable to level the wings prior to the left wing tip striking the ground. When asked about the performance of the glider, the pilot stated, "The glider performed fine. It was responding as designed. Unfortunately, the inputs were not correct."

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: rotorcraft: glider
  • Flight time: 214 hours in all; 4 in the last 90 days; 1 in the last 30 days; 166 as pilot in command
  • Last flight review: April 7, 2002
  • Medical certificate: None
  • Seat: frt
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,641 hours
  • Last inspection: annual inspection, December 18, 2001; 24 hours since
  • Maximum gross weight: 859 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Aero Engines; 0 hours total

The flight

  • Departed from: W73 Fairfield PA at 4:00 pm
  • Flight plan: none
  • Runway 33R, 2,700 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 55°F (13°C), dew point 45°F (7°C)
  • Altimeter: 30.32 inHg
  • Observation at 3:53 pm from HGR, 18 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/IAD02LA048.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.