FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07FA026 · Aircraft Mfg & Dev. Co. (AMD) CH601XL SLSA

4 Nov 2006 · Yuba City, CA, United States

Aircraft Mfg & Dev. Co. (AMD) CH601XL SLSA · Accident: airframe, component or system failure en route

From Lincoln Regional Karl Harder Field (LHM) to Willows Glenn County Airport (WLW)

Report a problem

Event

NTSB case
LAX07FA026
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
2 · 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

Aircraft Mfg & Dev. Co. (AMD) CH601XL SLSA

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
N158MD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lincoln Regional Karl Harder Field (LHM), Lincoln, CATo Willows Glenn County Airport (WLW), Willows, CA
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
Airframe, component or system failure
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

  • Horizontal stabilizer › Separation
  • Reason for occurrence undetermined
  • Wing › Separation

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Recorded radar data showed that the airplane was at 2,600 feet mean sea level cruising on course. It entered a gradual climb to 2,800 feet, leveled off, and then entered a 2,000-foot-per-minute rate of descent, which was followed by a profusion of primary radar targets around the secondary target. The wreckage was found within 1/2 mile of the last radar return with signatures consistent with an in-flight breakup. Several witnesses were found and none saw any adverse weather conditions in the area. One witness said the airplane had been in straight and level flight just prior to the breakup. The airframe was examined by Safety Board engineering and metallurgical specialists. Other than some assembly anomalies unrelated to the breakup, no evidence of any assembly contrary to design plans or material deficiency was found that related to the integrity of wings, stabilizer, or flight control surfaces. No evidence of fatigue, corrosion, or previous damage was found. The separation of the wings and horizontal stabilizer was in a downward direction. All observed fracture surfaces were overload, and no oscillatory loading of the control surfaces was apparent. Analysis of the radar data revealed that the climb and descent that occurred before the breakup did not require aggressive control inputs. The pitch angle would have changed about 0.4 degrees per second during the climb, and would have decreased about 0.75 degrees per second in the descent, with generated load factors ranging between 1.04 G and 0.88 G. A radar return is only received once every 4.5 seconds and contains uncertainties in both altitude and position measurements. Consequently, the radar may not have detected an abrupt control input that would overload the aircraft structure before the airplane position and altitude changed significantly. While there is no evidence of an abrupt control input or aggressive maneuvering in the available radar data, because of the limitations in the data, the possibility of an abrupt control input cannot be excluded. This airplane is very responsive in pitch control. One of the handling quality characteristics designed by the airplane's manufacturer is that movement of the control stick produces large and rapid changes in pitch attitude.

Probable cause

In-flight structural failure of the horizontal stabilizer and wings for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07FA026
Event ID
20061115X01677
Case number
LAX07FA026
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. 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: 10551fa011f4eaa63ce71a65e82d44bc79cc1387de0afef73a52c643f06a3171; retrieved 2026-09-20T17:00:18.834Z.