LAX06FA071 · Learjet 35A
Learjet 35A · Accident: loss of control in flight on approach
From Joslin Field Magic Valley Regional Airport (TWF) to Truckee Tahoe Airport (TRK)
Event
- NTSB case
- LAX06FA071
- 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
- Instrument Meteorological Cond
Learjet 35A
- Aircraft type
- Learjet 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
- N781RS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Joslin Field Magic Valley Regional Airport (TWF), Twin Falls, IDTo Truckee Tahoe Airport (TRK), Truckee, 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
- Approach · VFR pattern base
- 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(vso), not maintained
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Low altitude flight/maneuver, attempted
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with the ground during a low altitude, steep banked, base-to-final left turn toward the landing runway during a circling instrument approach. The airplane impacted terrain 1/3-mile from the approach end of runway 28, and north of its extended centerline. A witness, located in the airport's administration building, made the following statement regarding his observations: "I saw the aircraft in and out of the clouds in a close base for [runway] 28. I then saw the aircraft emerge from a cloud in a base to final turn [and] it appeared to be approximately 300-400 feet above the ground. The left wing was down nearly 90 degrees. The aircraft appeared north of the [runway 28] centerline. The aircraft pitched nose down approximately 30-40 degrees and appeared to do a 1/2 cartwheel on the ground before exploding." ATC controllers had cleared the airplane to perform a GPS-A (circling) approach. The published weather minimums for category C and D airplanes at the 5,900-foot mean sea level airport was 3 miles visibility, and the minimum descent altitude was 8,200 feet mean sea level (msl). Airport weather observers noted that when the accident occurred, the visibility was between 1 1/2 and 5 miles. Scattered clouds existed at 1,200 feet above ground level (7,100 feet msl), a broken ceiling existed at 1,500 feet agl (7,400 feet msl) and an overcast condition existed at 2,400 feet agl (8,300 feet msl). During the approach, the first officer acknowledged to the controller that he had received the airport's weather. The airplane overflew the airport in a southerly direction, turned east, and entered a left downwind pattern toward runway 28. A 20- to 30-knot gusty surface wind existed from 220 degrees, and the pilot inadequately compensated for the wind during his base leg-to-final approach turning maneuver. The airplane was equipped with Digital Electronic Engine Controls (DEEC) that recorded specific data bits relating to, for example, engine speed, power lever position and time. During the last 4 seconds of recorded data (flight), both of the power levers were positioned from a mid range point to apply takeoff power, and the engines responded accordingly. No evidence was found of any preimpact mechanical malfunction. The operator's flight training program emphasized that during approaches consideration of wind drift is essential, and a circling approach should not be attempted in marginal conditions.
Probable cause
The pilot's inadequate compensation for the gusty crosswind condition and failure to maintain an adequate airspeed while maneuvering in a steep turn close to the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA071
- Event ID
- 20060110X00039
- Case number
- LAX06FA071
- 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: 90c9cfbd518b4d671dbcfa83de167adfd3be9c3968390a91f5333597b91fded5; retrieved 2026-09-20T17:40:00.276Z.