LAX06FA014 · Lancair LC-41-550FG
Lancair LC-41-550FG · Accident: in flight encounter with weather en route
From Gillespie Field (KSEE) to Scottsdale Airport (KSDL)
Event
- NTSB case
- LAX06FA014
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Lancair LC-41-550FG
- Aircraft type
- Lancair LC-41
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N285JB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillespie Field (KSEE), El Cajon, CATo Scottsdale Airport (KSDL), Scottsdale, AZ
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Flightcrew › Altitude/clearance, not maintained
- Flightcrew › Flight into known adverse weather, continued
- Flightcrew › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The single engine airplane collided with mountainous terrain at the 6,111-foot level while maneuvering below an overcast cloud layer. Meteorological conditions over the area consisted of overcast cloud bases between 6,000 and 7,000 feet mean sea level (msl), and a patchy broken cloud layer with bases around 2,000 to 3,000 feet msl. Cloud tops were between 7,000 and 10,000 feet msl, and the freezing level was at 10,000 feet msl. Light to moderate rime or mixed icing was likely in clouds above the freezing level. Terrain ridgelines above 6,000 feet were occasionally obscured in the vicinity of the accident location, and occasional moderate turbulence was present. The airplane was not certified for flight into known icing. The airplane was equipped with a global positioning system (GPS) that was tied into a moving map cockpit display, which included terrain features and obstacles. The onboard avionics had received via a real time data downlink the latest weather radar images, station meteorological reports, and flight route data. The airplane's onboard GPS track data history and the Federal Aviation Administration (FAA) recorded radar data tracked the airplane from its departure, following a northeasterly track and cruising at altitudes between 5,000 and 6,500 feet msl for about 40 miles. The airplane then made a gradual descent from 6,500 feet to about 6,000 feet msl, and entered a shallow turn to the east where the track ends at the accident site on the south slope of a 6,150-foot mountain. The easterly turn was consistent with a turn towards the first en route waypoint that was delivered by the datalink. The initial point of impact on the mountain slope was the left wing tip at the 6,111-foot level causing the airplane to tumble and breakup over a distance of 501 feet along the mountain ridgeline. Analysis of the impact ground scars and the track history data disclosed the airplane was in level controlled flight when the terrain collision occurred. The airplane's owner, a non instrument rated private pilot, was in the left seat. The right seat occupant held airline transport pilot and certified flight instructor certificates.
Probable cause
The flight crew's failure to maintain adequate terrain clearance and their decision to continue flight into known adverse weather conditions. Contributing to the accident was overcast conditions, and terrain obscuration. A finding of the investigation is that the flight crew may have improperly used the navigation equipment, which had a graphical moving map display capability, to guide the airplane between clouds and mountainous terrain while in obscured visibility conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA014
- Event ID
- 20051026X01740
- Case number
- LAX06FA014
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: caba392df044506a0fc4ace30b55a0978b6e1f80ee8be5915ddced513af6c5a3; retrieved 2026-09-20T17:48:16.082Z.