DEN08LA013 · Learjet 35A
Learjet 35A · Accident: loss of control in flight during landing
From Fort Worth Meacham International Airport (FTW) to Goodland Municipal Airport (GLD)
Event
- NTSB case
- DEN08LA013
- 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
- 0 · 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
- N31MC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Worth Meacham International Airport (FTW), Forth Worth, TXTo Goodland Municipal Airport (GLD), Goolland, KS
- 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
- Landing · flare/touchdown
- 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
- Substantial
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the flight crew, they exited the clouds approximately 250 feet above ground level, slightly left of the runway centerline. The pilot not flying took control of the airplane and adjusted the course to the right. The airplane rolled hard to the right and when the pilot corrected to the left, the airplane rolled hard to the left. The airplane impacted the ground in a right wing low attitude, resulting in substantial damage. Further examination and testing revealed anomalies with the yaw damper and spoileron computer. According to the manufacturer, these anomalies would not have prevented control of the airplane. Greater control wheel displacement and force to achieve a desired roll rate when compared with an operative spoileron system would be required. The result would be a slightly higher workload for the pilot, particularly in turbulence or crosswind conditions. An examination of the remaining systems revealed no anomalies.
Probable cause
The pilot's failure to maintain aircraft control during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08LA013
- Event ID
- 20071030X01686
- Case number
- DEN08LA013
- 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: 02d9817847ce47a651a44c392d11d2ed08e15eb18344dc077338a5b14a415558; retrieved 2026-09-22T03:20:18.499Z.