FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02FA210 · Beech C35

29 Jun 2002 · Chambers, AZ, United States

Beech C35 · Accident: loss of control in flight en route

From Double Eagle II Airport (AEG) to Pierce Airport (10AZ)

Report a problem

Event

NTSB case
LAX02FA210
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
1 · 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

Beech C35

Aircraft type
Beechcraft 35
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
N5856C
Operator
William C. Wood · private individual
Onboard fatalities
Unknown
Route
From Double Eagle II Airport (AEG), Albuquerque, NMTo Pierce Airport (10AZ), Buckeye, 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
Loss of control in flight
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Fatigue

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a nighttime cross-country flight in clear visual meteorological conditions, the airplane departed from controlled flight and broke up during a steep high speed descent. Wreckage was located over a 1,650-foot-long southerly path about 0.4 miles from the last recorded radar position, with the right wing and right stabalator found early in the debris field. The pilot had awakened at 0600 and reported for work at 0750, and he had flown five contract flights dispersing fire retardant chemical on wildfires for a total of 7.4 flight hours on the day of the accident. Upon completing his last flight about 1900, the pilot was overheard stating "we had a tough one today." He then laid his head down on the airplane's wing and said, "dang I'm tired." A second associate reported that the pilot had experienced difficulty completing the required end of day paperwork, making arithmetic errors during simple addition calculations. This associate thought the pilot was tired and "mentally exhausted." The pilot told this associate that he was going to spend the night in a local hotel, but instead he departed about 2022. The pilot requested and received VFR radar flight following service, and at no time did the pilot indicate he was experiencing any difficulties or request assistance. Following about an hour of cruise flight at 10,500 feet, during the last 19 seconds of radar-recorded flight, the airplane's average ground track changed from 241 degrees to 170 degrees, while its altitude increased from 10,900 to 11,000 feet. There were no further altitude readouts. The airplane broke apart in flight and impacted flat, desert terrain at an altitude of about 6,200 feet mean sea level. The right wing spar fractures were positive overload failures and evidence shows that it separated and impacted the right stabilizer, which also then separated.

Probable cause

The pilot's loss of airplane control after falling asleep due to fatigue, which resulted in a structural failure of the airframe during a high speed descent after the design stress limits of the aircraft were exceeded.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02FA210
Event ID
20020715X01133
Case number
LAX02FA210
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-06-30.
  • API snapshot SHA-256: 564ffc558dd2dac5bb643e27f5f082305af54e0e9a88ed51acbf1d2f15984b77; retrieved 2026-09-20T19:58:29.332Z.