NTSB CAROL · Event
Event DEN01IA036
Aircraft involved
Probable cause & findings
the captain's failure to maintain the proper glide path. Contributing factors were the weather conditions that included low visibility and fog.
Factual narrative
On December 30, 2000, at 0808 mountain standard time, a McDonnell Douglas MD-90-30, N909DA, operated by Delta Air Lines, Inc., of Atlanta, Georgia, as flight 1147, sustained minor damage when it struck approach lights while landing at Salt Lake City International Airport, Salt Lake City, Utah. The airline transport rated captain and first officer, 3 flight attendants, and 75 passengers were not injured. Instrument meteorological conditions prevailed, and an IFR flight plan had been filed for the scheduled domestic passenger flight operating under Title 14 CFR Part 121. The flight originated at Kansas City, Missouri, at 0618 central standard time. According to the captain's incident report, the first approach briefing was made when ATIS (Automatic Terminal Information Service) indicated that a CAT (category) III ILS (instrument landing system) to runway 16R could be expected. When descent instructions were given, however, the descent profile was for landings to the north and this was confirmed by a revised ATIS information. The captain, who was flying the airplane, briefed the first officer for a second time, this time for a CAT III approach to runway 34R. Improved RVR (runway visual range) values indicated a Category I approach was feasible, and the decision was made to execute this approach. In his written statement that captain said, "At approximately 100 feet above minimums, I acquired the approach lights and by minimums I had acquired both the threshold and the runway. I disconnected the autopilot. As I began to initiate the flare, (the first officer) announced that sink rate was increasing. I crosschecked that my airspeed was correct and attempted to increase my pitch. Touchdown was firm but not hard and rollout was normal." Upon reaching the gate, the captain notified the control tower that he had "possibly touched down short of the runway." An airport operations vehicle reported observing an MD-90 land "prior to the numbers but had not touched down in the over run." Subsequent inspection revealed debris on runway 34R. According to airport personnel, the airplane struck the approach lights 400 feet short of the runway. Two threshold lights and one light each from the 100 foot and 200 foot approach light bars were found knocked off. Examination of the airplane disclosed damage to the left main wheel splash guard, and one of the tires was cut. A one-inch square piece of metal was found lodged in the left engine noise suppression material, and there was some damage to the left engine first stage fan section. The flight data recorder was sent to NTSB's Vehicle Recorder Division for readout. The Flight Data Recorder Factual Report is available in the public docket for this incident. Some of the findings of the report were: 1. Between 0758:50 and about 0800:30, the maximum glide slope deviation was -0.14 dots. 2. At 0800:32, the autopilot was disconnected. 3. At 0800:33, the control columns moved forward (-2.04 and -1.99 degrees, respectively) and the left and right elevators moved down (-3.53 and -2.90 degrees, respectively). 4. At 0800:39, nose down pitch was at its maximum (-1.23 degrees). 5. Glide slope warning occurred at 0800:41. 6. At 0800:44, nose up pitch (landing flare) was at its maximum (+5.45 degrees). 7. Weight on wheels (touchdown) on the left, right, and nose landing gears occurred at 0800:46, 0800:46, and 0800:48, respectively. Since electrical power was not interrupted after the incident and circuit breakers were not opened after the incident, the cockpit voice recorder was not retrieved because, being a closed loop 30 minute system, pertinent conversation would have been erased. At the time of the incident, Automatic Terminal Information Service (ATIS) Sierra was current: WIND, 330 degrees at 5 knots; VISIBILITY, less than 1/4-mile, freezing fog; SKY CONDITION, indefinite ceiling 100 feet; TEMPERATURE, -6 degrees Celsius; DEW POINT, -7 degrees Celsius; ALTIMETER, 30.24 inches of mercury; REMARKS, fog dispersal ongoing. The captain's first approach briefing was based on an ATIS report, indicating a CAT III ILS approach to runway 16R could be expected. When descent instructions were given, however, the descent profile was for landings to the north and this was confirmed by a revised ATIS information. The captain, who was flying the airplane, briefed the first officer for a second time for a CAT III approach to runway 34R. Improved RVR made a Category I approach feasible, and the decision was made to execute this approach. The captain said he acquired the approach lights 100 feet above minimums, and saw the threshold and runway when the airplane arrived at minimums. He disconnected the autopilot. As he began to flare, the first officer announced that sink rate was increasing. The captain attempted to increase pitch. Touchdown was "firm but not hard and rollout was normal." Upon reaching the gate, the captain notified the control tower that he had "possibly touched down short of the runway." An airport operations vehicle reported observing an MD-90 land "prior to the numbers but had not touched down in the over run." Subsequent inspection revealed debris on runway 34R. The airplane struck the approach lights 400 feet short of the runway. Two threshold lights and one light each from the 100 foot and 200 foot approach light bars were found knocked off. The airplane sustained damage to the left main wheel splash guard, and one tire was cut. A one-inch square piece of metal was lodged in the left engine noise suppression material, and there was some damage to the left engine first stage fan section. At the time of the incident, Automatic Terminal Information Service (ATIS) Sierra was current: WIND, 330 degrees at 5 knots; VISIBILITY, less than 1/4-mile, freezing fog; SKY CONDITION, indefinite ceiling 100 feet; TEMPERATURE, -6 degrees Celsius; DEW POINT, -7 degrees Celsius; ALTIMETER, 30.24 inches of mercury; REMARKS, fog dispersal ongoing. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_DEN01IA036.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- arXiv 2024 · arXiv preprint
A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2022 · arXiv preprint
Experimental Flight Testing of a Fault-Tolerant Adaptive Autopilot for Fixed-Wing Aircraft
This paper presents an adaptive autopilot for fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2021 · arXiv preprint
An Adaptive Digital Autopilot for Fixed-Wing Aircraft with Actuator Faults
This paper develops an adaptive digital autopilot for a fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2020 · arXiv preprint
Reinforcement Learning for Robust Missile Autopilot Design
Designing missiles' autopilot controllers has been a complex task, given the extensive flight envelope and the nonlinear flight dynamics.
Browse the full corpus — academia portal ↗