ATL01FA021 · Learjet LJ-60
Learjet LJ-60 · Accident: on ground/water collision with object during landing
From Dallas Love Field (DAL) to Troy Municipal Airport at N Kenneth Campbell Field (TOI)
Event
- NTSB case
- ATL01FA021
- 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
- Visual Meteorological Cond
Learjet LJ-60
- Aircraft type
- Learjet LJ-60
- 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
- N1DC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL), Dallas, TXTo Troy Municipal Airport at N Kenneth Campbell Field (TOI), Troy, AL
- 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 · landing roll
- 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
- On ground/water collision with object
- 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
- Object › Animal(s)
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 witnesses, the airplane collided with two deer shortly after touchdown. Following the collision, the airplane continued down the runway with the tires smoking, veered off the right side of the runway near the end, crossed a taxiway, impacted into a ditch and burst into flames. After the accident, the captain and first officer both reported that the thrust reversers failed to operate after they were deployed during the landing.
Examination of the landing gear found all three gear collapsed. The right and left main tires had areas of rubber that were worn completely through. The flaps were found extended, and both thrust reversers were found in the stowed position. Examination of the cockpit found the throttles in the idle position, and the thrust reverser levers in the stowed position.
Aircraft performance calculations indicate that the airplane traveled 1,500 feet down the runway after touchdown, in 4.2 seconds, before striking the deer. The calculations also indicate that the airplane landed with a ground speed of 124 knots. At 124 knots and maximum braking applied, the airplane should have come to a complete stop in about 850 feet. However, investigation of the accident site and surrounding area revealed heavy black skid marks beginning at the first taxiway turnoff about 1,500 feet down the 5,010 foot runway. The skid marks continued for about 2,500 feet, departed the right side of the runway and proceeded an additional 500 feet over grass and dirt.
The investigation revealed that deer fur was found lodged in the squat switch on the left main landing gear, likely rendering the squat switch inoperative after the impact with the deer, and prior to the airplane’s loss of control on the runway. Since a valid signal from the squat switch is required for thrust reverser deployment, the loss of this signal forced the thrust reversers to stow. At this point, the electronic engine control (EEC) likely switched to the forward thrust schedule and engine power increased to near takeoff power, which led to the airplane to continue down the runway, and off of it.
Following the accident, the manufacturer issued an Airplane Flight Manual revision that changed the name of the “Inadvertent Stow of Thrust Reverser During Landing Rollout” abnormal procedure to “Inadvertent Stow of Thrust Reverser After a Crew-Commanded Deployment” and moved it into the emergency procedures section.
[ This Brief of Accident was modified on April 5, 2010, based on information obtained during NTSB Case No. DCA08MA098. ]
Probable cause
On ground collision with deer during landing roll, and the inadvertent thrust reverser stowage caused by the damage to the landing gear squat switch by the collision, and subsequent application of forward thrust during rollout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL01FA021
- Event ID
- 20010119X00328
- Case number
- ATL01FA021
- 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: 4440e6263f10671060b6be0b4f680e53332840885f6725066386e2b50af2967e; retrieved 2026-09-21T10:15:21.604Z.