FTW96LA084 · Learjet 60
Learjet 60 · Accident: on ground/water collision with terrain/water during landing
From El Paso International Airport (ELP) to Aspen-Pitkin County Airport (Sardy Field) (ASE)
Event
- NTSB case
- FTW96LA084
- 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
- 0
- 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 60
- Aircraft type
- Learjet 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
- XAICA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From El Paso International Airport (ELP), El Paso, TXTo Aspen-Pitkin County Airport (Sardy Field) (ASE)
- 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
- 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 terrain/water
- 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 › In-flight planning/decision, improper
- Pilot in command › Proper touchdown point, not identified
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain said he aligned the airplane with what he thought was the runway centerline. The airplane touched down in a snow field 1,000 feet beyond the runway threshold and 25 feet to the right of runway centerline. The nose landing gear collapsed and, after traveling through several snow berms, the airplane skidded back onto the runway and came to a halt at the 4,000 foot mark. The captain said he was unable to positively identify the runway environment due to the blending of the snow-covered runway and surrounding terrain. The runway had been plowed and swept. The runway lights were covered with plowed snow and were not visible nor operating. Excess snow and dirt were dumped on the right side of the runway. The sun was bright and high in the sky. A NOTAM had been issued, noting that the runway was snow packed and covered with ice. Braking action was reported to be 'fair.'
Probable cause
The pilot's improper in-flight decision to continue with the landing when the runway had not been positively identified. Factors were the snow-covered runway and landing area, sun glare, and the inadequate snow removal by airport personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA084
- Event ID
- 20001208X05131
- Case number
- FTW96LA084
- 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. 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: 857534097ec5a38b80fcfb0302c55efb0e7a3e0306fdaf56771bf8c833cada3e; retrieved 2026-09-22T22:54:39.629Z.