NTSB CAROL · Event
Event LAX05LA064
Aircraft involved
Probable cause & findings
the pilot's failure to maintain the proper glidepath to avoid obstacles and terrain.
Factual narrative
On January 12, 2005, at 1438 Pacific standard time, a Lancair 235, N124JH, collided with a fence while on final approach for landing at Gillespie Field, El Cajon, California. The commercial pilot/owner operated the airplane under the provisions of 14 CFR Part 91. The pilot was fatally injured and the passenger was seriously injured; the airplane was substantially damaged. Visual meteorological conditions prevailed, and a flight plan had not been filed. The flight originated in Yuma, Arizona, about 1330. A witness driving a pickup truck told the National Transportation Safety Board investigator that she saw the airplane cross in front of her truck about 10 feet above the ground going very fast and low. Immediately after the airplane crossed her path, it struck the airport boundary fence with the right main landing gear, and impacted the dirt terrain beyond. The airport manager said that the wreckage was about 500 feet from the approach end of runway 27 right, and about 1,800 feet from the runway's displaced threshold. The passenger of the airplane stated that this was her first flight with the pilot. She recalls that the flight was very pleasant, and the pilot did not express any concerns regarding the airplane or the environment. As they approached the runway for landing the pilot said to her "Do you see the runway? I will reduce some power for landing." Moments after that statement the airplane collided with the airport boundary fence. On January 24, 2005, the Safety Board investigator and Textron-Lycoming technical representative examined the airplane and engine. The airplane's flight control cables and connections were traced from the cockpit to their respective control surfaces, demonstrating continuity. The right main landing gear sheared half off at mid strut, and the left main landing gear strut was intact. Seven gallons of fuel was recovered from the left fuel tank and 12 gallons were recovered from the right tank. During the engine exam, they achieved thumb compression on all cylinders, all valves lifted an appropriate amount and in firing order, and magneto timing on both magnetos was determined to be 25 degrees. The spark plugs were gray in color, which corresponded to normal service wear according to the Champion Aviation Check-A-Plug chart (AV-27), and they did not exhibit any mechanical damage. The airplane collided with an airport boundary fence about 500 feet short of the runway's approach end while on final approach for landing. A witness driving a pickup truck said that she saw the airplane cross in front of her truck about 10 feet above the ground going very fast and low. Immediately after the airplane crossed her path, it struck the airport boundary fence with its right main landing gear and impacted the dirt terrain beyond. The wreckage was about 500 feet from the approach end of the runway, and about 1,800 feet from the runway's displaced threshold. The passenger of the airplane said that this was her first flight with the pilot. She recalls that the flight was very pleasant, and the pilot did not express any concerns regarding the airplane or the environment. As they approached the runway for landing the pilot said to her "Do you see the runway? I will reduce some power for landing." Moments after that statement the airplane collided with the airport boundary fence. Examination of the airplane revealed no evidence of a preimpact malfunction or failure of the control system or power plant. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_LAX05LA064.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.