FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07LA130 · Beech 35-B33

15 Apr 2007 · Sedona, AZ, United States

Beech 35-B33 · Accident: loss of control in flight on approach

From K57A · Tucson, AZ to Sedona Airport (KSEZ)

Report a problem

Event

NTSB case
LAX07LA130
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

Beech 35-B33

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
N9556Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From K57A · Tucson, AZTo Sedona Airport (KSEZ), Sedona, 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
Approach · VFR pattern final
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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 › Airspeed, not maintained
  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Stall, encountered

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 impacted the slope of a bluff 200 feet short of, and below, the runway and was destroyed during the ensuing post impact fire. The airport is located on a plateau, with terrain that drops off steeply at both ends of the single runway. Wind gusts at the runway surface were recorded at 38 knots. According to FAA publication AC 00-57 - "Hazardous Mountain Winds and Their Visual Indicators," strong winds that are at the crest of a ridge or level with a mountain peak can create moderate or greater turbulence, strong up and down drafts, and very strong rotor and shear zones. Wind shear is defined as "A sudden, drastic shift in wind speed, direction, or both that may occur in the horizontal or vertical plane." A pilot, who had landed at the airport just before the accident airplane, reported severe turbulence and a 30-knot windshear at the approach end of the runway, and transmitted that information to the accident pilot. According to witnesses, the accident airplane appeared to get low and slow while on final, likely encountered an abrupt wind shear zone, and descended below the elevation of the approach end of the runway. To maintain the airplane flying, and to avoid the terrain, the pilot would have had to raise the nose, which increased the wings angle of attack, and therefore, decreased the stall margin. As it dropped below the level of the runway, a witness reported that the airplane assumed a nose high attitude, and the engine sounded as if it were operating at high rpm and "straining against the wind." The wing tips wobbled up and down, indicative of a stall, before the airplane rolled to the right and impacted rising terrain short of the runway. According to another pilot who routinely flew with the accident pilot, the accident pilot routinely flew approaches that were shallower than the 3.5-degree glide slope approach path that is recommended at this airport, which is equipped with a precision approach path indicator (PAPI) lighting system set to 3.5 degrees. In this instance, the pilot let the airplane drop well below the recommended glide slope during the approach to this runway. Medications that were identified in the pilot's toxicological report had been prescribed to treat his ongoing medical conditions and relieve pain. While the medications can cause impairment or spatial disorientation, the clear weather on this day, the low levels of medication found in the pilot's system (suggesting no recent use), and the circumstances of the accident make it unlikely that the medications had an effect on the pilot's ability to control the aircraft.

Probable cause

The pilot's inadequate compensation for the high wind conditions and wind shear encounter on final approach, that led to a failure to maintain an adequate airspeed and a stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07LA130
Event ID
20070418X00434
Case number
LAX07LA130
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: 11a673be72f2713b25a1cf92c0b83392e205d80baae8739fb2edb3af3b1bd8fb; retrieved 2026-09-20T16:44:02.020Z.