# NTSB LAX06CA021: Dirks Glaser DG-300, N30AS, California City, CA, October 29, 2005 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: October 29, 2005, 15:20 local (22:20 UTC) - Place: California City, CA - Coordinates: 35.153057, -118.013885 - Nearby events: https://openairdocs.org/map.md?lat=35.1531&lon=-118.0139&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report February 28, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration - Van Nuys FSDO - NTSB case key (mKey): 62752 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX06CA021 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62752/pdf - Page: https://openairdocs.org/ntsb/LAX06CA021 ## Probable cause the pilot's inadvertent retraction of the gear and failure to deploy the spoilers, and his subsequent failure to attain a proper touchdown point. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - On ground/water encounter with terrain/water, landing - roll - spoiler extension - not performed, pilot in command (cause) - terrain condition - berm - gear retraction - inadvertent, pilot in command (cause) - proper touchdown point - not attained, pilot in command (cause) ## Analysis The pilot intentionally ground looped the glider and struck a berm after overshooting the desired touchdown point on the landing runway. The pilot was performing a high parasite drag maneuver on landing. On approach he realized that he would overshoot the first half of the runway and chose to land on the second half. The pilot reached for the spoiler handle, but by mistake pulled the gear handle instead and inadvertently retracted the gear. The glider touched down on the runway at approximately 70 knots. The pilot feared he would strike a berm at the end of the runway head on and intentionally ground looped the glider, striking the berm at a 90-degree angle to the left. The glider was destroyed, and the pilot received minor injuries. ## Factual narrative On October 29, 2005, about 1520 Pacific standard time, a Glaser Dirks DG-300, N30AS, ground looped and collided with terrain in California City, California. The private pilot was operating the glider under the provisions of 14 CFR Part 91. The pilot, the sole occupant, sustained minor injuries; the glider was destroyed. The local flight departed California City Airport about 1410. Visual meteorological conditions prevailed, and no flight plan had been filed. The approximate global positioning system (GPS) coordinates of the primary wreckage were 35 degrees 09 minutes north latitude and 118 degrees 00 minutes west longitude. In a written statement to the National Transportation Safety Board, the pilot stated that he intentionally ground looped the glider after attempting to land on the runway. The pilot was performing a high parasite drag maneuver on landing. On approach, he realized that he would overshoot the first half of the runway and chose to land on the second half. The pilot reached for the spoiler handle, but pulled the gear handle inadvertently retracting the gear. The glider touched down on the runway at approximately 70 knots. The pilot feared that he would strike a berm at the end of the runway head on, and intentionally ground looped the glider, striking the berm at a 90-degree angle to the left. The glider was destroyed, and the pilot received minor injuries. The pilot reported no mechanical malfunctions prior to the accident. ## Aircraft - Registration: [N30AS](https://openairdocs.org/deregistered/N30AS-2014-11-25), registration cancelled 2014-11-25, S/N 3E14, built 1984 (OpenAirDocs) - Reported make and model: Dirks Glaser DG-300 - Registry model: [Glaser Dirks DG 300](https://openairdocs.org/model/glaser-dirks-dg-300) (registry code 3802509) (OpenAirDocs) - Registry engine: [NONE](https://openairdocs.org/engine/none) (registry code 00000, none) (OpenAirDocs) - Category: Glider - Serial number: 3E14 - Airframe hours: 1133 - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: James L. Skydell - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Annual, April 1, 2005, 32 hours before - Departed: L71, California City, CA - Destination: L71, California City, CA - Airport: L71, California City Municipal, runway 6, 6,000 × 150 ft, dirt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: minor; private; airplane ratings: single-engine land; last flight review April 1, 2005; seat: center; flight hours: 692 total, 364 in this make and model, 11 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 8 knots - Visibility: 9 statute miles - Lowest ceiling: none - Temperature: 160 °F, dew point 111 °F - Altimeter: 30.10 inHg - Observed at: BFL, 68 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20051029027259A](https://openairdocs.org/incident/20051029027259A), Oct 29, 2005: Glaser DG300, California City, CA, Substantial damage. (-23) On October 29, 2005, at approximately 1458 hours PDT, the pilot [privacy data omitted] acting as pilot in command of N30AS, a DG300 single place… ## Other investigations on N30AS (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR10LA377](https://openairdocs.org/ntsb/WPR10LA377), Jul 31, 2010: Glaser Dirks DG300 (N30AS), Morgan, UT, substantial damage, 1 fatal. Probable cause: The pilot's failure to maintain adequate airspeed while maneuvering, which resulted in a stall/spin and ground impact. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.