Dg-Flugzeugbau GMBH DG-500MB accident near Richland, Washington, June 24, 2012
On June 24, 2012 at about 9:25 pm local time, a Dg-Flugzeugbau GMBH DG-500MB (glider), registered N505JL, was substantially damaged in an accident during approach (VFR pattern final) near Richland, Washington (Richland Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the spoilers to retract because the right wing spoiler’s lower plate became jammed, which resulted in the glider not having enough lift to make it to the runway surface.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 24, 2012 · about 9:25 pm local time · cases in 2012
- Place
- Richland, Washington · Richland Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Dg-Flugzeugbau GMBH DG-500MB
- Registration
- N505JL · registry record · serial 5E-187B3
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
In a written statement, the pilot reported that the accident flight was his second flight of the day. After conducting a series of practice maneuvers, he was returning to the airport. The pilot entered a right traffic pattern and configured the glider for landing. With the landing gear extended and the flaps set at 10 degrees, he opened and tested the spoilers. While on the base leg of the traffic pattern, he noticed that the glider was low, and, as he maneuvered onto final approach, he closed the spoilers (forward activation of the lever). The glider’s sink rate was excessive and he observed that the spoilers visually appeared to be deployed although the control lever was in the full-forward (closed) position. He manipulated the lever back and forth, which had no effect on the spoiler position. The glider impacted railroad tracks about 1,000 feet from the approach end of the runway and sustained substantial damage to the fuselage and wings in the accident sequence. A postaccident examination of the glider revealed that the right wing spoiler’s lower plate appeared to have been rubbing the aft spoiler bay wall until it scraped off the resin. It appeared to have scraped enough material off that it caught on a fabric seam (once sealed in the resin) and would not retract. In other words, the spoiler’s lower plate would not push past the catch due to the exposed fabric edge. The location of the scrape marks and the fabric seam put the spoilers at half extension, which is consistent with the lack of performance the pilot reported. The left wing spoiler’s lower plate bushings were tight, with no play.
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
What happened, in order
- Loss of lift during approach (VFR pattern final) defining event
The NTSB's findings
- cause Aircraft › Aircraft structures › Wing structure › Spoilers › Unintentional use/operation other cases naming the airframe structure
- Aircraft › Aircraft structures › Wing structure › Spoilers › Fatigue/wear/corrosion other cases naming the airframe structure
Pilot
- Certificate: commercial pilot
- Ratings: instructor: glider; rotorcraft: glider
- Flight time: 1,303 hours in all; 311 in this make and model
- Medical certificate: None
- Injury: minor injuries
The aircraft
- Airframe total time: 878 hours
- Last inspection: annual inspection, November 22, 2011
- Seats: 2
- Landing gear: fixed
- Engine: Technoflug KS-1G-160-R-1 (piston); 0 hours total
- Operator: Sls Partnership LTD
The flight
- Departed from: RLD Richland WA at 9:15 pm
- Destination: RLD Richland WA
- Flight plan: not recorded
- Runway 26, 4,000 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 210° at 10 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 8,000 ft
- Temperature: 79°F (26°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on August 2, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Federal Aviation Administration Inspector Statement | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N505JL on the register today · the tail number may have moved to another aircraft since
- Engine: Technoflug KS-1G-160-R-1 · as the NTSB recorded it
- Richland Airport · nearest airport
- Accidents and incidents in Washington 2,713 since 1982 · 361 in the last ten years
- Washington 10,666 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR12CA288.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.
